More testing
I’ve done some more testing on the new installation, which was a bit of a problem since all licenses had expired…But at some point, the system was started properly.
There are still a few issues, one of them that stylesheets are not loaded properly – or delayed. Sometimes, pages didn;t show up at all, or just partly. Adding images to pages was troublesome as well, the page in which the image was to be added didn’t show up at all. But WATCH didn’t give a hint on the problem, it all looked nice. So there is still some way to go before I’m satisfied….
Anyway, I downloaded the files for an update: both WASD and PHP, but I didn’t install them yet.
Another product I need to test in MySQL – I downloaded the latest version and installed it according instructions. And it all went smoothly (except for some minor error), the database was created, but after that, it was impossible to start the daemon: it expects some table to exist – the first has to do with locking and this table can be added once the database is started. But alas – the second error requesting a table to exist fails – and by that, the process aborts.
I have asked support of the forum.
It may have to do with SLL 1.4 – but that would lead to other errors…
It might also be a matter of the C-RTL, but it doesn’t explain the non-existence of required tables.
VMS 8.3 updates
The last updates date back to 18-Apr-2010 is it is time to get the latest ones. Including SSL 1.4 and two that are related to this: ENCRYPT and ACMELDAP, both are influenced by this update. Installing it would require a rebuild of the web server, and possibly MySQL, so it’s one to be postponed.
But before installing them, I have to make a backup of the system disk – and find opportunity to do the actual installation. And that hasn’t arrived, yet…. And for the rest of the weekend, I won’t be near the machine-room…
One update has been done, though. As I found that older quarantined and discarded messages weren’t visible after the update, Hunter Goatley of Process Software hopped in to state an error in a new feature which caused these old messages to become invisible. He supplied new images that do not contain the error – and after installing them as he instructed (and setting protection to W:RE to allow them to be run by the web server) the problem was gone. Great support to a non-paying customer. That’s what I like!
Something else was wrong as well, but that was not reproducible. But the workaround was running a rule-compiler, and the problem should have gone. We’ll see.