If you have in fact discovered a way to provide external resource DLL's entry points to an active running process (in memory only) then it might be possible to put the entire bulk of active memory processes used by the operating system at runtime into a memory manager application (like a mod to himemsys or similar) that allows for the modification to take place at the operating system level during memory allocation prior to the actual running of the eq2 processes that way the modifications are not to the processes of the eq2 client but the OS runtime memory manager (this is a common practice for virus scanners in addition to other resource management tools and utilities that manage bus information between the kernell32.dll and the HAL [hardware abstraction layer] basically your hardware drivers)
anyway I might of took the boat over the falls here but I do believe that the concept is sound. so come all ye critics and point out my flaws cause if I know them I would not be spouting off conceptual fixes
Quote:
|
Originally Posted by Deathbane27
Does this require your DLL thing to work, or is it in the default functionality? Because afaik you're the first to figure out a way to do this. 
Yes, your DLL work would definately be an EULA viloation, so don't release it here. But I encourage you to keep experimenting and see if you can find more built-in functionality we haven't uncovered yet.  Just don't get banned in the process.  |