Only from ME :) Chris
----- Original Message ----- From: Aley Keprt <[EMAIL PROTECTED]> To: <sam-users@nvg.ntnu.no> Sent: 15 April 1999 15:07 Subject: E-Copy 3 (was: Re: SimCoupe & protected disks) > > Where can I get E-Copy 3? > > ---------------------------------------------------------------- > Aley [eili] Keprt - student, programmer (multimedia soft. etc.) > phone: +420-68-538 70 35 > e-mail: [EMAIL PROTECTED] *** http://get.to/aley > ---------------------------------------------------------------- > > > > > From: Aley Keprt <[EMAIL PROTECTED]> > > > > Can anyone recommend any demos or games that have use fairly > > non-standard > > > > disk formats? > > > > > > I can only recommend not to do this! > > > If soomeone made a protection, he probably wanted us not to copy these > > > diskettes. I'm affraid about copyright laws. > > > > But if you already own the software that has the protection on it, surely > > it's legal? > > > > (by the way, that was rhetorical - it is very much legal) > > > > > In addition, it is very problematic to use nonstandard formats under > > > Win32. Also, some features of Sam's drive are not compatible with pc's > > > drive. it simply cannot handle sectors other than 4 statndard sizes. > > > Since Sam can physically hanle much more sector sizes, it is almost > > > unpossible to use protected disks on pc. > > > > I don't believe that's the main problem; the VL1772-02 can only handle 4 > > sector sizes -- 128,256,512 and 1024 bytes. However, it can mix & match > > sector sizes on one track, and also can spoof address blocks; so that is > > more problematic. > > > > A program written on a SAM should be able to copy these disks though. > > > > > if we would copy these disks to an image, we would need a special > software > > > for the regular sam. this is another complication. > > > > Already got it - it's called E-Copy 3. -- minor modifications to dump to > > RAM/a PC disk/a specially formatted SAM disk would be easy. > > > > Simon Cooke > > (The views of this poster are his and his alone, and may or may not > reflect > > the views of the Microsoft Corporation). > > > > ps. NSFMSFT == Not Speaking For MicroSoFT. [force of habit, I guess] > > > > > >
