DX10 fix fails to install

[SteveFx]

There seems to be an issue/bug with windows 7 where the read only flag gets set in directories where it should not. There was one other person previously who had the same issue out of 1400 downloads.

 

From what i have read on the subject the only real solution to this is to reinstall windows, as you will have other problems in the future outside of fsx.

 

It's difficult to know what I can do as this problem doesn't happen for most people with windows 7, my 3 pcs all are fine for instance.

 

At some point in the future I will try and find a way to do the install a different way, copy the file elsewhere and edit it and copy it back.

[SpiritFlyer]

I am afraid I have the same issue, I worked almost all night running the suggested remedy from Microsoft, but no joy:

 

1.

attrib -r +s drive:\C:\Users\TF1\AppData\Local\Microsoft\FSX\Shaders10\General\ General10.fx_0x0a400000000000b1_0x0f

2

attrib -r +s drive:\C:\Users\TF1\AppData\Local\Microsoft\FSX\Shaders10\General\ General10.fx_0x0a400000000002b1_0x0f

3

attrib -r +s drive:\C:\Users\TF1\AppData\Local\Microsoft\FSX\Shaders10\General\ General10.fx_0x0a400000000002b9_0x0f

4

attrib -r +s drive:\C:\Users\TF1\AppData\Local\Microsoft\FSX\Shaders10\General\ General10.fx_0x0a400000000005b9_0x0f

 

etc.

 

...all the way to number 82 (modified by hand) Didn't work, ran "Take Ownership" and numerous other methods, but nothing worked.

 

Discouraging...

[Jim Young]

Hi Stephen,

Just delete the Shaders10 folder. It will be rebuilt when you restart FSX. Make sure you are sharing FSX. Right click on the main FSX folder and select Share with... then Advanced Sharing. Make sure your FSX folder is being shared on your network. Include all sub-folders.

 

Best regards,

Jim

[SpiritFlyer]

Does not work Jim, under any conditions. No option but to do a reinstall if I want to use DX10.

[Jim Young]

I don't understand as the attribute turned off read only and turn on making the file a system file which I find very strange.  Do not understand why it is doing that.  Should be easy to reinstall. Did you try the procedure in Post #9 by PJ where you can download the modified HSLS Shader folder and replace it with the current folder? This folder has the installation complete so you don't have to run the Steve's DX10 Shader fix.  You'll still need to delete the Shaders10 folder before you go flying.

 

Best regards,

Jim

[SpiritFlyer]

Hi Jim,

 

See Steve's reply above:

 

http://forum.avsim.net/topic/387367-dx10-fix-fails-to-install/?p=2595829

 

Yes, everything tried as well as reading a truck load online. Here is one MS answer, among a few, that I tried that did not work: http://answers.microsoft.com/en-us/windows/forum/windows_7-files/cannot-change-read-only-file-attributes-using/b02b2254-cd4d-4e50-a68a-cae8c748d086

 

Oh well, I have not reinstalled in a long time, so first windows 7-64, then a new FSX and all the trimmings. Here we go,

 

and a 1, and a 2, and a 3....GO!

[Charles575943]

There is a simple solution to this problem of not being able to update the write protected file and is a know problem with your versions of Windows.

 

Create another directory with the same structure as the folder and files you are trying to modify. The directory should include a copy of your shader files and very importantly a copy of your fsx.exe executable, (the batch file will look for the fsx.exe executable).  Providing you have created an identical directory structue to your existing FSX installation, run your batch file and let it seek out the copy of your fsx.exe program and then allow it to modify the copies of your shader files. It may be better to create your copied files on another disk or partition. Simply back up your original shader files and and overwrite. There is an copyright issue here, that's why you have to do it this way.

 

Charles

[Charles575943]

Since re-installing Windows 7, I no longer have problems with overwriting or updating files. Somehow the permissions for files/folders are ending up in a muddle, it's extreme but a reformat solved the problem.

 

With regards to the tip above, you might want to rename your main FSX folder temporarily to force the batch file program that comes with the shader packages to look else where for your pseudo FSX folder that you have created. 

 

Charles