VC program compiled on XP Home does not run on XP Pro?!?!
-
Hello, I am experiencing a very strange "phenomenon": When I compile a Visual C++ program in VS 2002 (no GUI, just console output) into an exe on XP Home it runs smoothly. However, when I give this to someone with an XP Pro machine, it does not run but stops with an exception error message box. We have tested this on 3 different XPPro boxes now and everywhere the same result. When I compile the program with the same VS 2002 installed on a XPPro machine into an exe, it runs BOTH on XPPro and XPHome. I am really puzzled and have no clue why this happens. Seems that in terms of OS at compilation time the exe's are downward compatible but not upward. Could anybody please help me and tell me what is going on? Thank you so much in advance, Tony
-
Hello, I am experiencing a very strange "phenomenon": When I compile a Visual C++ program in VS 2002 (no GUI, just console output) into an exe on XP Home it runs smoothly. However, when I give this to someone with an XP Pro machine, it does not run but stops with an exception error message box. We have tested this on 3 different XPPro boxes now and everywhere the same result. When I compile the program with the same VS 2002 installed on a XPPro machine into an exe, it runs BOTH on XPPro and XPHome. I am really puzzled and have no clue why this happens. Seems that in terms of OS at compilation time the exe's are downward compatible but not upward. Could anybody please help me and tell me what is going on? Thank you so much in advance, Tony
Tony Westminster wrote: Could anybody please help me and tell me what is going on? A lot depends on what the exception error is. Is this an MFC app or a pure Win32 app. Do you use the CommonControls dlls. Michael But you know when the truth is told, That you can get what you want or you can just get old, Your're going to kick off before you even get halfway through. When will you realise... Vienna waits for you? - "The Stranger," Billy Joel
-
Hello, I am experiencing a very strange "phenomenon": When I compile a Visual C++ program in VS 2002 (no GUI, just console output) into an exe on XP Home it runs smoothly. However, when I give this to someone with an XP Pro machine, it does not run but stops with an exception error message box. We have tested this on 3 different XPPro boxes now and everywhere the same result. When I compile the program with the same VS 2002 installed on a XPPro machine into an exe, it runs BOTH on XPPro and XPHome. I am really puzzled and have no clue why this happens. Seems that in terms of OS at compilation time the exe's are downward compatible but not upward. Could anybody please help me and tell me what is going on? Thank you so much in advance, Tony
This is happens to me also too. I is compilate on my office combuter (XP) and is runs fine also on home computer. But is compilate on home computer, is not run OK on office computer. I having the problem with spin controls jumping more than by one. Is also other problem that I fixed by moving some code from PreCreate to Create.
-
Tony Westminster wrote: Could anybody please help me and tell me what is going on? A lot depends on what the exception error is. Is this an MFC app or a pure Win32 app. Do you use the CommonControls dlls. Michael But you know when the truth is told, That you can get what you want or you can just get old, Your're going to kick off before you even get halfway through. When will you realise... Vienna waits for you? - "The Stranger," Billy Joel
Thank you very much for your quick answer. I am not quite sure how someone can tell if it is an MFC app or pure Win32 app? I assume you see it if it contains MFC*.dll? I used depends 2.1 to see which DLL's my App uses. I have attached below a list of all used DLLs. Note that Column1 and Column2 contain the same list of dll's, I have just sorted Column2 by name to facilitate analysis. Thank you so much for any help on this. If I cannot find an answer on why this happens, do you think it is safe to say: "Compiled exes will always work on XP Home when compiled on XP Pro but not necessarily the other way around." If I knew this was true, I could always only compile the progs on XP Pro and be on the safe side. Thanks again, Tony MPR.DLL ACTIVEDS.DLL ADVAPI32.DLL ADSLDPC.DLL COMCTL32.DLL ADVAPI32.DLL COMDLG32.DLL ADVPACK.DLL GDI32.DLL APPHELP.DLL IPHLPAPI.DLL ATL.DLL KERNEL32.DLL AUTHZ.DLL MSCOREE.DLL BROWSEUI.DLL MSVCP60.DLL CABINET.DLL MSVCRT.DLL CDFVIEW.DLL NTDLL.DLL CERTCLI.DLL OLE32.DLL CFGMGR32.DLL OLEACC.DLL CLUSAPI.DLL OLEAUT32.DLL COMCTL32.DLL RPCRT4.DLL COMDLG32.DLL SHELL32.DLL CREDUI.DLL SHLWAPI.DLL CRYPT32.DLL USER32.DLL CRYPTUI.DLL WINSPOOL.DRV CSCDLL.DLL WS2_32.DLL DBGHELP.DLL WS2HELP.DLL DEVMGR.DLL ACTIVEDS.DLL DHCPCSVC.DLL ADSLDPC.DLL DNSAPI.DLL ADVPACK.DLL DUSER.DLL APPHELP.DLL EFSADU.DLL ATL.DLL ESENT.DLL AUTHZ.DLL GDI32.DLL BROWSEUI.DLL GDIPLUS.DLL CABINET.DLL IMAGEHLP.DLL CDFVIEW.DLL IMM32.DLL CERTCLI.DLL INETCOMM.DLL CFGMGR32.DLL IPHLPAPI.DLL CLUSAPI.DLL KERNEL32.DLL CREDUI.DLL LINKINFO.DLL CRYPT32.DLL LZ32.DLL CRYPTUI.DLL MFC42U.DLL CSCDLL.DLL MLANG.DLL DBGHELP.DLL MOBSYNC.DLL DEVMGR.DLL MPR.DLL DHCPCSVC.DLL MPRAPI.DLL DNSAPI.DLL MPRUI.DLL DUSER.DLL MSASN1.DLL EFSADU.DLL MSCOREE.DLL ESENT.DLL MSGINA.DLL GDIPLUS.DLL MSHTML.DLL IMAGEHLP.DLL MSI.DLL IMM32.DLL MSIMG32.DLL INETCOMM.DLL MSOERT2.DLL LINKINFO.DLL MSRATING.DLL LZ32.DLL MSSIGN32.DLL MFC42U.DLL MSVCP60.DLL MLANG.DLL MSVCRT.DLL MOBSYNC.DLL MSWSOCK.DLL MPRAPI.DLL NETAPI32.DLL MPRUI.DLL NETCFGX.DLL MSASN1.DLL NETMAN.DLL MSGINA.DLL NETPLWIZ.DLL MSHTML.DLL NETRAP.DLL MSI.DLL NETSHELL.DLL MSIMG32.DLL NETUI0.DLL MSOERT2.DLL NETUI1.DLL MSRATING.DLL NETUI2.DLL MSSIGN32.DLL NTDLL.DLL MSWSOCK.DLL NTDSAPI.DLL NETAPI32.DLL NTLANMAN.DLL NETCFGX.DLL ODBC32.DLL NETMAN.DLL OLE32.DLL NETPLWIZ.DLL OLEACC.DLL NETRAP.DLL OLEAUT32.DLL NETSHELL.DLL OLEDLG.DLL NETUI0.DLL OLEPRO32.DLL NETUI1.DLL POWRPROF.DLL NETUI2.DLL PRINTUI.DLL NTDSAPI.DLL
-
Hello, I am experiencing a very strange "phenomenon": When I compile a Visual C++ program in VS 2002 (no GUI, just console output) into an exe on XP Home it runs smoothly. However, when I give this to someone with an XP Pro machine, it does not run but stops with an exception error message box. We have tested this on 3 different XPPro boxes now and everywhere the same result. When I compile the program with the same VS 2002 installed on a XPPro machine into an exe, it runs BOTH on XPPro and XPHome. I am really puzzled and have no clue why this happens. Seems that in terms of OS at compilation time the exe's are downward compatible but not upward. Could anybody please help me and tell me what is going on? Thank you so much in advance, Tony
Tony Westminster wrote: Seems that in terms of OS at compilation time the exe's are downward compatible but not upward Absolutely not. It doesn't matter what OS you compile on. I could run VC 5 on Win 95, build a GUI app, and it would run on XP or 2K3 or whatever. It would help if you posted the error message. --Mike-- Personal stuff:: Ericahist | Homepage Shareware stuff:: 1ClickPicGrabber | RightClick-Encrypt CP stuff:: CP SearchBar v2.0.2 | C++ Forum FAQ ---- "That probably would've sounded more commanding if I wasn't wearing my yummy sushi pajamas." -- Buffy
-
Tony Westminster wrote: Seems that in terms of OS at compilation time the exe's are downward compatible but not upward Absolutely not. It doesn't matter what OS you compile on. I could run VC 5 on Win 95, build a GUI app, and it would run on XP or 2K3 or whatever. It would help if you posted the error message. --Mike-- Personal stuff:: Ericahist | Homepage Shareware stuff:: 1ClickPicGrabber | RightClick-Encrypt CP stuff:: CP SearchBar v2.0.2 | C++ Forum FAQ ---- "That probably would've sounded more commanding if I wasn't wearing my yummy sushi pajamas." -- Buffy
Mike, thank you very much. I get an error message box that says: "The application failed to initialize properly (0xc0000135). Click on OK to terminate the application." Do you have any idea what could cause this? Thanks, Tony
-
Mike, thank you very much. I get an error message box that says: "The application failed to initialize properly (0xc0000135). Click on OK to terminate the application." Do you have any idea what could cause this? Thanks, Tony
-
Hi, Ithink it's problem about some Upgrades!! Try this, Upgrade WinXP (That your prog. didn't work on) with FrameWork1.1 avalable in microsoft site and run your prog again I think it works good. Please tell me if this solve your problem. Yours Mamad,
Dear Mamad, thanks so much for your answer. I will try it out but doubt that it works. Why? Because I think that Framework 1.1 you are talking about is the .NET Framework. But I have coded in pure VC++, not VC++.NET. So I cannot really see how the framework would influence my native code (no IL). I will try it anyway. Thanks again, Tony