Click here to Skip to main content
16,018,818 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
Dear all, I'm encountering this strange phenomenon. I recently upgraded an old VS6 project to VS2008 on a Win7 64 bit pc. On my pc, with VS2008 installed, everything works just fine. But when I try to run the application on a WinXP SP3 pc, it instantly crashed due to an exception in mfc90.dll. The app built in VS6 works without any problem on the WinXP pc.
I installed on that pc the most recent VS2008 distributables. The strange thing is that running DependencyWalker in WinXP, it does say that I'm missing some dll's, but I also miss the same dll's when I run my VS6 application in WinXP, and still it works. But what's really strange, is that I can profile my VS2008 app on WinXP without any problem using DependencyWalker. It runs as it should be. But running the exe directly is impossible.
Does anyone have a clue? I must say that the pc running the app is an industrial pc with Intel Celeron processor. I hope this is not causing the problem.
Thanks in advance.
Posted
Updated 13-Nov-14 1:36am
v2
Comments
Richard MacCutchan 13-Nov-14 3:40am    
There are a number of libraries and features in Windows 7 that are not available in XP. You will need to go through your project to find out which ones they are.
Member 10611628 13-Nov-14 7:42am    
Hi Richard, thanks for the reply. Since my project is upgraded from VS6, I don't use new Win7 libraries nor features. By the way, the VS6 app, also built in Win7, runs without any problem. Remote debugging also works, as well as another project (not migrated) built in VS2008 on the Win7 machine.
Richard MacCutchan 13-Nov-14 8:05am    
Very interesting but that does not give us any more information to help you with. It is quite possible (and not unusual) that building projects on Windows 7 will include versions of libraries that are not installed on XP.
Member 10611628 13-Nov-14 8:23am    
True, but how do you explain that another project runs without any problem? It's the same visual studio, the same Win7 operating system and yet it runs. What more information can I give you? All I know is that when I run the exe through DependencyWalker, I see that all the dll's are loaded, and the app starts normally. But I'm not able to start it directly. Remote debugging also works.
I forgot to mention that the VS6-project initially started on WinXP, so I only load libraries known to WinXP.
Richard MacCutchan 13-Nov-14 8:49am    
I don't explain anything; as I said, we don't have enough information. And just because one application works, does not automatically mean that all others will do. You will have to do some debugging to find out exactly what is happening in this particular one.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900