WampServer

Installed wampserver 2.1e (32 bit) on windows 7 Pro and seems fine.
Installed add-on for Apache 1.3.39, which also completed OK as long as I unticked 'start wampserver on finishing'.

However ...
If I change the Apache version from 2.2.17 to 1.3.39 the icon changes from green -> orange -> red -> orange.

In windows services the Apache service which was showing status='started'. startup type='manual' and with the description 'Apache/2.2.17(Win32) PHP/5.3.5' now has no status (not running), startup type='automatic' and doesn't show a description. The properties show it is using "c:\wamp\bin\apache\apache1.3.39\Apache.exe" -ntservice.

Trying to start the service from wamp's tray menu doesn't do anything (no error message either).
Try to put wamp online from the tray menu get the message from Aestan Tray Menu 'Could not execute menu item (internal error)[Exception] Could not perform service action:The service has not been started' And checking in windows services confirms it hasn't.

If I try to start the service in windows services it fails with the message 'Windows could not start the wampapache service on Local Computer Error 1067: The process terminated unexpectedly'

I have checked through this forum wondering if this a known issue but couldn't find any reference to the 1.3.39 package (I guess its pretty old!)

Any advice (apart from dump 1.3.39!) welcomed.

did you try downgrade php to 5.2.x .. 5.3 probably doesnt work with it

check c:\wamp\logs for some clues

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]

Thanks for tip about 'back-grading' php. I need to work with 5.2.6 anyway so I've done that now.
However it hasn't cured the issue. Does the Apache log help?

This log goes from:
- starting wamp with apache version 2.2.17 (which gives a green icon)
to:
- the orange icon after selecting version 1.3.39

apache_error.log
----------------
[Sun Jan 30 18:36:48 2011] [notice] Apache/2.2.17 (Win32) PHP/5.2.6 configured -- resuming normal operations
[Sun Jan 30 18:36:48 2011] [notice] Server built: Oct 18 2010 01:58:12
[Sun Jan 30 18:36:48 2011] [notice] Parent: Created child process 4276
[Sun Jan 30 18:36:48 2011] [notice] Child 4276: Child process is running
[Sun Jan 30 18:36:48 2011] [notice] Child 4276: Acquired the start mutex.
[Sun Jan 30 18:36:48 2011] [notice] Child 4276: Starting 64 worker threads.
[Sun Jan 30 18:36:48 2011] [notice] Child 4276: Starting thread to listen on port 80.
[Sun Jan 30 18:37:27 2011] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Sun Jan 30 18:37:27 2011] [notice] Child 4276: Exit event signaled. Child process is ending.
[Sun Jan 30 18:37:28 2011] [notice] Child 4276: Released the start mutex
[Sun Jan 30 18:37:29 2011] [notice] Child 4276: All worker threads have exited.
[Sun Jan 30 18:37:34 2011] [notice] Child 4276: Child process is exiting
[Sun Jan 30 18:37:34 2011] [notice] Parent: Child process exited successfully.

---
GFD

When downgrading, you have to do on all of them since they might not compatible; in other word, you should not use latest Wamp, but download older version instead

Download Wamp installer here
[downloads.jlbn.net]

Have fun,

FREE One A Day
FREE Photo
FREE Games
FREE Websites
FREE Portable GPS
FREE WAMP Guides

That sounded a good idea - thanks - but actually doesn't seem to make any difference (apart from old icon!). The apache service starts OK for 2.2.x but still fails to start for 1.3.x

All this stuff worked OK on an XP machine but have had to move on to windows 7 (32 bit). Anything else worth trying?

---
GFD

Make sure no other program conflict Wamp such as IIS, Skype, Zonealarm, firewall/antivirus, NOD32, Eset, any web related program including Remote Desktop ...

IIS and Apache/Wamp are both web server and might conflict in some way, so you have to disable IIS in order for Wamp to work

Disable IIS in Vista/W7:

Control Panel, Uninstall Programs, Turn Widows Features On or Off, uncheck Internet Information Services

Disable IIS in XP:

Control Panel, Add/Remove Programs, Add/Remove Windows Components, uncheck Internet Information Services (IIS)

Restart computer, then restart Wamp

Also, in folder C:\WINDOWS\System32\drivers\etc, open file hosts and delete anything in this file and have only this line below and nothing else

127.0.0.1 localhost

If using Skype, open Skype > Tools > Options > Advanced > Connection then uncheck "use port 80..." restart Wamp then Skype

Have fun,

FREE One A Day
FREE Photo
FREE Games
FREE Websites
FREE Portable GPS
FREE WAMP Guides

I had the same problem. Even though I was running Apache before on win 7 but I think due to some Windows update I lost my local server. I too went through this forum like crazy and did everything that was written here to no avail. I finally fixed it and I am itterating here for those who are having the same problem.
After installing WAMP, the quick launch icon showed the server was on line but I couldn't get localhost to come up. The quick launch icon was yelloow, like I was told it should be. Wrong, the icon needs to be green not yellow. So I clicked on the WAMP quick launch icon then the apache folderthen service then test port 80. Windows says port 80 is not being used! So back to the same spot: I clicked on the WAMP quick launch icon then the apache folderthen service then start/resume service and voila it started to work. I hope this helps.

I had checked for these before raising the issue as I noticed it had been suggested to others. However I have now carefully double checked as best I can.

IIS, remote desktop - definitely off.
Skype, Zonealarm - not installed.
Windows firewall set to allow each apache version.
NOD32, Eset - not sure what these are (I installed win7 on bare machine so unless they are part of win7 they shouldn't be there as I don't recognize them from the small amount of stuff I have put on)

Anti-virus is AVG 2011 (this worked OK with wamp on XP; it's only the a-v not the full Internet security package) I guess I'm not sure how to detect a conflict here but AVG hasn't burst into any alerts or anything.

The hosts file has some comment lines (#...) at the top but the only active line is:
127.0.0.1 localhost


So with wamp 2.0 / apache 1.3.39 / php 5.2.6 / mysql 4.1.22

The apache service, which is set to automatic, just doesn't start. The windows event log says:

Faulting application name: Apache.exe, version: 0.0.0.0, time stamp: 0x46de965e
Faulting module name: ApacheCore.dll, version: 0.0.0.0, time stamp: 0x46de965d
Exception code: 0xc0000005
Fault offset: 0x00026a5b
Faulting process id: 0x2b8
Faulting application start time: 0x01cbc2338b721199
Faulting application path: c:\wamp\bin\apache\apache1.3.39\Apache.exe
Faulting module path: c:\wamp\bin\apache\apache1.3.39\ApacheCore.dll
Report Id: d2408177-2e26-11e0-ae9d-842b2b9b4815

If I go to the wamp tray and do a test post 80 it reports 'Your port 80 is not actually used'. Which sort of makes sense if the service hasn't started, and confirms(?) a lack of conflicts.

If I switch the apache version to 2.2.11 (came with wamp 2.0) then the test port 80 result is 'Your port 80 is actually used by : Server: Apache/2.2.11 (Win32) PHP/5.2.6' - and it all works.

So, where does that leave us with 1.3.39?

---
GFD

@igwebs : Thanks for joining in.

Were you using Apache 1.3.39 ?

---
GFD

Quote

Anti-virus is AVG 2011

Some Wamp users reported that they had problem to run Wamp w/ this AV, so uninstall both Wamp and firewall/antivirus, remove wamp folder, run regedit to search and delete 2 registries wampapache and wampmysql, restart PC, reinstall Wamp first then reinstall firewall/antivirus AFTER and WHILE Wamp is running

Quote

So, where does that leave us with 1.3.39?

It's not compatible; check here
[jlbn.net]

Have fun,

FREE One A Day
FREE Photo
FREE Games
FREE Websites
FREE Portable GPS
FREE WAMP Guides

> So, where does that leave us with 1.3.39?
>
> It's not compatible; check here
> [jlbn.net]

My reading of this was Apache 1.3.9 was OK with any PHP 4 or PHP 5. How are you reading the chart?

---
GFD

yes the chart says its compatiable..

Apache 1.3.39 >= PHP 4.0

If you want ill take a quick look at it using teamviewer or similar...

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]

I need to make some tests with Apache 1.3.41 + PHP 5.2.6.

I downloaded and installed WAMPServer 2.0 (I though that an old version of Apache may not run on a new WAMPServer2.1x) then I got Apache 1.3.41 + PHP 5.2.6 installed on WAMPServer 2.0 and I'm experiencing the same problems as GreenFlagDog.

It seems to works fine if I change to Apache 2.2.11 + PHP 5.2.6

My OS = Windows 7 Professional


Please, what to do?

Thanks,
Julio Mafra



Edited 1 time(s). Last edit at 02/03/2011 11:10PM by jcmafra.

I tried, for 2 or 3 times, to start Apache 1.3.41 as follow:
- Ran "Command Prompt"
- Changed to the folder to which WAMPServer/Apache1.3.41 was installed
- typed command apache

A lot of error message came from and Apache did not run.

I'm posting the Apache erro log:

[Thu Feb 03 17:51:10 2011] [notice] Apache/2.2.11 (Win32) PHP/5.3.0 configured -- resuming normal operations
[Thu Feb 03 17:51:10 2011] [notice] Server built: Dec 10 2008 00:10:06
[Thu Feb 03 17:51:10 2011] [notice] Parent: Created child process 6920
[Thu Feb 03 17:51:10 2011] [notice] Child 6920: Child process is running
[Thu Feb 03 17:51:10 2011] [notice] Child 6920: Acquired the start mutex.
[Thu Feb 03 17:51:10 2011] [notice] Child 6920: Starting 64 worker threads.
[Thu Feb 03 17:51:10 2011] [notice] Child 6920: Starting thread to listen on port 80.
[Thu Feb 03 17:51:18 2011] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Thu Feb 03 17:51:18 2011] [notice] Child 6920: Exit event signaled. Child process is ending.
[Thu Feb 03 17:51:19 2011] [notice] Child 6920: Released the start mutex
[Thu Feb 03 17:51:20 2011] [notice] Child 6920: All worker threads have exited.
[Thu Feb 03 17:51:20 2011] [notice] Child 6920: Child process is exiting
[Thu Feb 03 17:51:20 2011] [notice] Parent: Child process exited successfully.
[Thu Feb 03 17:51:20 2011] [notice] Apache/2.2.11 (Win32) PHP/5.3.0 configured -- resuming normal operations
[Thu Feb 03 17:51:20 2011] [notice] Server built: Dec 10 2008 00:10:06
[Thu Feb 03 17:51:20 2011] [notice] Parent: Created child process 7812
[Thu Feb 03 17:51:21 2011] [notice] Child 7812: Child process is running
[Thu Feb 03 17:51:21 2011] [notice] Child 7812: Acquired the start mutex.
[Thu Feb 03 17:51:21 2011] [notice] Child 7812: Starting 64 worker threads.
[Thu Feb 03 17:51:21 2011] [notice] Child 7812: Starting thread to listen on port 80.
[Thu Feb 03 17:57:30 2011] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Thu Feb 03 17:57:30 2011] [notice] Child 7812: Exit event signaled. Child process is ending.
[Thu Feb 03 17:57:31 2011] [notice] Child 7812: Released the start mutex
[Thu Feb 03 17:57:32 2011] [notice] Child 7812: All worker threads have exited.
[Thu Feb 03 17:57:32 2011] [notice] Child 7812: Child process is exiting
[Thu Feb 03 17:57:32 2011] [notice] Parent: Child process exited successfully.
[Thu Feb 03 17:57:43 2011] [notice] Apache/2.2.11 (Win32) PHP/5.3.0 configured -- resuming normal operations
[Thu Feb 03 17:57:43 2011] [notice] Server built: Dec 10 2008 00:10:06
[Thu Feb 03 17:57:43 2011] [notice] Parent: Created child process 6024
[Thu Feb 03 17:57:43 2011] [notice] Child 6024: Child process is running
[Thu Feb 03 17:57:43 2011] [notice] Child 6024: Acquired the start mutex.
[Thu Feb 03 17:57:43 2011] [notice] Child 6024: Starting 64 worker threads.
[Thu Feb 03 17:57:43 2011] [notice] Child 6024: Starting thread to listen on port 80.
[Thu Feb 03 17:58:03 2011] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Thu Feb 03 17:58:03 2011] [notice] Child 6024: Exit event signaled. Child process is ending.
[Thu Feb 03 17:58:04 2011] [notice] Child 6024: Released the start mutex
[Thu Feb 03 17:58:05 2011] [notice] Child 6024: All worker threads have exited.
[Thu Feb 03 17:58:05 2011] [notice] Child 6024: Child process is exiting
[Thu Feb 03 17:58:05 2011] [notice] Parent: Child process exited successfully.
[Thu Feb 03 18:17:57 2011] [notice] Apache/2.2.11 (Win32) PHP/5.3.0 configured -- resuming normal operations
[Thu Feb 03 18:17:57 2011] [notice] Server built: Dec 10 2008 00:10:06
[Thu Feb 03 18:17:57 2011] [notice] Parent: Created child process 7036
[Thu Feb 03 18:17:57 2011] [notice] Child 7036: Child process is running
[Thu Feb 03 18:17:57 2011] [notice] Child 7036: Acquired the start mutex.
[Thu Feb 03 18:17:57 2011] [notice] Child 7036: Starting 64 worker threads.
[Thu Feb 03 18:17:57 2011] [notice] Child 7036: Starting thread to listen on port 80.
[Thu Feb 03 18:18:21 2011] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Thu Feb 03 18:18:21 2011] [notice] Child 7036: Exit event signaled. Child process is ending.
[Thu Feb 03 18:18:22 2011] [notice] Child 7036: Released the start mutex
[Thu Feb 03 18:18:23 2011] [notice] Child 7036: All worker threads have exited.
[Thu Feb 03 18:18:23 2011] [notice] Child 7036: Child process is exiting
[Thu Feb 03 18:18:23 2011] [notice] Parent: Child process exited successfully.
[Thu Feb 03 18:18:23 2011] [notice] Apache/2.2.11 (Win32) PHP/5.2.6 configured -- resuming normal operations
[Thu Feb 03 18:18:23 2011] [notice] Server built: Dec 10 2008 00:10:06
[Thu Feb 03 18:18:23 2011] [notice] Parent: Created child process 6352
[Thu Feb 03 18:18:24 2011] [notice] Child 6352: Child process is running
[Thu Feb 03 18:18:24 2011] [notice] Child 6352: Acquired the start mutex.
[Thu Feb 03 18:18:24 2011] [notice] Child 6352: Starting 64 worker threads.
[Thu Feb 03 18:18:24 2011] [notice] Child 6352: Starting thread to listen on port 80.
[Thu Feb 03 18:18:51 2011] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Thu Feb 03 18:18:51 2011] [notice] Child 6352: Exit event signaled. Child process is ending.
[Thu Feb 03 18:18:52 2011] [notice] Child 6352: Released the start mutex
[Thu Feb 03 18:18:53 2011] [notice] Child 6352: All worker threads have exited.
[Thu Feb 03 18:18:53 2011] [notice] Child 6352: Child process is exiting
[Thu Feb 03 18:18:53 2011] [notice] Parent: Child process exited successfully.
[Thu Feb 03 19:59:31 2011] [notice] Apache/2.2.11 (Win32) PHP/5.2.6 configured -- resuming normal operations
[Thu Feb 03 19:59:31 2011] [notice] Server built: Dec 10 2008 00:10:06
[Thu Feb 03 19:59:31 2011] [notice] Parent: Created child process 6496
[Thu Feb 03 19:59:31 2011] [notice] Child 6496: Child process is running
[Thu Feb 03 19:59:31 2011] [notice] Child 6496: Acquired the start mutex.
[Thu Feb 03 19:59:31 2011] [notice] Child 6496: Starting 64 worker threads.
[Thu Feb 03 19:59:31 2011] [notice] Child 6496: Starting thread to listen on port 80.
[Thu Feb 03 20:40:50 2011] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Thu Feb 03 20:40:50 2011] [notice] Child 6496: Exit event signaled. Child process is ending.
[Thu Feb 03 20:40:51 2011] [notice] Child 6496: Released the start mutex
[Thu Feb 03 20:40:52 2011] [notice] Child 6496: All worker threads have exited.
[Thu Feb 03 20:40:52 2011] [notice] Child 6496: Child process is exiting
[Thu Feb 03 20:40:52 2011] [notice] Parent: Child process exited successfully.
[Thu Feb 03 20:40:59 2011] [notice] Apache/2.2.11 (Win32) PHP/5.2.6 configured -- resuming normal operations
[Thu Feb 03 20:40:59 2011] [notice] Server built: Dec 10 2008 00:10:06
[Thu Feb 03 20:40:59 2011] [notice] Parent: Created child process 8532
[Thu Feb 03 20:40:59 2011] [notice] Child 8532: Child process is running
[Thu Feb 03 20:40:59 2011] [notice] Child 8532: Acquired the start mutex.
[Thu Feb 03 20:40:59 2011] [notice] Child 8532: Starting 64 worker threads.
[Thu Feb 03 20:40:59 2011] [notice] Child 8532: Starting thread to listen on port 80.
[Thu Feb 03 20:41:04 2011] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Thu Feb 03 20:41:04 2011] [notice] Child 8532: Exit event signaled. Child process is ending.
[Thu Feb 03 20:41:05 2011] [notice] Child 8532: Released the start mutex
[Thu Feb 03 20:41:06 2011] [notice] Child 8532: All worker threads have exited.
[Thu Feb 03 20:41:06 2011] [notice] Child 8532: Child process is exiting
[Thu Feb 03 20:41:06 2011] [notice] Parent: Child process exited successfully.
Processing config directory: c:/wamp2_0/alias/*
Processing config file: c:/wamp2_0/alias/phpmyadmin.conf
Processing config directory: c:/wamp2_0/alias/*
Processing config file: c:/wamp2_0/alias/phpmyadmin.conf
PHP Warning: PHP Startup: gd: Unable to initialize module
Module compiled with module API=20090626, debug=0, thread-safety=1
PHP compiled with module API=20060613, debug=0, thread-safety=1
These options need to match
in Unknown on line 0
<br />
<b>Warning</b>: PHP Startup: gd: Unable to initialize module
Module compiled with module API=20090626, debug=0, thread-safety=1
PHP compiled with module API=20060613, debug=0, thread-safety=1
These options need to match
in <b>Unknown</b> on line <b>0</b><br />
PHP Warning: PHP Startup: Unable to load dynamic library 'c:/wamp2_0/bin/php/php5.3.0/ext/php_mbstring.dll' - Não foi possível encontrar o procedimento especificado.

in Unknown on line 0
<br />
<b>Warning</b>: PHP Startup: Unable to load dynamic library 'c:/wamp2_0/bin/php/php5.3.0/ext/php_mbstring.dll' - Não foi possível encontrar o procedimento especificado.

in <b>Unknown</b> on line <b>0</b><br />
PHP Warning: PHP Startup: gd: Unable to initialize module
Module compiled with module API=20090626, debug=0, thread-safety=1
PHP compiled with module API=20060613, debug=0, thread-safety=1
These options need to match
in Unknown on line 0
<br />
<b>Warning</b>: PHP Startup: gd: Unable to initialize module
Module compiled with module API=20090626, debug=0, thread-safety=1
PHP compiled with module API=20060613, debug=0, thread-safety=1
These options need to match
in <b>Unknown</b> on line <b>0</b><br />
PHP Warning: PHP Startup: Unable to load dynamic library 'c:/wamp2_0/bin/php/php5.3.0/ext/php_mbstring.dll' - Não foi possível encontrar o procedimento especificado.

in Unknown on line 0
<br />
<b>Warning</b>: PHP Startup: Unable to load dynamic library 'c:/wamp2_0/bin/php/php5.3.0/ext/php_mbstring.dll' - Não foi possível encontrar o procedimento especificado.

in <b>Unknown</b> on line <b>0</b><br />
PHP Warning: PHP Startup: Unable to load dynamic library 'c:/wamp2_0/bin/php/php5.3.0/ext/php_mysql.dll' - Não foi possível encontrar o procedimento especificado.

in Unknown on line 0
<br />
<b>Warning</b>: PHP Startup: Unable to load dynamic library 'c:/wamp2_0/bin/php/php5.3.0/ext/php_mysql.dll' - Não foi possível encontrar o procedimento especificado.

in <b>Unknown</b> on line <b>0</b><br />
PHP Warning: PHP Startup: Unable to load dynamic library 'c:/wamp2_0/bin/php/php5.3.0/ext/php_mysqli.dll' - Não foi possível encontrar o procedimento especificado.

in Unknown on line 0
<br />
<b>Warning</b>: PHP Startup: Unable to load dynamic library 'c:/wamp2_0/bin/php/php5.3.0/ext/php_mysqli.dll' - Não foi possível encontrar o procedimento especificado.

in <b>Unknown</b> on line <b>0</b><br />
PHP Warning: PHP Startup: Unable to load dynamic library 'c:/wamp2_0/bin/php/php5.3.0/ext/php_pdo_mysql.dll' - Não foi possível encontrar o procedimento especificado.

in Unknown on line 0
<br />
<b>Warning</b>: PHP Startup: Unable to load dynamic library 'c:/wamp2_0/bin/php/php5.3.0/ext/php_pdo_mysql.dll' - Não foi possível encontrar o procedimento especificado.

in <b>Unknown</b> on line <b>0</b><br />
PHP Warning: PHP Startup: Unable to load dynamic library 'c:/wamp2_0/bin/php/php5.3.0/ext/php_pdo_sqlite.dll' - Não foi possível encontrar o procedimento especificado.

in Unknown on line 0
<br />
<b>Warning</b>: PHP Startup: Unable to load dynamic library 'c:/wamp2_0/bin/php/php5.3.0/ext/php_pdo_sqlite.dll' - Não foi possível encontrar o procedimento especificado.

in <b>Unknown</b> on line <b>0</b><br />
Apache server shutdown initiated...
Processing config directory: c:/wamp2_0/alias/*
Processing config file: c:/wamp2_0/alias/phpmyadmin.conf
[Thu Feb 03 20:46:01 2011] [notice] Apache/2.2.11 (Win32) PHP/5.2.6 configured -- resuming normal operations
[Thu Feb 03 20:46:01 2011] [notice] Server built: Dec 10 2008 00:10:06
[Thu Feb 03 20:46:01 2011] [notice] Parent: Created child process 6788
[Thu Feb 03 20:46:01 2011] [notice] Child 6788: Child process is running
[Thu Feb 03 20:46:01 2011] [notice] Child 6788: Acquired the start mutex.
[Thu Feb 03 20:46:01 2011] [notice] Child 6788: Starting 64 worker threads.
[Thu Feb 03 20:46:01 2011] [notice] Child 6788: Starting thread to listen on port 80.
[Thu Feb 03 20:46:11 2011] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Thu Feb 03 20:46:11 2011] [notice] Child 6788: Exit event signaled. Child process is ending.
[Thu Feb 03 20:46:12 2011] [notice] Child 6788: Released the start mutex
[Thu Feb 03 20:46:13 2011] [notice] Child 6788: All worker threads have exited.
[Thu Feb 03 20:46:13 2011] [notice] Child 6788: Child process is exiting
[Thu Feb 03 20:46:13 2011] [notice] Parent: Child process exited successfully.
[Thu Feb 03 20:46:13 2011] [notice] Apache/2.2.11 (Win32) PHP/5.2.6 configured -- resuming normal operations
[Thu Feb 03 20:46:13 2011] [notice] Server built: Dec 10 2008 00:10:06
[Thu Feb 03 20:46:13 2011] [notice] Parent: Created child process 7232
[Thu Feb 03 20:46:13 2011] [notice] Child 7232: Child process is running
[Thu Feb 03 20:46:13 2011] [notice] Child 7232: Acquired the start mutex.
[Thu Feb 03 20:46:13 2011] [notice] Child 7232: Starting 64 worker threads.
[Thu Feb 03 20:46:13 2011] [notice] Child 7232: Starting thread to listen on port 80.


Thanks,
Julio Mafra

-> Steve Martin:
Thanks for the offer to 'take a look'. While grateful and having no doubt it would bring a speedy resolution I am reluctant to open a channel into my machine - mainly because I wouldn't know what I was doing !!

-> jcmafra:
While trying to get Apache 1.3.39 to work I tried 1.3.41 and found the same as you.

---
If others are finding the same problem, that is:
Neither Apache 1.3.39 or 1.3.41 work with WAMP Server (2.0 or 2.1) on Windows 7 Pro and you have any useful error reports etc please add them to this thread so the valued and helpful experts in the forum can lead us out of this maze!

Just to recap my machine:
W7 pro
office 2010
AVG 2011 (a-v only)
IE8; Firefox 3.6, Filezilla 3.3, Eclipse
plus a small number of other coding and graphics apps typical of a web developer.

Win 7 was installed on a newly formatted machine only a couple of week ago, is only used by me, and hasn't complained about anything else - just apache 1.3.39/41 on wamp server.

---
GFD

yfastud had wondered (2/2/2011) if AVG anti-virus was a problem so ...

Uninstalled AVG anti-virus.
Uninstalled wampserver.
Removed wamp folder.
Removed registry entries (wampapache, wampmysql).
Restarted machine.

Installed wampserver2.1e-x32
Installed mysql 4.1.22 and selected it in the tray.
Installed PHP 5.2.6 and selected it in the tray.
All seems OK at this point (i.e. with Apache 2.2.17).

Installed Apache 1.3.39 went to tray and selected it and it pops up an error message.
'Could not execute menu item (internal error) [EAccessViolation] Access Violation ad address 0043AC36 in module 'wampmanager.exe'. Read address 69746349'

After dismissing this message and checking the tray it shows 1.3.39 as selected but not started. Testing port 80 reports 'your port 80 is not actually used'. At this point trying to start 1.3.39 triggers an error from Aestan Tray Menu.
'Could not execute menu item (internal error) [Exception] Could not perform service action: The service cannot be started, either because it is disabled or because it has no enabled devises associated with it.'

Notice at this point that no anti-virus has been installed so I'm guessing that isn't the issue.

OK this was wampserver 2.1e so, after cleaning that out, I tried wampserver2.0i which give a similar result from which I conclude the Apache 1.3.39 package will not run on Windows 7 Pro - unless someone knows otherwise ...

Perhaps a new compatibility table is required so Windows 7 users who need Apache 1.3.x need to look elsewhere?

---
GFD



Edited 2 time(s). Last edit at 02/11/2011 10:46AM by GreenFlatDog.

Same here with Apache 1.3.41 on Windows 7 x64 - doesn't start if accessed trom the Wamp server widget. It does not matter which PHP version is selected.

There is a workaround, though. Apache 1.3.x will run fine if started from the command line:

- Open a command prompt for your Apache 1.3 dir (C:\wamp\bin\apache\apache1.3.41 by default)
- run the command "apache -k start"

... and it works (at least it does for me).

So it looks like this is truly a Wampserver bug, perhaps with the control panel widget or the settings it tries to apply during startup. There is nothing wrong in principle to prevent Apache 1.3 from running on Windows 7.

That said, to my knowledge you can't run Apache 1.3 *as a service* on Windows 7. The bug report here suggests this won't ever be fixed: [issues.apache.org]

Cheers, Michael

1.3 is dead. and rightfully so

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]

@stevenmartin99: Unfortunately, that's wishful thinking. 1.3 can be found "in the wild" on all sorts of shared hosting services.

It should be part of routine testing for any component that is deployed in environments you don't have control over. Chances are that it will be around for some time to come. At the moment, it's probably about as dead as PHP 5.2 or Windows XP.

But I wish you were right

Cheers, Michael

php5.2 is the most used php on linux at the moment.

your talking about companys that nobody should be using..

1.3 is dead

its not supported any more and has tons of issues >> [httpd.apache.org]

there is no apache1.3 addon for wampserver2.2 but it is possible to run if you set up the wampmanaer.conf correctly

Steven Martin
stevenmartin99@gmail.com
stevenmartin99@hotmail.com
PampServer.com - [pampserver.com]