It’s OK, Windows 8 tablet. Shh shh. It’s gonna be OK. [Business Insider]
More:
- First Look At What’s New In Windows 8
- Install Windows 8 From A USB Stick
- Windows 8 Slate (Tablet) Hands On: It’s Pretty Fantastic
- Everything You Need To Know About This Week’s Windows 8 News
Cal
Thursday, September 15, 2011 at 7:52 AMI got that in vmware fusion but tried virtualBox and it installed. You cant go back to your host machine while it’s installing though because it will lock up and fail. after about the 5th time i was running the most un-user friendly OS I have ever tried.
BenDTU
Thursday, September 15, 2011 at 9:54 AMI largely had the same experience.
wsDK_II
Thursday, September 15, 2011 at 11:18 AMI installed it on my laptop, and it was perfect, no issues what-so-ever.
The OS is ok, MUCH more for tablets then PC’s. Ill put this on my tablet when it comes out, but as for my desktop ill keep win7
the best thing so far is the ‘sync’ options, allowing me to sync my ‘experience’ accross 2 computers :D
EckyThump
Thursday, September 15, 2011 at 7:59 AM“Your PC ran into a problem that it couldn’t handle”
Yeah sure blame my PC, the one that’s been running 7 flawlessly for years, well sort of anyway! Heh heh #]
Cameron
Thursday, September 15, 2011 at 8:29 AMI’m getting pretty sick of these “friendly” error messages. These are next to useless when troubleshooting, just look at Windows Backup, in windows 7 you get next to no description of why your backup failed, there’s no log file, just 1 line error message and a code, where are you supposed to go with that? When backing up 1Tb of data, I need a little more to go on thanks!
Liam
Thursday, September 15, 2011 at 9:10 AMI think they’re on the right path with this; I can say pretty safely that out of their entire range of users, there will be more people who would not know how to go about resolving an error (using logs, etc.), than those who can. By providing a simple message, indicating something went wrong, and how to go about fixing it (by looking up an error code which, more than likely, links to a guide a lot easier to follow and use for a novice than say, an error log).
That said, it should also have a message of something along the lines of:
“Oh, and to our more technical users, there’s a logfile that has been created at .”
Just some thoughts :)
Liam
Thursday, September 15, 2011 at 9:10 AMI think they’re on the right path with this; I can say pretty safely that out of their entire range of users, there will be more people who would not know how to go about resolving an error (using logs, etc.), than those who can. By providing a simple message, indicating something went wrong, and how to go about fixing it (by looking up an error code which, more than likely, links to a guide a lot easier to follow and use for a novice than say, an error log).
That said, it should also have a message of something along the lines of:
“Oh, and to our more technical users, there’s a logfile that has been created at .”
Just some thoughts :)
Narfmeister
Thursday, September 15, 2011 at 9:29 AMI’m sorry but there’s just no need to dumb down an error message.
They’re not meant for End Users to troubleshoot, that’s why there’s experts on the topic. There’s little point in dumbing down something important, something that most people are going to ask for the help of a professional/power user anyway? Why not provide all the information required all at once, then the poor support staff/friend on the phone doesn’t have to screw around trying to find out what happened and have the information front and centred, easily seen and found. Sure you can have the sadface and text saying something went wrong if you want, but gimme the rest of the details too so I can fix the problem!!
I don’t care if my error message looks pretty. Don’t sugarcoat the fact that something crashed. Just tell me what happened and why.
My 2 cents as a IT Support staff…
Micheal
Thursday, September 15, 2011 at 9:59 AMBut really, how hard is it for you to just open the dump file?
There’s no need to over dramatize what M$ has done here, and made a BSOD a much less scary for end users.
Micheal
Thursday, September 15, 2011 at 10:00 AM* Experience
olearymo
Thursday, September 15, 2011 at 3:06 PM‘M$’?
Dude, the nineties called, they said you’d know what it was about.
Richard
Thursday, September 15, 2011 at 6:48 PMOr event viewer. One exception is if the Blue Screen is preventing Windows starting at all in which case the above will be somewhat more of a pain to diagnose.
MotorMouth
Thursday, September 15, 2011 at 10:49 AMSorry, but I consider myself a power user, 14 years of 3D animation, high-end visual effects and real-time music, and when I get a BSOD I just restart the machine. I don’t care why it crashed because I know that restarting will always fix it. On the tiny chance that it does happen again, I am confident that will tell me where the problem is. People who need to know WHY they got a BSOD are in a miniscule minority, probably close to the one-in-a-million category, well wide of Microsoft’s target demographic.
Of course, the other issue is that it has been 7 or 8 years since I’ve seen a BSOD at all, when I installed the wrong drivers for an external audio device, which definitely relgates it to the one-in-a-million category.
jack
Thursday, September 15, 2011 at 9:30 AMbtw guys, i was ‘shocked’ this morning to watch it on sunrise that this guy was demonstrating windows 8 on a… macbook pro.
http://au.tv.yahoo.com/sunrise/video/-/watch/26616605/microsoft-shows-off-its-answer-to-ipad/
from a distance, i thought it was a dell but when they zoomed in, it’s mbp! well at least now i can try to install on mine and test it out :)
olearymo
Thursday, September 15, 2011 at 3:07 PMYou really didn’t know already that you could do that?
DanMan
Thursday, September 15, 2011 at 7:41 PMDear god, Sunrise users thinking this is a free trial sounds like an absolute disaster.
John Hedge
Thursday, September 15, 2011 at 9:38 AMVMWare player running on Win7 Ultimate 64bit couldn’t install Win8 Developer Preview 32bit.
“Your Pc ran …..”
HAL Initialisation failed!
BenDTU
Thursday, September 15, 2011 at 9:55 AMI love the subtitle.
“You can try googling GENERIC ERROR HANDLER because you’re the one at fault, not us! :)”
Joel
Thursday, September 15, 2011 at 10:35 AMI’d have more respect for them if it just said
“We f*cked up.
If you know your shit, here’s the log files.
If you don’t, just click to restart.”
Don’t sadface me windows, you’re the one who did it.
MotorMouth
Thursday, September 15, 2011 at 10:53 AMWhat if it wasn’t them that stuffed up, but a bad application? In my experience, Windoze has been all but completely bulletproof since Win2k, it is always applications that cause problems. Since Vista, Windoze has been vastly better at isolating application crashes, too. Like I said, 7 or 8 years since my last BSOD, and even that wasn’t Windoze’s fault.
Joel
Thursday, September 15, 2011 at 11:03 AMName and shame? lol
Replace “We” with “”
I just don’t like the sadface.. it doesn’t make me feel any better about the computer crashing.
Unless it has a restore feature like Lion.
“We have to restart now but hey at least we’ll restore everything for you.”
Matt
Thursday, September 15, 2011 at 1:12 PMBlue screen of sadness is now the appropriate term.
Matt L
Thursday, September 15, 2011 at 1:52 PMBlue screen of sadface haha.
ozoneocean
Thursday, September 15, 2011 at 2:47 PMMuch, much, much better than that “illegal operation” crap they used to have! A complete nonsense phrase that demonstrated that those moron engineers had no fricken idea who they were designing this product for: the consumer market.
Instances like that demonstrated why Apple is more attractive to that market (when it’s not focussed on price). Apple still has crashes, freezes and hangs, but always makes them less scary.
Useful log files and instructions about how to get to them would be good though, and useful error messages as well, (ie. NOT eeeeuia123_0876652**^&%$#@ or whatever)
Alex
Thursday, September 15, 2011 at 4:01 PMits a “Developers preview” wtf are you talking about? its not even Beta version of the product
its not designed for consumer
stop crying
villainsoft
Friday, September 16, 2011 at 9:47 AMyeah, judging a product that is not even in beta yet is pretty pointless. Developer versions are never f0r end-users.
yahya
Saturday, October 22, 2011 at 12:31 AMi have the same problem, does anyone solve it ?? i need my windows :(