No. It looked like it was working before I moved J. But addons were in the "Program Files" path and I edited one of the test scripts, using J not as administrator, at which time the file proceeded to disappear into never-never land. So, this was the last time to fight this problem, making sure J was running as administrator when I tried to update something that was in "Program Files". In case you haven't had the glorious opportunity to update a file in "Program Files" with Vista, if a program not running as administrator attempts to modify a file in "Program Files" it saves it in a private directory under your userid. So it appears to be in "Program Files" to you (most of the time), but not always. Other users don't see the changes. I don't know if the extra warning running JayScript came about because the files were no longer in "Program Files" or some other sacred Windows library or not. It's just a pain to get the warning every time JayScript is entered.
On Mon, Oct 13, 2008 at 1:10 PM, Björn Helgason <[EMAIL PROTECTED]> wrote: > Is it really neccessary to move all of J in order to get this to work? > Is it not enough to move just a few files such as some dll and possibly > give > it an attribute to be run as an admin? > > I have not had opportunity to spend time on this more than very short > glance. > > And yes I am using Vista Home for this exercise > ...
---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
