A
Adam Albright
Programs that stop working are a fact of life. Ever since XP came out
applications are suppose to run in their own "protected" memory space
so if they crash, they don't take down the whole system with them.
Operative word, that's how it USED TO BE.
I'm in the process of testing a upgraded version of Cyberlink's Power
Producer, a utility to do some simple DVD burning and other similar
tasks. It has been working for several days without problem. Now I
just clicked on its shortcut and it hung up. That isn't why I'm
writing.
Rather the issue is how you CAN'T gracefully recover from a crashing
application like you did in XP. At least I couldn't, at least not this
time, since it is the first "crash" since installing Vista, I'm not
sure if this is normal or not. Geez, I hope not!
If any of your software crashed in XP, you could do the old three
finger salute, holding down the Ctrl, Alt, and Delete keys at one
time, which would bring up Windows Task Manager. This allowed you to
stop a application that no longer was responding to Windows. That
feature is changed in Vista. The new sequence is Ctrl, Shift, Esc.
You would think Microsoft would tell people that made a needless in
picking which keys saves Microsoft's ass, but nope.
I try the new key combination. Nothing happens. Windows is locked up
good. Rats!
With Power Producer crashing, Windows too is locked up. Not suppose to
happen. No graceful way to shut down my other RUNNING applications. So
I just sit waiting to see what if anything would happen.
Couple minutes go by, oh look.... Windows did manage to show the Power
Producer window in a new washed out view. Cute, but not helpful. Vista
seems more about being "pretty", then useful.
Still everything locked up. Another minute goes by, oh look, Windows
now has faded out my entire desktop, maybe that's a new visual clue
that Windows has given up the ghost and wants to do to a hard
shutdown. I still can't shut down Power Producer the normal way or the
brute force way from Task Manger. Nor can I access or close any of the
other six applications that are running.
That creates a problem. I'm in the process of rendering a large video
file, A big project, hours away from finishing, obviously pointless to
not reboot since everything seems locked up. Even the clock stopped. I
sure sign Windows died.
However if I do a forced shutdown by pusing and holding the power
switch on my PC I run the risk of corrupting the source file that my
video project is based on plus who knows what harm it could do to any
other open files, including Windows System files.
Oh well, what choice do I have. So I do a forced shutdown, then reboot
and immediately go to the Event Viewer to see if Windows can say what
happened.
It says this:
"Faulting application Producer.exe, version 4.0.0.1024, time stamp
0x453e08a0, faulting module MFC71U.DLL, version 7.10.3077.0, time
stamp 0x3e77fc29, exception code 0xc0000005, fault offset 0x0005c598,
process id 0x110, application start time 0x01c754731e0dba67."
Vista does not crash gracefully, it falls flat on its face. I can live
with a application crashing. By the way its "Vista Ready" or so it
claims.
http://www.cyberlink.com/multi/products/main_3_ENU.html
I thought the days of Windows crashing due to a hung application were
pre XP vents. I guess Microsoft brought the good old days back.
applications are suppose to run in their own "protected" memory space
so if they crash, they don't take down the whole system with them.
Operative word, that's how it USED TO BE.
I'm in the process of testing a upgraded version of Cyberlink's Power
Producer, a utility to do some simple DVD burning and other similar
tasks. It has been working for several days without problem. Now I
just clicked on its shortcut and it hung up. That isn't why I'm
writing.
Rather the issue is how you CAN'T gracefully recover from a crashing
application like you did in XP. At least I couldn't, at least not this
time, since it is the first "crash" since installing Vista, I'm not
sure if this is normal or not. Geez, I hope not!
If any of your software crashed in XP, you could do the old three
finger salute, holding down the Ctrl, Alt, and Delete keys at one
time, which would bring up Windows Task Manager. This allowed you to
stop a application that no longer was responding to Windows. That
feature is changed in Vista. The new sequence is Ctrl, Shift, Esc.
You would think Microsoft would tell people that made a needless in
picking which keys saves Microsoft's ass, but nope.
I try the new key combination. Nothing happens. Windows is locked up
good. Rats!
With Power Producer crashing, Windows too is locked up. Not suppose to
happen. No graceful way to shut down my other RUNNING applications. So
I just sit waiting to see what if anything would happen.
Couple minutes go by, oh look.... Windows did manage to show the Power
Producer window in a new washed out view. Cute, but not helpful. Vista
seems more about being "pretty", then useful.
Still everything locked up. Another minute goes by, oh look, Windows
now has faded out my entire desktop, maybe that's a new visual clue
that Windows has given up the ghost and wants to do to a hard
shutdown. I still can't shut down Power Producer the normal way or the
brute force way from Task Manger. Nor can I access or close any of the
other six applications that are running.
That creates a problem. I'm in the process of rendering a large video
file, A big project, hours away from finishing, obviously pointless to
not reboot since everything seems locked up. Even the clock stopped. I
sure sign Windows died.
However if I do a forced shutdown by pusing and holding the power
switch on my PC I run the risk of corrupting the source file that my
video project is based on plus who knows what harm it could do to any
other open files, including Windows System files.
Oh well, what choice do I have. So I do a forced shutdown, then reboot
and immediately go to the Event Viewer to see if Windows can say what
happened.
It says this:
"Faulting application Producer.exe, version 4.0.0.1024, time stamp
0x453e08a0, faulting module MFC71U.DLL, version 7.10.3077.0, time
stamp 0x3e77fc29, exception code 0xc0000005, fault offset 0x0005c598,
process id 0x110, application start time 0x01c754731e0dba67."
Vista does not crash gracefully, it falls flat on its face. I can live
with a application crashing. By the way its "Vista Ready" or so it
claims.
http://www.cyberlink.com/multi/products/main_3_ENU.html
I thought the days of Windows crashing due to a hung application were
pre XP vents. I guess Microsoft brought the good old days back.