To be precise, from the Event Viewer :-
"Application popup: vcspawn.exe - Application Error : The application
failed to initialize properly (0xc0000005). Click on OK to terminate the
application.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp."
Clicking on the link in the event viewer produced a further information
page 'explaining' it.
"The program could not load a driver because the program user doesn't
have sufficient privileges to access the driver or because the drive is
missing or corrupt."
Now, vsupdate and vcspawn aren't drivers ? presumably they access some
(screen ? keyboard ? m/c hardware ?). This piece of junk doesn't
consider it worthwhile saying WHICH BLOODY DRIVER ISN'T WORKING !!!!
This message comes up if you execute them from VS.Net, the command line,
any old how. Command prompts run fine.
I've uninstalled and reinstalled VisualStudio.Net. No effect. Is there
no other solution to this problem but reinstalling every f**king driver?
Paul Robson - 18 Nov 2003 17:35 GMT
> To be precise, from the Event Viewer :-
Doesn't seem to be related to the older bug. The IDE and compilation
works fine. Running apps using 'Start' works fine ; 'Start without
Debugging' crashes....
Charles Goehring - 29 Nov 2003 18:01 GMT
Paul,
I kept getting this in VC6 when building the latest Apache source
(someone else's source & project). I had seen it before in an older
version of Apache. It throws the error on every file at least and says
"creating version resource" or some such in the output window.
The only thing I could figure was it was trying to access a version
control system and was not succeding (they probably use cvs). Couldn't
get it turned off for nothing - had to sit through a thousand clicks and
beeps to get the thing compiled. I even yanked the speaker wire out of
my computer.
My situation was a bit messed up because my source-safe was not
configured configurred right and the password/username has changed. I
fixed the two ini files to point to the correct vss file but that did
not help - had to endure the beeps & clicks
Have you fond a solution?
Chuck
> To be precise, from the Event Viewer :-
>
[quoted text clipped - 21 lines]
> I've uninstalled and reinstalled VisualStudio.Net. No effect. Is there
> no other solution to this problem but reinstalling every f**king driver?