The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Most BSoD events are now hidden from the user, as ms has followed apple's example of freezing the state of the monitor (apple shows a screenshot) whilst frantically killing and restarting stuff in the background.
The only way to see that anything happened is by checking the error log -- but even that only works sometimes, because the error log always seems to be one of the first things that stop working,
Personally, I'd rather get blue screens; who knows how much worse they make things by trying to hide errors?
I wanna be a eunuchs developer! Pass me a bread knife!
The company IT force upgraded the 7 year computer I was working on from 7 to 10, with zero checks why no indicators ever showed suggesting to upgrade.
Came into work to work one day and "oh, oh! Why is the desktop different. Win 10 upgrade."
Check VS and critical daily tools still worked. Cool.
Enable dual screen strecth. Odd - not finding 2nd monitor.
Odd - not finding graphics card.
Install radeon driver update - crash. but not BSOD crash.
Windows very kindly rolled the change back to using default windows graphics driver without completely falling over.
Issue - dell motherboard driver + some releated graphics driver is not supported for windows 10.
And even better is windows detected such a thing and never prompted to upgrade knowing that the hardware was not supported.
Months go buy, zero mention why I'm not using the 2nd monitor.
There was mentions ages ago that all old hardware would be replaced. Even filled out spreadsheet with computer details indicating serial number and model type which 10 second search would indicate age and if Win 10 supported, and said spreadsheet was used to remotely identify my computer for upgrading.
Suffice to say I started looking up articles on why devs and IT do not get along, wanted to find something regarding how a number of Devs write the software IT use and actually end up with a bunch of knowledge to get their work done which they know why not ... blah ... blah ... blah.
I've been building industrial control systems for a good 20 years now, and all based on the windows platform (okay some embedded stuff out there too), and other than hard disk or power supply failure the systems have been rock solid. I still have some XP machines out there just chugging away, and no one want's to upgrade them, if they are still working.
some machines have user interaction, others don't, I've got one machine (at least) out there that hasn't been restarted in close to 10 years, still ticking away with no issues. honestly the only real troubles I've had were do to system admins and IT people mucking about "tweaking" a system, then i get called out, put everything back the way it was, then they tweak it again, so i get called out again....
STOP TOUCHING THE #### COMPUTER!!! YOU DON'T KNOW WHAT YOU ARE DOING!!!
I've had control system's running on every version of windows since XP, the only true reason of the stability is: no windows updates can be installed, because there is no internet at these facilities
So ... a drop down, or set of radio buttons (drop down allows for more flexibility in future) and a tiny bit of code. What's the problem?
Sounds like a very nice little feature that is simple to implement and makes the user's life a load easier ...
Sent from my Amstrad PC 1640 Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
I once applied for a job in the military.
"Your resume says you're in IT so we have two available positions, you can become an Oracle DBA or we can test new torture methods on you."
"I'll take the torture methods, please."
They then presented me with an Oracle database