Iznogoud Posted February 11, 2016 Share Posted February 11, 2016 Hello, I have created a script on my own computer for uninstalling and installing a specific customer application. For some reason it works great on my own computer, but i doesn't run at all at the customer his or her computer. I have a Windows 7 Professional - 64-bit machine and the first machine i have tested it at the customers location was a 32-bit machine, so ok, maybe that is the problem, but at an other computer with 64-bit it also doesn't work. So i installed AutoIT with editior on both machines, but a simple RUN command doesn't work. #RequireAdmin Run("C:\TEMP\Setup2010\setup.exe") With or without the RequireAdmin doesn't make a difference. Could someone help me to understand why my script works great on my own computer, but when you move it to another computer it doesn't work? If you compile it or not. Kind regards, Remco Link to comment Share on other sites More sharing options...
Radiance Posted February 11, 2016 Share Posted February 11, 2016 If the script really runs with admin privileges, it's either the path is incorrect (check what FileExists() returns) or the program runs but immediately quits because of something else (check if Run() returns a Process ID). Link to comment Share on other sites More sharing options...
JohnOne Posted February 11, 2016 Share Posted February 11, 2016 If the path is correct and that is the whole code, then it's probably firewall/antivirus/security software blocking it. AutoIt Absolute Beginners Require a serial Pause Script Video Tutorials by Morthawt ipify Monkey's are, like, natures humans. Link to comment Share on other sites More sharing options...
rudi Posted February 11, 2016 Share Posted February 11, 2016 Hello. What error message do you receive, or what happens, when you try to start your application? A shot in the dark: Did you do the compilation of your AU3 script as 32bit or 64bit application? As your PC is x64 and the destination PC is 32bit you will have to compile it as a 32bit application regards, Rudi. Earth is flat, pigs can fly, and Nuclear Power is SAFE! Link to comment Share on other sites More sharing options...
JohnOne Posted February 11, 2016 Share Posted February 11, 2016 5 hours ago, Iznogoud said: i have tested it at the customers location was a 32-bit machine, so ok, maybe that is the problem, but at an other computer with 64-bit it also doesn't work. AutoIt Absolute Beginners Require a serial Pause Script Video Tutorials by Morthawt ipify Monkey's are, like, natures humans. Link to comment Share on other sites More sharing options...
rudi Posted February 11, 2016 Share Posted February 11, 2016 Then use processmonitor.exe to check, what's failing. Earth is flat, pigs can fly, and Nuclear Power is SAFE! Link to comment Share on other sites More sharing options...
Iznogoud Posted February 11, 2016 Author Share Posted February 11, 2016 The problem was a Windows environment connect to a UNIX environment and appearantly it was some kind rights issue. Nothing to do with the script. I copied the files to a local folder and it would work also. But ControlClick and some other features where not working properly and i had to use the #AutoIt3Wrapper_UseX64=n switch on a 32-bit machine. Do i really need to compile the script as a 32-bit AND a 64-bit version or can i just keep using a 32-bit compiled version for both systems? Link to comment Share on other sites More sharing options...
JohnOne Posted February 11, 2016 Share Posted February 11, 2016 3 minutes ago, Iznogoud said: can i just keep using a 32-bit compiled version for both systems? Yes, you can. AutoIt Absolute Beginners Require a serial Pause Script Video Tutorials by Morthawt ipify Monkey's are, like, natures humans. Link to comment Share on other sites More sharing options...
rudi Posted February 11, 2016 Share Posted February 11, 2016 For almost 100% of all use, also on x64 machines you are fine using scripts, that are 32bit compiled. Avoid using x64 compiled scripts, except you should really need to compile it as x64 executable. If you need to have two versions of a script, 32bit and 64bit, then use a third script, distingish the @OSARCH, and depending on the result fileinstall() the appropriate compiled script (MyScript32.exe, MyScript64.exe), then run(), what's needed. Earth is flat, pigs can fly, and Nuclear Power is SAFE! Link to comment Share on other sites More sharing options...
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