|
From: Bernard B. <ber...@gm...> - 2025-01-06 22:05:54
|
Dear all, First of all, I would like to wish you all a happy new year: success, health and peace, despite the appalling international situation... I've spent many days (and nights) fixing problems that have arisen following reports from a new user. I hadn't checked the installation and operation in MacOS carefully enough, feeling confident because the console and its interface were developed on my Mac with the latest version of the system. Part of the problem is that I am using MAMP PRO, which behaves differently to MAMP (free) and XAMPP. So when problems were reported, I checked installations on different Macs and Apache servers. MAMP and XAMPP run as different identities in MacOS. While MAMP uses your personal identity (by default), XAMPP uses "daemon". The user/group parameters of the "bolprocessor" folder (and all its contents) must therefore be different for these Apache servers, i.e: daemon:admin for XAMPP <user_id>:admin for MAMP So I modified the installer to detect the presence of XAMPP and change the parameters accordingly. I then installed MAMP (free) on one Mac and XAMPP on another Mac (which also runs MAMP PRO). There were three surprises: 1) MAMP (free) on MacOS keeps the time limit at 30 seconds, even when the PHP script tries to increase it. This is a surprise as there is no such limit on Windows. The result is that small projects with short execution times work fine, but larger ones (such as "-da.La_Campanella") end up with a "System error #500". There seems to be no way to fix this except by upgrading to the commercial MAMP PRO. 2) XAMPP works fine, but getting it to start Apache at boot time is not satisfactory. There are scripts available (at https://github.com/erwinagpasa/Launching-XAMPP-at-OSX-startup) that will automatically start Apache, but if real-time MIDI is used, MIDIClientCreate() returns an error. The only way is to run "manager-osx.app" and start (or restart) Apache manually. I've spent a whole day trying to restart Apache automatically in the console, but it never works because the restart command has to be called from "root". I may find a solution in the next few days, but until then the easiest way is to find "manager-osx.app" (in XAMPP/xamppfiles) and add it to the login items of the general settings of your MacOS system. 3) Since I'm running PHP version 7.4 on my MAMP PRO server, I hadn't noticed that PHP higher than 8.1.0 changed the parameters of some functions used for graphics. So the images were blank! I fixed this in the interface. All these changes are announced on the pages: https://bolprocessor.org/quick-install-macos/ https://github.com/bolprocessor/bolprocessor/blob/graphics-for-BP3/BP3-changes.txt Regarding Windows, I found out that the "BolProcessorInstaller.exe" works fine on my machine only because it was created on the same machine... This means that other machines will send a warning that it is from an "unknown author" and even trash it as "containing a virus"! This means that it needs to be certified in the same way as the MacOS installer. I started this process, which is supposed to be free, but for which I paid more than 120 euros for a "cryptographic card" sent from Germany (https://shop.certum.eu). :-( Wait and see... Bernard Bel |
