Randem Systems Support Board

That is incorrect. The file CRYSTL32.DEP does not show dependencies for CRPE32.dll. CRPE32.DLL is a dependency of CRYSTL32.OCX not the other way around. Here is the CRYSTL32.DEP file that shows the same. Look at the tree on the right side of InnoScript you can see what files are dependent on the others. I will take a look at your project.
 
; ------------------------------------------------------------------------------
; Dependency file for setup wizards.
 
 
[Version]
Version=8.0.0.4
 
 
; ------------------------------------------------------------------------------
; Dependencies for CRYSTL32.OCX
 
 
[CRYSTL32.OCX]
Dest=$(WinSysPath)
Register=$(DLLSelfRegister)
Version=8.0.0.4
Uses1=CRPE32.DLL
Uses2=COMCAT.DLL
Uses3=OLEPRO32.DLL
Uses4=
 
 
[COMCAT.DLL]
Dest=$(WinSysPathSysFile)
Register=$(DLLSelfRegister)
Uses1=
 
 
[OLEPRO32.DLL]
Dest=$(WinSysPath)
Uses1=

5.3.9 was faster after I excluded the entire Documents and Settings folder, so the Exclude feature is an improvement.  If I might make a suggestion, I have nearly 30GB of material on the hard disk of this system that I never want to search under any circumstances.  It would be nice if I could tell InnoScript about that once rather than for every project I might create.  Excluding at the project level is still desirable.
 
Two things are not being found at this point.  The first is the executable application, which I do not keep with the source code.  InnoScript searched exhaustively for the file and did not find it despite the fact that its location is described in the .VBP file as
 
      ExeName32=OMS.exe
      Path32=..\Bin
 
Where ..\Bin is relative to the location of the .VBP file.
 
The other thing that InnoScript is not picking up are the dependencies for CRYSTL32.OCX.  It does pick up CRPE32.DLL but does not pick up any of the dependencies for CRPE32.DLL, which are listed in CRYSTL32.DEP.
 
I've put together the package you requested.
 
Will

We found it was and environmental setting that was pointing to the Documents and Settings folder, so We have allowed you to select which folders that you do not want scanned. Be careful if you select a folder no sub folders under that will be searched either.
 
I have uploaded just the exe for InnoScript. Just replace your exe with this one. There is a button on the main screen that says Exclude. This is where you select the folders that you do not want InnoScript to search. Let me know how this works for you.
 
Mahalo and Thanks for your assistance. If you like we can run InnoScript thru your project to see what comes out of it. We could provide you with an FTP account on one of our servers for you to upload your project.
 

I will be happy to experiment with it but I can't get to it right away.
 
I ultimately built my script manually because I ran out of time - I had to deploy before I could figure out how I was mishandling InnoScript.  I did study the differences between what InnoScript decided was needed and what PDW said was needed; eventually I based my Inno Setup script on PDW and not InnoScript.  This is in sharp contrast to my previous InnoScript usage (v3), in which the InnoScripts were perfect.
 
I promised that I would post if I could not figure out what was going wrong.  I haven't reached that point yet because I haven't spent enough time to decide that I can't figure it out.  I will be spending more time because the next phase of development of the project involves adding numerous new components, so the script must evolve.  I'd love to get InnoScript getting it right automatically and saving me time.
 
Will

Will,
 
I have created a version that will allow you to eliminate folders that you do not want searched. If you would like to try it let me know.

OK. Look into the logs after each run. they have a lot of info in them and can help narrow things down.

I use My Documents for general document storage, including a lot of photos.  That's about 15 years work of archival stuff (yep, I need it).  Project work for clients is in other folders outside My Documents; I don't want you to think my code is in there.
 
I will look further to find out what InnoScript thinks is lurking in there.  I don't want to dump this off on you until I exhaust my own avenues, which is a better way for me to learn anyway.
 
Even though I just recently bought InnoScript, I have used it before (v3).  That earlier experience, which was completely problem free, is the reason I ponied up so quickly for the most current version.
 
Will

Aloha Will,
 
InnoScript does not default to the Document & Settings folder. There has to be something pointing it to that folder. Possible a registered file.
 
Another question, Why would your Documents and settings folder be that large anyway?
 
Zip up the files and I will take a look and give you the report.
 
BTW: Have you looked at the logs after your run. It will tell you a lot about where it is looking and for what.

I'm going to continue to tweak until I understand this better and if I can't work through it myself I'll zip up the files.
 
If InnoScript can not find the files using the information in the Search Path Area, does it automatically launch an exhaustive search for the files?
 
I still don't understand why it's searching in Documents and Settings, where there is nothing related to the project.  I looked at both the VBP file and Setup.LST from a run of PDW; neither contain any reference to D&S.  As I say, searching there burns a lot of time.
 
Thanks.
Will

Aloha Will,
 
The way the search path works is it will search the area that are listed there and also search the application folder. The resulting search path area you see after the run would be the folders where InnoScript actually found files. It will remove any path where no files were found to prevent unnessecary searches.
 
The resulting order of the search path area is just a top down listing of where InnoScript found files first. There is nothing to worry about the order.
 
Configured properly InnoScript will only take seconds to re-find your files after first finding them. I would need more information about your project. If you could zip and post the exe, vbp and pjt files I will take a look see.

I am confused about how InnoScript decides where to search and how to control that with the Search Path Area.
 
First, does InnoScript automatically scan the sub-folders of the folders that are listed in the Search Path Area?
 
Second, InnoScript insisted on searching c:\Program Files and c:\Documents and Settings\Will (my user area) even though neither were listed in the Search Path Area.  My user area is very large but contains absolutely nothing related to the VB project, so it is a huge waste of time. How do I stop that?
 
Third, when I realized that InnoScript was making an exhaustive search for certain files, I added folders to the beginning of the Search Path Area.  It worked; performance improved.  However, after the run the folders were both moved and modified.
 
I added the following two folders to the beginning of the Search Path Area:
 
C:\Development\Ruxton OMS\bin
C:\Development\Ruxton OMS\bin\reports
 
After the InnoScript run, this is what was in the Search Path Area:
 
C:\Development\Ruxton OMS\Source\;
C:\WINDOWS\system32\;
C:\Program Files\Common Files\Microsoft Shared\DAO\;
C:\Development\Ruxton OMS\Bin\;
C:\Program Files\Common Files\;
 
Why was bin moved from the front to the middle, why was source added, and what happened to the reports entry?
 
InnoScript takes much longer to run than PDW's Create Dependency File option even though the latter is effectively finding the same files.  It seems to me that I should be able to configure InnoScript so that the run time is faster.
 
Thanks.
Will