I know, but right now I'm fully InnoDB and don't have suitable work for Archive or MyISAM. I just had quite a time with MyISAM on one heavy loaded site with tons of reads and writes with a few extremely hot tables (50/50 reads/writes) peaking at 1500 SQL queries/sec. MyISAM broke every few days and I had to do optimize with repair 2 times a day to keep it working - still got some instances of corruption to handle at peak time. So I invested time into converting everything into InnoDB and some query rewriting for it's specifics - never had a DB issue related to data corruption since for 4 years now.
If someone doesn't want to stick with the InnoDB - he should look at the MariaDB - the successor of MyISAM. Personally never had a chance to work with it, but it's redesigned to be fault-resistant and doesn't corrupt data randomly like MyISAM can - at least people never complained about it.