Decompression Error

[NewsArchive]

I have a customer who has tried our webupdate and seems to have a
decompression error come up. To provide a solution I uploaded a complete
SETUP of our application which they downloaded, but when ran it too comes up with a decompression error, and the same file, TPSFIX.EXE. Trouble is these installs work fine in our office and fine with other customers, just seems to be this one site. They are running it on a DELL laptop if that makes any difference. Any ideas anyone???

Colin Wynn

[NewsArchive]

Colin,

Got a URL? I can test the install on my laptop. Compaq Presario 3000, XP
Home.

--
Russ Eggen
www.radfusion.com

[NewsArchive]

The thing is Russ you'll need a serial number to install and get to that
point. As I said, it works here on 2 PC's, and has worked several times in
the past week at various clients, so I'm not convinced its Setup Builder,
but was just looking for any pointers. But thanks for the offer anyway :)

[NewsArchive]

Colin,

I got a decompression error when installing an product update (made with
SetupBuilder) yesterday.

Problem was I had the file open. Other things may cause this, eg file has
read-only atrribute.

JAT.

--
Regards,

David Groves
Alchemy Technology

[NewsArchive]

Thanks David, trouble is TPSFix is a new file being installed, so it didn't
already exist. I've spoken with our technician that dealt with this and he's
said that once they moved the downloaded SETUP.EXE from the desktop to the
application's installation folder it ran fine, so maybe it's a
security/administration setting on the client's notebook???

[NewsArchive]

Hi Colin,

I don't know what could be causing the problem but my understanding is
that the error would more likely occur when there is an existing file
that it can't seem to over-write. Ask your client to delete any
existence of TpsFix.exe and then try the re-installation.

Best Regards,
Geoff Spillane
Data Down Under

[NewsArchive]

Thanks Geoff, trouble is TPSFix is a new file being installed, so it didn't
already exist. I've spoken with our technician that dealt with this and he's
said that once they moved the downloaded SETUP.EXE from the desktop to the
application's installation folder it ran fine, so maybe it's a
security/administration setting on the client's notebook???

[NewsArchive]

Colin,

Perhaps a virus scanner (auto-protect) or anti-spyware tool put a "lock"
onto the file so the installer cannot write to it (any longer).

By default, the installer checks if the file can be written. If there
is a read-only attribute on an existing file, the installer removes it.

Friedrich

[NewsArchive]

Well I dont for one minute think its SetupBuilder, as I said once the file
was moved from the desktop (which I'm told took some doing) it worked! So,
if it was a read-only issue it wouldn't have worked at all on that notebook.
All very confusing.

[NewsArchive]

Very strange... I hate computers <g>

Thanks,
Friedrich

[NewsArchive]

Me too, I've been threatening to become a bin man for many years now! lol

[NewsArchive]

The cans are usually full at the off license <bg>.

--
Russ Eggen
www.radfusion.com

[NewsArchive]

lol :) HIC ;)

[NewsArchive]

> Very strange... I hate computers <g>

You should put a COFFEE alert on that statement Friedrich.

I've seen it from you before <vbg>

;-)

Charles


--
-------------------------------------------------------------------------------------------------------
Charles Edmonds

www.ezround.com - "So that's how they make those round corner HTML tables!"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
-------------------------------------------------------------------------------------------------------

[NewsArchive]

Colin,

I have a client that is getting this error as well and your last statement
has me puzzled. During the update you dictate where the files are installed
and you said the tpsfix.exe is being installed for the first time.

What was on the desktop that got moved that allowed the success of
the update?

Thanks.

Lee

[NewsArchive]

Colin

One possibility if its an XP machine the user may not have the correct
access rights so cant make changes to ini files in the winnt folder so
programs that require the ability to write ini files can fall over here.

JAT

Cheers

Richard

[NewsArchive]

Cheers dude, I think it's an access right issue, but it wasnt writing to an
ini file at that point, just uncompressing a file :(

[NewsArchive]

Hi Colin

I have one customer who has a decompression error every time they update.
Problem is they don't make a note of the file involved! Education is needed
here.

Cheers
Simon Burrows
Visit the new Data Ferret Website
http://www.dataferret.net

[NewsArchive]

Hmmmmm, glad I'm not alone on this then, but I still dont believe it's a
SetupBuilder problem.

[NewsArchive]

Colin,

The next SetupBuilder build will display an additional error code for
decompression errors to identify the cause of this. We can then find out if
the file was "locked", etc.

Friedrich

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

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

[NewsArchive]

Hi Colin

In my case it's the same user every time. Single user machine (i.e. no on
else running the app via a network or anything). No other Clarion apps
running (that I am aware of).

One thing that I did get the other day. I use Organise365 by Gary James
(very good little app) and I did an update the other day. It closed down
the running program correctly, but then I had a decompression error on one
of the Clarion runtime files (C60ASCX.dll if I remember rightly). Tried it
again and it still failed. I then shut down my Clarion IDE that was running
and it went through no problem. A clue?

Cheers
Simon Burrows
Visit the new Data Ferret Website
http://www.dataferret.net

[NewsArchive]

Well at first Lee they tried using the Web Update Client but this just
wouldn't pass the decompression error of TPSFIX, so we compiled up a full
SETUP.EXE which the customer downloaded from our website and saved to their
desktop. When this file was ran from the desktop it too had the same
decompression error. However, when the SETUP.EXE file was then copied into
our application's install folder it ran fine! Go figure... *confused*

[NewsArchive]

Fingers crossed Friedrich :)

[NewsArchive]

Well this is the first time this user has ran the web update client, altho
other users and ourselves (with Clarion IDE open and closed) have used it to
great success over the past week or two now.

But his security settings are a nightmare, he couldn't even change the date
and time the other day!!!

[NewsArchive]

A couple of thoughts...

If the file was literally 'moved' from the desktop to another folder, it
would retain its permissions.
If, OTOH, the file was copied, it would inherit the permissions of the
parent folder.
It might be interesting to check the permissions on his desktop items. An
EXE actually located on the desktop needs the "Read & Execute" permission to
run. A shortcut just needs "Read"

The other thing I've been burned with is path length. With one program I
didn't allow long enough strings, and someone actually installed my program
on his desktop. So the path was c:\documents and settings\his long user
name\Desktop\some other folder\my program stuff.

Jane

[NewsArchive]

Thanks Jane, your comments are appreciated and noted :) Now I'll tackle my
client in the week with the next update lol