SystemFunction036 debugging problem

[James Hawkins]

> Is this program linking to SystemFunction036 statically or dynamically?

I'm not really sure.  Is there another way to tell besides doing a trace+all?

> If it is linking dynamically (i.e. with GetProcAddresa), one option to try
> is to completly remove SystemFunction036 so it is not exported from
> advapi32.dll. It might then be that the apps that call it will see that it
> is not present and do something else.

Actually I just added the stub to advapi32, because the program will
crash when it tries to call an umimplemented function.  The main
problem is that the program is expecting some result from
SystemFunction036 (Filip thinks it might be a random generator thing),
but it's next to impossible (or so it seems) to implement it correctly
without documentation of what it does.  I wanted to be able to see
which function calls this to see whether I can get in there and keep
it from calling.


On Tue, 28 Sep 2004 07:01:33 +0800, Jonathan Wilson <jonwil at tpgi.com.au> wrote:
> Is this program linking to SystemFunction036 statically or dynamically?
> 
> If it is linking dynamically (i.e. with GetProcAddresa), one option to try
> is to completly remove SystemFunction036 so it is not exported from
> advapi32.dll. It might then be that the apps that call it will see that it
> is not present and do something else.
> 
> Another option is to try to contact the author of the app in question
> (MyPhotoCalendars or whatever it is) and ask them about the function.
> 
> 



-- 
James Hawkins