"Linux can be booted "indirectly" just like a Windows. In such a case the Item (2) information is not needed. The sole requirement is to ensure the Linux has the boot loader inside its root partition. In "indirect" booting Grub only boots the boot loader and not the system.

There is no PC system I know that cannot be booted by a Grub floppy and all the necessary booting tips are in here"

That's not what you were stating before when you were claiming to be able to load any OS by floppy! Core 4
will not load with Grub4Dos even when trying the grub loader used by G4D. What loads Core 4 along with XP at
this time is the GNU/Legacy Loader included with the Fedora distro. With XP set as the default the screen for
Core 4 appears briefly following the post tests. The kernel itself is too large for G4Dos. That was conveyed
by other sources even on other forums. The current drawback at present is no sound and video drivers for the
installed hardwares. ATI has no video drivers for Linux apparently. And the Creative Audigy 4 + Audigy 4 Pro
models are detected as Audigy 2. The Audigy 4 line offers no support for 9x-ME let alone VFAT type drivers.

The question here would be the type of usb device being used such as a usb hard drive that would accomidate
the default loader being installed into the system's mbr. The usb drive/device would also have to bootable to
have Core 4 load. That is where you would need an mbr especially due to being used on two different systems.
Another alternative is the Live distros booted from either a cd or dvd drive where there is no installation
requirements to any drive. Those are self contained.

Linux Newcomer,

You must stop piling many problems together. Just ask one question so that there is no confusion. ok?

Grub floppy is Grub unattached to an OS.

The GNU/Legacy you get from FC4 is still Grub. By press "c" in FC4 boot menu you get a Grub prompt, the exactly the same thing you get from booting a Grub floppy. Therefore you can use FC4's GNU/Legacy to boot any system too. If you can't understand that it is the same thing there is nothing I can do. I have spent over 50 posts explaining it to you.

Grub4Dos boot to a Grub nominated by you. In fact if you type grub.exe and do not nominate a Linux to boot Grub4Dos will try to search your hard disk to locate and load the first /boot/grub/menu.lst it can find.

I have gone over the same ground with you so many times. Like the size of the kernel has nothing to do with booting but you never listen. The bootable Grub floppy only has Grub inside and it is no bigger than 150 kbytes. Why keep telling others FC4 kernel too large?

"You're causing yourself a lot more trouble by attempting to do it this way. A floppy isn't big enough to use to boot fedora. The kernel is larger than what will fit on a single floppy.
http://forums.fedoraforum.org/showthread.php?t=45910

The audigy4 will work in Linux provided that you have the most recent version of ALSA.

98 will work with >512mb of ram. You just need to change a setting.
http://support.microsoft.com/defaul...&NoWebContent=1"

The above was one knock down at one forum when the final Grub floppy still would not load Core 4. There was
no "/boot/grub/menu.lst" to find even now with XP and Core 4 joined at the hips so to speak. The Core 4 logo
screen is clearly visible for those few seconds allowing it to load properly with the Legacy loader. A remark
by that source on 512mb can be disregarded since the author there overlooked the actual 2gb of installed ram
causing an endless amount of issues with 98SE even after review of MS articles on the subject. Unfortunately
that source also failed to provide a link for Linux sound drivers that would work on an Audigy 4 Pro as well.

Regarding the FC4 boot menu there is none seen. Pressing "C" would simply load Core 4 when pressed. Fedora's
logo screen is the only screen appearing prior to loading XP set as the default OS. After the posts are over
any key pressed during that short time loads Core 4. The current problem unresolved after 98's demise is the
sound issue for the newer Audigy line. A possible SUS Linux patch might work if the instruction page was to be relocated again. Knoppix Live would be used to copy the drivers from the XP primary on the second drive to
the correct folder in the Core 4 partition along with the rest of the distro's main files. With the info that
the download site provided the new folder needed to install the drivers from could be created. At this point
the sound is the single remaining issue since Grub had to be installed on the second drive's mbr in order for
Core 4 to run. It was the 2nd drive's mbr not the first's that saw the loader installed into it this time.

I am not going to be diverted into Xp, sound and Win98 problems again.

Please stop all of them and concentarte on your booting FC4 and answer the following questions.

(1) Do you have a bootable Grub floppy?

Don't both to answer the following if you haven't.

(2) Can you boot up the Grub floppy, type
and report what Grub has to report.

I am pretty sure whatever booting problem you have most of the answers can be found in the links of my signature. I wouldn't mind repeating them here. But it is not going to help if you still haven't been able to make a bootable Grub floppy after over 60 posts.

As indicated earlier in Post #57 a Grub boot floppy was already made seeing no effective loader for Core 4.
As that time 98 was still on the 2nd drive's primary with directories made according to Grub4Dos instructions
in order for the Grub loader there to load C4. That could not load C4 due to previously posted errors.

To answer the second question was to go back one post. Grub did not find the "/boot/grub/menu.lst". Neither
did the use of Knoppix Live for dvd(cd image)locate the location of that file. The anaconda installer uses a
different method for configuring the loader it installs into XP's mbr that is more Windows orientated. Core 4
loads normal when pressing any key when the Fedora splash screen is seen. Otherwise XP takes over and boots
when the timer reaches "0" from an NTFS not FAT32 primary partition on the second drive. Too many issues with
98SE and the current hardware that has 2000/XP requirements saw 98SE put "out to pasture". Thus Grub4Dos will
not run it's own loader on an NTFS partition to add to that.

Core 4 currently loads with no issues besides the lack of sound and video drivers. Reconfiguring the loader
to stay onscreen a few seconds longer simply takes a boot of the FC4 disk #1 to correct that by simply making
a simple adjustment in the manual settings. That was initially overlooked when the Legacy grub was installed.
You simply have to press a button faster to load Core 4. What you are missing is the actual end result where
the initial goofs effecting both drives are now seeing Core 4 running on the second one along with XP instead
of 98SE. Booting FC4 has already been resolved. Unfortunately it took a multiboot with XP to see it happen. A
few drivers for Linux are all that are needed at this time.

If you can load FC4 can you paste here the content of the directories of
/boot
/boot/grub

Bah, spent too many days playing with Fedora. I downloaded a single Debian ISO, burned it, rebooted with it in the cd drive, installed Debian in the unallocated space I had made by resizing a big partition and I was up and running almost everything within 1 hour. Grub installed properly (and automatically) in the MBR and everything. I'm dual booting effortlessly and doing everythign I need. Fedora couldn't do any of that for some odd reason. Debian rules.

Now you are starting to get the idea as to why the various links and commands provided by a
talented Linux user here didn't see results besides the 98 issues that kept coming up. Core 4
runs as smooth as silk with the Legacy loader installed into the XP mbr on the second drive.
The original goof was when anaconda bypassed the previous 98 mbr and went into the mbr on the
XP primary drive. Finally the link to make a working grub boot floppy came about. That though
saw 7 not 1 partition on the first drive and 7 on the second 5 partition dual OSed drive. But
Fedora won't access the XP partition on either drive to copy one set of sound drivers to the
FC4 partition holding all of the main files. Knoppix Live however has proven itself to be the
best of the distros tried so far due to being able to access FAT32 and NTFS partitions alike.

In response to saikee's request for what was found in the "/boot/grub/" folder that was the
"splash.xpm.qz" as mentioned earlier in post #32. That simply is the splash screen seen prior
to XP's loading that has the Fedora logo. The use of the Knoppix Live distro to find menu.lst
in any of the FC4 partitions was futile. Sorry about that saikee. For some reason a creation
of that one file was never seen. The commands provided earlier also failed in creating one in
the efforts there. Gee? Does Knoppix Live have a full package for a hard drive to replace...

In that case your FC4 installation is incomplete.

Can you not let us see your FC4's
/boot
/boot/grub
directories?

You can create your own /boot/grub/menu.lst or re-install FC4 again. Where the Legacy Grub should go from FC4 is entirely at your hand. MBR always the first 512 bytes of the "first" bootable disk.

Actually Core 4 has been reinstalled about four or five times so far due to first having a dual 98SE/FC4 on
the second drive. You already know what happened with the initial installation when the primary drive was the
one to see the Legacy grub install to the unintended mbr. That mess was cleaned up fortunately by isolating a
primary from any activity on the second drive by simply "pulling the plug"!(or connectors). With implementing
the Knoppix Live distro all partitions can be examined thoroughly. The "/boot/grub/menu.lst" has somehow been
the one "elusive animal" during the entire process. This is even after the repeated downloads of Core 4. FC4
was repeatedly written to disk to insure integrity. Yet no menu.lst is found. One last look with Knoppix Live
is on the schedule. This will allow you an extensive look at all folders and subfolders found.
(Anyone for book writing?)

This is the whole problem of you prolonging this thread over 70 posts and everybody could not know why!!!

For what reason on earth that you can boot up FC4 but have to use Knoppix to investigate FC4 directories?

Can you not in FC4 terminal mode and juts type
This is my flustration. You keep confusing us with Win98 issues when we are concentrating to resolve your Grub problem.

Your FC4 cannot boot itself without Grub and there must be something in /boot/grub dirtectory. So just show us what have you got. Don't get Knoppix involved as you have confirmed FC4 boots successfully.

The 98 issues were resolved. XP replaced 98 due to the consistent problems with hardware. That is rather old
news at this point as you are well aware of. The Knoppix Live for dvd/cd distro has proven itself a valuable
tool for the Linux "NEWBEEEEE..." here. The browser allows full access to any partition whether or not it is
a Linux or MS type partition. Some recommend using a Live version first when being unfamiliar with Linux to
more or less avoid the goofs initially made here admittedly.

But there is some good news on the horizon to place here. The following was seen for the first time after a
fifth reinstallation of Core 4 somehow required a change of the mount partition. This is where all of the FC4
files were found. When entering "Local Host ~l$ ls /boot/grub" the following appeared for the first time.
"Device.map grub.conf minix_stage1_5 stage2
e2fs_stage1_5 iso9660_stage1_5 relserfs_stage1_5 vfs2_stage1_5
fat_stage1_5 jfs_stage1_5 splash.xpm.qz vstafs_stage1_5
ffs_stage1_5 menu.lst stage1 xfs_stage1 xfs_stage1_5"

Apparently the modification of the main file populated partition in order to get Core 4 up and running was a
tool in the creation of the "menu.lst" file now being seen. Success here saikee! Finally we are getting some
working results. Thanks for hanging in there! The latest install saw results with the above now being able to
recognise the Linux commands. You will note that the splash.xpm.qz remained consistenr during all of this. It
was first seen using the Knoppix Live cd to browse through the Core 4 partitions. Don't rule out the use of
one thing that does work when the default OS doesn't. With Core 4 up and running at this point where it does
now recognise the commands you have posted the making of a new directory to install sound will be done when
the web page instructions for installing Linux sound drivers can be relocated. Knoppix Live will then be the
tool for copying the downloaded drivers to the new Core 4 directory. Knoppix still has uses.

That is great news. I thought I could be here for the next Christmas.

Anyway if you are happy with Knoppix consider it as part of your installed systems, since you could be pretty skilfull with it now.

I wouldn't trying too hard to solve the hardware problems now because installing a few distros and you will find all of them work. You can then go back to compare the settings and improve the situation.

Something obviously wouldn't go on during the first installations. The last two were done with a second set
of cd-rs after a repeat download. Yet the second set still saw the same error message when trying to verify a
quality of burn. The Knoppix Live acts like a free agent that go between Linux and MS partitions. That is why
that is kept onhand in cd-r form. Apparently the second install of Core 4 mainly due to XP not accepting SP2
on the prior 2gb partition and cause for a repartition and reformat saw one thing different. A partition for
Mountng saw a change is size due to not being large enough. The bulk of Core 4's files were found there where
the original 2gb was increased to roughly 40gb as the now XP primary used 54.6gb.

The issues with hardware mainly surrounded 98 not Fedora. It will take time for sound as well as having the FireFox browser configured for going online. But that was to be expected anyway. That's part of learning the ropes inside and out with any operating system you are taking the first steps with. Now the Linux commands in
one or more tutorial can be tried out as well. At least you will get a clean bill of health for your patience
through all of this. I'll have to let you know which distros will be running on the next upgrade ironically scheduled for the end of the year. And Thank You for seeing this through.