Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!eecae!netnews.upenn.edu!rutgers!tut.cis.ohio-state.edu!osu-cis!att!twitch!anuck!ksp
From: ksp@anuck.UUCP (p.s.kasten)
Newsgroups: comp.sys.amiga
Subject: Re: Project D Copier
Summary: Project D Hanging
Message-ID: <1477@anuck.UUCP>
Date: 13 Feb 89 14:22:24 GMT
References: <9185@bloom-beacon.MIT.EDU> <14528@cup.portal.com>
Organization: AT&T Bell Labs, Andover Ma.
Lines: 13


It is imperative that, once you've made a copy of a disk with Project D,
you remove at least one of the two disks when the copy is finished.  Project
D, when it makes a backup, puts the identical creation date and time stamp
on the backup and the master (unlike Marauder and Rawcopy).  Apparantly
Exec doesn't like two identical disks, and hangs if it detects them.
Also, Project D validates the disks as soon as it can (allowing the disk
drives to be used by other programs) instead of forcing the drives to be
BUSY.

phil kasten
AT&T Bell Labs
att!mvuxj!ksp