Randem Systems Support Board

Jim Carlock  
 
The reasons that InnoScript would take absurdly long amounts of time searching for files would be:
 
1) Very slow computer.
2) Paths to files for InnoScript to search for are not at the front of the search path.
3) Paths to files for InnoScript to search are not in the search path at all.
4) Files in the dependency files are not found.
5) Paths for InnoScript to search have large amounts of files.
 
If there are missing files InnoScript has to search all search paths for the file not to be found.
 
Test here for large scripts takes less than 4 minutes in Unsafe mode and under 1 minute in Safe mode.
 
All information is search for in dynamic mode to ensure proper searching. Static information would prove to be problematic expecially if files were moved.

I seem to have reached some sort of limit with that last message.
 
Send me an email if you'd like to talk about it. I am interested in some things concerning the remote updates.

I'm not sure how you've set up the searching for the files and such, but I'll tell you what I'm thinking.
 
In the past, I've done some database programming that basically downloaded about 20 to 30 minutes worth of information over a DSL line (about 150KB per second). It was performing the downloads via ODBC connections to a remote database. My initial attempts when creating that, indicated that it would take 24 hours to do the processing.
 
So what I did was I ran make table queries inside a database that brought just the necessary information over rather than running 20 queries to do processing on the data remotely, it would download the whole tables and then proceed to process locally (running the processing queries on localized tables).
 
In the end, more data was transferred initially to get the data to a local database (MS Access) and even though more data was transferred, the localized tables were processed 23.5 hours faster.
 
And I'm thinking something similar can be done with InnoScript. I'm thinking the whole process
could be brought down to less than two minutes for me.
 
I don't know how you process everything. If you'd like to talk about it over email or what not, you have my email address.
 
A linked list works really great in this case, or even an Access database could work really well.
 
You could set up a list of well-known files in an Access database, or in a regular text files, it can be loaded instantly and held in memory. Files that are determined could be compared against this list rather than being searched for in unknown locations. Such things as %SystemDrive% and %SystemRoot

Clint,
 
Also, you are probably running in 'Safe Mode'. This will take considerably more time to find the files for it cannot use any files in the system folders. If you run in 'UnSafe Mode' it will be measurably faster, but you need to be careful of what you deploy.

Clint,
 
If you check the log, all the dependency files that InnoScript looks for are there. As far as the long searches, check the log and/or your script for the files that are found. The folders that it found the files in is probably not in your search list.
 
What happens is that when InnoScript finds the dependency file, it also has to find all the files that are in the dependency file and these files folder names may not be in your search list.
 
Look at your script and log and make sure that the folders that InnoScript need to search are listed.

Hi,
 
The one thing that drives me crazy when using Inno Script is that it does not display which dependency information file it is looking for.  So, I basically have no way of knowing which files I should be storing in one of the 'path' directories.
 
I did make a dependency folder and copied all .dep files into this directory, and have this listed at the beginning of the list of directories to search, but the program still seems to be searching for LONG periods of time (the message displayed is ... Searching for dependency information files 8 of 13) for some unknown files.  It does eventually find them, because after the script compiles, it says all files were found.