dmalloc

Thank you, excellent answers! That works like a charm. You might want to consider enabling something like this in a plugin or making specific hooks for it, as this is a very common feature someone comming from type-setting will request ??

Just to follow up on my own post. I also see things like this:

<div class="post-content">
<p><img src="*" width="179" height="300" alt="" title="" /> My girl is

But even then the wraparound does not happen. This is something that I have seen with many themes, I wonder why?

and on we go with the odd effects.
The original error code:
SQL/DB Error:
[Specified key was too long. Max key length is 500]
ALTER TABLE wp_posts ADD INDEX ( post_name )
SQL/DB Error:
[Specified key was too long. Max key length is 500]
ALTER TABLE wp_categories ADD INDEX ( category_nicename )
The one I used which works:
ALTER TABLE wp_posts ADD INDEX (post_name(166));
ALTER TABLE wp_categories ADD INDEX (category_nicename(166));
I just double checked. With the steps I mentioned here, the WP install now works without any flaws. The options show in the drop downs now.

Ok. Using this statement works:
CREATE TABLE wp_optionvalues ( option_id int(11) NOT NULL, optionvalue tinytext, optionvalue_desc varchar(255), optionvalue_max int(11), optionvalue_min int(11), optionvalue_seq int(11), UNIQUE (option_id, optionvalue(85)), INDEX (option_id, optionvalue_seq) );
Apparenlty the optionvalue(85) vs optionvalue(255) triggers the error.

Hello ?? Thank you for you answers but the blog does not work correctly. All drop down fileds which should have some preset values in the Options area are empty. Sometimes errors pop open when I try to set an option, possibly indicating that the table is missing while trying to read the value.