Re: .nib Images to real Apple disks

["John B. Matthews" <nospam@nospam.invalid>]

In article <O7CdnfOClfSwfl3WnZ2dnUVZ8m2dnZ2d@giganews.com>,
 "Bill Garber" <willy46pa@garberstreet.com> wrote:

> "Toinet" <antoine.vignau@laposte.net> wrote in message 
> 710be06c-b3f5-4ad9-ad3a-097199d20210@u22g2000yqf.googlegroups.com">news:710be06c-b3f5-4ad9-ad3a-097199d20210@u22g2000yqf.googlegroups.com...
> On 10 avr, 10:55, AppleCPM <a...@wilserv.com> wrote:
> >> Hi!
> >>
> >> On Apr 9, 11:22 pm, Antoine wrote:
> >> <--- snip --->
> >>
> >> > This Apple program is not protected nor the disk. The .NIB image is bad:
> >> > - two sectors of track 3 cannot be read
> >> > - one sector of track 4 cannot be read
> >> > The NIB image shows that the disk uses standard markers D5AA96/DEAA
> >> > and D5AAAD/DEAA
> >>
> >> You say that there are sectors on tracks 3 and 4 that cannot be
> >> read. By what program? AppleWin has no problem accessing
> >> "FORT2fixed.nib". My analysis of that image file says that track 3,
> >> sectors 9 and 13 and track 4, sector 0 have epilogue bytes $DEAB, not
> >> $DEAA.
> >>
> >> Willi
> >
> > applewin and sweet16 were the emulators. disk fixer 4,
> > locksmith 6.3 and advanced demuffin were the a2 programs.
> >
> > i don't know what was fixed in that nibble image but from my
> > experience, i would say the image is bad and the disk is not
> > copy-protected. at the end, the program cannot be used.
> >
> > antoine
> 
> I know one thing. Ciderpress was unable to copy 'SYSTEM.COMPILER'
> to the clipboard. All other files were able to be copied. I don't
> know if it can be copied directly via other means.

This accords with my recollection of one 512-byte block (two 256-byte 
sectors) containing the compiler on FORT2: being copy resistant when I 
bought the original release. I don't see how sectors 9 and 13 could be 
part of the same block, but track 4, sector 0 would be the first half of 
block 33.

-- 
John B. Matthews
trashgod at gmail dot com
<http://sites.google.com/site/drjohnbmatthews>