The MASM Forum

Miscellaneous => The Orphanage => Topic started by: xanatose on September 09, 2015, 05:40:32 AM

Title: Dealing with old windows version.
Post by: xanatose on September 09, 2015, 05:40:32 AM
Recently I had a problem with a client that was using windows 2003. My software was using an API that was not present on that windows.  I do not have windows 2003 and the product was a dll for a server. so all that the client could tell me was error 127.

Is there a list somewhere on the additions to the API between each windows version?

Better yet, is there a tool that automatically detects what function are incompatible with each windows.
Title: Re: Dealing with old windows version.
Post by: dedndave on September 09, 2015, 07:19:50 AM
i think windows 2003 was the server version of XP - i could be wrong, there

the problem you are faced with is a huge documentation issue
i don't know of any clear-cut way to deal with it, either
many MSDN pages can even be misleading

but - the server versions are different, and may not support all functions

you didn't tell us which function - lol
Title: Re: Dealing with old windows version.
Post by: dedndave on September 09, 2015, 07:29:43 AM
there are older documents around
for example, windows 95 and 98 CHM files with API's listed

another way to go - get old copies of the PSDK and or MSDN library
Title: Re: Dealing with old windows version.
Post by: xanatose on September 09, 2015, 11:28:27 AM
Good idea, thanks. Just downloaded PSDK for windows 2003. Hopefully I will get link errors using this libraries and see what was the problem.
Title: Re: Dealing with old windows version.
Post by: dedndave on September 09, 2015, 12:36:00 PM
you can look in the header files (.h) and see what functions are supported
Title: Re: Dealing with old windows version.
Post by: sinsi on September 09, 2015, 08:42:24 PM
I've used a program called filealyzer, looks at the imports and whether they are in a particular windows version.
Title: Re: Dealing with old windows version.
Post by: xanatose on September 18, 2015, 09:46:02 AM
It was GetTickCount64. Only supported from Windows 2008
Changed to GetTickCount and logic for when it resets.