On Windows 2000 Pro corrupted files while extracting to network drive

[NewsArchive]

Hi,

I have a very weird issue.

Using the latest SetupBuilder 6.5 Dev. 1953.
I have made a setup file.

On Windows 2000 Professional:
When my customer runs the setup and let the files install on a network path,
the extracted files get corrupted (smaller size) and when my customer runs
my program executable after the installation, he gets the error:
"X:\FOLDER\PROGRAM.EXE is not a valid Win32 application"
BUT when he runs the setup and let the files install on his LOCAL drive,
everything is installed correctly.
After that he copies the local files to the network path and then the files
have the correct filesize and my program exe is working well.

On a Windows XP machine (in the same network), my customer has no problems
at all, so extracting the files on a network or local drive is working
correctly on Windows XP.

2 Different customers with Windows 2000 Professional have already mentioned
this problem.

Has anybody a clue?

Best regards

Jeffrey

[NewsArchive]

Hi Jeffrey,

Because this is nit a SetupBuilder issue, I think it has something to do
with one of their Windows (security) settings.

BTW, if the installer did not report a file installation error during the
installation process, then this file corruption even happens *AFTER* the
installation!!!!

I remember a similar case some years ago where the Admin set some wired
security settings. Unfortunately, I cannot remember which setting this was.

Does this help?

Friedrich

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

"point. click. ship" - that's SetupBuilder 6.5
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

> Because this is nit a SetupBuilder issue, I think it has something
> to do

Should read "...is not a SetupBuilder issue..."

Friedrich

[NewsArchive]

Hi Friedrich,

Thanks.
I will check further.

Jeffrey

[NewsArchive]

Hi Jeffrey,

We have all support messages archived. I remember that specific case, but
don't know when it was. If you cannot find a solution, we can try to search
for it here in our backups. This may take a few days because we handle
15,000+ customer requests per year.

Friedrich

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

"point. click. ship" - that's SetupBuilder 6.5
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

If you can find the solution, I can wait a couple of days. No problem at
all.
Thanks for your offer!

Best regards

Jeffrey

[NewsArchive]

Hi Jeffrey,

> If you can find the solution, I can wait a couple of days. No problem at
> all. Thanks for your offer!

Already did a quick search and found the specific case. But I don't know
the solution because the customer figured it out himself.

BTW, you can check in your uninstall .log what SetupBuilder installed. You
can also see the file size of the installed file.

For example, the following uninstall .log entry:

|006|_0000_|C:\Program Files\Lindersoft\SetupBuilder 6
Developer\Lib\PKEY.EXE|101|2007/08/10|09:15:58|6.5.1845.0|58416|9C2FA0CA||0|

2007/08/10 is the original file date
09:15:58 is the original file time
6.5.1845.0 is the original file version
58416 is the FILE SIZE!!!!! <--------
9C2FA0CA is the CRC32 value

I am sure the FILE SIZE in your log is correct, right? If the original and
installed file CRC32 is different, the installer would abort the
installation (with an error message) immediately. If there was no error
message, the file installed successfully, but some kind of security software
(virus-scanner, etc.) or system protection truncated the file after the
installation!

Hope this helps.

Friedrich

[NewsArchive]

Hi Friedrich,

This helps!!
Thanks and best regards

Jeffrey

[NewsArchive]

You are very welcome, Jeffrey!

Friedrich

[NewsArchive]

Friedrich,
Just a thought after reading this thread. How about adding a SB
feature that could be used to verify each file at the end of the
install? Since you have the file size and CRC, simply go back through
each file that was written and recompute based on the file actually
written and compare to what it should be. You already provide a
mechanism for verifying the integrity of the installation program.
-- Thanks, Roger Due

[NewsArchive]

Roger,

Thank you for your suggestion. This can already be done. There is a
built-in function to compute the CRC of files.

But in this specific case, the problem is that "something" modifies the file
after the installation process. That means, SetupBuilder installs the file
and checks the CRC of the written and the original file. No problem is
detected. After that some kind of system protection/manipulation kicks in
and changes the binary contents of the (correctly) installed file.

Thanks,
Friedrich

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

"point. click. ship" - that's SetupBuilder 6.5
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner