Re: DEC BA213 and BA213 S-boxes?
On Sat, Mar 31, 2018, 4:26 PM Glen Slick via cctechwrote: > On Sat, Mar 31, 2018 at 9:04 AM, Bill Degnan via cctech > wrote: > > > > FYI - Not sure if I mentioned this but I too am working on setting up a > > DECServer 550 to be an 11/83. Useful tips recently, thanks all. > > b > > Using an M7554 KDJ11-D DECserver 550 CPU (in which case it would be an > 11/53), or with an M8190 KDJ11-B CPU? > > Using an M7554 KDJ11-D DECserver 550 CPU is nice in that you get 1.5MB > of RAM on board and the two MMJ async ports on the S-handle bracket, > but of course it is slower than an M8190 KDJ11-B CPU because it has no > cache, no support for adding an FPJ11 FPA, and no support for PMI > memory. > > With an M8190 KDJ11-B CPU you would have to hack up some sort of > bracket for the console async port, and for the diagnostic LED display > if you wanted that too. If DEC ever made an S-handle console panel for > the M8190 KDJ11-B CPU I have never seen one. > I am starting with the M8190 AE (CPU) M8637 EH (or EA?) RAM M8637 EH RAM I have other cards here: http://vintagecomputer.net/browse_thread.cfm?id=715 With these I should be able to get started, thanks all for the info. Bill >
Re: DEC 3000 (alpha) faultfinding
> > According to the 21066 HRM, the processor loads its initial I-stream from > the SROM. All Icache bits are loaded from the SROM, including the cache > block metadata. The blocks are loaded in sequential order starting with > block 0 and ending with block 255. For the 20166, the Icache is loaded > LSB first filling from left to right (i.e. bit 0 of LW0 will be the first > bit loaded). This is the resulting order of each cache block: > > BHT LW7 LW5 LW3 LW1 V ASM ASN TAG LW6 LW4 LW2 LW0 > No wonder I am not making sense of the image! > > I thought I had some code do unmultiplex each bit stream from an SROM image > and then reconstruct the resulting memory image, but I can't find it or I > just thought about doing that. > If it turns up and it works on a 21064, I'd be very interested in a copy. It looks like I may have to program a new SROM image in order to disable the cache at startup to see if that works around the issues my machines are having (assuming I can figure out how to disable the cache). Regards, Peter Coghlan.
Re: DEC 3000 (alpha) faultfinding
> > According to the 21066 HRM, the processor loads its initial I-stream from the > SROM. All Icache bits are loaded from the SROM, including the cache block > metadata. The blocks are loaded in sequential order starting with block 0 > and ending with block 255. For the 20166, the Icache is loaded LSB first > filling from left to right (i.e. bit 0 of LW0 will be the first bit loaded). > This is the resulting order of each cache block: > > BHT LW7 LW5 LW3 LW1 V ASM ASN TAG LW6 LW4 LW2 LW0 > No wonder I am not making sense of the image! > > I thought I had some code do unmultiplex each bit stream from an SROM image > and then reconstruct the resulting memory image, but I can't find it or I > just thought about doing that. If it turns up and it works for a 21064, I'd be very interested in a copy. It looks like I may have to program a new SROM image in order to disable the cache at startup to see if that works around the issues my machines are having (assuming I can figure out how to disable the cache). Regards, Peter Coghlan.
Re: DEC 3000 (alpha) faultfinding
> > I thought you'd get the SROM firmware to halt and wait for a command > after POST if J8 was removed and none of the other positions shorted. > Have you tried running with all positions open? > It turns out that jumpers J8-J1 select one of the d0-d7 outputs from the 27C512 which contains the eight SROM images, one per data line. One of the positions must be jumpered or no SROM image is loaded and nothing happens. (Nothing much seems to happen with the jumper in the J1 position either. Maybe there is no image on the d7 bit or maybe the there is an image there that doesn't drive the either the mini console port or the diagnostic LEDs.) It also turns out that I had an intermittent bad connection in my hacked up mini console interface. This is why I was not able to enter commands with the jumper in position 1 (J7) or position 2 (J6). With this fixed, I can enter mini console commands with either of those positions jumpered, so they seem to be the ways to access the mini console on the 3000 600 machines anyway. I ran the various tests provided by the different jumper settings on my second 3000 600 and I found that the memTest (no-cache) LongWord Memory Test (position 5, J3) failed as well as the tests involving the cache. In an attempt to find which memory was failing, I swapped around the memory risers. Bizarrely, the (no-cache) failures went away completely when I swapped around the front two risers. The failures returned when I swapped them back. This is very odd as the two risers appear to be identical and seem to be populated with identical SIMMs. Regards, Peter Coghlan. > > Maciej >
Re: Instruction video on laserdisk
At 07:46 AM 3/31/2018, E. Groenenberg via cctalk wrote: >Today I received a PDP-11 instruction video on a laser disk, part 3 & 4. >The disk partno. is EY-5537E-V2-0001, the title says >'Introduction to the PDP-11, Internal use Only, (c) 1988' This one? https://www.marktplaats.nl/a/cd-s-en-dvd-s/vinyl-overige/m1261283993-laser-videodisc-introduction-to-the-pdp-11.html?c=3c1f5dcc18d02a99040ca8de656940d2=lr I have LD player, digitizer, and abilities. Midwest USA. IVIS was a DEC Pro 350 system for interactive learning: https://books.google.com/books?id=wi8EMBAJ=PA18=PA18=%22digital+equipment%22+%22ivis%22=bl=k9_3BUKTrJ=lHcIslE5v9hWZ8YxAoWWFxaYnao=en=X=0ahUKEwiGwpaj1JfaAhUl74MKHcwVAfEQ6AEIOzAC#v=onepage=%22digital%20equipment%22%20%22ivis%22=false - John
Re: Speed now & then (Space and time?)
On 3/30/2018 5:32 AM, Peter Corlett via cctalk wrote: On Thu, Mar 29, 2018 at 10:07:27PM -0500, Mark Linimon via cctalk wrote: On Thu, Mar 29, 2018 at 09:00:35PM -0500, Jon Elson via cctalk wrote: It was an absolute DOG! It took several minutes for Emacs to load. So, uh, I hate to tell you about the state of the art these days ... It starts up within half a second or so on my development box, even though my .emacs pulls in all sorts of weird and wonderful packages. On my remote servers, it can take a few seconds if the box is overloaded, but is otherwise instant. A lot of traditional software has *not* encountered the kind of bloat needed to counteract Moore's Law, and so performs beautifully. What *is* bloating is Windows software -- mercifully I don't run Windows -- half-jobbed ports of said Windows software to other platforms (Firefox, mainly), and web-based stuff. The latter includes various phoned-it-in apps which are basically written in Javascript and embed an invisible web browser, which includes Slack, Spotify, and a few other bits and pieces. The obvious answer is to not use that bloated crapware and find something else that does the same job. But that is the old fly in the ointment, other software may not be avilable. I do run windows and real text screen UNIX is not aviable anymore. All I know it is same $$$ cycle as always, BUY the new machine for faster software, but you need buy the software that has bug fixes and patches for the new system and the software slows down again. GUI's gave us 8x bloat and streaming media another 8x bloat. It is about time NEW notebook computers to come out to let you use them to take NOTEs rather than some ap for your phone for notes. Ben. PS: Do I need a VALVE computer for the best sounding digital music? PPS: Notice how records are selling again.
Re: DEC BA213 and BA213 S-boxes?
On Sat, Mar 31, 2018 at 9:04 AM, Bill Degnan via cctechwrote: > > FYI - Not sure if I mentioned this but I too am working on setting up a > DECServer 550 to be an 11/83. Useful tips recently, thanks all. > b Using an M7554 KDJ11-D DECserver 550 CPU (in which case it would be an 11/53), or with an M8190 KDJ11-B CPU? Using an M7554 KDJ11-D DECserver 550 CPU is nice in that you get 1.5MB of RAM on board and the two MMJ async ports on the S-handle bracket, but of course it is slower than an M8190 KDJ11-B CPU because it has no cache, no support for adding an FPJ11 FPA, and no support for PMI memory. With an M8190 KDJ11-B CPU you would have to hack up some sort of bracket for the console async port, and for the diagnostic LED display if you wanted that too. If DEC ever made an S-handle console panel for the M8190 KDJ11-B CPU I have never seen one.
Re: Instruction video on laserdisk
I have a NTSC LD player AND a video capture device (or two). Located in the Seattle area. I recently picked up some Prisoner LDs and confirmed that LD player is still working. It did involve opening it up and blowing dust off of the optical sensors inside of it. alan On 3/31/18 10:28 AM, John Ames via cctalk wrote: I don't know where you're located, but I'm in the US and have an NTSC Laserdisc player. If someone can hook me up with a video capture card, I'd be happy to copy the video for you.
Re: Instruction video on laserdisk
I don't know where you're located, but I'm in the US and have an NTSC Laserdisc player. If someone can hook me up with a video capture card, I'd be happy to copy the video for you.
Re: How to set DZ11 line speeds under RT-11 V4?
> On Mar 30, 2018, at 10:37 AM, Fritz Muellerwrote: > > When SYSGEN-ing RT-11 V4, the only speed initialization options offered for > the DZ11 lines are 110 or 300 baud. Is there a utility or incantation which > will allow me to reconfigure these after RT-11 is booted? So I found that the sysgen process is just setting the value for the DZSP$D macro in SYCND.MAC; I can edit this to an appropriate value (7000, taken from the .MTGET programed request docs) by hand after sysgen and before assembling the monitor and, all the DZ11 lines come up configured at 9600 baud now. Still haven't found anything that comes out of the box with RT-11 V4 to allow tailoring the terminal lines once up and running. I guess if you want to do that you need to write your own small utility. cheers, --FritzM.
Re: Digitising collections of microfiche - Re: Looking for opinions...
On Thu, 29 Mar 2018, Fred Cisin via cctalk wrote: On Thu, 29 Mar 2018, geneb via cctalk wrote: I'm probably WAY over simplifying this because I don't have a grasp of the optics involved, but wouldn't it be possible to get a good image of individual pages on a microfiche by using a DSLR with the right lens and a CNC X/Y table made from one of the large (8x10) LED illuminators used to treat SAD? The lights are pretty bright and are under $50. Getting EVEN illumination throughout the frame will still be an issue. BIG issue for photographic images, but still a minor issue for bitonal text and schematics. Theoretical ideal is a point source with collimating "condenser" lenses (like the top half of an enlarger). BUT, for this, a diffuse light source or an added diffuser MIGHT be adequate. Particularly for bitonal, where half-tone density, or color balance, is not significant. The unit I saw last week was very even. The person that owned it uses it for studio lighting for video production. The X/Y table build would be very simple and cheap to build. For you, maybe. I'm a little overwhelmed contemplating that part of the project. Even the film holder is a little work. Which is why I was suggesting gutting a fiche reader for those mechanical parts, and then adding positioning mechanisms. The X/Y table is probably the simplest part of the build - every part of it is a solved problem, from the motion gantry to the controller. It could be driven by an Arduino Uno and a pair of Pololu Stepper Drivers connected to a pair of 1.8 degree NEMA17 steppers. The gantry could be made from 3D printed carriages equipped with 608 skate bearings riding atop rails made from 1/2" EMT conduit. The camera system is WAY outside my wheelhouse, but I'd be happy to work with someone to get an X/Y gantry built. I've got plenty of idle 3D printers and tons of unused skate bearings. :) g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.diy-cockpits.org/coll - Go Collimated or Go Home. Some people collect things for a hobby. Geeks collect hobbies. ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://scarlet.deltasoft.com - Get it _today_!
Re: DEC BA213 and BA213 S-boxes?
Ethan; I have owned both BA213 and BA215 microvaxes. The one recurring problem I had was with the power supplies, H7868 I think the number is. Luckily, I picked up a couple of Dec Serv 550's which gave me spares and a PDP11/53 S box CPU. I was able to run the PDP11 in one of the VAX based BA boxes, the BA215 would make a good choice based on size and weight. If I remember correctly, the BA215 had space for one full height drive and a tape drive. Maybe someone else knows, but I think both boxes could use ordinary power cords, not like the VAX 4000-400 series which has that 20 amp cord. Doug On 3/31/2018 1:14 AM, Ethan Dicks via cctech wrote: Hi, All, Watching some of the recent traffic about what newer Qbus boards will and won't work with 2.11BSD, I've remembered a thing I was once looking for. Back when I did DEC hardware for a living, we stopped buying new stuff after we got a MicroVAX-II. As such, I have plenty of LSI-11 to KA630 parts but very little from after that era. I do happen to have 2-3 boards with S-box handles including a KDF-11 CPU and a SCSI card, a great start to a system. What I don't have is the enclosure. I have a BA123 "World Box" and it's great. I know a BA213 is roughly the same size, but I've never had one. The BA215 looks more interesting to me as a match for size and power requirements (1 PSU and 6 slots, half the BA213) but I've never even seen a BA215. Anyone here have much experience with the BA215? Any "gotchas"? So far, from my looking on eBay, I think I spotted one loaded as a VAX. I'm more interested in setting mine up as a PDP-11, so the VAX end of one is not exactly a selling point to me. An empty box would do just as nicely. I'd say 80% of my Qbus work has been with two boxes, the BA-11N and the BA-23, thus all the S-box questions. Thanks for any tips, tidbits and stories. -ethan
Instruction video on laserdisk
Today I received a PDP-11 instruction video on a laser disk, part 3 & 4. The disk partno. is EY-5537E-V2-0001, the title says 'Introduction to the PDP-11, Internal use Only, (c) 1988' Besides that, no indication if the video stream is NTSC or PAL. Anybody have a clou? I want to have the disk read and put the video on youtube eventually. Ed -- Ik email, dus ik besta.
Re: DEC BA213 and BA213 S-boxes?
On Sat, Mar 31, 2018 at 11:45 AM, Douglas Taylor via cctech < cct...@classiccmp.org> wrote: > Ethan; > > I have owned both BA213 and BA215 microvaxes. The one recurring problem I > had was with the power supplies, H7868 I think the number is. > Luckily, I picked up a couple of Dec Serv 550's which gave me spares and a > PDP11/53 S box CPU. > I was able to run the PDP11 in one of the VAX based BA boxes, the BA215 > would make a good choice based on size and weight. > If I remember correctly, the BA215 had space for one full height drive and > a tape drive. > Maybe someone else knows, but I think both boxes could use ordinary power > cords, not like the VAX 4000-400 series which has that 20 amp cord. > > Doug > > > FYI - Not sure if I mentioned this but I too am working on setting up a DECServer 550 to be an 11/83. Useful tips recently, thanks all. b
Re: RL02 Question
> > From: Aaron Jackson > > > I have tried three controllers, two r/w modules and two servo > > controllers. I'm beginning to think the drive is fine and there is a > > problem with the RLV21 controller. > > Err, think you mean RLV12 QBUS controller board, right? Woops, yes! I get mixed up with the RXV21. > Anyway, you've already tried ("three controllers") swapping that out? As in the logic controller inside the drive. I only have one RLV12 unfortunately. Although a friend has recently purchased one, so hopefully I can test with that soon. > If you have, perhaps there's a problem with a cable and/or the terminator? > > > However, at this point, sub-system swapping is probably not going to be the > best way to make progress. I think you're going to have to actually debug the > problem; i.e. dive in and work out what's happening wrong, and why, and trace > it back to the origin. > > Luckily, for this generation (and before), DEC produced wonderful technical > manuals, which go into full detail of how the thing works. With that in hand, > the investigative process is a lot easier; you don't have to work out how the > thihg works by looking at the prints, it's all laid out in detail. And tech > manuals for both the RL02 drive and RLV12 controller (EK-RLV12-TD-001) are > available online, as are the prints (MP01282 for the RLV12). > > So, I'd sit down with the RLV12 tech man and read through the section on the > drive<->controller bus (section 3.3). Then start looking at what the two are > saying to each other on the bus, and figure out what's actually going wrong. > From there, you'll know where the source of the problem is, and can chase it > further. > > I know this sounds like it would be time-consuming, but when you think about > the time/energy you've already put into swapping things around, chasing this > problem, it won't be. > > Noel I have been studying the technical description manual, and the schematics in quite some detail. I think it is time I hook up a logic analyser to the cable between the RLV12 controller and the drive to try and see what is going on during the initial seek. I have already checked to see if there is a 4.1MHz clock signal (there is). Thanks, Aaron.
Re: RL02 Question
> On Sat, Mar 31, 2018 at 11:04 AM, Noel Chiappa via cctalk < > cctalk@classiccmp.org> wrote: > >> > From: Aaron Jackson >> >> > I have tried three controllers, two r/w modules and two servo >> > controllers. I'm beginning to think the drive is fine and there is a >> > problem with the RLV21 controller. >> >> Err, think you mean RLV12 QBUS controller board, right? >> >> Anyway, you've already tried ("three controllers") swapping that out? >> >> If you have, perhaps there's a problem with a cable and/or the terminator? >> >> >> However, at this point, sub-system swapping is probably not going to be the >> best way to make progress. I think you're going to have to actually debug >> the >> problem; i.e. dive in and work out what's happening wrong, and why, and >> trace >> it back to the origin. >> >> > > > I remember spending a great deal of time on my RL02 problem until I finally > figured out the problem source was the backplane. I have a UNIBUS system > and I had a miswired DD11C. I took a DD11B and removed the NPG jumper in > slot 2 as an experiment. It caused my RL02 to be functional, exposing the > DD11C as the issue. > > I know that this will not help you directly, but given you have (probably) > one working RL controller of the three I'd test the QBUS itself, power > etc. Perhaps this was already discussed I am just catching up to this > thread. I also assume this RL02 has been proven to work somewhere else > with same cables. If not I'd try that experiment too. > > Bill Thanks for the tip Bill. I have run out ideas for debugging on the drive - everything looks fine! I have starting turning my eyes towards my RLV12 controller. A friend has recently bought an RLV12, so I can test it with his in the near future. Although, studying the technical description manual, I am not seeing that any communication, other than 4.1MHz clock, is required when loading the heads. I have been assuming that all of this logic is handled by the drive only. Thanks again, Aaron.
Re: RL02 Question
On Sat, Mar 31, 2018 at 11:04 AM, Noel Chiappa via cctalk < cctalk@classiccmp.org> wrote: > > From: Aaron Jackson > > > I have tried three controllers, two r/w modules and two servo > > controllers. I'm beginning to think the drive is fine and there is a > > problem with the RLV21 controller. > > Err, think you mean RLV12 QBUS controller board, right? > > Anyway, you've already tried ("three controllers") swapping that out? > > If you have, perhaps there's a problem with a cable and/or the terminator? > > > However, at this point, sub-system swapping is probably not going to be the > best way to make progress. I think you're going to have to actually debug > the > problem; i.e. dive in and work out what's happening wrong, and why, and > trace > it back to the origin. > > I remember spending a great deal of time on my RL02 problem until I finally figured out the problem source was the backplane. I have a UNIBUS system and I had a miswired DD11C. I took a DD11B and removed the NPG jumper in slot 2 as an experiment. It caused my RL02 to be functional, exposing the DD11C as the issue. I know that this will not help you directly, but given you have (probably) one working RL controller of the three I'd test the QBUS itself, power etc. Perhaps this was already discussed I am just catching up to this thread. I also assume this RL02 has been proven to work somewhere else with same cables. If not I'd try that experiment too. Bill
towards a working PDP: Anyone has a PDP 11/35 or PDP11/40 panel for $$$ to offer?
Hello all, As I never came across a complete unit of an early PDP-11 with lights-and-switches console, I decided 5-6 years ago to figure out, if I can't build one of out of different parts. It seemed possible to get there if I focus on parts for a 11/35 or 11/40. 5 years ago, I came accross a backplane for such as system. Two years later, I was lucky to purchase an almost complete board set (one board missing, the M7232) from another classic computer enthusiast. Last year, I got a BA11-F chassis with the power supply. Over all those years, I looked out for a 11/35 or 11/40 panel (KY11-D), but I never was lucky to come accross one.On epay US, somebody is offering the plain PCB, but the seller says that he cannot ship to Europe :-( My frustation pushes me now to ask, if anybody on this list has such a panel with the electronics board that he would consider to offer me for some $$$ to help me building a complete machine? I don't mind the panel color, e.g., if it's from a front-end PDP-11 of some bigger DEC system, or if the silkscreen is damaged or even missing. It would be great for me to get an early PDP-11 up and running and connect it to peripherals such as an RK07 that are in my collection. I am located in Germany. Contact me off-list, if you have something to offer, please. Best regards,Pierre --- Pierre's collection of classic computers moved to: http://www.digitalheritage.de
Re: RL02 Question
> From: Aaron Jackson > I have tried three controllers, two r/w modules and two servo > controllers. I'm beginning to think the drive is fine and there is a > problem with the RLV21 controller. Err, think you mean RLV12 QBUS controller board, right? Anyway, you've already tried ("three controllers") swapping that out? If you have, perhaps there's a problem with a cable and/or the terminator? However, at this point, sub-system swapping is probably not going to be the best way to make progress. I think you're going to have to actually debug the problem; i.e. dive in and work out what's happening wrong, and why, and trace it back to the origin. Luckily, for this generation (and before), DEC produced wonderful technical manuals, which go into full detail of how the thing works. With that in hand, the investigative process is a lot easier; you don't have to work out how the thihg works by looking at the prints, it's all laid out in detail. And tech manuals for both the RL02 drive and RLV12 controller (EK-RLV12-TD-001) are available online, as are the prints (MP01282 for the RLV12). So, I'd sit down with the RLV12 tech man and read through the section on the drive<->controller bus (section 3.3). Then start looking at what the two are saying to each other on the bus, and figure out what's actually going wrong. >From there, you'll know where the source of the problem is, and can chase it further. I know this sounds like it would be time-consuming, but when you think about the time/energy you've already put into swapping things around, chasing this problem, it won't be. Noel
Re: Identifying an aluminum panel
The size is just large enough to fit in a 19" rack. It's also possible that I don't have what it goes to. Here are more panels to puzzle over: http://imgur.com/a/8nJ5I In related news, I am missing the bottom panels for an RK05J. Never got it with the unit I picked up, nor the cards. I've been slowly accumulating cards, but I'm not quite there yet. It's in otherwise nice shape. Not sure what happened in its former life. Kyle
Re: DEC BA213 and BA213 S-boxes?
On Fri, Mar 30, 2018 at 10:14 PM, Ethan Dicks via cctalkwrote: > > I have a BA123 "World Box" and it's great. I know a BA213 is roughly > the same size, but I've never had one. The BA215 looks more > interesting to me as a match for size and power requirements (1 PSU > and 6 slots, half the BA213) but I've never even seen a BA215. > > Anyone here have much experience with the BA215? Any "gotchas"? So > far, from my looking on eBay, I think I spotted one loaded as a VAX. > I'm more interested in setting mine up as a PDP-11, so the VAX end of > one is not exactly a selling point to me. An empty box would do just > as nicely. I have a BA215 box that was configured as a MicroVAX 3300 when I got it with an M7624 KA640 CPU. Currently I have it configured as a VAX 4000-200 with an M7626 KA660 CPU and maxed out with 64MB with a 3rd party Camintonn CMX-4200-48 48MB board and an M7622 16MB board. With DSSI and Ethernet controllers built in with the KA660 that leaves 3 of the 6 slots free for an S-handle M5976 KZQSA to attach a SCSI CD-ROM and an S-handle M3119 CXY08 for 8 async lines. Loaded up the BA215 is certainly not light, but you can easily wheel it around, and if necessary I can pick it up and carry it a short distance by myself. I won't try to move a BA123 or BA215 / BA430 / BA440 box by myself beyond just rolling them without stripping them down to completely empty boxes. If you want to set up a BA215 as a PDP-11 a nice way to go is with an S-handle M7554 KDJ11-D DECserver 550 CPU, the 18MHz version with 1.5MB. Sometimes good deals on those can be found. Then add either a 2MB M7551 MSV11-Q or a 2MB M8637 MSV11-J for 3.5MB. Add an S-handle M3127 DESQA Ethernet controller, and an M3119 CXY08 if you want more than the 2 async lines on the M7554 KDJ11-D. If the BA215 box came with any DSSI drives installed add an M7769 KFQSA. The KFQSA is MSCP compatible so later PDP-11 software should be able to use it. If you can find a decent deal on a BA215 box it is worth grabbing one. Most of the time I would rather work on a BA215 box than a BA23 / BA123 or BA215 / BA430 / BA440 box (ok, the BA440 VAX will be much faster). In some cases only 6 slots might be limiting if you wanted to use something like a 3 board set M7168 / M7169 VCB02 or a 2 board set M7164 / M7165 KDA50-Q.