• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Vista startup error 'dhtml.exe entry point not found'

Kadence

Senior member
When booting Vista 64 I'm now getting the error:

'dhtml.exe - Entry Point Not Found'
'The procedure entry point __iob_func could not be located in the dynamic link library MSVCR70.dll'

I hadn't rebooted for a few days when this appeared on a reboot. There was an msvcr70.dll in the C:\Windows directory. I googled the error and read something about it being located in the system or System32 folders, so I copied and pasted it to both those folders, but the error remained. I then tried downloading the file and pasted it in the Windows, Windows\system, and Windows\System32 folders (backed up the original), but that didn't solve the error either.

Also on reboot it says the HP monitor application 'HP My Display has stopped working' after I click OK for the dhtml.exe error. And if I manually try to start the application I get the .dll error again, so that is at least one app that needs it.

What is this error, and how might I fix it?
 
I have the same monitor and same problem, though using Windows Vista Home Basic, 32-bit version. I dont have a fix yet.

According to process explorer, the offending program is located here:
C:\Program Files\Portrait Displays\HP My Display\DTHtml.exe

It was run with these commandline arguments:
-Customer=HPW -startup_folder
 
Oh the problem was my brand new out of the box dell pc with vista home basic had a version c:\windows\system32\msvcr70.dll dating from 2000. In the HP My Display directory there is a newer one (2002), however the HP software uses this only if there isn't one already in the system path. So it uses the old one and fails when it tries to use a function that isn't in the old interface. This is an error in the HP software - if it requires a specific version of the dll, and ships with it, it _should_ be using it as a priority.
 
Back
Top