Chris, give me until tomorrow night, I'll check it on mine. intel 200 Mhz pentium on an abit board. ( currently running mandrake 8.2 on it ) has usb support, but no usb ports hooked in.
Chris wrote: >Hi again, > >No luck with any of the suggestions. I also tried this with the released >9.0 Dolphin. When I boot with the floppy cdrom.img-2.2.19-BADZ5 image it >almost immediately says "Boot failed" after the "SYSLINUX ..." text. >When booting from the CD with > > boot: linux noauto > >it loads the image and hangs again after it wrote "Ready.". > >I should correct the hanging behavior I described when I boot from the >9.0 CD: The screen clears with just a blinking cursor when the initial >progress bar has finished - not even Ctrl-Alt-Del works after this. > >The Pentium 200 MMX sits on an Intel TC430HX motherboard (no USB) and I >have had Windows 2000 Adv Server installed and now SNF7.2 recently >installed and still running on this PC with this hardware configuration >(96 MB RAM, Adaptec 2940, Pioneer SCSI CD, Intel PCI network card, >Netgear PCI network card, Matrox Mystique G200, Quantum IDE harddisk). > >Is this a i586 issue or a hardware/motherboard issue? I have no other >plain Pentium (i586) PC where I can try the 9.0 on. Has anyone else >succeeded to install the 9.0 on an "old Pentium"? > >/Chris > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, September 24, 2002 17:13 >To: [EMAIL PROTECTED] >Subject: Re: [Cooker] rc3 install hangs on a P200 MMX > >"Chris" <[EMAIL PROTECTED]> writes: > >>Hi, >> >>I've tried to install rc3 on a Pentium 200 MMX but the PC hangs >>when it comes to the second stage (the installer had installed >>the 2940 driver and the progress bar for loading the 2nd stage >>had completed) - the screen went blank and the PC & keyboard is >>dead. I've tried different kernels via expert install but the PC >>hangs then too (says "loading..." and then prompts "Ready." but >>the PC is totally dead). >> > >You may try adding the boot options "noauto" so that it >workarounds a possible USB driver problem. > >You may also try `images/alternatives/cdrom.img-2.2.19-BADZ5'. > >
