Randem Systems Support Board

Why would InnoScript want to move a file from where the user saved it in the first place. The user should just save it where they want it... They should know where they want to save it... Moving it would only cause much confusion and complicate things.

I am sure you have heard of a File Move using an  API call.  This can be done when the user presses Save.  Or even a menu choice to move the project file to the project folder.  Just a thought.  Merry and Happy!

On second thought, There is no way for InnoScript to determine the project folder before the project is created. By then the user will have already created the project in the location they wanted it to be.

When you create a new project, you are suggesting that InnoSript use the vbp path to present to the user to save the project. It is a good idea.
 
Look in C:Program Files (x86)Common FilesRandem SystemsRelease for the following files:
 
AutoUpdateW.exe - 09/25/2010
FileDownloadW.exe - 09/16/2010
RSGenRtnsW.dll - 09/16/2010
 
Make sure these files are registered, for if there is another files with the same name registered you may get the subscript error.

No i did not have 9 or anything earlier than 10 installed.
I even looked at the folder tree.
 
My two PCs have identical folder structure so it does not matter.  i have had no problems with this aspect.
 
i should have said that InnoScript should present the path to the app Scripts folder when saving the project as the default.
 
I always present my users with meaning full suggestions that they are allowed to change.
usually that means people have less of a struggle using the application.

If that is the cause of the subscript error, you installed version 10 over version 9 and that is a no-no. You were either supposed to install it in a different folder or uninstall the old version. That is a known issue and why it was instructed NOT to do what you have done...
 
The .pjt file is saved where YOU saved it, so if it is not where you like it it is not InnoScripts fault. You can save it anywhere you like. So how is that an improvement?
 
If you are moving the project around then you should be using Relative Addressing In InnoScript then include all your files in the project foler in sub folders. Go to the Options Tab then choose Relative Paths.

The subscript fatal error is case by the option in InnoScript to check for updates on startup.
Fatal because InnoScript does not start.
I have to go to Process Explorer and kill a Randem file that looks for updates before trying loading the main InnoScript. This cycle repeats over and over if the checkbox is checked.
If I can get in and uncheck it, the error no longer occurs and InnoScript starts properly every time.
 
Improvement Suggestion:
Put the project file .pjt in the same folder as the .vbp or .vbg (which ever is selected to use) or the Scripts folder so we have portability.  I move my files via pen drive between my two copies of InnoScript on different laptops as I travel.  Now I have to hunt down the .pjt file and copy it way down a tree to put it where you like it.  Not very friendly.

1) InnoScript does not search source files. Add the dll files in the Add Files tab then InnoScript will place them in the script. If they are system files then they do not need to be in the script at all for the OS will have these files automatically. If they are third party files then add them in the Add Files tab and you can set the flags there. Since you mentioned that they are not to be registered the flags will not really be needed unless you need to do something special with the files or the installation, like alwaysoverwrite or ignoreversion or something like that.
 
2) I can't answer why you are using any file that you are using. InnoScript will only confirm that you are using it or something you are using is using it. You have to make the determination either to include it or not.
 
3) Try installing the complete updated version of InnoScript. zip and post your exe, vbp, vbg and I will take a look to see what I see that may be causing the error.

(1) Source as in source, not the .vbp project or .vbg group files.
There are .dll(s) that are called out in Declare statements in the source. These are not registered (or registerable).  VB looks for them in the app path and the system32 folders.  They do not apperar in the .vbp or .vbg files.
They MUST be included in the script since they must be distributed as part of the install package.  What flags do I use with that type of situation?
I know how to set the paths but NOT the flags.
Maybe treat it like a text file??? or is there something unique for this type of file?
 
(2) The script generator is still trying to include the debug file dbghelp.dll. Why is it being included?  Each Win has its own version.  You have to go to M$ to get the latest  
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
Not sure if it is compatible.
 
(3) getting that subscript out of range error at InnoScript startup.

1) You have to change the JET template to reflect YOUR systems location for the listed files. You would need to download the appropriate files from the website and place them on your system then change the template to reference that location.
 
2) Everything is what it should be, the 1 is the Major version number of your project. If you do not want it there you can go into the parameter screen and delete it (Settings->Parameter DefaultDirName}
 
3) You are very unclear just what you mean. InnoScript does scan your VBP file and every exe/dll/ocx that is included to find referenced dlls, then includes then in the script with the proper flags.

(1) 10.4 B4 Some things changed and some new stuff is added.
What is this?  I have no E: Drive
Source: e:server dataRandemDevelopSupportmdac_typ_281.exe; DestDir: {tmp}; Flags: ignoreversion; MinVersion: 4.0,4.0; OnlyBelowVersion: 0,6.0
Plus 4 additional similar related to mdac & jet.
If these files are needed then give an error if cannot be found.  this could easily be overlooked until later then we have to go back and fix it.
 
(2) ALSO after I compile the first time I get
Parameters Default Dir Name formed like this
filename 1
what is the 1.  That should not be there.
If I delete it is does stay deleted ?ut if I forget it will garbage up the script.
 
(3) InnoScript is missing some .dll(s) that are called out in the source.  these are NOT registerable .dll(s).  They do not appear in the Project Reference.  Does InnoScript provide a way to scan the VB source to find these and include them i the script?  Suggestions please!
So how would I write a script line to include them (no registration needed).  Can be loaded in the app folder since the app.exe looks there for them.  These are unique to this app.  Just need help with the Flags.

Try this to see if you can do some of the things you want to do with the VBRuntime, Search and Exclude folders.
 
 
 
Just replace the old exe with this one.

I have researched the issue and you are correct if you change the search/exclude folders and do not exit the old folders are in use for the script generation. This is being worked on and will be in the next maintenance release. Still looking into the VB Runtime folder issue.

You can point to other location but you also need to exclude the locations you do not want InnoScript to use.
 
Unless VB6 has been updated lately there are no New Universal Files. If you want to change the location use the template function to replace those lines or place your NEW files in the location InnoScript expects them to be.

As I have said twice before the universal files provided are OLD.  I donwloaded the newer ones from MS and want to point at those.  The Entry allows me to enter a different path but then InnoScript erases that and put in the path to the old files under Inno folder.  That is very confusing.
 
COPY? Then follow Windows protocol and do not allow highlighting of the text.  Highlighting indicates COPY ability.  What language are you using that does not allow you to copy highlighted text to the clipboard?
 
Bottom line is:  only use files where InnoScript wants them and not where the user wants them.
Except for VB control files that are in System32.  They are registered there but you can point elsewhere for a copy of them.  Sorry I am breaking your rule.  So why cannot I do this for my other files?