blahblahblah5038 Posted February 10, 2008 Posted February 10, 2008 I have had auto it working on my desktop for almost 2 years now, but when I installed it on my new laptop and started running scripts with it, I started getting "unhandled win32 exception" errors that offer to let me debug in visual studio. what's up with this? Noteworthy works:Fast Pixel SearchSigned: WG
Tomb Posted February 10, 2008 Posted February 10, 2008 is your new pc vista? if it is, you can right click on the application and go to properties, and set it to work for compatibility mode of xp service pack 2 and it might work. my new pc is vista, and i have had some problems like this.
GaryFrost Posted February 10, 2008 Posted February 10, 2008 You might try a new version of autoit also. SciTE for AutoItDirections for Submitting Standard UDFs Don't argue with an idiot; people watching may not be able to tell the difference.
blahblahblah5038 Posted February 10, 2008 Author Posted February 10, 2008 I took vista off my machine. I am runing XP SP 2 on both machines, and I have tried the newest release version and the beta. Noteworthy works:Fast Pixel SearchSigned: WG
Uten Posted February 10, 2008 Posted February 10, 2008 chkdsk, defragment and retry. Then report back. Without any information about the script and AutoIt version used (if compiled) it's not easy to help you.. Please keep your sig. small! Use the help file. Search the forum. Then ask unresolved questions :) Script plugin demo, Simple Trace udf, TrayMenuEx udf, IOChatter demo, freebasic multithreaded dll sample, PostMessage, Aspell, Code profiling
blahblahblah5038 Posted February 10, 2008 Author Posted February 10, 2008 the code for the program I was working on was only about 10 lines, so I started disabling one line at a time until the program worked. The problem is in a dll call. $storage = DllCall("Grant PJAS DLL.dll", "int", "PJAS", "int", $sides) I tried my other programs on the laptop that use dll's and get the same error. Those programs work perfectly on the desktop. The laptop has version v3.2.10.0 of autoit on it. the desktop has an older version. Noteworthy works:Fast Pixel SearchSigned: WG
GaryFrost Posted February 10, 2008 Posted February 10, 2008 the code for the program I was working on was only about 10 lines, so I started disabling one line at a time until the program worked. The problem is in a dll call.$storage = DllCall("Grant PJAS DLL.dll", "int", "PJAS", "int", $sides)I tried my other programs on the laptop that use dll's and get the same error. Those programs work perfectly on the desktop.The laptop has version v3.2.10.0 of autoit on it. the desktop has an older version.You might need to check what the parameters are supposed to be for that dll. Verify that both are supposed to be "int" SciTE for AutoItDirections for Submitting Standard UDFs Don't argue with an idiot; people watching may not be able to tell the difference.
Uten Posted February 10, 2008 Posted February 10, 2008 Also versify that you have the same user rights on both computers. Please keep your sig. small! Use the help file. Search the forum. Then ask unresolved questions :) Script plugin demo, Simple Trace udf, TrayMenuEx udf, IOChatter demo, freebasic multithreaded dll sample, PostMessage, Aspell, Code profiling
blahblahblah5038 Posted February 11, 2008 Author Posted February 11, 2008 I checked, and I have administrative rights on both computers. The dll call is correct, and I tried another dll that I know works on my other machine and got the same error on this laptop. If it helps, the error suggests that I should debug using visual studio. Noteworthy works:Fast Pixel SearchSigned: WG
blahblahblah5038 Posted February 18, 2008 Author Posted February 18, 2008 I have resolved my own problem. The problem is not AutoIt, it is visual studio. when an unhandled exception occurs, visual studio activates it's just in time debugger. The error may or may not have been a serious one, but it kills your program all the same. I realized it was not Auto it when I tried playing games, and the games started crashing in the same way. if you have this problem go to this support forum and read the part about Delete the following registry keys: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\DebuggerHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebuggerafter you do that, restart your machine and the problem should go away. Noteworthy works:Fast Pixel SearchSigned: WG
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now