I have an old daisy wheel printer by Hewlett-Packard, their 2601A. We got
this from an estate cleanout and I would like to sell it. It has been
powered up and the power light comes on and the carriage moves to the
starting position. It is a large, very heavy machine. I have it on ebay for
$150 (https://www.ebay.com/itm/223533138720) but that was just a shot in
the dark. There is a better description and more pictures in the listing.
Any reasonable offer considered. I have no way to ship this item from here
but will drop it off at the ups store. The buyer will have to make their own
arrangements for packing and shipping with ups.
Mark
mark at meba.com
Andrea (Brent & Glen)
Nice work spotting the factory ..
Needless to say, it might not even be possible to do anything, but hopefully someone takes an interest!
Hi
???? Due to the help from Glen Slick. (The only guy to answer the
question as asked.)
???? What to do is interesting. How to do it will get you there.
I now have a SCSI drive on the 11/93 that thinks its an RD54 and is
trying to boot RSTS/E.
It fails gracefully during the boot? giving an error message.
So we have a working Hard Drive and Controller on the target system.
No to find out what it does not like.
The transfer rig is now working OK.
So I can try out more drives if needed
Rod
--
> From: Holm Tiffe
> You have to have an already existing parition structure on the disk and
> an OS that knows what todo with that.
The "--list" command to 'dd' gives a whole bunch of stuff:
Win32 Available Volume Information
\\.\Volume{cd4ae459-0daa-11e2-9625-806d6172696f}\
link to \\?\Device\HarddiskVolume1
fixed media
Mounted on \\.\d:
\\.\Volume{f3c65dd6-01af-11e1-a511-806d6172696f}\
link to \\?\Device\HarddiskVolume2
fixed media
Mounted on \\.\c:
\\.\Volume{f3c65dd7-01af-11e1-a511-806d6172696f}\
link to \\?\Device\CdRom0
CD-ROM
Mounted on \\.\m:
\\.\Volume{a531c21e-b869-11d9-9977-806d6172696f}\
link to \\?\Device\Floppy0
removeable media
Mounted on \\.\a:
\\.\Volume{89bdc974-217e-11e8-96f6-00038a000015}\
link to \\?\Device\Harddisk2\DP(1)0-0+7
removeable media
Mounted on \\.\e:
NT Block Device Objects
\\?\Device\CdRom0
size is 2147483647 bytes
\\?\Device\Floppy0
\\?\Device\Harddisk0\Partition0
link to \\?\Device\Harddisk0\DR0
Fixed hard disk media. Block size = 512
size is 20020396032 bytes
\\?\Device\Harddisk0\Partition1
link to \\?\Device\HarddiskVolume2
\\?\Device\Harddisk1\Partition0
link to \\?\Device\Harddisk1\DR1
Fixed hard disk media. Block size = 512
size is 10262568960 bytes
\\?\Device\Harddisk1\Partition1
link to \\?\Device\HarddiskVolume1
\\?\Device\Harddisk2\Partition0
link to \\?\Device\Harddisk2\DR6
Removable media other than floppy. Block size = 512
size is 15833497600 bytes
\\?\Device\Harddisk2\Partition1
link to \\?\Device\Harddisk2\DP(1)0-0+7
Removable media other than floppy. Block size = 512
size is 15829303296 bytes
some of which appear to be entire disks, not partitions.
Since I was trying to write into a specific area of an SD card connected via a
USB adapator, I took the path which seemed to be that of least resistance,
which was to use a partition which covered the blocks I wanted to write.
If I needed to write the boot block (which contains the partition table), I'd
have probably tried using some of the other devices in the list, but since I
didn't need to, I decided not to get diverted from my real goal by trying
other devices.
Maybe it won't work for what he needs to do. But it worked fine for me, doing
something very similar, so I thought I'd mention it.
Noel
Hey all,
I bumped into someone who has some early (mid 1970 on some of the photos
I've seen) PDP-11 bits - front panel and a handful of boards (the
backplane, PSU, rack, peripherals etc. are long gone). The front panel's
branded as "Industrial 11" though, which isn't something I've seen or heard
of before.
Address bus is 16 bits wide, and aside from the branding, the style appears
to be the same as an 11/05 or 11/10. Were there any differences to the
system internally though, or in the standard set of boards fitted, or was
the "industrial" aspect purely a marketing exercise?
cheers
Jules
Hi, sorry about the delayed reply; been dealing with this:
http://ana-3.lcs.mit.edu/~jnc/jpg/backoak/WholeTreeS.jpg
The cranes arrive tomorrow...
> I took a look at all the lines you mentioned. BDAL3-13, BDIN, BSYNC, and
> BBS7 are all active and jump around in some manner.
Hmm. Well, that shoots down the simplest theory; that a CPU BDAL (or perhaps
BDIN) driver (technically, a transceiver) chip is bad; if you're seeing any
activity at all on a line, the driver must be working. So, either both console
cards have an issue, or something more complex is going on.
Here are some pictures to show you what you should be seeing, and what I'm
seeing with an LSI-11 with no console card. First, normal operation:
http://ana-3.lcs.mit.edu/~jnc/tech/pdp11/jpg/BSYN-BDAL_OK.jpg
The top trace is BSYNC, the bottom BDAL10 (which should be asserted for
0177560, the console CSR's address; it's the 02000 bit). The timebase on this
one is 1 usec per division. As you can see, it's in a tight loop reading that
register.
The QBUS spec shows that for a DATI cycle, the DAL lines are set up before
BSYNC is asserted (falling edge here, since the bus lines are inverted).
BDA10 is indeed asserted (low) when that happens; shortly after it goes back
to 0 (high) so that device can put its data out on those lines. It stays high,
so that bit in the CSR must be 0.
OK, now a picture of the bus with no console card:
http://ana-3.lcs.mit.edu/~jnc/tech/pdp11/jpg/BSYN-BDAL_NoCon.jpg
It's a bit hard to interpret what's going on here (note that the timebase is
much larger - 5 usec). The long assertion of BSYNC is undoubtly the CPU trying
to get the console CSR to respond, and eventually timing out. Not sure what
the short assertion following it is - without looking at the ucode for the
ODT, there's no way to know what the CPU's doing.
Even harder to understand is what the BDAL line is doing. It looks like it's
un-asserted (0, i.e. +3V) on the falling (electrically - rising, logically)
edge of BSYN (which would be incorrect - see above). And then it hops around
while BSYNC is asserted, which makes no sense at all to me.
At this point, my best guess at the most likely cause of your problem (given
the 'all the lines are doing stuff') is that both console cards have
issues. Tomorrow, when I'm not outside, I'll try and look at some other BDAL
lines and see if they are doing the same thing with no console card in.
Noel
trying to ID early core stacks from GE 200 series ( like for dartmouth basic machine) or or ERMA. any old times have close up docs or part numbers? I may have found the lost treasure...
we? have a? ?2 each 21 inch? or? ?so? wide? thing? ?with 2? monster ass? stacks? mounted in each one..
one is? intact? and? dirty? but? ? ?intact!
?the other? ?stacks? and? weird other things mounted to metal? frame? work are there? but? ? ?some? stiff is? just? hanging? off it
unit? ?2? might? be? subdivided? and shared .? ? I? have never seen? GE? core? that? was? this? large......
Metal? ?frame? has? log? ?GE? part? number? ? each? stack? has? ?one? ?too
the? game is? afoot!
if? not? solved? rather? ?quickly? they? return to the? warehouse.
thanks? ed sharpe? archivist? for smecc