Problem with registring server
-
Hi, I created an InProcServer(ToolBand.dll) on my Windows NT Wkts which works fine for NT Server4.0, Win98, 2K, and Me. This doesn't get installed on the setup of Win95 running IE5. I get error message "This function is only valid in Win32 mode". There were some "Ex" Registry API used in DllRegiserServer(). I've replaced it with normal API's i mean without "Ex", but the problem remains same. I get same error message with RegSetValue(..) API. Is there any compatibility issue? It seems that Windows 95 is not pure win32. Hey Any comments? Why its so ironical behaviour? Should I need to build this application on VC++ running on Windows 95? I there any registry key or service to get some Win32 services on Win95. I'm fed-up with this behaviour. Help me with any comments. --Sumit
-
Hi, I created an InProcServer(ToolBand.dll) on my Windows NT Wkts which works fine for NT Server4.0, Win98, 2K, and Me. This doesn't get installed on the setup of Win95 running IE5. I get error message "This function is only valid in Win32 mode". There were some "Ex" Registry API used in DllRegiserServer(). I've replaced it with normal API's i mean without "Ex", but the problem remains same. I get same error message with RegSetValue(..) API. Is there any compatibility issue? It seems that Windows 95 is not pure win32. Hey Any comments? Why its so ironical behaviour? Should I need to build this application on VC++ running on Windows 95? I there any registry key or service to get some Win32 services on Win95. I'm fed-up with this behaviour. Help me with any comments. --Sumit
Sumit PAndya wrote: It seems that Windows 95 is not pure win32. Yep. Win95/98/ME do not support the complete Win32 API. Much of the Unicode-versions of functions are flat-out missing, others are partially implemented (and will return the error you mention), and a few are implemented fully for COM use. It sounds like you are using an NT-or-greater-only function in your code. Take another look at the bottom of the MSDN help pages for information on what platforms support what functions. You can also put
#define _WIN32_WINDOWS = 0x0410 #define WINVER = 0x0400- Before all other includes in your StdAfx.h file to help check what functions you are using. (Look up those identifiers in MSDN for more information.) Peace! -=- James. -
Sumit PAndya wrote: It seems that Windows 95 is not pure win32. Yep. Win95/98/ME do not support the complete Win32 API. Much of the Unicode-versions of functions are flat-out missing, others are partially implemented (and will return the error you mention), and a few are implemented fully for COM use. It sounds like you are using an NT-or-greater-only function in your code. Take another look at the bottom of the MSDN help pages for information on what platforms support what functions. You can also put
#define _WIN32_WINDOWS = 0x0410 #define WINVER = 0x0400- Before all other includes in your StdAfx.h file to help check what functions you are using. (Look up those identifiers in MSDN for more information.) Peace! -=- James.Hi, It is a surprise knowledge that Win95 is not pure Win32 OS. Thanks for this information. Hey anyway I defined those system-variables but it didn't helped me out. I've verified all the API's and its documented for Win95 and later so as far documentation is concern there is no issue of lacking support. But Do you believe in M$ Documents ;-)? Personally I never, I've many bad experiences with false commitment and wrong information in documentation from M$. The main surprise for me is error in Registry API call, RegCreate..., which i've used in many of my softwares and was not creating any problem in those. But it stucked up in this development and with previously used API's but those were normal application and this is COM.... Grrrrrr.... Let me notify if you have another suggession on this. Regards, --Sumit
-
Hi, It is a surprise knowledge that Win95 is not pure Win32 OS. Thanks for this information. Hey anyway I defined those system-variables but it didn't helped me out. I've verified all the API's and its documented for Win95 and later so as far documentation is concern there is no issue of lacking support. But Do you believe in M$ Documents ;-)? Personally I never, I've many bad experiences with false commitment and wrong information in documentation from M$. The main surprise for me is error in Registry API call, RegCreate..., which i've used in many of my softwares and was not creating any problem in those. But it stucked up in this development and with previously used API's but those were normal application and this is COM.... Grrrrrr.... Let me notify if you have another suggession on this. Regards, --Sumit
Sumit Pandya wrote: The main surprise for me is error in Registry API call, RegCreate..., Please specify exactly how you are calling the failing function, what parameters you are passing in to it, and the total length of any string parameters. Peace! -=- James.