Microsoft has begun privately beta testing a new tool, known as “Windows Advisor,” which is aimed at helping consumers better pinpoint why their Windows machines might not be up to snuff. Windows Advisor currently supports Windows XP Service Pack 2 and Windows Vista. The beta version is available in English only. Microsoft officials have been saying that Windows, and especially the much-maligned Windows Vista, isn’t to blame for all of users’ PC problems. Faulty drivers and badly written apps are often behind users’ unhappiness with their new PCs, the Softies have said. Microsoft is making sure that users will be able to place blame where it belongs with Windows Advisor.
Link: ZDNet Blogs
Absolutely right. I can't count the amount of times people have moaned at me about Windows because <insert application name here> keeps crashing.
Absolutely right. I can't count the amount of times people have moaned at me about Windows because <insert application name here> keeps crashing.
explorer.exe?
iexplore.exe?
Absolutely right. I can't count the amount of times people have moaned at me about Windows because <insert application name here> keeps crashing.
explorer.exe?
iexplore.exe?
It's still not a problem with Windows now is it
Splitting hair. Aren't we ?
Absolutely right. I can't count the amount of times people have moaned at me about Windows because <insert application name here> keeps crashing.
explorer.exe?
iexplore.exe?
And yet most of the time the crash is not from those two apps ether. The only crashes I have had with IE have been from bad Add-Ons or codecs with explorer
Absolutely right. I can't count the amount of times people have moaned at me about Windows because <insert application name here> keeps crashing.
explorer.exe?
iexplore.exe?
And yet most of the time the crash is not from those two apps ether. The only crashes I have had with IE have been from bad Add-Ons or codecs with explorer
Don't be so quick to be dismissive. I can still crash IE after a clean install + all updates, and while Explorer itself is more resilient to outrigth crashes, I can certainly get it to misbehave.
Windows is the problem because the design of Windows is what has created many of these problems. Windows is unstable and fragile. One single corrupt or missing entry in the registry and it all comes crashing down. Windows is too $*(^(!*^$ stupid to reset its services and reconfigure the hardware when that happens. One bad driver and it won't boot because it's too @)$^(!
It really is Microsoft's fault. Other operating systems don't experience the same problems in quite the same way. They are more resilient to many of these errors that make Windows come crashing down, or not even boot. Much of it comes down to the Registry and the amount of bloat (and legacy support) that is in Windows.
2) It's not private... I have not been invited and I can see it in my profile.
3) Looks good.
Blue screens of death are actually a good thing. The data is spits out will help you troubleshoot a failure. But people are too ignorant to understand that so they blame Microsoft because there's just NO WAY the problem could be between the chair and the keyboard
it should be cool that the advisor shows the application that is causing the problem,perhaps with advanced monitoring.
not very mature at all microsoft
Microsoft is at fault,
Add-On companies are at fault,
laa laa laa.
Edit: And, god forbid, sometimes, it's you, the end user, who doesn't know what the f*ck to do.
So a simple error such as a program trying to reference invalid memory takes out the whole OS - crashing down into oblivion with any open apps and files going south with it - Yeah a great response to what could behandled much more safely.
I have had a few instances wher I have had some app try to write to invalid memory say - now I know the OS should intercept that and freeze it but can't they simply inform you - force an orderly shutdown of open apps and files and then force a shutdown.
Apparently not - for a simple memory error - a harmless incident if handled more elegantly - the OS crashes down then upon reboot scrambles your hard disk because checkdisk is more often than not set to run because of the file system errors generated by the Blue Screen.
As I said earlier I have something as inocuous as a memory allocation error force a Blue Screen, crash the OS and totally scramble the system partition on restart so that the only sensible solution was a re-install.
In fact - lets be honest - Windows almost demands a clean install every few months to keep running error free - no matter who is at fault.
Microsoft ARE responsible for the Blue Screens - it may not always be their code that cause them BUT it is their code which does such a bad job of handling it.
At worst, the application/OS will terminate (BSOD) thereby preventing further damage to the user data. The worst thing the application/OS can do is claiming everything is "alright" when it's in fact corrupting things.
http://www.geekstogo.com/forum/Windows-XP-...des-t43519.html
Memory errors are never "simple."
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.