Chromium OS

 Chromium OS is an open-source project that aims to build an operating system that provides a fast, simple, and more secure computing experience for people who spend most of their time on the web. Here you can review the project's design docs, obtain the source code, and contribute. To learn more about the project goals, read the announcement blog post.

 

Chrome OS is an operating system based on the Linux kernel and designed by Google to work with web applications and installed applications. Initially, Chrome OS was almost a pure web thin client operating system, with only a handful of "native" applications, but Google gradually began encouraging developers to create "packaged applications", some of which can work offline. In 2014, Google upgraded its Play Store standards for packaged apps, requiring that these applications work offline. Around the same time, Google also announced that Chrome OS would gain the ability to run Android apps natively, by late 2014. In September 2014, App Runtime for Chrome (beta) was launched together with four Android apps being able to run on Chrome OS.
Chrome OS is built upon the open source project called Chromium OS which, unlike Chrome OS, can be compiled from the downloaded source code. Chrome OS is the commercial version installed on specific hardware from Google's manufacturing partners.The launch date for retail hardware featuring Chrome OS was delayed from late 2010 to June 15, 2011, when "Chromebooks" from Samsung, and then Acer shipped in July.

Chrome OS Guided Tour

 

 

Live Boot Chromium OS of a USB

 

Download Links:

Chrome OS Download
http://chromeos.hexxeh.net/

Image Writer:
https://launchpad.net/win32-image-wri...

 

                            Disk Volume Error

We would like to get a better understanding of this issue so we can better assist not only you but other users with similar problems as well. 
Follow the methods mentioned below.
Method 1:
You can try to run a Check Disk in order to know whether there are any bad sectors present on the disk. Follow the steps mentioned below.
You can solve some computer problems by checking a drive or drives for errors. For example, you can check your computer's primary hard disk to fix some performance issues, or you can check an external hard drive if it's not working properly.
1.      Open Computer by clicking the Start button and then clicking Computer.
2.      Right-click the drive that you want to check and then click Properties.
3.      Click the Tools tab, and then, under Error-checking, click Check now. If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
To automatically repair problems with files and folders that the scan detects, select Automatically fix file system errors. Otherwise, the disk check will report problems but not fix them.
To perform a thorough check, select Scan for and attempt recovery of bad sectors. This scan attempts to find and repair physical errors on the drive itself, and it can take much longer to complete.
To check for both file errors and physical errors, select both Automatically fix file system errors and Scan for and attempt recovery of bad sectors.
4.      Click Start.
Depending on the size of your drive, this might take several minutes. For best results, don't use your computer for any other tasks while it is checking for errors.
Note
If you select Automatically fix file system errors for a drive that's in use (for example, the partition that contains Windows), you'll be prompted to reschedule the check for the next time you restart your computer.
For further reference check the article mentioned below
Check a drive for errors
http://windows.microsoft.com/en-US/windows7/Check-a-drive-for-errors
You can also try the Check disk from command prompt. Follow the steps mentioned below.
1.      Click on Start.
2.      In the Start Search Box type cmd and run it as an administrator.
3.      In the command prompt type “chkdsk DriveLetter: /r” (/r identifies the bad sectors and repairs them) and Enter.

1.  
   1. Note If one or more of the files on the hard disk are open, you will receive the following message:

Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)
Type Y, and then press ENTER to schedule the disk check, and then restart your computer to start the disk check.

1.  
   1. To repair errors, locate bad sectors, and recover readable information, at the command prompt, type chkdsk volume:/r, and then press ENTER.
      
      Note If one or more of the files on the hard disk are open, you will receive the following message:

Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)
Type Y, and then press ENTER to schedule the disk check, and then restart your computer to start the disk check.

Method 2:
You can also run an SFC scan to check for bad sectors in the drive. Follow the steps mentioned below.
Steps to perform SFC scan:
1. Click the Start button.
2. From the Start Menu, Click All programs followed by Accessories.
3. In the Accessories menu, Right Click on the Command Prompt option.
4. From the drop down menu that appears, Click on the 'Run as administrator' option.
5. If you have the User Account Control (UAC) enabled, you will be asked for authorization prior to the command prompt opening. You may simply need to press the Continue button if you are the administrator or insert the administrator password etc.
6. In the Command Prompt window, type: sfc /scannow and then press Enter.
7. A message will appear stating that 'The system scan will begin'.
8. Be patient because the scan may take some time
9. If any files require replacing SFC will replace them. You may be asked to insert your win7 DVD for this process to continue
10. If everything is okay you should, after the scan, see the following message "Windows resource protection did not find any integrity violations"
11. After the scan has completed, close the command prompt window, restart the computer and check.

Hope this information is helpful.