Modify

#34 closed Bug (Works For Me)

Pixelchecksum returns wrong values

Reported by: stevy80@… Owned by: Jon
Milestone: Component: AutoItX
Version: 3.2.10.0 Severity:
Keywords: Cc:

Description

Hello,

I developed an application with visual c# under windows xp. This program uses autoitx3.dll. Everything worked fine until I upgraded the system. With the new cpu (64 bit) - still under xp - the pixelchecksum function (aprox. in the half of the cases) returns wrong values (-2147483648).

After this, I tried the program on two more machines with Intel P4 cpu, and the results was the same.

I tested the checksum at these machines with autoit main too, and that worked perfectly. So I think the problem is in autoitx.

Attachments (1)

AutoItXTest.au3 (757 bytes ) - added by Valik on Jan 29, 2008 at 1:30:41 AM.

Download all attachments as: .zip

Change History (3)

in reply to:  description comment:1 by Jpm, on Jan 17, 2008 at 3:34:05 PM

Replying to stevy80@gmail.com:

Hello,

I developed an application with visual c# under windows xp. This program uses autoitx3.dll. Everything worked fine until I upgraded the system. With the new cpu (64 bit) - still under xp - the pixelchecksum function (aprox. in the half of the cases) returns wrong values (-2147483648).

After this, I tried the program on two more machines with Intel P4 cpu, and the results was the same.

I tested the checksum at these machines with autoit main too, and that worked perfectly. So I think the problem is in autoitx.

You have to know tha tautoitX3 have not be ported to X64. So certainly tou get a crash looks to me as the result of the -2147483648. Jon will confirm

comment:2 by Valik, on Jan 29, 2008 at 1:31:50 AM

Resolution: worksforme
Status: newclosed

With the above attached file, since you didn't provide one, it runs fine on 64-bit Windows running with 32-bit AutoIt/AutoItX. I'm marking this as works for me.

Modify Ticket

Action
as closed The owner will remain Jon.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.