Read Only Destination Issue - SB5

[NewsArchive]

Hello,

I haven't seen this before, as I thought SetupBuilder 4 (5?) can handle
this.

If the file on the destination is "Read-Only", then SetupBuilder returns:

"A decompression error has been detected."

That's all ... it doesn't say "Read-Only File". But, more importantly ...
can it not just overwrite Read-Only files and put in the new attributes?
Or - at least say "Read-Only File!" ....

Anyway ... thoughts?

Thank you.

[NewsArchive]

Yes - I just ran the same installer using SetupBuilder 4 - and it
successfully installed and overwrote the Read-Only files.

However, SB5 complains. Is this a regression, or on purpose? I'd really
like to overwrite read-only files, as if the user set a read-only file, a
reinstall of the software should ignore this.

-Robert

[NewsArchive]

I tried doing "Set File Attributes" - but that does not work either because
if you leave everything unchecked, it doesn't UNCHECK the file attribute.
The setting/function is only used to SET THEM - not remove or change them.
:-(

-Robert

[NewsArchive]

Hi Robert,

I just tested one of my installers by changing an installed file to
"Read Only" then re-installing over the top and it replaced it no
problems (no error messages). Do you want to post your script?

Best Regards,
Geoff Spillane
Data Down Under

[NewsArchive]

Robert,

Just run a test here on our machines and it works fine. It replaced the
read-only file without any problem.

Would it be possible for you to send me a small test script and a zipped
read-only file?

Thanks,

Friedrich

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

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

[NewsArchive]

Hi,

I was installing from a Windows XP box onto a Windows 2000 SBS network drive
.... if that makes any difference.

\\isa\iqanywhere\ADOTemplate.asp

That was actually the destination file name.

When I run the exact same install using SB4, it just goes right along and
overwrites all the files.

So, what I did was I have 50 files in that directory. All read-only, and it
stopped on the first one (see above). So, what I did was I changed just
that one file to not read-only, and re-ran SB5. This time, it worked fine
on the first file, and then stopped on the second file with the same error.
So, I'm sure it has to do with the attribute.

I am signed on as an Administrator and full authority to the box.

-Robert

[NewsArchive]

Robert,

I tested this here on our network and it works fine. I have two read-only
files on the server. The destination path is:

\\AMD64WIN64\DriveC\Development\RobertP

It replaced both files without any problem :-(

Friedrich

[NewsArchive]

I sent you zip file.

Let me know if you need anything ... same thing seems to not work on C drive
either.

-Robert

[NewsArchive]

See private email. I have tested this on Windows 98, Windows NT4, Windows
Me, Windows 2000 Professional, Windows Server 2003 Data Center, Windows XP
(32-bit), Windows XP (64-bit), and Windows Vista (beta) without any "luck".

So I need your help <g>.

Friedrich

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

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

[NewsArchive]

I think I found your problem ... I just emailed you.

"Backup Replace Files" not being checked does not replace read-only files.

-Robert

[NewsArchive]

Thank you for your help. I can reproduce this now. Item in review.

Friedrich

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

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

[NewsArchive]

I think it's fixed now, thank you!

Friedrich

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

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

[NewsArchive]

I knew you'd fix it. <g>

When will it be ready is the next question? ;-)

-Robert

[NewsArchive]

See recent post <g>

--
Russ Eggen
www.radfusion.com

[NewsArchive]

I'm way ahead of ya! :-)

It's already tested and the fix works great.

-Robert