The latest thing that I have done is to dig up an old P100 system and stick the harddrive into it along with two network cards. (Used DFE-530TX+ instead of eepro100.) After changing modules.conf to load the right modules, everything came up happy. I then tried ripping out the hard drive and both NICs and sticking it back into 1 GHz Athlon system. It did the same thing as it did before. Moving everything back to the P100 lead back to everything being happy again. Under clocking 1 GHz system to 950 MHz also didn't seem to make a difference. Windows ME and mdk 8.0 seem to come up on my 1 GHz system without a problem. Any insight on what is going wrong with SNF on my 1 GHz linux test / windows system? [EMAIL PROTECTED] wrote: > That got xcdroast running like a champ once again, thanks. > > After burning and verifying another CD under xcdroast it still fails to > find any valid devices to install to. Does SNF support the Promise > PDC20265 that comes with the ASUS A7V m/b? I bit the bullet and > connected my hard drive to the controller that has a long history of > causing problems intermittently and was able to install SNF. (I was > holding my breath hoping that the controller wouldn't hang like it has > repeatedly done with several different devices including the hard drive > that I was using.) > > Something else that came up with both the network boot floppy and the > SNF after installing it is that I can't get it to initialize my NICs. I > am using an older Intel EEPRO 100 for eth0 and a D-Link DE-528CT for > eth1. I set it up to use static IP address. I configured the internal > card (eepro100) to use an address that is not in use on my internal > network but is in the address range that I am using. The external NIC > is set up with the static address that my cable company provided, but I > did not hook the card into anything yet. When I type in ifup eth0 or > ifup eth1 under SNF I get: > SIOCSIFFLAGS: Resource temporarily unavailable > SIOCADDRT: Network is down > <snip> > With the boot floppy it seemed that I got the first line of the previous > message.
