VC++ 6.0 and XP
-
Need some help. I have created a .dll library for an AI technology and have tested it on 98/2000 & ME OS. Project built using VC++ 6.0. I have someone having difficulty running on XP - what would the problem tend to be - memory handling? Never used XP and do not have it available. What would be so different? Do I need to go to .Net? Any help greatly appreciated! Thanks Mike http://www.ccoreinnovations.com
-
Need some help. I have created a .dll library for an AI technology and have tested it on 98/2000 & ME OS. Project built using VC++ 6.0. I have someone having difficulty running on XP - what would the problem tend to be - memory handling? Never used XP and do not have it available. What would be so different? Do I need to go to .Net? Any help greatly appreciated! Thanks Mike http://www.ccoreinnovations.com
If an app runs on W2k it should run on XP without a problem. The problems you may encounter are: 1) Permissions. Your user, for example, may need to be logged in as an Administrator. 2) Fast user switching. However, if the app runs using W2K terminal services, it should run on XP. (This is usually only a big issue if you used shared memory and global/local named synchronization objects.) 3) DLL Hell. If you are using the good old MFC 5/6 DLLs and they are out-of-sync on the XP box. (I've written many apps using VC6 that run in all environments. Never had a problem that weren't developer/user errors.) Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
-
If an app runs on W2k it should run on XP without a problem. The problems you may encounter are: 1) Permissions. Your user, for example, may need to be logged in as an Administrator. 2) Fast user switching. However, if the app runs using W2K terminal services, it should run on XP. (This is usually only a big issue if you used shared memory and global/local named synchronization objects.) 3) DLL Hell. If you are using the good old MFC 5/6 DLLs and they are out-of-sync on the XP box. (I've written many apps using VC6 that run in all environments. Never had a problem that weren't developer/user errors.) Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
-
Thanks Joe! But about the out-of-sync DLL's, how do you fix that!? Can you lead me to a source? Mike
You could compile the DLL statically (which might be a problem if the App is linked dynamically), you can ship the offending DLL with your DLL--as long as they're in the same directory in XP, the local DLL will be used. The final option is create an install package. To find out if DLLs are a problem, VC6 comes with an applet called Depends.exe. Use this to find your DLL dependencies and then get the versions of the same DLLs in XP and see if, for example, msvcrt.dll is out of date. Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke