Path To Scripts Windows 7

Colorguy · Post by **Colorguy** » Fri May 20, 2011 10:23 pm

Since I don't have a computer running Windows 7 and probably won't get one for a while, I have a question. I have a big colletion of Actions which call Scripts on Windows systems using the following path: C:\Progam Files\Scripts00\NameOfScript.jsx

WIll all these paths need to be changed if using Windows 7, both 32 and 64 bit installations?

xbytor · Post by **xbytor** » Sat May 21, 2011 12:33 am

"C:\Program FIles" still exists, so you're OK provided you have appropriate permissions.

Colorguy · Post by **Colorguy** » Sat May 21, 2011 12:48 am

Thanks X. Let me ask this...I have an installer that places this folder of scripts on the end users system. Is that an issue or can the install path of C:\Program Files\Scripts00 remain the same as long as the user has admin status on their system?

xbytor · Post by **xbytor** » Sat May 21, 2011 2:12 am

Colorguy wrote:I have an installer that places this folder of scripts on the end users system. Is that an issue or can the install path of C:\Progam Files\Scripts00 remain the same as long as the user has admin status on their system?

The xtools installation script has this problem. To get around that, I have them do "Run as Administrator" on PS then run the installation script. Win7 is far more security conscious.

BTW, if you use Adobe Extension Manager to install scripts, you will have the same problem, which I consider a bad design feature. AEM should do permissions escalation request during the install of your extension instead of requiring a "Run as Administrator". The problem doesn't exist on OSX.

Colorguy · Post by **Colorguy** » Sat May 21, 2011 5:11 pm

Thanks again X for the advice. Very few problems exist on OSX, much unlike Win. I basically use Macs for everything and Win as needed. I think I'll have to buy a cheap new Winbox with 7 installed just for testing.

undavide · Post by **undavide** » Sat May 28, 2011 4:13 pm

Why wouldn't you use virtualization? Photoshop/Win7 runs fine on Parallels (MBP 17"), and for testing purposes it's enough - cheaper, possibly, and more practical for sure than a dedicated machine.
Just my point of view
Cheers

David

kpt · Post by **kpt** » Wed Jun 01, 2011 10:17 pm

Isn't there a difference between running PS as administrator and giving the user temporary admin privileges during the installation?

I have an installation script which places jsx-files in the user's "My documents" folder. If PS is run as admin, then the files are written to admin's "My documents".

xbytor · Post by **xbytor** » Wed Jun 01, 2011 11:39 pm

kpt wrote:Isn't there a difference between running PS as administrator and giving the user temporary admin privileges during the installation?

I have an installation script which places jsx-files in the user's "My documents" folder. If PS is run as admin, then the files are written to admin's "My documents".

Doing a "Run as Administrator" on a process adds you to "Administrators" group so you get can operate with that set of permissions, but it does not not change your user id to "Administrator" or whatever. Your home directory is still the same.

If you are using cygwin, open up one shell as Admin and another normally then run 'id'; You'll see Administrators added to the list of groups.
There's probably a similar way to see a difference with cmd.exe or powershell.

kpt · Post by **kpt** » Thu Jun 02, 2011 8:27 am

Really? If I run this script

Code: Select allvar f = new File(Folder.userData + "/test.txt");
alert(f.fsName);

I get a different result when I run PS as "run as admin".

xbytor · Post by **xbytor** » Fri Jun 03, 2011 2:18 am

I just checked this out and got the same path when "Run as Administrator" is used as when it isn't. Both pointed to my AppData/Roaming folder.
The only time Folder.userData should be different is if you login as a different user.