From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <530210B9.3070802@mail.com> Date: Mon, 17 Feb 2014 14:38:01 +0100 From: Adriano Verardo User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:27.0) Gecko/20100101 Firefox/27.0 SeaMonkey/2.24 MIME-Version: 1.0 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> References: <5300E0E2.60304@mail.com> <53010006.60600@mail.com> <5301017F.6030707@mail.com> <7f7686c73d65e654125113a970537326@mikro.quanstro.net> <53011910.6010203@mail.com> <20140216223312.7af86e0101f6ce4b57f6086a@student.gsu.edu> <5301EC37.6080303@mail.com> <49c64b96ff76e6646520d7b886084205@mikro.quanstro.net> In-Reply-To: <49c64b96ff76e6646520d7b886084205@mikro.quanstro.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [9fans] usbinstamd64 on Dell 3010 Topicbox-Message-UUID: bb1103f4-ead8-11e9-9d60-3106f5b1d025 erik quanstrom ha scritto: >> final result is exactly the same. > i blame the usb driver. i hope to get some time to look at it today. > > - erik > > I'm observing that, with different fresh usb keys and writing tools, the error is (almost) always the same. A long long time ago I had a similar behaviour with the driver of a DEC-RL-02-like disk, due to a my mistake in the calculus of physical sector/track. That driver worked fine for 1+ years till the first access to sectors over a given (I don't remember ..) address. adriano