> No - yours is not a bug. > > flp_use ram oops: I actually meant to say "ram_use flp", sorry. Totally confused by all this aliasing stuff already.... Tobias
He he, if you REALLY want to get confused, try using the full power of the DEV device, using the third parameter where one DEV drive links to the next and so on, letting defaults search all 8 possible drives! DEV_USE 1,win1_quill_,2 DEV_USE 2,win1_archive,3 DEV_USE 3,win1_easel,4 DEV_USE 4,win1_abacus,5 DEV_USE 5,win1_exec_,6 DEV_USE 6,win1_mydocs,7 DEV_USE 7,win1_basic_,8 DEV_USE 8,win1_ Set up something likes this, and attempting something like LOAD dev1_MYPROGRAM will look through 8 possible locations, possibly not including DATA_USE or PROG_USE defaults too! Something like: DEV_USE 1,WIN1_,2 : REM hard disk DEV_USE 2,ROM1_,3 : REM RomDisq DEV_USE 3,FLP1_,4 : REM disk drive 1 DEV_USE 4,FLP2_,5 : REM disk drive 2 DEV_USE 5,RAM1_,6 : REM ramdisk 1 DEV_USE 6,RAM2_,7 : REM ramdisk 2 DEV_USE 7,MDV1_,8 : REM microdrive 1 DEV_USE 8,MDV2_,7 : REM microdrive 2 should find something no matter where it hides as long as not in a sub-directory. Rename the DEV device, possibly add a few renamed SUB, PTH and other such devices and you have the perfect recipe for total chaos. The one useful fact is that DELETE will not try all devices erasing everything in its tracks!!! Do I get the prize for the most confusing bit of useless information? ;-)) -- Dilwyn Jones _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
