Hi,

Yes, it is happening with .exe files as per the current stand point. I have tried .doc, .pdf, .zip and other files that have no issues.

I don't have a clue to find the difference. Visible difference is that they have different set of information in file properties.

My file download application is hosted on HPUX, so the file comes from file area to HPUX web server and then it is downloaded to local machine from HPUX box to local machine through browser.

The working client is a Windows utility, it downloads the file from file area to local machine and there is no OS difference as per my understanding.

Does the OS flavors difference harm the .exe file while transfer? Sorry, if I am too dumb with this question. In fact I am. This thing has started to prick a little more than anticipated.

I have attached a jpg that has the snapshots of both the property windows.

Thanks again for all the help.

Attached Images

untitled.JPG (76.2 KB, 2 views)

Screen shots don't help much to find out where the difference is coming from. Are, say, the first five bytes identical? What about the last five?

Hi Era,

No solution but I am happy that I could find the problem. The one file that I called faulty is correct but it has lost its feature of MSI (Microsoft soft self-extracting installable). I tried opening the file using WinRAR which is similar to Winzip. It gave me the unzipped contents and I found one exe within that which works like a charm. The difference to users now is that they see all the individual components instead of a self extracting single executable.

Any idea that makes it a MSI in HPUX environment will be great. Anyway, the users won't be unhappy with the current solution.

I got that idea when I used the file command to check the attributes - It was indicating ASCII cpio archive. Am I close to any solution here?

Special thanks to Era; you are wonderful.

Regards,