Cannot get full screen in 3.0.2

Discussions related to using VirtualBox on Windows hosts.
Post Reply
CarlSeiler
Posts: 11
Joined: 17. Jul 2009, 01:42
Primary OS: MS Windows 7
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Linux, Windows XP, Windows Vista

Cannot get full screen in 3.0.2

Post by CarlSeiler »

Just upgraded from 2.2.x to 3.0.2. After installing, I could not get the screen to go to full screen. I reinstalled with the new Guest additions and I almost have a full screen, but not really. It's 1280x960 instead of the native 1280x1024 which I could get in 2.2.x. Now I have a black bar at the top and bottom of the screen about 5/8" tall each. How do I get full screen back?
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Cannot get full screen in 3.0.2

Post by Perryg »

Does this do the same thing on the Linux and the Windows PC?
With version 3.0.2 you need to install the Windows guest additions in safe mode.
Also sometimes you need to fiddle with the screen by using the full screen hot keys (host + F) a few times to get it all sorted out.
CarlSeiler
Posts: 11
Joined: 17. Jul 2009, 01:42
Primary OS: MS Windows 7
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Linux, Windows XP, Windows Vista

Re: Cannot get full screen in 3.0.2

Post by CarlSeiler »

Perryg wrote:Does this do the same thing on the Linux and the Windows PC?
With version 3.0.2 you need to install the Windows guest additions in safe mode.
Also sometimes you need to fiddle with the screen by using the full screen hot keys (host + F) a few times to get it all sorted out.
I don't have it installed on my Linux machine as host. I get similar but not exactly the same thing with the Windows Host and Xubuntu guest. After fiddling around with the hot keys, host + F and host + G, I was able to get both the Windows XP and Xubuntu guests to display in 1280x1024, but I'm not sure what the combination of key strokes necessary to get them going right is. I certainly don't recall dealing with this situation in 2.2.x, but at least I know how to get it to work now. Thanks for the suggestion.
Post Reply