Try fixboot from the Windows recovery console?

The fedora release notes are in disk 1 of the distribution.
There is nothing in there to help the installation problems described.
The Personal Installation, is the site I suggested. mjm has much more than just that.

As for that other suggestion - nat a bad first post: sureley though, the windows fixboot will fix it by installing the windows bootloader.

Nah - there is something odd about the install.
For some reason the system thinks the filesystem is corrupted somehow - which is why it wants the rescue disk. One could attempt to boot from disk 1 - type "linux rescue" at the prompt, and use disk druid to check out the partitions. Or one could use qparted from a dedicated rescue cd (or Ubuntu, or Yoper, or ...)

Personally, the FC4 install was the only RH install that went right first time for me. Usually I miss a check box or something and something ends up weird. Mind you, it helps if you master the Cds.Reinstalling with careful attention to details usually fixes it.

Hope you read this before the new install.

Sorry I meant to ask last night.

Does it make 'any' difference what CD you have in the drive?
Apart from Linux Boot?

May sound silly. But I don't think Windoze has anything to do with this.
What I am suggesting is put on non-bootable CD in the drive !?
I also am hoping you can do a quick edit to your /boot/grub/grub.conf

Find grub.conf and expand on the default time to load and actually see if you have an erroneous menu option that is rather easier to fix.

-- Hope you see this. I am curious myself !

Cheers,
alar

I couldn't find mbrfix on W2K?

Shy of re-booting on to a new computer that is not on the Internet
Would this be applicable to me too?

<Bang, bang: Two postings same user >>

Figure if ure reading anyway...

Also, if i remember correctly, it is specified that it is not a recommended option to install GRUB in the MBR when you are using NT systems. So maybe you should install it on the 1st boot sector of your Linux's boot partition, create an image file of the bootsector (named bootsector.lin for the exemple), put it in your Windows root (C:\), and add the following line in your boot.ini file C:\bootsect.lin="Linux"
This way, you will use NTLDR as 'boot loader', and get the choice to boot on either system.
That is a workaround i used on my own config.
Remember that if your windows drive is not C: at first because for some reason you remapped it to a different letter, you still wanna use c:\ since remapping is not done at the early stage of the boot sequence.

I hope i was clear enough

I've had similar problems with a few old computers, and what I've found is that the architecture might be too old.

Check if the kernel has been installed in /mnt/sysimage/boot. Most of the new distros, FC4, CentOS3.5 distribute glibc*i686.rpm and this package won't install on a i586 or older computer. And because of dependencies the kernel won't install.

And when Grub can't find the kernel files it won't install itself. And thus, not able to boot...

Find an old distro that supports the CPU architecture, forget about using the latest. Or upgrade the hardware