dockhwa.blogg.se - Black screen red alert 2

Note the space between gamemd.exe" and -winĬompatibility : Win Xp Service pack 2 (Seems to be most stable)ĩ.

Go to properties and in 'Target' add at the end after " add -winĮxample Target: "C:\Users\Roberto\Desktop\Red Alert 2\gamemd.exe" -win Create a shortcut to the game and move it to your desktopħ.

Edit aqrit.cfg in notepad and change these two settings to 1 as in below:Ħ. Download zip file and extract the files to the directory that you've patched the game inĥ. Rename Yuri's Revenge to gamemd.exe, then run the patch to patch the game (for ra2, rename to game.exe)Ĥ. Download the graphics patch from and extract it into the directory that you just movedģ. Copy the directory Red Alert 2 (Typically found in C:\Program Files (x86)) to somewhere outside of Program FilesĢ. If this doesn't work follow use this method instead:ġ. Follow all the video steps and it should fix it. Maybe is somthing went wrong with your monitor settings and now you hav a duplicate monitor. Applications that have high requirements on the GPU (drawing, 3D, games, video) are expected to not work as good as on the real hardware, if they work at all.I found that this bug happen on windows 7 64bit and windows 8/8.1 too. The virtual GPU itself is from around 1995-2000 in terms of capabilities. They use after all a virtual graphics card, not your host's real graphics card. Virtual machines will never be as powerful as the host, especially on the video side. Keep in mind that programs like these tend to push the physical hardware to their limit hence the strict requirements for the graphics card (GPU) specifications. See the "Upload attachment" tab below the reply form.

Save only the first "VBox.log", ZIP it and attach it to your response.

With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".

Start the VM from cold-boot (not from a paused or saved state) / Observe or recreate the problem / Shutdown the VM (force close it if you have to).

We need to see a complete VBox.log, from a complete VM run, where the problem occurs: Moving this to "Windows Guests" from "OSX Hosts", the problem that you're having is with your Guest.