Version 4.1.8r75467 Full Screen fails

[MacNala]

Running VBOX 4.1.8r75467 on Windows 7 Ult SP1 16 bit and guest machines Win 7 SP1 64 bit.
Using Host+F changes virtual window to full screen but guest os does not resize. This is a change from previous version.
Obviously there must be a setting I am not seeing such as "auto-resize",
Where is it?

[Perryg]

When in windowed mode you will find them in the view tab (top left) and when in full screen if you don't have the mini menu use the host+home toggle to open the menu.

[MacNala]

Many thanks. I had not thought of looking there.
Has it always been there or did 4.1.8 guest additions introduce it?

I am still having a problem. One of my virtual machines responds correctly with the auto-resize selected but another identical machine does not.

Where should I look to check the differences?

[Perryg]

First thing to do is re-install the guest additions. Watch for any error message that is noted.
If this does not fix the error post the guests log file (as an attachment).

[MacNala]

I have reinstalled the guest additions.
The result is I get a full screen window but the OS does not re-size in it. The log of the installation of the additions is attached.
What next?

[Perryg]

What happens if you change the processor count to (1)?

[MacNala]

Both the working and the non-working machines had 2 processors defined.
I changed the non-working machine to have 1 processor but this did not change the result, it still does not resize the OS portion of the fullscreen window.
Thanks for the input, what next?

[Perryg]

I don't know. The log shows that everything is happy and should be in full screen.
You might want to report it to bugtracker

[MacNala]

Thanks again for all your help. I will checkout the bugtracker link you gave.

[MacNala]

I am still having trouble with this problem.
I have raised a new defect over on Bugtracker #10201.
I am delving deeper into the reasons why 3 of four virtual machines fail to resize the guest OS.
I have tracked down a difference which I do not know if it may be the cause.

The working machine vbxw72 has its definitions in
C:\Users\Alan Cameron\Virtualbox VMs\vbxw72\vbxw72.vbox

whereas the vbxw71 failing machine definitions appear to be in
C:\Users\Alan Cameron\.Virtualbox\Machines\vbxw71\vbxw71.xml

Could this be the cause of the different operation?
If so how should I correct the failing machines?

I have full Windows 7 Backups including System Images of all the machines on an NAS device.

[MacNala]

I am still in trouble with the OS resizing.
I have tried cloning the failing machines and exporting/re-importing but without success.
Has anyone got any other ideas to solve this?

[MacNala]

Anyone??

[Perryg]

The two different locations you are showing are due to the version of VirtualBox that was used to create these guests. Ver => 4.* will be in VirtualBox VMs where as versions before would have been .Virtualbox\Machines. I don't have this mix any more as I saw it causing *me* issues and converted all of mine shortly after 4.* came out to the new format.

I know others still have this mix though and they don't seem to have full screen issues, and as I said the log files really don't show a reason.

Make sure that auto-resize is enabled (host+g) and that you are not in scaled mode (host+c). Other than that I don't what else to tell you.
The hot keys are toggles. You might need to use them 2 times especially if it was in auto-resize to begin to make sure that it is enabled.

[MacNala]

Thanks for the opinions.
I have taken your advice and have reduced the number of old machines in the old format to 1.
I am a little disappointed that when I installed version 4 I did not convert then but I did not see any information about how to do that. To be fair it is not really necessary to provide all the information to users of what is a niche product. I only use it 1. because it is free and 2. to test out various pieces of other software before committing it to production machines. But I do expect it all to work.
Complicated beyond maintainability.

[jnpapado]

I had the same issue on a couple of my Windows 7 guests, come to find out that somewhere along the line my guests picked up some ACER monitor that would not support the higher resolutions. So I went into the device manager for each of the guests and uninstalled the monitor (I had to click the box that asks about deleting the drivers from my system). After a reboot, the guests picked up the Generic non-PnP Monitor and everything is fine now... All resolutions work.