no offense meant by this, but what's the point of a fake windows 8 pic? seems pretty useless and stupid to me...
How about you brand your fake pics with 'fake' ? And heck consume... really, do you even read? The fake had a error, ricky, 7989 in build name.. lol
Yes obviously I saw that but it didn't look edited at all. There are two real screenshots of a prebeta build in this thread and it made me wonder if it could be real. This entire thread is stupid actually, we get it, you're good with photoshop...congratulations.
I love how every feels the need to constantly spam these giant ass watermarks over the simplest things. Stop being so insecure. Yes, it's a marvelous photoshop, it's too bad you shat all over it making it look like ass.
It's just some image on the internet. Who cares if it's "stolen". Come a few months no one is going to care, or even remember these screens as we'll all be playing around with the real thing. If people care that much about some random image to where they feel the need to place a watermark on it they could make it subtle. Not some opaque text that covers up 90% of the shot. What the hell's the point of that.
God that looks awful. Not your photoshopping but the idea in general. I honestly hope your trusted source is bulls**tting you.
Double damn. I guess now I'll just be hoping that there will be a third revision. Even though I haven't seen a BSOD in years, I don't like the idea that if something goes down it'll treat me like a kid on AIM with that face. What happens if a driver crashes, will it still say hello.sys address here? Or do all you get is that next to useless message?
It would only be great if it was useful. With that non-information on it now, I'd rather the computer reboot without my consent. It hardly tells you anything, there's no specific code (0x07b etc) or driver file that caused the problem (assumed) so there's no point in it to even be there. Blue isn't worth it.
Codes were awful and impossible to understand... moreover, in the bsod i got in win7, i never got any driver name (because it was caused by kernel...) and at reboot, windows shows the error code (at least, it shows it on windows 7, i don't know for 8). And you can use WhoCrashed / BlueScreenView to see these informations
They're easy to understand once you know what the mean, and what to look for. Hell you could just google the error code / bug check code and get a good answer. I've helped a lot of people fix errors with those codes now it's fairly useless. And you can't use programs if it's so bad you can't make it to the desktop or fully boot.