I downloaded and installed the 7.2 beta as I need to install a VB6 program on a Vista PC. The installation went fine but now I cannot run my 6.0 version. I need this as I don't recall what the the 3 entries at the top left are:
1. VB Runtime files folder
2. VB Basic Project File (.vbp)
3. Inno Setup Script Output File (.iss)
I am a complete novice using both innoscript & innoset up. I was able, with lots of help for people in here, got the V6.0 working perfectly but now I cannot get back into the 6.0. When I try to use my .pjt file made from V6.0 in V7.2 it doesn't do anything, i.e. not shows in the 3 areas noted above. So, I am really, really, in lots of trouble as I cannot use either Version to make a executable file either for XP or Vista. Can anyone help me? I desperately need helpclipart {crazy}
If you have not upgraded since 6.0 you will need to open your pjt file in notepad to get the missing elements if they are not present.
1) The VB runtime folder info can be obtained by creating a new project and then copy and paste that info into your current pjt.
2) Your VB project file. You should know where that is...
3) Your iss file. You should know where you want it to go.
So what do you mean Version 7.0 doesn't do anything? Have you read the instructions? That should clear up most problems. At the main menu Help->Instructions
Take a look at that document and let me know if it clear up things. Things have changed since Version 6...
Ok, I found the reference you mentioned, i.e. C:\Program Files\Randem Systems\InnoScript\InnoScript 6.0\VB 6 Redist Files\
I ran both InnoScript and InnoSetup and both apprently work. Now I just have to update my program, do the Inno things again, and then re-install it on the Vista PC.
I might have created a problem when I installed the V6.0 on the Vista PC as Vista gave me an error about stdole and cannot register library. But, I clicked on IGNORE and the program installed. But now I can not uninstall it
I am wondering if you happen to know how to uninstall the 1st program before I try to install the new Vista version? Or should I just not worry about it and install the newer version and see what happens. I don't want to mess up the client's PC so any suggestions would be nice to have for an old man still learning about PC, VB, and Vista.
I am unsure of what you are installing on the clients computer, InnoScript or your app.
I am installing the .exe file made with Inno Script 7.2 and InnoSet up. I am also wondering if I can test the .exe on an XP PC.
Sure you can. You can test on every OS. It all depends on what components you have included in your installation. Post your script and I will take a quick look.
Ok, here is the .iss file. Note it is Version 6 Build 5. Do I have the right InnoScript?
The program is for a GOLF DOGFIGHT, one where golfer compete against each other based on points. Points are cumulated by 2 pts = par, 4 pts = birdie, 1 pt = bogey, and 0 pts for anything higher than bogey.
I only mention this because of the M. Vick problem.
; InnoScript Version 6.0 Build 5
; Randem Systems, Inc.
; Copyright 2003-2007
; website: https://randemsystems.com (https://randemsystems.com)
; support: https://randemsystems.support (https://randemsystems.support)
; Date: August 28, 2007
; VB Runtime Files Folder: C:\Program Files\Randem Systems\InnoScript\InnoScript 6.0\VB 6 Redist Files\
; Visual Basic Project File (.vbp): C:\Dogfight Manager\Dogfight Manager.vbp
; Inno Setup Script Output File (.iss): C:\Dogfight Manager\Package\Dogfight Manager.iss
; ------------------------
; References
; ------------------------
; Visual Basic runtime objects and procedures - (MSVBVM60.DLL)
; OLE Automation - (STDOLE2.TLB)
; --------------------------
; Components
; --------------------------
[Setup]
AppName=Dogfight_Manager
AppVerName=Dogfight_Manager 6.1.0
AppPublisher=Dave Thomson
AppPublisherURL=www.wise-old-man.com (http://www.wise-old-man.com)
AppVersion=6.1.0
VersionInfoVersion=6.1.0
AllowNoIcons=no
DefaultGroupName=Dogfight Manager 6.0
DefaultDirName=C:/Dogfight Manager
AppCopyright=Copyright 2007 by Dave Thomson
PrivilegesRequired=None
MinVersion=4.9,5.0
Compression=lzma
OutputBaseFilename=Dogfight Manager610Beta
[Tasks]
Name: desktopicon; Description: Create a &desktop icon; GroupDescription: Additional Icons:
[Files]
Source: c:\program files\randem systems\innoscript\innoscript 6.0\vb 6 redist files\msvbvm60.dll; DestDir: {sys}; Flags: sharedfile;
Source: c:\program files\randem systems\innoscript\innoscript 6.0\vb 6 redist files\oleaut32.dll; DestDir: {sys}; Flags: sharedfile;
Source: c:\program files\randem systems\innoscript\innoscript 6.0\vb 6 redist files\olepro32.dll; DestDir: {sys}; Flags: sharedfile;
Source: c:\program files\randem systems\innoscript\innoscript 6.0\vb 6 redist files\asycfilt.dll; DestDir: {sys}; Flags: sharedfile;
Source: c:\program files\randem systems\innoscript\innoscript 6.0\vb 6 redist files\stdole2.tlb; DestDir: {sys}; Flags: sharedfile regtypelib;
Source: c:\program files\randem systems\innoscript\innoscript 6.0\vb 6 redist files\comcat.dll; DestDir: {sys}; Flags: sharedfile;
Source: c:\dogfight manager\boscobeldogfight.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobeldogfightarchive.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobeldogfightpayout.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobelinstructions.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobelpasswords.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobelsenior.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobelseniordogfightarchive.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobelseniordogfightpayout.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobeltodaydogfight.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobeltodayseniordogfight.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\dogfight manager.exe; DestDir: {app}; Flags: ignoreversion;
[INI]
Filename: {app}\Dogfight Manager.url; Section: InternetShortcut; Key: URL; String:
[Icons]
Name: {group}\Dogfight_Manager; Filename: {app}\Dogfight Manager.exe; WorkingDir: {app}
Name: {group}\Dogfight_Manager on the Web; Filename: {app}\Dogfight Manager.url
Name: {group}\Uninstall Dogfight_Manager; Filename: {uninstallexe}
Name: {userdesktop}\Dogfight_Manager; Filename: {app}\Dogfight Manager.exe; Tasks: desktopicon; WorkingDir: {app}
[Run]
Filename: {app}\Dogfight Manager.exe; Description: Launch Dogfight_Manager; Flags: nowait postinstall skipifsilent; WorkingDir: {app}
[UninstallDelete]
Type: files; Name: {app}\Dogfight Manager.url
You are using the very old version. The current version is 7.1 Build 6 and Version 7.2 Build 0 Beta. But what you have will work.
Everything looks ok for all OS's
I have totally screwed up all the Script and Setup files now
I re-installed the trial version and finally got things to work right, i.e. the correct version, etc.
But somehow the Script file is telling the Setup program that
Source: c:\dogfight manager\package\dogfight manager.v7exe.exe; DestDir: {app}; Flags: ignoreversion;
I have no idea how the extra exe got in the name. I have looked at everything I can and cannot for the life of me figure it out.
Everything got really messed up when I went to the new Vista Script. I have no idea how in the world to correct this. I am at the point of dispare. I just have no idea what to do at this point.
Right now it is 5AM EDT and I have been up since 3:45AM trying and trying to figure this out. You help is greatly appreciated and I hope you can guide this old man to the answer.
Here is a snapshot of the InnoScript I am attempting to use. Note the Minimum Versions that I have set. I did get an exe from using InnoSetup and I did try to install it on my other XP PC. It wouldn't install as I got the message that there was a problem with the version of NT on my XP PC.
Another odd thing is that now I have is the a folder C:/Dogfight Manager/Package/Output/Output. I believe there should NOT BE.
I have spent hundreds of hours developing this program and the compliled exe for distribution worked fine on my other XP PC. And it worked on the Visata PC but without the stdole file (which may be a real problem). Now I simply can not get an installation exe file to work on my XP.
Maybe I should set up Script for XP and see if I can get that to install on my XP PC. If that does then I guess I could switch it over to Vista and see if it will install on the Vista PC. (https://randemsystems.support/discus/messages/12/4153.gif)
Aloha,
Yes your iss file is pointing to the wrong location. it should be c:Dogfight ManagerPackageDogfightManager7.iss The Output folder is create by Inno Setup to contain your installation exe.
Oh, I forgot that you were running on 6.x version and it did not handle the VB runtimes correctly unless you added the vb runtime template. I believe that version had the template. It had the flags needed for Vista. But since I see you are using the current Beta version you just add in the VB Runtime template and all will be fine (as I see you have done). No need to worry about the stdole2 file.
Post your new script.
Here is the new script (below this text and a graphic). I have delete most of my duplicate files to eliminate any confusing on my part. I am getting more and more confused at this point using the Vista InnoScript. I don't know where the compiled program from InnoSetup is going. Here is a graphic that show my explanded folder where I keep my VB file which is in them main folder. what is confusing now is the several Output sub folders. Maybe you can explain what they are, if there should be so many, and what I can do about it.
(https://randemsystems.support/discus/messages/12/4164.gif)
Now the script:
; InnoScript Version 7.2 Build 0 Beta
; Randem Systems, Inc.
; Copyright 2003-2007
; Website: https://randemsystems.com (https://randemsystems.com)
; Support: https://randemsystems.support (https://randemsystems.support)
; OS: Windows XP 5.1 build 2600 (Service Pack 2)
; Date: August 29, 2007
; VB Runtime Files Folder: C:\Program Files\Randem Systems\InnoScript\InnoScript 7.0\VB 6 Redist Files\
; Visual Basic Project File (.vbp): C:\Dogfight Manager\Dogfight Manager.vbp
; Inno Setup Script Output File (.iss): C:\Dogfight Manager\Dogfight Manager Beta.iss
; Script Template Files (.tpl): C:\Program Files\Randem Systems\InnoScript\InnoScript 7.0\Templates\Beta.tpl
; : C:\Program Files\Randem Systems\InnoScript\InnoScript 7.0\Templates\VBRuntime.tpl
; : C:\Program Files\Randem Systems\InnoScript\InnoScript 7.0\Templates\Vista.tpl
; ------------------------
; References
; ------------------------
; Visual Basic runtime objects and procedures - (MSVBVM60.DLL)
; OLE Automation - (STDOLE2.TLB)
; --------------------------
; Components
; --------------------------
[Setup]
;UsePreviousAppDir=no
AppId=InnoScript Beta
;-----------------------------------------------------------------------------------------------------
; Taken from VBP Project File Parameters AppName, AppName AppVersion and Company
;-----------------------------------------------------------------------------------------------------
AppName=Dogfight_Manager
AppVerName=Dogfight_Manager 7.0.0
AppPublisher=Dave Thomson
;-----------------------------------------------------------------------------------------------------
AppVersion=7.0.0
VersionInfoVersion=7.0.0
AllowNoIcons=no
DefaultGroupName=Dogfight Manager
DefaultDirName=C:\Dogfight Manager
AppCopyright=copyright 2007, dave thomson, anderson, sc
PrivilegesRequired=Admin
MinVersion=4.0,6.0
Compression=lzma
OutputBaseFilename=Dogfight ManagerBeta
[Tasks]
Name: desktopicon; Description: {cm:CreateDesktopIcon}; GroupDescription: {cm:AdditionalIcons}
[Files]
Source: c:\program files\randem systems\innoscript\innoscript 7.0\vb 6 redist files\msvbvm60.dll; DestDir: {sys}; Flags: uninsneveruninstall regserver restartreplace sharedfile; OnlyBelowVersion: 0,6
Source: c:\program files\randem systems\innoscript\innoscript 7.0\vb 6 redist files\oleaut32.dll; DestDir: {sys}; Flags: uninsneveruninstall regserver restartreplace sharedfile; OnlyBelowVersion: 0,6
Source: c:\program files\randem systems\innoscript\innoscript 7.0\vb 6 redist files\olepro32.dll; DestDir: {sys}; Flags: uninsneveruninstall regserver restartreplace sharedfile; OnlyBelowVersion: 0,6
Source: c:\program files\randem systems\innoscript\innoscript 7.0\vb 6 redist files\asycfilt.dll; DestDir: {sys}; Flags: uninsneveruninstall sharedfile; OnlyBelowVersion: 0,6
Source: c:\program files\randem systems\innoscript\innoscript 7.0\vb 6 redist files\stdole2.tlb; DestDir: {sys}; Flags: uninsneveruninstall sharedfile regtypelib; OnlyBelowVersion: 0,6
Source: c:\program files\randem systems\innoscript\innoscript 7.0\vb 6 redist files\comcat.dll; DestDir: {sys}; Flags: uninsneveruninstall regserver restartreplace sharedfile; OnlyBelowVersion: 0,6
Source: c:\dogfight manager\boscobeldogfight.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobeldogfightarchive.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobeldogfightpayout.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobelinstructions.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobelpasswords.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\boscobelsenior.txt; DestDir: {app}; Flags: ignoreversion;
Source: c:\dogfight manager\dogfight manager.exe; DestDir: {app}; Flags: ignoreversion;
[INI]
Filename: {app}\Dogfight Manager.url; Section: InternetShortcut; Key: URL; String:
[Icons]
Name: {group}\Dogfight_Manager; Filename: {app}\Dogfight Manager.exe; WorkingDir: {app}
Name: {group}{cm:ProgramOnTheWeb, Dogfight_Manager}; Filename: {app}\Dogfight Manager.url
Name: {group}{cm:UninstallProgram, Dogfight_Manager}; Filename: {uninstallexe}
Name: {commondesktop}\Dogfight_Manager; Filename: {app}\Dogfight Manager.exe; Tasks: desktopicon; WorkingDir: {app}
[Run]
Filename: {app}\Dogfight Manager.exe; Description: {cm:LaunchProgram, Dogfight_Manager}; Flags: nowait postinstall skipifsilent; WorkingDir: {app}
[UninstallDelete]
Type: files; Name: {app}\Dogfight Manager.url
[Code]
function GetAppFolder(Param: String): String;
begin
if InstallOnThisVersion('0,6', '0,0') = irInstall then
Result := 'C:\Users\Public\' ExpandConstant('{username}')
else
Result := ExpandConstant('{pf}');
end;
[Comments]
; In the folder where your installation was created is a folder named Support. In this folder you will place the AutoOSUpdater, .Net Framework and the Scripting Runtime installations
; that you want to deploy with your installation. Both you installation exe and this folder need to be deployed fo your installation to work properly
I try running what I believe is the output from InnoSetup and it gives me the message:
... requires Windows NT 6.0 or later.
The installation file is places on my hard drive in C:/dogfight manager/output/
I am so confused and frustrated now that I cannot remember where the installation exe was locate prior to getting and running InnoScript. I think it was in C:/dogfight manager/Package/Output. At this point my mind is numb and blank
Your installation exe was exactly where I told you it should be. You don't use what I stated and you seem to expect good results.
I stated: c:Dogfight ManagerPackageDogfightManager7.iss
You used: c:Dogfight ManagerDogfightManager7.iss
It can't possibly come out the same. So I would imaging that you are doing this with other things as well. Please re-read my last post and you probably want to use Internal Installs... No support folder will be needed in the deployment.
Ah, you see, when I tried the free version 7 it changed how I was doing things. I got totally mixed up and frustrated which I am sure you can understand from my posts, many posts.
So now I am keeping my VB .exe file in my folder, dogfight manager. I have a InnoScript file that used this exe and puts the .iss file in the same (top) folder. I run innosetup and it puts the exe in the sub-folder, dogfight manager/output.
So all seems to be working just fine. I even purhcased the full copy of innoscript today. Figure with all the help you have given me it is well worth it.
I will use the new version of innoscript to make two .iss files, one for XP and one for Vista.
As you suggested once I tried installing the Vista .exe on my other XP PC. Didn't like it as it said I needed a higher NT version, I believe it was 6.0 or higher. So the only way to test the installation of the Vista version is do it on a Vista PC. I might have buy a laptop as my access to the Vista PC is limited at best.
Well, as I said above I purchased the full version 7.2 Build 0 Beta. Now, when I run it I can make a .pjt file and run the file which produces the .iss file. However, when I close down 7.2 and then re-open it the file that I saved is now blank. I assume this means that the trial period is over. No problem.
I paid for the full version today and received the email with the registration codes. The email says to Please enter ALL information as given but doesn't tell me where to enter the information. What am I missing? I HATE being a damn fool who can't figure things out! I am the only one who is this STUPID?
The registration codes are named after the field they go into. I don't follow what you mean...
Go to Help->Enter License Info
Then enter the license info there.
Thank you. This helped. I finally figured out that you meant to run InnoScript and use the HELP > ENTER LICENSE INFO in the tool bar! Perhaps I am one of the stupid ones who end up using your really great program and doesn't realize to use the ENTER LICENSE INFO in InnoScript. Maybe this would be helpful to less knowledgeable use to have this tip in the registration email.
One other comment from a user. An alert comes up when InnoScript that says I should be using 1280X800 resolution. Now, I don't have the ability to change my resolution to that setting. I set the resulations to these sizes on my monitor which is several years old: 1028X768, 1280X768, and 1280X1024. Therefore, I assume you are now using a new, wide-screen monitor. I understand that many people like the wide screen. Maybe one day I will have one if I live long enough and my current PC system needs to be replaced.
Finanlly, I lost my InnoScript file when I used InnoScript after the trial period ran out. Why not just tell the trial user that they can not save changes to a file rather than writing a blank file with the same name when they save the changed file? If this were the case then the trial user would not have to enter all the necessary information again when they purchase InnoScript and enter the registration codes.
Again, thank you for you help. InnoScript is a very useful tools with the ability to make a distribution .exe with an amazing number of options.
That is not the way InnoScript works... Any file you save during the trial period is still available and usable in the full version no changes. This is ALWAYS the way InnoScript has worked and will continue to work.
So you must have either created a new project with the same name or saved your project elsewhere...
Thanks
You know that very may have been what happened. At the point that this happened I was no discouraged, frustated and beating my head against the wall that I was not aware if I messed up or not. But, without being able to function in my normal mode I had to assume it was Innoscript. I am certain glad that it was not Innoscript.
So, now I am back in control, running the Innoscript on my two projects so I can have both XP and Vista versions. If you have the time and your are interested in seeing one of my programs made with VB6 and compiled with InnoScript and InnoSetup please take a peek at http://www.wise-old-man.com/analyzeyourretirement.com/index.html (http://www.wise-old-man.com/analyzeyourretirement.com/index.html). I have a domain name expressly for the program but it has not resolved yet.
Again, thank you for your patience and your program. It has been well worth the price.