[Kamokazi]

Originally Posted by FormerPalmOS

Putting it in the XIP won't make it any faster by itself. Turning it into a module will. Currently, the default d3dm.dll is a module. If you install a cab with a new .dll (like d3dm_ati.dll) it probably won't be any faster since that isn't a module. You would need to make it a module, fit it into the virtual memory space, and cook it into the ROM. Assuming the default d3dm.dll, the d3dm_ati.dll and Samsung Omnia driver (d3dmxsc50pb.dll) are all roughly the same size, you should modularize all of them into the same VM space, then in the kitchen select only one.

But correct me if I am wrong - D3D is for 3D rendering only. What we need to speed up is 2D rendering - and that's DDRAW.DLL (again, already a module). We need a faster DDRAW.DLL. Then again, TF3D makes mostly calls to the 3D rendering DLL (as specified in the registry), not the 2D... So really we need both?

He is talking about 2D Rendering in Landscape mode...currently there is a major performance hit. And there are some people that have cooked in a newer dll that makes it much faster...ddi.dll from a new Diamond ROM.