Thinkpads Forum

I am running a TP 600 on a docking station with Win 98 2nd edition. I installed the modem driver and on restart, I get the message:
MWME: Modem Internal Error
Primary Code: 5(0x0005)
Secondary Code: 105(0x0069)
I installed the same driver on an identical TP 600 the other day and it worked great, so I'm pretty sure there is no problem with the driver.
I tried to remove the modem and reinstall it but it won't let me without first removing "Think Pad Digital Signal Processor". When I go into "Device Manager" it says the modem is working but when I go to "Properties" on the "Think Pad Digital Signal Processor" it says "Setup cannot load installer (mwci.dll) for the MWave DSP Hardware being installed". Does anyone have any idea what I need to do or what my problem is? I greatly appreciate any and all help.

Jimclean, Did you solve this Modem Error problem. I have exactly the same problem ( Win98SE, TP 600 ) aftre recently installing the OS, although I can work around it by simply ignoring it and letting the system boot up. Please let me know if you have found a fix. Thanks.

Sudevan

I suggest you read the text file from the following link for installing and uninstalling the modem driver and the ThinkPad Digital Signal Processor.

ACP modem driver II for Windows 95/98/Me/2000/NT - ThinkPad 600/E, 770/E/ED/X/Z

Software and Device Drivers - ThinkPad 600

The 600 also has a test suite in EZSetup. Try testing your modem with that to be sure the hardware is working.

Thank you GomJabbar and Whizkid. I read up on the sites that GomJabbar sent me, then began with Whizkid's advice to test the modem after booting into EZ-Setup. The tests ( modem and DSP ) ran successfully. Then I uninstalled the modem drivers and reinstalled them, and everything worked. I did a second shutdown and reboot into Windows, just to make sure the error message would not come up, and it worked fine.

Interesting, though -- being a scientist, I am always curious about why things are the way they are: I wonder why the uninstall and reinstall worked here. Is it possible that in the space of three or four days, the drivers we installed had become corrupted somehow? Or did we install them incorrectly, perhaps?

Thanks for the terrific advice, chaps.

Sudevan