installed a new motherboard to replace my nf3/agp. without really considering it, i installed the nf4 NAM (network access manager) along with the rest of the nf4 drivers. big mistake.
kept having "irq less than" and bluescreens caused by http.sys. after some research, it seems NAM is a bit buggy and this was the likely cause. the fix was to remove it.
so uninstalled via "add remove programs" in control panel, and now my networking is hosed. rather than accepting the DHCP address, it assigns 169.254.139.98 to the adapter (regrdless of which lan adapter i enable - nv or marvel).
i've "reset" the tcp/ip stack via windows shell script, deleted all pertinent registy entries, and even reloaded windows (not clean - too many apps to reload after 4 years), and it still does the same thing.
anyone offer any ideas? i've run out of em...
edit: found the resolution. resetting tcp/ip stack was not enough. using shell to reset winsock was also required, and doing so seems to have corrected the problem - and no more bluescreens!
kept having "irq less than" and bluescreens caused by http.sys. after some research, it seems NAM is a bit buggy and this was the likely cause. the fix was to remove it.
so uninstalled via "add remove programs" in control panel, and now my networking is hosed. rather than accepting the DHCP address, it assigns 169.254.139.98 to the adapter (regrdless of which lan adapter i enable - nv or marvel).
i've "reset" the tcp/ip stack via windows shell script, deleted all pertinent registy entries, and even reloaded windows (not clean - too many apps to reload after 4 years), and it still does the same thing.
anyone offer any ideas? i've run out of em...
edit: found the resolution. resetting tcp/ip stack was not enough. using shell to reset winsock was also required, and doing so seems to have corrected the problem - and no more bluescreens!
Facebook
Twitter