Now lets see... who the real noobs are...........
1. Do you guys exclude the g6lite drive from a/v scanning?
2. Do you have any crap like norton's security running in the background, taking snapshots of the g6lite drive?
3. Is there anything touching the g6lite drive besides the u-manager? if so that is probably why your card is corrupt.
How much spyware and crap do you guys have loaded on your pc? mine is clean as a whistle with 0 problems.
You said a few meaningful things I don't need to reply to, but the above: Noone that has posted in this thread has actually had corruption, so I don't know who you've posted it for. Also, a/v scan is a read-only operation (if configured right) and can never do anything to corrupt data. (Unless some kind of jackass force-unplugs his cart WHILE there's some scanning operation going on. But that's more likely just to crash the host computer and not corrupt the cart.)
Norton's security/security centres in general might do something, especially if program control is on and it tries to halt an operation pending on your input (such as ZoneAlarm). However, I doubt it...
From an engineer's point of view my best guess (alas, I'm not 100% positive) is that the error comes from erroneous writing of roms. E.g. some instruction/data in the cart gets scrambled (remember; no such thing as a perfect channel) and performs some undesirable operation that corrupts some of the data banks on the cart.
Hell, it could even be a faulty write that (due to, say a voltage surge from the extension cord some people are using) accidentaly writes game-data into the SRAM repository and thus fawks up all saves.
Fact is, nobody knows for sure why it is happening and that's why I posted my "guidelines". It's just a little safer way of burning your flash carts. I didn't ask you to follow them, I just made a suggestion.
So bottom-line is that if you don't want to follow my guidelines, fine, don't. Maybe you'll never experience corruption in your carts. Just don't be an ass/rude about it. Thanks.