FIX UPDATE: for NODv2 install problems due to MSVCRT.DLL errors.

CAUSE
One possible cause of this error is that the application has written past the block of memory that is owned by a particular object. The small-block heapmemory manager that ships with the Visual C++ 6.0 run-time libraries incorporates heap control structures within the small-block heap. Overwriting the memory block changes small-block heap pointer addresses, effecting a bad pointer and possibly a fault in Msvcrt.dll when the pointer is referenced

RESOLUTION
Application vendors need to ensure that their applications are using the C run-time small-block heap correctly.

To help customers who are experiencing this problem in their third-party applications, Microsoft has released a new C run-time dynamic-link library (DLL), Msvcrt.dll, which implements two heap managers: the Visual C++ version 5.0-compatible heap manager and the Visual C++ version 6.0-compatible heap manager. Msvcrt.dll detects which version of Visual C++ your application is built with, and uses the appropriate heap manager for that application. If the version is Visual C++ 6.0 or greater, the Visual C++ 6.0-compatible heap manager is used; if the version is earlier than version 6.0, the Visual C++ 5.0-compatible heap is used.

Visual Studio 6.0 users can get the new Msvcrt.dll file by installing the latest Microsoft Visual Studio Service Pack. If you are not using Visual Studio, install the Microsoft Libraries Update; for additional information, see the following article in the Microsoft Knowledge Base and for download:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;197298

Download:
http://www.microsoft.com/windows98/downloads/contents/WURecommended/S_WUFeatured/Libraries/Default.asp


rgds,

Martin

 

Hi Martin,

thx. for the info.

jan

 

Hi Martin

There were reported similiar problems which led to crash in msvcrt.dll on

windows 9x/me. I've reproduced the problem, and it was caused indirectly by

imon. In fact, it was conflict between IMON and another program using the same

winsock hook technique. In that case it was drwhook.dll file, which is part of

DrWeb antivirus. There is/was version of DrWeb, which has inscorrectly

uninstalled itself and left the this hook registered after uninstallation.

This might be also your case. This problem was discussed somewhere in v2beta

forum, which is still available.
If you are not sure, if this is your problem, send PM to jan and ask him for

sporder.exe . He will give you instructions what to do.
Regards

Tomas
IMON developer

 

Hi Tomas,

I do not have DrWeb installed on my WinME, could there be another file that could cause trouble??

Can you tell me what this Sporder.exe is about??

thanks,

Martin

 

Hi Martin,

the sporder.exe tell us more about the Windows Sockets Configuration - Service providers.

I've already sent it to you.

Thanks,

jan

 

Hi Jan, i noticed that, but what will that tell me
Or what kind of info will it give me, and how can this info help me wiith the install problem

Thanks Jan,

rgds,
Martin

 

Hi Martin,

it can help us to find where is the possible conflict.

Thanks,

jan

 

Copy that Jan,

thanks,
Martin

 

Martin,

I sent you a PM.

Thx.,

jan