Oh hi. I found my 3-in-1 in the mail today, and I've spent the last few hours playing around with it, testing it's capabilities and so forth. Using an R4, I need a 3rd party application to write GBA ROMs to the 3-in-1. I've been using Rudolph's tool with moderate success, experimenting with interchanging saves and ROMs. I haven't done exhaustive tests, but it seems like for PSRAM and NOR, the ROM's .sav file is automatically written to the /GBA/SAVE directory. If so, under what circumstances is it imperative that the user uses the manual backup features of Rudolph's tool? Also, does the ROM's save type (EEPROM, Flash or SRAM) ever need to be taken into account? It worries me that the interface only ever refers to SRAM saves. Anyway, since this has practically become a blog (which I'm morally opposed to), I'll cut to the chase. Is Rudolph's Tool better than NDStation? I don't care about the "more integrated and unified" feel. Is either more/less reliable/fast/stable/prone to failure/etc? I have little understanding of NDStation, but I assume it creates a .nds container that integrates a GBA ROM, .sav file, a piece of code to write the memory each time and some header data. Is this accurate. Thanks for reading through that epic wall of text, and any insight into anything I mentioned is appreciated.