Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: Hmmmm....

Author: KarinsDad

Date: 07:03:13 02/06/99

Go up one level in this thread


On February 06, 1999 at 01:55:38, Eugene Nalimov wrote:

>On February 05, 1999 at 21:51:00, James Robertson wrote:
>
>>On February 05, 1999 at 15:36:03, KarinsDad wrote:
>>
>>>On February 05, 1999 at 15:05:13, James Robertson wrote:
>>>
>>>>When I try to run my program under Windown NT, I get the following error:
>>>>
>>>>The procedure entry point  could not be located in the dynamic link library
>>>>KERNEL32.dll.
>>>>
>>>>I am compiling my program in Win95 with VC++ 5.0.
>>>>
>>>>Thanks for any help!
>>>>
>>>>James
>>>
>>>Your problem is most likely that you are making Win95 API calls which are not
>>>supported in WinNT.
>>>
>>>Check the documentation for any Microsoft calls that you are making to ensure
>>>that they work in both OSs. Usually, you can check the OS version in your code
>>>and call the approprate routine accordingly, however, if it is within a speed
>>>critical section, you will want to conditionally compile for the routines for
>>>the appropriate OS as opposed to checking them at runtime.
>>>
>>>Good Luck :)
>>>
>>>KarinsDad
>>
>>Darn. I went through my program and looked up every function I used (that I
>>didn't write), and in the documentation, every one is supposed to be WinNT
>>compatible. The only ones there was no listing for were the iostream classes.
>>Are they NT compatible?
>>
>>James
>
>Use DUMPBIN utility (it's part of MSVC distribution). Run
>    dumpbin /imports your_program.exe >t.txt
>    dumpbin /exports c:\winnt\system\kernel32.dll >q.txt
>After that in t.txt try to found function imported from
>kernel32 that is not present in export list in q.txt.
>
>Of course problem can be in one of the DLLs you are
>calling from your program...
>
>Eugene

If it is one of the DLLs, you could comment out the more obscure routines, one
at a time and recompile. Then run it NT. It doesn't matter if your code runs
correctly, you should get the same error once you hit the proper routine (and
possibly the DLL). Then at least you have an idea as to where the problem is.

I would try Eugene's technique first though, since it may find the problem much
faster.

KarinsDad




This page took 0 seconds to execute

Last modified: Thu, 15 Apr 21 08:11:13 -0700

Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.