At 11:33 PM 7/23/2005 +, you wrote:
This may be a side effect of memory corruption with EMM386. In
fact, it appears to be a result of some interaction with EMM386.
I do not believe the hard disk in question is faulty and I do not
believe that it has non-standard parameters.
Doubtful. Ther
Michael Devore wrote:
At 04:01 PM 7/21/2005 -0500, I wrote:
When you invoke FDISK without arguments, it goes into the
Interactive_User_Interface() routine. That, in turn, asks about FAT32
support, via Ask_User_About_FAT32_Support() function. OK so far.
After that call -- without any furth
This may be a side effect of memory corruption with EMM386. In
fact, it appears to be a result of some interaction with EMM386.
I do not believe the hard disk in question is faulty and I do not
believe that it has non-standard parameters.
I do not believe the memory corruption is due to the hard
Hi,
Eric Auer escribió:
Please test if your devices can still be loaded with the new DEVLOAD
version (DEVLOAD allows you to load devices from the prompt which
otherwise would be loaded with DEVICE= or DEVICEHIGH=, but note that
UMB support is limited, memory drivers like HIMEM / EMM386 should no
Hi, I think you will be safe as you apply FDISK to NEW harddisks:
The problem is "only" that if you get a read error while reading
the existing partition scheme, our FDISK has the stupid strategy
to write a new empty partition table as "automatic solution".
Your new PCs should not show read errors
On Sat, 23 Jul 2005 15:29:04 +0100, you wrote:
Hi Gerry,
>It's just I have to build 30 PCs in coming weeks, plus some production
>servers, and plan to use FreeDOS FDISK to partition them. I was a bit
>worried reading about this bug, but all my hard drives are brand new, so
>should be OK.
If y
Hi Michael,
If it's always been there, why have more people not been affected?
Biggest mitigating factors are that if your hard drive behaves without
errors, is reasonably standard with expected parameters, and there is no
corruption of the program, the MBR write on startup won't occur.
Ah
On Sat, 23 Jul 2005 03:17:48 +0200 (MEST), you wrote:
Hi,
>XFDISK? I mean, XFDISK is open source. It only does not LOOK like
>the old MS DOS user interface, but hey, that was crap anyway...
The correct procedure should be:
1) Contact Brian and ask him if he still works on Free FDISK or not
2) V
