Well, like others have said, it's not the game, it's the memory card. Something is causing it to fail the check that tells the gamecube that the card's okay. It's possible that it really does have corrupt information, in which case you'd have to reinitialize the card (thus erasing any and all save data on it) to return it to normal but there's a chance that's not what's happening to you.
I've found that Memory cards are just like old video game cartridges. if there's a little dust inside of them, the console won't read the data that's on them. Now if you have an SNES (or any other form of game console that reads cartridges), you'll know what I'll tell you to do next:
1. Swallow all of your spit so that you'll have a dry mouth. Moisture is bad for electronics.
2. Take the memory card out of the gamecube. Make sure that the gamecube's off before you do this.
3. Gently (but not too Gently) blow inside of the cavity with the connectors, from side to side.
4. Put the card back into the gamecube and continue with normal operation.
Now if this doesn't work the first time, you may have to repeat the process. Normally you'll have to try this 6-7 times, maybe more or maybe less. What this does is knock the dust loose so that the gamecube can properly read the card. Now I might like to say that this doesn't always work. However, considering the amount of time that good save files take to make, I think it's at least worth a shot.
Then there's also the possibility that the memory card reader has somehow gotten some dust in it. You'll want to try and blow that out in the same manner as you did with the card itself. Just remember to push in the dust covers while doing this because it'll be worthless to blow on them.
Now, if that doesn't work, then you'll have to reinitialize the card. I think that the gamecube will prompt this to you automatically if it thinks the save data is corrupt. It's been a while since I had this happen to me last so I don't remember. It'll erase all of the data on the card in an attempt to reset it back to normal.
If that doesn't get it working, then your card is a flimsy piece of garbage. Throw it away and get a new one. Preferably one under the Nintendo brand name because they'll be the most reliable ones seeing as how they're the makers of the Gamecube. While you're at it, you might want to buy two so that you can backup your data just incase something like this happens again. Afterall, they are electronic devices so failures like this are bound to happen eventually. Also, never touch the memory card while the power to the cube is on and never turn off the cube while it's saving. Those are two sure fire ways to corrupt your data and as you have recently found out, that isn't a good thing.
I hope that the info I gave you helps. It's save me many a time with all sorts of gaming related devices.
Oh and before I leave:
Quote:
Originally Posted by crash26821
All I have to say is, It's a gamecube what do you expect. The controllers are always spacing out and making the icons move by itself. That things all beat up...
It sounds like your controller's not set in nuterual mode. Just put down and pull out your controller and put it back into the 'cube when things like that start to happen. Given that the joysticks and buttons are all in their default positions while doing this, everything should work just fine. You see, while turning it on, the gamecube assumes whatever positions the joysticks are in is the direction they're being pushed when left alone. So if your joysticks are out of synch when turning the gamecube on, then the gamecube will think you're pushing them even while you're not. The same thing goes for the R/L buttons too actually. Pulling out the controller and putting it back in restarts that process. There's also a button combination that you can press to do the same thing but I forgot what it was =-/ . I'm assuming that the springs inside of the controller are okay, right? The joysticks aren't limp or stuckish feeling are they?
Well, my gamecube is always in perfect working order, unless there has been some form of user error and belive me, I don't keep it in an ideal state. That's why I'm able to give you both advice right now :D .
