I am knee deep in the hacking docs right now so I have no time for actually making this, this is just a feeler post to see what people think. Cracker and I were having a conversation whereupon the idea of a kind of virtual file system for the DS appeared. I am sure most of you reading are well aware of the file system for the DS and how nice it is for hacking (no space worries, no need to trace the start of the file outside of stuff like NARC files and a few exceptions which again is simple enough). My main reason is for tracing. For those not aware the GBA had the rom mapped to the memory (08000000 and 09000000 with mirrors at different wait states), this means you can find the text in a game (in the actual memory by whatever method you like) and then look to see where that data was sourced from (often the rom itself or the section it was decompressed to (meaning you just repeat that step with the new memory section)). Other uses include the potential for a bit of on the fly* editing (or at least dodging the need for a rebuild) and corruption (it is simpler than tracing in some cases). The DS having a file system means tracing is not quite as easy as it once was (in fact is is nigh on impossible). *The emulators acting like a DS you may end up editing the file too late and the original data is loaded (something that could hopefully be rectified with a collection of save states) and editing the size of the files is sure to cause headaches as the file table is usually loaded at startup and used from there onwards. Now I have a whole bunch of tools for video that effectively do just this (and you probably are all familiar with the likes of daemon tools: DS files are not overly different to isos) and are thus able to trick most programs into believing a video is in a given format (usually avi) which would be doubly nice as it means any emulator/other tool could use it. So discussion, worth attempting? any pitfalls you can see? DS nitrorom file system specs: http://nocash.emubase.de/gbatek.htm#dscart...roromfilesystem ndstool is open source too. It might also be able to expand this to read individual files but that would likely require linking it more directly to an emulator unless you wish to fiddle with grabbing memory reads with the OS.