On Nov 12, 2007, at 10:05 AM, Malcolm Greene wrote:

> I'm not a fan of making changes to the registry and you may find that
> many customer workstations are locked down where you can't make the  
> type
> of change you are considering.

        That's why this would be an option for the user.

> As an alternative: Why not have your setup program generate a *.BAT  
> (or
> *.CMD) file with the path to your app and store this BAT/CMD file in a
> writeable folder in the path. This will have the same effect as  
> altering
> the path. Note that I said writeable path. On locked down  
> workstations,
> not all folders will be updatable.

        Two issues: one, I don't know the location of the EXE ahead of time,  
since the user can put it anywhere when they run the installer, so  
the BAT file will have to be modified on the fly. Second, if they are  
"locked down" I want to allow them the option of skipping this entirely.

> Another idea: If you're committed to updating the path via its  
> registry
> setting, use Inno Setup to create your install and have your Inno  
> Setup
> script make the appropriate changes to the path. This will be  
> easier and
> may be more reliable than trying to make changes to your path in your
> code.

        I am using InnoSetup, but I can't find out how to change the path. I  
found this page: (http://www.codeproject.com/tools/SetEnv.asp) that  
starts off by stating: "I recently used the excellent Inno Setup  
utility to create some install scripts for my own applications. I  
discovered that there was no way to set a system-wide environment  
variable except by using an external application. SetEnv supports  
User and System environment variables."

        I don't want to include yet another program, so I was hoping to do  
this natively in either InnoSetup or by including a BAT file as you  
mentioned above.

-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com




_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to