Hello to all who dare to answer.

It shouldn't be this hard. I have spent a dozen hours getting my localhost environment up and running. Had PhpED working, until I installed WAMP, (to solve a different problem). Got WAMP working by uninstalling the additional PHP versions. (After trying everything else I could think of)

I looked for a WAMP version with PHP versions to match ANY of the three listed in PhpED, but I can't seem to find it. Isn't there an addon somewhere? An additional PHP version I can add to WAMP so PhpED works?

Can't the two play nice? Any suggestions?

WAMP 64 bit:
wampserver2.2e-php5.3.13-httpd2.2.22-mysql5.5.24-x64

Apache: 2.2e
PHP: 5.3.13
MySQL: 5.5.24

PhpED: 8.1

Thanks in advance for all who offer suggestions, I appreciate you taking the time to help this geek out.

Cenay'

You don't need any "matched" versions of php. Just any of them from 4.4 up to 5.4 will work with a very slim exceptions like 5.2.0-5.2.2 or 5.0.0-5.0.4 and a few others which are broken/incompatible from the beginning, but it's definitely not the case with all recent versions of php.

As of "suggestions", it's unclear what does not work for you. You said roughly nothing about that.

No localhost is available, unless I remove (using control panel) the PHP installations of the versions the PhpED installs. And it shouldn't effect it, I know!

Uninstalled everything (PhpED and WAMP), and started over, in a different order. WAMP ran fine until I installed PhpED. WHen I got to the IDE, I attempted to debug a PHP script. IDE reported missing files (something about the DBG wizard) and asked if I wanted to "fix it". I said yes, then the localhost went away again.

No PHP scripts, even NOT running with IDE work now.

Uninstalled PhpED and my WAMP environment is back, localhost works, and I am able to run PHP scripts locally.

In general the "localhost" hostname availability depends on OS, not on user software. If you mean HTTP service behind localhost, like http://localhost/ - it depends on http server, not on PhpED. What PhpED checks is php.ini placed into a wrong/shared place like C:\Windows directory. This is what breaks ALL OTHER php distro installed and would not let them work at all. Guess what will happens with your c:\blahblah\php if it loads php.ini from C:\Windwos and there is extension_dir points to load extensions from C:\Wamp\php. No way.
If WAMP works this way, I'd highly recommend you not to use it or move its php.ini into WAMP's own, non-shared directory and adjust apache settings to have php finding its php.ini appropriately. Then raise an issue at WAMP site so they will change their defaults to that.
Alternatively, you can try our own stack of php+apache - NuSphere TechPlatform. It does not break php installed by others (including our owns)

I had exactly this problem with an already installed WAMP server. Old posts on this subject don't apply to newer wamp server installs. phped now handles the .dll file extension issue but I had to add this line:
extension=dbg-php-5.4.dll
into C:\wamp\bin\apache\apache2.2.22\bin\php.ini
hope this helps
cheers