Partition Table Corruption - Need Fix
J. L. Stadelmann
7 has been previously installed, it marks it's partition as a FAT32.
If one then uses the Unixware 7 FDISK to examine the partition
information, the so-called "Windows" partition is tagged as "OTHER".
One can mark any partition active and either Unixware or Windows '98
will boot properly.
If, however, you install Unixware 7 on a drive already containing a
Windows '98 Partition, it correctly sees it, but after it creates it's
own non-overlapping partition, the Windows Partition now gets
marked as "DOS" and it becomes unbootable, and the Window's
DOS Fdisk reports it as "PRI DOS" System "UNKNOWN"
the UNKNOWN field is where Window's puts the FAT32
designation.
Because this partition is exactly the same size as before and
still contains the original file system, it would seem that there
should be a utility (either DOS or Unix) to return the original
parameters so that it remains useable. Just because MS decides
to implement a new file system which is not recognized by other
co-existing operating systems, one shouldn't be penalized. It
does seem that SCO is at fault here as well for not preserving
Partition Table data as it finds it. I don't appreciate having
to spend hours restoring it from tape every time I experiment with
another operating system. I was unsuccessful in getting a response
from SCO or from Micro$oft.
Does anybody know of a utility or work-around which would
permit restoring the Standare Windows FAT32 partition table info
after SCO stomps on it?
Thanks in advance for your assistance.
-jim
ARE Enterprises
(A...@XXXxnet.com) (please remove extra X's if replying via e-mail)
___________________________________
James Stadelmann
ARE Enterprises
XXXXs...@charlie.cns.iit.edu
Warren Young
>Does anybody know of a utility or work-around which would
>permit restoring the Standare Windows FAT32 partition table info
>after SCO stomps on it?
Yes, Linux fdisk should fix this. With it (and, TTBOMK no other tool,
except perhaps the *BSD equivalents) you can change the type ID of any
partition without changing anything else (i.e. it doesn't change the
data in the partition). It knows about virtually every partition ID
out there, including FAT32, though UnixWare vxfs appears to be
missing.
= Warren -- http://www.cyberport.com/~tangent/
D.Scharo
Your not specific on what the problem is, but I assume you can't boot
to win partion from boot prompt....get a disk geomitry error? ..
If so, boot to sco and try dparam -w and reboot, then bootos <part#>.
On Mon, 28 Jun 1999 19:25:00 GMT, tan...@cyberport.com (Warren Young)
wrote:
David Woolley
J. L. Stadelmann <orp...@CXXXxnet.com> wrote:
>own non-overlapping partition, the Windows Partition now gets
>marked as "DOS" and it becomes unbootable, and the Window's
>DOS Fdisk reports it as "PRI DOS" System "UNKNOWN"
>the UNKNOWN field is where Window's puts the FAT32
>designation.
>Does anybody know of a utility or work-around which would
>permit restoring the Standare Windows FAT32 partition table info
>after SCO stomps on it?
Use Linux fdisk, if it is just the partition type code that has changed.
This should be on all single disk Linux maintenance floppies and install
disks.
It may be possible to compile it for SCO but it will probably issue
IOCTLs which are unknown to SCO. Hopefully it will only do this after
it has made the change, so that you can just reboot to get the same
effect.
J. L. Stadelmann
>When Windows '98 is installed on a free area of a drive after Unixware
>7 has been previously installed, it marks it's partition as a FAT32.
>If one then uses the Unixware 7 FDISK to examine the partition
>information, the so-called "Windows" partition is tagged as "OTHER".
Warren wrote:
Yes, Linux fdisk should fix this. With it (and, TTBOMK no other tool,
except perhaps the *BSD equivalents) you can change the type ID of any
partition without changing anything else (i.e. it doesn't change the
data in the partition). It knows about virtually every partition ID
out there, including FAT32, though UnixWare vxfs appears to be
missing.
And David wrote:
Use Linux fdisk, if it is just the partition type code that has
changed. This should be on all single disk Linux maintenance floppies
and install disks.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thanks for your help, I never even thought of using Linux. However I
have one major concern about using the Linux fdisk - if, as Warren
wrote, it doesn't recognize Unixware vxfs file system types, it could
easily happen that it will fix Windoze and trash the Unix Partiions by
marking them differently just as Unixware did to the DOS parition.
I would feel much more courageous using this utility if somebody out
there has already tried in on a Unixware 7.xx system - not likely that
people would have both SCO and Linux on the same drive but somebody
might be doing OS comparisons on the same hardware.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As for Mr. Sahro's suggestion that I use 'dparam', I'm afraid it
doesn't appear to be a part of the Unixware distribution. But I am
not having disk geometry errors - it is FAT32 that is being clobbered.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I appreciate everyone's help even though I probably should have posted
it in comp.unix.unixware.misc and saved the non-unixware folks from
having to decipher my babble. I hope I can be assistance to others in
this group as well.
-jim
bint...@gmail.com
For More Info Visit: http://www.partitionundelete.com/restore-table.html