Dear Randem,
I have a very basic and fundemental problem using InnoScript. I think it must be a common problem to all new users to create VB software. I have spent four days without any clear information discovered. My key problem is how to let the VB system files valid for deployment, or I may simply skip them all ?
When I use Normal Script option, the VB files are refered under c:windowssystem directory in the output .iss file. When I run Inno Setup Compiler for the .iss scripts, I get error messages like:
Attempt to deploy DLL file from own Windows System directory
Then I made a change in order to get a better understanding. I used a tpl file and redirect all the same VB files to my own support directory. In this directory, the VB files have the same version as those in c:windowssystem. When I run the Setup Compiler, I then get different error messages like:
Parameter Flag cannot have the sharedfile flag on a file copied to the {tmp} directory, or when the deleteafterinstall flag is used
So it is impossible to get VB system files deployed in anyway. What should I do then? Actually the list of the VB files are herited from the VB Package and Deploy Wizard. I don't think I may skip them. I checked the DLL database of Microsoft, I don't see much instructive information.... I am toally in darkness! Please help !
Attached are the two script files: My problems are around the DLLs declaration. Please give a direction. Thank you.
best regards,
Y. Ren
=================
In the tpl file you will see the [File] like this:
[Files]
Source: C:_BIZbiz_pluspackagesupportmsvbvm60.dll; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: regserver restartreplace sharedfile
Source: C:_BIZbiz_pluspackagesupportoleaut32.dll; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: regserver restartreplace sharedfile
Source: C:_BIZbiz_pluspackagesupportolepro32.dll; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: regserver restartreplace sharedfile
Source: C:_BIZbiz_pluspackagesupportasycfilt.dll; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: sharedfile
Source: C:_BIZbiz_pluspackagesupportstdole2.tlb; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: uninsneveruninstall sharedfile regtypelib
Source: C:_BIZbiz_pluspackagesupportcomcat.dll; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: regserver restartreplace sharedfile
Source: c:programmerandem systemsinnoscriptvb_dcom_mdac_jet_autosetup.exe; DestDir: {tmp}; MinVersion: 4.0,4.0; Flags: sharedfile deleteafterinstall ignoreversion
Source: C:_BIZbiz_pluspackagesupportmci32.ocx; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: regserver restartreplace sharedfile
Source: C:_BIZbiz_pluspackagesupportmscomctl.ocx; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: regserver restartreplace sharedfile
Source: C:_BIZbiz_pluspackagesupportcomdlg32.ocx; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: regserver restartreplace sharedfile
Source: C:_BIZbiz_pluspackagesupportmsstdfmt.dll; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: regserver restartreplace sharedfile
Source: C:_BIZbiz_pluspackagesupportmsinet.ocx; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: regserver restartreplace sharedfile
Source: C:_BIZbiz_pluspackagesupportpicclp32.ocx; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: regserver restartreplace sharedfile
Source: C:_BIZbiz_pluspackagesupportrichtx32.ocx; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: regserver restartreplace sharedfile
Source: C:_BIZbiz_pluspackagesupportriched32.dll; DestDir: {sys}; MinVersion: 4.0,4.0; Flags: restartreplace sharedfile
Source: C:_BIZbiz_plusWisdomExplorerPlus.exe; DestDir: {app}; Flags: ignoreversion
...
Hi yan Ren,
I am not sure of what you are having problems with. The default installation of InnoScript has the VB runtime files installed in a folder which InnoScript already points to. When used with that setting all the VB Runtime files are deployed to the {sys} location. You should not placed may of the flags on a file deployed to the {tmp} folder. The only flag that I see is appropiately is deleteafterinstall.
What do you have in the folder drop down box for the VB Runtime files. You could also send me the InnoScript.ini file from the installation location of InnoScript so that I may take a look.
The VB runtime files have to be deployed for you package to operate on a system that does not have VB or an associated VB package already installed.
I do not see anything wrong with your script. When you compile what error are you getting on the VB Runtime files?
What version of Inno Setup are you using?
Hello,
It is greate you respond so quickly. You are offering greate help! Thank you a lot!
My problems are:
1. if I don't use tpl to overrule the path for the VB run time files (such as msvbvm60.dll ...), they are pointing to c:\windwos\system by default. Then I get a problem: when I run the Setup Compiler, I get error saying Attempt to deploy DLL file from own Windows System directory
2. So I overrule the path for the files. Then I got some other error messages: Parameter 'Flag' cannot have the 'sharedfile' flag on a file copied to the {tmp} directory, or when the 'deleteafterinstall' flag is used
- so I am really confused what to do! Should I remove the run time files, alter the path or do sth. else?
I checked the installation directory of InnoScript, VB6 run time files are not updated at all. I downloaded a copy of VBrun6SP6.zip from your site and ran it. Only the relevant files in my windows\system are updated. The directory in InnoScript remains untouched. In the output iss file, I don't see any directory pointing to this directory neither.
My OS is WINME 4.90.3000.
My InnoScript is 2.3.9.
My InnoCompiler is 4.2.7.
I think there are at least 3 problems:
1. InnoScript excludes the link to the VB run time local copy in its own installation directory. Instead it is pointing to Windows\system directory.
2. the directory for the local VB copy is never get updated. Instead the files in the system directory do.
3. Maybe the iss script does not get correct flag settings for these files.
About your questions:
In the run time drop-down box, there are in total two options
C:\Programme\Randem Systems\InnoScript\InnoScript 2.3\VB5 Runtime\
C:\Programme\Randem Systems\InnoScript\InnoScript 2.3\VB6 Runtime\
The ini file can be found below the end of this mail.
Please advice,
Thanks!
regards,
Yan
=========================
[InnoScript]
VB6Dir1=C:\Programme\Randem Systems\InnoScript\InnoScript 2.3\VB6 Runtime\
VB6Dir2=C:\Programme\Randem Systems\InnoScript\InnoScript 2.3\VB5 Runtime\
MinWinVersion=1
MinNTVersion=1
VBVersion=6
ProcessFile=1
TemplateFile=1
UseUNCPath=0
SafeMode=False
AutoOSUpdater=1
LastSaveDir=C:\PROGRAMME\RANDEM SYSTEMS\INNOSCRIPT\INNOSCRIPT 2.3
FormColor=12632064
RTFColor=12632256
SearchPath=C:\WINDOWS;C:\WINDOWS\COMMAND;
NTServicePack=
AppDir1=C:\_BIZ\biz_plus\WisdomExplorerPlus.exe
PDWFile1=C:\_BIZ\biz_plus\WE.VBP
InnoSetupFile1=C:\_BIZ\biz_plus\Package\plus.iss
InnoSetupFile2=C:\_BIZ\biz_plus\Package\plus3.iss
TemplateFile1=C:\_BIZ\biz_plus\Package\InnoScript.tpl
TemplateFile2=C:\Programme\Randem Systems\InnoScript\InnoScript 2.3\Template\InnoScript.tpl
AppDir2=C:\_BIZ\biz_plus\Package\Support\
PDWFile2=C:\_BIZ\biz_plus\Package\SETUP.LST
AppDir3=C:\_BIZ\biz_plus\WisdomExplorerPlus.exe
AppDir4=C:\_BIZ\biz_plus\WisdomExplorerPlus.exe
PDWFile3=C:\_BIZ\biz_plus\Package\Support\Setup.Lst
[Errors]
ErrorNo=0
[Screen]
Left=60
Top=345
Width=15420
Height=10275
WindowState=2
[BScreen]
Left=60
Top=60
Width=15480
Height=11220
WindowState=2
Hello,
May I ask the status of InnoSetup and InnoScript : how mature is it for serious use?
I am almost crashed by the problem of Inno Setup and InnoScript. I am expecting your feedback to my questions. Unfortunately I don't hear anything from you so far. I have to make decision to stay with Inno products or move to others.
To be honest, I like the product except the problems. It is straightforward and professional-looking.
I tried to install and run the product on a win 2K PC. I got another set of problems. The major problem is always with the path to the VB dll files. Inno does not allow me to have these files included in the setup.exe.
Please give an advice a.s.a.p. I really have to make switch if I have to because my clients are waiting for my products.
regards,
Yan
Yan,
Both products are mature and widely used. You seem to be confused on the usage. It is straight forward. The VB runtime files are allowed to be in the setup.exe. InnoScript is distributed with these files in it's setup and InnoScript is created with Inno Setup, so it does work.
Thousands use these products daily. If you use the default path for the VB runtime files for the default installation you will have no problems. I suggest you uninstall, re-download and re-install to get back to the defaults.