Link to home
Start Free TrialLog in
Avatar of srini123
srini123

asked on

Windows 2000.. ,warning message after booting

I installed 2000 recently on my system.All drivers were installed successfully from OS itself  except modem driver.My modem  is  HM2868( PC TEL )make ( internal modem) , this driver is available in OS and it got  installed, but gave erratic messages stating that 'the driver is not suitable for win 2000'.When the modem driver was installed from the CD(Modem driver) it got installed successfully and is working fine.But whenever system is booted it throws a message that
' load=load=load=  remove from the registry entry.. '
If  that message is ignored system is working perfectly alright.
Iam not able to understand what is the meaning of that message.To stop this message what shoul di do?
 any Suggestion is highly appreciated
Thanks in advance to Gurus.
M.Srinivas
Avatar of dis1931
dis1931

What is the exact message?
Avatar of srini123

ASKER

Exact  message is
'load=load=load=load=

 cannot find the file 'load=load=load=load='( or one of its components),make sure the path or file name are correct and that all required libraries are available.

it asks  to press ok
after pressing ok
again one more message which says

could not load or run 'load=load=load=load=' specified in the registry ,make sure the file exists on your computer and remove the reference to it in the registry.
ASKER CERTIFIED SOLUTION
Avatar of dis1931
dis1931

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I think I deserve at least part of the split as I mentioned re-installing the software for the modem.  And also suggested the most likely answer which is to look in one of the two run keys that probably hold the incorrect registry entry.  Both of the other participants expanded a little on those two answers that I supplied and kidnme added some other thoughts or considerations of his own as well.
Agreed.