Re: Manual WinXP installation??

Hi Greg, Sorry, yes, I forgot to give adequate details of my setup: I'm on WinXP Pro. The server is Apache 1.3.24 running PHP 4.2.3, ( and I understand that the favoured solution is to upgrade PHP, which is probably what I shall ultimately do). There is an added complication that my brief is to establish working procedures with PEAR, before utilising the main University (Unix) servers for the whole web team. PEAR isn't yet functional on the main servers at present either. The maintainer of those servers is on leave, which is why I am trying to install it on my local machine for starters - localhost is a lot less complex. So, on my computer the directories are a bit of a mess following my numerous installation efforts, and I only wrote the help email because I was losing the place. My webRoot directory is c:\_publish, in there, there are two pear attempts.. c:\publish\gopear\PEAR\cache, data, docs,tests c:\publish\PEAR\cache, data, docs, OS, PEAR,scripts, tests.. and in that PEAR sub-directory c:\publish\PEAR\PEAR\ cache,Command,data,docs,Frontend,tests Then outside the web directories I have.. c:\apache\ Apache and php423 c:\apache\php423\pear\ containing.. Archive,Console,Crypt,Date,DB,docs,File,HTML,HTTP,Mail,Net, PEAR,Schedule,scripts,tests,XML c:\apache\php423\pear\PEAR\ command, Frontend I suspect the full set of directories (Archive, etc.) came with the PHP install, since the Webinstaller didn't appear to get files - it just created directories. c:\apache\php423\pear2\ cache,data,docs,tests and in this cache, based on the error message from the WebInstaller, I manually downloaded and unzipped.. c:\apache\php423\pear2\cache\PEAR-1.2b2 which has OS,PEAR,scripts, and here PEAR only contains c:\apache\php423\pear2\cache\PEAR-1.2b2\PEAR\ Command and Frontend. Then there's another lot at: c:\php4\pear\.registry cache,data,docs,tests and c:\php-4.2.1-Win32\pear\ which contains the full set.. Archive,Console,Crypt,Date,DB,docs,File,HTML,HTTP,Mail,Net, PEAR,Schedule,scripts,tests,XML c:\php-4.2.1-Win32\pear\PEAR\Command and Frontend\ php.ini include_path is pointing to ".\;C:\_publish\PEAR", and I had matching directories set in pear.bat. However, at some point I was able to run whichever commandline prg allows show-config options (?) and this reported the paths as being "c:\php4" - nothing to do with what I set in the batch file. (This php4 is left over from an earlier attempt, and was not intentionally part of the current installation session. I don't know where this path is getting recorded, because running SET doesn't show it as a variable. So, that was one problem.) Most times, I tried the WebInstaller method, calling http://localhost/go_pear.php which ran the frontend OK, went online, and reported the error Starting installation ... Loading zlib: failed <--- I suspect this is the main place where the autoinstall went awry? Downloading uncompressed packages: C:/DOCUME~1/com168/LOCALS~1/Temp/gop1E.tmp The downloading following the zlib comment appears to fail; which the empty directories c:\publish\gopear\PEAR\cache, data, docs,tests appear to confirm. (Also, C:\Documents and Settings\usr168\Local Settings\Temp is empty) - I leave it for a respectable length of downloading time before having to "Esc" the browser. Running C:\_PUBLISH\PEAR>pear.bat gives <br /> <b>Fatal error</b>: Failed opening required 'Console/Getopt.php' (include_path= '.\;C:\_publish\PEAR') in <b>C:\_publish\PEAR\System.php</b> on line <b>23</b><br /> I made several attempts with webInstaller, and also (since I had it installed) running the command line from CYGWIN.... but, it's all getting a bit vague now, just exactly what I did from which directory. Consequently, I thought it would be quicker just setting up things manually, and deleting all the other stuff... or, upgrading PHP to 4.3.x So, there's some details which perhaps indicate the reason why I judged you, "didn't want to know", in my original email :-) Thanks for your interest. If you want to know further and more relevant details, don't hesitate to ask, as I would be glad to assist with installer debugging efforts, but perhaps you will agree that, at this stage, the simplest solution *for me* is to upgrade PHP 4.3.x? :-) John -- (Montgomery, Web Design Unit, 01224 273218, j.t.montgomery@abdn.ac.uk) Open Day 2003 - Tuesday 26th August For more details see: http://www.abdn.ac.uk/openday