[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Brutal Deluxe's holidays project 3: EDD/SST and NIB images



Nick Westgate wrote:
On Aug 13, 11:21 am, "Michael J. Mahon" <mjma...@aol.com> wrote:
In fact, it's necessary to do it later, since only the actual execution
of the program can specify which nibbles of which "tracks" are actually
read.

That depends on whether you have already traced/cracked (or have
params) for the disk you're "ripping".

Of course, maybe it's best to hard-code the options: all tracks (up to
40!?) at step .25 synchronized. Send the rip to the experts for
editing, and they'll keep the original rip archived forever - just in
case!

Actually, RIP is not a bad filetype name for this format.
Hopefully all old software can be peacefully laid to rest!

That actually gets precisely to the point I was making--unless the
program has been *completely* reverse-engineered, you can never be
sure that it doesn't depend on something peculiar on the disk that
just hasn't yet been encountered.  ;-)

...and then there are the issues of noting all the "weak" or
unrecorded bits on the disk, as opposed to what a couple of
reads might come up with.

-michael

NadaNet 3.0 for Apple II parallel computing!
Home page:  http://home.comcast.net/~mjmahon/

"The wastebasket is our most important design
tool--and it's seriously underused."