|
grub.conf is just a text file. Just open it in a text editor:
vi /boot/grub/grub.conf Then change the valuse you need so that the windows system is referenced properly. Best to make a backup copy first ;): cp /boot/grub/grub.conf /boot/grub/grub.conf.bak |
The text editors are both denying me access to grub.conf.
|
To change to the root account, open an x terminal and use these commands from your user account. Note the change in the prompt.
Code:
[fancy@tinwhistle fancy]$ su - |
Thanks, between fancypiper and david_ross I finally got in there.
BUT I must have entered something wrong. Here is what I have. ----------------------------------------------------------------- title Red Hat Linux (2.4.18-14) root (hd0,0) Kernal /vmlinuz-2.4.18-14 ro root=LABEL=/ initrd /initrd-2.4.18-14.img title Windows98 rootnoverify (hd1,0) map (hd1))hd0) map (hd0)(hd1) makeactive chainloader+1 ------------------------------------------------ originally after the Linux part there was a Dos loader which I removed. Linux is on hda, Windows is on hdc Am I almost there? |
That looks like your /boot/grub/grub.conf file. Use the code tags (button labled #) to post commands, config files, etc.
Installing a bootloader Multiboot with GRUB Mini-HOWTO For your reference, here is my partitioning: Code:
[fancy@tinwhistle fancy]$ su -Code:
# Celeron 850 tinwhistle /etc/fstab/fileCode:
# Celeron Coppermine 850 tinwhistle box /boot/grub/grub.conf file |
Your map command has "))" and it should have ")("
|
Thanks again, especially to fancypiper and david_ross.
I finally got through to Win98. I was leaving out spaces (hd1) (here) (hd0) (hd0) (here) (hd1) chainloader (and here) +1 Thanks again RAL :D |
Quote:
if you have a hard drive on the same cable as a cdrom drive, and put a cdrom in the drive that the drive can't read, your system will slow to a crawl, because the cdrom will keep getting that bus locked to try to read things it can't and will hang up everything. whatever is sharing a cable, cannot both be transferring data on the cable at the same time. they take turns. the master should be at the end of the cable, with the slave in the middle, but it will usually work both ways with the old style 40 pin cable. lots of drives will not work well together at top speed. i've often had to slow down a drive a dma mode or 2 when it has another drive on the cable with it, to get it to work right. luckily with most drives it makes little difference between the top 2 speeds the drive will run at. some basically run the same speed at udma 66 or 100. it's also possible to run both drives in cable select mode. it's called cable select, because the cable is what decides which drive is the master or slave. you can buy or alter your own cable for this purpose. in this situation both drives are set to cable select, and the special cable with one of the wires to the master cut, and, the drives get set master or slave by where they are on the cable. this can be handy for moving drives around without having to change jumpers. i can't remember which pin to cut though, but i'm sure you could find it on the web. also, lots of cdrom drives will mess each other up being on the cable with each other. i'll sometimes go thru a stack of different brands and speeds of cdrom drives and burners trying to find 2 that will work together perfectly on a machine, with both in dma mode. hopefully the new serial drives will get rid of this madness. ( while probably introducing a new madness of their own). i just found some newer information on CS, that corrects a few errors on my part. it's good info. http://www.pcguide.com/ref/hdd/if/ide/confCS-c.html |
| All times are GMT -5. The time now is 06:09 AM. |