> Now a brief commercial: > > Sun's VirtualBox is working so well and so > transparently, I have not booted up my other Solaris > notebooks (running on bare metal) for over a week now > (& don't see any incentive at least in the near > future). > > Let's face it, we will be fooling ourselves to think > that we can convince anyone (or even ourselves) to > install OpenSolaris on a brand new notebook. Doing > so will void the warranty. As I mentioned in my > previous post, nowadays you can get a very decent > notebook (say, dual core, 3GB/250GB) at a very decent > price (mine for ~$650). Running VirtualBox allows us > to break the hardware barrier. > > As a side note, Build 98 is working really great. > Its GUI package installer now works like a charm. > Everyone's got to try it. :-)
Normally, for security considerations, I won't play sound on the machines that I consider important. Perhaps this fear has become unfounded, but I am not 100% convinced. (Thus, VBox seems to offer a pretty good alternative of playing sound in the Vista host, but also blocking it in the Solaris guest.) However, this weekend since I was interested in getting ready for Songbird: http://blogs.sun.com/pengyang/entry/what_s_new_in_the I decided to enable sound for one of my VBox machines. To do this, you must: 1. Click on the Audio box in VBox (while the VM is off), then check the "enable audio" and "Windows sound driver) boxes. 2. Restart the OpenSolaris VM. 3. Download and Install the OpenSound driver from http://www.4front-tech.com/download.cgi 4. Do an osstest command to see the sound works OK. At the present time, when the sound is enabled, the Vista host won't go into suspend mode. For the reasons I mentioned above, I don't know whether this is a bug or can be spun as a feature. -- This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
