Today we are unleashing dAMP 3.1.0, which includes many new features, enhancements, tweaks, and much more. This one took a lot of thought, programming, and testing to complete.
Before we get into what's new we would like to point out that this new version has a small little message that will appear in the lower right corner of your computer screen above the time clock after about 10 minutes. It will stay there until you close dAMP. It just says the version number by DialMe.com, and informs you that it is donationware. This message could be removed completely in future releases depending on the number of donations.
If this message bothers you too much you can:
1. Make a donation and we will send you an update without the message.
2. Restart dAMP after the message appears and you have 10 more minutes without it.
3. Don't use dAMP.
*See the ReadMe file or button in dAMP for more details.
Overall it's very small and not any more noticeable than the Boonex Logo in the Free Dolphin version.
With that in mind here is what's new in this release:
You now have the option to extract dAMP anywhere on your computer. It should run from any location including an external USB or flash drive.
If you move dAMP to another location at a later time you will need to do one of two things.
1. Delete the file:
(Folder-Location)\dAMP\dAMPserver\www\dolphin\inc\header.inc.php restart dAMP and it will automatically generate a new header.inc.php file with the new location for you.
2. Update the file:
(Folder-Location)\dAMP\dAMPserver\www\dolphin\inc\header.inc.php with the new location path.
For example find this line in header.inc.php:
$dir['root'] = "C:/dAMP/dAMPserver/www/dolphin/";
Keep in mind that you need to use forward slashes (/) and not backslashes (\).
2. Custom Apache/httpd.conf ability
dAMP creates a new Apache httpd.conf file each time it starts up. This is necessary in the event that you move it to another location. If you do so the new paths will be generated automatically. This means that you can't directly edit httpd.conf because your changes would be overwritten each time it starts.
In order to prevent that if you want to use your own customized httpd.conf file you can do the following:
Make a copy of:
(Folder-Location)\dAMP\dAMPserver\server\Apache\conf\httpd.conf and name it httpd-custom.conf. Save/place it in the same folder. So you would have (Folder-Location)\dAMP\dAMPserver\server\Apache\conf\httpd-custom.conf.
You can then edit or change it, however, you want. After doing so save your changes, and restart dAMP so the changes take effect.
Each time dAMP starts up it will look for httpd-custom.conf first. If it finds it, it will use that one. If it doesn't it will genrate and use the default httpd.conf file.
If you mess up or change your mind simply delete the httpd-custom.conf file you created and dAMP will use the default httpd.conf file again.
Make sure that you don't save it as httpd-custom.txt or httpd-custom.conf.txt. It needs to be httpd-custom.conf only or it won't work.
If you do create a httpd-custom.conf file when you click on the Apache Config button in dAMP it will open your httpd-custom.conf file. If it doesn't find it the standard/default httpd.conf file will open.
3. Easy change PHP settings along with optional full php.ini editing
When you click on the PHP Config button in dAMP a new window will open and you can quickly change 5 of the more popular PHP settings that will affect Dolphin.
Max Execution Time
Max Input Time
Upload Max File Size
Post Max File Size
You may not need to change these as they are generally set high enough already. If you do just make your changes and click the Save Changes button. dAMP will then do a quick restart so they can take effect.
If you change Memory Limit, Upload Max File Size, or Post Max File Size be sure to include the M for MegaBytes at the end. 384 Megabytes would be 384M and not 384.
Max Execution Time, and Max Input Time are in seconds. 600 seconds is 10 minutes.
4. Enable/Disable APC Cache
In the same window you can select enable or disable APC Cache, and save the changes. dAMP will then restart. It is disabled by default. It really isn't necessary, but it's there to play with. If you notice anything strange happening in Dolphin disable APC Cache. It works well on some systems and not so well on others.
5. Edit php.ini and Restart button on the PHP Config screen.
You will also find a text link where you can manually edit the full php.ini. If you make any changes to php.ini you will find a restart button that you can use so your manual changes will take effect.
6. Apache/MySql checks.
If you click on a button in dAMP that would require Apache or MySql then a quick check is performed to ensure they are running. If they are your request is processed. If one, the other, or both are not running dAMP will attempt to restart them. If either fail to start after two consecutive attempts dAMP will perform a quick restart. If the problem persists make sure you haven't improperly changed or edited configuration files.
7. dAMP CPU resource usage reduced.
Not that dAMP itself used very much CPU power to begin with, but we did manage to reduce CPU usage to almost none. That's not considering Apache, MySql, or ffmpeg. Their CPU usage will very depending on what you do. Ffmpeg/video related use with Dolphin is the most CPU hungry application by far. That's not Dolphin specific though, it's video conversion itself. Any time videos are converted whether with Dolphin or any other program it will chew up CPU power.
8. phpMyAdmin was updated to version 220.127.116.11
9. Dolphin was updated to 7.1.4