Installaware changes the file Attribute to read only

[aziaaddini]

Hi,
We are using a native engine, and using the install file to drop 2 files on the target machines. But then files are copied their attribute will be set to read only!!! Thats not the selected option seems installaware does that itself. The initial source files are not set to read only either.
What could cause this issue? Please advise. Thanks
**Its not actually the attribute on the file, it changes the permissions on the file. will make the permission for the users as Read and Execute only.** whereas it should have the write access as well.

[FrancescoT]

Dear Aziaaddini,

can you please post a very VERY minimal project that replicates the issue?

Last but not least, which IA version are you using?

Regards

[aziaaddini]

Thanks for the reply, I managed to fix it by using set Access Control after install file to give it read/write access to the Authenticated users, that seemed to fix the issue. But if you still think, that shouldnt happen, I can create a minimal project for you to see. This happens with any project we create. We are using Installaware X6 Build 0.13.2017. As I mentioned any file you drop on a local machine, will set the file permission to only read/Execute.

[FrancescoT]

Dear Aziaaddini,

because it should not happen, I would like to receive a VERY minimal project that replicates the issue.

Regards

[aziaaddini]

I Just tried the following: dropped a test.txt file to %temp% and I can see the issue. Please add that to a blank script and drop a text file. After the file dropped to %temp% please do a right click and check the properties/Security for users. it will only have Read and Read/Execute.

Set Variable FX to NONE
Set Variable NATIVE_ENGINE to TRUE
Get Environment Variable %temp% into Variable TEMPDIR
Set Variable MYAHLOGO to TRUE
Set Variable NATIVE_OVERWRITE to ALWAYS
Set Variable NATIVE_OVERWRITE_OLDER to TRUE
Get Common Folder Location System->System Directory into WINSYSDIR

Install Files .\data\test.txt to $TEMPDIR$

[FrancescoT]

Dear Aziaaddini,

I am not able to replicate any problem. I used a small project based on your instructions.
For what I see, the file Attribute doesn't switch to read only.

For your convenience, attached you find the project I used.

Hope this helps you.

Regards

[aziaaddini]

Hi
Its the file permission not attribute. it was my mistake. It changes the file Access Permission.

[FrancescoT]

I see what you mean.

I'll send a note to our dev team.

Regards and thanks for reporting this.

[aziaaddini]

Thank you, Can you please update this when this is fixed. Thank you

[FrancescoT]

Dear Aziaaddini,

please try with setting to FALSE the "NATIVE_HARDLINK" pre-defined variable at the very beginning of your script.

This should solve your issue. The copied files will inherit the security settings from the destination directory.

Hope this helps you.

Regards

[Werner]

1.
I had a similar problem that with native engine:
- creating a folder
- set read/write permissions for that folder
- installing files in various subdirs of that folder
did not result in those dirs/files having the same permissions as set for the empty folder.

Setting "NATIVE_HARDLINK"=FALSE solved that problem.

Is there a bug fix available for this problem, so that we don't need to set "NATIVE_HARDLINK"=FALSE ?


2. FYI : Different behaviour dependent on destination drive letter :

Using "set read/write permissions" in the script for setting write permissions was only necessary when installing into a folder on system drive C:
Then afterwards the installed files had only read permissions, which led to various problems.

When I changed the destination folder to a path on another drive (eg. E:) then the files automatically had read/write permission
and there was no need to use "set read/write permissions" to set write permissions.