On Thursday, July 19, 2012 5:05:33 AM UTC+2, kcrisman wrote: > > > > On Wednesday, July 18, 2012 3:40:41 PM UTC-4, Volker Braun wrote: >> >> You can just run >> >> VBoxManage startvm "Sage-5.0" >> >> from a script and it'll fire up that Virtual Machine. >> >> > Thanks. > > I assume that it's not possible to have Sage start with just the one click > from a pre-installed VM, at this time? (Assuming we don't use Emil's > solution of the self-installing Linux partition!) >
I am not into the details of building VMs and integrating them into Windows atm, but I think this would be possible with a similar command to Volkers "VBoxManage startvm". There is also the command "VBoxSDL", which will start the VM window without the VBox control window, and "VBoxHeadless", which will start the VM in the "background". There could be a windows batch script that starts a sage vm (CLI only, running the server) in "headless mode", shows an appropriate message, waits for it to start up and then opens the windows default browser with the sage notebook. The mentioned "self installing Linux Partition" is unrelated to this topic, because this "Windows exe installer" of the Live CD OS would require the user to reboot the machine and startup Linux ( For completeness: it is not a linux partition but an automated "frugal install to NTFS", where the linux OS is inside a single file on the Windows partition (similar to the popular Ubuntu - WUBI install). About the long startup time: In reality it is not really necessary to have that, because lots of the time consuming stuff during bootup is not necessary when starting a linux in a fixed virtual environment. E.g. the whole hardware detection stuff could be minimized. Of course this would mean to use a customized boot script inside the initrd of the vm ... greetings emil Here's one user's comments: > ++ > 1) Fire up Virtual Box (only one click if there's an icon on the desktop, > which I THINK we can have happen for everyone). > 2) Fire up Sage inside Virtual Box (only one click, I think). > 3) Be told that the mouse doesn't work anymore (even though it > demonstrably does), and have to click "okay". > 3) Wait a LONG time (about 1.5 minutes) while lots of scary stuff is > printed on the screen, including "Booting 'Fedora Linux", etc. It's > actually worse when there is a blank, black wondow, and nothing else is > happening. During that endless 90 seconds, I had to click "okay" three > separate times when being told again that "mouse pointer integration" was > not supported. > 4) now we have a normal Sage notebook screen (see attached screenshot1), > whew. > ++ > Fine for personal use, but not so great for a lab. > > -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
