View Single Post
  #10  
Old October 9th 05, 12:11 AM
Franc Zabkar
external usenet poster
 
Posts: n/a
Default

On 7 Oct 2005 23:49:40 -0700, put finger to
keyboard and composed:

Glee:

The NIC was not using an IRQ that was in use by another device.
Device manager said, "No conflicts" regarding the NIC.


FWIW, here are a few ideas you might like to try.

What does "Start - Run - winipcfg - More info" tell you about your
NIC? Does winipcfg display an "Adapter Address", ie the physical
address of the NIC?

What do you see in the Configuration window in Control Panel -
Network?

You might like to see what happens if you boot to the command prompt
only and then type either "win /d:m" or "win /d:n". This gives you the
option of Safe Mode with or without networking.

WIN [/D:[F][M][S][V][X]]

/D Used for troubleshooting when Windows does not start correctly.

:M Enables Safe mode.
This is automatically enabled during Safe start
(function key F5).

:N Enables Safe mode with networking.
This is automatically enabled during Safe start
(function key F6).

You could also try selecting the "Logged /bootlog.txt" boot option.
Hopefully the log file will tell you where the boot process is falling
down.

Do you have any ISA cards? I ask this because I have a special purpose
ISA card in a 486 box whose jumpered (non-PnP) resources are not
detected by Windows 95. Such a card could give rise to an undetected
conflict.

Do you have a LAN chip on your motherboard? Some motherboards of that
era had a LAN chip but required an optional cable and slot bracket to
make use of it.

-- Franc Zabkar

Please remove one 'i' from my address when replying by email.