PDA

View Full Version : SetupBuilder 2017 Version 10 Build 5708 Maintenance Release Available



NewsArchive
11-24-2017, 02:34 AM
All,

Happy Thanksgiving! There is a lot we are thankful for this year at
Lindersoft.

The SetupBuilder team would like to thank you for your continued support and
we hope that each and every one of you have a wonderful Thanksgiving. Please
be safe and enjoy your friends and family.

We just released version 10 build 5708 which is a free upgrade for all
SetupBuilder customers with an active Maintenance and Support Plan. The
update contains new features, enhancements, important bug fixes and
stability improvements. The easiest way to obtain this version is to click
'Help' > 'Check for Updates' in the SetupBuilder 10 IDE.

We strongly recommend that all customers upgrade to the new build of
SetupBuilder 10 as soon as possible to maintain the highest level of
support, performance and reliability. This new release introduces support
for Windows 10 Fall Creators Update.

NOTE: This build 5708 includes tons of internal compiler and linker
modifications to support SSL in the soon coming SetupBuilder 2018 release!

Thanks to everyone who contributed to build 5708!


SetupBuilder 2017 Version 10 Build 5708 (November 24, 2017)
----------------------------------------------------------------------------

NEW : IDE: This build includes tons of internal compiler and linker
modifications to support SSL in the soon coming SetupBuilder
2018 release.

NEW : Add Core PreRequisites built-in support for "Microsoft .NET
Framework 4.7.1" (x86, x64).

NEW : The "System Software Requirements" option supports .NET
Framework 4.7 and 4.7X detection.

NEW : Add Core PreRequisites built-in support for "Microsoft Visual
C++ 2013 build 12.0.40660 (Update 5) Redistributable Package
(x86).

NEW : Add Core PreRequisites built-in support for "Microsoft Visual
C++ 2013 build 12.0.40660 (Update 5) Redistributable Package
(x64).

NEW : Add built-in support for .NET Framework 4.7 and 4.7X detection.

NEW : Installer: Add support for hyperlinks in RTF controls (Readme
and License Agreement dialogs).

NEW : IDE: Add a new "Compiler Report" feature.

NEW : IDE: Add a "Enable Compiler Output generation" option to
'Tools' > 'Options' > 'Compiler'.

NEW : IDE: Add "Save and Close" button to the toolbar.

NEW : IDE: Add "Save and Close" menu item.

NEW : Add "Use 64-bit hive" option to the "Get Registry Key Value..."
script function.

NEW : Add "Do not expand environment strings if the value is of
type REG_EXPAND_SZ" option to the "Get Registry Key Value..."
script function.

NEW : IDE: The Compiler window supports the CTRL+C shortcut key
combination to copy the highlighted line into the clipboard.

NEW : IDE: Add WILDCARDHIDDENFILES #pragma to process hidden and
system files when using wildcards in the "Install File(s)..."
script function.

NEW : Add experimental enhancements to the "Features" system. Please
note that this is still work in progress. We have enabled
support for the enhancements because some developers need the
new functionality in their projects. The changes are not
documented yet.

NEW : IDE: Add "Import..." and "Export..." capability to the "SKU
Management Wizard".

FIX : Installer: The "Exit Installation..." script function with
"Cancel Wizard" option enabled did not work as expected.

FIX : Installer: Work around a possible LFN buffer overrun issue when
installing files where the file/folder name is > 256 bytes.

FIX : IDE: Missing SHA-1 timestamp server issue (if not defined in
the global code-sign properties).

FIX : IDE: The "Microsoft Visual C++ 2017 Redistributable Packages
did not provide "Custom Information" details ("Details" button
in the Core PreRequisites Visualizer).

CHANGE : The "Exit Installation..." script function with "Cancel Wizard"
option enabled terminates the application if used outside of
a "Wizard Loop" statement.

CHANGE : Installer: [SB#7-03311] ES_WANTRETURN style added to multiline
dialogs (Line1\nLine2\nLine3). Please note that this will cause
a runtime crash in all previous SB versions!

CHANGE : Installer: Variable value size increased from 260 to 1024 bytes
in a multiline dialog.

CHANGE : IDE: The 'File Properties -> Browse for Variable' function is
non-case sensitive now.

CHANGE : Installer: The stub loader does not display any fatal error
message box when the command line switch /S set the application
to silent mode processing.

CHANGE : IDE: Cosmetic IDE modifications (including the switch to new
flat icons).

CHANGE : IDE: Removed the outdated [SB5_*] system compiler variables (a
leftover from SetupBuilder 5).

CHANGE : License agreement text file size increased from 100KB to 200KB.

CHANGE : IDE: The #pragma VERSIONINFO_LANGID is backward compatible to
Windows 95 and Windows 98 now.

CHANGE : IDE: If the "Convert to lowercase" option is enabled in the FTP
"Release Distribution" for Web Update projects then the
compiler writes a lowercase installer file name to the Server
Manifest File.

----------------------------------------------------------------------------
----------------------------------------------------------------------------

The full history list can be obtained through the following link:
www.lindersoft.com/HISTORYSB10.TXT


Best regards,

--
Friedrich Linder
Lindersoft | SetupBuilder | www.lindersoft.com
954.252.3910 (within US) | +1.954.252.3910 (outside US)

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

NewsArchive
11-24-2017, 06:21 AM
There is a problem with the SKU Management Wizard (caused by a last minute
compiler change).

I'll make a patch available for those of you who make use of the SDK Wizard.

Friedrich

NewsArchive
11-27-2017, 08:44 AM
I tried to update from the program, and after that I downloaeed the
installer.
For first time ever, the upgrade/install did not work, and I am at the
time beeing without Setupbuilder.

Best regards

Edvard Korsbæk

NewsArchive
11-27-2017, 10:36 AM
Edvard,

> I tried to update from the program, and after that I downloaeed the
> installer.
> For first time ever, the upgrade/install did not work, and I am at the
> time beeing without Setupbuilder.

What does not work? Nothing changed in the update procedure for 10+ years.
Perhaps your protection software blocks it?

Any error message?

Friedrich

NewsArchive
11-27-2017, 10:37 AM
Edvard,

You said in the support request: "When i tried for the 6’th time, it
completed, and is running right now". You always got "Decompression error
[#-200000005]".

I am sorry to say that this has nothing to do with SetupBuilder and we can't
do anything to "fix" it. It's a typical false-positive issue. Your
protection software has a bug and blocks the write action (real-time
monitoring).

"Decompression error [#-200000005] means: "The decompression engine was
unable to create the file in the specified folder. The Windows GetLastError
function returns ERROR_ACCESS_DENIED(0x05) = Access is denied."

So your only hope is that your protection vendor fixes the bug or can
try to add the installer to your exclusion list. But it might happen again
in the future!

Friedrich

NewsArchive
11-27-2017, 03:44 PM
Dear Friedrich!

You are absolutely not sorry...

ESET/Malwarebytes is my protection vendor.

A more descriptive error message would be helpfull, to a very, very
good programme.

Edvard

NewsArchive
11-27-2017, 03:45 PM
Edvard,

the main problem is that it is not easy to find out what causes this.

Yes, it's a decompression error (because it's reported from the LSPack
decompression library) but it's not really a decompression thing. I know
it's a bit confusing in this case...

The problem here in this very specific case is that the installer runtime
checked for write access and the check did *NOT* detect a locked file
scenario. Why? Because it was not locked when the installer checked for
write access. So "replace on reboot" did not kick in, the installer
continued and called the unpack procedure to replace the existing file.
Okay, but suddenly, the CreateFile Windows API in the unpack library failed
with ERROR_ACCESS_DENIED (that is the "5" in the "-200000005" error code.
At this point, it was too late to offer a "Retry" because it's a fatal
decompression error. It's also possible that this happens for new installs
(no replace scenario). The installer creates the file, this succeeded, but
one millisecond after this the protection software locks the newly created
file... All these bugs in the protection software systems are a nightmare!

In short, the installer checked for write access, write access was possible
but directly after the check your protection software (real-time monitoring)
locked the file and BANG......

A typical false-positive bug :-( Users should never see "-200000005".

Friedrich

NewsArchive
11-27-2017, 03:47 PM
Hi Friedrich,

> completed, and is running right now". You always got "Decompression error
> [#-200000005]".
>
....
> "Decompression error [#-200000005] means: "The decompression engine was
> unable to create the file in the specified folder. The Windows GetLastError
> function returns ERROR_ACCESS_DENIED(0x05) = Access is denied."
Would it be possible to include that verbiage with/in the "decompression
error" to make it easier to see what the problem is (and less support
for you :)

Best regards,


--
Arnor Baldvinsson
Icetips Alta LLC

NewsArchive
11-27-2017, 03:47 PM
Arnor,

>> "Decompression error [#-200000005] means: "The decompression engine was
>> unable to create the file in the specified folder. The Windows
>> GetLastError
>> function returns ERROR_ACCESS_DENIED(0x05) = Access is denied."
> Would it be possible to include that verbiage with/in the "decompression
> error" to make it easier to see what the problem is (and less support for
> you :)

Unfortunately, it's not easy to do. The error code might change. It's not
always the "5" (access is denied) in [#-200000005]. I need some more
information to tell what is going wrong. In this case (based on the
additional information Edvard provided) it was clear to me that it was
caused by a false-positive bug. And as I understand it, both the web update
and full install image failed. So this is a new dimension in the whole
false-positive saga <g>. They do not have their protection systems under
control anymore. That's for sure.

Friedrich

NewsArchive
11-27-2017, 03:48 PM
> I am sorry to say that this has nothing to do with SetupBuilder and we can't
> do anything to "fix" it. It's a typical false-positive issue. Your
> protection software has a bug and blocks the write action (real-time
> monitoring).

I have seen this before and the problem that it is intermittent. It is
virtually impossible to point what is causing it. I have concluded that
it is definitely a bug in AV software.

Andre Labuschagne

NewsArchive
11-27-2017, 03:50 PM
Hi Friedrich,

> Unfortunately, it's not easy to do. The error code might change. It's not
> always the "5" (access is denied) in [#-200000005]. I need some more
> information to tell what is going wrong. In this case (based on the

Yeah, figured!

Best regards,


--
Arnor Baldvinsson
Icetips Alta LLC

NewsArchive
11-28-2017, 05:50 AM
Hi Edvard,

> ESET/Malwarebytes is my protection vendor.

BTW, we are also using ESET NOD32 Antivirus on all machines. IMO, this
vendor delivers the strongest protection with the fewest false positives. At
the moment <g>.

Friedrich

NewsArchive
11-29-2017, 03:45 AM
Hi Friedrich,

I just installed the update Build 5710.
There are no documentation updates when I check for it. Is that right?

Best regards,
Jeffrey

NewsArchive
11-30-2017, 03:03 AM
Jeffrey

> I just installed the update Build 5710.
> There are no documentation updates when I check for it. Is that right?

Unfortunately, yes :-( Still working on the updated documentation with new
screenshots (the IDE style changed).

The updated documentation will be released when the new SSL support is
available.

Friedrich