17-Oct-2006

No E107...
because there really is something wrong in there. So that's be abandoned for the moment. Mark says I ran into one of the issues with PHP, hopefully someone at HP will pick it up.
Wordpress
however did install, but creating the database was another issue. The ones that were created before didn't work with this newer version, so I deleted them and created a new one. That is: creating a wp-config.php fila failes since the root directory seems unwriteble - but it is set to W:RWE, so HTTP$NOBODY would be able to write. No way....So I created the file manually according the manuals and created the database.
With some trouble, it does work - sort of. I got a number of messages that headers could not be resent and all of a sudden these were gone. Login did succeed - and one of the previous problems is gone: I can now see (and select) other themes, but running the admin script is still a bit of a wonder - it should run wp-admin/index.php ut it does not. Might be a default in WASD to be set.
Not 100% yet: There is some problem with a value in a select statement:

[Unknown column 'publish' in 'where clause']SELECT DISTINCT * FROM wp_posts WHERE 1=1 AND post_date_gmt <= '2006-10-17 18:35:59' AND (post_status = "publish") AND post_status != "attachment" GROUP BY wp_posts.ID ORDER BY post_date DESC LIMIT 0, 10
and the admin site has no theme loaded.

Well, something still needs to be examined.

Update
Found the cause: post_status is defined as
enum('publish', 'draft', 'private', 'static', 'object', 'attachment')
and that seems to be the trouble. Taking out the references to post_status and MySQL returns the data. Pass that to Jean-Francois Pieronne (who ported MySQL to VMS).

Anyway, it's a bit weird in the SQL statement to specify both:
(post_status = "publish")
and
post_status != "attachment"
DUH! if post_status equals "publish", it won't equal "attachement"...