Hi.

I have been running the USMDOS version of SlackWare 7 alongside Windoze 98.
As a Linux newbie this was the easiest solution for having both systems on
one machine.

I bought a book (Using Linux, fourth edition, published by QUE), which
contained CDs for Red Hat 5.1 and Caldera OpenLinux Lite 1.2.  As this book
covered non-UMSDOS versions only, I decided to take the plunge into a 'real'
(i.e, native) Linux installation.

The problem I have concerns my partitions.  The hard drive (partitioned
using the version of fdisk that came with Win98 Second Edition), is split up
as follows (according to SlackWare 7 fdisk):

Device    Boot Start End Blocks   ID System                (my comments)
/dev/hda1         2   20  143640  84 unknown               Suspend to disk
/dev/hda2   *    21  297 2094120   b win95 FAT32           Win98 drive c:
/dev/hda3       298  839 4097520   f win95 extended (LBA)
Partition 3 has different physical/logical endings:
Phys=(837,239,63) logical=(838,239,63)
/dev/hda5       298  574 2094088+  b win95 FAT32           Win98 drive d:
/dev/hda6       575  737 1232248+  b win95 FAT32           Win98 drive e:
/dev/hda7       738  755  136048+ 82 Linux Swap         ID mod. by linux
fdisk
/dev/hda8       756  839  635008+ 83 Linux Native       ID mod. by linux
fdisk

The problem is that the Red Hat fdisk does not recognise the extended
partition, viz.:
/dev/hda3       298  839 4097520   f unknown

It does not see anything in the extended partition.

Would it be safe to use the Red Hat 5.1 version of fdisk to change the
partition ID of /dev/hda3 from f (unknown) to 5 (extended)?  Would this blat
the contents of the drives within the extended partition from the Win98 side
(i.e, D: & E:), or worse, the whole lot, including C:?

Please help this clueless Linux newbie!

Regards,
Ozz.

Reply via email to