MySQL cannot start the service, MySQL is stuck, InnoDB 'registry as a storage engine

Keyword: MySQL cannot start the service, MySQL is stuck, InnoDB 'registry as a storage engine failed. Unknown/unsupported table Type: InnoDB.
A few days ago, when I started MySQL, I suddenly reported a 1067 system error and failed to start.
At that time, the Registry was reinstalled, cleared, and restarted, but there was no way to start it.
It is always the last step in the Post-installation configuration to start the service. It does not respond for half a day.
After two or three hours, I suddenly remembered that I should check the log,
110223 15:58:08 [note] plugin 'federated 'is disabled.
110223 15:58:08 InnoDB: initializing buffer pool, size = 17.0 m
110223 15:58:08 InnoDB: Completed initialization of Buffer Pool
InnoDB: no valid checkpoint found.
InnoDB: If this error appears when you are creating an InnoDB database,
InnoDB: the problem may be that during an earlier attempt you managed
InnoDB: to create the InnoDB data files, but log file creation failed.
InnoDB: if that is the case, please refer
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/error-creating-innodb.html
110223 15:58:08 [Error] plugin 'innodb' init function returned error.
110223 15:58:08 [Error] plugin 'innodb' registry as a storage engine failed.
110223 15:58:08 [Error] Unknown/unsupported table Type: InnoDB
110223 15:58:08 [Error] aborting
The error message returned when the InnoDB initialization fails and the InnoDB type is unknown.
Google, open the my. ini file, and change default-storage-engine = InnoDB to default-storage-engine = myism.
Started successfully. However, the InnoDB engine cannot be found during table creation.
But I thought, I can't keep it like this, so InnoDB won't work anymore. with Google, it's mainly caused by incorrect InnoDB log size.
Innodb_buffer_pool_size = 512 m
Innodb_log_file_size = 128 m
Increase the preceding parameters, delete the ibdata1, ib_logfile0, and ib_logfile1 files, and then restart the service.
If the problem persists, add a path like tmpdir = "USR/tmp" to the my. ini file, because InnoDB also needs a temporary file cache.
Another problem is that the password is correct, but the GUI tool cannot log on. You can first configure the program to change the password, and then log on to the command line to refresh the permission. Flush privilege.
Record it for your reference only.