Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

A Corrupted File

Jan 23, 2005 8:49AM PST

Hello. I have messed up my Windows 98SE and am asking for help for a fix that is beyond my basic knowledge.
A while back I tried to delete an added program's software by selecting any file that carried its' name in it and pulling the trigger--duh, not a good idea. Now when my computer starts, I get the error "The BVRPDIAG.DLL file cannot start" File checker says the setupx.dll file at C:/WINDOWS/SYSTEM needs to be restored from the installation disk. Since I'm no rocket scientist, do I put the Windows 98 or the SE disk in? The file checker says to specify the file to be restored--that would be the 'setupx.dll' or the 'BVRPDIAG.DLL'? A repair shop was trying to talk me into spending a lot of $$ at $80.00/hour, and this SEEMS like it would be a fairly simple task--but I have been wrong before. Could someone please advise me through this proceedure step-by-step so I don't mess anything else up? Many thanks. Annie_C.

Discussion is locked

- Collapse -
Installation disk. . .
Jan 23, 2005 9:24AM PST

is the one for the program you tried to uninstall. Reinstall the program then uninstall it properly from Control Panel, Add/Remove Programs.

And we learned somethin, huh. Never delete files and folders from a program unless you have properly uninstalled it first. Then and only then can you delete a leftover folder.

Good luck,

Telephony facts, analog/digital explained.

See the CNet faces behind the posts.

If you're reading this, thank a teacher. If you're reading this in English, thank a U.S. soldier.

- Collapse -
Jeeze, somebody take the delete button away from me...
Jan 23, 2005 10:34AM PST

I tried to uninstall Norton Utilities, and if I remember right I did use the Add/Remove first, but there were some leftover files it didn't take with it, so it was then I made my mistake. I have gotten the impression the corrupted file is a Windows Startup--so my reference to the '98SE disk--- because every 30th time or so windows won't load--just a black screen with the cursor blinking in the upper left hand corner. I turn it off manually, restart, and it runs ok after that, but I have been hesitant to add any other programs to it because of my stoopid error. Is there anyway to tell if the file that is corrupted and the one that cannot start are the same ones? Or to tell to what they belong to? This has been driving me nuts for a long time now; but it's easier to close the error message box and not worry about it because it does run, the problem is out of sight out of mind and all, but I know the computer is limping along. Thank you for your help. By the way--have you seen the "Support the American Way/Welcome to America--Now Speak English" T-Shirts? Wink

- Collapse -
Dave, Did You Read Those Links ?
Jan 24, 2005 2:05AM PST

...Specifically read the second link you provided. The files mentioned are part of the "Netwaiting" portion of the Digital Line Detection software (dlg.exe) for the modem connection and it doesn't appear to be spyware ..The Digital Line Detection isn't really a required service and can be disabled, but it really isn't spyware. Another link that describes it as "NOT A Pest".

http://research.pestpatrol.com/Analyses/2004-08-29_045848.asp

One more that describes what it is:

Conexant NetWaiting Application V.2.5.6 supporting V92 Modem on Hold

Hope this helps.

Grif

- Collapse -
Yes...that's why I said could =
Jan 24, 2005 6:44PM PST

but you're right, disable Dlg.exe so it doesn't call on Bvrpdiag.dll and she shouldn't get the error message.

- Collapse -
The easiest solution
Jan 23, 2005 11:09PM PST

would be to reinstall the original program, reboot the computer, then go to Add-Remove Programs and use the uninstaller to properly uninstall the program....it will take the files it normally uses right along with the uninstall. For sure the first file isn't a windows file.....and I suspect the setupx.dll isn't either and it should take that file out the door with the others and doesn't need to be replaced.

TONI