Dear managers,
the Dec guy came with another boad PMAZC-AA (with firmware version 2.3,
mine was 2.1) and the result was the same, that is the boot command (boot "
1/dka400 ") did not work with both cd (firmware 5.0 and DU 4.0B operating
system). That was not the firmware of the board...
So we decided with the Dec guy to plug (with the right cable he brought)
the cdrom on the first controller, instead of a BA350.
We were then able to upgrade the firmware of the 3000 box to 7.0, booting
on the cd firmware 5.0.
After plugging again the BA350 on the first controller, and the cdrom on
the PMAZC board, the boot command (allways the same, boot " 1/dkb400 ")
did not work after this upgrade with the firmware upgrade 5.0 cd, but it
has worked with the Digital Unix Operating System 4.0B cd ...Seems illogic,
no ? Or the format of these cd is different ? I don't know.
Thanks for your numerous responses,
Regards,
JD
Original post :
Hi gurus...
I'm trying to update the firmware and update to dunix 4.0b a 3000/600 box
with Dunix 3.2G. The problem is that the cdrom device is on the second scsi
bus (with a PMAZC option card) . So the command to boot is (from the
installation guide of DU 4.0):
boot " 1/dka400 "
because the cdrom device is on the slot 1, device number 4 (verified with
the command " t tc1 cnfg " at the >>>prompt)
All that I get is an error message that I can't read but looks like "
access violation " followed by a dump on the console. I've tried several
cdroms (firmware releases 3.4,3.7,3.8,5.0 ; Operating system volume 1), and
got always the same behaviour...So...What's wrong ?
Received on Thu May 14 1998 - 15:55:48 NZST