5 Dec
2006
5 Dec
'06
5:44 p.m.
At 12:17 PM -0500 12/5/06, Dave McGuire wrote:
On Dec 5, 2006, at 12:10 PM, Ethan Dicks wrote:
The reason I recommended leaving RSTS/E to last is that installing it
and DECnet/E can be tricky to say the least. Of the 3 (4 if you
count M+ separately), it seems to be the most picky about how it is
installed. I've installed RT-11, RSX-11M, and M+ all from CD-R, but
have yet to figure out how to do that with RSTS/E. Trust me,
DECnet/E doesn't like it if you try to install off of a 4mm DAT tape.
It took me a long time to figure out that was half my problem (the
other half was a marginal Network switch). Basically RSTS/E is the
only reason my PDP-11/73 still has a TZ30 (TK50) drive.
Zane
--
| Zane H. Healy | UNIX Systems Administrator |
| healyzh at aracnet.com (primary) | OpenVMS Enthusiast |
| MONK::HEALYZH (DECnet) | Classic Computer Collector |
+----------------------------------+----------------------------+
| Empire of the Petal Throne and Traveller Role Playing, |
| PDP-10 Emulation and Zane's Computer Museum. |
| http://www.aracnet.com/~healyzh/ |
Agreed as well. I have nothing against RSTS/E,
but having worked with
all three OSes, I'd suggest learning something about RT-11 before
tackling RSTS, and even then, seeing if RSX11M or M+ had something to
offer before tackling RSTS. It has its place, but that place tended
to be larger systems intended for multiple simultaneous users. The
OP's CPU has plenty of horsepower to go around, but RSTS is complex
enough that it might take a lot of work to get a system to the point
where it's something fun to play on rather than a seemingly-perpetual
exercise in software archaeology. I've done both RSTS and RSX
sysgens... the RSX ones seemed to be more straightforward and resulted
in a running system with less user intervention.
Interesting...My RSTS vs. RSX experience has been exactly the
opposite. For me, on my old 11/34a eons ago, an RSX sysgen (v4.1)
took many hours of painstaking work, whereas a RSTS sysgen (v9.4)
took five minutes of interactive work and then let the command
procedure run until it's done.