Neverware CloudReady (working Chrome OS VM's with sound)

935 views
Skip to first unread message

Piotr Machacz

unread,
Apr 13, 2016, 10:11:49 AM4/13/16
to axs-chrome-discuss
If anyone is interested, I stumbled across this while researching a way of getting Chrome OS virtualised.
This includes a virtual box and a vmware configuration. And even though they both use the virtual box .OVF format, I had no problems getting this booted on either Fusion 8 on Mac or Player 12 on Windows, just open the file with “vmware” in the title. When booted wait 30 seconds or so and press ctrl+alt (option on OS X)+Z to turn on ChromeVox and go from there. The search key is the Windows key on Windows, and Command on OS X.

The one thing i haven’t been able to get to work is ChromeVox next, though this is most likely my stupidity. The image is 
Chrome 44, but I upgraded it to Chrome 47. However, pressing search+shift+Q Q doesn’t do anything as the page would suggest. Do you have to be on the beta or dev channels? If so then for some reason I don’t see the option for this, I go to the about screen, press the more info link but don’t see a change channel button. If anyone knows what’s wrong I’d be interested to know. :D

Devin Prater

unread,
Apr 13, 2016, 10:30:08 AM4/13/16
to axs-chrom...@googlegroups.com
Wow, thanks for this! How much RAM does this need? 

Sent from my iPhone
--
You received this message because you are subscribed to the Google Groups "axs-chrome-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to axs-chrome-disc...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

mattias jonsson

unread,
Apr 13, 2016, 3:22:41 PM4/13/16
to axs-chrom...@googlegroups.com
wich tts?

Deedra Waters

unread,
Feb 8, 2017, 1:20:44 AM2/8/17
to axs-chrome-discuss
I found this message in the archives when i was looking at cloud ready earlier tonight going to see how well this works on my macbook to see if it's worth going through the dualboot setup for neverwear. I'd be interested to do this for several reasons if it's actually doable. at any rate thanks for putting this together. I'm assuming it will let me update it to the current versions of os and apps/extensions/whatever if not, i suppose it will be back to the drawing board. but thanks for putting this together on the surface it definitly looks interesting and worth a shot.

Deedra waters

unread,
Feb 8, 2017, 3:44:20 AM2/8/17
to axs-chrom...@googlegroups.com
curious as to wether there is a version of this that is 64bit. the about info for chromium in says 32bit however 64bit would be even better.:)

Trenton Matthews

unread,
Feb 8, 2017, 10:22:54 PM2/8/17
to axs-chrome-discuss
Hi all!

Chromevox Next does not work on non-Chromebook devices, as it wasn't made for those.  

Chris Brannon

unread,
Feb 8, 2017, 10:33:02 PM2/8/17
to axs-chrome-discuss
Trenton Matthews <queens...@gmail.com> writes:

> Hi all!
>
> Chromevox Next does not work on non-Chromebook devices, as it wasn't made for those.

Non-Chromebook or non-ChromeOS? Don't see why the hardware should make
any difference to the screen reader. I'd think it would run fine on
ChromeOS, regardless of the device it is running on.

-- Chris

B. Henry

unread,
Feb 9, 2017, 8:00:40 AM2/9/17
to axs-chrom...@googlegroups.com
Yes sir, can't figure out why there would be an issue virtualized either, i.e. one would think any issues would be with the whole OS, and even that seems
unlikely.
Is there some difference in how next handles sound, e.g. is it mapped to a different channel, going through some entirely distinct audio server or
something like that?
Also, as long as we are on posible OS specific development, in the longterm vision of chromevox devs is CV-next never going to be used with chrome browsers
on opperating systems other than chromeOS?
And a completely unrelated question if I may: how much diskspace does chromeOS require for a full installation, and does it set up a swqp partition by
default, (if not, how is virtual memory handled)?
Yeah, I know the last couple of questions I can google up, but if one of you good folks can share a bit of your knowledge I'll return the favor
someday...grin
--
B.H.
Registerd Linux User 521886


Chris Brannon wrote:
Wed, Feb 08, 2017 at 07:30:47PM -0800

Chris Brannon

unread,
Feb 9, 2017, 8:31:29 AM2/9/17
to axs-chrom...@googlegroups.com
"B. Henry" <burt1...@gmail.com> writes:

> Yes sir, can't figure out why there would be an issue virtualized either, i.e. one would think any issues would be with the whole OS, and even that seems
> unlikely.
> Is there some difference in how next handles sound, e.g. is it mapped to a different channel, going through some entirely distinct audio server or
> something like that?

Well, Deedra is running ChromiumOS on a non-ChromeBook device with
ChromeVox Next, and it's working beautifully for her. That's native,
not virtualized. She tried virtualized for a while, but I think that
was with ChromeVox and not ChromeVox Next. When running virtualized, it
didn't quite have enough RAM. And some things didn't work out so well,
like streaming.
She installed it eyes-free a few hours ago.
I think her worst struggle was getting her device to boot the USB media.
So we can add ChromiumOS to the list of operating systems that can be
installed without a pair of eyes.
Maybe she can write a bit about her experience when she has email
working again. I don't have answers to your other questions about disk
usage and swap at the moment.

-- Chris
Reply all
Reply to author
Forward
0 new messages