I'd like to try it to see if a faux response to IsDebuggerPresent is all that is required to have CCleaner 2.x run on Windows 95B.
Another fix I found mention of was using a hex editor to find and change the IsDebuggerPresent text to another function call like GetCurrentProcess which has the same number of characters. However, that won't work on programs that self-test for corruption.
Something that just lurks waiting for calls to IsDebuggerPresent then returns False to satisfy the program that the function it won't be using "exists" would be a useful thing.
One thing about CCleaner 2.x that makes me think this may work is in its installed location is an executable named something like win95pop.exe (I don't have it installed now.) Doubleclick that and all it does is pop up the IsDebuggerPresent error message. Looks like a hack made specifically to stop people from using it on Windows 95. Hrmmm, I wonder what would happen if I just deleted that .exe?
Obviously the main executable calls that, or a dll or other file called by the main executable calls it, somewhere up the chain the call to the error popper executable would need edited to stop it.
Edited by bizzybody, Yesterday, 01:27 AM.