Why is it that when I use the GetCurrentHwProfile() I keep getting this error from my compiler. Incidentally, I am using Windows XP and the compiler is VS6.

error C2065: 'GetCurrentHwProfile' : undeclared identifier.

The same message also appears when I use the HW_PROFILE_INFO.

error C2065: 'HW_PROFILE_INFO' : undeclared identifier.

I have used the correct header files but still I keep getting the errors.

I then decided to declare both the structure and the function explicitly in the application and naturally enough the program compiled without any complaints but the output was pure gibberish.

What is happening and more importantly why?

Oh! yes, I did use the example in toto given by Microsoft with the same result.

Thanks.

: Why is it that when I use the GetCurrentHwProfile() I keep getting
: this error from my compiler. Incidentally, I am using Windows XP and
: the compiler is VS6.
:
: error C2065: 'GetCurrentHwProfile' : undeclared identifier.
:
: The same message also appears when I use the HW_PROFILE_INFO.
:
: error C2065: 'HW_PROFILE_INFO' : undeclared identifier.
:
: I have used the correct header files but still I keep getting the
: errors.
:
: I then decided to declare both the structure and the function
: explicitly in the application and naturally enough the program
: compiled without any complaints but the output was pure gibberish.
:
: What is happening and more importantly why?
:
: Oh! yes, I did use the example in toto given by Microsoft with the
: same result.
:
: Thanks.
:

From what I can tell from http://msdn.microsoft.com/en-us/library/ms724311(VS.85).aspx you need to "(..) define the _WIN32_WINNT macro as 0x0400 or later." (last line of text before the example).
I think they do this to make you aware that this is a highly version specific API.
Best Regards,
Richard

The way I see it... Well, it's all pretty blurry

: : Why is it that when I use the GetCurrentHwProfile() I keep getting
: : this error from my compiler. Incidentally, I am using Windows XP and
: : the compiler is VS6.
: :
: : error C2065: 'GetCurrentHwProfile' : undeclared identifier.
: :
: : The same message also appears when I use the HW_PROFILE_INFO.
: :
: : error C2065: 'HW_PROFILE_INFO' : undeclared identifier.
: :
: : I have used the correct header files but still I keep getting the
: : errors.
: :
: : I then decided to declare both the structure and the function
: : explicitly in the application and naturally enough the program
: : compiled without any complaints but the output was pure gibberish.
: :
: : What is happening and more importantly why?
: :
: : Oh! yes, I did use the example in toto given by Microsoft with the
: : same result.
: :
: : Thanks.
: :
:
: From what I can tell from
: http://msdn.microsoft.com/en-us/library/ms724311(VS.85).aspx you
: need to "(..) define the _WIN32_WINNT macro as 0x0400 or later."
: (last line of text before the example).
: I think they do this to make you aware that this is a highly version
: specific API.
: Best Regards,
: Richard
:
: The way I see it... Well, it's all pretty blurry

I tried to use that ID in both the source and compiler options, but VS kept this _WINNT... "unnoticed", so I used the brute force approach - simply open these compiler headers and copy/paste the definitions you need into your code. Protect with ifdef's for next compiler.

: : : Why is it that when I use the GetCurrentHwProfile() I keep getting
: : : this error from my compiler. Incidentally, I am using Windows XP and
: : : the compiler is VS6.
: : :
: : : error C2065: 'GetCurrentHwProfile' : undeclared identifier.
: : :
: : : The same message also appears when I use the HW_PROFILE_INFO.
: : :
: : : error C2065: 'HW_PROFILE_INFO' : undeclared identifier.
: : :
: : : I have used the correct header files but still I keep getting the
: : : errors.
: : :
: : : I then decided to declare both the structure and the function
: : : explicitly in the application and naturally enough the program
: : : compiled without any complaints but the output was pure gibberish.
: : :
: : : What is happening and more importantly why?
: : :
: : : Oh! yes, I did use the example in toto given by Microsoft with the
: : : same result.
: : :
: : : Thanks.
: : :
: :
: : From what I can tell from
: : http://msdn.microsoft.com/en-us/library/ms724311(VS.85).aspx you
: : need to "(..) define the _WIN32_WINNT macro as 0x0400 or later."
: : (last line of text before the example).
: : I think they do this to make you aware that this is a highly version
: : specific API.
: : Best Regards,
: : Richard
: :
: : The way I see it... Well, it's all pretty blurry
:
: I tried to use that ID in both the source and compiler options, but
: VS kept this _WINNT... "unnoticed", so I used the brute force
: approach - simply open these compiler headers and copy/paste the
: definitions you need into your code. Protect with ifdef's for next
: compiler.
:
:
:I did what you suggested AsmGuru62 but to no avail. I opened winbase.h :and did a copy and paste of the relevant section in my application but to
:no avail. I kept getting the same error messages. To cut a long story :short, I merely rewrote the application in Visual Studio 2008 and I had :it running with no hassle. That it worked is satisfying but I still would :like it to work in VSC++6. Hope I can manage that. Then my efforts would :indeed be satisfying.

: :I did what you suggested AsmGuru62 but to no avail. I opened
: winbase.h :and did a copy and paste of the relevant section in my
: application but to
: :no avail. I kept getting the same error messages. To cut a long
: story :short, I merely rewrote the application in Visual Studio 2008
: and I had :it running with no hassle. That it worked is satisfying
: but I still would :like it to work in VSC++6. Hope I can manage
: that. Then my efforts would :indeed be satisfying.
:

Riiight... read over that part.
The Visual C++ 6.0 'package' is meant for Windows 98 and NT 4.0 (I believe). It doesn't know about XP and certainly not about new features introduced later.
Still, copying all the relevant code parts should do the trick. It should at the very least change the error message(s) to something else.
Try copying all the relevant parts to your own include header, then try to compile and fix any errors the compiler gives you. If you need help, you can post the source code and error messages here.
Best Regards,
Richard

The way I see it... Well, it's all pretty blurry

: : :I did what you suggested AsmGuru62 but to no avail. I opened
: : winbase.h :and did a copy and paste of the relevant section in my
: : application but to
: : :no avail. I kept getting the same error messages. To cut a long
: : story :short, I merely rewrote the application in Visual Studio 2008
: : and I had :it running with no hassle. That it worked is satisfying
: : but I still would :like it to work in VSC++6. Hope I can manage
: : that. Then my efforts would :indeed be satisfying.
: :
:
: Riiight... read over that part.
: The Visual C++ 6.0 'package' is meant for Windows 98 and NT 4.0 (I
: believe). It doesn't know about XP and certainly not about new
: features introduced later.
: Still, copying all the relevant code parts should do the trick. It
: should at the very least change the error message(s) to something
: else.
: Try copying all the relevant parts to your own include header, then
: try to compile and fix any errors the compiler gives you. If you
: need help, you can post the source code and error messages here.
: Best Regards,
: Richard
:
: The way I see it... Well, it's all pretty blurry
:
:What freaks me out with this API is that it is part of the compiler.
:When I write the function it registers and shows the parameters that are :needed. But it comes up with the "undefined identifier" when I attempt to compile it.

: What freaks me out with this API is that it is part of the compiler.
: When I write the function it registers and shows the parameters
: that are :needed. But it comes up with the "undefined identifier"
: when I attempt to compile it.
:

You're in luck: I happen to be behind a computer with VC++ 6.0 installed.
It took a bit of trying, and some weird weird errors... but this approach worked for me:

In stdafx.h:

#define WIN32_LEAN_AND_MEAN
//For GetCurrentHwProfile
#define _WIN32_WINNT 0x0500
#include <windows.h>

Then you might need to force it to recompile all. I got the impression from the weird errors I got that later disappeared that some things are less smooth than they should be. After this change, recompile the entire project (possibly force Rebuild All) and it should work. It did for me.
Good luck
Best Regards,
Richard

The way I see it... Well, it's all pretty blurry

: : What freaks me out with this API is that it is part of the compiler.
: : When I write the function it registers and shows the parameters
: : that are :needed. But it comes up with the "undefined identifier"
: : when I attempt to compile it.
: :
:
: You're in luck: I happen to be behind a computer with VC++ 6.0
: installed.
: It took a bit of trying, and some weird weird errors... but this
: approach worked for me:
:
: In stdafx.h:
:

: 
: #define WIN32_LEAN_AND_MEAN
: //For GetCurrentHwProfile
: #define _WIN32_WINNT 0x0500
: #include <windows.h>
: 

:
:
: Then you might need to force it to recompile all. I got the
: impression from the weird errors I got that later disappeared that
: some things are less smooth than they should be. After this change,
: recompile the entire project (possibly force Rebuild All) and it
: should work. It did for me.
: Good luck
: Best Regards,
: Richard
:
: The way I see it... Well, it's all pretty blurry


That ...LEAN_AND_MEAN... thing is not good. Using it excludes some low level (or maybe rarely used, like that hardware profile function) stuff from Win32 headers. I remember, when creating projects with VC++ 6.0 - the first thing I was doing was opening stdafx.h and deleting that line.

:
: That ...LEAN_AND_MEAN... thing is not good. Using it excludes some
: low level (or maybe rarely used, like that hardware profile
: function) stuff from Win32 headers. I remember, when creating
: projects with VC++ 6.0 - the first thing I was doing was opening
: stdafx.h and deleting that line.
:

In this case LEAN_AND_MEAN does nót excluse the HW profile API.
But it is sort of a good thing. It cleans up some of the excess functions. Not a problem if you're aware of it and what it does. My policy: remove it once I find that I need non-standard stuff.
Best Regards,
Richard

The way I see it... Well, it's all pretty blurry

:
: :
: : That ...LEAN_AND_MEAN... thing is not good. Using it excludes some
: : low level (or maybe rarely used, like that hardware profile
: : function) stuff from Win32 headers. I remember, when creating
: : projects with VC++ 6.0 - the first thing I was doing was opening
: : stdafx.h and deleting that line.
: :
:
: In this case LEAN_AND_MEAN does nót excluse the HW profile API.
: But it is sort of a good thing. It cleans up some of the excess
: functions. Not a problem if you're aware of it and what it does. My
: policy: remove it once I find that I need non-standard stuff.
: Best Regards,
: Richard
:
: The way I see it... Well, it's all pretty blurry
:
:Well, well I put the value _WIN32_WINNT 0x0500 in the stdafx.h file and wonder of wonders the program was running. Well this has taught me something new. Many thanks BitByBit_Thor.