Amiga.org

Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: macto on July 30, 2004, 03:41:49 PM

Title: Assigning Devs: etc.
Post by: macto on July 30, 2004, 03:41:49 PM

I'm trying to setup user Devs:, C:, etc. assigns.  To do so, I've added lines like:

ASSIGN Devs: WB2:MyDevs ADD

To my user-startup file.  According to the manual and various websites (such as this one: http://www.amigarealm.com/archives/thisoldworkbench/html/towb23.html) this should be possible.  Then I do:

ASSIGN

And surely enough the expected paths are displayed.  Then I do:

DIR Devs:

or

LIST Devs:

And I only see the files in one of the paths (namely WB2:Devs, which was assigned by the system.)  I go through the same thing for C: and have the same symptoms.  Fine.

Now I try to do something with these new paths.  Stuff in the system and user C: assign seem to work.  The stuff in the Devs: assign doesn't seem to work.  Is there anything unique about Devs: which would explain why this doesn't work, or should I be looking for the problem elsewhere.

Title: Re: Assigning Devs: etc.
Post by: Piru on July 30, 2004, 03:57:54 PM

@macto

Applications need to support multiassigns to take advantage of other than the first assign destination. Shell does this for C:, ramlib does this for DEVS: (OpenDevice) and LIBS: (OpenLibrary).

Dir, List etc don't support multiassigns, only the first assign destination is listed.

Title: Re: Assigning Devs: etc.
Post by: macto on July 30, 2004, 04:14:17 PM

Quote

Piru wrote:
Applications need to support multiassigns to take advantage of other than the first assign destination. Shell does this for C:, ramlib does this for DEVS: (OpenDevice) and LIBS: (OpenLibrary).

Thank-you for that bit.  Now was there any point in the past when ramlib didn't support multiple assigns for Devs: (eg. I'm using Workbench 2.04)?

Title: Re: Assigning Devs: etc.
Post by: Daedalus on July 30, 2004, 04:19:51 PM

Yes, the Assign command with the ADD keyword will work in this case, but as Piru said, it needs to be supported by the application trying to access devs:whatever. IIRC VNC supports this as an option you can enable (TrueMultiAssigns I think), then typing dir devs: will list all the files. But as ramlib supports multiassigns, it will search all assigned paths when any application actually tries to open a file in DEVS: through the normal methods. Beware though, it will stop looking when it finds the first version, not the newest version, so if you have a copy in both locations, it'll only use the one in SYS:Devs/ and not the one in SYS:MyDevs/.

If you only want to use SYS:MyDevs/ as your Devs drawer (though I can't think why you'd do that), you can use "Assign DEVS: DISMOUNT" and then "Assign DEVS: WB2:MyDevs" to reassign it.

Title: Re: Assigning Devs: etc.
Post by: Piru on July 30, 2004, 05:05:54 PM

Quote

If you only want to use SYS:MyDevs/ as your Devs drawer (though I can't think why you'd do that), you can use "Assign DEVS: DISMOUNT" and then "Assign DEVS: WB2:MyDevs" to reassign it.

That would be "Assign DEVS: REMOVE" not "Assign DEVS: DISMOUNT".

Title: Re: Assigning Devs: etc.
Post by: Piru on July 30, 2004, 05:06:55 PM

Quote

Thank-you for that bit. Now was there any point in the past when ramlib didn't support multiple assigns for Devs: (eg. I'm using Workbench 2.04)?

AmigaOS 2.x supports multiassigns for ramlib.

Title: Re: Assigning Devs: etc.
Post by: Daedalus on August 01, 2004, 11:13:31 PM

Quote

That would be "Assign DEVS: REMOVE" not "Assign DEVS: DISMOUNT".

Oops, Apologies, that is indeed correct. Be careful with the Dismount option, it's for removing actual devices or volumes, not assigns...

/me goes back to sleep...