VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- How To / Troubleshooting (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=2)
-- Hotsync causes MSVCRT.DLL error (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=24643)

Hotsync causes MSVCRT.DLL error

Hello --

I am unable to hotsync. I get an error saying that Hotsync has caused an error in MSVCRT.DLL and will now close.

I un- and reinstalled Hotsync several times to no avail.

Can anyone help?

Thanks!
Jay
AdventureGrrl!
Building a Boat & a Dream
http://www.adventuregrrl.com/

__________________
Jay
Building a Boat & a Dream
http://www.adventuregrrl.com

Welcome to DLL Hell

I've had similiar problems with other applications causing same error. Usually traced to another program install that overwrote MSVCRT.DLL with a newer version that causes other programs that use the older version to crash.

Following search on MSDN turned up this possible solution. There are over 200 search hits on this subject.


http://support.microsoft.com/suppor...H&SPR=MSALL

PRB: Some System DLLs Are Only Seen in the System Directory

--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Windows 98

--------------------------------------------------------------------------------


SYMPTOMS
Windows 98 only looks in the \Window\System directory for some system DLLs. For example, if MSVCRT.dll or MFC40.dll are installed in an application's directory, but not in the system directory as expected, the application will not see the DLLs even though they exist in the same directory.



CAUSE
Windows 98 defines a registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\SessionManager\KnownDLLs
If a .dll name is placed under this registry setting, Windows 98 only looks in the system directory for that file. This enhances performance. If you remove the registry key, Windows 98 will find the DLL in the application directory.



RESOLUTION
Remove the registry key for the DLL if this is a problem.



STATUS
This behavior is by design.


Always Backup your registry before removing keys!!


Also try searching for MSVCRT.DLL and see how many hits you get. Some application installs will move replaced DLL's to a backup directory.

If, for instance, you are running Win98, you can recopy the DLL from the Installation CD by using the expand program.

This DLL problem with Windows has been somewhat alieviated by Win2000 and XP that provide for side-by-side DLL usage.

DOTNET has eliminated this problem, but we won't see DOTNET upgrades to programs anytime soon.