Ssetup Builder Fails on Install

[NewsArchive]

Setup Builder 6.9.2309
This application has encountered a problem and has to close. Please contact
the vendor of the installation.

Error #: 0001-000-3

robert paresi

[NewsArchive]

> Setup Builder 6.9.2309
> This application has encountered a problem and has to close. Please
> contact the vendor of the installation.
>
> Error #: 0001-000-3

The installation loader was unable to unpack/initialize the required
decompression library. The LZCOPY Windows API failed.

Make sure that:

1. the temporary Windows folder is accessible.
2. the "protection" software on that machine does not lock files (in the
temporary folder).
3 it is not caused by a corrupt installation image.

HTH,

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

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hello,

This has been happening now on many machines - three at one site, and a
host of others.

It's only started happening when we added 11 fonts to the installation
builder.

If we remove the fonts, then it works without issue. The user is signed on
as Administrator.

-Robert

[NewsArchive]

Hello,

BTW ... I know it is not #3 because it works on 3 of the 6 machines at the
site...so we'll go with #1 and #2 for now. I'll have our installer check
those things out.

However .... this same executable always worked on all these machines for
years ... and I've never seen the issue with this same executable as
thousands and thousands of properties.

But, we've added the 11 fonts to the SB because of a new product release and
now we seem to be seeing it. So, I'm positive it has to do with adding
Windows Vista fonts (Segoe) to the SetupBuilder and installing them on WIN
XP and WIN2003 boxes for some reason.

-Robert

[NewsArchive]

It has definitely nothing to do with fonts, etc. The error is reported
before the installer is even executed.

The pre-loader decompresses a SetupBuilder service file (LSPack) and this
fails because a Windows API (LZCOPY) reports an error. At this point, the
installer, which includes the script engine, all the files (including fonts)
is not started. So there is another reason for this.

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

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Robert

> But, we've added the 11 fonts to the SB because of a new product release
> and now we seem to be seeing it. So, I'm positive it has to do with
> adding Windows Vista fonts (Segoe) to the SetupBuilder and installing them
> on WIN XP and WIN2003 boxes for some reason.

Unless your Users have Office 2007 on a 2003/xp box I'm pretty sure we are
not allowed to redistribute the fonts so wondering if theres some copy
protection or something in the font file to lock things?

b. Font Components. While the software is running, you may use its fonts to
display and print

content. You may only

· embed fonts in content as permitted by the embedding restrictions in the
fonts; and

· temporarily download them to a printer or other output device to print
content.



Cheers



Richard

[NewsArchive]

Hi,

Yes, I'm thinking that too .... :-)

We've developed a beautiful kiosk application and we chose these fonts ...
we might go and use another font that we actually have ownership rights on
for a development license.

-Robert