----------------------

Well, I think I finally found a way to run Windows and PC-NFS together
without having the window manager choke and die on all the drive letters
that do not have disks mounted on them.  You don't need the undocumented
"/d" option in the config sys either (which nukes the ability to see spool
files on the T: U: and V: drives).  Clearing the upper 2 bits of offset 0x43
in the current directury structure for a given drive makes the drive
"invalid" as far as DOS is concerned.  All one needs to do is scan through
all the drives through LASTDRIVE and "nuke" any drive letter that has no
disk mounted to it.  I use IOCTL (int 0x21, function 0x44, subfunction 9)
to determine if the drive is "remote" (a drive IS mounted) or "local" (a
drive IS NOT mounted) to determine this.  Once all the unused drive letters
are gone, fire up Windows and poof - no more errors accessing phantom disks.

Now there is one small disadvantage in doing this.  If, after you've nuked
all your excess drive letters, you mount or unmount a drive (yes, NET USE
still works) the new drive will still be invalid, and the dropped drive
will still exist (as far as DOS is concerned).  My solution is to first
mark every drive letter as valid, then check each drive and mark the
invalid ones.  After any NET USE command, simply repeat this process to
reflect the change.
