Everything is a PCI Simple Communications Controller !!

  • Thread starter Thread starter Martin
  • Start date Start date
M

Martin

Can anyone give me a clue as to what would be causing my IBM Netvista
(Win2K) to recognize any device I insert in a slot as a "PCI Simple
Communications Controller"?

A modem, a 2nd NIC, a DigiBoard (multiple serial port card) - it sees
them all as Simple Communications Controllers. For example, if I
insert the modem card and force my way thru the Add/Remove hardware
wizard and tell it to install a modem, it will tell me it can't find a
modem and offer to install it only on COM1 (I assume it assumes that
the modem is external).

All of these cards WERE working OK in this computer. I removed the
DigiBoard (without un-installing it first) and I've had this problem
ever since.

How do I get past this?

Thanks.
 
I really need some help here. Any advice would be appreciated.

If I insert a modem, it's seen as being a PCI Simple Communications
Controller and it can't install it. If I step thru and tell it to
install a modem, it can't find a modem to install.

If I put the NIC in, it recognizes it as a NIC but when I follow the
mfgr's directions and point to the proper driver folder on the CDRom,
it says it can't find any drivers.

IOW, it's acting bizarre.

Other than the problems trying to install cards, the computer starts
up and runs normally with no error messages.

What do you think? Do I need to do a "Product Recovery"?

Help?
 
are you certain you have the proper drivers for w2k for
these devices??? do you have the .inf files for w2k?

When you step thru and specify a modem, are you also
finding the particular manufactor and model for the device?
it may not find it, load the drivers anyway, ensuring they
are the proper ones for your device and w2k.

Do not let the hardware wiz search for a device, instead
choose from a list, then find your particular make and
model
 
This error state is very often attributed to a failed Office 2000 update
(or could be from another failed update, but I have seen this most
commonly with Office 2000 SR1 updates). There are several dependant
..dll files that the Simple Communications Controller shares with Office
(Good 'ole M$oft). The failed update can be a result of loosing power
during an update, loosing Internet connectivity during an update (like
with Office update on the web), bad sectors on an HDD that are accessed
during an update, or any similar situation.

These are steps that I have taken in the past to fix this issue.
Perform them in order:

1. Boot from a Win2K or WinXP (respectively) CD, and launch the
Recovery Console. Repair the current installation by following the
instructions.

2. Uninstall and reinstall Office 2000 and reapply all of the service
packs (I know...this sux, but it works if #1 doesn't fix the issue).

3. Start from scratch (Reload/Reimage/Restore).

This error is the result of a corrupted set of .dll files. I have even
replaced and re-registered (regsrv32.exe) the .dll's that I thought
were affected (anything hooked by the subprocesses that use the PCI Bus
and any related hardware - NIC, Modem, etc.) to no avail.

Hope that this helps!


LoonaTech
 
Back
Top