Hi Michael,
My main point was that the FDISK bug may have been _triggered_ by EMM386
with VDS, and that if he hadn't been running EMM386 his FDISK tests
would not have caused a bad partition table. You were saying this:
Oh good grief. EMM386 doesn't have the code or capability to mess
with
At 01:08 AM 7/31/2005 +0100, Gerry Hickman wrote:
Oh good grief. EMM386 doesn't have the code or capability to mess with
disk partitions. Period.
But if drive geometry is being misreported or misunderstood under EMM386
with VDS (which appears to be the case), then my guess is that it would
On Sat, 30 Jul 2005 17:43:04 +0100, you wrote:
Hi Gerry,
>Old OSs, including DOS, Win3.xx and NT, were not aware of this extension
>and therefore always need an overlay program to use large hard drives .
That means Win98 FDISK ignore the "INT13 extension".
Thanks for the information.
Rgds,
Hi Michael,
Can you clarify; when your partition table became damaged, were you
running EMM386 at the time, and have you tried it without?
Oh good grief. EMM386 doesn't have the code or capability to mess with
disk partitions. Period.
But if drive geometry is being misreported or misunder
At 08:23 PM 7/30/2005 +0100, Gerry Hickman wrote:
Ah, yes, ... :-) Try emm386 without the VDS argument and under no
circumstances run FreeDOS FDISK unless you want to risk an erased
partition table.
Can you clarify; when your partition table became damaged, were you
running EMM386 at the t
Ah, yes, ... :-) Try emm386 without the VDS argument
and under no circumstances run FreeDOS FDISK unless
you want to risk an erased partition table.
OK I ran the tests again, after taking out VDS everything is working
normally, FDISK /INFO reports the correct partition sizes and luckily my
Hi Gerry:
Yes, I was running emm386. However, FDISK erased my
(and at least one other) partition table without any
prompt or request at all when only requested to
examine the table. It's too risky to run the program at
all until that bug is addressed (IMHO). I believe there
is a development ver
Hi Mark
Ah, yes, ... :-) Try emm386 without the VDS argument
and under no circumstances run FreeDOS FDISK unless
you want to risk an erased partition table.
Can you clarify; when your partition table became damaged, were you
running EMM386 at the time, and have you tried it without? Maybe
Hi Gerry:
Ah, yes, ... :-) Try emm386 without the VDS argument
and under no circumstances run FreeDOS FDISK unless
you want to risk an erased partition table.
Thanks for reporting this. Let us know what happens without
the VDS argument to EMM386!
Mark
> Hi,
>
> I tried some rough tests t
Gerry Hickman wrote:
In an eariler post I said I'd seen drive sizes reported as 8Gb with SCSI
when the drives are actually much bigger. I thought it was related to
not using a SCSI driver and BIOS (INT13) reporting wrong size, and Eric
said it wasn't. I think Eric is right, but my BIOS has bee
Hi,
I tried some rough tests today with BIOS, SCSI and TUNS. Here's are some
results.
In an eariler post I said I'd seen drive sizes reported as 8Gb with SCSI
when the drives are actually much bigger. I thought it was related to
not using a SCSI driver and BIOS (INT13) reporting wrong size,
11 matches
Mail list logo
