sorry harley, but I just absolutely didn't understant that. can you try to make it a bit clearer?

Finally got Core 3 to install. My laptop is dual boot. What did it for me was to boot to Windows, download, and burn core 3 on the laptop (same drive that would be trying to read the install CD's). It worked fine. So, if you can burn on the same drive you want to install from, it may work.

For those of you having problems with media checks when burning on one machine to install to another, there are some alternatives if you have 1) a 2nd box that can get to the Internet. In this case you might be able to put the disk into the other box, burn CD's and install without writing a Grub or LILO. You'd have to do that once the disk was in the correct machine; or 2) have a LAN where you could load the installation CD's on another machine and do an NFS install. Would need to create a kickstart floppy or CD and boot from it. It should then go to the NFS mount. On a network, these are good installs. There might be a gotcha or 2 with the first alternative. Not quite sure about drive/fs info (hdb1 on temp machine. What is it on the target machine? I haven't tried this.

BTW, Linux is not the only one having this kind of trouble. I was trying to load Windows a while back. It kept hanging in the middle of the install. It was the driver they were using. Not as good as the one available after install!

I did burn on the same drive I'm trying to read from. I think I'll just try to install anyway since it's not on my windows hard drive. I can just reformat that HD from windows if it doesn't work and try that network install you mentioned. I had forgoten about doing that.

Hi, I had a similar difficulty with the FC3 install disks. Disk 1 passed the media test and Disks 2, 3, 4 failed. But here was the solution that worked for me:

cdrecord dev=0,1,0 speed=16 padsize=63s -pad -v -eject /home/myuid/myiso.iso

The main idea is to use padding when recording. All four disks passed with no problem after this!!
Note: dev=0,1,0 is where my drive is (yours may be different. Try: cdrecord -scanbus or
cdrecord -dev=ATAPI -scanbus with ATAPI drives like mine) Also, set the speed to the LOWEST speed of your drive (my drive is labeled: 48x/24x/48x/16x so I used 16 as the speed). Finally, DO NOTHING ELSE while the cd is burning (it only takes a few minutes).

Here is the website that solved this problem (and has useful info on cd burning in general):
http://www.troubleshooters.com/linux/coasterless.htm

Good Luck!

I'm sorry I wasn't clear. What I did was take the Install disk 1 for Fedora Core 2 or it can be Fedora Core 1. I booted up on the install cd just like I was getting ready to install and when I got to the media check screen hit OK and started testing cd's. When your done testing just reboot the system. I found cd2 and the rescue cd was bad and just re-downloaded these two.

Ahhhh, I see. Much clearer. Thanks

Allow me to also reclarify. The instructions I gave is for a situation where you (a) have done an MD5 check (md5sum myiso.iso) and it matches and (b) your disks are labeled properly and you know what OS your working with! The reason for point (a) is if the MD5 sums check it is probably a waste of time and bandwidth to download the large iso files again. While it is possible that the checksums were given incorrectly, it is much more likely that the download was good, but the burn to disk was bad.

Happy installing

I was having problems with media check failures. Check sums on the .iso's were fine. I finally just ignored it and went on with the install. It appears that it worked fine. For a home install this may be OK, might not want to do it w/a production server.