RE: Real tape drive densities
> So, apparently my NRZI 9 track drive has the density option included, and I don't know if there were any other 200/556 bpi 9 track drives out there. > When we got the drive I had hoped it would be a 7 track drive, but it isn't. Now I finally get it. NRZI, 200, 556 and 800 densities, but in 9 track all the time. That's weird. You'd think the lower densities would be for 7 track. Could it be that it is a read-only for 7 tracks at lower density, but a read/write at 800 for 9 tracks? If you looked at the head you might be able to confirm if it has a dual 7 track / 9 track head. Marc
Re: Stuck bits on 11/73 Clearpoint 4MB memory - how to repair?
On 02/12/2016 6:55 PM, Jay Jaeger wrote: On 2/12/2016 5:32 PM, Jacob Ritorto wrote: Hi, Seems I have bits 4 and 3 sticking on my Clearpoint QRAM-2-SAB-1 88b 4MB memory in my pdp11/73. Can anyone offer hints as to how to identify which component is broken and how to go about repairing this? It's the only memory board in this machine, so I guess the problem might actually be a bus or processor board, right? I have no other q-bus memory to test with, so can't do swapping / process of elimination to be sure. Here's the manual: http://www.arclightindustries.com/docs/Clearpoint-88B.pdf (which I probably should add to manx or archive.org or something). Here's a snippet of the VMJA diags run illustrating bits 4 and 3 sticking. During the next VMJA run, all addresses were showing up as errored instead of just the ones ending in xxx000xx, so I guess it's getting worse! @173000g Starting system BOOTING UP XXDP-XM EXTENDED MONITOR XXDP-XM EXTENDED MONITOR - XXDP V2.5 REVISION: F0 BOOTED FROM DL0 124KW OF MEMORY NON-UNIBUS SYSTEM RESTART ADDRESS: 152000 TYPE "H" FOR HELP ! .R VMJA?? VMJAB0.BIC CVMJAB0 ECC/PARITY MEMORY DIAGNOSTIC 11/83 CACHE AVAILABLE SWR = 00 NEW = 40 CSR MAP CSR 0 1 2 3 4 5 6 7 8 9 A B C D E F MEMTYPE P CSR NUMBER 0 CONTROLS TOO MANY BANKS 2044K OF Q-BUS PARITY MEMORY 2044K WORDS OF MEMORY TOTAL MEMORY CONFIGURATION MAP 16K WORD BANKS 1 2 3 4 5 6 7 012345670123456701234567012345670123456701234567012345670123 ERRORS MEMTYPE CSR PROTECT PP 1 1 1 1 1 1 1 0 1 2 3 4 5 6 456701234567012345670123456701234567012345670123456701234567 ERRORS MEMTYPE CSR PROTECT 1 7 01234567 ERRORS MEMTYPE CSR PROTECT MEMORY DATA ERROR PCBANK VADD PADD GOOD BAD XOR CSR MTYP INT PAT 027606 10 06 0100 10 30 20 0 P 27 027606 10 060002 0102 10 30 20 0 P 27 027606 10 060004 0104 10 30 20 0 P 27 027606 10 060006 0106 10 30 20 0 P 27 027606 10 060010 0110 10 30 20 0 P 27 << SNIP >> Well clearly it is only affecting certain address bits - or the diagnostic would not run at all - note that it is starting at 01000, so that points to the memory, rather than the processor or bus, at least as a first approximation. No guarantees, but I'd sure start with that as a working theory. Another sign: this is right at the boundary between two rows. If you can't find a schematic, you can use the address to identify the address lines on the bus (See Table 3, page 1-5), and trace them on the board to find the relevant row of chips. Then use the bits the same way to identify the specific chips. If the chips are in sockets, you could always pull them one at a time to find the relevant place in the array, as well. ... Are you seeing the parity error light when this occurs? Anyway, once the relevant chip(s) are identified, if they are in sockets you can swap them with other bits or the same bits in other rows to confirm. Otherwise you get to unsolder the suspects, and put in new ones. JRJ An old trick we use for testing soldered in DRAM is to simply jam a known-to-be-good DRAM on top of the suspect one (legs bent in to make good contact). DRAM normally fail bits high and so putting a good one on top causes nothing different to happen if the suspect is good, but if the suspect is bad then the top DRAM will drive the output and your RAM test will pass. Of course you wedge the good one on the suspect when the power is off. Unless you are in a rush, and willing to possibly kill your test DRAM. As a side note - there appears to be an error message: "CSR NUMBER 0 CONTROLS TOO MANY BANKS" Or is that irrelevant? I know nothing about the PDP-11 test messages... John :-#)#
Re: IBM System z9 available near Ann Arbor, MI
There's another z9 in Vancouver, WA. Has two tape drives with it as well, but starting bid is $1200. http://www.publicsurplus.com/sms/auction/view?auc=1542011
Re: pdp11/04 : the pics....
On Fri, Feb 12, 2016, Charles Anthony wrote: > On Fri, Feb 12, 2016 at 8:29 PM, Eric Christopherson < > echristopher...@gmail.com> wrote: > > > On Feb 12, 2016 11:10 AM, "Jos Dreesen" wrote: > > > > > > > > > On ftp.dreesen.ch/PDP11 you can find some pics on how the rescued > > PDP11/04 fits right in next to its cousin, a PDP8/a > > > > > > This 8a, BTW, has more memory (128K x 12) and more oomph ( a FPP8A ) > > than the PDP11/04 > > > > > > > > > Jos > > > > I'm just getting a Synology page-not-found page. > > > > Try ftp://ftp.dreesen.ch/PDP11 (It's marked as an HTTP link, but's it > really an FTP. Oh, yes. I didn't see that the URL had no explicit protocol part. Should have tried that. -- Eric Christopherson
RE: IBM 3290 terminal
> -Original Message- > From: cctalk [mailto:cctalk-boun...@classiccmp.org] On Behalf Of Kevin > Bowling > Sent: 13 February 2016 05:26 > To: General Discussion: On-Topic and Off-Topic Posts > > Subject: Re: IBM 3290 terminal > > Thanks for your opinion on compatibility. I talked to a friend that is a > career > IBMer and learned the support disks are 1.2MB floppies that go in the 2nd > drive and are trivially created and imaged with PC/AT drives. Can you just copy them to a 1.44 3.5" disk then and pop in the Memorex. I know the Memorex Disks are DOS compatible as I have some but the controller they went with was long gone when I acquired them... > > Regards, > Kevin > Dave G4UGM
Re: Real tape drive densities
On Thu, 11 Feb 2016, Christian Corti wrote: I have a 7970B (-236) with options 127, 006, 007, 012 and 023. According to the HP 1000 Peripherals Selection Guide from 1982, page 16, option 236 specifies an 800bpi master magnetic tape subsystem with one drive and two-card 13181B interface. And you can't mix 800 and 1600 bpi on the same interface for the HP 1000. You need either the 13181 for NRZI, or the 13183 for PE. So, apparently my NRZI 9 track drive has the density option included, and I don't know if there were any other 200/556 bpi 9 track drives out there. When we got the drive I had hoped it would be a 7 track drive, but it isn't. Christian
Re: Real tape drive densities
On Fri, 12 Feb 2016, Curious Marc wrote: Can you confirm it can read and write 9 track formats in PE 1600 cpi? Was there ever a 7970B with PE? I have the manual matching this unit (serial number is marked on the cover page) and there's no mention of PE AFAIK. It's the 1971 version of the 7970B/C manual, the drive is from 1971, too. What I know is that I can read and write 800bpi 9 track tapes. I've not tried the other densities, yet. Christian
Stuck bits on 11/73 Clearpoint 4MB memory - how to repair?
Hi, Seems I have bits 4 and 3 sticking on my Clearpoint QRAM-2-SAB-1 88b 4MB memory in my pdp11/73. Can anyone offer hints as to how to identify which component is broken and how to go about repairing this? It's the only memory board in this machine, so I guess the problem might actually be a bus or processor board, right? I have no other q-bus memory to test with, so can't do swapping / process of elimination to be sure. Here's the manual: http://www.arclightindustries.com/docs/Clearpoint-88B.pdf (which I probably should add to manx or archive.org or something). Here's a snippet of the VMJA diags run illustrating bits 4 and 3 sticking. During the next VMJA run, all addresses were showing up as errored instead of just the ones ending in xxx000xx, so I guess it's getting worse! @173000g Starting system BOOTING UP XXDP-XM EXTENDED MONITOR XXDP-XM EXTENDED MONITOR - XXDP V2.5 REVISION: F0 BOOTED FROM DL0 124KW OF MEMORY NON-UNIBUS SYSTEM RESTART ADDRESS: 152000 TYPE "H" FOR HELP ! .R VMJA?? VMJAB0.BIC CVMJAB0 ECC/PARITY MEMORY DIAGNOSTIC 11/83 CACHE AVAILABLE SWR = 00 NEW = 40 CSR MAP CSR 0 1 2 3 4 5 6 7 8 9 A B C D E F MEMTYPE P CSR NUMBER 0 CONTROLS TOO MANY BANKS 2044K OF Q-BUS PARITY MEMORY 2044K WORDS OF MEMORY TOTAL MEMORY CONFIGURATION MAP 16K WORD BANKS 1 2 3 4 5 6 7 012345670123456701234567012345670123456701234567012345670123 ERRORS MEMTYPE CSR PROTECT PP 1 1 1 1 1 1 1 0 1 2 3 4 5 6 456701234567012345670123456701234567012345670123456701234567 ERRORS MEMTYPE CSR PROTECT 1 7 01234567 ERRORS MEMTYPE CSR PROTECT MEMORY DATA ERROR PCBANK VADD PADD GOOD BAD XOR CSR MTYP INT PAT 027606 10 06 0100 10 30 20 0 P 27 027606 10 060002 0102 10 30 20 0 P 27 027606 10 060004 0104 10 30 20 0 P 27 027606 10 060006 0106 10 30 20 0 P 27 027606 10 060010 0110 10 30 20 0 P 27 027606 11 06 0110 11 31 20 0 P 27 027606 11 060002 0112 11 31 20 0 P 27 027606 11 060004 0114 11 31 20 0 P 27 027606 11 060006 0116 11 31 20 0 P 27 027606 11 060010 01100010 11 31 20 0 P 27 027606 12 06 0120 12 32 20 0 P 27 027606 12 060002 0122 12 32 20 0 P 27 027606 12 060004 0124 12 32 20 0 P 27 027606 12 060006 0126 12 32 20 0 P 27 027606 12 060010 01200010 12 32 20 0 P 27 027606 13 06 0130 13 33 20 0 P 27 027606 13 060002 0132 13 33 20 0 P 27 027606 13 060004 0134 13 33 20 0 P 27 027606 13 060006 0136 13 33 20 0 P 27 027606 13 060010 01300010 13 33 20 0 P 27 027606 14 06 0140 14 34 20 0 P 27 027606 14 060002 0142 14 34 20 0 P 27 027606 14 060004 0144 14 34 20 0 P 27 027606 14 060006 0146 14 34 20 0 P 27 027606 14 060010 01400010 14 34 20 0 P 27 027606 15 06 0150 15 35 20 0 P 27 027606 15 060002 0152 15 35 20 0 P 27 027606 15 060004 0154 15 35 20 0 P 27 027606 15 060006 0156 15 35 20 0 P 27 027606 15 060010 01500010 15 35 20 0 P 27 027606 16 06 0160 16 36 20 0 P 27 027606 16 060002 0162 16 36 20 0 P 27 027606 16 060004 0164 16 36 20 0 P 27 027606 16 060006 0166 16 36 20 0 P 27 027606 16 060010 01600010 16 36 20 0 P 27 027606 17 06 0170 17 37 20 0 P 27 027606 17 060002 0172 17 37 20 0 P 27 027606 17 060004 0174 17 37 20 0 P 27 027606 17
Re: Stuck bits on 11/73 Clearpoint 4MB memory - how to repair?
On 2/12/2016 5:32 PM, Jacob Ritorto wrote: > Hi, > Seems I have bits 4 and 3 sticking on my Clearpoint QRAM-2-SAB-1 88b > 4MB memory in my pdp11/73. > > Can anyone offer hints as to how to identify which component is broken > and how to go about repairing this? > > It's the only memory board in this machine, so I guess the problem > might actually be a bus or processor board, right? I have no other q-bus > memory to test with, so can't do swapping / process of elimination to be > sure. > > Here's the manual: > http://www.arclightindustries.com/docs/Clearpoint-88B.pdf (which I probably > should add to manx or archive.org or something). > > Here's a snippet of the VMJA diags run illustrating bits 4 and 3 > sticking. During the next VMJA run, all addresses were showing up as > errored instead of just the ones ending in xxx000xx, so I guess it's > getting worse! > > @173000g > > Starting system > BOOTING UP XXDP-XM EXTENDED MONITOR > > XXDP-XM EXTENDED MONITOR - XXDP V2.5 > REVISION: F0 > BOOTED FROM DL0 > 124KW OF MEMORY > NON-UNIBUS SYSTEM > > RESTART ADDRESS: 152000 > TYPE "H" FOR HELP ! > > .R VMJA?? > VMJAB0.BIC > > CVMJAB0 ECC/PARITY MEMORY DIAGNOSTIC >11/83 CACHE AVAILABLE > SWR = 00 NEW = 40 > > >CSR MAP > > CSR 0 1 2 3 4 5 6 7 8 9 A B C D E F > MEMTYPE P > > > CSR NUMBER 0 CONTROLS TOO MANY BANKS > 2044K OF Q-BUS PARITY MEMORY > 2044K WORDS OF MEMORY TOTAL > > MEMORY CONFIGURATION MAP > 16K WORD BANKS > 1 2 3 4 5 6 7 > 012345670123456701234567012345670123456701234567012345670123 > ERRORS > MEMTYPE > CSR > PROTECT PP > 1 1 1 1 1 1 1 > 0 1 2 3 4 5 6 > 456701234567012345670123456701234567012345670123456701234567 > ERRORS > MEMTYPE > CSR > PROTECT > 1 > 7 > 01234567 > ERRORS > MEMTYPE > CSR > PROTECT > MEMORY DATA ERROR > PCBANK VADD PADD GOOD BAD XOR CSR MTYP INT PAT > > 027606 10 06 0100 10 30 20 0 P 27 > 027606 10 060002 0102 10 30 20 0 P 27 > 027606 10 060004 0104 10 30 20 0 P 27 > 027606 10 060006 0106 10 30 20 0 P 27 > 027606 10 060010 0110 10 30 20 0 P 27 << SNIP >> Well clearly it is only affecting certain address bits - or the diagnostic would not run at all - note that it is starting at 01000, so that points to the memory, rather than the processor or bus, at least as a first approximation. No guarantees, but I'd sure start with that as a working theory. Another sign: this is right at the boundary between two rows. If you can't find a schematic, you can use the address to identify the address lines on the bus (See Table 3, page 1-5), and trace them on the board to find the relevant row of chips. Then use the bits the same way to identify the specific chips. If the chips are in sockets, you could always pull them one at a time to find the relevant place in the array, as well. I expect this is not the issue, but, one has to ask these things, just in case. Did this memory work before? I ask because this is the 19th bit. If the backplane is a Q18 backplane, that might be a problem? Along those same lines, make sure that jumper P07 is positioned correctly for a 22 bit address, and that P05 and P06 are set correctly for the memory size. Are you seeing the parity error light when this occurs? Anyway, once the relevant chip(s) are identified, if they are in sockets you can swap them with other bits or the same bits in other rows to confirm. Otherwise you get to unsolder the suspects, and put in new ones. JRJ
Re: pdp11/04 : the pics....
Clicking on the link gets me: Sorry, the page you are looking for is not found. cut/patse and trying as a fto server times out On Fri, Feb 12, 2016 at 12:33 PM, Jay West wrote: > No, the "pride of the collection" must be the HP calculator on top ;) > > J > > > >
Re: Stuck bits on 11/73 Clearpoint 4MB memory - how to repair?
On Fri, Feb 12, 2016 at 3:32 PM, Jacob Ritorto wrote: > Hi, > Seems I have bits 4 and 3 sticking on my Clearpoint QRAM-2-SAB-1 88b > 4MB memory in my pdp11/73. > > Can anyone offer hints as to how to identify which component is broken > and how to go about repairing this? Are the 256Kx1 DRAM chips in sockets? If they are it shouldn't be too hard to come up with a scheme for exchanging some of the DRAM chips to see if the stuck bits move and then work out which chip positions map to which bits and then which DRAM chips need to be replaced.
