php-install Digest 5 Jul 2002 12:53:02 -0000 Issue 917

Topics (messages 7623 through 7627):

gd and freetype
        7623 by: Daniel Svanbäck

newbie-Apache Install on XP
        7624 by: Brandon

Re: Installing PHP on WinXP with IIS
        7625 by: Saci

Small Doubt
        7626 by: Phaneendra

Aspell Mystery Files & Functions
        7627 by: Alex J. Champandard

Administrivia:

To subscribe to the digest, e-mail:
        [EMAIL PROTECTED]

To unsubscribe from the digest, e-mail:
        [EMAIL PROTECTED]

To post to the list, e-mail:
        [EMAIL PROTECTED]


----------------------------------------------------------------------
--- Begin Message ---
Hi!

How do I install freetype2 when I allready have gd 1.8.4 installed. Do I
have to recompile the php module.. there have to be an easier way


--- End Message ---
--- Begin Message ---
I am attempting to set up PHP 4.2.1 on WinXP Home with Apache 2.0.39 already installed 
and running.

After following instructions in the install file to move dll's into appropriate 
locations and edit php.ini accordingly, I continuosly receive an error when attempting 
to 
start Apache. Apache will not start and I find the following error message in the 
Application Event Error log:

Apache.exe: module "c:\php4build\snap\sapi\apache2filter\sapi_apache2.c" is not 
compatible with this version of Apache.

and the System Error from the system log:

The Apache2 service terminated with service-specific error 1 (0x1).

Is there a configuration file pointing to this file? I can't find the file anywhere on 
the system... 

Any ideas????

Thanks,
Brandon


--- End Message ---
--- Begin Message ---
Did you read the Help ? I Guess not


Windows NT/2000/XP and IIS 4 or newer and PWS 4 on NT Workstation or W2K non
server editions

   To install PHP on an NT/2000/XP Server running IIS 4 or newer,
   follow these instructions. You have two options to set up
   PHP, using the CGI binary (php.exe) or with the ISAPI module.

   In either case, you need to start the Microsoft Management
   Console (may appear as 'Internet Services Manager', either
   in your Windows NT 4.0 Option Pack branch or the Control
   Panel=>Administrative Tools under Windows 2000). Then
   right click on your Web server node (this will most probably
   appear as 'Default Web Server'), and select 'Properties'.

   If you want to use the CGI binary, do the following:
    Under 'Home Directory', 'Virtual Directory', or
    'Directory', click on the 'Configuration' button,
    and then enter the App Mappings tab.

    Click Add, and in the Executable box, type:
    c:\php\sapi\php.exe (assuming that you have unzipped PHP in c:\php\).

    Please note that you cannot use php-cli.exe with your webserver, you
need
    to use php.exe which can be found in the sapi directory of your PHP
    distribution.

    In the Extension box, type the file name extension you want
    associated with PHP scripts. Leave 'Method exclusions'
    blank, and check the Script engine checkbox. You may also
    like to check the 'check that file exists' box - for a small
    performance penalty, IIS (or PWS) will check that the script
    file exists and sort out authentication before firing up php.
    This means that you will get sensible 404 style error messages
    instead of cgi errors complaing that php did not output any data.

    You must repeat from 'Click Add...' for each extension you
    want associated with PHP scripts.
    (.php is recommended. although .phtml and .php3 may be
    required for legacy applications.)

    Set up the appropriate security. (This is done in Internet
    Service Manager), and if your NT Server uses NTFS file system,
    add execute rights for I_USR_ to the directory that contains
    php.exe

   To use the ISAPI module, do the following:

    If you don't want to perform HTTP Authentication using PHP,
    you can (and should) skip this step. Under ISAPI Filters,
    add a new ISAPI filter. Use PHP as the filter name, and
    supply a path to the php4isapi.dll.

    Under 'Home Directory', click on the 'Configuration' button.
    Add a new entry to the Application Mappings. Use the path
    to the php4isapi.dll as the Executable, supply .php as the
    extension, leave Method exclusions blank, and check the
    Script engine checkbox.

    Stop IIS completely (net stop iisadmin)
    Start IIS again  (net start w3svc)


"Bill Ross" <[EMAIL PROTECTED]> escreveu na mensagem
news:[EMAIL PROTECTED]...
> I'm trying to set up PHP on my winXP box that is running IIS.  I have
tried
> the win32 installer for the newest version of PHP but after running the
> installer the server still did not know what to do with a php file.  I
also
> tried the manual install of PHP 4.1.2 and it also is not working.  IIS is
> recognising the isapi filter and I have double checked that all of the
dll's
> are in the right spot but all that is displayed when I run a php test page
> is the code.  Any help on this would be great.
>
>


--- End Message ---
--- Begin Message ---
I want to configure PHP to run on Apache so that my user won't get
the .php  extension on his browser window while interacting with my
script ...

Can I do this ??? If Yes, How??? ...

Thanx in advance ...

/Phani
[EMAIL PROTECTED]



--- End Message ---
--- Begin Message ---
Hey,

I've been labouring over this and searching about it for too long now, and 
thought I'd turn to here as a last resort.

Pspell .12.2 is compiled, along side aspell .33.7.1.  It works fine from 
the command line.

I've got the latest PHP (4.2.1), compiling fine with pspell (and working, 
though no dictionaries)... I gathered I needed aspell's dictionaries to fix 
that, so I tried to compile --with-aspell.  It whinges about the C header 
file "aspell-c.h", which apparently was not updated in the latest few 
distributions due to the move to C++, and is no longer supported.  So I 
fetched it from another slightly earlier version of aspell, but naturally 
the symbols are undefined (still no support for the C interface either).

With an older version of aspell (.33), it complains about the wrong format 
of dictionaries when I run from the command prompt.

So my question really is, what versions of pspell and aspell libraries do I 
need to get a working module?!

Agony!

Thanks,
Alex

--- End Message ---

Reply via email to