From: Fred Kleinsorge [kleinsorge@star.zko.dec.com]
Sent: Thursday, June 07, 2001 12:24 PM
To: Info-VAX@Mvb.Saic.Com
Subject: Re: disabling floppy drive


> CD-ROM for correction (but must have 2 disks !!).
>
> I am confused with the "corrupt sys$config.dat" resolution:
>will be DVA0: checked even if exluded in *supported* manner ??
>(as you know I do not have corrupted floppy controller on hand
> to check ;)!)


Corrupt was a euphamism for modify so the floppy wont work.

OK, here goes.  First on some other system, init a floppy

$cre/dir dva0:[000000.sys0.sysexe]
 ditto for .sysupd and .sys$ldr
$cre/dir dva0:[000000.vms$common.sysexe]
ditto for .sysupd and .sys$ldr
$set file/enter dva0:[000000.sys]syscommon.dir dva0:[000000]vms$common.dir

Now, create a file called CONFIG.DAT.  In this file, put the record for the
floppy from sys$config.dat -- but change the driver name to something silly
like SYS$NOSUCHDEVICE

Copy this file to dva0:[000000.vms$common.sysexe]

Now, boot the CD, but give it 0,80000 as the boot flags, AND add a ", DVA0"
to the end of the boot command (i.e. B -fl 0,80000 dqa0, dva0)

It will tell you that you are doing a 3rd party boot.  The secondary device
is DVA0 when it asks.

This will cause the record in sys$config.dat on the CD to be overridden.
And the floppy driver will not be loaded.

Once you complete the VMS installation, boot the new disk interactive, and
at SYSBOOT tell
SET NOAUTO 1

Now when you boot the device won't be configured (you could also have done
the 2nd boot like the CD boot to stop it).  Edit sys$config.dat and make the
same change you did to config.dat - and the floppy will then never be
loaded -- OR you can simple tell SYSMAN to have an exclude list with DVA0 in
it.