#mounlist 3.0?
2 messages in this thread
hi- ive just upgraded to 3.0 from 1.3. i love it, but somre thimngs are
different, and i have a few questions? re the mountlist- do they operate the
same way? it doesnt seem to, but im not even sure 3.0 uses the mountlist in teh
same manner, from the same place etc- i guess specifically id liketo know how
to set up a VD0: on 3.0, and what i need to write on my 1.3 mountlist for it to
run the 105 syquest thats hooked into the 400 4000 that is please mail me at
72401,463 peace
Matthew: Just curious, but has 3.1 been released yet? I've heard rumors
that it had been released in Europe, but haven't seen anything definite on
it yet. To answer your questions, no the mountlist operate quite a bit
differently between 1.3 and 3.x. With 3.x, the method of mounting devices
is using a single entry for each device stored in the Devs/DosDrivers
drawer. Upon bootup, each of the files stored in that drawer are mounted
automatically. You will also find a new drawer called Storage that
contains all of the DosDriver's, Monitor drivers, etc. that are in this
temporary storage area. In the Storage/DosDrivers drawer you will find
most of the devices that you are accustomed to like RAD:, AUX:, PC0:, etc.
So what you need to do is move the icons from the Storage/DosDrivers to
the Devs/DosDrivers drawer for whatever devices you want automatically
mounted at bootup. If you don't need a RAD: device all the time, then keep
it in Storage and when you do need to mount it, just click on the icon.
You will also notice drawers in Storage such as DataTypes, Monitors,
Keymaps, etc. So if you want the Amiga to recognize all the DataTypes at
bootup, move the DataType icons from the Storage drawer to the appropriate
Devs drawer. Just to let you know, the mountlist is still supported under
3.x so if you have a mountlist entry for RAD:, then doing a MOUNT RAD:
should still work. Hope this wasn't too confusing and enjoy 3.0! BTW, I
would mail this to you but it's considered bad manners to Email messages
with information others can use and get benefit's from.
// John – (Flying via AutoPilot)
\X/