At 04:05 AM 7/30/2005 +, Mark wrote:
Well, the E000 message is repeatable on this box...
Thanks again for all of your help!
Well, we can check if your VDS vector is okay pretty easily. Try this with
the test EMM386 using VDS option. Don't type VOL first to crash things or
load UDMA.
Hi Johnson,
fix the problem of it not booting at this stage
Yes.
I remember the procedure clearly, it's really doesn't make sense to me
also.
Luckily some parts not yet arrive and I can still spend some time to
play with it, I'll break the RAID and try again, following your step.
And see
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,
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
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
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
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
At 09:32 PM 7/30/2005 +0200, Bernd Blaauw wrote:
1) harddisk present, but unpartitioned and not formatted
d 0:12C
U 0307:0145
U 0307:0180
output:
MOV BYTE PTR CS:[0084],00
CMP AL,02
JZ 01E1
You're not using test EMM386 is what that indicates. No test for AL equal
to zero, as was added.
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
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
Hi,
Johnson Lam escribió:
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
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,
On Sun, 31 Jul 2005 05:57:13 +0200, you wrote:
Hi Aitor,
The correct procedure should be:
1) Contact Brian and ask him if he still works on Free FDISK or not
(or someone else if Brian can't)
2) Vote here, keep Free DISK or switch to XFDISK
3) Someone have to examine XFDISK's source to
13 matches
Mail list logo
