#cl failing (0xc0000005)
4 messages in this thread
I didn't get any errors during the install, so I'd rather not just go through
the (time-consuming) task of comparing all the files on the hard disk with
those on the CD-ROM. I'd prefer to track it down from the analytical approach:
What exactly causes an application to fail with the message "Failed to
initialize (0xC0000005)?"
There are 2 Replies.
Theo,
All that the "failed to initialize" tells us is that one of the components
needed for initialization causes a problem. Since the compiler normally does
run successfully, I suspect that one of the .exe or .dll files is corrupt.
Julie
I do not see the first message of the problem but the subject looks just like
the one I am having.
I have the Store Bought shrink-wrap version of NT and the March BETA SDK, when
I link I get the following pop-up:
CL386.EXE: entry point not found
The procedure entry point RtlExAllocateHeap could not be found in the dynamic
link library ntdll.dll
Please help!
There is 1 Reply.
Garrett,
The March SDK will not run on the final release of Windows NT. Only
applications which were built with the March SDK (or later) will run on the
final release. The March SDK was not built with itself, hence it references
an old entry point which cannot be resolved.
There is nothing that can be done except to update your SDK or wait for
Visual C++ for Windows NT.
Sincerely,
Julie Solon
Microsoft Developer Support