OS incompatibility problem
-
:)I have developed a software using visual C++ 5.0. It works fine in Windows 95 and Windows 98. It does not work when executed under Windows 2000. The error message is as below: "The instruction at "0x10217a1f" referenced at "0x0043c1a0. The memory could not be "written". Click on OK to terminate the program Click on CANCEL to debug the program" Please help me out from this problem.: G. S. Gupta
-
:)I have developed a software using visual C++ 5.0. It works fine in Windows 95 and Windows 98. It does not work when executed under Windows 2000. The error message is as below: "The instruction at "0x10217a1f" referenced at "0x0043c1a0. The memory could not be "written". Click on OK to terminate the program Click on CANCEL to debug the program" Please help me out from this problem.: G. S. Gupta
Well Win9x and Win2k are not directly related. Win9x is based on DOS, while Win2k is based on NT. You will first want to start by installing VC++ on a Win2k box and debug the code there. If this is not posible then you are going to have to put some more information in your code around the area where you suppect the error to be so it outputs to the console and have the person using this on Win2k keep running it for you. Eitherway you have to find the line(s) of code where you are doing something bad to Win2k. Then you need you look at the platform SDK documentation for Win2k and go over this part of your code, and either find a compatible fix that will work on Win9x and Win2k or not support Win2k/XP or to privide differnt version of your application, one for Win9x and one for Win2k. I hope this helps. FYI, that error message not helpful because it dealing with memory locations in RAM that are system dependent. Aalst
-
Well Win9x and Win2k are not directly related. Win9x is based on DOS, while Win2k is based on NT. You will first want to start by installing VC++ on a Win2k box and debug the code there. If this is not posible then you are going to have to put some more information in your code around the area where you suppect the error to be so it outputs to the console and have the person using this on Win2k keep running it for you. Eitherway you have to find the line(s) of code where you are doing something bad to Win2k. Then you need you look at the platform SDK documentation for Win2k and go over this part of your code, and either find a compatible fix that will work on Win9x and Win2k or not support Win2k/XP or to privide differnt version of your application, one for Win9x and one for Win2k. I hope this helps. FYI, that error message not helpful because it dealing with memory locations in RAM that are system dependent. Aalst