Click here to Skip to main content
15,898,134 members
Please Sign up or sign in to vote.
4.50/5 (2 votes)
See more:
Hi there,

I use Visual C++ 6.0 for my software - legacy software originally developed with MSVC 6.0.

Anyway was working fine in Windows 7 until today. Suddenly the program just won't start any more.

I can't think what the reason was. It suddenly stopped working, and I did a reboot, Windows did an update during the reboot but that can't be the reason, also I rolled back all the updates.

The error is:
CSS
Faulting application name: msdev.exe, version: 6.0.8168.1, time stamp: 0x35889589
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e211319
Exception code: 0xe06d7363
Fault offset: 0x0000b9bc
Faulting process id: 0x12e0
Faulting application start time: 0x01cdab02f8cfd6fe
Faulting application path: C:\Programs\Microsoft Visual Studio\Common\MSDev98\Bin\msdev.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 37e889fb-16f6-11e2-a335-f0def18ffc44


Also when it first started, got this error as well - this one first then the previous one (but don't get this one any more)

CSS
Faulting application name: msdev.exe, version: 6.0.8168.1, time stamp: 0x35889589
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000005
Fault offset: 0x000344ec
Faulting process id: 0x3f9c
Faulting application start time: 0x01cda7c98218d338
Faulting application path: C:\Programs\Microsoft Visual Studio\Common\MSDev98\Bin\msdev.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 8aa702da-16c3-11e2-a5e3-f0def18ffc44


I can run it in XP mode still - so could do that e.g. to make the release build. But it's not much good for debugging, as my debugged program also runs in XP mode if I do that (with 256 colour too actually).

I want to be able to debug my software in MSVC 6.0 with both msdev.exe and my debugged program running as Windows 7 programs. And despite warnings about compatibility was able to do that just fine until 1pm today (UK time).

Just have no idea what changed and why it stopped working. Anyone got any ideas, anyone encountered anything like this?

Any help or ideas or suggestions much appreciated, thanks.

Robert (Walker)
Posted
Updated 15-Oct-12 8:45am
v2
Comments
fjdiewornncalwe 15-Oct-12 15:10pm    
I think it is time for you to upgrade your solution to a newer version of Studio.
Richard MacCutchan 15-Oct-12 15:27pm    
I think you are likely to get only one answer to this. It is always possible that a recent Windows 7 update has had some adverse effect, but it's unlikely that you will get it fixed. Upgrade now before it's too late.
Sergey Alexandrovich Kryukov 15-Oct-12 15:29pm    
Could you run it under debugger to see real exceptions?
--SA
Robert Inventor 15-Oct-12 15:35pm    
I'm already using the Microsoft Visual Studio 2010 Express.

But much prefer Visual 6.0 - there was a major change in the interface after 6.0 which is partly why many still use it - the last version of the older interface (which I find much easier to use).

It's also the expense - £500 to update to the latest version of the full product - which equates to about 10 weeks of income from the software I develop. I have just finished building a house and have very little left in the bank after the build - and with my current low levels of income, would need to save up for maybe six months or more before I'd feel comfortable about spending that much on the compiler, as I have other expenses to find as well.

Especially also since it was working just fine until today. If worse comes to worse will continue to use it in XP mode, and on my netbook too, but - what could it be?

Anyone got any ideas why it might suddenly stop working like this? I wondered if it meant that some of the core dlls of Windows have changed - but why? I hadn't even just installed a program or anything - did install some programs a couple of days ago but not today. Automatic Windows updates today but they had only downloaded, not yet installed when the error first occurred, and after uninstalling them all again it is still there. System File Checker shows no problems at all. The last Windows update was on the 13th two days ago.

I also wondered if Norton might be preventing it from running, as it sometimes silently prevents programs from running and of course does silent updates and had an update today - but nothing shows up in its event history.

What could have changed? Anything else I can check? Anyone got any ideas?
Robert Inventor 15-Oct-12 16:06pm    
Just remembered a bit more (after looking at my notes for the last debug session). I was working with the debugger. Did a simple edit of the resource file with the resource editor. MSVC then crashed. It does that occasionally though not often. I started it up again and nothing happened. Also tried it with a backup of my project in case the current project was causing the crash and that also didn't work. That's when I tried the reboot. So - beginning to wonder if MSVC itself did something when it crashed that caused the issue, and - damaged registry is maybe my top suspicion now, or something like that?? Any thoughts?

Not too much information to help here, but…

The most usual problem with legacy code while executed in Windows 7 is the permission issue. To figure out it this is the case, please first try to run the application "as administrator". Having logged in as administrator is not enough. You need to elevate the application privileged bases on the user privileges. Here are the options you have:
http://www.sevenforums.com/tutorials/11841-run-administrator.html[^].

Let's assume the application started to work. It means, the permission is the problem. Please check up all the directories and files you are trying to work with. Some of them may be illegal in Windows 7. For a check up, you can do some administrative work and ease up permission of the file system objects involved. But it's much better to modify the code to make it legitimate. There are no cases, for example, when any hard-coded path names can work. Path names should always be calculated during runtime, using some configuration files, user input and other modifiable data. You can also use the executable directory (for read-only stuff only) and the "special folders" associated with the user accounts (and also those under "all users" directory).

—SA
 
Share this answer
 
Comments
Robert Inventor 15-Oct-12 16:00pm    
Thanks, actually I'm doing that already. I run it as administrator already. The thing is though - I can't start up msdev at all now. I can't even get to the blank page with no project loaded. When I click to run it, then nothing happens.

Also - the problem is with msdev.exe itself - it won't run any more. My own software is running just fine in Windows 7, no problems compiling up to date Windows 7 code in MSVC 6.0.

In detail - I get the usual message when I try to run Visual Studio 6.0 "Do you want the following program from an unknown publisher to make changes to your computer". That's just because I elevated its privileges to administrator and of course as legacy software not signed by microsoft.

The process msdev.exe briefly appears in task manager then disappears then if I go to the error log I get the error message posted above.

And - it was working fine until earlier today, I was using it to debug my programs no issues at all, well minor issues but I had sorted those all out long ago - things like the paths and setting the application to always run with admin privileges etc and it was working fine. Stopped working. Did a reboot in hope that would fix it but didn't.

I also tried running it under compatibility mode for XP to see if that made any difference - doesn't work either though it works in "Windows XP Mode" - the Virtual PC thing.

Trying to think if there was anything I did or that happened that could explain it but can't think of anything. Did wonder about a corrupt registry though. Anyone know where the registry settings are kept for MSVC 6.0, might it be worth removing those and trying again?

It is so old that you can just copy the folder to a new computer and it works just fine there - I lost the CD for it long ago while traveling so can no longer install from CD so have had to do that when I transfer it to a new computer but it works okay.
Sergey Alexandrovich Kryukov 15-Oct-12 16:12pm    
I did not get it: why running old version of msdev at all (even though it should work, may be something is corrupted, I don't know)? Wouldn't it better to use just the source code and compile it with the newest Visual Studio you have. You know what? I never though VC 6 was a stable project (despite of its long life). In my experience, the decent Visual Studio with .NET starts with VS 2005, and the good one just for C++ is probably 2003. Everything before it is just trash. I remember when we got rid of VS v.6 -- it was a lot of relief. You would likely need to rebuild you old code of the time of VS v.6 anyway, sooner or later, just because the C++ language stuff. How about that?
--SA
Robert Inventor 15-Oct-12 16:19pm    
My code builds fine in Visual Studio 2010 express and I do use that because it picks up a few syntax and runtime errors - but is so limited - no resource editor, can't break on data, and various other issues (the update to the full product is outside my budget right now) - and I find it clunky to use.

I think - the thing is I'm a C programmer, don't do any programming in C++ except for a few things that can only be done in C++ such as finding the special folder locations (say). The whole program is written in C and I work at a pretty low level. So that's probably why Visual C++ 6 works great for me, and the improvements in Visual Studio 2003 + that you talk about - expect those are mainly for C++ programmers, and for me, just adds more clutter and useless stuff (for me) to the interface and makes it harder to use. There is very little in the new interface that is actually of much use to me sadly.

If I have to, will be able to get by - debug some of the time in Visual Studio Express, sometimes in XP Mode, sometimes on my netbook (slow) - and together will be able to do the same things as before but it will be slower and clumsy for me.
Maciej Los 15-Oct-12 16:52pm    
I didn't get it... Just build your code in VS 2010 Express Edition, fix the errors and have a fun using newer version of old software. ;)
Tip: If VS 2010 has got a limitations, you can buy a VS 2005 Standard Edition for 49,95$ ;)
Sergey Alexandrovich Kryukov 15-Oct-12 16:55pm    
Exactly. Please see my commend to the same OP's comment.
--SA
Fixed!

It was a corrupted registry entry.

Deleted the key
HKEY_USERS\S-1-5-21-2880284692-2946324583-1242380101-1000\Software\Microsoft\DevStudio\6.0

and all its subkeys etc
and it is now running fine just as it was before :)

Thanks for all your suggestions everyone - and I might well get that Visual Studio 2005 offer for $49 seems a good deal.
 
Share this answer
 
v2
Comments
SoMad 15-Oct-12 20:15pm    
Great, now you can postpone paying for an upgrade :).
This is good to know. I did not even notice your solution because I was looking into the problem with GPSVC.DLL - sorry if I led you astray with the Dependency Walker suggestion.

Soren Madsen
Robert Inventor 15-Oct-12 20:26pm    
Soren, that's okay thanks for your suggestion, and thanks for looking into it for me, learnt from it, and it seemed quite likely at first, when I saw those red errors.
Open the vc++ 6 as run as administrator.

After you should abel to use, it should work normally. Now i also now used and running sucess fully.
 
Share this answer
 

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