🚀 go-pugleaf

I've just written a short test program to find all the drives in
a system and report the characteristics of each drive.  The procedure
is simply to get the DOS list of lists (21h/52h) and walk along the
chain of disk param blocks (DPBs) until one has ffff:ffff in its
'next' field.  On stand-alone systems this has worked well.

Disaster struck when the test program was loosed on a workstation
attached to a Netware network.  The workstation has an A: and a B:
its own but nothing more; then come the server 'drives'.  My test
program stopped at B:.

The very useful book *Undocumented DOS* does say that there are no
current directory structures for network drives under Netware but
I don't believe it says there are no DPBs for those drives.

Two questions:

1. Will I really then have to try to setdisk() for each possible
drive up through LASTDRIVE (in the LoL)?

2. If so, what will I get back if I ask DOS for the DPB for each
disk I *can* change to (21h/32h)?

Any suggestions appreciated.

--
Frank Burleigh  burleigh@cica.cica.indiana.edu
USENET: ...rutgers!iuvax!cica!burleigh BITNET: BURLEIGH@IUBACS.BITNET
Department of Sociology, Indiana University, Bloomington, Indiana 47405