Well, I'm glad it's still blue, now I can sleep peacefully at nightZonder wrote:just seen the new blue screen of death in the new windowssorry oft again
Also, the color and the message has improved
Well, I'm glad it's still blue, now I can sleep peacefully at nightZonder wrote:just seen the new blue screen of death in the new windowssorry oft again

Maybe it's because MS Windows is still prone to viruses, even in it's latest and greatest edition (Win8), so if they fail, at least they look good at it.betajaen wrote:
I don't like it. Then again, I can't see why BSODs are needed in these day and age.

So does OSX, Linux, AmigaOS, BeOS and so on.Mind Calamity wrote:Maybe it's because MS Windows is still prone to viruses, even in it's latest and greatest edition (Win8), so if they fail, at least they look good at it.betajaen wrote:
I don't like it. Then again, I can't see why BSODs are needed in these day and age.
(My opinion may be a little anti-Microsoft, but I don't believe I'm wrong. )


Thing is; They don't need to reset, or freeze. It can just recover from the error and continue. Once Windows has loaded, or resumed. It can go into a special mode such as safe mode, then give the user all the information why it crashed and given suggestions on where to go for help, or better still do it automatically through Windows Update.Kojack wrote:BSOD can be handy, it can give a clue as to what caused it (most of mine in the past were from nvidia dlls).
Plus they are better than the black reboot of death (doing something or playing a game when suddenly the screen goes black for a second or 2, then the bios memory check appears).
If you are getting that screen then somthing is serious going on and it's the kernal or a driver that has failed I wouldn't expect a normal user to be able to debug it so thats why the introduced the system restore feature. Most blue screens in recent years have been caused by nvidea (thats from our microsoft representative for the company I work at)betajaen wrote: To a lot of people; a BSOD is pretty much the end of the computer to them. They would have to take it back to the shop, or use expensive phone help services to get it working again. Letting the computer fix itself would make it far more friendly and less dreadful if anything serious goes wrong.

Well how hard is it to for Windows; Make a note to not to load that driver on boot, then reboot? Windows automatically comes with fallback drivers for graphics cards, surely it's quite easy to swap them around on boot. Boot into Windows, load up Windows Update, then get the latest stable driver.Zonder wrote:If you are getting that screen then somthing is serious going on and it's the kernal or a driver that has failed I wouldn't expect a normal user to be able to debug it so thats why the introduced the system restore feature. Most blue screens in recent years have been caused by nvidea (thats from our microsoft representative for the company I work at)
If a driver caused the issue then replacing it with a stock driver on reboot should be possible.betajaen wrote:Well how hard is it to for Windows; Make a note to not to load that driver on boot, then reboot? Windows automatically comes with fallback drivers for graphics cards, surely it's quite easy to swap them around on boot. Boot into Windows, load up Windows Update, then get the latest stable driver.Zonder wrote:If you are getting that screen then somthing is serious going on and it's the kernal or a driver that has failed I wouldn't expect a normal user to be able to debug it so thats why the introduced the system restore feature. Most blue screens in recent years have been caused by nvidea (thats from our microsoft representative for the company I work at)
What I'm getting at here is; At this day of age, with the processing power, wealth of software available and the internet. There is no reason why computers (software wise), can't repair themselves. Heck, when I installed Windows 7 the other month, I didn't even install any drivers. Windows did it for me.
BSODs are from an archaic time where such feats weren't possible, so in the OS had to dump as much information that a human could read on to the screen, in hope that they could fix it. There is no need for them anymore.










Old, hmmm, C++ is ~30 years old, not much has changed even with the newest revision. The code i write in vs2005 still works in win8, I have very little likely hood of using anything that's new builds that i can't already do in vs2005, and the generate code will run what? 1% faster? Sorry, i'll stick to vs2005/vs2008 where the UI is clean, it's stable, and i know where everything is.Mind Calamity wrote:What if it get's old ? Will you not upgrade it either ?bronzebeard wrote:i'll stick to vs2005, or codeblocks.
If it ain't broke don't fix it!
Actually windows 3.1 is still in use, entertainment centers in the backseats of 767s come to mind. Just because something is newer doesn't mean it's better or worth the upgrade. Hell, the space shuttle ran on 386s!betajaen wrote:We could use the same attitude when it comes to Windows 3.1bronzebeard wrote:i'll stick to vs2005, or codeblocks.
If it ain't broke don't fix it!![]()




I got to this website without using a keyboard.I would love to see any version of Windows come close to the simplicity of Open/FluxBox or XFCE, heck I don't even have to use my keyboard to get to a website I frequent

I am just pointing out that you haven't tried KDE then.Mind Calamity wrote:I haven't tried the newer versions of KDE 4.x, at the time I tried it it was still in it's beginnings, I didn't use KDE 3 all that much either, but it still was way faster than KDE 4 at the time.
