> These problems could be solved by locating the device drivers in the \DEV
> directory and not making them visible in any directory. 

That's the unix solution, but it creates one heck of a nightmarish
directory structure...

The solution -I- was always fond of was putting a colon after the device
name.  you can echo ath0 > com1: and that'll work fine.

Also, this way you could consider the various hard drives to be
"devices".  You could install a ram disk driver and access it as
ram:\files much more easily.  Or you could install a print spooler and
provide support for something along the line of dir prn: and it could list
jobs waiting to be printed.  Sick, eh?

And the nifty thing about that is, com1: and com1 wouldn't conflict any
more than drive letter a: and the filename "a".

I -HOME- that IBM is working on something similar to this with thier
"dynamically installable device driver" model.  If not, perhaps I
should suggest it to them, but why would they pay attention to me?

Rob
 
--- Xblat