John Aldrich wrote:
> On Sun, 20 Aug 2000, Jerry Human wrote:
> > It seems to me that Win95B will occasionally write an id to the root
> > partition of the drive even though it only has access to the fourth
> > partition and that id corrupts the RH boot. How can this be avoided? The
> > problem only occurs when booting RH after working in Win95B. Once RH
> > boots, the box can be started in RH any number of times without problem.
> > No degrading of the RH boot was noticed since the original ATA/66
> > problem. This problem just happened, no hardware/software settings were
> > changed for Win95B or RH.
> >
> How did you partition the hard drive? Did you partition it
> with a Dos/Windows based util? If so, then Windows has
> probably become aware of it. What is recommended is to
> leave the linux space unpartitioned and then when you
> install, partition it using the linux fdisk or disk druid.
> That way, Windows is unaware that the drive space even
> exists.
Actually, I have a small maintenance install of RH 6.2 on hda4. The install
that no longer boots is on a new WD 10.2 gig I installed just for RH, which is
hdc. I used the hda4 RH to partition the new drive with four primary
partitions. hdc1 is 3 gig for RH 6.2, hdc2 is 100 meg for swap, hdc3 is ext2
space for downloads and data files and hdc4 is vfat for Win95B downloads and
data files. RH install formatted (installed file system) hdc1 and hdc2, the
new install was used to format hdc3 and hdc4 was formatted vfat by Win95B.
Does this help? At this point, I have to reinstall RH on hdc1 but that won't
stop the corruption.
Thank you.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
