AlphaServer Firmware - DEC 3000 AXP

Reading the release notes before updating firmware is highly recommended.

» PDF version     » Postscript version     » Text version

Important: The default settings on some browsers may cause downloading problems with filenames having the extensions *.sys, *.btp, and *.rom. If you experience difficulties downloading files of those types, please add those extensions to MIME type application/octet-stream.

1. Download the appropriate file then rename to fwupdate.exe.

   Note: If your floppy drive is named something other than dva0, use that name instead of dva0 in the following steps.

   Enter the following commands in the directory containing fwupdate.exe on an OpenVMS system to make a bootable floppy:

   $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) fwupdate.exe
   $ init/dens=HD/index=begin dva0: fwupdate
   $ mount dva0: fwupdate
   $ create/dir dva0:[dec3000]
   $ copy/contiguous fwupdate.exe dva0:[dec3000]
   $ mcr writeboot
   No
   Yes
   [enter AXP bootfile:] dva0:[dec3000]fwupdate.exe
   $ dismount dva0:

2. Insert the floppy on the target system and boot it from the SRM console:

   P00>>> boot dva0

For more detailed instructions, please refer to the release notes.

Download appropriate file then rename to fwupdate.exe.

1. Download the file mkbootfirm which is used to make a bootable floppy diskette.
2. Format floppy diskette:
   # fddisk -fmt /dev/rfd0a

3. Run mkbootfirm
   # ./mkbootfirm fwupdate.exe | dd of=/dev/rfd0c bs=64k

   NOTE: This assumes the mkbootfirm executable is in the current directory and that the floppy is in drive zero.

4. Insert the floppy on the target system and boot it from the SRM console:

   P00>>> boot dva0

For more detailed instructions, please refer to the release notes.

Copy the downloaded file to a UNIX based network server for BOOTP booting on the target system. For details on configuring the BOOTP server, refer to Tru64 UNIX documentation or the target system's Firmware Release Notes document.

1. Copy the downloaded file to an OpenVMS based network server for MOP booting on the target system. For details on configuring the MOP server, refer to OpenVMS documentation or the target system's Firmware Release Notes document.
2. Rename file to fwupdate.sys
3. Set file attributes to ensure that the downloaded file is in a proper VMS fixed record format:

   $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) "fwupdate.sys"

Rename the downloaded file to fwupdate.exe.

1. Enter the following commands on the target OpenVMS system:

   $ set file/attr=(rfm:fix,lrl:512,mrs:512,rat:none) fwupdate.exe
   $ copy/contiguous fwupdate.exe "system_disk":[sys0.sysexe]

   NOTE: Insert the name of your system disk in place of "system_disk", for example dka100:.

2. Shut down the operating system, to get to the console prompt.

3. Boot the update utility from the console as follows:

   P00>>> boot dka100 -flags 0,80

   NOTE: Replace dka100 with the "system_disk" from previous step.

4. After some printouts, you will be asked for the bootfile. Enter the directory and file name as follows :

   Bootfile: [sys0.sysexe]fwupdate.exe