Re: C64 system cost?
- Original Message - From: "Jim Brain" To: "General Discussion: On-Topic and Off-Topic Posts" Sent: Thursday, January 21, 2016 1:11 AM Subject: Re: C64 system cost? > On 1/20/2016 1:37 PM, Pete Rittwage wrote: >> That is an extremely good price... However, the site is very old and he >> takes a very long time to reply, typically. (Months and months, if ever!) > Is that recently? I know Joe's daddied and that interrupted things, but > I thought he has been responsive lately. > > I'd still contact him. Mike S is on here, and I'm on the toronto > mailing list, where lots of people close to Joe can get to him if you > don't get a response. > I spoke to Joe and he is indeed still very much in business; if you're looking for something VIC/C64/C128 related you might want to contact him and inquire, and let us know if you have any problems reaching him. BTW, one of the reasons for the simplicity of his web page is so that a C64 can access it. m
Re: SD Card disk drive for C-64?
- Original Message - From: "Jim Brain" To: "General Discussion: On-Topic and Off-Topic Posts" Sent: Saturday, January 23, 2016 10:28 PM Subject: Re: SD Card disk drive for C-64? > On 1/23/2016 8:58 PM, Eric Christopherson wrote: >> On Sat, Jan 23, 2016, Jim Brain wrote: ... snippage >>> After the PET intro, Peddle designs a drive, a beast of a device, with 2 >>> CPUs and it costs a fortune. Peddle is convinced a smart drive is best, and >>> the delay allows other manufactures to create "dumb" drive options (saw one >>> at World of Commodore, forgot the name). >> How did these dumb drives interface with the computer at a software >> level? I'd think a DOS would need to be loaded somehow. >> > The one I saw at the WoC was a 8" drive connected to a PSU and the cable > attached to a small PCB that replaced the editor ROM in the PET. THe > PCB mapped a controller into the address space and the editor ROM was > patched to support a DOS. > > It was an interesting setup. Mike N (of 6502.org) had the unit. Steve > Gray on here was there too and could provide more details. > > Jim --- I was the third guy at Mike's WoC booth trying to help figure out why it wasn't working initially; took a while for one of us to notice that the PET we were using was a different revision than the one Mike used at home and it had to be connected slightly differently. I also made a cable to try using a 5.25HD drive instead of the 8" but we (I) didn't have enough time to get that working completely. The device in question is a CGRS Microtech PEDisk II and just like most systems it has a boot ROM which provides some low level functions including the loading of a DOS from disk, which in turn is accessed with a set of 'wedge' commands. When I asked here recently about cloning a PCB this is the one I had in mind, but we'll need a schematic anyway sooner or later; Mike's already done a heck of a job reverse-engineering the software. More info here: http://mikenaberezny.com/hardware/pet-cbm/cgrs-microtech-pedisk-ii/ m
Re: IDE knowledge anyone?
On Sun, 24 Jan 2016, Maciej W. Rozycki wrote: > "Note: Previous ATA specifications were unclear about the error conditions > that this command may indicate. Some implementations do not indicate any > errors for this command even when the command fails. However, most of > these implementations do fail media access commands if a valid CHS > translation is not in effect." > > -- which is (the latter sentence, that is) obviously what you've been > observing with your WD drive. Furthermore: "Note: Some ATA-1 devices require that this command be issued prior to media access." Maciej
Re: IDE knowledge anyone?
On Wed, 30 Dec 2015, Oliver Lehmann wrote: > Command 91h did the trick. Issueing this once before any > read/write commands makes the drive finally work! FYI, this is what ATA-2 has to say about this command: "Note: Previous ATA specifications were unclear about the error conditions that this command may indicate. Some implementations do not indicate any errors for this command even when the command fails. However, most of these implementations do fail media access commands if a valid CHS translation is not in effect." -- which is (the latter sentence, that is) obviously what you've been observing with your WD drive. Also: "A device shall support the CHS translation described in words 1, 3 and 6 of the IDENTIFY DEVICE information. Support of other CHS translations is optional." FWIW, and good luck with your project! Maciej
Re: VT100 PSU smelling.
On Sat, 23 Jan 2016, Jules Richardson wrote: On 01/22/2016 06:26 PM, Tothwolf wrote: The translucent yellow Rifa (now owned by Kemet) class X/Y safety capacitors in particular have a 100% failure rate and are on my replace-on-sight list. They usually begin to show visible signs of cracking in their outer casing before they finally go out with a bang. It's a well-known fault, but has anyone ever known one fail and actually cause any damage (other than to itself)? AIUI, they're there to reduce noise from the device leaking back out onto the AC supply - a system should run quite happily without them. I've had maybe four or five fail on me over the years, out of several hundred systems. They're a definite weak spot, but given that I've never heard of one damaging anything it's the sort of thing I'd consider doing only if I was carrying out some other repair work on the PSU. I've seen blown/cooked series resistors (which I replace with metal oxide resistors) and sometimes a blown fuse. I always replace them whey I'm doing other work on a psu, however I'm not sure I'd knowingly leave one in place since they let out a lot of smoke when they go. I usually replace them with a film capacitor from Epcos of the same value and safety class. Is the voltage rating on the US ones different (new vs. old)? I can't remember now. I know all the old UK ones seemed to be 250V, while modern parts were rated at 275V. Higher voltage parts are available but they are more expensive. I've seen 300V, 350V, 375V and even 400V safety rated parts.
Re: SD Card disk drive for C-64?
I can't say much about the other brands, but so far as Apple was concerned, you're exactly correct. The Apple Disk II drives were quite 'dumb' and required a disk controller card (installed in a slot, on the motherboard) plus a software DOS (3.2, 3.3, etc.) loaded at startup from a bootable disc. If one weren't careful, it was no trouble to start up an Apple II machine, write a nice piece of BASIC code, and then be unable to save it to disc - as the DOS had not yet been loaded. Very annoying, but not a mistake you'd make more than once or twice.. as loading the DOS requires a system reset, losing anything in RAM at that time. On Sat, Jan 23, 2016 at 8:58 PM, Eric Christopherson < echristopher...@gmail.com> wrote: > On Sat, Jan 23, 2016, Jim Brain wrote: > > On 1/23/2016 7:15 PM, drlegendre . wrote: > > >" I am saying don't make a permanent hardware change to a 1541 that > > >does not have the switches unless you really want it to be permanent > > >because there is a software method of assigning drives that is good > enough > > >most of the time. BUT if you must make it permanent and you don't have > the > > >external switches, consider adding some form of external switch so you > > >don't ever have to open the case again to put it back to the default." > > > > > >Well then, we're having a major agreement. ;-) > > > > > >The device ID switch is the ultimate fix for Commodore drives, and I'm > > >really not sure why CBM didn't incorporate one into the design - at > least > > >from the 1540 on upwards. Can't have cost much to add a discretely > located > > >access hole (or a knock-out) in the case, along with a 2-place DIP > switch > > >for controlling device ID. > > But, they did. The 1541-II, 71, and the 81 have switches. > > > > I would disagree on your point that Commodore should have made it part of > > the design... > > > > Let's travel back in time. > > > > After the PET intro, Peddle designs a drive, a beast of a device, with 2 > > CPUs and it costs a fortune. Peddle is convinced a smart drive is best, > and > > the delay allows other manufactures to create "dumb" drive options (saw > one > > at World of Commodore, forgot the name). > > How did these dumb drives interface with the computer at a software > level? I'd think a DOS would need to be loaded somehow. > > -- > Eric Christopherson >
Re: SD Card disk drive for C-64?
On 1/23/2016 8:58 PM, Eric Christopherson wrote: On Sat, Jan 23, 2016, Jim Brain wrote: On 1/23/2016 7:15 PM, drlegendre . wrote: " I am saying don't make a permanent hardware change to a 1541 that does not have the switches unless you really want it to be permanent because there is a software method of assigning drives that is good enough most of the time. BUT if you must make it permanent and you don't have the external switches, consider adding some form of external switch so you don't ever have to open the case again to put it back to the default." Well then, we're having a major agreement. ;-) The device ID switch is the ultimate fix for Commodore drives, and I'm really not sure why CBM didn't incorporate one into the design - at least >from the 1540 on upwards. Can't have cost much to add a discretely located access hole (or a knock-out) in the case, along with a 2-place DIP switch for controlling device ID. But, they did. The 1541-II, 71, and the 81 have switches. I would disagree on your point that Commodore should have made it part of the design... Let's travel back in time. After the PET intro, Peddle designs a drive, a beast of a device, with 2 CPUs and it costs a fortune. Peddle is convinced a smart drive is best, and the delay allows other manufactures to create "dumb" drive options (saw one at World of Commodore, forgot the name). How did these dumb drives interface with the computer at a software level? I'd think a DOS would need to be loaded somehow. The one I saw at the WoC was a 8" drive connected to a PSU and the cable attached to a small PCB that replaced the editor ROM in the PET. THe PCB mapped a controller into the address space and the editor ROM was patched to support a DOS. It was an interesting setup. Mike N (of 6502.org) had the unit. Steve Gray on here was there too and could provide more details. Jim -- Jim Brain br...@jbrain.com www.jbrain.com
Re: ESR meter recommendations.
On Sat, 23 Jan 2016, Mattis Lind wrote: 2016-01-23 13:54 GMT+01:00 Noel Chiappa : If you do a lot of work with analog components (and it sounds like you do), it's probably worth getting capacitance and ESR meters, they can be obtained (new) on eBay for not that much. I have one of each that I got that way; their quality is pretty good, considering how little I paid for them (I didn't think I'd be using them enough to make it worth paying out a lot for really good ones). I haven't used the ESR meter much, but the capacitance meter works quite well, and has been very helpful. Of course, it can't be used in-circuit, but... Yes. agree with you.I really should get one. I have been thinking I need to get one every time I get my head into anther PSU and then everything is sorted out and the PSU seems to work fine and I forget about it. I have been looking at the DerEE DE-5000 which looks nice and has got good reviews as far as I can tell. What meter do you have and recommend? The one I absolutely cannot in good faith recommend (unless you are going to custom build it) is one that seems to come up in these discussions the most, and that is the Blue ESR from Anatek. The design itself isn't that bad, however Anatek used some of the worst junk-sourced parts I have ever seen when they kitted up the one I bought. I used the pre-programmed micro, the led displays, and most of the fixed value resistors, but junked most of the rest of the components they included and used my own. The trimmer resistors they included didn't even fit the pad layout of the board. The wire they included to make the "test leads" was also really bad quality and was wadded up and kinked. I fitted some shrouded banana jacks to my tester instead of the short hard wired leads. Another thing to keep in mind with the Blue ESR is that the firmware has a limitation and cannot measure small value capacitors (under 0.1uF?) and it also only goes down to 0.01 ohms.
RE: VT100 PSU smelling.
On Sat, 23 Jan 2016, tony duell wrote: Incidentally, some machines have those sealed metal cans containing filter capacitors, inductors and sometimes discharge resistors [2]. Has anyone ever had the capacitors in one of those fail? Actually, yes. I had one fail in one of my scopes. I don't recall the brand/series right now, but it is apparently a known issue with that particular series of filters. I still need to replace the same filters in the other scopes since they will most like do the same thing eventually. [2] I wish the manufacturers would print a schematic on the can, or at least in an available data sheet. If I measure a 1M leak to earth from the live pin (say), I want to know if it's a deliberate discharging resistor or a leaking capacitor. Most of the IEC320 input filters I've used have a schematic on the can or in the datasheet. They are usually also careful to denote the medical-rated filters which lack the Y-type safety capacitors between the two supply terminals and ground.
Re: SD Card disk drive for C-64?
On Sat, Jan 23, 2016, Jim Brain wrote: > On 1/23/2016 7:15 PM, drlegendre . wrote: > >" I am saying don't make a permanent hardware change to a 1541 that > >does not have the switches unless you really want it to be permanent > >because there is a software method of assigning drives that is good enough > >most of the time. BUT if you must make it permanent and you don't have the > >external switches, consider adding some form of external switch so you > >don't ever have to open the case again to put it back to the default." > > > >Well then, we're having a major agreement. ;-) > > > >The device ID switch is the ultimate fix for Commodore drives, and I'm > >really not sure why CBM didn't incorporate one into the design - at least > >from the 1540 on upwards. Can't have cost much to add a discretely located > >access hole (or a knock-out) in the case, along with a 2-place DIP switch > >for controlling device ID. > But, they did. The 1541-II, 71, and the 81 have switches. > > I would disagree on your point that Commodore should have made it part of > the design... > > Let's travel back in time. > > After the PET intro, Peddle designs a drive, a beast of a device, with 2 > CPUs and it costs a fortune. Peddle is convinced a smart drive is best, and > the delay allows other manufactures to create "dumb" drive options (saw one > at World of Commodore, forgot the name). How did these dumb drives interface with the computer at a software level? I'd think a DOS would need to be loaded somehow. -- Eric Christopherson
Re: VT100 PSU smelling.
On Sat, 23 Jan 2016, Mattis Lind wrote: I don't have a ESR meter or similar. It is not shorted at least and the resistance is in the several mega ohm range when measuring in circuit. Are they likely to go bad in a non catastrophic way? They can. The translucent yellow Rifa (now owned by Kemet) class X/Y safety capacitors in particular have a 100% failure rate and are on my replace-on-sight list. They usually begin to show visible signs of cracking in their outer casing before they finally go out with a bang. It seems to be due to chemical decomposition of the paper insulator which swells over time and causes the case to crack. I usually replace them with a film capacitor from Epcos of the same value and safety class. This is a 0.0033 uF 1600VDC SPARAGUE capacitor. It looks nice and orange and there are no signs of cracks whatsoever. What is the likelihood of this being bad? I've seen similar Panasonic and Sprague film capacitors fail in snubbers used in flyback circuits, so it is certainly possible. As inexpensive and readily available as these parts are, when in doubt, I just replace them. I would probably also replace the series resistor is there is any doubt that it might not be reliable (I often do this for carbon comp and carbon film resistors used in series with the Rifa safety capacitors I replace).
Re: SD Card disk drive for C-64?
On Sat, Jan 23, 2016, drlegendre . wrote: > " I am saying don't make a permanent hardware change to a 1541 that > does not have the switches unless you really want it to be permanent > because there is a software method of assigning drives that is good enough > most of the time. BUT if you must make it permanent and you don't have the > external switches, consider adding some form of external switch so you > don't ever have to open the case again to put it back to the default." > > Well then, we're having a major agreement. ;-) > > The device ID switch is the ultimate fix for Commodore drives, and I'm > really not sure why CBM didn't incorporate one into the design - at least > from the 1540 on upwards. Can't have cost much to add a discretely located > access hole (or a knock-out) in the case, along with a 2-place DIP switch > for controlling device ID. I'm feeling my C128 privilege here -- the 1571 and 1581 always had DIPs for just that purpose, and I never even realized the 1540/1 didn't. -- Eric Christopherson
Re: RIFA EMI caps [WAS: Re: VT100 PSU smelling.]
On Sat, 23 Jan 2016, Chuck Guzis wrote: On 01/23/2016 02:40 PM, Pontus wrote: All I could find were new similar Kemet capacitors. Do you know if newer Kemet suffer from the same problem and I will regret buying them? I usually replace the Rifa capacitors with equivalent polyester safety caps (X or Y rated). Kemets are most common and work just fine. It's not a bad idea, if you're in a 240AC mains country to bump the AC voltage rating up a bit. I've seen too many line filters with 250VAC rated caps labeled for either 120 or 240V use. That would make me nervous if I lived in a 240V country. Kemet bought out Rifa and the parts from Kemet with the same P/N also use a paper insulator. Rifa used to tout the paper insulator as a selling point, but after seeing so many fail, I won't touch them, new manufacture or not. I'm using Epcos brand polyester film safety capacitors as replacements. So far I've been able to match them up 1:1 with the correct physical sizes (lead spacing) and values.
Re: SD Card disk drive for C-64?
Jim, That's an interesting and colorful narrative, and much of it makes good sense - in the giddy days of the 1980s home computer market, and for CBM in particular. But speaking as one who was fairly hot & heavy into the VIC-20 (and then almost immediately the C-64), this 'drive ID' issue has more-or-less dogged us since day one. While it's true that +most+ end-users couldn't or didn't buy a second 1541, it was very common to connect two or more drives to a single machine for demonstrations, software shows, user group meetings or what might have been the 1980's equivalent of the LAN party.. where we shared & swapped software. And on top of that, as time wore on, there were a number of programs that supported multiple drives. So we can agree that Jack, being Jack, had his reasons. But ultimately, I still see this decision as short-sighted. There's a reason that the circuit board jumper pads were well-publicized, as were the many text files on adding device ID switches to the 1541. On Sat, Jan 23, 2016 at 7:33 PM, Jim Brain wrote: > On 1/23/2016 7:15 PM, drlegendre . wrote: > >> " I am saying don't make a permanent hardware change to a 1541 that >> does not have the switches unless you really want it to be permanent >> because there is a software method of assigning drives that is good enough >> most of the time. BUT if you must make it permanent and you don't have >> the >> external switches, consider adding some form of external switch so you >> don't ever have to open the case again to put it back to the default." >> >> Well then, we're having a major agreement. ;-) >> >> The device ID switch is the ultimate fix for Commodore drives, and I'm >> really not sure why CBM didn't incorporate one into the design - at least >> from the 1540 on upwards. Can't have cost much to add a discretely located >> access hole (or a knock-out) in the case, along with a 2-place DIP switch >> for controlling device ID. >> > But, they did. The 1541-II, 71, and the 81 have switches. > > I would disagree on your point that Commodore should have made it part of > the design... > > Let's travel back in time. > > After the PET intro, Peddle designs a drive, a beast of a device, with 2 > CPUs and it costs a fortune. Peddle is convinced a smart drive is best, > and the delay allows other manufactures to create "dumb" drive options (saw > one at World of Commodore, forgot the name). > > Tramiel is mad, and the drive doesn;t sell terribly well at first. > > When the VIC-20 comes out, the drive is just marketing materials. Why > would someone want a business storage system for a home computer basically > built because Jack needs to unload a bunch of VIC-I ICs that he can't sell > to video game firms? > > But, people asked for it, and CBM delivered, taking Peddles IEEE design, > ditching the IEEE cabling (Jack: "Get OFF that bus", as the cables from > Belden/Beldin(sp?) cost a mint and supplies had been spotty at times). The > unit is retooled to use 1 drive, 1 CPU (and in the process the changes > introduce the fabled "save with replace" bug. Enter the 1540 > > But, the designers put little jumper pads on the drive to set dev number, > as they were very sure most people would never buy two of them. > > Then the 64. Paddle's ColorPET design loses out to a hacked VIC-20, which > became the 64 > > Now the drive seems more useful, and can be made more cheaply. As well, > other units in the marketplace have drives, so it is a competitive need. > All is well, though, as the 1540 is already in production. Dump some gray > tan/gray colorant in the injection mold machines, and you're done. That's > classic Jack. > > The 1540 has a problem though. The bit banging protocol (introduced late > in the 1540 design cycle after it was determined that the VIC shift > register has issues) fails on the 64. high/low times are 20uS/20uS, and > sometimes the CPU is stopped for 50uS on the 64. Enter the 1541. No > changes except the ROM, which slows down sends from the drive to the 64 to > 60/60uS clock. Jack is done. He doesn't care if people buy them per se, > just that the drive is there so he can tout it being there as he competes > with the Apples and Ataris. > > So, at the time, with the drive being as much as the computer, no one > thought people would buy more than 1, and thus no need to pay for extra > parts (switches) and changing the molds. > > With the C128 and the case redesigns, people were buying multiple drives, > and it was a selling point, so the switches made their appearance. > > Jim >
Re: SD Card disk drive for C-64?
On 1/23/2016 7:15 PM, drlegendre . wrote: " I am saying don't make a permanent hardware change to a 1541 that does not have the switches unless you really want it to be permanent because there is a software method of assigning drives that is good enough most of the time. BUT if you must make it permanent and you don't have the external switches, consider adding some form of external switch so you don't ever have to open the case again to put it back to the default." Well then, we're having a major agreement. ;-) The device ID switch is the ultimate fix for Commodore drives, and I'm really not sure why CBM didn't incorporate one into the design - at least from the 1540 on upwards. Can't have cost much to add a discretely located access hole (or a knock-out) in the case, along with a 2-place DIP switch for controlling device ID. But, they did. The 1541-II, 71, and the 81 have switches. I would disagree on your point that Commodore should have made it part of the design... Let's travel back in time. After the PET intro, Peddle designs a drive, a beast of a device, with 2 CPUs and it costs a fortune. Peddle is convinced a smart drive is best, and the delay allows other manufactures to create "dumb" drive options (saw one at World of Commodore, forgot the name). Tramiel is mad, and the drive doesn;t sell terribly well at first. When the VIC-20 comes out, the drive is just marketing materials. Why would someone want a business storage system for a home computer basically built because Jack needs to unload a bunch of VIC-I ICs that he can't sell to video game firms? But, people asked for it, and CBM delivered, taking Peddles IEEE design, ditching the IEEE cabling (Jack: "Get OFF that bus", as the cables from Belden/Beldin(sp?) cost a mint and supplies had been spotty at times). The unit is retooled to use 1 drive, 1 CPU (and in the process the changes introduce the fabled "save with replace" bug. Enter the 1540 But, the designers put little jumper pads on the drive to set dev number, as they were very sure most people would never buy two of them. Then the 64. Paddle's ColorPET design loses out to a hacked VIC-20, which became the 64 Now the drive seems more useful, and can be made more cheaply. As well, other units in the marketplace have drives, so it is a competitive need. All is well, though, as the 1540 is already in production. Dump some gray tan/gray colorant in the injection mold machines, and you're done. That's classic Jack. The 1540 has a problem though. The bit banging protocol (introduced late in the 1540 design cycle after it was determined that the VIC shift register has issues) fails on the 64. high/low times are 20uS/20uS, and sometimes the CPU is stopped for 50uS on the 64. Enter the 1541. No changes except the ROM, which slows down sends from the drive to the 64 to 60/60uS clock. Jack is done. He doesn't care if people buy them per se, just that the drive is there so he can tout it being there as he competes with the Apples and Ataris. So, at the time, with the drive being as much as the computer, no one thought people would buy more than 1, and thus no need to pay for extra parts (switches) and changing the molds. With the C128 and the case redesigns, people were buying multiple drives, and it was a selling point, so the switches made their appearance. Jim
Re: SD Card disk drive for C-64?
Pardon the quick re-post.. FYI, you don't actually need a BASIC program to change a drive ID. This 'one-liner' will do the job just fine: OPEN 15,8,15:PRINT#15,"M-W";CHR$(119);CHR$(0);CHR$(2);CHR$(*device number* +32)+CHR$(*device numver*+64):CLOSE 15 Again, this change will not persist between drive (and possibly IEC bus) resets. The drive will reset to its original hardware-assigned device number (8 on an unmodified drive) upon reset. On Sat, Jan 23, 2016 at 7:15 PM, drlegendre . wrote: > " I am saying don't make a permanent hardware change to a 1541 that > does not have the switches unless you really want it to be permanent > because there is a software method of assigning drives that is good enough > most of the time. BUT if you must make it permanent and you don't have the > external switches, consider adding some form of external switch so you > don't ever have to open the case again to put it back to the default." > > Well then, we're having a major agreement. ;-) > > The device ID switch is the ultimate fix for Commodore drives, and I'm > really not sure why CBM didn't incorporate one into the design - at least > from the 1540 on upwards. Can't have cost much to add a discretely located > access hole (or a knock-out) in the case, along with a 2-place DIP switch > for controlling device ID. > > Grumble grumble.. > > On Sat, Jan 23, 2016 at 6:33 PM, Jim Brain wrote: > >> On 1/23/2016 6:28 PM, Eric Christopherson wrote: >> >>> On Sat, Jan 23, 2016, Jim Brain wrote: >>> On 1/23/2016 2:18 PM, drlegendre . wrote: > First off, my bad - I thought the OP was wanting to change the device > ID > (which is not the drive number, btw**) on a genuine 1541. I'd have no > idea > how it's done with one of the SD-based drive emulators. > Google is still a friend: https://www.google.com/search?q=sd2iec+change+device+numbers&ie=utf-8&oe=utf-8 There are no external switches on some of these drives. But, the BASIC commands used to switch device numbers on the 1541 also work on these units, and putting an extra char at the end of the command will make the changes permanent, as I recall. Jim >>> Jim, don't you sell a device that's useful for temporarily switching off >>> specific drives so the device numbers can be changed more easily? >>> >>> QuadPortIEC, but you can also just switch the ATN line on the cable. >> Disabling the ATN (Attention) line means the drive will not respond to any >> commands. >> >> Jim >> >> >> -- >> Jim Brain >> br...@jbrain.com >> www.jbrain.com >> >> >
Re: SD Card disk drive for C-64?
" I am saying don't make a permanent hardware change to a 1541 that does not have the switches unless you really want it to be permanent because there is a software method of assigning drives that is good enough most of the time. BUT if you must make it permanent and you don't have the external switches, consider adding some form of external switch so you don't ever have to open the case again to put it back to the default." Well then, we're having a major agreement. ;-) The device ID switch is the ultimate fix for Commodore drives, and I'm really not sure why CBM didn't incorporate one into the design - at least from the 1540 on upwards. Can't have cost much to add a discretely located access hole (or a knock-out) in the case, along with a 2-place DIP switch for controlling device ID. Grumble grumble.. On Sat, Jan 23, 2016 at 6:33 PM, Jim Brain wrote: > On 1/23/2016 6:28 PM, Eric Christopherson wrote: > >> On Sat, Jan 23, 2016, Jim Brain wrote: >> >>> On 1/23/2016 2:18 PM, drlegendre . wrote: >>> First off, my bad - I thought the OP was wanting to change the device ID (which is not the drive number, btw**) on a genuine 1541. I'd have no idea how it's done with one of the SD-based drive emulators. >>> Google is still a friend: >>> >>> >>> https://www.google.com/search?q=sd2iec+change+device+numbers&ie=utf-8&oe=utf-8 >>> >>> There are no external switches on some of these drives. >>> >>> But, the BASIC commands used to switch device numbers on the 1541 also >>> work >>> on these units, and putting an extra char at the end of the command will >>> make the changes permanent, as I recall. >>> >>> Jim >>> >> Jim, don't you sell a device that's useful for temporarily switching off >> specific drives so the device numbers can be changed more easily? >> >> QuadPortIEC, but you can also just switch the ATN line on the cable. > Disabling the ATN (Attention) line means the drive will not respond to any > commands. > > Jim > > > -- > Jim Brain > br...@jbrain.com > www.jbrain.com > >
Re: opening the drive door/lid of an RM03 ?
Strange. Here's one of mine. No lid issues! https://www.youtube.com/watch?v=xcc5fJOgp7A Mike On Sun, Jan 24, 2016 at 10:47 AM, Henk Gooijen wrote: > Hello readers, > I cleaned the first of my RM03 drives today. The drive is quite clean > even after several years of no attention. Just a few spiders webs and > tiny dead spiders, and little dust. I picked up this drive in Turin > Italy, together with Edward several years ago. I cannot remember doing > it, but the head lock pin was in the lock position. > After cleaning and a good inspection (I found a small metal bracket > piece next to the PSU output plugs, and have not found where it came > from!), I mounted a mains power plug to the drive cable. Massbus cable > is attached to the drive, the other end is not connected to anything. > After setting all circuit breakers ON (two inside the drive, two at the > rear side next to the running hours counter), I plugged the mains in > and switched mains on. I hear humming of the fans, so it seems OK. > > However, this is my problem: the door latch stays locked, I cannot open > the lid. I want to open the lid to clean the inside of the drive bay. > After some reading (EK-RM023-TD-001_RM02_03_Tech_May78.pdf), I found > this in chapter 4.4 (page 4-7): > > The initialize sequence starts with the receipt of a Massbus INIT > signal from either port A or B. This sequence is used to condition both > the adapter and drive circuits to a known reset state. The functional > block diagram for the initialize command is shown in Figure 4-5. > The Massbus INIT signal (whether coming from port A or B) clears the > AT A bit in the attention summary register in the IF module. In the CS > module, it is converted to the MBA clear signal which performs the > following: > 1. Clears the enable search latch > 2. Sets the on latch > 3. etc. > > So, do I understand this correctly that without an initial Massbus INIT > signal the lid remains locked? Or has this RM03 drive a "lock issue"? > If somebody has an RM03 drive, is it possible to open the lid without > Massbus cables hooked to the RH70 or RH11 controller? Is that Massbus > connection required + INIT command to unlock the lid? > > I have not yet cleaned the other two RM03 drives, and I do not want to > apply power without cleaning and inspection! So, I cannot check whether > all 3 drives keep the lid locked. > > I forgot to take the camera with me, but I will take pictures! > > Thanks, > - Henk -- http://www.corestore.org 'No greater love hath a man than he lay down his life for his brother. Not for millions, not for glory, not for fame. For one person, in the dark, where no one will ever know or see.'
Re: SD Card disk drive for C-64?
On 1/23/2016 6:28 PM, Eric Christopherson wrote: On Sat, Jan 23, 2016, Jim Brain wrote: On 1/23/2016 2:18 PM, drlegendre . wrote: First off, my bad - I thought the OP was wanting to change the device ID (which is not the drive number, btw**) on a genuine 1541. I'd have no idea how it's done with one of the SD-based drive emulators. Google is still a friend: https://www.google.com/search?q=sd2iec+change+device+numbers&ie=utf-8&oe=utf-8 There are no external switches on some of these drives. But, the BASIC commands used to switch device numbers on the 1541 also work on these units, and putting an extra char at the end of the command will make the changes permanent, as I recall. Jim Jim, don't you sell a device that's useful for temporarily switching off specific drives so the device numbers can be changed more easily? QuadPortIEC, but you can also just switch the ATN line on the cable. Disabling the ATN (Attention) line means the drive will not respond to any commands. Jim -- Jim Brain br...@jbrain.com www.jbrain.com
Re: SD Card disk drive for C-64?
On Sat, Jan 23, 2016, Jim Brain wrote: > On 1/23/2016 2:18 PM, drlegendre . wrote: > >First off, my bad - I thought the OP was wanting to change the device ID > >(which is not the drive number, btw**) on a genuine 1541. I'd have no idea > >how it's done with one of the SD-based drive emulators. > Google is still a friend: > > https://www.google.com/search?q=sd2iec+change+device+numbers&ie=utf-8&oe=utf-8 > > There are no external switches on some of these drives. > > But, the BASIC commands used to switch device numbers on the 1541 also work > on these units, and putting an extra char at the end of the command will > make the changes permanent, as I recall. > > Jim Jim, don't you sell a device that's useful for temporarily switching off specific drives so the device numbers can be changed more easily? -- Eric Christopherson
Re: RIFA EMI caps [WAS: Re: VT100 PSU smelling.]
On 01/23/2016 02:40 PM, Pontus wrote: All I could find were new similar Kemet capacitors. Do you know if newer Kemet suffer from the same problem and I will regret buying them? I usually replace the Rifa capacitors with equivalent polyester safety caps (X or Y rated). Kemets are most common and work just fine. It's not a bad idea, if you're in a 240AC mains country to bump the AC voltage rating up a bit. I've seen too many line filters with 250VAC rated caps labeled for either 120 or 240V use. That would make me nervous if I lived in a 240V country. --Chuck
RIFA EMI caps [WAS: Re: VT100 PSU smelling.]
On 01/23/2016 01:26 AM, Tothwolf wrote: They can. The translucent yellow Rifa (now owned by Kemet) class X/Y safety capacitors in particular have a 100% failure rate and are on my replace-on-sight list. They usually begin to show visible signs of cracking in their outer casing before they finally go out with a bang. It seems to be due to chemical decomposition of the paper insulator which swells over time and causes the case to crack. I usually replace them with a film capacitor from Epcos of the same value and safety class. I have heard similar from a few other places. And I'm replacing a five of these in a bigger SGI PSU as preventive maintenance. A few of them are showing cracks. All I could find were new similar Kemet capacitors. Do you know if newer Kemet suffer from the same problem and I will regret buying them? Thanks, Pontus.
Re: Introduction and RK05J Drive cabling
On Fri, Jan 22, 2016 at 4:00 PM, Joshua Stetson wrote: > > Over the past couple of years, I've managed to work back even further, > piecing together a PDP-8/e system from various parts collected over the > past 4 years and now I have a fully working 8/e including 32kw of core and > an RK05E card set. I've been running the system using Kyle Owen's > os8diskserver and David Gesswein's sendtape utilities which both work > absolutely wonderfully. It was amazing to be able to run Adventure on a > native system! > > I'd like to send a shout out to Kyle for the os8diskserver, that is some > pretty awesome work there. David for his software and archive of DEC > documentation which was indispensable for helping me debug a few boards and > get everything running and tested. I also want to thank Vincent Slyngstad > for his help and support on some questions. Always happy to hear of another happy user! Even better to hear of another working 8/E. Hope you get your RK05 going. I am still waiting for a good deal on an RK05; I'll probably have a custom SD card board made for the Omnibus before that happens, though... :) Kyle
Re: SD Card disk drive for C-64?
On Sat, Jan 23, 2016 at 4:12 PM, Jim Brain wrote: > On 1/23/2016 2:18 PM, drlegendre . wrote: > >> First off, my bad - I thought the OP was wanting to change the device ID >> (which is not the drive number, btw**) on a genuine 1541. I'd have no idea >> how it's done with one of the SD-based drive emulators. >> > Google is still a friend: > > > https://www.google.com/search?q=sd2iec+change+device+numbers&ie=utf-8&oe=utf-8 > > There are no external switches on some of these drives. > > But, the BASIC commands used to switch device numbers on the 1541 also > work on these units, and putting an extra char at the end of the command > will make the changes permanent, as I recall. > > Jim > Right. I am saying don't make a permanent hardware change to a 1541 that does not have the switches unless you really want it to be permanent because there is a software method of assigning drives that is good enough most of the time. BUT if you must make it permanent and you don't have the external switches, consider adding some form of external switch so you don't ever have to open the case again to put it back to the default. Less likely to burn traces, etc if you can avoid working on the same circuit more than once. b
opening the drive door/lid of an RM03 ?
Hello readers, I cleaned the first of my RM03 drives today. The drive is quite clean even after several years of no attention. Just a few spiders webs and tiny dead spiders, and little dust. I picked up this drive in Turin Italy, together with Edward several years ago. I cannot remember doing it, but the head lock pin was in the lock position. After cleaning and a good inspection (I found a small metal bracket piece next to the PSU output plugs, and have not found where it came from!), I mounted a mains power plug to the drive cable. Massbus cable is attached to the drive, the other end is not connected to anything. After setting all circuit breakers ON (two inside the drive, two at the rear side next to the running hours counter), I plugged the mains in and switched mains on. I hear humming of the fans, so it seems OK. However, this is my problem: the door latch stays locked, I cannot open the lid. I want to open the lid to clean the inside of the drive bay. After some reading (EK-RM023-TD-001_RM02_03_Tech_May78.pdf), I found this in chapter 4.4 (page 4-7): The initialize sequence starts with the receipt of a Massbus INIT signal from either port A or B. This sequence is used to condition both the adapter and drive circuits to a known reset state. The functional block diagram for the initialize command is shown in Figure 4-5. The Massbus INIT signal (whether coming from port A or B) clears the AT A bit in the attention summary register in the IF module. In the CS module, it is converted to the MBA clear signal which performs the following: 1. Clears the enable search latch 2. Sets the on latch 3. etc. So, do I understand this correctly that without an initial Massbus INIT signal the lid remains locked? Or has this RM03 drive a "lock issue"? If somebody has an RM03 drive, is it possible to open the lid without Massbus cables hooked to the RH70 or RH11 controller? Is that Massbus connection required + INIT command to unlock the lid? I have not yet cleaned the other two RM03 drives, and I do not want to apply power without cleaning and inspection! So, I cannot check whether all 3 drives keep the lid locked. I forgot to take the camera with me, but I will take pictures! Thanks, - Henk
Re: SD Card disk drive for C-64?
On 1/23/2016 2:18 PM, drlegendre . wrote: First off, my bad - I thought the OP was wanting to change the device ID (which is not the drive number, btw**) on a genuine 1541. I'd have no idea how it's done with one of the SD-based drive emulators. Google is still a friend: https://www.google.com/search?q=sd2iec+change+device+numbers&ie=utf-8&oe=utf-8 There are no external switches on some of these drives. But, the BASIC commands used to switch device numbers on the 1541 also work on these units, and putting an extra char at the end of the command will make the changes permanent, as I recall. Jim
Re: SD Card disk drive for C-64?
> > > "Given the potential flakiness of 1541 drives, why make permanent hardware > changes when a basic program allows you to assign the drive to whatever you > want for the temporary need of the day?" > > Though I'm not entirely sure it exists, any "potential flakiness" is > probably a very good reason to make the change in hardware. Device IDs > assigned via software (with a M-W command to the DOS) don't persist between > drive resets and may not persist between serial bus resets either, for that > matter. So if the drive does screw up and requires a power cycle, you're > back to device 8 again afterwards. This means shutting off one drive, > re-assigning the device ID to 9 or whatever, then powering on the second > drive. > > If you're using more than two drives, it really becomes a hassle. In any > event, just install a switch (or pair of them..) on each drive and all is > well. > > > How about a middle ground then, if you must control drive assignment with hardware, put in a jumper that can be changed externally without opening the case each time, or a switch. Further, I my friendly opinion that one should start with a software solution. Switch to hardware when it becomes a hassle and you're 100% sure you want to leave it permanently. I switch things around all of the time, to me it's just part of what you do with Commodore drives. Among other useful tools I have a drive assignment program on my SD drive root. Here is a link to a video I made to demonstrate commodore drive assignment using a Commodore B-128, 8050 drive, D9090 drive, and 1571 drive together https://www.youtube.com/watch?v=jBeFXDWbw8A b
Re: Character ROMs for HP 2631G printer / 264x terminals
On Sat, Jan 23, 2016 at 2:13 AM, wrote: > No, but I have an HP 1670G, does the same trick. I also managed to install it > as a printer on Windows 98 using a GPIB ISA card and National Instruments DOS > drivers. Even had the choice of 14 7/8 inch fan fold paper in the printer > dialog! I'm working on a nicer HP only demo. > Marc Cool, make a demo video of the 2631G doing a print screen from the 1670G sometime. That would be interesting to see.
Re: SD Card disk drive for C-64?
First off, my bad - I thought the OP was wanting to change the device ID (which is not the drive number, btw**) on a genuine 1541. I'd have no idea how it's done with one of the SD-based drive emulators. "Given the potential flakiness of 1541 drives, why make permanent hardware changes when a basic program allows you to assign the drive to whatever you want for the temporary need of the day?" Though I'm not entirely sure it exists, any "potential flakiness" is probably a very good reason to make the change in hardware. Device IDs assigned via software (with a M-W command to the DOS) don't persist between drive resets and may not persist between serial bus resets either, for that matter. So if the drive does screw up and requires a power cycle, you're back to device 8 again afterwards. This means shutting off one drive, re-assigning the device ID to 9 or whatever, then powering on the second drive. If you're using more than two drives, it really becomes a hassle. In any event, just install a switch (or pair of them..) on each drive and all is well. (** Devices on the CBM serial bus (or IEC bus) have device IDs, with the disk drives usually being 8,9,10 and 11. Each device can actually have two physical drives, 0 and 1. Now in the later era (1540 and beyond) there's only one physical drive per device, which is device 0, the default. But in case you ever wondered why the correct syntax for a DOS command has this "extra" 0:, now you know - as in OPEN 15,8,15,"I0:". It's explicitly specifying drive 0.. as opposed to drive 1.) On Sat, Jan 23, 2016 at 8:00 AM, william degnan wrote: > > > > > http://www.ebay.com/itm/Beige-SD2IEC-Commodore-1541-Disk-Drive-Emulation-SD-Card-Reader-Vic20-C128-C64-/330919501256?hash=item4d0c56ddc8:g:7sUAAOxy0NtTEQKk > > > > > > > > Also having rtouble hooking up my original floppy drive as " LOAD > "$" > > > > ,9,1 > > > > > > > How are the jumper on the reak floppy to be set? > > > Have you tried to simply run a basic program to temporarily reassign the > drive number? This is documented on the web. For example see page 39 > here (ignore the fact that this is for a VIC 1541, the method is > universal): > > > http://www.commodore.ca/manuals/pdfs/commodore_vic_1541_floppy_drive_users_manual.pdf > > Given the potential flakiness of 1541 drives, why make permanent hardware > changes when a basic program allows you to assign the drive to whatever you > want for the temporary need of the day? > > Try the following for your SD card drive, My case is different but the > insides are the same > http://vintagecomputer.net/browse_thread.cfm?id=490 > > At the bottom the thread there is a link to more info. > > Google is your friend, he misses you. > > > b >
RE: Introduction and RK05J Drive cabling
> The other thing to be aware of is the emergency head retract batteries are > toast and should > be replaced with a 3.6v NiCd pack, that way if the power fails you don't > trash a pack. I thought originally it was a 4.8V pack (4 cells). Over here a common cordless telephone used the same pack about 20 years ago, so spares for that (available quite easily) went in my RK05s... The RK06/RK07 has an 8 cell pack, it's exactly 2 RK05 packs in series. > They are really nice drives for saying they where DEC's first removable media > hard drive, a > bit heavy to move but not that bad. I can't get one onto the rack sliders on my own if it's fully assembled. I normally remove the PSU and positioner and then it is quite easy... -tony
RE: Introduction and RK05J Drive cabling
> > This one looks like it's in really good condition, but I have read about > those issues. I'm just going to monitor it closely when initially mounting > packs to verify the seals and integrity. As much as I hate to do so, I know > it's common to run these without the top cover on for calibration purposes. > Any tips for that? Maybe a piece of plexiglas over the heads to avoid any > potential dust or should I not worry too much? It is not a problem. The outer casing is not sealed anyway. Clean air (from the absolute filter) is blown in the bottom of the pack, then out over the head area If any dust gets near there it will be blown away from the heads. Be sensible about it, don't smoke when working on these drives. But other than that there is nothng to worry about. > > The other thing to be aware of is the emergency head retract batteries are > > toast and should be replaced with a 3.6v NiCd pack, that way if the power > > fails you don't trash a pack. > > > > This is also on my list of things to do. Is there anyway to test this > function without using a pack to verify it after replaced? With the mains off and no pack loaded, slip a folded lens tissue (or similar) between the heads (in case they do touch) and carefully pull the carriage towards the front of the drive. You should not be able to do it, as soon as it gets off the end stop and the microswitch releases, it should snap back home again very sharply. That's due to the NiCd being connected to the positioner coil, of course. -tony
VAXELN Datagram Service
I am doing a bit of VAXELN programming and I am trying to get the Datagram Service to only read packets of a certain EtherType, but unless I use promiscuous mode, nothing is read. Here is the relevant code: form.format = ELN$K_NI_PTT; form.mux.ptt = 0x0360; mode = 0; pad = 0; eln$ni_connect(&status, &portalId, config.clist.list[i].control_port, &dispatchPort, &form, NULL, &mode, NULL, NULL, NULL, NULL, NULL, &pad); Anyone know why this might not return any packets at all when I wait on the port? Regards Rob
RE: VT100 PSU smelling.
> > It's a well-known fault, but has anyone ever known one fail and actually > cause any damage (other than to itself)? AIUI, they're there to reduce Not really. Maybe a blown fuse. I have had the live-earth capacitor in a filter fail and trip the RCD in my consumer unit (meaning I was in the dark until I reset t). Does damage to my nerves count :-) If one of these capacitors in a mains filter circuit fails I tend to replace the lot (for all I don't like shotgun debugging). If I was repairing something for somebody else then I'd probably change them [1]). I might change them if I was rebulding the PSU section of a machine I own. Otherwise I just leave them until the fail. [1] Otherwise when they fail a few weeks/months/years later I might find I have to replace them for free. Incidentally, some machines have those sealed metal cans containing filter capacitors, inductors and sometimes discharge resistors [2]. Has anyone ever had the capacitors in one of those fail? [2] I wish the manufacturers would print a schematic on the can, or at least in an available data sheet. If I measure a 1M leak to earth from the live pin (say), I want to know if it's a deliberate discharging resistor or a leaking capacitor. -tony
Re: HP 9000/382 Questions
As already mentioned, you should start off looking at http://www.hpmuseum.net for documentation and software for the HP 9000/382 I obtained an .ISO image of the HP-UX 9.0 installation CD-ROM there along with HP BASIC 6.2 images, both stand alone BASIC and BASIC/UX. There are currently no direct download links for those images. Jon Johnston there has been great about responding to requests for images if you send him an email. The SCSI hard drive in my 9000/382 was dead when I received it. It was fairly straight forward to install HP-UX 9.0 from scratch on a replacement hard drive from a SCSI CD-ROM. I forget how much memory mine had when I received. I found some additional memory to install and that helped with performance running HP-UX 9.0. I don't think I ever got around to trying to use HP BASIC to control any GPIB interface test equipment yet.
Re: ESR meter recommendations.
On 1/23/2016 9:22 AM, Mattis Lind wrote: Yes. agree with you.I really should get oneWhat meter do you have and recommend? I use the BLUE ESR Meter of AnaTek Corp (designed by Bob Parker). I've been using it for several years and really like it. - J.
Re: VT100 PSU smelling.
On 1/23/2016 5:40 AM, Mattis Lind wrote: This is a 0.0033 uF 1600VDC SPARAGUE capacitor. It looks nice and orange and there are no signs of cracks whatsoever. What is the likelihood of this being bad? Not highly likely, but possible. Just put another one in temporarily and see if it solves your problem. Or try to measure what kind of current is causing the resistor to heat up -- is there AC across it, or is that cap leaking? - J.
Re: VT100 PSU smelling.
On 01/22/2016 06:26 PM, Tothwolf wrote: The translucent yellow Rifa (now owned by Kemet) class X/Y safety capacitors in particular have a 100% failure rate and are on my replace-on-sight list. They usually begin to show visible signs of cracking in their outer casing before they finally go out with a bang. It's a well-known fault, but has anyone ever known one fail and actually cause any damage (other than to itself)? AIUI, they're there to reduce noise from the device leaking back out onto the AC supply - a system should run quite happily without them. I've had maybe four or five fail on me over the years, out of several hundred systems. They're a definite weak spot, but given that I've never heard of one damaging anything it's the sort of thing I'd consider doing only if I was carrying out some other repair work on the PSU. > I usually replace them with a film capacitor from Epcos of the same > value and safety class. Is the voltage rating on the US ones different (new vs. old)? I can't remember now. I know all the old UK ones seemed to be 250V, while modern parts were rated at 275V. cheers Jules
Re: ESR meter recommendations.
> From: Mattis Lind > What meter do you have and recommend? My capacitance meter is a Uyigao UA6013L, and I'm quite happy with it; it seems pretty reasonable build-quality. A number of people on eBay are selling them, IIRC. My ESR meter is, alas, literall nameless - I looked on both the meter, and the (single-sheet) documentation, and there's no name anywhere. (Yes, yes, I know, I got what I paid for - which was not much! :-) Noel
RE: VT100 PSU smelling.
> > Well. It depends if you read the schematics before you do so. In this case > I powered the startup voltage from a 12 V bench supply. Normally the > startup voltage comes from a small mains transformer and a 7812. Then I > supplied the primary side voltage for the main switch transistor using a > variac. Works perfectly well if you know what you are doing. Have done this > practice with many SMPS supplies. Remember an SMPSU approximates to a constant _power_ load. It will draw more current as the input voltage decreases. As a result, if the supply is fairly well loaded on the output side, the primary side current can be high enough to damage the chopper transistor if you run it at low input voltage. -tony
Re: HP 9000/382 Questions
On 2016-01-22 4:52 PM, Pete Lancashire wrote: Hello from a newbie to the list I've just acquired 2 HP 382's with expanders. Have not had the time to look inside them yet. End goal is to set one up as an instrument controller i.e. using the built in GPIB and potentially a 2nd GPIB card. One thing I do not have is a display, keyboard and mouse. A few question Is there a PS/2 or USB (yea long shot) adapter for the HPIL interface ? Does someone have a keyboard/mouse they a not beholding to, or know where there maybe one ? Once I get the opened up and take an inventory, anything I should look out for be trying to power one of them up ? Can one boot to a terminal on the RS-232 port. Until I find a kbd/mouse ? What would be optimum version of HP-UX to run on them ? -pete Wow great find, those are nice 9000s, I have been looking for one with ethernet and SCSI. You will find lots of documentation for them at hpmuseum.net. It would seem that the display interface is standard VGA, however as you discovered the keyboard is HP-HIL. HP did make a PS/2 adapter module, however it would seem they are extremely rare, I would like to get one too. I have also though of building my own, the usual interface is a custom chip made by HP that handles most of the protocol, that is coupled with a National Semiconductor COP series microcontroller using the microwire interface, I have some of these obtained from other HIL devices, the one that is the most promising is from an ID module it has all of the HIL hardware in it and a ROM-less COP420 so all of its code is in an external EPROM making it easy to alter. There is documentation available for the HP-HIL protocol. There are HP-HIL keyboards and mice available on eBay but they are not cheap. The 382 apparently has space for internal disks so you may be in luck and find it still has an OS installed, the 382 owner guide I found says the minimum level of HP-UX is 8.0, I would guess that at some point HP stopped supporting the 68K machines but I am not sure when that happened. I looked through the users guide and there is no mention of using a serial console, however is there is an OS installed it is possible that a serial port could be set up as a workstation. Paul.
ESR meter recommendations.
2016-01-23 13:54 GMT+01:00 Noel Chiappa : > > From: Mattis Lind > > > I don't have an capacitance / ESR meter so I cannot check it. > > If you do a lot of work with analog components (and it sounds like you do), > it's probably worth getting capacitance and ESR meters, they can be > obtained > (new) on eBay for not that much. I have one of each that I got that way; > their quality is pretty good, considering how little I paid for them (I > didn't think I'd be using them enough to make it worth paying out a lot for > really good ones). I haven't used the ESR meter much, but the capacitance > meter works quite well, and has been very helpful. Of course, it can't be > used in-circuit, but... > > Yes. agree with you.I really should get one. I have been thinking I need to get one every time I get my head into anther PSU and then everything is sorted out and the PSU seems to work fine and I forget about it. I have been looking at the DerEE DE-5000 which looks nice and has got good reviews as far as I can tell. What meter do you have and recommend? > Alas, I can't (easily) help with the VT100 question! :-) > That's a pity! > > Noel > /Mattis
Re: SD Card disk drive for C-64?
> > http://www.ebay.com/itm/Beige-SD2IEC-Commodore-1541-Disk-Drive-Emulation-SD-Card-Reader-Vic20-C128-C64-/330919501256?hash=item4d0c56ddc8:g:7sUAAOxy0NtTEQKk > > > > > > Also having rtouble hooking up my original floppy drive as " LOAD "$" > > > ,9,1 > > > > How are the jumper on the reak floppy to be set? > Have you tried to simply run a basic program to temporarily reassign the drive number? This is documented on the web. For example see page 39 here (ignore the fact that this is for a VIC 1541, the method is universal): http://www.commodore.ca/manuals/pdfs/commodore_vic_1541_floppy_drive_users_manual.pdf Given the potential flakiness of 1541 drives, why make permanent hardware changes when a basic program allows you to assign the drive to whatever you want for the temporary need of the day? Try the following for your SD card drive, My case is different but the insides are the same http://vintagecomputer.net/browse_thread.cfm?id=490 At the bottom the thread there is a link to more info. Google is your friend, he misses you. b
Re: Introduction and RK05J Drive cabling
> From: Guy Sotomayor > To that end, I've made new "paddle" board that take 2 60pin ribbon > cables. Guy, this is fantastic news! I have previously speculated about doing this, but it's still on the 'someday' list. > I'll let folks know how they turn out (ie do they actually work!). They should. DEC made the same basic part, but using 3x40-pin cables: M9042 (half-length, knuckle-buster) and M9014 (full-length). Apparently the characteristic impedance of N-pin flat cable is close enough to the BC11 cable that it works. Speaking of M9014's, though, the board list describes them as "UNIBUS to 3 H854s", and also lists an M9015, described as "3 H854s to UNIBUS". Does anyone know what the difference is between the two? Unlike the QBUS, the UNIBUS shouldn't need two different kinds of board, since the 'grant in' pin on one end of a UNIBUS cable is the same as the 'grant out' pin on the other end (unlike the QBUS, where the pinout is designed to support plugging in boards, so there are separate 'grant in' and 'grant out' pins). I can't for the life of me think of anything about the UNIBUS that a straight through-connect wouldn't handle - i.e. a pair of M9014's, on each end of the cable set. Certainly, BC11 cables ends aren't marked 'in' and 'out'! ;-) So does anyone know why the M9015 exists - what it different about it, etc, etc? Or was someone at DEC just not thinking hard enough when they spec'd it? > The downside is that they were somewhat expensive Heh, they'll still be cheaper than actual BC11's! :-) Noel
Re: Introduction and RK05J Drive cabling
> From: Joshua Stetson > Ideally I would like to find the following: > ... > The interface cable between the two drives: BC11A > The terminator card M930 The former is going to be a pain. The latter are findable on eBay. If you can't find one, drop me a line - I may have one I can spare. > I know it's common to run these without the top cover on for > calibration purposes. Any tips for that? Maybe a piece of plexiglas > over the heads to avoid any potential dust or should I not worry too much? Don't worry about it; BITD we used to run for short periods with the cover off, to calibrate heads, etc. The air-flow through the pack and out the head entrance hole will keep the heads clear. I wouldn't run them without the cover all the time, but for short periods, it will be fine. > From: Tony Duell > The M930 and BC11 should be easy to find, they are actually the same as > the bits used on PDP11 Unibus connections. The second part is correct, but not the first: BC11 cables are now pretty much unobtainium. Noel
Re: VT100 PSU smelling.
> From: Mattis Lind > I don't have an capacitance / ESR meter so I cannot check it. If you do a lot of work with analog components (and it sounds like you do), it's probably worth getting capacitance and ESR meters, they can be obtained (new) on eBay for not that much. I have one of each that I got that way; their quality is pretty good, considering how little I paid for them (I didn't think I'd be using them enough to make it worth paying out a lot for really good ones). I haven't used the ESR meter much, but the capacitance meter works quite well, and has been very helpful. Of course, it can't be used in-circuit, but... Alas, I can't (easily) help with the VT100 question! :-) Noel
Re: VT100 PSU smelling.
>>> >> I don't have a ESR meter or similar. It is not shorted at least and the >> resistance is in the several mega ohm range when measuring in circuit. Are >> they likely to go bad in a non catastrophic way? >> > > They can. The translucent yellow Rifa (now owned by Kemet) class X/Y > safety capacitors in particular have a 100% failure rate and are on my > replace-on-sight list. They usually begin to show visible signs of cracking > in their outer casing before they finally go out with a bang. It seems to > be due to chemical decomposition of the paper insulator which swells over > time and causes the case to crack. I usually replace them with a film > capacitor from Epcos of the same value and safety class. > This is a 0.0033 uF 1600VDC SPARAGUE capacitor. It looks nice and orange and there are no signs of cracks whatsoever. What is the likelihood of this being bad? /Mattis
Re: VT100 PSU smelling.
> > >> Well. It depends if you read the schematics before you do so. >> > > Assuming they're available for the particular PSU one is attempting to > test. > > Yes of course. If I have a PSU where I have doubts about the function and there is no schematic I spend a few hours trace out the relevant portions. Normally this is not a big chore. Then there are of course complex PSU and simple ones. I would not like the idea of tracing out the VAX-11/750 PSU, but a VT100 PSU is very small circuit on the primary side. > > I powered the startup voltage from a 12 V bench supply. Normally the >> startup voltage comes from a small mains transformer and a 7812. Then I >> supplied the primary side voltage for the main switch transistor using a >> variac. >> > > I wasn't aware of this interesting method; I'd also misread your original > sentence and thought you were just using a variac alone to bring up the > entire SMPS. OK. No I am not using onIy a variac. That wouldn't work very well. I usually try to identify the control circuit and power it independently of the switch circuit. That is usually no problem. Some PSU has a simple voltage divider from mains input other like the VT100 has a normal small iron core transformer to supply the control circuit supply. > > > > Works perfectly well if you know what you are doing. Have done this >> practice with many SMPS supplies. >> > Just curious -- what is *your* reason for bringing up an SMPS with the > help of a variac? > Many of the PSUs I work with have been not been powered up for decades. I think it is a good practice to take it slowly in the beginning. Observing it so that everything behaves well in the circuit using a very light load. Verify that the switch control circuit and regulation circuit behaves well and that the switching transistor waveforms looks good. Nothing is getting abnormally hot or so. Also be a little bit kind to all the electrolytics in the circuit etc. That is why I do this and I think that this method have served me well. Then of course I also use a protection transformer and very often some kind of input current limitation, not just a variac and a bench supply. > > Thank you- > -J. > > /Mattis
Re: VT100 PSU smelling.
> > Speaking generally, I don't know that that will necessarily save one (in > using a variac on a SMPS). > I for one think it is a good practice to start carefully. I like the idea of bringing up the voltage over capacitors and other electronics in a controlled manner. Electronics that had been sleeping for decades. I use a protection transformer, variac and also often means to limit the current. Then I could easily measure how the switching transistor behaves. The base/gate drive etc. > A SMPS functions as a constant-power converter in response to varying > supply voltage. For a given load, as the supply V goes down the supply > current goes up, to keep the load delivery constant. (This is in contrast > to linear-regulator supplies which maintain headroom V into the regulator > and simply limit the output V - the only thing that changes as the supply V > varies is the headroom V and how much energy is wasted as heat in the > difference.) > > AIUI, the concern for SMPSs is that if the supply V is too low, the supply > current and consequent factors may go too high for parts such as the driver > transistors, etc. > Whether it's a catastrophe depends on a variety of factors: whether the > design detects & incorporates shut-down under these conditions, how large > the load is (how much power the PS is trying to convert) (if the PS is > lightly loaded relative to it's max capability there may be no problem), > whether the pulse-width/switching characteristics are wide enough to become > a problem under low supply V, and so on. > All this depend on what load your are using. When running on the bench with variac I have a very modest load. In this case 100 mA at full 5V. Just 1 % of rated output. In that case there is very unlikely to overload the switch transistor. > > Supplying an external start-up V would strike me as a crap-shoot, > dependent on the design of the supply: > - On the one hand, if the PS was designed so that an > early-energised control circuit would shut-down > or limit the main switching under low supply V, then good. > That was the case for the VAX-11/750 supply which didn't enable switching under low main input conditions. Something I deliberately disabled to be able to test. In the case of the VAX-11/750 PSU I was able observe and detect a number of failures in the supply at low and non-harmful voltages. Regardless of protection transformer or not I don't like the idea of working with a PSU with 300VDC everywhere when probing with the scope probe. > - On the other hand, if the PS was designed such that the control > circuit wouldn't be energised > by the startup supply until the supply V was in the safe region > for the main switching, then bad - > the external startup supply may fool the control into thinking > the supply V is in the safe region. But "safe" depend on the load applied to the supply. On the other hand my question to the list was not if the use of variac is a good practice or not. I will continue to use this method since it has served me well and I am not forcing any one else to use it if they feel it is wrong. The question I have is why R27 in the snubber network is getting what I think excessively hot. The schematic for the primary side can be found here: http://i.imgur.com/VlInF90l.png One input that I had that if C19 is marginally bad then that might happen. Like if the dielectric as deteriorated over time and cannot whit-stand the voltage in the circuit. The capacitor is not cracked like the RIFA ones. It looks perfectly fine. It is a SPRAGUE 0.033uF 1600VDC. I don't have an capacitance / ESR meter so I cannot check it. Maybe I should just go ahead replacing it. But I don't like idea of replacing things without really knowing they are bad. Another question is whether the R27 is normally getting hot or not. What is VT100 owners experience here? /Mattis
Re: Character ROMs for HP 2631G printer / 264x terminals
No, but I have an HP 1670G, does the same trick. I also managed to install it as a printer on Windows 98 using a GPIB ISA card and National Instruments DOS drivers. Even had the choice of 14 7/8 inch fan fold paper in the printer dialog! I'm working on a nicer HP only demo. Marc > On Jan 19, 2016, at 8:51 PM, Glen Slick wrote: > >> On Tue, Jan 19, 2016 at 8:15 PM, Curious Marc wrote: >> Here is the restoration video. Works beautifully now: >> https://youtu.be/54bu0bM0Qjo >> Marc > > Do you have an HP 16500 series logic analyzer? They are supposed to be > able to print to an HP 2631G if you select the printer type as > QuietJet. Might make for an interesting quick demo.
Re: Introduction and RK05J Drive cabling
On 23/01/2016 00:23, Joshua Stetson wrote: The other thing to be aware of is the emergency head retract batteries are toast and should be replaced with a 3.6v NiCd pack, that way if the power fails you don't trash a pack. This is also on my list of things to do. Is there anyway to test this function without using a pack to verify it after replaced? With the power off and the drive opened up, try to pull the heads (gently) out from the retracted position. If the battery is good, you'll only be able to pull them out a few millimetres before they pull back in (with some force). I've found a common inexpensive 3-cell battery pack for a DECT phone is an exact match. If you replace the battery, be aware that the polarity suggested by the black/red wires on the RK05 - at least on the RK05s I've seen - is the opposite to what you'd expect, so check it. If you get the battery the wrong way round it will make the heads, on their thin stainless steel arms, shoot OUT instead of in, and your hand will most likely be in the way. You can imagine how I found this out, but the blood cleaned off the stainless steel without any problem. -- Pete
Software Products International LogiQuest III manual?
The LogiCalc manual is here: http://bitsavers.org/pdf/softwareProductsInternational/ anyone have the LogiQuest III manual to go with it? Here is an advertisement for the SPI application suite that includes Logiquest III: http://i.imgur.com/k0D3wRX.png LogiQuest III was a relational database from circa 1982 and appears to have been written in UCSD Pascal although it was later ported to the CP/M. thanks.
Re: Introduction and RK05J Drive cabling
> On Jan 22, 2016, at 2:29 PM, tony duell wrote: > >> > > The M930 and BC11 should be easy to find, they are actually the same as the > bits > used on PDP11 Unibus connections. > I have had no end of problems with the *many* BC11A cables that I have (ie they’re bad cables). It’s the flex ribbon cable itself that’s been the issue. To that end, I’ve made new “paddle” board that take 2 60pin ribbon cables. I expect to have the first round of boards back from the fab house in a couple of weeks. I’ll let folks know how they turn out (ie do they actually work!). They differ from the DEC ones in a few of ways: They’re full hight. No more “knuckle” busters. The cables are “standard” 60-pin ribbon (you need 2 ribbon cables) The cables are not “fixed” to the paddle board but use 3M connectors for attachment There are two versions of the paddle boards normal “out the top” 90-degree right angle so you don’t have to “fold” the cables for certain uses (like RK05 drives) I did these primarily because I need more cables and my BC11A’s are very flakey. Also I have uses where I need the cable to terminate to something that is agreeable to attach to other than another Unibus backplane. The downside is that they were somewhat expensive (I ordered 10 of each just because that made sense price wise for a prototype run). TTFN - Guy
Re: Introduction and RK05J Drive cabling
Also be careful of the air plenum, may of them are very fragile now and if it gets cracked you are in a hard spot. And also if the foam is compressing too much it will not make a good deal with the bottom of the pack. The other thing to be aware of is the emergency head retract batteries are toast and should be replaced with a 3.6v NiCd pack, that way if the power fails you don't trash a pack. They are really nice drives for saying they where DEC's first removable media hard drive, a bit heavy to move but not that bad. Matt Sent from my iPhone > On Jan 22, 2016, at 6:25 PM, Joshua Stetson wrote: > > I think I lucked out on the foam, as that was one of the first things I > checked. I had to go through and replace all the form in my 8/e chassis and > that was a pretty disgusting process. These drives were used in a > production environment up until a recently and seem really well maintained, > and from the looks of it, a very clean environment. They were even shipped > to me with the heads locked properly. I'm still going to be super cognizant > of the foam when I pull the filters to check them though. Thanks! > > On Fri, Jan 22, 2016 at 3:09 PM, Pete Lancashire > wrote: > >> Be very careful of the filter assembly, make sure the foam seals are not >> deteriorated to where they can add to what ends up on the platter. >> >> >> >> On Fri, Jan 22, 2016 at 2:00 PM, Joshua Stetson >> wrote: >> >>> Hi there, long time viewer, first time poster. First an introduction: >>> >>> My name is Joshua Stetson and I'm a software engineer by trade. My >> earliest >>> memories have always involved computers starting with a DOS based Zenith >>> 8088 where I played some of my first games. >>> >>> My first foray into "classic" computing was on a Commodore 64 which my >>> Uncle gave me while I was still in Jr. High. I'd already been introduced >> to >>> programming at an early age, so this machine was an absolute treat to me >> at >>> the time as it was my first step into assembly language. As time >>> progressed, my interests turned older and I began a collection of S-100 >>> gear including an IMSAI 8080 and a SOL-20. >>> >>> Over the past couple of years, I've managed to work back even further, >>> piecing together a PDP-8/e system from various parts collected over the >>> past 4 years and now I have a fully working 8/e including 32kw of core >> and >>> an RK05E card set. I've been running the system using Kyle Owen's >>> os8diskserver and David Gesswein's sendtape utilities which both work >>> absolutely wonderfully. It was amazing to be able to run Adventure on a >>> native system! >>> >>> I'd like to send a shout out to Kyle for the os8diskserver, that is some >>> pretty awesome work there. David for his software and archive of DEC >>> documentation which was indispensable for helping me debug a few boards >> and >>> get everything running and tested. I also want to thank Vincent Slyngstad >>> for his help and support on some questions. >>> >>> Now to my ask: >>> >>> Recently I've found a pair of RK05J drives and a few disk packs. One of >> my >>> drives seems to be in fully working order, the other the blower is not >>> working, so I'm working on fixing that right now. >>> >>> I'm currently missing cabling for connect these drives to the RK05E board >>> set. If anyone happens to have an extra cable set they'd be willing to >> part >>> with so I can bring these beasts back to life, I'd appreciate it! >>> >>> Ideally I would like to find the following: >>> 7009026 Cable which is two ribbon cables with a M933B or C flip chip on >> the >>> other end >>> The interface cable between the two drives: BC11A >>> The terminator card M930 >>> >>> At minimum, I'm pretty sure I'd only need the first cable to run one of >> the >>> drives, but I'd appreciate any help from those who have more experience. >>> >>> Also, I don't have a rack for this equipment yet, so I'm running it all >>> tabletop, but I'm in the market for a rack + rails (I only have the rails >>> for the equipment, but not the ones that mount to the rack itself. Any >>> leads on more 16-sector packs would also be appreciated! Also, still >> hoping >>> to get the extended arithmetic boards, RTC, and possibly a TSC8 >> Timesharing >>> option as I have 4 SLUs and would love to try out some timesharing. >>> >>> On a side note, I'm looking to perhaps sell or trade my SOL-20 sometime >>> soon. It's 100% working as I restored it about 3 years ago. It works >> great, >>> but I'm looking to part with all of my S-100 equipment to focus more on >>> DEC. >>> >>> Thanks! >>
Re: Introduction and RK05J Drive cabling
> > Also be careful of the air plenum, may of them are very fragile now and if > it gets cracked you are in a hard spot. And also if the foam is compressing > too much it will not make a good deal with the bottom of the pack. > This one looks like it's in really good condition, but I have read about those issues. I'm just going to monitor it closely when initially mounting packs to verify the seals and integrity. As much as I hate to do so, I know it's common to run these without the top cover on for calibration purposes. Any tips for that? Maybe a piece of plexiglas over the heads to avoid any potential dust or should I not worry too much? > The other thing to be aware of is the emergency head retract batteries are > toast and should be replaced with a 3.6v NiCd pack, that way if the power > fails you don't trash a pack. > This is also on my list of things to do. Is there anyway to test this function without using a pack to verify it after replaced?
Re: Introduction and RK05J Drive cabling
Thank you, I won't ask on how you found this out, but I'll make sure to have the terminator before running even a single drive! :) On Fri, Jan 22, 2016 at 2:29 PM, tony duell wrote: > > > Ideally I would like to find the following: > > 7009026 Cable which is two ribbon cables with a M933B or C flip chip on > the > > other end > > The interface cable between the two drives: BC11A > > The terminator card M930 > > > > At minimum, I'm pretty sure I'd only need the first cable to run one of > the > > drives, but I'd appreciate any help from those who have more experience. > > You must put the terminator in, even on a single drive system. I've had > problems > where you get glitches on unterminated lines and the drive can end up > writing > when it shouldn't. Don't ask... > > The M930 and BC11 should be easy to find, they are actually the same as > the bits > used on PDP11 Unibus connections. > > -tony >
Re: SD Card disk drive for C-64?
On Fri, Jan 22, 2016 at 5:56 PM, drlegendre . wrote: > Have you cut the appropriate jumper to designate that drive as device #9? > > On Fri, Jan 22, 2016 at 9:58 AM, Mike wrote: > > > Have any of you bought this item here is a link to the one I bought I > > have a few questions on disk swapping. > > > > > > > http://www.ebay.com/itm/Beige-SD2IEC-Commodore-1541-Disk-Drive-Emulation-SD-Card-Reader-Vic20-C128-C64-/330919501256?hash=item4d0c56ddc8:g:7sUAAOxy0NtTEQKk > > > > Also having rtouble hooking up my original floppy drive as " LOAD "$" > > ,9,1 > How are the jumper on the reak floppy to be set? *Mike's *
Re: Introduction and RK05J Drive cabling
I think I lucked out on the foam, as that was one of the first things I checked. I had to go through and replace all the form in my 8/e chassis and that was a pretty disgusting process. These drives were used in a production environment up until a recently and seem really well maintained, and from the looks of it, a very clean environment. They were even shipped to me with the heads locked properly. I'm still going to be super cognizant of the foam when I pull the filters to check them though. Thanks! On Fri, Jan 22, 2016 at 3:09 PM, Pete Lancashire wrote: > Be very careful of the filter assembly, make sure the foam seals are not > deteriorated to where they can add to what ends up on the platter. > > > > On Fri, Jan 22, 2016 at 2:00 PM, Joshua Stetson > wrote: > > > Hi there, long time viewer, first time poster. First an introduction: > > > > My name is Joshua Stetson and I'm a software engineer by trade. My > earliest > > memories have always involved computers starting with a DOS based Zenith > > 8088 where I played some of my first games. > > > > My first foray into "classic" computing was on a Commodore 64 which my > > Uncle gave me while I was still in Jr. High. I'd already been introduced > to > > programming at an early age, so this machine was an absolute treat to me > at > > the time as it was my first step into assembly language. As time > > progressed, my interests turned older and I began a collection of S-100 > > gear including an IMSAI 8080 and a SOL-20. > > > > Over the past couple of years, I've managed to work back even further, > > piecing together a PDP-8/e system from various parts collected over the > > past 4 years and now I have a fully working 8/e including 32kw of core > and > > an RK05E card set. I've been running the system using Kyle Owen's > > os8diskserver and David Gesswein's sendtape utilities which both work > > absolutely wonderfully. It was amazing to be able to run Adventure on a > > native system! > > > > I'd like to send a shout out to Kyle for the os8diskserver, that is some > > pretty awesome work there. David for his software and archive of DEC > > documentation which was indispensable for helping me debug a few boards > and > > get everything running and tested. I also want to thank Vincent Slyngstad > > for his help and support on some questions. > > > > Now to my ask: > > > > Recently I've found a pair of RK05J drives and a few disk packs. One of > my > > drives seems to be in fully working order, the other the blower is not > > working, so I'm working on fixing that right now. > > > > I'm currently missing cabling for connect these drives to the RK05E board > > set. If anyone happens to have an extra cable set they'd be willing to > part > > with so I can bring these beasts back to life, I'd appreciate it! > > > > Ideally I would like to find the following: > > 7009026 Cable which is two ribbon cables with a M933B or C flip chip on > the > > other end > > The interface cable between the two drives: BC11A > > The terminator card M930 > > > > At minimum, I'm pretty sure I'd only need the first cable to run one of > the > > drives, but I'd appreciate any help from those who have more experience. > > > > Also, I don't have a rack for this equipment yet, so I'm running it all > > tabletop, but I'm in the market for a rack + rails (I only have the rails > > for the equipment, but not the ones that mount to the rack itself. Any > > leads on more 16-sector packs would also be appreciated! Also, still > hoping > > to get the extended arithmetic boards, RTC, and possibly a TSC8 > Timesharing > > option as I have 4 SLUs and would love to try out some timesharing. > > > > On a side note, I'm looking to perhaps sell or trade my SOL-20 sometime > > soon. It's 100% working as I restored it about 3 years ago. It works > great, > > but I'm looking to part with all of my S-100 equipment to focus more on > > DEC. > > > > Thanks! > > > > >
Re: Introduction and RK05J Drive cabling
Be very careful of the filter assembly, make sure the foam seals are not deteriorated to where they can add to what ends up on the platter. On Fri, Jan 22, 2016 at 2:00 PM, Joshua Stetson wrote: > Hi there, long time viewer, first time poster. First an introduction: > > My name is Joshua Stetson and I'm a software engineer by trade. My earliest > memories have always involved computers starting with a DOS based Zenith > 8088 where I played some of my first games. > > My first foray into "classic" computing was on a Commodore 64 which my > Uncle gave me while I was still in Jr. High. I'd already been introduced to > programming at an early age, so this machine was an absolute treat to me at > the time as it was my first step into assembly language. As time > progressed, my interests turned older and I began a collection of S-100 > gear including an IMSAI 8080 and a SOL-20. > > Over the past couple of years, I've managed to work back even further, > piecing together a PDP-8/e system from various parts collected over the > past 4 years and now I have a fully working 8/e including 32kw of core and > an RK05E card set. I've been running the system using Kyle Owen's > os8diskserver and David Gesswein's sendtape utilities which both work > absolutely wonderfully. It was amazing to be able to run Adventure on a > native system! > > I'd like to send a shout out to Kyle for the os8diskserver, that is some > pretty awesome work there. David for his software and archive of DEC > documentation which was indispensable for helping me debug a few boards and > get everything running and tested. I also want to thank Vincent Slyngstad > for his help and support on some questions. > > Now to my ask: > > Recently I've found a pair of RK05J drives and a few disk packs. One of my > drives seems to be in fully working order, the other the blower is not > working, so I'm working on fixing that right now. > > I'm currently missing cabling for connect these drives to the RK05E board > set. If anyone happens to have an extra cable set they'd be willing to part > with so I can bring these beasts back to life, I'd appreciate it! > > Ideally I would like to find the following: > 7009026 Cable which is two ribbon cables with a M933B or C flip chip on the > other end > The interface cable between the two drives: BC11A > The terminator card M930 > > At minimum, I'm pretty sure I'd only need the first cable to run one of the > drives, but I'd appreciate any help from those who have more experience. > > Also, I don't have a rack for this equipment yet, so I'm running it all > tabletop, but I'm in the market for a rack + rails (I only have the rails > for the equipment, but not the ones that mount to the rack itself. Any > leads on more 16-sector packs would also be appreciated! Also, still hoping > to get the extended arithmetic boards, RTC, and possibly a TSC8 Timesharing > option as I have 4 SLUs and would love to try out some timesharing. > > On a side note, I'm looking to perhaps sell or trade my SOL-20 sometime > soon. It's 100% working as I restored it about 3 years ago. It works great, > but I'm looking to part with all of my S-100 equipment to focus more on > DEC. > > Thanks! > >
HP 9000/382 Questions
Hello from a newbie to the list I've just acquired 2 HP 382's with expanders. Have not had the time to look inside them yet. End goal is to set one up as an instrument controller i.e. using the built in GPIB and potentially a 2nd GPIB card. One thing I do not have is a display, keyboard and mouse. A few question Is there a PS/2 or USB (yea long shot) adapter for the HPIL interface ? Does someone have a keyboard/mouse they a not beholding to, or know where there maybe one ? Once I get the opened up and take an inventory, anything I should look out for be trying to power one of them up ? Can one boot to a terminal on the RS-232 port. Until I find a kbd/mouse ? What would be optimum version of HP-UX to run on them ? -pete
RE: Introduction and RK05J Drive cabling
> Ideally I would like to find the following: > 7009026 Cable which is two ribbon cables with a M933B or C flip chip on the > other end > The interface cable between the two drives: BC11A > The terminator card M930 > > At minimum, I'm pretty sure I'd only need the first cable to run one of the > drives, but I'd appreciate any help from those who have more experience. You must put the terminator in, even on a single drive system. I've had problems where you get glitches on unterminated lines and the drive can end up writing when it shouldn't. Don't ask... The M930 and BC11 should be easy to find, they are actually the same as the bits used on PDP11 Unibus connections. -tony
Introduction and RK05J Drive cabling
Hi there, long time viewer, first time poster. First an introduction: My name is Joshua Stetson and I'm a software engineer by trade. My earliest memories have always involved computers starting with a DOS based Zenith 8088 where I played some of my first games. My first foray into "classic" computing was on a Commodore 64 which my Uncle gave me while I was still in Jr. High. I'd already been introduced to programming at an early age, so this machine was an absolute treat to me at the time as it was my first step into assembly language. As time progressed, my interests turned older and I began a collection of S-100 gear including an IMSAI 8080 and a SOL-20. Over the past couple of years, I've managed to work back even further, piecing together a PDP-8/e system from various parts collected over the past 4 years and now I have a fully working 8/e including 32kw of core and an RK05E card set. I've been running the system using Kyle Owen's os8diskserver and David Gesswein's sendtape utilities which both work absolutely wonderfully. It was amazing to be able to run Adventure on a native system! I'd like to send a shout out to Kyle for the os8diskserver, that is some pretty awesome work there. David for his software and archive of DEC documentation which was indispensable for helping me debug a few boards and get everything running and tested. I also want to thank Vincent Slyngstad for his help and support on some questions. Now to my ask: Recently I've found a pair of RK05J drives and a few disk packs. One of my drives seems to be in fully working order, the other the blower is not working, so I'm working on fixing that right now. I'm currently missing cabling for connect these drives to the RK05E board set. If anyone happens to have an extra cable set they'd be willing to part with so I can bring these beasts back to life, I'd appreciate it! Ideally I would like to find the following: 7009026 Cable which is two ribbon cables with a M933B or C flip chip on the other end The interface cable between the two drives: BC11A The terminator card M930 At minimum, I'm pretty sure I'd only need the first cable to run one of the drives, but I'd appreciate any help from those who have more experience. Also, I don't have a rack for this equipment yet, so I'm running it all tabletop, but I'm in the market for a rack + rails (I only have the rails for the equipment, but not the ones that mount to the rack itself. Any leads on more 16-sector packs would also be appreciated! Also, still hoping to get the extended arithmetic boards, RTC, and possibly a TSC8 Timesharing option as I have 4 SLUs and would love to try out some timesharing. On a side note, I'm looking to perhaps sell or trade my SOL-20 sometime soon. It's 100% working as I restored it about 3 years ago. It works great, but I'm looking to part with all of my S-100 equipment to focus more on DEC. Thanks!
