Direct3D Support?

[viking]

I am running Win7 - 64 bit host and Guest. I have tried Virtualbox 3.x and currently v4.1.12 (which is the highest version I can use to be compatible with ShadowProtect).

When I try to enable the screen saver(e.g. bubbles) I get the message "The screen saver can't run because it requires a newer video card or one that's compatible with Direct3D". I have already enabled 3D support and use 128 MB of video RAM.

If I understand correctly, I can install Direct3D Support when installing the Guest Additions by answering "No" in the "Would you like to install basic Direct3D support" dialog displayed when the Direct3D feature is selected. Furthermore, this has to be done in Safe Mode.

I have already installed the Guest Additions (in normal mode and I do not remember if I selected YES or NO). Thus, I wanted to reinstall in safe mode.
I booted in safe mode and selected "Install Guest Additions". However, nothing happened. How do I reinstall?

[Perryg]

Installing the wddm drivers in Windows 7 does not require the guest to be started in safe mode.
Install in normal and answer no to the first question.

If clicking install guest additions does nothing they are more than likely mounted. Use the file manager and start the install manually.

Warning: OpenGL screen savers can be really hard on the CPU, especially in a Virtual Guest. If you must use a screen saver I always suggest a blank screen. After all it is called a screen saver and what better way to save the screen?

[viking]

Installing the wddm drivers in Windows 7 does not require the guest to be started in safe mode.
Install in normal and answer no to the first question.

If clicking install guest additions does nothing they are more than likely mounted. Use the file manager and start the install manually.

Warning: OpenGL screen savers can be really hard on the CPU, especially in a Virtual Guest. If you must use a screen saver I always suggest a blank screen. After all it is called a screen saver and what better way to save the screen?

I was able to install the WDDM driver; Thanks!
My main reason for doing this was not to run the screen saver but try to get Windows Media Center to work (I couldn't play any files).

I now got two new problems.
1. With the new WDDM driver, the maximum resolution is 1400x1050. With the previous driver I had a resolution closer to the one on the host (1920x122) so the VM filled up my whole screen in windowed mode. Is there any way to set the resolution to the same using the WDDM driver?

2. When I now start Windows Media Player using the WDDM driver, the screen goes black with occasional flashes. I need to reboot.
If I turn off 3D in the Settings, WMC starts up normally (but I can still not play any files)

[Perryg]

Normally I find the mouse drag, or the host+f toggle, to work better, but you should be able to use the maximise box on the title bar and get close to full screen but stay in windowed mode. Usually the reason that the guests video settings is off (within the guest) is due to a wrong monitor choice.
You can force the resolution if you really want to by using VBoxManage and setting the resolution manually (see your VirtualBox users manual).

Now playing video in a guest is really IO intensive and the bigger the screen the harder it is on the guest. Make sure that you have given enough resources to the guest and don't run anything that might steal resources on the host.

You can post the guests log file (as an attachment) and we can see if there is anything that jumps out as an issue.

Oh and it may be that you will have issues with the version of VirtualBox you are using. The wddm drivers were improved in the newer releases. => 4.2.*

[viking]

Normally I find the mouse drag, or the host+f toggle, to work better, but you should be able to use the maximise box on the title bar and get close to full screen but stay in windowed mode. Usually the reason that the guests video settings is off (within the guest) is due to a wrong monitor choice.
You can force the resolution if you really want to by using VBoxManage and setting the resolution manually (see your VirtualBox users manual).

Now playing video in a guest is really IO intensive and the bigger the screen the harder it is on the guest. Make sure that you have given enough resources to the guest and don't run anything that might steal resources on the host.

You can post the guests log file (as an attachment) and we can see if there is anything that jumps out as an issue.

Oh and it may be that you will have issues with the version of VirtualBox you are using. The wddm drivers were improved in the newer releases. => 4.2.*

Unfortunately, the last supported version (by ShadowProtect) is v4.1.12 . Is it possible to use the wddm drivers from 4.2.* in v4.1.12? If so, how would I install those?

When I started Vbox today, the higher resolution, 1920x1096, was somehow magically set again. No clue how it come back by itself (highest available option yesterday was 1400x1050). Anyway, the Black & Flashing screen was still there as soon as I started Windows Media Center. I have attached the log file for this session.

[Perryg]

Is it possible to use the wddm drivers from 4.2.* in v4.1.12? If so, how would I install those?

I doubt it. It is not uncommon for older GAs to work on newer releases, but the new GAs in an older version of the base install usually causes a big issue.
I guess you could try to clone and try it on the clone, so nothing is lost.

[viking]

Is it possible to use the wddm drivers from 4.2.* in v4.1.12? If so, how would I install those?

I doubt it. It is not uncommon for older GAs to work on newer releases, but the new GAs in an older version of the base install usually causes a big issue.
I guess you could try to clone and try it on the clone, so nothing is lost.

How would I install just the wddm drivers?
Did you see anything suspicious in the log file that could explain the black/flashing screen with WMC?

[Perryg]

This does not look good

Guest Log: VBoxMP::VBoxMPValidateVideoModeParams: WARNING! host does not like special mode 1920x1096:32 for display 0

Nor do all of the OpenGL warnings, so there is an issue. Normally I would say just upgrade and this should take care of it, but if you can't you can't. I don't know what else to tell you. You can always post a ticket at bugtracker and see what the DEVs have to say. Be sure to include this log file and describe the issue completely.