W2k Server startup problems

[Guest]

I have a Windows 2000 server which recently contained an ISDN card that was set up for demand dial routing in Remote Access

I needed to remove this card but stupidly didn't uninstall it first

I can no longer boot the server (the server just freezes on the white Windows 200 Server screen about half way through)

However, I can login in safe mode and have noticed that the system is still trying to process the drivers when starting up. There is nothing in device manager for me to remove he drivers

Is there any way of removing the reference to this ISDN driver? I can find a reference to it in the registry? Is there a file which determines which device drivers get loaded on startup

This is all I can think the problem could be - there are also lots of issues logged in the event viewer including a lot of MxrSmb problems and also some Active Directory ones. Could the removal of the ISDN card cause the NIC to fail therefore stopping AD loading and the server to fail loading

Any help greatly appreciated

Thank

Jof

 

[Pegasus \(MVP\)]

I have a Windows 2000 server which recently contained an ISDN card that

was set up for demand dial routing in Remote Access.

I needed to remove this card but stupidly didn't uninstall it first.

I can no longer boot the server (the server just freezes on the white

Windows 200 Server screen about half way through).

However, I can login in safe mode and have noticed that the system is

still trying to process the drivers when starting up. There is nothing in
device manager for me to remove he drivers.

Is there any way of removing the reference to this ISDN driver? I can

find a reference to it in the registry? Is there a file which determines
which device drivers get loaded on startup?

This is all I can think the problem could be - there are also lots of

issues logged in the event viewer including a lot of MxrSmb problems and
also some Active Directory ones. Could the removal of the ISDN card cause
the NIC to fail therefore stopping AD loading and the server to fail
loading.

Any help greatly appreciated!

Thanks

Jof

You could rename the driver for the card. If the Event Logger subsequently
raises an alarm then that alarm would have sufficient details to disable the
service that invokes the driver.

Here is what I did on my machine to determine what driver is used for my
network adapter:
1. Determine the network adapter. It's a Netgear FA311.
2. Launch regedit.exe and navigate to HKLM.
3. Search for "FA311". The first reasonable hit is here:
HKLM\software\Microsoft\Windows NT\CurrentVersion\NetworkCards\8
4. Under "Service Name" the data is {33ED9E5A-525F-4346-846A-4E1A77E6EA5D}.
Put this in my past buffer (Ctrl+C).
5. Navigate to HKLM\System\CurrentControlSet.
6. Seek {33ED9E5A-525F-4346-846A-4E1A77E6EA5D}.
7. I get a hit on this key:

HKLM\System\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE
10318}\0007.
8. Make a note of the value against InfPath and InfSection. In my case it's
oem6.inf and FA311.ndi
9. Open c:\winnt\inf\oem6.inf (in my case) and navigate to [FA311.ndi].
10. The next section is [FA311.ndi.reg]. Amongst other things it lists
FA311ND3.sys. This is the driver file for my network adapter. If I rename
the file itself then the driver won't load.

 

[Guest]

I've tried deleting these keys but to no avail

I think the solutions is to disable the routing and remote access service - thereby stopping it from trying to load the drivers

I've disabled the services but this isn't the same as Disabling it itself (so that it losses all the config information). Obviously I cannot do this in Safe Mode

This is all I can think that it could be. Is there anything else that I could have thought of

What in particular gets loaded during this White Screen period? Device drivers?

 

[Pegasus \(MVP\)]

I've tried deleting these keys but to no avail.

I think the solutions is to disable the routing and remote access

service - thereby stopping it from trying to load the drivers.

I've disabled the services but this isn't the same as Disabling it itself

(so that it losses all the config information). Obviously I cannot do this
in Safe Mode.

This is all I can think that it could be. Is there anything else that I could have thought of?

What in particular gets loaded during this White Screen period? Device

drivers?


Seeing that I went to quite some trouble in creating a step-by-step
procedure, you could make your feedback a little more detailed than just
saying "I've tried deleting these keys but to no avail". For example, you
say nothing at all about Step 10. Did you find the driver file? What is it?
Did you rename it? What happened when you renamed it? Furthermore: You say
you deleted some keys. I never suggested that you should . . .

 

[Guest]

So, yes, I renamed the driver which was something fpci.dll (or .sys?) if I remember

Its a BT ISDN Speedway card that had been recgonised as a Fritz card automatically

I missed your tip about accessing the INF files so I will try that

Failing that - who knows

Thanks for your help!