Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-lcc!ames!ncar!boulder!sunybcs!rutgers!att!occrsh!uokmax!ngorelic
From: ngorelic@uokmax.UUCP (Bamf)
Newsgroups: comp.sys.amiga
Subject: Re: WARP & DF1:
Message-ID: <2187@uokmax.UUCP>
Date: 6 Jan 89 00:06:57 GMT
References: <5372.AA5372@heimat>
Reply-To: ngorelic@uokmax.UUCP (Bamf)
Organization: Big Blue Box
Lines: 35

In article <5372.AA5372@heimat> sneakers@heimat.UUCP (Dan "Sneakers" Schein) writes:

    <On getting warp to use df1:>

>  Use a File Zap type of program and simply change each "DF0:" with a "DF1:".
>

    Nope, nice try though.  There are no occurances of DF0: in the executable.

    Probably, (and mind you, this is only my uneducated guess) because warp 
uses the trackdisk.device in some strange way, it's not coded as df0:, but in
more along the lines of a call with a number in it.  Something like:

     OpenDevice(something, unit_number, etc...)

  Where unit number is the drive number. (in this case 0)
I'd give a suggestion on how to fix it, but I'm afraid that's a little out 
of my league.  (Leo?  Matt?)

BTW: There is only ONE version of Warp (v1.1Z)   That's right, ONE!  all the 
rest of these are filezap's.  The source code was lost, and 1.1Z is it.
If you take a good look at the file lengths, and/or dig through them with an
editor, you'll see what I mean.

Bamf

You want it should sing too?          |          ngorelic@uokmax
<Never have figured out what goes here>    ...hpuecoa!bgphp1!ngorelic 
Dis-Claimer, Dat-Claimer, to look at  | anybody@tavern {as soon as it's up}
them, you'd never know the diff...    | "Beam me up scotty, we're outta beer"
-- 
You want it should sing too?          |          ngorelic@uokmax
<Never have figured out what goes here>    ...hpuecoa!bgphp1!ngorelic 
Dis-Claimer, Dat-Claimer, to look at  | anybody@tavern {as soon as it's up}
them, you'd never know the diff...    | "Beam me up scotty, we're outta beer"