Users cannot run install on W64bit system - sbimage0041.jpg (0/1)

[NewsArchive]

Friedrich.

I updated my SB Prof system to SB5.6.1627 and now my clients cannot run my installs.

They are suggesting that it is because they are running a Win 64 OS. They get messages
as per attached.

I have tested the install I built with no problems on a win 2K system.

Any clues?

Thanks
John Griffiths

[NewsArchive]

John,

I don't think it's related to x64. We are running the latest Windows x64 on
AMD64 machines here and all our test installers work fine without any
problem.

IMO, they have "locked" the Windows temp folder or something like that. The
error means that the installer is unable to link into the LSPack
decompression library.

Friedrich

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

"point. click. ship" - that's SetupBuilder 5.6

[NewsArchive]

Hi John,

Definitely a Windows temp folder problem (not a SB5 bug). I believe they
have "locked" the Windows temp folder or a protection system denies access
to that folder. This results in a 0002:000126 error, then followed by a
0002:0004202513 error.

Friedrich

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

"point. click. ship" - that's SetupBuilder 5

[NewsArchive]

Hi Friedrich

Thanks for the info. I had told the client that I thought it was related to something
they had changed, perhaps a different anti-virus system or other 3rd party add-on. But
they claimed nothing there had changed...

I shall pass on the heads-up on their windows Temp folder. I will be sending them
another update install later today. We shall see if that works. It is a simple updater
with perhaps one or two new DLLs. I ended up supplying them just one new dll today
when they could not run the update exe.

I shall post here as soon as I know how they go tonight. I am back in Australia now (
arrived back Saturday) for the southern summer. Gotta follow the sun!

John Griffiths

[NewsArchive]

Hi John,

Thank you.

BTW, it's nothing you did in your installation configuration. This error
simply means that the temporary Windows folder cannot be accessed. And I am
sure the first message they received was 0002:000126, then error
0002:0004202513.

You can simulate this by "locking" the temporary Windows folder.

Wow, following the sun is cool <g>

Friedrich

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

"point. click. ship" - that's SetupBuilder 5

[NewsArchive]

Hi John,

Data Execution Prevention (DEP) in Windows XP SP2, Windows x64, and Windows
2003 stopped SetupBuilder executables.

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

"point. click. ship" - that's SetupBuilder 5