Win7-AMD64 host;WinXP x86 guest - Is 4.3.2x broken?
Win7-AMD64 host;WinXP x86 guest - Is 4.3.2x broken?
I just updated from 4.2.xx and the guest video is locked to something like 400x200 px? undocumented feature? Is it just me?
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Win7-AMD64 host;WinXP x86 guest - Is 4.3.2x broken?
Yeap, it's just you.
But, just to make sure, would you mind sharing some information about your setup according to: Minimum information needed for assistance. The most important part is the zipped VBox.log.
But, just to make sure, would you mind sharing some information about your setup according to: Minimum information needed for assistance. The most important part is the zipped VBox.log.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Win7-AMD64 host;WinXP x86 guest - Is 4.3.2x broken?
Yup, it was me...kinda. New app wiped out default monitor in guest? Anyway thanks for the quick reply, I think I'll have it shortly.
Re: Win7-AMD64 host;WinXP x86 guest - Is 4.3.2x broken?
OK, I'm baffled.
Host: Win7 AMD64 4G Ram 4 core Phenom ATI HD5400 graphics 19kx10k(?)
Guest: WinXP 32 Sp3(?) 1.2G ram
Vbox: 4.2.28 or 4.3.26.98988-Guest Additions-4?
size of initial guest window while loading is very small, but can be expanded once loaded to about 10k x 800.
Vbox window is expandable to larger, but guest stays at 10x8
Before update, load window was 800x600 ish and could be expanded to 14x10 or more and guest followed
Host: Win7 AMD64 4G Ram 4 core Phenom ATI HD5400 graphics 19kx10k(?)
Guest: WinXP 32 Sp3(?) 1.2G ram
Vbox: 4.2.28 or 4.3.26.98988-Guest Additions-4?
size of initial guest window while loading is very small, but can be expanded once loaded to about 10k x 800.
Vbox window is expandable to larger, but guest stays at 10x8
Before update, load window was 800x600 ish and could be expanded to 14x10 or more and guest followed
- Attachments
-
- leyden_Logs_20150317.rar
- I don't have anything older
- (83.29 KiB) Downloaded 11 times
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Win7-AMD64 host;WinXP x86 guest - Is 4.3.2x broken?
Could you please post your "WinXP_1.vbox" zipped? Right-click on the VM, Show in Explorer, zip it, attach it here.
PS. Would you mind switching to full numbers when you're talking about resolutions? It took me half an hour to figure out that 10kx8x actually meant 1024x768 (right?). You know that "k" stands for thousands? So you said that your resolution was 10000x8000.
Similarly, 14x10 actually meant 1400x1050, 1440x900 or 1440x1080?
PS. Would you mind switching to full numbers when you're talking about resolutions? It took me half an hour to figure out that 10kx8x actually meant 1024x768 (right?). You know that "k" stands for thousands? So you said that your resolution was 10000x8000.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Win7-AMD64 host;WinXP x86 guest - Is 4.3.2x broken?
Sorry about the numbers, I had a hard time thinking about how to explain the issue.
I assume 'rar' is OK? You must have opened the logs....
----------------------------------------------------------------------
WOW, I reopened the guest and I have two rez choices [max color] 800x600 and 1920x1080 [which is host setting]
I looked at the winxp_1.vbox and I see some stuff that needs a little tweak [ I know don't do it 'raw', let VB do it].
Learning curve ahead...
TIA
I assume 'rar' is OK? You must have opened the logs....
----------------------------------------------------------------------
WOW, I reopened the guest and I have two rez choices [max color] 800x600 and 1920x1080 [which is host setting]
I looked at the winxp_1.vbox and I see some stuff that needs a little tweak [ I know don't do it 'raw', let VB do it].
Learning curve ahead...
TIA
- Attachments
-
- Leyden_WinXP_1.vbox.rar
- (2.62 KiB) Downloaded 6 times
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Win7-AMD64 host;WinXP x86 guest - Is 4.3.2x broken?
OK, make a backup of your "WinXP_1.vbox" and try with the attached one. See if that fixes it.
For your reference, what I did is to delete the following lines:
<ExtraDataItem name="GUI/AutoresizeGuest" value="off"/>
<ExtraDataItem name="GUI/LastGuestSizeHint" value="1920,1080"/>
<ExtraDataItem name="GUI/LastGuestSizeHintWasFullscreen" value="true"/>
<ExtraDataItem name="GUI/LastNormalWindowPosition" value="4,24,1690,968"/>
<ExtraDataItem name="GUI/LastScaleWindowPosition" value="-32764,-239,640,480"/>
I believe the last one to be the one messing up with your system. I could be very well wrong...
For your reference, what I did is to delete the following lines:
<ExtraDataItem name="GUI/AutoresizeGuest" value="off"/>
<ExtraDataItem name="GUI/LastGuestSizeHint" value="1920,1080"/>
<ExtraDataItem name="GUI/LastGuestSizeHintWasFullscreen" value="true"/>
<ExtraDataItem name="GUI/LastNormalWindowPosition" value="4,24,1690,968"/>
<ExtraDataItem name="GUI/LastScaleWindowPosition" value="-32764,-239,640,480"/>
I believe the last one to be the one messing up with your system. I could be very well wrong...
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Win7-AMD64 host;WinXP x86 guest - Is 4.3.2x broken?
[quote="socratis"]OK, make a backup of your "WinXP_1.vbox" and try with the attached one. See if that fixes it.
Thanks for the effort, but no luck, I've tried a few edits of my own using a text editor [notepad++, good stuff], but no luck either. I need to research the options under the 'view' dropdown, such as 'Auto-resize, scaled, etc.' When attempting to go fullscreen while running I get a 0x00000... memory error and VB aborts. I'm fairly sure NO VBOX or VBOX services are running when I edit, so I assume I'm safe not using VBoxManage?
(see comments added to 'code' lines below )
For your reference, what I did is to delete the following lines:
<ExtraDataItem name="GUI/AutoresizeGuest" value="off"/>
<ExtraDataItem name="GUI/LastGuestSizeHint" value="1920,1080"/> {this gets changed or replaced to weird sizes }
<ExtraDataItem name="GUI/LastGuestSizeHintWasFullscreen" value="true"/> { changed my me (and VB?) to 'false' and stays that way }
<ExtraDataItem name="GUI/LastNormalWindowPosition" value="4,24,1690,968"/> { what exactly do these coordinates mean? 'Start box' starts at 4px down and 24 px from left of screen and extends to 1690 px down and 968 px to the left? - This is not what I think I'm seeing }
<ExtraDataItem name="GUI/LastScaleWindowPosition" value="-32764,-239,640,480"/> {negative numbers ?? If I delete this or change it, it returns as shown here !? }
Again, thanks for your time & effort
Thanks for the effort, but no luck, I've tried a few edits of my own using a text editor [notepad++, good stuff], but no luck either. I need to research the options under the 'view' dropdown, such as 'Auto-resize, scaled, etc.' When attempting to go fullscreen while running I get a 0x00000... memory error and VB aborts. I'm fairly sure NO VBOX or VBOX services are running when I edit, so I assume I'm safe not using VBoxManage?
(see comments added to 'code' lines below )
For your reference, what I did is to delete the following lines:
<ExtraDataItem name="GUI/AutoresizeGuest" value="off"/>
<ExtraDataItem name="GUI/LastGuestSizeHint" value="1920,1080"/> {this gets changed or replaced to weird sizes }
<ExtraDataItem name="GUI/LastGuestSizeHintWasFullscreen" value="true"/> { changed my me (and VB?) to 'false' and stays that way }
<ExtraDataItem name="GUI/LastNormalWindowPosition" value="4,24,1690,968"/> { what exactly do these coordinates mean? 'Start box' starts at 4px down and 24 px from left of screen and extends to 1690 px down and 968 px to the left? - This is not what I think I'm seeing }
<ExtraDataItem name="GUI/LastScaleWindowPosition" value="-32764,-239,640,480"/> {negative numbers ?? If I delete this or change it, it returns as shown here !? }
Again, thanks for your time & effort
Re: Win7-AMD64 host;WinXP x86 guest - Is 4.3.2x broken?
Okay, now I'm really confused -or- vbox graphics adapter has taken a few steps back.
I loaded up a Kali Linux image and the video response is very similar to the WinXP problem - max rez after a very small start screen is 1024x768. I was able to go higher before I updated to 4.3.2x ....so is it the 'new' virtual graphics adapter?
In WinXP, the device manager driver 'update' routine shows two VB graphics adapters available: 4.3.6 (!?) and 4.3.2x, neither of which work like it did before the 'update'. Before, I would see a window about 800x600 as an 'opening' screen, then Windows would finish it's initial startup [after the Win logo] and The virtual machine would go to something like 1600 x 900 which is what it was previously set to using 'display' controls in the control panel. I tried to uninstall 4.3.2x and re-install 4.2.28, but the video still had the same issues......
Now, in the Winxp guest the control panel options are minimal and will not change, and/or grayed out
I loaded up a Kali Linux image and the video response is very similar to the WinXP problem - max rez after a very small start screen is 1024x768. I was able to go higher before I updated to 4.3.2x ....so is it the 'new' virtual graphics adapter?
In WinXP, the device manager driver 'update' routine shows two VB graphics adapters available: 4.3.6 (!?) and 4.3.2x, neither of which work like it did before the 'update'. Before, I would see a window about 800x600 as an 'opening' screen, then Windows would finish it's initial startup [after the Win logo] and The virtual machine would go to something like 1600 x 900 which is what it was previously set to using 'display' controls in the control panel. I tried to uninstall 4.3.2x and re-install 4.2.28, but the video still had the same issues......
Now, in the Winxp guest the control panel options are minimal and will not change, and/or grayed out