SetupBuilder 5.6 build 1635 Release Candidate
All,
Data Execution Prevention (DEP) in Windows XP SP2, Windows x64, and Windows
2003 stopped SetupBuilder executables.
DEP problems caused "To help protect your computer, Windows has closed this
program." Windows messages. On top of that, installation executables
compiled with SetupBuilder 5.6 build 1627 resulted in an installer Error#
0002:000998 followed by an installer Error# 0002:0004202513.
We have uploaded a small (570 KB) SetupBuilder 5.6 build 1635 Release
Candidate patch. Please let us know if this fixes the DEP problems for you.
http://www.lindersoft.com/sb50/SB56_1635rc_Dev.exe
Note: The patch requires an exactly matched previous version of SetupBuilder
5.6 Developer Edition which is build 1627.
We have updated all SetupBuilder DLLs and LIBs. Build 1635 includes a
recompiled wupdate.exe Web Update client.
To uninstall SetupBuilder 5.6 build 1635 Release Candidate patch, run the
"Uninst_SetupBuilder 5.6 Dev 1635 RC.exe" uninstall application.
--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
+1.954.252.3910
"point. click. ship" - that's SetupBuilder 5.6
Re: SetupBuilder 5.6 build 1635 Release Candidate
Hello,
Ok - Great.
So the two issues ARE related and do not have to do with Admin or Temp
Folder? I will create a build this morning and have them try again ...
they are 4 hours behind us in SLC.
-Robert
Re: SetupBuilder 5.6 build 1635 Release Candidate
Hello Robert,
Yes, SetupBuilder 5.6 build 1627 installer error# 0002:000998 followed by
Error# 0002:0004202513 and the "To help protect your computer, Windows has
closed this program." DEP message do not have to do with Admin or Temp.
All previous SB5 versions (5.0 - 5.5) displayed the "To help protect your
computer, Windows has closed this program." Windows message only.
BTW, even the SetupBuilder 5.6 IDE caused the DEP failure. Fixed now.
Friedrich
Re: SetupBuilder 5.6 build 1635 Release Candidate
Dang
That link asks for a User ID and Pasword to download the candidate patch.
I have one somewhere from way baclk with SB5 betas, I will try that...
Otherwise, how do we get this patch?
John Griffiths
Re: SetupBuilder 5.6 build 1635 Release Candidate
Hi John,
The release candidate is for Developer Edition only (to test if the DEP
issue is fixed).
Are you on Pro 5.6 build 1627? If this is the case, I'll send you a patch
for Pro via email.
Friedrich
--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
+1.954.252.3910
"point. click. ship" - that's SetupBuilder 5
Re: SetupBuilder 5.6 build 1635 Release Candidate
Dang again...
I managed to use my old SB 5 beta user name and password to login and download the
candidate patch.
But when I run it, it says if fails to find SB5 Developer version, and I have
Professional Version.
Any way I can get a patch to fix this damn DEP problem with SB5.6.1627 Professional.
I am trying to send another program update in the next 2 hours. The one I sent last
night failed again.
John Griffiths
Re: SetupBuilder 5.6 build 1635 Release Candidate
Hi John,
I'll develop a Pro patch for build 1627 and send it via email.
Friedrich
Re: SetupBuilder 5.6 build 1635 Release Candidate
Hi Friedrich
Thanks. Looks like it is time I upgraded to Developer version. This is planned for
when my present license is up for renewal in a few weeks :-)
The best email to get me is either the gmail one you see here, or
oztime AT tpg.com.au
Regards
John Griffiths
Re: SetupBuilder 5.6 build 1635 Release Candidate
Friedrich,
I just downloaded the patch and rebuilt my install using it. It ran fine on
a Windows 2003 R2 64 bit server. I will now upload and try on my customer's
server.
Best Regards,
Mike Gould
Re: SetupBuilder 5.6 build 1635 Release Candidate
Hi Michael,
Great, thank you!!
We have tested this in-house on the latest Windows XP SP2, Windows x64, and
Windows 2003 R2 builds and it worked fine. So I think (I hope) it's fixed
now.
BTW, we noticed that after bringing Windows to the latest build, this DEP
error popped up on most machines (Intel and AMD). And it happens with all
previous SB5 (5.0 Gold - 5.5) builds. So I think Microsoft changed
something in one of the new patch updates.
Friedrich