View Single Post
Old 08-15-10, 10:06 AM   #8
Seeadler
Pacific Aces Dev Team
 
Join Date: Mar 2001
Location: Northern Germany
Posts: 1,096
Downloads: 169
Uploads: 0


Default

Quote:
Originally Posted by clouclou View Post
What worries me is that we already have a d3d9.dll in Windows 7 System32! Duplicate?
The d3d9.dll in the System32 folder is the original Microsoft d3d9.dll and should _never_ be overwritten!

The d3d9.dll of this fix is a Proxy.dll and must always be placed in the folder of the Exe which use this fix.

A proxy DLL exploits a peculiarity of the Windows OS. An EXE looks at first in his own folder for dll's to load and afterwards in the System32 folder.
If now a d3d9.dll is present in the EXE's folder, this dll will be load and not the original dll from the System32 folder.

This new dll takes up towards the commands from the Exe and passes them to the system instead of the original dll. Some of these commands can now make other matters, which are not foreseen in the original DLL, before forwarding the command to the system.

This d3d9.dll here for example set the number of pre-rendered images. The one of the widescreen fix override the resolution. Therefore mods with a d3d9.dll are not compatible to each other until someone builds all the extended functions in only one d3d3 proxy dll
__________________
--
Vapor-ware is always easier to sell because there's no limit what it can do!
Seeadler is offline   Reply With Quote