Kernel32.dll - 95 vs. NT Problem

I've written a program which has been working great on Win95 platforms, however, now that I'm trying to get it to work on an NT 4.0 machine I get the following error message:
"The procedure entry point Thread32First could not be located in the dynamic link library kernal32.dll".
 I also get the same message for Thread32Next, Process32First, and Process32Next.  After exporting the functions for both versions of the library I see that the NT version doesn't even include these functions.  I have found no documentation on this, and no explanation for it.  It appears that Microsoft has done it again.

Any ideas?
ocuranceAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

vinniewCommented:
They have different threading models, you'll have to find their replacements.
0
chensuCommented:
These functions belong to Windows 95 Tool Help Library. Windows NT does not support these functions. In general, you should link them dynamically (::GetModuleHandle() and ::GetProcAddress()). You can find the documentations under
Win32 SDK\Programming Guides and Tools\Programmer's Guide to Windows 95\Using Windows 95 Features\Tool Help Library.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
vinniewCommented:
Based on the comments here I don't understand what needs to be done to get around this?  Does "Link them dynamically" mean these functions still exist somewhere and I should just make the calls dynamically, or do I need to distribute the missing functions?  And I haven't a clue about using the dynamic data key of the registry, I wouldn't know where to begin.  

I don't know where these functions are being called, or even what they do.  Is there no way to simply emulate these calls, replace the missing functions, or something of the sort?  I'm in a bit of a bind and left hanging because 32bit functions didn't get ported from 95 to NT.  What's up with that?

Thanks
0
ocuranceAuthor Commented:
You cannot use these functions in NT as they do not exist in NT. You cannot distribute them from 95, because they are integrated into the operating system.

If you want to use your program on both 95 and NT you will have to link to them dynamically on a 95 system, so you don't get an error message when starting your program on an NT machine.

What do you use the functions for? Most probably you can do the same thing in NT using the HKEY_PERFORMANCE_DATA key in the registry.
0
y96andhaCommented:
y96andha has explained well.

You may find more useful information from Win32 SDK documentations about System Services\Performance Monitoring and some samples under Windows SDK Samples\Windows NT Utilities.

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Development

From novice to tech pro — start learning today.