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. I usually partition a 20 Gig drive with a 3 or 4 Gig C: drive. If installing XP anything smaller will be difficult as XP "can" take up to 1.6 Gigs of disk space from a fresh install (I've seen this on a couple of systems). After it's finished go ahead and install Linux. Usually I make a boot partition of around 40 megs then whatever you want after that for root and other junk. I believe grub doesn't suffer from the 1024 cylinder problems lilo usually does so this should work out (comments on grub?).
Haven't tried 7.2 seriously yet. I have a test system running with ext3. Very impressive so far :-)
Good Luck!
Frank
Brandon Dorman wrote:
[EMAIL PROTECTED]"> 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," until I pressed Control-C which I shouldn't have and it ended up giving a message something like, "initd was done repeatedly too much" then I restarted. I remembered that I had used Partition Magic's bootmagic in the past and put in that rescue disk, and was able to boot into windows, where I am now. So I can't go back into linux just yet to get the rest of fdisk -I - it doesn't work under windows.
HDD is because I have my harddrive on the second controller with the jumpers marked as slave. I'm thinking I may try messing with those settings as well, set it to auto select or something. When booting, it shows: IDE0= Quantum (my windows drive), IDE3=WDC (Western Digital, the new drive) and therefore linux calls the first drive hda1 and the other one hdh (I know hdd is a cdrom drive, dont know about the other letters. I have a cdrom drive and a cdwriter drive that linux recognizes, hadn't paid much attention to drive lettes in a long time thanks to an awesome-working RH 7.2).
I'll pull out my boot disk and try to boot into linux enough to run fsck and fdisk -i today, thanks for the help. I'll also try df to get the listing of the partition stuff and write it down for here. I will try to be more concise in future posts.
-Brandon
At 08:56 AM 1/8/02 -0700, you wrote:
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 to my XP cd and performed an install. Once completed I inserted my 7.1 boot disk and ran lilo. This overwrote the boot sector and now I can boot 7.1 or XP from lilo. Grub should have a similar utility available. Perhaps reading the man page would shed some light?
BTW, my 7.1 root is hda1 or 2 I believe. Hope this helps.
I've got RH 7.2. Just got a new harddrive. Let's call it HD1, the new
one HD2. /boot and / are on HD2, Windows and such is on HD1. I thought
I installed GRUB on the master boot partition, but during the
installation process it listed it as, "hdh5" because that's the first vfat partition on the second harddrive. Below is the pertinant portion
of my grub.conf file in /etc/ It looked identical to the one in
/boot/grub Input is appreciated, as I can't even load windows with a
boot disk, and being in college I need to go in there to print as I have
a Lexmark USB multifunction device with no drivers for linux... good
thing the semester is just starting. Thanks
splashimage=(hd1,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.7-10)
root (hd1,0)
kernel /vmlinuz-2.4.7-10 ro root=/dev/hdh2 hdd=ide-scsi
initrd /initrd-2.4.7-10.img
title Windows
rootnoverify (hd1,4)
/dev/hda1
chainloader +1
Sincerely,
Brandon Dorman
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.303 / Virus Database: 164 - Release Date: 11/24/01
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.303 / Virus Database: 164 - Release Date: 11/24/01
