A little problem with installing Apache

The Apache (2.2) was installed a long time ago, and now it's suddenly a problem: accessing the file in a http://127.0.0.1/exercise/x.php way is normal, but entering the phpMyAdmin build table finds it impossible to log in ( The account password is correct and is recorded on the TXT document). Online check, all said may be port occupancy (such as IIS or Thunderbolt), toss A will choose to reload, the result, a bigger tragedy-even localhost can not access, plus 80 can not (also automatically ignored by the browser), some people say, To launch Apache in the bin directory Apache Monitor.exe, I take a go, disappear from thin air, and then from the Csdn down a, version number is also consistent, but directly to a fail, and then think how to let Monitor start success, stumbled finally met good people, Proverbs are as follows:. \apachex (x is the version number) \conf\ the httpd.conf file under the path, modify the listening port 80->88In this way, not only Apache service monitor can be started, Access localhost:88 can also display Appserv successfully installed pages, clickEnter your account number and password to enter phpMyAdmin.Originally, the port is really a problem ah, and then just want to see the process of the occupied port is the guy (after all, after all, with a good, suddenly by the horizontal knife to win love). Enter the DOS interface with CMD and enter the Netstat–nao commanddiscover that port 80 is actually occupied by pid=4 processes and then into Task Manager (Ctrl+alt+del) 799018-20170305111435157-1799703394.jpg (28.22 KB, download number: 0) Download attachments to albums 2017-3-11 18:44 Upload See the system these words, I dare not easily banned, had mistakenly deleted the system configuration file tragedy vividly, http://www.662p.com/a/system/window/2017/0311/6229. HTML This link is a relatively scientific solution to the NT Kernel & system occupancy Problems

A little problem with installing Apache