Windows API

Is there anywhere I can EASILY find how to translate Windows API calls to Windows NT API?
LVL 4
broadbentAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
MTroutwineConnect With a Mentor Commented:
Pellep statement is true.  There is a file called 'Win32api.csv' that ships with Visual Studio.  You can find it in the D:\Program Files\Microsoft Visual Studio\VC98\Lib\ folder.  It is in Excel spreadsheet format and has a column for the following:

Element (API Name)
Windows NT Version
Window CE
Windows
Win32s

(just to name a few)

Under these particular columns you can determine if the API is available for the O/S.  This is not a small file it contains 11,187 entries.
0
 
VBGuruCommented:
I think you got to check the SDK
0
 
PedroGCommented:
As i know, most of the Windows API's work in windows NT.

The diference resides in the fact that some win API's are only availiable for Win 95/98 other for win 98 and other for win NT.

Can you be a bit more specific, what realy is the API you whant to use in NT??
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
Erick37Commented:
Do you mean how do find out which APIs are available only for NT?  The API documentation will specify which platform the function is designed for.  Most APIs are designed for both operating systems.
0
 
Bob LearnedCommented:
Are you talking Windows 3.x to Windows NT?  If you are, then data types, such as Integer have been changed to Long (16-bit to 32-bit).  But this is not true for all API calls, so you have to be careful.
0
 
pellepCommented:
A word of caution. WinNT sp6 and above (Win2000) doesn't support 16-bit functionality any longer. That means that if you intend to run your program in the future it must be ported to Win32 API. When you say Windows API I presume you mean 16-bit API (Windows 3.11 and such).
The NT specific API revolves mostly around network- and security-specific functionality. Apart from that most functions lie under the Win32 API and is available both for ASCII and UNICODE. If your program only does GUI, db-access, disk-access, registry, socket-comm or other basic features you shouldn't have to worry about WinNT API, only Win32.
0
 
VBGuruCommented:
broadbent are you there?
0
 
broadbentAuthor Commented:
You guys are quick. I only just asked the q and already I have a conversation.

I've just started debugging a VB6 app in Windows NT and noticed some subtle changes in the Windows Registry.

eg HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics

MenuFont varies between Windows98 and WindowsNT.

Is there any reason for this?

0
All Courses

From novice to tech pro — start learning today.