Help moving phpBB database, bigdump - Prob with Charset or Engine?

I'm trying to help out someone who is moving a phpBB to a new host using BigDump. The new host has mySQL version 4.0.24. Not sure what the old host had.

They are getting this error:

BigDump: Staggered MySQL Dump Importer ver. 0.24b
Processing file: cessna_bb.sql
Starting at the line: 1

Error at the line 36: ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;

Query: CREATE TABLE IF NOT EXISTS `address_book` ( `address_book_id` int(11) NOT NULL auto_increment, `customers_id` int(11) NOT NULL default '0', `entry_gender` char(1) NOT NULL default '', `entry_company` varchar(32) default NULL, `entry_firstname` varchar(32) NOT NULL default '', `entry_lastname` varchar(32) NOT NULL default '', `entry_street_address` varchar(64) NOT NULL default '', `entry_suburb` varchar(32) default NULL, `entry_postcode` varchar(10) NOT NULL default '', `entry_city` varchar(32) NOT NULL default '', `entry_state` varchar(32) default NULL, `entry_country_id` int(11) NOT NULL default '0', `entry_zone_id` int(11) NOT NULL default '0', PRIMARY KEY (`address_book_id`), KEY `idx_address_book_customers_id` (`customers_id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;

MySQL: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'DEFAULT CHARSET=latin1 AUTO_INCREMENT=2' at line 17
Stopped on error
​

Any suggestions? Is it a problem with versions of mySQL or something else?
Thanks for any help.

 

The error is this:

ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;

Code (markup):

You will need to change every ocfurace of that string pattern with:

ENGINE=MyISAM;

Code (markup):

When I had a large database like that, I just did a regex replace using php and filter out that and save my new dump file. You can also do that with notepad++ or any advanced plain text editor.

 

There is a memory limit that stops the process halfway with bigdump. An ideal approach for the move would be to let your host handle the database restoration.