I think you've hit it on the head Mark. I was stupidly hard coding the target instead of using [installdir], although the end location was the same. Before I tried changing a file and moving it per Hilmar's suggestion, I realized that I probably didn't need to hard code, so I added [INSTALLDIR] and moved everything there, then deleted my hard coded tree. Then I moved the changed files into the appropriate spots in the new tree. The move happened so fast I didn't think anything had actually happened, and had to check the dates on the files to be sure.

I couldn't figure out why new files moved so fast while before, it took such a long time. Reading your message, I realized what had happened. I guess if you don't use predefined folders, it actually copies files into a tree you specify, but if you do, it just sets pointers.

Thanks everybody.

Alan

>>You're probably right about the compression. As far as Installshield's intelligence, what you say is true, but since I won't necessarily be doing a setup for the same project each time, it still means that each new project is going to cost a lot of time in the setup creation.
>>
>>I guess I'll have to look around for something better. I just hoped there was something about Installshield express that I was missing.
>>
>>Thanks
>>
>>Alan
>
>Something is wrong. No compression is done until you hit the build button. All you are doing is indicating which files should be included in the CAB files. When you are in the Files section of InstallShield, right-click on the Destination Computer icon. Click the Show Predefined Folder, then click [INSTALLDIR]. Then all you should have to do is drag from the top half down to the bottom half just like explorer. For me this transfer is near instantaneous. All this does is just create a pointer that tells IS where the file is and where it goes during User Installation. The file is not actually physically copied anywhere.