I'm About to Give Up on InnoScript - Part 1

Started by tomb, November 28, 2007, 06:29:15 AM

Previous topic - Next topic

Tom Buggy

Scripten.exe and Scr56en.exe you just download from our site
 
I got them from C:VBPackageFiles on my development system.  I'm not sure if I created this folder or it was already there.  In any case, here's version comparison between what I used and what I just downloaded from your site.
 
scripten: Used - 6.2.29.0  Your site -      5.50.4134.600
scr56en:  Used - 5.50.4134.0   Your site -   5.50.4134.600
 
Implications?
 
Is not another approach for Vista to prepare a separate Setup and have it install to C:UsersPublicAppName?  Or, require Administrator Privileges and install to Program Files?  I realize that you advise against the latter (I did read your Vista page) but most all of our customers run on a single standalone computer that they control, so it may not be a problem.  Plus, I read an article in vbforums that recommended Run As Administrator for Setups.
 
The Available Switches window may have come from Inno Setup versus InnoScript.  I'll do some more research and see if I can get a screen print.

Randem

Scripten.exe and Scr56en.exe you just download from our site at https://randemsystems.com/innoscript//
 
1) Yes, that is exactly what I was suggesting. In that way you can duplicate the script at anytime with just a push of a button anytime you add something new. Use the script as documentation also.
 
2) No, if your program is not setup to use the APPDATA environment yet. You can add in the Vista Template so that you can have your installation detect if it is on Vista and install to the C:\Users\Public\YourAppName folder so that your app can work under Vista (with no protection).
 
3) Available Switches? InnoScript doesn't build such a screen in the installation. Perhaps you can show a screen print of this window?
 
Thank you for your kind words...

Tom Buggy

BINGO!!!   With some additional script modifications I was able to get a Setup package that installed the app on my clean XP system under Virtual PC.  Although additional testing is required, the app appears to be running well - including being able to print a label over anetwork to a shared label printer.
 
The major script change was to install dymolbl.exe to the App folder versus the Sys folder (we both missed that one).  I also had to research the location of scripten.exe and scr56en.exe on the development system.
 
Three followup questions:
 
1) I have been working only with the script file.  I think I should also modify the project file you sent me.  Any suggestions in that regard?
 
2) I assume the script is usable for Vista installs except for the taboo of installing to Program Files when there are data files to be written to in that folder (which is my present situation).  Should I prepare a separate script for Vista installs?
 
3) At the end of the Setup run there's an Available Switches window with an OK button.  It doesn't seem to have any value to end users and may confuse our neophyte users.  Is there a way to eliminate it?
 
Thanks again for your EXTRAORINARY support.  I not only have a Setup package I can be comfortable with versus PDW, but I have learned a great deal about the installation proces (which is far more complex than I imagined).  You can be sure that I will recommend InnoScript and Randem Systems to others.

Randem

Yes, Remove it from the run section. I had to change InnoScript no to do that with ActiveX exe's.

Tom Buggy

Not quite to bed.  I noticed that you included the dymolabel.exe in the Run section.  I'm not sure about that - I think its inclusion is what screwed up my standard Dymo Label installation with my first script try a few days ago.  I'll do some research (that word again) in the Dymo SDK I used to integrate label printing into the app.
 
Now I am going to bed!

Tom Buggy

I''ve been away most of the day (and night).  It's now 12:20 AM and I'm just reading you new posts.
 
Yeah right, you know I know what I'm doing!  But I will say that I'm gaining on it, including research.
 
The labels.dll and labels.def files will likely never change or, if they do, they will be newer.
 
The ghmhelp.chm file definitely has to be added, which I also noticed after my last post.  The varbetterbutton.hlp file isn't needed and I should delete it in the PDW build.  I'm not sure about msstkprp.dll - I'll do some research!
 
With respect to you question, what I did was use your script and change the sources of the files to their location on my system.  That's what I meant by editing the script.
 
Going to bed - I'll finish things in the morning and test on my clean Virtual XP PC.

Randem


Randem

You also have support files in you added into PDW that may need to be added into your script:
 
varbetterbutton.hlp
msstkprp.dll
ghmhelp.chm
 
 
Question: Did you edit the script or did you change the values in InnoScript to recreate the proper script? The latter is the best way.

Randem

2 - The file Labels.def has to be installed where the Labels.dll is installed and you could remove the ignoreversion flag for if there is already a file by that name there it will not be copied over.
 
The tricky part is if the labels.dll file is not newer that the one already installed then it will not be copied and the labels.def file will. So it's a judgement call for that file...

Randem

1 - Yes Include the scripting runtime
 
2 - Don't worry about that message, it is a warning to get you to make sure of what you are doing. An I am sure...

Tom Buggy

Thanks.  I've edited the script for the file locations on my development system and ran a compile with Inno Setup.  Two questions before I attempt to use the generated Setup program:
 
1) I notice that Scripting Runtime (scripten.exe) is not included in the Files or Run sections. scrrun.dll is included in the References section.
I use File System Objects in the app.  Should Scripting Runtime be included in the script?
 
2) Inno Setup gave a Warning about labels.def: Unsafe File Usage - the ignoreversion flag should not be used on files installed to the Windows System Directory.  What to do about that?

Randem

Thank you...
 
I will do you one better than just the script. Here is the pjt file for InnoScript that will allow you to change things and still get the same results. You can change the search and file location inside InnoScript and that way you don't have to start from scratch...
 
 

Tom Buggy

Some progress but not enough.  The Setup ran to a point until I got an error reading the file VB_dcom_mdac_jet_autosetup.exe - says the file is corrupted.
 
Don't know what else might be done regards downloading the Setup .exe file.  I guess my next step is to edit the script file to substitute my file sources and then run Inno Setup.
 
I'm leaving now for a few hours.  If you have any other ideas I'll read them on my return and work on all this tomorrow.
 
I will say this is one of the best examples of user support I have ever experienced.  My compliments and thanks.

Randem

Ok, use the same link in the post to download the zip file.
 
The Installer Problems link has been fixed in the post also...

Randem

BTW: I downloaded the exe file and had no problems starting it up...