> Out of curiousity wouldn't 'dd' on UNIX, or a the following on VMS work?
A hybrid disk has multiple sessions recorded on it. On the DEC disk, the
first session is a music track, and the second is a 9660 file system with
Windows gunk on it. The tarball has everything from the second session.
I tried making an ISO image, and it only saves the first session.
The content is fairly lame. Some blocky AVI's, and the DEC timeline with
low resolution images from the DEC archives, pretty much identical to the timeline that was
on the DEC website. The whole thing is about 90mb.
Henk Gooijen wrote:
> Hi Fred Jan,
>
> are you sure those are 2114's?
> Not that I am 100% sure, but to me those are 2111 RAMs, 400 ns types.
>
>
Thanks for pointing out my camera optics are better than the internals
;-). The chips are clearly 2111s, even the schematics agree with this.
Making it an even weirder design; 256 bytes of stack RAM.
Fred Jan
I contacted a friend of mine who lives in Kentucky, and forwarded that post
to him. He's not interested in the machines, but might be willing to help
out a bit:
---------- Forwarded Message ----------
Subject: Re: Fwd: HP 9000/300 computers available
Date: Monday 06 October 2008 18:45
To: "Roy J. Tellason" <rtellason at verizon.net>
> > I work in Lexington, so it's not far at all. But, like you,
> > I don't have room for those systems. I could assist someone
> > in having them shipped somewhere if anyone wanted them
> Ok, since you didn't respond to my earlier post and since I have the
> feeling from earlier comments that you're not into putting your info out
> there the way I do, how about I just take the above and forward _that_ bit
> to the list? Then I can take what replies I get and forward 'em to you.
>
> Will that work for ya?
Ok, that'll work. It's been a hectic day at work.
I may be a bit slow about getting things shipped out, too. It's
beginning to look like I may end up working lots of OT in the next
few weeks.
Dave
-------------------------------------------------------
So, if someone wants those machines, email _me_. I'll batch up the replies
and pass 'em along to Dave, to work out whatever he's able and willing to
handle with the parties involved. How's that?
--
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space, a critter that can
be killed but can't be tamed. --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James
M Dakin
The disc is a hybrid audio/isofs, so I wasn't able to figure out how to make
an image. A tarball of the isofs part is up now under
http://bitsavers.org/bits/DEC/cd
Hi.
I'm looking for reference materials regarding very early implementations
of virtual memory and/or memory protection. I'm really most interested
in exploring the evolution of these features in operating systems.
Anyone have any pointers for me as to where to look for this information?
Thanks.
Peace... Sridhar
> I'm a bit annoyed at the latest request that I falsely put
> a value of $25 on a customs form. At least he's asking
> before he bids. Would someone in Europe please comment on
> customs duties and lying on forms?
I've had $giantUScorp expect me to lie to Customs officials
about my purpose to enter Canada. They wanted to avoid
paying a $200 work visa. I told them they can pay it or they
can get someone else to do the job. I doubt $giantUScorp was
going to bail me out of a foreign jail, hire a lawyer to get
me undone and pay me for all my wages during that time.
So whilst the GNU project was announced in 1983 I've heard many examples
being cited of the source to software being shared prior to this, E.g.
IBM's VM up to vN.N. And indeed recall reading somewhere that up until a
certain point in time the source to most if not all software was
available. As vendors made their money from hardware sales and you were
unlikely to be able to buy a clone or build a machine yourself, and so
safe-guarding source code was not a major concern.
Does anyone know if the history of closed/unavailable vs. open/available
source is documented anywhere? Ideally in a book or journal that can be
properly referenced.
Regards,
Andrew
----------------
Andrew Back
a at smokebelch.org
Thanks to TonyM, I have a replacement power supply that works and I now
have the Otrona mostly running. (I do intend to repair the original
power supply -- I found what looks to be a bad transistor and I've
ordered a replacement (can't find it at the local shop.)).
The Otrona almost works properly, it just won't boot from floppy. I
need a bit of help debugging the floppy controller. Thus far I've
verified that the following are good:
- The drives themselves and the disks I'm trying to boot from (hooked
the drives up to my PC and used ImageDisk to dump the disk contents
successfully)
- The drive cable
- The NEC 765 controller (was originally bad! replaced with a known-good
765 from an old PC floppy controller and this improved things somewhat.)
Symptoms are: Drive spins up, seeks to track 0 but won't boot; running
the ROM diagnostics (thanks to Bob for a scan of the service manual!)
helps narrow down things a bit:
- The "Format" diagnostic runs, which means the heads load, the drive
seeks, and enough is working so that the Otrona thinks it's formatting.
I've tried reading the resultant diskette using ImageDisk and it chokes
on it, so I'm not sure it's formatting correctly.
- Reading or Writing a sector on a known good, CP/M formatted floppy
fails. The error code returned (4004) indicates a missing Sector ID.
There aren't a lot of chips involved in the floppy controller (about 12
or 13) so I'm hoping this shouldn't be too hard to track down. Any
suggestions on where to start? (Schematic at
http://oldcomputers.net/Attache_Schematics.pdf on page 6). Would it
make sense to start investigating the chips leading back from the /RD
DATA pin?
Thanks as always,
Josh
>
> >Thanks for the replies, all, especially Tony Duell who had it
> >spot-on:
Alas I've seen it dar too many times...
> >
> >>This normally means there's a short in the keyboard matrix, as if one =
> key=20
> >>is stuck down.
> >>
> >>What I would do is open up the keyboard casing (there are 2 screws =
> under=20
> >>the plastic posts/feet) and remove the internals.=20
> >(snip)
> >>Connect the PCB to the terminal with the normal cable and power up. =
> Most=20
> >>likely the LEDs will go through the normal sequence and there'll be no=20
> >>error message, which shows the fault is in the keyboard itself.
> >
> >The LED's do indeed cycle when the isolated PCB is hooked up, and
> >eventually "VT220 OK" appears on the screen. So now I either have
So the electronics is almsot certainly working.
> >to find the shorted key (it's pretty dirty in there so blowing
> >with compressed air might help) or just get another keyboard. I
If uou are really keen, you could try to find the shorted key. I have a
pinout of the keyboard tails, it's a 17*8 matrix :
J1 :
N/C
Row 5
Row 7
N/C
LockLED/
Col 2
Col 3
N/C
Col 4
Col 1
Col 5
N/C
J2
N/C
Col 6
COl 7
Col 8
Col 0
Col 9
HoldLED/
Row 4
Col 10
Col 11
Con 12
LED+
J3
WaitLED/
Col 13
Row 0
Col 14
Col 15
Col 16
Row 1
Row 2
Col 17
Row 3
Row 6
ComposeLED/
If you're not sure what end the pins are numbered from, the 'Row' lines
go, in order to port 0 of the 8051 microcontroller, the column lines come
>from the outputs of the '145 chips E2 (cols 0-9( and E3 (10-17)
What you need to do is check each Row connection to each Column
connection with an ohhmeter. See if you van find one that's low
resistance. When you do, let me know the row and column and I can tell
you which key that is.
You might then be lucky in that removing the key and lifting the leaf
spring away from the membrant might cure it. But alas it rarely does.
> >won't try and wash it after reading the warnings here.
> >
> >BTW I see one on ebag right now (190254818657) but it's a
> >"VT220-Style" unit, made by another manufacturer. Think it'd work
> >with a real VT220?
I doubt it. Many manufactuered copied the keyboard layout and design but
not the interface.
I thought LK201s were not that hard to find.
-tony