Page 1 of 1

New control panel launches old xampp

PostPosted: 02. October 2020 07:20
by dCart
Hi
I have big problem with my xampp.
In "xampp7.2" folder I have xampp with php 7.2, in "xampp7.4" I have xampp with php 7.4. When I run control panel from xampp7.4 directory, it run xampp from "xampp7.2" directory. What I must do if I want use two xampp with php 7.x?

p.s I have third xampp with php 5.6 but it works very well.

Best regards
Paul

Re: New control panel launches old xampp

PostPosted: 02. October 2020 07:30
by Altrea
Did you register any Windows services for your xampp 7.2 components?

Re: New control panel launches old xampp

PostPosted: 02. October 2020 08:53
by dCart
Thank you for your answer.
What do you mean?

Re: New control panel launches old xampp

PostPosted: 02. October 2020 09:31
by Nobbie
In Xampp Control Panel you can activate an option for each tool (Apache, Mysql etc.) to run it as a windows service. There is a controlbox for each service where you can click and set a red cross. Did you do that?

Re: New control panel launches old xampp

PostPosted: 07. October 2020 16:02
by silvanet
Altrea wrote:Did you register any Windows services for your xampp 7.2 components?


Is there a version 7 of xampp controller? I just installed the latest version of xampp from apachefriends and the control panel says version 3.2.4.

I had an older version on Windows 10 and followed instructions to delete it and install the new version (I selected 7.4.10. The first thing I noticed was red letter warning that Windows was using port 21 & I must resolve the conflict or Filezilla would not start.

Well, Filezilla started fine and I used the client to do file transfers on port 21 without a problem.

When I shut down the client and stopped what I was running on the control panel (Apache, MySQL, and Filezilla) then tried to quit, I got a bigger problem that I'm not sure was related. I got Windows access denied error and unable to create control.ini. Xampp control hung up and I had to eventurlly kill the process. The only way to stop that was to manually start xampp controller as administrator.

I don't know how to do that other than manually though. Filezilla then works fine and no errors on shutdown or control panel quit. But still that red message appears on every start before I even run Filezilla.

OK, I figured out my confusion. I wasn't using Filezilla server at all. I really don't need to. I was running Filezilla Client. Still, I never saw those messages in my prior Xampp installation, nor the access errors.

Do I just have to live with that?