I'm getting a bit confused/frustrated here.

I run a few bots and they all run fine overall.  I ran into an issue a while back with the tower_attack table saying it was full (not sure whoever decided to make that an MyISAM instead of InnoDB was thinking, but whatever) so I had to tweak it's max size.  I'm now setting up a brand new bot for someone and I get this same message with the botname_settings table on creation.  At first I had it sharing a DB with another bot so I could share whois info and such so I even tried moving it to its own table to see if that made a difference but it didn't.  I've checked the HDD itself thinking maybe I had ran out of space but that isn't it (have gigs of available space on there) so I'm now sort of at a loss as to what the heck (the tweak I did before dosen't work, and actually wouldn't since it is an InnoDB table, not a MyISAM).

Any ideas?

The only way I can see an issue is if the user is using FAT32. Even then, 2gb or 4gb is rather large for MySQL tables... All my org bots weigh in at 24mb, even Campalot is only 67mb of data.

Seems like there might be something else going on on the user's system...like a full (or near full?) hard drive?

MyISAM is the default storage engine for MySQL. The Windows installer howerver sets the default to InnoDB in the config file. I haven't been able to find any reason why this change was made on Windows.

Ok, I got this one fixed... but the fix is really odd.

I changed the engine on that table from Innnodb to MyISAM and then did the ALTER TABLE botname_settings MAX_ROWS=1000000000
part of that article (which is the same one I was following before actually) and suddenly all is fine with the world.  No freaking clue why my server suddenly hates InnoDB!!