Define intimidating behaviour
You just need to copy this code into a PHP file.//php Code starts from here......//Reading the Registry$Wshshell= new COM('WScript.
Shell');$data= $Wshshell-reg Read('HKEY_LOCAL_MACHINE\SOFTWARE-Zip\path');echo "Data is::".$data;//Function for writing to the registry.function registry_write($folder, $key, $value, $type="REG_SZ")// Function to deleting from the Register Entry.function registry_delete($folder, $key, $value, $type="REG_SZ")//Here 7-ZIP is taken as a example.
All you needto do is add the following lines to the very end of the file: Load Module php5_module "C:/PHP/php5apache2_2.dll"Add Type application/x-httpd-php PHPIni Dir "C:/PHP"Make sure the Load Module and PHPIni Dir lines point to your PHP installationdirectory, and note the use of forward slashes (/) instead of backslashes (\) inthe paths.
Save your changes and Restart Apache using the Apache Service Monitor system tray icon.
Once in that situation the php installation routine cannot be rerun to correct the problem, so you effectively have a hosting lockout situation which can only be corrected by manual intervention.
Open from c:/php in your text editor If you installed Apache in the default location, the path shouldbe "C:\Program Files\Apache Software Foundation\Apache2.2\htdocs".
The values under the key should have the name of the PHP configuration directive and the string value. However, only configuration values changeable in Being able to put php directives in and have them work on a per-directory or per-vitual host basis is just great.
Now there's another aspect which might be worth being aware of: A directive put into your apache conf file applies to php when it runs as an apache module (i.e.
Look for the existing line in this file that begins with Directory Index, shownhere: All of the remaining options in this long and intimidating configuration fileshould have been set up correctly by the Apache install program.If all iswell, Apache will start up again without complaint.Registry Key Handling Through PHP: This is an ready to use code.One of the most serious problems here is that it is hard to determine programmatically which of three or more possible configuration methods (php.ini, ini, .htaccess) should be used on any given hosting company's server.The worst outcome is if an routine attempts to set .htaccess directives on a cgi-mode server, in which case the outcome is usually a '500' crash.