Strange Error When Trying To Install Fedora Core 9

[Gollum1405241558 0]

Hi all, I tried to install Fedora Core 9 in a VmWare virtual machine under WinXP.I downloaded the DVD ISO image and proceeded with the installation. When the process was started since about a minute, the following error did show:"The file evince-2.22.1.1-1.fc9.i386.rpm cannot be opened. This is due to a missing file, a corrupt package or corrupt media"Fine, I told to myself, let's download the ISO image again, this time from a different server, just in case. No joy, same error. Tried another couple of times, each one using a different server for the download. Same results...Browsing under Windows the DVD produced with the ISO image, I am perfectly able to find that evince-2.22.1.1-1.fc9.i386.rpm file, and even to hexadecimal browse it, without reported errors...Help, please.... -Fred

[xboxrulz1405241485 0]

Sounds like a broken ISO, file a report at Fedora's bugtracker.
https://bugzilla.redhat.com/index.cgi

Have you tried to see if there's anything about it in Fedora 9's release notes?
https://docs.fedoraproject.org/en-US/Fedora/9/html/Release_Notes/

Else try not to install this evince ... I'm not even sure what type of package that is myself.

xboxrulz

[Gollum1405241558 0]

Else try not to install this evince ... I'm not even sure what type of package that is myself.

Thanks for the reply. Well, I would like to be able to choose which packages to install... but Anaconda does not offer me this possibility. Sometimes making the install of Linux too much user friendly can have adverse results. Ok, I will investigate in the Fedora forums to see if I am the only pour soul getting that error.

TNX

-Fred

[yordan 10]

It should work. I guess that your distro is like the other fedora distros, there is probably, at the beginning, a box saying something like "do you want to check that your CD is correct?", and if you click "Yes" it will check that each necessary rpm is present and is valid. I'm pretty sure that you said "no". Try saying "Yes" in order to verify the ISO file.What I love with vmware is that you can directly install from the ISO file instead of burnig a CD, you save a lot of time if the iso is corrupted. And the verification program is nice, it avoids failed installs.

[iGuest 3]

i am really unable to help you here to tell you the truth i dont even know whay fedora core is or even what it is for can some one plz do me a really really big favour and tell me what it is and what it is for i would be reaplly really great full for any answers big or smallCheersJay

[iGuest 3]

CD

Strange Error When Trying To Install Fedora Core 9

 

Why don't you try getting the image from any PC Magazine.

I got mine from one and it installed properly.

Try

http://www.planetmy.com/blog/how-to-install-fedora-8-werewolf-in-vmware-server/

for steps

[Mordent 0]

*waves his wand of thread necromancy*Anyway, I recently installed Fedora 9 on my desktop (on a separate hard drive partition), but yeesh...it took a lot of patience to actually do it. My main OS is (and still is) Windows XP Home SP3 (which ironically runs like a dream , except for the random errors), but as all of the computers around my uni have Fedora as the "preferred" OS (not to mention my entire programming course uses Fedora as the basis for their tutorials) I thought I could have another shot at it.What was the trouble? My damned USB stick! Being the sort of person that I am (namely a university student, and therefore pretty skint) I didn't fancy buying a CD/DVD to burn the .iso to, so I played around with ways of getting it to boot from my USB flash drive. The process seemed simple enough, but it turns out that my particular memory stick didn't want to play along. If it had said that earlier then I would have saved myself a lot of hassle, but instead I got the joys of CRC (or CRR, basically funny copying where the bit checking didn't match up) errors. Pass as to what it stands for, but I remember spending a lot of time trying to download the .iso and mount it on my USB stick again and again.Anyway, in the end I borrowed someone else's memory stick. Worked first time. Figures, huh? I guess the moral of the story is to not always read too much in to what the error is saying. It's an indication of where the system mucked up, but it may not be the cause of the muck up (if that makes sense).