AutoHotkey Community
It is currently May 27th, 2012, 10:23 am

View unanswered posts | View active topics


Board index » AutoHotkey » Scripts

All times are UTC [ DST ]



Post new topic Reply to topic  Page 2 of 2
  [ 28 posts ]  Go to page Previous  1, 2
  Print view | E-mail friend Previous topic | Next topic 
Author Message
corrupt
 Post subject:
PostPosted: August 7th, 2007, 12:42 am 
Offline
User avatar

Joined: December 29th, 2004, 1:28 pm
Posts: 2545
The compiling process on my main XP machine is extremely slow and always produces an error after compiling if I right-click on a script to compile.
Quote:
Windows cannot find 'c:\WhateverTheScriptIsCalled.ahk'. Make sure that you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search.
...but it's probably something configured incorrectly that I've been too lazy to troubleshoot since I've had this issue on this machine since I first installed AutoHotkey (1.0.23 I think). The compiling process is much faster and doesn't produce an error when using the GUI though...

Results from current XP PC I'm using ( P4 2.8 ):
Quote:
Time for standard compiler with UPX (in ms): 1203
Time for FavorFast compiler with UPX (in ms): 1000
Time for FavorFast-Pentium4orHigher compiler with UPX (in ms): 1188
Time for standard compiler without UPX (in ms): 375
Time for FavorFast compiler without UPX (in ms): 359
Time for FavorFast-Pentium4orHigher compiler without UPX (in ms): 563

Results from the XP PC with the issue ( P4 2.4 ):
Quote:
Time for standard compiler with UPX (in ms): 1188
Time for FavorFast compiler with UPX (in ms): 1937
Time for FavorFast-Pentium4orHigher compiler with UPX (in ms): 1594
Time for standard compiler without UPX (in ms): 359
Time for FavorFast compiler without UPX (in ms): 938
Time for FavorFast-Pentium4orHigher compiler without UPX (in ms): 1093


MsgBox that appeared 4 times while running the script (only on the PC with the issue)
Quote:
---------------------------
iLib
---------------------------
The script file "D:\iLib" does not exist. Create it now?
---------------------------
Yes No
---------------------------
Path to the ahk script used for testing and also the script that was chosen to compile:
Quote:
D:\Program Files\AutoHotkey\Compiler\test\New AutoHotkey Script.ahk


Report this post
Top
 Profile  
Reply with quote  
engunneer
 Post subject:
PostPosted: August 7th, 2007, 1:09 am 
Offline
User avatar

Joined: August 30th, 2005, 8:43 pm
Posts: 8667
Location: Salem, MA
corrupt wrote:
MsgBox that appeared 4 times while running the script (only on the PC with the issue)
Quote:
---------------------------
iLib
---------------------------
The script file "D:\iLib" does not exist. Create it now?
---------------------------
Yes No
---------------------------


Exact same thing happened to me with the "non-standard" ahk2exe files. (Mine was in C:)

I ended up just puting a blank file there, but maybe Chris should see if there is something included wrong in the code.

_________________
Image
(Common Answers) - New Tutorials Forum - Humongous FAQ


Report this post
Top
 Profile  
Reply with quote  
corrupt
 Post subject:
PostPosted: August 7th, 2007, 1:21 am 
Offline
User avatar

Joined: December 29th, 2004, 1:28 pm
Posts: 2545
Interesting...

I forgot to mention that although I get errors when compiling using my main XP machine unless I use the GUI, the scripts always seem to compile and run ok. I'm using the standard ahk2exe file (not a modified version) :) along with the other 2 versions. The same test script and AutoHotkey files/versions don't seem to produce any errors on a different XP machine. The only difference I'm aware of is that the XP machine that doesn't produce any errors has AutoHotkey installed in the standard location on C:\ (not sure if that makes any difference).


Report this post
Top
 Profile  
Reply with quote  
Chris
 Post subject:
PostPosted: August 7th, 2007, 1:36 pm 
Offline

Joined: March 2nd, 2004, 3:36 pm
Posts: 10720
During compiling, ahk2exe invokes AutoHotkey.exe briefly to find out if any stdlib or userlib functions need to be included. The command line it uses is:
Code:
sprintf(szCmdLine, "\"%s..\\AutoHotkey.exe\" /ErrorStdOut /iLib \"%s\" \"%s\""
   , m_szAut2ExeDir // Contains a trailing backslash.
   , output_include_filename
   , aOutputScriptFilename);
AutoHotkey.exe's /iLib switch was added in v1.0.47.00 to support the standard library. It tells AutoHotkey.exe to inform ahk2exe of which library files need to be auto-included.


Report this post
Top
 Profile  
Reply with quote  
engunneer
 Post subject:
PostPosted: August 7th, 2007, 5:59 pm 
Offline
User avatar

Joined: August 30th, 2005, 8:43 pm
Posts: 8667
Location: Salem, MA
it's interesting that it was looking for an actual file called iLib in the root directory of our drives. Is this a problem of the test ahk2exes, or a problem on our end? I guess it is our fault for not having the latest AHK to support this switch.

_________________
Image
(Common Answers) - New Tutorials Forum - Humongous FAQ


Report this post
Top
 Profile  
Reply with quote  
corrupt
 Post subject:
PostPosted: August 8th, 2007, 12:25 am 
Offline
User avatar

Joined: December 29th, 2004, 1:28 pm
Posts: 2545
engunneer wrote:
it's interesting that it was looking for an actual file called iLib in the root directory of our drives. Is this a problem of the test ahk2exes, or a problem on our end? I guess it is our fault for not having the latest AHK to support this switch.
If I answer Yes it does seem to create a file called iLib (without any extension) in D:\. Hmm... I am using the latest version of AutoHotkey...


Report this post
Top
 Profile  
Reply with quote  
Chris
 Post subject:
PostPosted: August 8th, 2007, 5:35 pm 
Offline

Joined: March 2nd, 2004, 3:36 pm
Posts: 10720
Maybe there is a copy of AutoHotkey.exe older than 1.0.47.00 in the directory above the one that contains your ahk2exe. If so, that would explain it because that is the file that ahk2exe tries to launch.


Report this post
Top
 Profile  
Reply with quote  
corrupt
 Post subject:
PostPosted: August 8th, 2007, 11:54 pm 
Offline
User avatar

Joined: December 29th, 2004, 1:28 pm
Posts: 2545
Chris wrote:
Maybe there is a copy of AutoHotkey.exe older than 1.0.47.00 in the directory above the one that contains your ahk2exe. If so, that would explain it because that is the file that ahk2exe tries to launch.
There doesn't seem to be. I am running ahk2exe in its' standard installation location relative to AutoHotkey.exe.


Report this post
Top
 Profile  
Reply with quote  
Chris
 Post subject:
PostPosted: August 9th, 2007, 12:32 am 
Offline

Joined: March 2nd, 2004, 3:36 pm
Posts: 10720
That's pretty mystifying. It might remain an unsolved mystery until I can find some way to reproduce it here.

Is it possible you have an older version of AutoHotkey.exe in one of the directories in your PATH environment variable?


Last edited by Chris on August 9th, 2007, 1:09 am, edited 1 time in total.

Report this post
Top
 Profile  
Reply with quote  
trik
 Post subject:
PostPosted: August 9th, 2007, 1:02 am 
Offline

Joined: July 15th, 2007, 1:43 am
Posts: 1320
Time Elapsed for Compile wrote:
Time for standard compiler with UPX (in ms): 1594
Time for FavorFast compiler with UPX (in ms): 984
Time for FavorFast-Pentium4orHigher compiler with UPX (in ms): 1157
Time for standard compiler without UPX (in ms): 422
Time for FavorFast compiler without UPX (in ms): 375
Time for FavorFast-Pentium4orHigher compiler without UPX (in ms): 500


Erm, I don't really know what info to put so I'll just put everything on the CPU :roll:

Processor:
AMD Athlon 64
Processor 3500+

Optical Drive:
LightScribe Double/Dual
Layer 16x max
DVD R/RW drive

Memory:
512MB

Hard Drive:
160GB

_________________
Religion is false. >_>


Report this post
Top
 Profile  
Reply with quote  
corrupt
 Post subject:
PostPosted: August 9th, 2007, 5:05 am 
Offline
User avatar

Joined: December 29th, 2004, 1:28 pm
Posts: 2545
Chris wrote:
That's pretty mystifying. It might remain an unsolved mystery until I can find some way to reproduce it here.

Is it possible you have an older version of AutoHotkey.exe in one of the directories in your PATH environment variable?
As I have a couple XP machines here (one with the issue and one without), I'll see if I can determine the cause.


Report this post
Top
 Profile  
Reply with quote  
corrupt
 Post subject:
PostPosted: August 9th, 2007, 5:24 am 
Offline
User avatar

Joined: December 29th, 2004, 1:28 pm
Posts: 2545
Well... :oops:

It seems that I had gone playing around with the path settings and executable filenames recently and was really running version 1.0.46.17 instead. Running the latest version got rid of the error messages. The error message and delay with right-clicking to compile was fixed by changing the advanced options for the compile option. If I remember correctly, I had played around with the settings originally due to problems with compiling long filenames in WinME originally. Changing the options to the default values now allows me to right-click then compile without any error messages being produced. It also compiles much, much faster when right-clicking now.

Sorry for the confusion. Thanks for looking into it :) .


Report this post
Top
 Profile  
Reply with quote  
Chris
 Post subject:
PostPosted: August 9th, 2007, 5:27 am 
Offline

Joined: March 2nd, 2004, 3:36 pm
Posts: 10720
Thanks for the follow-up. I'm glad you solved it.


Report this post
Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 2 of 2
  [ 28 posts ]  Go to page Previous  1, 2

Board index » AutoHotkey » Scripts

All times are UTC [ DST ]

Who is online

Users browsing this forum: XX0 and 25 guests

You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Powered by phpBB® Forum Software © phpBB Group