bates@ssdevo.dec.com (Ken Bates DTN 522-2039) (10/14/86)
Does anyone know if the global location "BootDrive" (location 0x210) is really valid? If I access it on either a HD20 or a HyperDrive, the contents are 0x8023, which strikes me as a rather weird drive number. If I take this number as valid and skim through the vcb queue looking for a match, I never find it (looking for a match between BootDrive and vcbDrvNum). Booting from a floppy, BootDrive turns out to be 0xFFFF, which is even stranger. The goal of this was to find out the vRefNum of the boot drive (i.e., which drive should not be unmounted). I had planned to access BootDrive, then skim through the vcb queue looking for a match, and then using vcbVRefNum of the matching vcb entry, but since the contents of BootDrive appear to be bogus, I can't do it this way. Any suggestions on 1) why this fails and 2) how to determine the boot drive? - Ken Bates
dwb@well.UUCP (David W. Berry) (10/16/86)
Correct me if I'm wrong (Good thing I give you permission, otherwise you never would, right :-) but BootDrive holds the wdRefNum of the "Blessed" folder on systems starting with 3.X. -- David W. Berry dwb@well.uucp dwb@Delphi dwb@GEnie 293-0752@408.MaBell