al@genrad.UUCP (Al Gudaitis) (05/23/84)
Could all the people who have reported trouble with the @0: command please
give some more information on the type of files they had on the disks when
they had problems? Were the files of type: program, sequential, relative,
and/or random? I have disks with just 'prg' and 'seq' files on them and I
have never had any problems with the save and replace command (at least with
about 20-30 uses of the command). Could the problem be related to the vintage
of disk drive used? My drive has that 'whacking' sound whenever I perform a
disk initialization but I have heard rumors that current models no longer do
that. (Sounds like a great idea if the sound is indeed the by-product of a
head de-alignment process.)
Al Gudaitis
decvax!genrad!al
linus!genrad!alrwh@aesat.UUCP (Russell Herman) (05/24/84)
I've encountered the problem with simple disks of <20 files, all type prg.
Perhaps someone with the ABACUS-published book on the 1541 can throw some
light on whether there is some readily identifiable state-of-the-disk and
characteristics-of-the-file under which overwrites may trash the disk so that
"@" mode can be used some of the time.
BTW, I have the ABACUS book with the C-64 ROM disassembly. It's worth the
price for the listing alone, although there do seem to be a fair number
of errors in the introductory chapters and examples. The ROM listings are
probably the only way to understand how the beastie really works.
Commenting is quite lucid except for a few areas where nearly totally omitted!
--
______ Russ Herman
/ \ {allegra,ihnp4,linus,decvax}!utzoo!aesat!rwh
@( ? ? )@
( || ) The opinions above are strictly personal, and
( \__/ ) do not reflect those of my employer (or even
\____/ possibly myself an hour from now.)