Graphics problems when hosting XP SP3

[finn]

Hi,

I've got a Lenovo ThinkStation 330 (NVidia P620) running a Windows 10 (19024.746) as a host for an Windows XP XP3 guest.

We've configured the graphics (NVidia Mosaic) to merge to physical screens, and present them as one large resolution screen to the guest OS (e.g. 3200x1200).

The problem is a weird striping problem, where it look as though every 2-3 lines are dropped, resulting in an interlaced/stripy look.

The machine catches up after a few seconds and completes the picture, but does not look good when a lot of things on-screen are changing.

I've reviewed forum posts, and tried running the VirtualBox executable using the on-board IntelHD card; and tried various 3D settings in VirtualBox settings and NVidia control panel.

Has anyone run into similar problems, and what should I be look at in order to solve this?

[scottgus1]

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log and the hardening log next to it, zip them, and post the zip file, using the forum's Upload Attachment tab.

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

[finn]

Hi,

Here are the VBox and hardening logs as requested from a recent boot.

Thanks in advance!

[scottgus1]

You're running an unusual Virtualbox executable for the VM:

00:00:01.744975 Executable: C:\Program Files\Oracle\VirtualBox\VBoxSDL.exe

That's usually "VirtualBoxVM.exe".

You're also running a mistaken VM template:

Topic title: "...hosting XP SP3"
00:00:01.876241 Guest OS type: 'WindowsXP_64'

XP 64 bit was a rare beast and its final service pack was "Windows XP and Server 2003 Service Pack 2 - 64-Bit". I am not certain if this interferes or not, but if you really have XP sp3 in the VM then that's 32-bit. It might interfere.

Finally, the VM OS does not have Guest Additions installed. This is probably the big cause.

Install GAs, and try the normal start instead of whatever is starting the VM now, so the VM is run by "VirtualBoxVM.exe". If that works, then try back with VboxSDL.exe, re which see viewtopic.php?f=7&t=36061#p161580. FWIW VboxSDL no longer has a section in the manual, it may be deprecated.