Posts: 6 Location: Apeldoorn, The Netherlands Joined: 12.01.06
Posted on February 16 2007 01:37
Just another few suggestions:
- Is your medium ok (works on another system?)
- is the scsi-bus properly terminated (is the terminator neatly seated and working?, normally poorly terminated scsi-busses will result in (a lot of) strange intermitted error messages, possibly starting later in the boot sequence or even when running OpenVMS.
- can you boot the firmware cd -> cdrom drive OK
- Is the OpenVMS supporting this hardware, IIRC not all (very old) systems are supported any more with the latest OpenVMS versions.
- Do you have enough memory (minimum required quantity)
- do a conversational boot (boot dka400 -fl 0,1) see snippet below.
I hope this will help a bit...
The following is a list of values you can specify with the SET BOOT_OSFLAGS command.
NOTE: HP recommends that you keep the BOOT_OSFLAGS parameter at the default value 0 unless you have a specific need to change it (for example, to troubleshoot a system boot problem).
Hexadecimal Value System Response
Allows a conversational boot (the system displays the SYSBOOT> prompt).
Maps XDELTA to a running system.
Stops the boot procedure at the initial system breakpoint.
Performs a diagnostic bootstrap.
Stops the boot procedure at the bootstrap breakpoints.
Omits header from secondary bootstrap image.
Prompts for the name of the secondary bootstrap file.
Halts the system before the secondary bootstrap.
Marks corrected read data error pages as bad.
Displays extensive, detailed debug messages during the boot process.
Displays selected user-oriented messages during the boot process.
The following examples show how to use the SET BOOT_OSFLAGS command:
The following command specifies the root directory as 0 and the parameter as 1, which sets the system to perform a conversational boot from the [SYS0] directory when you enter the BOOT command:
Yes, we ran thru this with Stephen- basically the boot bails out with what you see in first post, so before loading bootstrap: that's why I'm suspecting RRD- but finding a drive that still supports 512b sectors proves very difficult, even on eBay and local auctions. Well, an AlphaStation 600 5/333 is heading my way (supposedly dead though- that's why it was costing 40 bucks with shipping).
I'm thinking of pushing Tru64 for it, but you never know, maybe I'll try to fool the installer and install just base raw VMS on "jensen" drive, then move the drive back.
PS.: Yup, it's says Alpha in the print on CD- though, of course, I can't really verify the content
The RRD42 is a standard DEC drive, so it should work just fine. I usually select that as my first culprit for unknown dirve configurations, when I saw RRD42, I figured it had to be something else. Some drives are typically 512, but have jumpers to allow 512 byte operation. I've seen a couple of references that this drive might have a 512/2048 jumper. Can you take the drive out and look on it? These kind of things are generally visibly marketed on the back of the drive, and it probably a DIP switch pack.
[quote:70e2cf2a22="imiller"]Re XDM -have you RTFM ?
Well, figured that one out: nowdays X servers have access control lists enabled by default (tried Sun, X.org, XF86), when started with -ac option (which disables access control), I'm good to go to DECwindows land.
Now the silly question: how can I get "dtlogin" (or whatever it's called in DECwindows) instead of xdm screen- the question is of course more about the "what it's called" part (knowing where XDM files reside in sys$specific:[tcpip$xdm] it's no problem to configure it now)
Let there be DECWindows! The Jensens are nice systems. Looks like a typical tower PC, but once you pick it up, you realize quickly it's a little beefier. These days, I almost expect BIC to introduce a PC to market, since PC's are almost as disposable these days.
[quote:b0c70edf07="Stephen Hoffman"]The DEC 2000 and DECpc 150 AXP series (Jensen and Culzean) are not my most favorite of Alpha boxes, and not what I would recommend to the undedicated or the un-Alpha-initiated.
Yeah, my friend, who actually bought the machine first (and later I bought it for "two chickens at Chinese" could barely make it to work. Since I already had experience with AS200, getting SRM mastered wasn't much of a problem.
The series does work, but it tends to be finicky about its I/O configuration, SCSI length, graphics, firmware and ROMs, and ECU.
[u:b0c70edf07]Especially[/u:b0c70edf07] EISA configuration, SCSI works fine (just my 9 gig Seagate was recognized as 517 MB ), 2.2 firmware is actually very reliable IMO. Just if it had a REAL battery, not something from Viking...
The RRD42 is very old, and tends not to read various recordable media formulations all that well.[/quote:b0c70edf07]
...or in contrary :-)
Regardless, congrats on getting this configuration to work; booting and getting DECwindows working on this box is more of an achievement than some might realize.[/quote:b0c70edf07]
Thanks, really happy to have the machine up and running.
A little off topic, does anyone have old Tru64 V4.0 media (or Digital UNIX)?
V5 won't run...
malmberg December 12 2017 HPE only makes the most current version of OpenVMS Alpha / IA64 /VAX available to hobbyists. When I had access to the Alliance 1 program it was the same. No public downloads are allowed by HPE.
nmbonao December 08 2017 Is anybody knows OpenVMS 8.2 version downloadable version? or CD copy? Thank you very much
aarommes December 02 2017 Bitcoin and Blockchain enthusiasts ( plus distributed computing ) please connec / reply: http://www.openvmshobbyis t.com/forum/viewthread.ph p?forum_id=130&thread_id= 2991
malmberg September 10 2017 https://sourceforge.net/p /vms-ports/wiki/VMSInstal lation/ For the most part just use VMS 6.1 media instead of 7.3. But why run the older release?
DoeveR August 07 2017 Where can I find the write up on running VMS 6.1 using the simh emulator?
Bart March 20 2017 Happy to have found my password again!