According to Nathan Lamb: While burning my CPU.
>
> Yes, I did try these disks on other computers, and they worked fine.
>
> Yes, it is an EIDE Western Digital 2.5 gig HD. I have scanned the disks
> before, and I have a stack of 10 or so COLOR.GZ images, all of which were
> used with 'perfect' disks.
>
> This is really confusing.
It is to me as well, however Ray Olszewski <[EMAIL PROTECTED]>, made a nice
suggestion, now i have some more, but try Ray's first he could just be
right.
If what he says does not help take all other hardware out of the box which
is not needed to boot, ie cdrom all other disks which come after the disk
which you intend to install linux on, extract the NIC, now see what happens,
if you can boot add all the suff back one by one booting after every piece
of hardware has been replace exachtly the way it was.
Why do i say that,?? i have experianced a simalar problem, in my case the
cdrom was the culpret alongside a large hraddisk, the cdrom was placed as
slave on the secondary ide-interface with the large drive as master, in
linux thats /dev/hdc (harddrive) and /dev/hdd (cdrom), i brought the drive
new and added it to my machine, (the jumpers were set accordingly) huum
"thats what i thought" but the H/D needed to be jumpered as having a NON
ata device on the same interface otherwise problems arose.
Of course i'm not saying thats your problem, but a situation like that will
show up straiat away under linux whereas widows "could" allow it.
>
> Nate
>
>
>
--
Regards Richard.
[EMAIL PROTECTED]
