Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!agate!ucbvax!mtxinu!rtech!cpsc6a!cpsc6b!crs
From: crs@cpsc6b.cpsc6a.att.com (Chris (The Home of the Killer Smiley) Seaman)
Newsgroups: comp.sys.amiga
Subject: Re: Re-assigning DF0: to DF1:
Keywords: simple mountlist solution
Message-ID: <570@cpsc6b.cpsc6a.att.com>
Date: 10 Jul 89 21:36:12 GMT
References: <19138@louie.udel.EDU> <14952@watdragon.waterloo.edu> <14982@watdragon.waterloo.edu>
Distribution: na
Organization: AT&T (CPSC), Oakland, CA
Lines: 31

ehoogerbeets@rose.waterloo.edu (Edwin Hoogerbeets) writes:
< sjorr@rose.waterloo.edu (Stephen Orr) writes:
< % Two solutions are possible, the first and easiest is to assign DF1: to
< % DF0:
< % 	assign DF1: DF0:
< % this will trick quite a few programs, 
< 
< Well, what happens if you change the disk in df0: to a different
< AmigaDOS disk? A requester will come up asking to insert volume "My Old
< Volume:".  Or if the disk in df0: is actually not in Amiga SFS or FFS
< format? The assign simply will not work.
< 
< What actually is needed is AssignDev by Phillip Lindsay and Olaf
< Seibert.  AssignDev clones the devicelist
< entry, making "df1:" mean the same as "df0:" instead of making "df1:"
< mean "My Volume:".
< 
< Edwin

Why would AssignDev be necessary?  Wouldn't it work to add a Mountlist
entry for 'DF1:' that references the same device as DF0:?  This could
then be mounted, and used as an independent device, much as the example
from the 1.3 Mountlist for mounting DF2: as DF1:.  If I am missing something,
then I deserve some serious flaming :-), but it seems to be a simple
solution.

-- 
Chris (Insert phrase here) Seaman |    ___-/^\-___      bIyIn nI' je chep.
crs@cpsc6a.att.com <or>           |  //__--\O/--__\\       (Look it up
...!att!cpsc6a!crs                | //             \\        in your
The Home of the Killer Smiley     | `\             /'   Klingon Dictionary)