<< Previous Message <<
Date: | Mon, 15 Feb 1999 23:32:15 PST |
From: | Peter Skye <pskye@peterskye.com > |
Reply-To: | scoug-help@scoug.com |
To: | scoug-help@scoug.com |
Subject: | SCOUG-Help: Corrupted Partition Table |
Content Type: text/plain
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
> Peter Skye wrote:
Lists [Sheridan] wrote:
P.M. Version 3.03 has the above menu selections. :)
> For disk #2, all it says is: "0 MB Partition table error #116 found".
Okay, things are looking a little better. :)
Look in your Graham Utilities pink manual at DiskEdit (see p. 149 and p.
Run DiskEdit and print the screen, so you have a printout of all the
Now post what you just printed out so we can see what part of the
(Tech note to readers: I know Sheridan has DiskEdit 'cause I talked to
=====================================================
To unsubscribe from this list, send an email message
For problems, contact the list owner at
=====================================================
Return to [ 15 |
February |
1999 ]
> > Can you boot directly to either your OS/2 or Windows partition? Use
> > your Partition Magic to make the desired partition "Active", then boot
> > your machine. The motherboard BIOS looks at the primary partitions (on
> > all drives) and boots to the first one it finds that's marked "Active".
> > Use Partition Magic's "Advanced .. Set Active" option (I think
> No I can't. FDISK will only allow 'delete partition' and my edition of
> PartitionMagic doesn't have any such option (it's either too old or the OS/2 text
> version (pqmqgict) which I have to use booting from floppies does not include it in
> the menu).
> Error #116 is: "Partition table begin and start inconsistant".
...
> FDISK does report a size for all three unreachable partitions. The reported sizes
> are close to what I set but I don't know if the numbers are exactly correct. If
> they are how would I patch the partition table or verify the values as Steve
> suggested?
359), and especially the section "Edit Partition Table" beginning on p.
359 and going to the top of p. 364. (And see the first paragraph on p.
150 about editing the partition table.)
partition table values. Then exit DiskEdit.
partition table might be scrambled.
him on the phone. The values in the partition table don't all start on
byte boundaries, which makes hex editing of it sorta difficult.
Graham's DiskEdit allows editing of the ten fields in each of the four
partition table entries, and you edit the numeric values of the fields,
not the hex values of the bytes.)
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
"rollin@scoug.com".
<< Previous Message <<