M
Mossaiby
Hi,
I have problems with nVidia nForce chipset on EPox EP-MGF6100-M. I only
need the NIC which is on-board. Searching this group, I finally found
out the simplest way is copying INF, SYS and DLL files to appropriate
locations. I have copied the files for the Networking Controller and
also Network Bus Enumerator. When I add RAM Disk, Core Networking and
Client for Microsoft Network components, everything goes fine, and
after FBA, I have a working NIC. But when I try to remote boot clients
with it, the device fails to work! In a build with Device Manager I get
error 1 for this device: The device is not configured correctly.
This is very strange. I also tried loading the SDI file using Boot.ini
option, and it doesn't work either on the same computer that Post-FBA
image works. What is special when loading from a RAM Disk?
Thanks for your help!
P.S. In both states, the Plu and Play Software Device Enumerator
reports error 19: Windows cannot start this hardware device because its
configuration information (in the registry) in incomlete or damaged.
Any idea?
I have problems with nVidia nForce chipset on EPox EP-MGF6100-M. I only
need the NIC which is on-board. Searching this group, I finally found
out the simplest way is copying INF, SYS and DLL files to appropriate
locations. I have copied the files for the Networking Controller and
also Network Bus Enumerator. When I add RAM Disk, Core Networking and
Client for Microsoft Network components, everything goes fine, and
after FBA, I have a working NIC. But when I try to remote boot clients
with it, the device fails to work! In a build with Device Manager I get
error 1 for this device: The device is not configured correctly.
This is very strange. I also tried loading the SDI file using Boot.ini
option, and it doesn't work either on the same computer that Post-FBA
image works. What is special when loading from a RAM Disk?
Thanks for your help!
P.S. In both states, the Plu and Play Software Device Enumerator
reports error 19: Windows cannot start this hardware device because its
configuration information (in the registry) in incomlete or damaged.
Any idea?