Hey-
I get the following error messages while installing 8.0 from downloaded ISOs. I have downloaded from 3 locations to verify my problem was not from a particular mirror site.
I used checksum tool to verify and also "tested media" during install all saying that everything passed.
I would appreciate any help.......thanks

TRACEBACK (most recent call list)

File "/usr/lib/anaconda/gui.py", line 786, in handle render callback
self.current window. render callback ()
File "/usr/lib/anaconda/iw/progress_gui.py", line 149, in reder callback
self.intf.icw.next clicked ()
File "/usr/lib/anaconda/gui.py", line 632, in next clicked
self.dispatch.goto next ()
File "/usr/lib/anaconda/dispatch.py", line 215, in movestop
rc=apply(func,self.bindArgs(args))
File "/usr/lib/anaconda/packages.py", line 719, in doinstall
problems=ts.run (0,~rpm.RPMPROB_FILTER_DISKSPACE,cb.cb,0)
File "/usr/lib/anaconda/packages.py",line 283, in cb
fn=self.method.get Filename (h, self.pkg timer)
File "/usr/lib/anaconda/image.py", line 119, in get Filename
f=open ("/mnt/source/.discinfo")

IO error: [Errno 2] No such file or directory: '/mnt/source/.discinfo'

Ewww, that looks nasty. If you checked checksums, and tested media the CDs should be good. What are you installing it on? Anything odd about the hardware? Any other clues other than the traceback stuff, where in the install did this occur?

I get the error message about half way through the install. Nothing's unusual about my hardware configuration and actually 8.0 seemed to be the first distro that recognized and accepted everything I'm running.
I'm going to try and install on my box at work today.

AMD 450
320 mb sdram
Radeon 7000
on board sound
Com 21 cable modem

Thanks, ahead of time, for any suggestions!

It must be configuration. I used a seperate drive at work and it installed fine.
I have my home box partitioned with sysyem commander.
Thanks for the help.

I'd try leaving the space for Linux unpartitioned and partition during the install. Something must be odd about the partition setup you did with System Commander. My guess is it was close enough to fool the installer into starting, and then blew up with rather spectacular results once it really got into it.

I've created problems with partitions not starting and ending on proper boundaries, I don't remember but I may have done it with partition magic. Seems like the DOS based stuff might be the culprit . There's a partition tool called 'Ranish Partition Manager' that comes with 'Extended Operating System Loader' (http://www.xosl.org) that's really good about enforcing the rules about partitions, but you should be fine partitioning during the install if you leave unpartitioned space.

Good luck

Thanks for the tips Psycho-

I tried to install on seperate drive at home and got the same errors again??!!!

It has to be some sort of hardware issue I guess?

The same media I installed with at work gave me the error message again at home.

I'd appreciate any other suggestions as to other linux oses

ScottyB,
I would be interested to know whether you solved this problem, as I now have exactly the same error messages when trying to install from a set of Redhat 8.0 Disks. The strange thing is that I have successfully installed on the machine previously, using the same disks. The only changes I have made in the meantime are:
* I have added more RAM (was 192 but now 320).
* I have given entire 10 GB to Linux, whereas before I shared the drive with Windows
* I have created a /usr/local partition, as well as the /usr partition that I always create in Linux

If this error is hardware-related, it may be because of my new RAM configuration. I removed a 128 MB module and replaced it with a 256 MB module.

Any help would be appreciated.

A friend tells me that my problem is almost certainly because of the new stick of RAM that I installed a few weeks ago. My machine is a Celeron 500 MHz (a few years old), so it will have problems with new memory modules, in particular 256 MB modules. He tells me to get an older 128 MB module and test this. I will post a message in the next week with the results.