Jan van Wijk wrote:
> Hello Damien,
>
> On Mon, 12 Dec 2016 20:01:47 +0100 Damien Guibouret wrote:
>
>>
>>Jan, something you can try (if you can easily perform this), you can change
>>the
>>kernel to use a not FAT32 one, as this check only exists in FAT32 specific
>>code.
>>You will see if
Hello Damien,
On Mon, 12 Dec 2016 20:01:47 +0100 Damien Guibouret wrote:
>
>
>Jan, something you can try (if you can easily perform this), you can change
>the
>kernel to use a not FAT32 one, as this check only exists in FAT32 specific
>code.
>You will see if it works or not (it is perhaps not
Eddie Anderson wrote:
> "Jan van Wijk" ecomstat...@dfsee.com wrote:
>
>
>>Message: 1
>>I have seen this problems numerous times over the last 10 years,
>>starting with the 1.0 kernel, then the 1.1, and I now just verified that
>>it still happens with the kernel that is in the 1.2 RC1 release.
>>
Hi Eddie,
On Sun, 11 Dec 2016 12:35:53 -0500 Eddie Anderson wrote:
>
>> Run chkdsk: Bad FAT I/O: 0x0001
>>
>> The message is repeated at least a dozen times, then the sector/block number
>> is incremented and another bunch or errors is repeated.
>>
>Thanks for your detailed
"Jan van Wijk" ecomstat...@dfsee.com wrote:
> Message: 1
> I have seen this problems numerous times over the last 10 years,
> starting with the 1.0 kernel, then the 1.1, and I now just verified that
> it still happens with the kernel that is in the 1.2 RC1 release.
>
>
> Description of the
Hi,
Resurrecting a old post here, since it still happens, and in some circumstances
is REALLY annoying, and can wast a lot of time ...
Background:
I have been using FreeDos for more then ten years in combination with
the DOS version of my Partitioning and Filesystem analysis tool 'DFSee'.
(and
