apache locking up windows 98 at startup

i installed apache webserver v2 on win 98 ver 2. when i start it up my
computer locks up. i used standard setup and when i test config it returns
'syntex ok'

error log
[Sat Jun 26 21:44:25 2004] [notice] Parent: Created child process -567107
[Sat Jun 26 21:44:26 2004] [notice] Child -567107: Child process is running
[Sat Jun 26 21:44:26 2004] [notice] Child -567107: Acquired the start mutex.
[Sat Jun 26 21:44:26 2004] [notice] Child -567107: Starting 250 worker threads.

any advice

alison

On 26 Jun 2004, allicyn1023@aol.com (Allicyn1023) wrote in
news:20040626171605.05570.00000693@mb-m14.aol.com:

> i installed apache webserver v2 on win 98 ver 2. when i start it
> up my computer locks up. i used standard setup and when i test
> config it returns 'syntex ok'
>
> error log
> [Sat Jun 26 21:44:25 2004] [notice] Parent: Created child process -567107
> [Sat Jun 26 21:44:26 2004] [notice] Child -567107: Child process is running
> [Sat Jun 26 21:44:26 2004] [notice] Child -567107: Acquired the start mutex.
> [Sat Jun 26 21:44:26 2004] [notice] Child -567107: Starting 250 worker threads.

I don't know the answer to your problem, but those lines from your error log
are normal for a normal startup.

I think apache warns against using version 2 on Windows 98.

On 26 Jun 2004 21:16:05 GMT, allicyn1023@aol.com (Allicyn1023) wrote:

>i installed apache webserver v2 on win 98 ver 2. when i start it up my
>computer locks up. i used standard setup and when i test config it returns
>'syntex ok'
>
>error log
>[Sat Jun 26 21:44:25 2004] [notice] Parent: Created child process -567107
>[Sat Jun 26 21:44:26 2004] [notice] Child -567107: Child process is running
>[Sat Jun 26 21:44:26 2004] [notice] Child -567107: Acquired the start mutex.
>[Sat Jun 26 21:44:26 2004] [notice] Child -567107: Starting 250 worker threads.
>
>any advice
>
>alison

I am only guessing here, but I recall many years back when I was using
Windows 95 that a driver bug somewhere caused the system to lock up
whenever an DOS-type console window was displayed while the modem
driver was active.

This affected all console applications including Apache running in
console mode. I remember using a small program, which I think was
called Apache Monitor, to run Apache in the background with the
console hidden. This bypassed the problem for Apache at least.

I believe that Apache 2 for Windows now ships with Apache Monitor as
part of the distribution. You may like to give it a try if you haven't
already.

Also, if you *are* using a dialup modem you might like to try running
Apache while there is no Internet connection active. It would also be
interesting to see if you are able to open other console applications
without the system locking up.

Good luck,
-Claire