🚀 go-pugleaf

In article <4i59k9$7v2@slip.net>, shotgun@slip.net says...
>
>
>Hi,
>
>Recently I decided it would be nice to use the WhereIs command to check for 
>a file's location on ALL the drives, rather then one drive at a time. But when 
>I tried to use the command to go from one drive to the other on its own, it 
>stopped on the frist drive and quit.
>
>Reading another post on here, I got the idea to use the Assign command. Here 
>is what I tried...
>
>Assign WI: DH0:
>Assign WI: DH1: add
>Assign WI: DH2: add
>Assign WI: DH3: add
>Assign WI: DH4: add
>
>..then I typed...
>
>WhereIs WI: *.zip
>
>..when it was done searching DH0: it quit instead of going onto the next 
>drive or doing all drives at the sametime. I figured it would of done one or 
>the other. So is there a better way to have this command hunt for files in ALL 
>the drives (one after the other) or do I need another command altogether?
>
>Thanks,
>
>Michael (shotgun@slip.net)

   This is a limitation of the system, the file search utilities, which
hasn't caught up with itself, wrt the enhancements to logical assignments.
A better way? I just found out about whereis today! I suppose you should 
just write a script that'll parse your requested filename and farm it 
out to the disks.  How to get a list of devices associated with a logical?

Greg

   BTW finding specific files in S:, Libs:, devs:, L:, and c: works
for multiply-assigned logicals, in the important functions (running a program
etc.) but not in the list or dir commands (I can't cite all cases).