Randem Systems Support Board

You should have capitalized PLEASE about starting a new thread.  
 
At this point I am using the Beta version but I won't be distributing the app for another few weeks.  As for the network install, I had a PDW-created Setup running on both a XP and Vista system.  I understand app on each machine and database on the host (server).  What I do for the client machines is have them install via a UNC Path to the host.  The installation instructions tell the user to overwrite the C:\Program Files\GHM installation path with the UNC Path.  That was simple when the app and the data files were in the same shared folder - I just used \computername\sharename where sharename was the folder name.  I guess I'm now going to have to provide different sharename content for each OS.  
 
Most of the users have only two or three client machines using the app.  In fact, most of those on a network only use a single machine, in which  case I have them install locally to C:\Program Files\GHM on that single machine.
 
I believe I'm okay with concurrency checking.  I've read your Database Problems article and I will read it again.

Good,
 
No, well leave the title as is for others to read how one change actually change their minds about something with the proper support.
 
I take it you are using the Beta version to deploy your system?
 
On the Network install what do you expressly want to do? The app will still need to be installed on each users machine and the database on the network.  
 
How many users will you support and does your app support concurrency checking for the database currently?
 
Look here for more information - Database Problems
 
For the Network install... Please start a new thread...

After all I've been through, and all I've put you through, I believe I now have one Setup program for all Windows systems from Win98 through Vista.  I specified 98 as the minumum Windows Version and NT 4.0 as the minimum NT Version, adapted a script, created a Setup program, and installed and ran the program successfully on my XP Virtual PC and Vista computer.  (BTW, the Dymo dll register problem did not occur on either system.)
 
All I can say is a sincere Thank You.  Although you may not be done with me yet as I move on to a Network install and test, I believe I have a decent handle on things.  In fact, if you can, you can change the title of this enormous thread from I'm About to Give Up on InnoScript to I'm Comfortable With InnoScript.

That's good that you have found the templates useful. They were designed for users to add functionality to the program before it was actually in the program.

You are select the MINIMUM Windows version that your app will be installed on.
 
That is very clear and it is in the documentation.  No need for intuition.  I aplogize for the check boxes comment.
 
As for the ActiveX exe, I'm glad my experience with the dll found something for you.  Although I didn't need it, thanks for the details on the template.  Believe it or not, I've done so many things template-wise that I've become pretty good at it.

The line in your template file should look something like this:
 
[Files]
Source: e:workstombuggydymolbl.exe; DestDir: {app}; Flags:  restartreplace sharedfile;

Use the template and copy the line with that exe into it and remove the regserver flag from the line in the template and re-run.
 
That should solve that problem. The correct to that will be in the next release of the Beta version.

I just realized that you are attempting to register a ActiveX exe. You should not be register that file it will register itself when it is run.

1) You are select the MINIMUM Windows version that your app will be installed on.
 
2) I got the error message on Vista also but not on XP.

1) I guess we have a bit of a communications and/or semantics situation, or I'm misinterpreting the sequence direction of the selections in the OS sections.  I am assuming a top-to-bottom sequence - for example, if I select Win95 I also get 98 and ME covered.  And, if I select NT 4.0 I also get Wink2K, XP and Vista covered.  Is that correct?  Or, is it the opposite - for example, selecting Vista gets you everything above it in the list?  (BTW, check boxes instead of option buttons would be more intuitive.)
 
My Vista Setup has only the Vista button checked and None in the other section.  The other Setup has Win95 and Win NT 4.0, which worked on XP.
 
2) That's interesting news.  I'm going touninstall the Dymo printer on the Virtual PC XP system and see what happens.

1) it is exactly logical. The latter What? Your app is the only thing that will support these OS's and you already stated that they did. So why would selecting that it would be OK to be installed on these OS matter?
 
2) I did not get a problem here when I installed your software and I definitely do not have the Dymo printer installed.

1) I interpret what you're saying is that I should make Windows 98 the Windows Version selection and Vista the selection for NT Version.  It doesn't seem logical (or at least intuitive) that the latter will support XP and Win2K - ?
 
2) I do not believe that the situation with the Label Printer is just a Vista situation.  I assume (research/testing required) that it will occur on any system that doesn't have the Dymo printer and software installed.  I'll have to do some research on Tasks.  I'm not aware that you can use questions to the user in the script or setup and base what is installed on the answers.
 
As for why the dll fails, the regservr error code is 0x4.  I'll do some research.

1) If the script states that the lowest version of Windows is 95 (Which should not be supported without Advil or something stronger) and the NT version is Vista it will support all versions.
 
2) First Question: does the label printer work on Vista even with the file not registered? If so then on Vista just do not attempt to register the dll. Two of the same lines except one uses the OnlyBelowVersion parameter and one uses the MinVersion parameter to distinguish between Vista and every other OS.
 
You could put in a task that the user can select to install the label printer or not and on Vista you could disable the task and un-check it.  
 
Second Question: Why is the dll failing. Research, research, research...

You will be pleased (and perhaps surprised) to know that your project code is now included in my app and that I have successfully installed and ran from Inno Setup packages for both XP and Vista.  Now that the GetSpecialFolders code is in the app I can support any version of Windows if any users are foolish to be on any version less than Win2K.  Just for kicks I may try to install and run on an old Win98 computer in the storeroom.
 
I'm looking forward to getting back to thorough testing of the app itself and network installations.  Before I do I have two questions:
 
1) For whatever testing reason I have two Setups.  One has Windows 95 selected in the Windows Version section of the script and NT 4.0 selected in the NT Version section.  The other script has None selected in Windows Version and just Vista selected in NT Version.  Can I use the first one for all systems, including Vista?
 
2) Not all users will be using the Dymo Label Printer.  When I install on my Vista system that does not have the Dymo software installed I get an error during install that says the .dll for Dymolbl.exe cannot be registered.  I can click Ignore without consequence but I'm concerned that users will be confused, especially given the presented Not Recommended associated with Ignore (even if I provide documentation about it).  I've tried to use the noregerror flag in different parts of the Flags: section for the file but I still get the error message during install.  Is there a specific place in the Flags section where noregerror has to be placed, or is there another way around the situation?  I really don't want to have spearate Setups for those that do and don't have the Dymo printer.

Also add the folder to the Exclude Folder Tabs so that it won't happen again, if I am reading you correctly.