Randem Systems Support Board

It is taking it from there because you did not change the template as suggested. If you use c:tmp then your source line in the template file should look like this:
 
Source: c:tmpCRXI_RDC_ReDistribution.MMMSICRXI_RDC_Redistribution.msi; DestDir: {tmp}; Flags: nocompression ignoreversion deleteafterinstall
 
If you did not edit the templates to reflect where the files are located on your system they cannot be found. The template is just an example that you need to modify to your computer's files locations.
 
It is a mistake to use the Add Folder selection to add files if you are using the template to add the same files.

Ok I have attached the debuglog,errorlog,ISS script...
 
But I am having some problems.. I have the CR MSI and the autosetup XP in a folder called c:\tmp ..  
 
So in script
 
1) [Files]
Source: ..\CR XI Merge Module Installation\out\CRXI_RDC_ReDistribution.MM\MSI\CRXI_RDC_Redistribution.msi; DestDir: {tmp}; Flags: nocompression ignoreversion deleteafterinstall
Why is it takeing like this ??
 
2) Source: e:\server data\randem\develop\vb 6 redist files\
 
Why is it taking this source?? does not exist at all..  
 
i have done uninstall and reinstall of innoscript.. still taking the same source..  
 
I have mentioned the c:\tmp in the sourcepath.. its taking the CR MSI easily from it
 

BTW: You can distingus=ish which files are for CR by looking at the Components and Reference section for entries such as this:
 
; Crystal Reports ActiveX Designer Run Time Library 11.0 - (CRAXDRT.DLL)
 
Then looking in the debug log for the dll mentioned CRAXDRT.DLL and finding the dependent files for it. If you exclude the repetitive VB and OS files you will have the CR files.

This line is unneeded if you use the template
 
Source: C:\CRXI_RDC_Redistribution\*.*; DestDir: (app)\CRXI_RDC_Redistribution; Flags: ignoreversion
 
You also need to either change the template to match where you have stored the msi file or place the msi file where the template expects it.
 
It looks like you pull all your CR files from e:\pack\support,  c:\program files\common files\business objects\3.0\bin\ and c:\program files\common files\business objects\3.0\crystalreportviewers11\activexcontrols\
 
I would place all those filenames in the unsafe file list so that you do not need to remove them on future runs.
 
You may also want to deploy the AutoOSUpdater for MDAC support. If you do you can remove the DAO350.dll from your script.
 
Post your debug and run scripts. I want to take a look at them.

Just for ur info
 
I was also testing compilation with Microsoft Visual Studio Installer 1.1
 
I added MSM files of CR11 in them and did some code changing in my Vb Prog
 
The error is gone and package is working 100%...
 
So awaiting your answer for the above question so that i can compile from ISS and test and tell u the result..  
 
BTW MVS Installer has made the package 100 MB with the MSM files  
 
I have added the CR redisturb file and OS updater in the ISS and i think this package will also goto 100 MB approx..

this is the script generated when i choose tempelate script
 
; InnoScript Version 6.0  Build 4
; Randem Systems, Inc.
; Copyright 2003-2007
; website:  https://randemsystems.com
; support:  https://randemsystems.support
 
; Date: March 10, 2007
 
;              VB Runtime Files Folder:   C:\Program Files\Randem Systems\InnoScript\InnoScript 6.0\VB 6 Redist Files\
;     Visual Basic Project File (.vbp):   D:\Project\eAIMS\eAIMS.vbp
; Inno Setup Script Output File (.iss):   C:\pack2\New2.iss
;         Script Template Files (.tpl):   C:\CRXI_RDC_Redistribution\CR XI RDC Redistribution.tpl
 
; ------------------------
;        References
; ------------------------
 
; Visual Basic runtime objects and procedures - (MSVBVM60.DLL)
; OLE Automation - (STDOLE2.TLB)
; Osen Kusnadi

To us it just put the template file in the template folder of InnoScript then change the source location in the template file to the location of where you stored the msi file.  
 
Select view->templates from the menu and select the template file. The msi file will be included in your script at next generation. All the CR files that are in your script now can be added to the UNSAFE file list so that they will be removed from the script at next generation. That should be it.
 
Yes, we took care of the error in the new version. Did you read the Version History from the support site?
 
For the other parameters it is better explained in the manual.

I have downloaded the zip CR file..
 
But how do i use it?? can u give step-to-step instruction.. new to it.. it has a MSI and a TPL file.. Please guide here how to add it in the script and remove CR DLL as u suggested in the previous post..  
 
Also i dont know what a template is and how to use it..
 
TOTAL N00B.. sorry  
 
Also What are these options and what do they do exactly in ur innoscript  
 
1) Auto OS updater
2) ISTool
3) Minimum Windows Ver
4) Minimum NT Version
5) NT Service pack..
 
WHat all do i need to choose??
 
the C   runtime Error is gone in the new version

OK, It's the msvcr80.dll file that is causing the error. Since the OS subsystem handles that error it does not return an error to InnoScript and InnoScript continues normally. There is no problem with the script it generates for that file cannot be registered.
 
We will see if we can eliminate the error, but all else is well.

You can eliminate all the CR files and include the merge modules from the site at https://randemsystems.com/innoscript// It's the way CR want's it deployed. It's a whopping 67mb.
 
There is a template file that you can just add to InnoScript and change the locations of the MSI file supplied.

CR 11 developer edition
 

Can you zip and send me msvcr80.dll

The msvcr80.dll has rpcrt4.dll associated with it. Are you using CR XI or CR X?

yes.. it continues..  
 
every time i run innoscript on my project.. error comes.. i click ok and it continues

rpcrt4.dll is an unsafe file that should be removed by InnoScript, so I don't think that is the case.
 
Can you duplicate the error? Since this error message is given by the OS InnoScript doesn't know about it. What happens when you get this error? DO you just press OK and InnoScript continues?