Invalid Configuration Directive

[taskmeister]

I think I have installed PEAR on a 64-bit Vista Installation. However when I perform any of the pear command line activities I receive a warning "Invalid Configuration Directive" which I click an OK button on.

The command line operations seem to function just fine otherwise.

The config-show indicates that I should probably have a pear.ini and pearsys.ini files in my C:\windows directory. However a search of my machine indicates that no pear.ini or pearsys.ini files exist.

I attempted to create a blank set of ini files into the directory and found it required administrative authorization. When I copied files in to that location the command line operations failed with a bad or corrupted configuration file.

Well I guess a blank file isn't what was expected so I am thinking that the installation creates the .ini files and it was unable to because it did not have administrative authority.

Is there a way to build the .ini files or are they not absolutely necessary?

I have a Windows XP machine that built it's own pear.ini so not being certain of the format I am hesitant to attempt an edit build for this machine using that old formatted pear.ini.

[miketux]

I'm in a windows 2003 x64 and the same thing is happening, all the commands works fine, but I recieve that diturbing message.
_________________
Making the web a better place to live.