On Tue, Jul 6, 2010 at 6:59 PM, john wendel <jwendel10@xxxxxxxxxxx> wrote: > On 07/06/2010 01:29 PM, mike cloaked wrote: >> On Tue, Jul 6, 2010 at 9:18 PM, Dr. Michael J. Chudobiak >> <mjc@xxxxxxxxxxxxxxx> wrote: >>> On 07/06/2010 04:08 PM, solarflow99 wrote: >>>> On Tue, Jul 6, 2010 at 12:47 PM, Stephen Gallagher<sgallagh@xxxxxxxxxx> wrote: >>>> some of the problems I had are known (repo problems, etc.) but at >>>> other times, anaconda would abort at different points during the >>>> install, i'm going to have to try with F-12 and see if its any better. >>> >>> Did you try installing from a live CD instead? Often that works better >>> than using a classic install CD. >> >> An awful lot of people have installed F13 perfectly successfully - >> which hardware and what method did you use to install? >> >> > > I've done two installs using the X86 lxde live cd and both got an error > while reading the install cd (and claimed it must be corrupt). One box > is an Athlon X2 Dell system and the other is a homebuild Athlon XP (very > old). The cd checks fine. The 2nd try worked fine in both cases. And the > installed systems work great. Well, I used F-12 and it worked perfectly, so it is definitely something to do with x86 F-13's anaconda. seems strange i'm the only one to encounter this. I tried both with a HD and DVD install, the media was tested and she shasum matched, so I dont know why... I never did find an updates.img with all the cumulative fixes included which might have helped. I am doing this on a HP P-4 2.8Ghz 1GB 80G IDE, memtest86 passed -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
