RE: Question about writing to 1541

From: Baltissen, GJPAA (Ruud) (ruud.baltissen_at_abp.nl)
Date: 2005-05-06 13:12:34

Hallo Spiro,


> With that compare, I discovered that the last sector written
> was always bad. Doing some more analyses, I found out that it
> was always the last 2 bytes which were wrong.
 +
Silverdream:
>> You mean the two padding bytes, right?
>
> Exactly.

Ahhh, that clears the matter on my behalf (most probably a misunderstanding
from my side). I thought you were mentioning the _data_ bytes, the last two
of the 325 GCR bytes. In this case I only can say: forget the matter, we
have seen enough conflicting things already and this is just another one.

Regarding the analyse of the gap between header and data: 'hut ab'!


--
     ___
    / __|__
   / /  |_/     Groetjes, Ruud
   \ \__|_\
    \___|       URL: Ruud.C64.org
















=====DISCLAIMER=================================================================

De informatie in dit e-mailbericht is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Wanneer u dit bericht per abuis ontvangt, verzoeken wij u contact op te nemen met de afzender per kerende e-mail. Verder verzoeken wij u in dat geval dit e-mailbericht te vernietigen en de inhoud ervan aan niemand openbaar te maken. Wij aanvaarden geen aansprakelijkheid voor onjuiste, onvolledige dan wel ontijdige overbrenging van de inhoud van een verzonden e-mailbericht, noch voor daarbij overgebrachte virussen.

The information contained in this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you have received it in error, please contact the sender immediately by return e-mail; please delete in this case the e-mail and do not disclose its contents to any person. We don't accept liability for any errors, omissions, delays of receipt or viruses in the contents of this message which arise as a result of e-mail transmission.

       Message was sent through the cbm-hackers mailing list

Archive generated by hypermail pre-2.1.8.