X16 Express freezes when defining files to include

[BruceEglington]

In have Installaware Express X16 and am encountering a problem when defining some files to include in the self extracting exe package. This only happens when I have a project with a lot of files in the folder contineing the single file I want to add to the package. In the case that I have trouble with, the source folder contains several thousand xml files occupying a few Gb of disk space. I do not want to include these files but their presnence in the source folder seems to be what cause the problem. Installaware just freezes when I navigate into the folder to be able to select the single file I want to package in a specific folder in my script. I have to use TaskManager to terminate Installaware once frozen

What is the maximum folder size that can be accessed, even if I don't want to include most of the files in the folder. It would also be useful to know what the maximum number of files (or total size of these) that is permitted in an Installaware project although the latter is not essential for my needs. All these xml data files can be provided outside of Installaware. It is the main software and the folder structure that needs to be provided to end users.

Thanks

Bruce

[JohnGaver]

There's no practical limit that we're aware of, since the controls use virtual views which are accelerated, and are capable of supporting hundreds of thousands of files.

Can you look at, for example, the system32 folder? Mine has 5k+ files, and there's no perceptible slowdown.

Since these are shell views, it could be that your third party shell extensions are slowing or destabilizing things a bit. Sadly, this is where Windows's extensibility works against it in terms of stability.

A great way to test this theory would be to install InstallAware Multi Platform, and see if the IDE slows down with that one as well. Again, I don't see any issues here with it either; but InstallAware Multi Platform's browser doesn't actually implement shell views - so if this one works very fast while yours doesn't; you can be sure it's third party shell extensions doing something funny.