btw, you mentioned earlier you were multibooting as linux didn't have
drivers for your printer. Which printer are you running?
Brandon Dorman wrote:
> Thanks Frank,
>
> I think I will have to completely overhaul my system. :-( I
> can't afford the downtime right now due to a new seme
Thanks Frank,
I think I
will have to completely overhaul my system. :-( I can't afford the
downtime right now due to a new semester starting but should be able to
get to it this weekend, for now windows is working fine if not my
preferred environment. Would it be ok if I did this:
HDA
(8g
If it's an option I would strongly recommend starting over with the system.
It sounds like there are many more problems than could be easily dealt with
in a timely manner.
Here's what I've done in the past. This has worked for 98SE, NT, 2000 and
XP systems.
Install Windows on your C: drive.
It appears the problem is worse than I thought. I rebooted after posting
that post and Linux came up with all kinds of filesystem erros, the whole,
"you have 5 seconds to perform a manual file system check" after which,
finding duplicate clusters, it scanned with something like, "Pass A1, B1,"
I'm just starting to mess around with grub. Not very familiar with it
(yet). Here is something that could help.
I had an instance where I was multibooting with Redhat 7.1 and Windoze
XP. Originally I had Windows 98SE and had enough. From Linux I deleted
the windows partition then rebooted
g of the windows disk which Linux should call "/dev/hda"
and which you called "HD1".
You should also include *ALL* of your grub.conf file, not just what you
consider the "pertinent part".
Offhand, it looks like the "Windows" stuff is pointing at the wrong d
Clarification:
In
title Windows
> rootnoverify (hd1,4)
> /dev/hda1
> chainloader +1
the part about /dev/hda1` is me guessing. But anyway my windows
partition is /dev/hde1 anyway, in case that can help. Please I realize
that e-mail is kinda unclear, I'm a bit panicked h
