InstallAware

HAHNmediaservice

What about this post? Do we get an answer on that issue?

HAHNmediaservice

What about this post? Do we get an answer on that issue?

HAHNmediaservice

What about this post? Do we get an answer on that issue?

HAHNmediaservice

What about this post? Do we get an answer on that issue?

HAHNmediaservice

What about this post? Do we get an answer on that issue?

HAHNmediaservice

Sorry, we're not allowed from the third party company.

HAHNmediaservice

When opening the MIS file created during the build process (single) we do not find our customized dialogs in there. Where to find them?

Furthermore we have the impression that changes made to the MSI file do not affect the "product". Could that be?

HAHNmediaservice

Tahnk you, it work's.

HAHNmediaservice

We are going to write an DLL-Library with functions we need during our setup. Is it possible to use those functions even if the DLL is not yet installed / the setup is not finished?

HAHNmediaservice

Yes, we have, in the foretime and once gain now: (1) We don't like to have a password on our setups. (2) It does not matter if you encrypt or not! We did the same procedure with encrypted setups (example IA Setup "InstallAware_9_With_Runtimes.exe") ... and all mentioned files are affected ...

HAHNmediaservice

We need help soon. How long will it take to fix it?

HAHNmediaservice

We need help soon. How long will it take to fix it?

BTW: Where we can find a list with bugs already reported?

HAHNmediaservice

What's about that bug report which is almost 1 year old? As we see the System->Temporary Directory is still missing ... we're now using:

Get Environment Variable %TEMP% into Variable TEMPDIR

HAHNmediaservice

When running an InstallAware created setup it’s packed component’s are always and unasked unpacked to %TEMP%. This is not the perfect's way because if there is not enough space it breaks down ... even if all program data would fit, BUT: It's amazing to us that everybody can see the dialog forms (*.d...

HAHNmediaservice

It's a warning and yes, only errors threaten logo certification, not warnings. But we want to get rid of the ICE60 warnings as well. We still think the InstallAware’s build process is inaccurate (it's a bug, isn't it?), so please help on that, but don’t advise changing the MSI file table manually ...