I did, however, stumble upon the ability to change the Chrome OS mode. By default, the OS runs in "stable" mode. Google feeds automatic, tested updates to your stable version of Chrome OS approximately every couple of weeks. Under the settings "wrench", on the "About Chrome OS" page, the user can change this mode to either Beta (less stable) or Dev (short for "development", and extremely unstable.
Since looking before leaping is not my style, I decided to check out what the Dev mode was like. On reboot, Chrome immediately ran an OS update that shot the user experience several months in the future. I was now using the most advanced, wild west version of my Chromebook. Eventually, Dev updates graduate to Beta mode for further user testing, and eventually those that survive make it to a future stable update.
One thing that was different in my Dev version was the apps interface, which acted as a popup rather than a new tab:
What I did not realize was that I was trapped like Marty McFly in the future. Changing the mode to Stable or Beta did not trigger an OS update (or rollback, in this case), because there is no such thing as a Chrome OS rollback. After researching the Chromebook user groups, I was informed that I had two choices:
1. Wait for the Stable OS version to surpass the Dev version, thus updating the to the latest Stable version. This could take 6-12 weeks. School starts sooner than that, so not gonna happen.
2. Perform a factory reset, wiping the machine and reinstalling Chrome.
I chose #2, which is actually a simple process involving poking a hole-button on the bottom of the CB, using another machine to download the OS onto a memory stick, and booting the CB from the USB. Ironically, the only snag I had was a Windows 7 machine that decided it's most recent Windows update forbade it to accept usb drives. Typical. Another machine was more compliant.
No comments:
Post a Comment