jwhitman@st-louis-emh2.army.mil (Jerry Whitman) (07/07/89)
Thanks to Simon Rademacher I now know why I cannot get PCPatch_II to work while others seem to have no trouble. It appears that PCPatch_II and track_disk:device expect to access DF1: to read the IBM 3.5 inch disk. Since I have a vanilla 2000HD I do not have a DF1: Therefore children, comes the question - Can I re-assign DF0: as DF1: and will this cure the problem, or does track_disk expect a 2nd drive to make this work? I would prefer a software method of re-assigning the drive, but if push comes to shove I can suffer through a hardware re-assignment providing I do not get crippled in other areas for lack of DF0: Any suggestions or enlightenment would be appreciated. Regards, Jerry
sjorr@rose.waterloo.edu (Stephen Orr) (07/07/89)
Two solutions are possible, the first and easiest is to assign DF1: to DF0: assign DF1: DF0: this will trick quite a few programs, alternatively, find a newer version of PC-Patch, the one I'm using support 360-720k formats and ASKs which drive to use. The commercial program Dos2Dos is even better for moving files back and forth though. - sjorr
ehoogerbeets@rose.waterloo.edu (Edwin Hoogerbeets) (07/08/89)
In article <14952@watdragon.waterloo.edu> 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. It can be found on Fish 111 or the older version on Fish 79,
or by ftp from uxe.cso.uiuc.edu. AssignDev clones the devicelist
entry, making "df1:" mean the same as "df0:" instead of making "df1:"
mean "My Volume:".
Edwincrs@cpsc6b.cpsc6a.att.com (Chris (The Home of the Killer Smiley) Seaman) (07/11/89)
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)
Ata@multics.radc.af.mil (John G. Ata) (07/12/89)
Date: 10 July 1989 17:36 edt
From: "Chris (The Home of the Killer Smiley" <crs at CPSC6B.CPSC6A.ATT.COM>
Subject: Re: Re-assigning DF0: to DF1:
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.
Have you tried mounting df2: as df1: as in the example mentioned? I
did a while ago and noticed that the system had a hard time tracking
df1: as the identical device as df2: Particularly, after mounting
df1:, if you referenced df2: again, the system would become extermely
confused and would end up in a guru... Additionally, the info command
would print some very interesting numbers.
--
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)
John G. Atalaurel@ziebmef.uucp (David Maxwell) (07/22/89)
In article <19494@louie.udel.EDU> Ata@multics.radc.af.mil (John G. Ata) writes: > > Date: 10 July 1989 17:36 edt > From: "Chris (The Home of the Killer Smiley" <crs at CPSC6B.CPSC6A.ATT.COM> > Subject: Re: Re-assigning DF0: to DF1: >Have you tried mounting df2: as df1: as in the example mentioned? I >did a while ago and noticed that the system had a hard time tracking >df1: as the identical device as df2: Particularly, after mounting >df1:, if you referenced df2: again, the system would become extermely >confused and would end up in a guru... Additionally, the info command >would print some very interesting numbers. > -- > 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) > John G. Ata This is somewhat similar to a problem I just discovered. I just (today) purchased an AIR drive (external 3.5 floppy) and was setting it up as df1: Well, a funny thing happened on the way to mountlist and an assign showed me that I had a df2: (I don't) before I executed a 'mount df1:' I deleted df2: s setup from my mountlist and put in a df1: df1 now mounts fine, but df2: is also my external drive. (I have a task held error behind my Access screen to prove it!) it as you say, it isn't being tracked nicely. I put some assigns in my startup to show me WHEN df2: appears on the device list (at the end of 'assign') and I now know it's somewhere in this... BindDrivers Assign WB: sys: IF EXISTS sys:s/JH0 echo "etc..." Wait 5 DJMount my assign follows there and shows df2: as mounted. BindDrivers wouldn't do it (would it?) Assign wouldn't, if, echo, and wait wouldn't, Would DJMount mount df2: ? My setup is an A2000, 33Meg HardDrive (Janus) Bridgeboard, one internal floppy 3.5, one internal 5.25, and the new external. Anyone have a suggestion as to how I stop it from mounting df2: ? David Maxwell laurel@ziebmef