"Agreed it is still just alpha-level software, but I still maintain that undo is a rather fundamental function though. I'm sure they'll include it in future releases."
- GeekLad
"Thanks for the mention Adam. Seems most folks commenting on the post at MakeUseOf been able to write the image to a USB drive and boot it, although some have run into snags here and there."
- GeekLad
"Well, I'm not sure what the minimum memory requirements are for Chrome, but it may be that 450 MB isn't enough. You could try running it directly on your computer instead of through VirtualBox. This weekend, I found a nice tool for writing disk images and wrote up a tutorial on MakeUseOf on how to run Google Chrome on a real machine via a USB thumb drive. If you have a 4GB USB drive you can use to try it, you might want to check it out."
- GeekLad
"Yeah, at this point it's not terribly fast. Since you need to run it on a machine that is capable of doing all the same things it can do (and do them much faster), I wouldn't imagine using it a whole lot other than just to try it out."
- GeekLad
"Yep, as of right now it's pretty much just the web browser. Before go-live they will provide other applications and all the applications will actually work (calculator & notebook do not work right now, for instance). They have also said that the user interface is subject to change, so we'll have to wait and see what the first production release will actually look like."
- GeekLad
"You could build a wave with the group and just continually modify it. However, if you're working in a collaborative group, it is unlikely you'll only ever work on a single topic. If the entire subject matter changes, or you're working on a new project with those folks, you would lose all the work on the previous project if you were to use the same wave and overwrite it with the new project/content."
- GeekLad
"You should be able to use bridged or NAT. The OS does need to be set to Linux, and you do need more than 256MB of allocated memory. My ovf file takes care of all this when you import it, rather than just trying to use the disk image with your own new virtual machine."
- GeekLad
"That is correct, you do need it set to Linux. I already have it set as Linux / Other in the ovf file, so if you import it, everything should be all set."
- GeekLad
"Are you running Virtualbox 3.0.12? It seems others are having similar issues. I did find one thing that may help, from the VirtualBox forums here: http://forums.virtualbox.org/viewtop...&... Someone logged in as "chronos", hit refresh on the tab displayed, it tried to resolve the servers and started working. Try logging in as chronos with "password" as the password (no quotes) and see if that does the trick."
- GeekLad
"It may be a problem with the network configuration on your installation of VirtualBox. Do you have any other VirtualBox virtual machines where networking is working fine?"
- GeekLad
"Security and confidential information is a valid concern and one that many others share. The beauty of the project is that it is open source, so there will eventually be other Linux distributions derived from Chromium OS. I suspect that the majority of them will allow disconnection from the cloud. They will allow the machine to operate completely independently, without requiring the user to ever store their information online."
- GeekLad
"Did you import the chromium.ovf file or just add the .vmdk file to a new virtual machine? If you import the chromium.ovf file it should work without issue."
- GeekLad
"It shouldn't matter what type of host system you're using for VirtualBox. Did you import the chromium.ovf file? You need to import the appliance into VirtualBox for it to work. I've updated the instructions to include this info."
- GeekLad
"Yeah, you'll have to create your own virtual machine and then add the .vmdk file to it. There's a tutorial on TechCrunch on how to do it: http://www.techcrunch.com/2009......"
- GeekLad