Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!sugar!karl
From: karl@sugar.hackercorp.com (Karl Lehenbauer)
Newsgroups: comp.sys.amiga
Subject: Re: Nib 2.0 arrives!
Message-ID: <5151@sugar.hackercorp.com>
Date: 15 Feb 90 01:07:05 GMT
References: <4193@jhunix.HCF.JHU.EDU> <2562@gmu90x.gmu.edu> <4218@jhunix.HCF.JHU.EDU>
Reply-To: karl@sugar.hackercorp.com (Karl Lehenbauer)
Organization: Sugar Land Unix - Houston
Lines: 21

In article <4218@jhunix.HCF.JHU.EDU> barrett@jhunix.UUCP (Dan Barrett) writes:
>In article <2562@gmu90x.gmu.edu> jbaker@gmu90x.UUCP (John Baker) writes:
>>When an exact copy of a disk is made, and both disks are inserted at once,
>>AmigaDOS gets the two disks confused.  If you then eject them, the system
>>will generally crash.  This happens with most commercial disk copiers....

>	It doesn't happen with Marauder II, nor AmigaDOS DiskCopy.
>Therefore, there must be a way around this.

It was sort of said but I think I'll make it more clear, that in its default
copying mode, Marauder II *does not* make a verbatim copy of the disk.  Like
diskcopy, Marauder puts a new timestamp out on the VTOC (or whatever CA
calls it) of the new disk.

In verbatim mode, though, Marauder does not write a new timestamp, and 
AmigaDOS will then be confused when both disks are inserted.

-- 
-- uunet!sugar!karl	"As long as there is a legion of superheros, all else
--			 can surely be made right." -- Sensor Girl
-- Usenet access: (713) 438-5018