S. Brandt wrote:
Alexey Eremenko wrote:
VirtualBox uses WineD3D which forwards all Direct3D calls via OpenGL.
In fact you can install WineD3D on your host platform, so all Direct3D
code runs via OpenGL on host.
Sorry, could you please explain in more detail?
Just putting the VBox D3D dlls
Your installer needs to do the following on the guest:
copy %system32%/d3d{89}.dll to %system32%/msd3d{89}.dll
copy vbox's d3d{89}.dll over %system32%/d3d{89}.dll
copy vboxd3d{89}.dll to %system32%/vboxd3d{89}.dll
and copy vboxogl*.dll there as well.
Note, on win2k/xp systems you have to go to
On Wed, Jul 1, 2009 at 11:36, Leonidleonid.lobac...@sun.com wrote:
Your installer needs to do the following on the guest:
copy %system32%/d3d{89}.dll to %system32%/msd3d{89}.dll
copy vbox's d3d{89}.dll over %system32%/d3d{89}.dll
copy vboxd3d{89}.dll to %system32%/vboxd3d{89}.dll
and copy
S. Brandt wrote:
Just - not enough memory for nice resolutions ...
Oh, that's only D3D7 which obviously is not supported.
Direct3D 7-Testergebnisse: Abbruch in 8 (3D-Gerät wird erstellt): HRESULT =
0x8007000e (not enough memory)
VBox window automatically resizes to D3D screen size - OK.
Thx,
Leonid wrote:
Your installer needs to do the following on the guest:
copy %system32%/d3d{89}.dll to %system32%/msd3d{89}.dll
copy vbox's d3d{89}.dll over %system32%/d3d{89}.dll
copy vboxd3d{89}.dll to %system32%/vboxd3d{89}.dll
and copy vboxogl*.dll there as well.
Note, on win2k/xp systems
Spent some time debugging in building amd64 on windows.
There is a mistake in configure.vbs file, without this fix, win.x86 will be
built even if on amd64 windows box.
I attached the diff file, pls make the correction.
There are other issues on building the recompiler on windows, debugging
Antonio,
On Tuesday 30 June 2009, Antonio Doldo wrote:
today I have compiled the svn r21049 debian package, but VirtualBox
exit with a crtical error:
Well, this particular changeset cannot be responsible for your
problem.
Fallimento nella creazione dell'oggetto COM VirtualBox.
Mark,
On Saturday 27 June 2009, mark browser wrote:
thank you for your reply and sorry for distracting this list, but I
couldn't find any information regarding this issue. I'm not sure if you got
me right, so here is the original message I wrote:
-
I am looking for a host audio mixing
Hi,
On Wednesday 01 July 2009, Huihong Luo wrote:
Spent some time debugging in building amd64 on windows.
There is a mistake in configure.vbs file, without this fix, win.x86 will be
built even if on amd64 windows box.
I attached the diff file, pls make the correction.
There are other
On 07/01/2009 01:55 PM, Frank Mehnert wrote:
Walt,
On Wednesday 01 July 2009, walt wrote:
r21113 | vboxsync | 2009-07-01 04:48:47 -0700 (Wed, 01 Jul 2009)
xpcom: first go at making xpcom bitness-safe
For me, running on Linux, vbox won't even start after the above
commit: Failed to create the
Hi Frank,
I managed to build all pieces on win.amd64 except these two modules:
VBoxRem2.rel and RuntimeR3NoCRTGCC
I had to comment these 2 out from .kmk files in order to build the rest.
Can you shed some lights on how to build these two? What mingw gcc version are
you using on amd64
11 matches
Mail list logo
