Custom Query (16363 matches)
Results (409 - 411 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #664 | fixed | kstart --iconify VBoxManage startvm "WinXP"" changes resolution to 640x480 -> fixed in SVN/1.5.2 | ||
| Description |
Mandriva Linux 2007.1
When my computer boots into KDE I want that Virtualbox automatically start "Snapshot 1" of my virtual WinXP.
#!/bin/sh
With "kstart --iconify" the virtualbox window starts minimized just as I want it.
When I use the virtualbox window it shows my virtual WinXP desktop at resolution 1024x768.
So can you developers please change the way how Virtualbox saves the resolution of the virtualbox window when it starts a snapshot of a virtual machine: when the virtualbox window starts minimized you should save the display setting when it is not minimized.
In the mean time could you provide me with an easy WinXP command/script that I can click on my virtual WinXP desktop to change immediately the display setting from 640x480 to 1024x768? That seems to me now the fastest solution to my problem.
Off course I will try myself to find on the Internet how to do that WinXP command. vatbier |
|||
| #665 | fixed | VirtualBox Aborts on WSUS 3 install | ||
| Description |
I've been trying to get WSUS 3, Windows Server Update Services, the newest version, installed on my VBox 1.50 VM. It gets through most of the way, and then the whole VM is aborted. It doesn't always seem to crash at the exact same spot, but always towards the end of the install. It did this on 1.40 also. I was excited when 1.50 came out as I was hoping it would fix this. My host is a Ubuntu 7.04 Desktop/Server (mixed). My guest is a Windows Server 2003, MS SQL 2005 SP2, AD DC. I've tried it with 256, 512, and 1gb of RAM. I've tried installing it on the primary C and secondary E drives. I've tried clipboard on/off, networking NAT or bridged, mouse integration on/off. I've completely recreated an entirely new VM in 1.50 (instead of my upgraded 1.4) and it always always crashes on install. No error messages or warning signs, just kablooey ABORTED. This is not a blue screen, or Windows crashing as far as I can tell. I can't imagine WSUS 3 is all that complicated a program. I've installed the newest version of SMS - SCCM 2007, Softgrid, and a host of other things, but WSUS 3 is the only thing that seems to crash it like this. Thanks. |
|||
| #669 | fixed | Unsupported Linux (Arch Linux) | ||
| Description |
VirtualBox cannot determine the type of my distribution (neither in host nor in guest mode). I use Arch Linux with 2.6.22-ARCH kernel. |
|||

