Right there in the palm of your hand.
A Windows Phone 8-using wag claims he provoked his Microsoft handset into asking for an installation DISC - with a boot manager error message familiar to anyone who's wrestled with Windows NT. The offending boot screen At least it didn't do a blue screen of death The error is by no means standard and - we're told - only …
Right there in the palm of your hand.
The next lot of mobile phones circa 2013, will have even bigger screens so there will be an opportunity to install a disc drive in them. Problem solved.
...and you wonder why phone OEMs lock down bootloaders and try to stop people flashing their own firmware. It is to stop this sort of publicity caused by people messing around with the OS.
> will have even bigger screens so there will be an opportunity to install a disc drive in them
Well the Lumia 710 and 820 did suddenly add a microSD slot ... seems like a suitably mini "disc" drive.
No RICHTO, we know why Windows phone manufacturers ("OEMs" in Microsoft corporatespeak) lock down bootloaders and try to stop people flashing their own firmware. It's because the licensing agreement with Microsoft requires it. Microsoft wouldn't want people wiping the virus off their new (subsidised) purchase and installing better on it. What would Microsoft gain from that?
Unlike Android of course, built on an OS that pre-dates Windows NT.
The fact you can scoop out an error message (regardless whether it's been hacked or not) that's designed originally for desktop OSes is pure laziness in my own opinion. To disguise it is worse. It really serves nothing more than some embarrassing headlines, but still; it's nasty to the common consumer user who'd be totally confused with such an error if one of the key files corrupted.
Even the title for the error page isn't centred. Sheesh.
@JDX: You, sir, are a troll, though a troll with a very nice gold badge!
For once I'm going to give M$ the benefit of the doubt here: maybe there is some wag of a code monkey in the WinPho8 dev team who mocked-up this screen to be displayed on a boot failure likely to have been caused by tinkering with the standard boot image. Surely someone at M$ has a sense of humour...surely...
assuming that the common consumer mucks about with their flash rom image
I bet that if you asked a man on the clapham omnibus if you could muck about with his flash rom image to show him something funny, you would get a smack.
What about over-the-air updates that could go wrong due to the battery cutting our or some data becoming corrupt during the download process? This is what I mean. You don't see Androids and iPhones chucking out random guzzle that consumers don't understand.
Flashing the ROM on a WP Phone is the same as asking iTunes to do a restore on an iPhone (to a certain degree). How can anyone defend the laziness Microsoft has showed here to tie up loose ends?
That's what the big Tiles are hiding...
@fiddley - okay, you have me on that one. still, i like the fact they're prepared to put a funny within their crash code... "we are hanging here".
Agreed! When I see Chrome crash and take down Windows with it, it's the hilarious Star Trek message ("it's dead Jim") that makes the loss of all my work bearable.
I'll believe a lot, but someone at Microsoft having a sense of humor? That is TOO much to ask.
You don't think the guy just took a photo of a desktop PC bootscreen error, then displayed it fullscreen on the phone?
Would be a fine joke to play.
you are just talkin' mess.
Why would you spend the resources to take it out especially is the actual server and desktop OS still need that code? Why would you spend the time and money to remove a scenario that you can only get to by screwing with the boot loader? What % of smart phone owners do that?
You my friend would make a terrible dev manager and or PM.
> ...and you wonder why phone OEMs lock down bootloaders and try to stop people flashing their own firmware. It is to stop this sort of publicity caused by people messing around with the OS.
This would not be a problem on my phone. I could just use an OTG cable and plug a CD drive into it.
> Unlike Android of course, built on an OS that pre-dates Windows NT.
NT is a VMS knockoff. So that means that it is no spring chicken either.
Are you advocating a position that users should not be able to do what they want with their own property?
"When I see Chrome crash and take down Windows with it"
You use an OS where a program crash will take it down ? Good grief !
Because android phones don't crash into those kinds of death screens....
and Apples iDevices don't either....
Perhaps it's simply because it asks for the disk, in that case...BFD. By the way those photos are from links in the comments from the page that you posted in another article Bob, but maybe you didn't read that far in your excitement to get another anti-MS comment posted. You (again) fail to mention this "true innovation" happened because they were pissing about with their phones and flashing firmwares.
Yeah, I just don't use chrome. I've not had any other program crash the OS. I run Safari, firefox, Iron, Opera and sometime even IE and they all manage to run without breaking the OS. I guess those Google engineers are just really clever (as well as really funny!).
Actually, thinking about it, it doesn't crash the OS so much as make it shut down. It goes through the same process it goes through when you click shut down, so it's not technically a crash, it's an unwanted reboot...
It is a message you would never see with a standard ROM. This message was generated by hacking the ROM.
But then, I reckon you just looked at the picture.
It doesnt say he is running a custom ROM...just that he played with the flashing ROMS. Obviously there is some code in their that has just been added in without editing it for the phone. But i suppose if the average user never see's it why bother changing it.
it shows how much optimization has been done i.e. the bare minimum
Keyboard bad, press F1 to continue?
I'm waiting for a "No ROM BASIC" error to appear myself.
Whether I agree with your sentiment or not, the fact that you actually typed the word 'sucky' to describe something, and then submitted said statement, deserves a downvote.
The two trolls must share a bedsit and woke one another up to post!
Newsflash : Messing around flashing your phone may break it. Coming up : Windows Phone 8 built on NT kernel.
Pretty pathetic excuse for linkbait if you ask me.
It shows there is some code in there to handle errors that should never happen. How did Microsoft test that code? Are there any bugs in it? Even if you assume the code identical to and fully tested on other platforms it shows there is unreachable code that make your ROM bigger than it need be i.e. more expensive, slower and more power hungry (more cache misses).
Says to me that all those vicious rumours, dismissed by experts like RICHTO, that Windows had layer upon layer of old code lurking under the bonnet were all true.
AC -- what time-zone are you in? Wake up. Don't take everything so seriously. It was mildly amusing. Enjoy a grin/smirk while you have your coffee.
Or are you one of MS's attack dogs just doing your job?
Has anyone found any detail on what he was doing?
I can't find anything on whether he has played with the shipped ROM and found an error that shouldn't be displayed (so, hidden code) or whether he's shifted a ROM from a different product across, where the error would make sense.
What does "Gritpants" mean?.. I think we may have met in person?
@AC "Says to me that all those vicious rumours, dismissed by experts like RICHTO, that Windows had layer upon layer of old code lurking under the bonnet were all true"
How does it show that? All it shows is that there is some code in this part of the system which exists for both the WP, probably RT, Desktop and Server versions of NT.
In other news, MS make a big thing about the fact that it's the same core OS on each device.
It shows there is some code in there to handle errors that should never happen.
Anything that Should Never Happen (tm) will happen.
Loverock Davidson strikes again!
"It shows there is some code in there to handle errors that should never happen. How did Microsoft test that code? Are there any bugs in it?"
They tested it by having it in the Windows source for the last couple of decades. #1 rule of large-scale software engineering is not to mess with code that doesn't need it. Do you really think it would be a good idea to fork the NT kernel just so that an error message you'd never see on a phone isn't included? Every little change like that exponentially increases the test matrix, making a future failure all the more likely.
@ El Andy: Eh? Even rewording the text of error messages? Just how fragile can the NT kernel be? Shhhhhhhh... Softly now... you might crash your phone.
Non-standard, f*&ked with ROM shows Non-standard error!
And the story is...... ?
Windows8 is realy NT in disguise!
"Windows8 is realy NT in disguise!"
I'm guessing that since this is about Windows PHONE 8, you mean Windows PHONE 8
So are pretty much all the other Windows releases, probably also including the ones most of us use on our Windows desktops.
So, now one presses CTRL-ALT-DEL?
This article smells of queef.
So does your mum.
At least it didn't ask him to press F1 to continue...
Better, of course, with a proper blue screen and the 'press any key' option.