Hello, have not actually installed the software yet, but highly interested because I have been using WAMP for my PC and obviously MAMP for my MAC. Just going through the forum to investigate any problems beforehand. Nonetheless it appears to be an excellent stack and it seems many users are being a bit creative during the installation process.
So would the resolve of this particular issue have anything to do with the installation directory? Normally these type type of stacks install natively on the C: drive. As the DLL error stack points. Again seems like a lot of user creativity going on without the knowledge of knowing the paths need to be set in the config and/or ini files of each (Apache, PHP and MySQL) ...at least that is the case for WAMP ...however I leave the installation as the original programmer intended and leave outside creativeness to updating phpMyAdmin if applicable (that involves changing paths to the new version) and/or vhost configurations with paths to the www to a drive or its own sole partition. (I.e. E:\www)
Regardless it involves known path setting, and maybe you have done this since this is version 3.3 and I have 3.6 prepared to install to replace WAMP and MAMP...maybe enforce the native installation dir and rename the change directory button to advanced (with a JS alert stating "not recommended unless you know what you are doing and how to edit the files...") dialog...unless there is a script that edits and registers the directory based on custom install path during installation OR at least checks for an argument that considers known paths such as:
Drive:\Ampps
Drive:\Program Files (older OS)\Ampps ...or the same as older OS for x64
Drive:\Program Files (x86 newer OS)\Ampps
&& reject installation or disable folders if (user sets Desktop, or system folders such as Windows or System32...*you'd be surprised about this one and a couple of YouTube vids on how to know your system--especially editing the host file: a process for setting up virtual host domains can do to a person*)
It just seems like developers taking on this software should be path-oriented because making a website is solely based on it, and should be able to identify an error like C:\Ampps and C:\Program Files\Ampps are two different creatures and clearly pointing out the issue. I guess it is the programmer in me outside of also being a web developer which are two different creatures as well.
I was attracted to this post because "Apache failing to start..." is a noteworthy issue to gaze at, but I see no issues here other than the obvious. *sips tea*
----------------------- The worst installation to support is when a user installs the application to the Desktop!
|