|
HP OpenVMS Systemsask the wizard |
|
The Question is: Error message: BOOT DKA300.3.0.1004.0 BLOCK 0 OF DKA300.3.0.1004.0 IS NOT VALID BOOTBLOCK BOOTSTRAP FAILURE I have both OpenVMS and NT on the Alpha machine on a single drive, and when running Disk Administrator under NT it asked for writing a signature on all disks, it was saying that it's safe for nonwin OS-es so I clicked Yes. I guess the problem is in the bootblock but I don't know how to repair it. If I stop it when this error is shown I get the >>> prompt and I can boot the NT easily, but not the OpenVMS. The Answer is :
Microsoft Windows NT lied. Writing the "signature" is only a safe
operation as far as Windows NT is concerned. The "signature" can
and often is a fatal disk structure corruption to any other disk
file structure used by another operating system.
The OpenVMS Wizard uses the following rule of thumb:
If any product asks if some operation it wants to perform is
"OK", then it is often inherently not an "OK" operation. Until
you become familiar with exactly what the product wants to do,
you will probably not want to allow the program to perform the
requested operation. (ie: If the operation were truely safe or
entirely innocuous, then the product would not have been set up
to ask the question in the first place.)
Unfortunately, you will likely need to restore your OpenVMS disk(s)
from BACKUP. Dependong on exactly what Windows NT corrupted on the
disk and if you have access to the OpenVMS bootable environment (the
OpenVMS CD-ROM installation kit), you MAY be able to salvage the disk
by writing a new boot block onto the disk via the WRITEBOOT utility
and running the disk analysis utility. (To be certain of clearing
the disk structure corruption, you will have to reinstall.)
Do not allow Microsoft Windows NT to access disks using any disk or
file structure that is not explicitly recognized by Microsoft Windows
NT. (The same holds for any other operating system accessing a disk
using a Microsoft Windows NT disk structure for write operations -- do
not allow this to happen, unless the operating system supports the disk
structure.
|