Xampp Download 64 Bits

[Roman Bayramdurdiyev]

BecauseI've been using xampp / lampp for over one year and it's a very simple solution for web programmers - I don't need any "real" apache server on my PC. It gives me apache + php + mysql just with one simple command, and doesn't stay in memory after reboot (can be even stopped and removed after start).

I have xampp 7.1.9 for linux 64 bit from here. And by the way, after following your steps, I have no idea how to start mongo, I have never used pecl before. If I where you I'd install mongo using apt-get, Anyway good luck.

I have been searching in this forum and on internet just to find out if the Uniform Server installation package available for 64 bits machine like WAMP Server Packages that clearly indicates which one is for 32 bits and which for for 64 bits machine.

That is correct, on a 32bit OS individual processes have a RAM ceiling of 4GB (technically speaking. On windows it works out to be more like 3GB). This isn't a big deal for the Apache process, because if it's using that much RAM you're doing something wrong. On the other hand, it is a very big deal for MySQL, especially if you're wanting to use the InnoDB storage engine which needs to allocate a chunk of memory on initialization. As well, major performance gains can be made in MySQL by putting as much of your database into memory as possible to reduce hits on the hard drive - so, a 3GB-4GB ceiling on RAM usage by the MySQL process puts considerable limitations on how large the database can grow while still meeting performance needs.

Unfortunately, getting a fully 64bit Apache/PHP/MySQL server running nicely on windows is a pain in the ass. If you check the official PHP/Apache sites, you'll notice there aren't official 64 bit binaries (not the case with MySQL, though). What the WAMP Server folks are doing is building their own 64 bit versions of Apache and PHP. Even with full control over the binaries and the build process it's STILL non-trivial to get the server running without a hitch. It can also be difficult to find/build 64 bit versions of needed Apache modules and PHP extensions. Altogether, providing 64bit WAMP package is alot of work, and seeing as the 32bit version of Uniform server is more than adequate for doing development work, I can understand why Uniform Server hasn't gone 64bit yet.

So, if you want a 64bit Apace/PHP/MySQL Windows server, your choices are to build your own binaries, use a package like WAMP Server, or incorporate unofficial 64bit versions from some other source into the Uniform Server package. The best source for 64bit builds at this point in time is probably Recently, a forum user on that site built a 64bit version of PHP 5.4.4, which I've found to be remarkably stable when used as an Apache module. I've put together a Uniform Server package where I've replaced the 32bit versions of Apache/PHP/MySQL with 64 bit ones. Note that the MySQL version used in this package is the development release (5.6.5m8). I've left the 32 bit version of PHP in but renamed its directory to 'php32'. If the mod_fcgid module is loaded by apache, the 32bit binary in that directory is used (CGI). If mod_fcgid is not loaded, the 64bit version of PHP is loaded as an apache module. Check the Apache httpd.conf for some other minor changes (directories need 'ExecCGI' when mod_fcgid is used, for example). One thing I know for certain that still needs work is tweaking the MySQL config (my.ini). Here's a link to the package:

We've all seen that famously misspelled error message when attempting to install XAMPP on our 64 bit desktop Linux machines. I wonder how many people using XAMPP are still on 32 bit? I suppose enough to justify keeping it 32 bit. Speaking of which, this Kingston biscuit is falling to bits. Munch munch.

I would like to debug PHP in Eclipse PDT while it runs under an Apache server with a bit of MySQL thrown in. In order to do the remote debug one needs to configure PHP to use XDebug which is a standard cross-platform debugger that is used by a variety of languages to debug over the wire. It is based on DBGp, a common debugger protocol for languages and debugger UI communication.

After a lot of really boring reading in the usual forums and help web sites I find out that the php_xdebug.dll is not compiled correctly for the version of PHP I'm using. This is very strange because it was downloaded as a bundle so everything should be compatible with everything else, but it wasn't.

Microsoft Windows dictates an internal DLL binary format which coincidentally is released with a new version of Microsoft's Visual studio. This makes programs compiled with different versions of compiler incompatible with each other - thanks for that. It causes problems in every computer language that is compiled with a Microsoft compiler. PHP is just one of them. Python is another. If you compile Python under Visual Studio 9 you will have to recompile all the support modules with the same compiler. So not only do you have to care about whether it was compiled into 32 or 64 bit code but you also have to care about which compiler was used too.

The name of the XAMPP binary tells you which version of Visual 'C' was used to create the application suite. In my case I downloaded xampp-win32-1.8.2-0-VC9-installer.exe paying special note to the win32 and *VC9** in the file name. From the file name we can see that this is a windows 32 bit version compiled using Visual 'C' 9.

This only gives us some of the story. For the rest we need to run XAMPP and get it to tell us how it was compiled. In the document root E:\xampp\htdocs create a file called p.php and fill it with:Next open you browser and go to:

Zend Extension Build and PHP Extension Build have their compiler options although in this case the only important part of this is the TS bit. I think that in some builds of PHP the TS may not exist or it might be NTS instead.

Windows being what it is with locking files means that you have to stop Apache before copying the DLL in to the correct place which will slightly increase the downtime. This might work better as a tested upgrade on a production system where you don't want to touch the configuration files.

Most people choose this option because it gives you a better infrastructure for testing different versions as well as an easy rollback or upgrade path in case anything goes wrong. It also reminds you which version of XDebug you are using. The DLLs stay in place and you are only changing the configuration files. As a result there is no gap between the Apache restart.

After first successful installation on Linux Ubuntu, I trying reinstall it on other computer, and something getting wrong in step 3 of instructions provided by Bredy. I had the same problem first time, and then I replaced it from other code I found on Google.

Now it the same problem

Is it possible to post installation instruction on OpenEmr downloads, for Docker- Linux users. It will be very helpful for all users, who interesting in more advanced Openemr platform.

I struggled through trying to upgrade using the current newest Xampp and version 5.0.2 because I could not just upgrade my current installation due to a lower version of php. It seems in addition to some bugs like you mentioned such as overlapping code boxes on the fee sheet, that it went back to the problem of very slow performance under windows.(using windows10, I7 processor and 8gb ram) Unfortunately all the previous suggestions that seemed to help before did not seem to help with the updated xampp version.So I am stuck at this point because it takes too long to load a patient to make it workable in my office so far.

The Docker thing looks like a pretty big learning curve for us windows users. Does it solve the performance problem because it seems like it would add more overhead that way?

I built a server and tried the mint thing a while back and found it very difficult to get it to serve files correctly to the 6 windows work stations in my office. After struggling with it for awhile I converted back to xampp for windows. Xampp has been just fine since it is only running on a local wired network and I set all the suggested passwords which limits the security concerns. Frankly version 5.0.1 has worked fine for my needs in a small primary care office but it would be nice to keep up with the updates.

If the xampp option is going away however it would be nice to see some instructions on how to transfer all your data from 5.0.1 under windows xampp into a docker or VM and how you would set that up to run on a windows network. I am up to about 16 GB of data, so starting over without importing those files does not seem like an option.

I just finished today my project to transfer my 5.0.1 windows Xampp based data, to 5.0.2. platform in Linux Mint.

We also have small private clinic, with a office based network for 8 computers. Every time with EMR upgrade we had a lot of issues. We moved the server to Linux Mint this time and it is working very well on the server computer but all the other computers are running Windows 10 without conflicts. This is my suggestion for your as well.

If you doing new Open EMR installation on Linux, you not suppose to receive this message.

When you restoring your backup.tar data, you need to rename openemr folder to like openemr_old, and then start the process. Restore process will create new openemr file automatically. And then after finish the process, need to delete openemr_old.

Same, in time of upgrade process to 5.0.2. need to rename openemr folder to openemr_bk.

Here are the steps I used to to upgrad MySQL to MariaDB in XAMPP on Windows in about 5 minutes. After completing this process, MariaDB will look and work just like MySQL. You may even notice a performance increase in your website. No need to panic fellow developer, increased performance is perfectly normal and just one of the great benefits of MariaDB over MySQL.

IMPORTANT: Before you begin, always be sure to make a good backup. Do not do move instead of copy files in the instructions below as the original files may be required in order to back out and restore the original MySQL environment if it doesn't work out for you.

3a8082e126