Randem Systems Support Board

No way. You did something different when you generated the second script. There is no reason InnoScript would eliminate them.
 
Did you generate the second script from the PDW lst file. That would be a no-no... That function is only there for people who have created a working PDW script and want to port it to Inno Setup.

i have no idea.. even the 2nd script is generated via PDW and inno same result. dont know y it happened

Where did all the other dll's in the first script come from then?

i did not remove them
 
all i did was moved my whole project to a new folder.. and then it just took the above mentioned dll.. does not ask any other.. even in PDW just the above mentioned DLL are being asked

Why did you eliminate the dll's. It is installing successful on your computer because the other dll's already exist on it.
 
Your installation need the files you can't eliminate them from the installation.

OK.. Now I have a new problem..  
 
I made a NEW installer.. it made this script.. and hardly took any DLL..  
 
; InnoScript Version 6.0  Build 3  Trial
; Randem Systems, Inc.
; Copyright 2003-2007
; website:  https://randemsystems.com
; support:  https://randemsystems.support
 
; Date: March 02, 2007
 
;              VB Runtime Files Folder:   C:\Program Files\Randem Systems\InnoScript\InnoScript 6.0\VB 6 Redist Files\
;     Visual Basic Project File (.vbp):   C:\New Folder\eAIMS\eAIMS.vbp
; Inno Setup Script Output File (.iss):   C:\Package\Script.iss
 
; ------------------------
;        References
; ------------------------
 
; Visual Basic runtime objects and procedures - (MSVBVM60.DLL)
; OLE Automation - (STDOLE2.TLB)
; Microsoft DAO 3.51 Object Library - (dao350.dll)
; Crystal ActiveX Report Viewer Library 11.0 - (crviewer.dll)
; Crystal Reports ActiveX Designer Design and Runtime Library 11.0 - (craxddrt.dll)
; Microsoft Shell Controls And Automation - (SHELL32.dll)
; Microsoft Windows Installer Object Library - (msi.dll)
 
 
; --------------------------
;        Components
; --------------------------
 
;  Osen Kusnadi

If the dll's are system dll's then they should be deployed in the system folder (default). You should not place system dll's in another folder upon install for when you register them that is where the system will look for them. Bad idea!!!
 
Upon install if the user wants to change the installation path that is where it is done not in the script. You can change the default path in the script by changing the parameter
 
DefaultDirName={pf}eAIMS  
 
to
 
DefaultDirName=c:eAIMS

Ok i got the problem worked out..  
 
what i did was put all the 30 DLL in a new dir and gave that path..
 
Now I have a couple of more questions..  
 
1) When the Installer is making the setup.. should i tell all the DLL to go in 1 folder.. like app.path/dll so that i can keep a track and then it should delete all while uninstall.. How do i mention the directory to that??
 
2) Is that wise what i am trying to do? is it wise to move them from their default to the dll directory
 
3) Also how to change the default app directly to change from program files to something else like c:prog as default and c:progdll for all dll to  go there
 
will post more question if i can think of.. this SYSTEM ROCKS!!!  keep up the good work..
 
(Message edited by alpha2001 on March 01, 2007)

i did.. i confirmed the file is in C:WINDOWSsystem32 and the path exists.. still not able to find them... tje files do exist there
 
these are the paths there
 
C:WINDOWSsystem32;C:Program FilesCommon FilesMicrosoft SharedDAO;C:Program FilesCommon FilesBusiness Objects3.0bin;

Specify What???
 
If you mean the Search Path Area, it the area just above the script that contains all the paths... Just add the new path to the list.

wher do i specify that ??

As the message states... the files in RED are files that cannot be found in the current search paths. They are either in your systems folder or in a path you did not include for InnoScript to search.
 
You will have to add the CR folder where these files reside into the Search Path Area for them to be found.
 
The message tell you what to do with system files that are not found.

I am totally new to this.. I just loaded a VBP file and left all same.. then i clicked on Create Inno Script File.. it gave the following script..  
 
; InnoScript Version 6.0  Build 3  Trial
; Randem Systems, Inc.
; Copyright 2003-2007
; website:  https://randemsystems.com
; support:  https://randemsystems.support
 
; Date: March 01, 2007
 
;              VB Runtime Files Folder:   C:\Program Files\Randem Systems\InnoScript\InnoScript 6.0\VB 6 Redist Files\
;     Visual Basic Project File (.vbp):   C:\New Folder\eAIMS\eAIMS.vbp
; Inno Setup Script Output File (.iss):   C:\test\test.iss
 
; ------------------------
;        References
; ------------------------
 
; Visual Basic runtime objects and procedures - (MSVBVM60.DLL)
; OLE Automation - (STDOLE2.TLB)
; Microsoft DAO 3.51 Object Library - (DAO350.DLL)
; Crystal ActiveX Report Viewer Library 11.0 - (crviewer.dll)
; Crystal Reports ActiveX Designer Design and Runtime Library 11.0 - (craxddrt.dll)
; Crystal Reports ActiveX Designer Run Time Library 11.0 - (CRAXDRT.DLL)
; Microsoft Shell Controls And Automation - (SHELL32.dll)
; Microsoft Windows Installer Object Library - (msi.dll)
; Crystal Query Engine  - (CRQE.DLL)
; keycode 9.0 Type Library - (KEYCODE.DLL)
; Crystal Reports SAX Serialize Type Library 11.0 - (SAXSERIALIZE.DLL)
; Crystal Analysis XML Serialization Type Library 11.0 - (SAXMLSERIALIZE.DLL)
; Crystal Analysis Communication Layer Library 11.0 - (SACOMMLAYER.DLL)
; Crystal Reports Prompting 1.0 Type Library 11.0 - (PROMPT.DLL)
; Parameter Prompting Library 11.0 - (PARAMETERDESIGNER.DLL)
 
 
; --------------------------
;        Components
; --------------------------
 
;  Osen Kusnadi