Oh, I just remembered--I had a similar problem with CMake, where for
everyone else the installer successfully modified PATH, but not on my
machine.
I use a lot of command line programs, all installed in different
directories, so my PATH was too long for the CMake installer to modify.
There was a C
On 9/14/12, Andrew Pennebaker wrote:
> I am using Windows 7 Professional x64. Which version are you using?
> My Windows account has full Administrative privileges. I'm curious if the
> installer neglects to explicitly request administrative privileges.
IIRC UAC asked me for the administrator pa
>
> Well, I just checked:
>
> http://svn.freepascal.org/cgi-bin/viewvc.cgi/trunk/install/fpc.ist?view=annotate&root=fpcbuild
> around line 253 and further.
>
> It matches my experience.
>
> Maybe you are using Windows ME or older windows versions.
I am using Windows 7 Professional x64. Which vers
2012/9/14 Andrew Pennebaker :
>> It did work perfectly on my Win7 laptop.
>> You might want to have"administrator privileges whilst installing
>> (IIRC modifying the global PATH variable requires administrator
>> privileges).
>
>
> I do have administrator privileges, and the installer could be buil
>
> It did work perfectly on my Win7 laptop.
> You might want to have"administrator privileges whilst installing
> (IIRC modifying the global PATH variable requires administrator
> privileges).
I do have administrator privileges, and the installer could be built to
modify the user's PATH variable
On 9/14/12, Andrew Pennebaker wrote:
> fpc.exe and related binaries are installed in C:\FPC\2.6.0\bin\i386-win32,
> but the installer does not add this directory to the PATH environment
> variable. Thus, opening a Command Prompt and typing "fpc" fails.
It did work perfectly on my Win7 laptop.
You
