Script "reacting" differently on other computers...?

[Krustbox]

So i made a script that includes a reactionary type of thing, using functions like pixelchecksum or pixelgetcolor inside loops with sleep(50) or so to free up some processing power. The script works flawlessly as designed on MY computer, however I've tested the exact same script on TWO other computers and have the same problem on both. The script is not reacting as precisely on the other computers to changes in pixels with pixelchecksum or finding colors with pixelgetcolor. Even though i use sleep(50) inside my loops it's taking like a full second. So when a color appears on my computer it will take 50 milliseconds to notice it, but on the other computers it takes like an entire second, as if i was using a larger sleep() than i have in there, which is 50. I'm clueless at this point. Anyone had this problem before with scripts working on the computer that they built the script on, but not on others? It is for sure NOT anything to do with resolution sizes, and both of the other computers are actually faster than mine, so it's not a processor issue. As far as i can tell everything is the same and should work the same. Any help is appreciated, thanks.

EDIT:

It's 100% for sure a 64bit vs 32bit problem. Works fine on vista 32-bit machines, does not work on windows 7 or vista 64-bit machines.

Edited December 18, 2011 by Krustbox

[Krustbox]

I've actually been able to determine that it is because of 32-bit vs 64-bit operating systems. It works on all 32-bit systems but fails to work properly on 64-bit system. I have no idea how to fix this, i've tried compiling and running the script in both modes and it makes no difference. It will not work in 64-bit. Any ideas?

[Blue_Drache]

#requireadmin

Otherwise, the only thing I can say is post your code so we can help you diagnose it ... because ...

So i made a script that includes a reactionary type of thing, using functions like pixelchecksum or pixelgetcolor inside loops

you're being extremely vague about what you're doing with it. Edited December 18, 2011 by Blue_Drache

[JohnOne]

I cannot remember where I read this, or the solution if there were one, but I read that some themes which use

a certain method (like aeroglass for example) slow pixel* functions down a lot.

EDIT:

At the risk of failing I think the method used by these themes was named "dwm" or something similar

and the only solution was to turn it off.

Edited December 18, 2011 by JohnOne

[Krustbox]

I cannot remember where I read this, or the solution if there were one, but I read that some themes which use

a certain method (like aeroglass for example) slow pixel* functions down a lot.

EDIT:

At the risk of failing I think the method used by these themes was named "dwm" or something similar

and the only solution was to turn it off.

This sounds like it could be my problem, because it's definitely a pixel problem with pixelgetcolor and pixelchecksum. I

m not using any themes though. All i know is it is 100% for sure a 64bit vs 32bit issue. And like i said compiling or running scripts in either version both do not work properly on windows 7, but work perfectly on 32-bit vista.

Edited December 18, 2011 by Krustbox

[Melba23]

Krustbox,

The "dwm" code JohnOne referred to is this:

_DwmEnable(False)
Sleep(5000)
_DwmEnable(True)
Sleep(5000)
_DwmEnable(False)
Sleep(5000)

Func _DwmEnable($fState)
DllCall("dwmapi.dll", "long", "DwmEnableComposition", "uint", $fState)
EndFunc

Give it a try and see if it helps.

M23