No Administrator rights error...

[ajrock2000]

When I use the installer for version 1.0, I keep getting the no write access to the windows directory error no matter what I do.

I am logged into windows as an administrator...Is there anyway around this error?

[cweiske]

[ajrock2000]

I am on Windows XP, and after installation, there is no "pearsys.ini" in the windows directory. Should there be one?

[cweiske]

[ajrock2000]

Yeah, I can. What should I put in it?

[Doug G]

I'm sorry to bring an old thread back to life

I am trying to install Gnope "side-by-side" with my existing php5.0/Zend Studio/IIS/isapi installation that's been working fine for some time. I installed php-gtk2 to a non-standard directory I picked \utl\programs\php-gtk2\ during the installation.

First try, got a bunch of can't find dll errors. Looked around here, found a post that said to move the existing php.ini out of the windows folder, which I did, and came up to this administrator rights error. I removed c:\php from the PATH, reran the installer, same error.

I had an existing pearsys.ini file in the existing c:\php directory, and the gnope installer wrote into that file! The path to pear in my new, nonstandard directory was inserted, even though I still got the admin rights error.

I created a blank pearsys.ini in c:\windows, the installer completed fine, and the windows pearsys.ini is still empty. I'm going to see if I can put the path back and the previous windows php.ini back and see what works now.

I'm hoping to be able to make this configuration work, I'll post more if I discover more.

[cweiske]

I never had another php installation with Gnope, but here is what I learned until now:
- You will get an Administrator rights message when you have another PEAR installation somewhere on the hard disk.
- There are two things the PEAR installation is seen from the installer:
* The pearsys.ini in the Windows directory. It contains paths to your current pear installation, and that irritates the installer.
* The environment variable PEAR_PHP_BIN (or so) that points to a specific php executable.
- Both the settings are not overwritten when installing Gnope, meaning that Gnope installs its own PEAR in its own directory, but when you execute the php delivered with Gnope or even just type "pear" in the command line, the other PEAR installation will be used.

By removing the environment variable and the pearsys.ini from the windows directory, and *then* installing gnope, everything (for gnope) works fine. I just don't know what happens to your previous pear installation. The other php will probably use the Gnope pear installation.

When I found out how to make a pear installation without putting a file into the windows dir, Gnope 1.1 will not make that problems.

[Doug G]

Actually, my pearsys.ini file was in c:\php not windows, there was no pearsys.ini in my windows folder, and still the Gnope installer wrote into that file somehow.

I got thing more-or-less working by creating an empty pearsys.ini file in windows (leaving the existing one alone) and running the installer. I left the original php.ini in \windows, and I found I could add a -c <myspecialdirectory\> argument to the Gnope shortcut and get php-gtk to run using the Gnope version of php. I was able to work on existing php pages in Eclipse and Zend with the original php, at the same time fiddle with the Gnope demo apps running under the Gnope php5.1.1 version.

Left to do is to tweak the GnopeAppRun so it doesn't search all around my system looking for a php installation, but will just default to the gnope php installation when it fires off a php-gtk app. Right now the app launcher doesn't work, but I can directly open the php demo page and run the demos.

I may be missing some other problems, I haven't done much yet, but so far so good getting two different php to run. The pear side of things may not be right, since I have a whole bunch of PEAR environment variables all pointing to the original installation.

Ideally for me is to be able to create a gnope-based application that I can distribute without interfering with any existing php/pear on a target machine.

[cweiske]

[Doug G]