Hello -
I was briefly trying to help Dana out Saturday evening. However, there was
trouble with the CD that he had burned, and I needed to leave, so we
didn't get very far.
Some things that I noticed:
Initially, before the CD went batty, the paritioner *did* see both hard
drives. We managed to partition the second hard drive, and were trying to
format the swap partition when the CD died.
Later, while briefly checking to see if we could do an FTP install instead
of a CD install, the boot disk was having trouble with not being able to
see both drives. The partitioning that had been done before the CD died
was still there, on the 8G drive, but the windows drive did not show up. I
decided that I was going to stop right there, because I wasn't sure what
sort of problems the partitioner's not being able to see the windows drive
would pose (in addition to lilo not knowing about that drive, of course).
Apparently I didn't explain the reason for my reluctance to continue well
enough, considering that Dana later wrote another CD (correctly,
apparently), and attempted the install on his own. Seems as if the
partioner's inability to see the drive still occured.
I do *not* think that Windows was overwritten, assuming that the behaviors
that I saw were continuing to occur. I will likely have a chance to take a
look at his machine around 8p tonight, and will see what I can find out.
I'll attempt to see if changing the lilo.conf will help, but suspect that
the iniability to see the drive will still be happening. I've not run
into this specific problem before, so am unsure what else to try after
that. If nothing else, killing lilo would prolly bring Windows back,
assuming that adding in those lines to lilo doesn't bring it back.
I'm somewhat concerned about the fact that the partitioner (the graphical
one that comes with RedHat - the name escapes me at the moment) suddenly
decided that it couldn't see the windows drive - it was complaining about
something along the lines of not being able to see 'temp/hdd' - he doesn't
*have* four hard drives.
It was *definately* seeing the drive he was intending to use for Linux
when I was there, and not the windows drive. Of that I am completely sure.
But again, I wasn't there this last time.
I've half a mind to suggest that he use fdisk next time, but I seem to
recall that changing the partitioners was the first thing I checked -
neither of them could see the windows partition the second time we tried
playing with it.
I doubt he did a backup; I'm somewhat ill, and didn't think to suggest
that Saturday. I don't generally (I'm not sure that 'generally' is
applicable when I've installed on my own machine twice...) do them because
I keep all my important stuff on my (regularly backed up) school account.
Anyway. I'll look at it tonight or Weds night, and see what I can do.
Suzanne
--
[EMAIL PROTECTED] http://pubpages.unh.edu/~shillman
Student Engineer University of New Hampshire
(603) 862-4626 RCC/IOL, ATM Consortium
Law of programming: Constants aren't, variables won't.
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
