Widespread geekiness observed me seeking to get the Chrome OS strolling this weekend. It took a lot of time to work through all the sources, which included conflicting commands and a horrific software program. It all worked out, although I now have the OS strolling on a netbook. This submission is a brief precis of what turned into worry and does not include the numerous dead ends and problems I encountered.
This is Google’s try to develop a small-footprint manipulation device for netbooks for walks net-primarily based apps. The core plumbing is Linux, and the UI is a variation of the Chrome browser. Whether this may discover massive-scale mindshare may not be determined for quite a while. The reliable release will probably be 12 months from now. However, it’s a thrilling idea, and I wanted to get my palms around it if it does emerge as famous as it will be something that consumer assistance professionals will want to comprehend to aid their apps correctly.
The two main factors are the device hardware and the Chrome OS software.
The pre-release model of Chrome OS has plenty of hardware dependencies, so I did a few internet studies to pick out a tool on which the OS has been successfully set up. There have been several applicants. I picked the Asus Eee laptop Seashell because it met the requirements and looked like a pleasant netbook.
The netbook comes with Windows 7 installed. To use Chrome OS, you want to boot from a USB flash drive with a picture of the software. Jorge Sierra’s page referenced underneath provides commands, a Chrome build, and a photograph writing device. I already had a couple of pieces of equipment mentioned in the article.
I did all the flash disk processing on my Toshiba/Vista computer.
The Sierra article hyperlinks to a chunk Torrent package with the Chrome OS and an image writing device. There are different Chrome OS builds, but this one worked well. I ran the torrent, and the download took approximately ten minutes. I opened the zip record in the torrent package and then extracted the Chrome OS build: chrome_os-img. The following step was to format a flash pressure.
Because the image document became close to three GB, I purchased a four-GB SanDisk Cruzer. Any logo will be paintings, but I wanted one with an LED to inform people there has been activity. I used the HP Disk garage format tool to format the USB drive using the NTFS file system. The format device is available from several sites.
I checked the formatting using the Windows manage command. Click on laptop/control/storage/Disk management. You should see the USB pressure indexed and a “healthful” message if the formatting went successfully. Next, I used the Win32 Disk Image application to install the picture file on the USB force.
This was covered in the Sierra package deal, but I already had it. After launching the application, I pointed to the chrome_os—img record. My USB drive (E) has already been decided on. Click on Right, and the process starts. While the development bar is complete, the copying is complete. The USB force is now equipped to be used.
After unpacking the netbook, I activated the Windows 7 Starter package protected by the tool. I do not assume you need to do this. However, I wanted the tool to work with Windows. I also wanted to test the wifi connection. The wifi discovered my community was great, and I powered it down.
The final step calls for a trade to the BIOS so the netbook boots from the USB drive.
I plugged the USB power cord into the netbook, pressed the energy button, and tapped the F2 key until the BIOS setup was regarded. The BIOS key might be unique from device to tool, so I needed to tap the F2 key instead of preserving it. The boot commands I found online did not work, so I needed to make changes inside the BIOS. The following commands worked for this Asus netbook.
