as it has said; it was an unexpected error, try a fresh install (:, kidding, but it may work, try once more, if not someone will figure sth out, i ve always wondered why b2 did not have an external .sql to import yourself by default

Thanks for your reply. I tried the following:

-deleting all of the tables and trying the installer again - same error.
-deleting the db and re-creating it, then trying to run the installer - Same error.

Thanks,
marc

Try DROPPING all the tables in your brand-new-but-not-working database, then running only the query you pasted in your first post here.

CREATE TABLE evo_users (
user_ID int(11) unsigned NOT NULL auto_increment,
user_login varchar(20) NOT NULL,
user_pass CHAR(32) NOT NULL,
user_firstname varchar(50) NULL,
user_lastname varchar(50) NULL,
user_nickname varchar(50) NULL,
user_icq int(11) unsigned NULL,
user_email varchar(255) NOT NULL,
user_url varchar(255) NULL,
user_ip varchar(15) NULL,
user_domain varchar(200) NULL,
user_browser varchar(200) NULL,
dateYMDhour datetime NOT NULL DEFAULT '2000-01-01 00:00:00',
user_level int unsigned DEFAULT 0 NOT NULL,
user_aim varchar(50) NULL,
user_msn varchar(100) NULL,
user_yim varchar(50) NULL,
user_locale varchar(20) DEFAULT 'en-EU' NOT NULL,
user_idmode varchar(20) NOT NULL DEFAULT 'login',
user_allow_msgform TINYINT NOT NULL DEFAULT '1',
user_notify tinyint(1) NOT NULL default 1,
user_showonline tinyint(1) NOT NULL default 1,
user_grp_ID int(4) NOT NULL default 1,
user_validated TINYINT(1) NOT NULL DEFAULT 0,
PRIMARY KEY user_ID (user_ID),
UNIQUE user_login (user_login),
KEY user_grp_ID (user_grp_ID)
) 

This will tell us if for some reason your new server will simply never ever like this table, or if something else unknown is causing the blockage. IF you can make that table then (again) DROP it and get a brand new copy of the 242 package, unzip it, edit the conf/_basic_config.php file to suit your needs, and upload all the files again. Actually delete all the files from your server first! The idea is if you have a bonked up set of files then completely replacing them all the way back to the .zip package will take care of that issue.

Thanks for your help!

I dropped all of the tables, ran the sql statement and it created the table with no problems! I deleted everything, downloaded 2.4.2 again, and am uploading now. I will post my results.

Thanks again!

Hi Again, no, it still stops at the same point when I run via the installer. :-(

But I am getting a new errno now - Errcode: 28 - which means that MySQL is out of available disk space if I am correct....*groan* time to call the web host.

errno: 135 could mean that there is too much files in /tmp and so mysql can't create temporary file

Hi All - Thanks for all of your help. My hosting provider did something...and I was able to install and get it up and running!