All,

If you have NOD32, please note that one of the latest NOD32 definition file
updates introduced problems.

If you are using the SetupBuilder "#pragma SETUPICON" compiler directive to
customize the actual installer icon (this will inject a new icon into your
setup.exe binary) and you see the following error, then you should report it
to ESET:

Fatal Compiler Error: GEN1094: Cannot inject stub loader entrypoint: Para1:
C:\SYS\APPS\install\cd\yada.exe Para2: 91648 Para3: 6664

It's also possible that some of your scripts give an "Cannot be saved [2].
The error code reported is: 5 -- Access Denied" error that it can not save
the changes and offers to try again.

If "excluding" the SB7 IDE does not help, completely disabling NOD32 will do
the trick. But of course, this is a suboptimal workaround <g>.

Unfortunately, there is absolutely nothing that we can do because it is not
caused by SetupBuilder at all. It's a NOD32 bug.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

--Helping You Build Better Installations
--SetupBuilder "point. click. ship"
--Create Windows 8 ready installations in minutes
--Official Comodo Code Signing and SSL Certificate Partner