lifesavers2

I don't see why MediaFire fails for you, but the only other option would be the Spanish link. The file is too large to be attached to this post... But I can assure you that there's no virus in the program; I've scanned it with three AVs, if that's what you're worried about. If it's just blocking it, though, I'd temporarily disable it.

That just so happens to have been answered in post #8... ;D

Well, the way Pokemon names and OTs are handled is based on the sendpkm script, so any handling of alternate character sets is pretty much done by that. I'm not really advanced enough with Python to help you with that, sorry. It looks like DeSmuMe is your only option... But if it's only names missing, you can always add them back after processing, using PokeGen or PokeSav.

The program I use (which appears to be the only one available) is Enciclopedia Pokemon (yes, it is misspelled). I believe you can find the English file here. It may be an outdated version, but it's the only one I could find in English. The project page (in Spanish) can be found here. Edit: Oh, yeah, meant to say there's no Mac version, but, considering it's a single executable file, I say it's a 99/100 chance it'll run under a compatibility shell.

That's... certainly interesting. I have no idea why it would do that. What program are you using to view the files? If you're using PokeGen and it's set to 5th gen, it'll show a bit of wierd stuff.

Well, I refined and specialized the script because I just saved my first Pokemon game's .sav with a Multiboot cable, so it's much more batch-conversion friendly. It still can't process multiple files at once, though (because I still suck at Python). It's such a change, I decided that it deserved its own thread. You can find it here.

A while ago I modified Infinite Recursion's IR-GTS script to simply run its GBAtoNDS fuction to batch-convert .3gpkm files to .pkm files so I could transfer my mobile phone's Ruby ROM Pokemon to my Diamond ROM and then eventually to my Black 2 game cart. Someone sent me a PM not too long ago asking for it, so I'll post it here for everyone to use, since to my knowledge there is no program that can do this other than IR-GTS (and it takes about five minutes per Pokemon). Keep in mind I made this for personal use, and it may not be amazing in terms of integrity, so check your files with PokeCheck or something similar. It does have a tendency to spew random trash bytes everywhere, so I'd recommend running them through Trashbytes.exe if you can still find a copy. http://www.mediafire.com/?aqnt8nob93cqtci I've just begun splashing around with Python, so if anyone would like to give advice or critiques, I'd like that.

If you're still interested (it's been, what, four months?) I had modified the IR-GTS script to invoke the save function before it sends. I used it a bit, but the integrity of the Pokemon made with IR-GTS (And especially the little edit I made, for whatever reason) seems questionable, so I stopped. The name and hold item seems corrupted most times, amongst other things that occasionally get flipped. I would definitely check it with PokeGen/Check/whatever. But you could try it if you'd like. Just replace sendpkm.py in IR-GTS\src with the attached file and delete the corresponding .pyc file It only saves if it's a .3gpkm. EDIT: False alarm. There were some Pal Park trash bytes in some places, so I read it a bit wrong, but it seems every Pokemon has nearly the exact same data as before it was transferred. (Nearly, meaning IR-GTS treats every .3gpkm as it was from Emerald, regardless of its actual origin, amongst other lazy things) sendpkm..zip

*** Important for anyone attempting this! I hate to bump a thread, but it's necessary and I can't believe that no one's noticed it over these years. This is a great guide, don't get me wrong, but there is one flaw: it's incorrect. Your pinout is reversed. The view from the link cable is actually the view from the console connector. I initially tried it by this guide to no avail, but once I realized the pinout was fishy and used the one directly from the No$GBA readme it worked like a charm. The correct pinout, slightly modified from above, is as follows: