You are not logged in.
Pages: 1
Well, then, I'm sorry to report that long paths still don't work as of desmume revision 3766 (compiled it 4 hours after your 3766 commit)
as you can see there
Or am I doing something wrong ?
to launch the newly built desmume from svn, I'm using this command :
E:\Coding\Tools\DeSmuME_dev.exe --cflash-path=E:\Coding\Ankinds\Release\ E:\Coding\Ankinds\Release\Anki.nds
btw, it's really nice that desmume now automatically patches homebrew roms with the MPCF dldi. Thanks for that too.
1. maybee I didn't identify correctly where my problem was coming from : turning the long file names into short ones solved the problem but maybee it wasn't related to desmume (I might have been using the official 0.96 release, would it make a difference ? )
I'll investigate the matter further and try to build a simple test case if desmume is at fault.
2. Ok, I'll cope with it.
2a will be a very nice addition in a couple of months and don't bother with 2b.
Better spend your time and energy on another place (especially if 2a is coming).
Just out of curiosity (I'm a noob in emulation/desmume internals, so bear with my stupidity ^^;),
At the moment, is there a way for desmume to know if the rom has tried to write to the "emulated fat files" that you maintain somewhere in memory ? And which file has been written to ?
If both answer are yes, maybee writting the file to the directory could be done by pausing emulation, writting the dirty emulated file to disk and rescanning the directory. But I guess that it would be slow.
And last but not least : I loooooooooove you and desmume.
Since I have managed to make libfat/nitrofs work in desmume, development speed has considerably increased (how I hated testing on the ds by removing putting in the sd card and the flashcart).
Many many thanks to the desmumle team.
I compiled r3766 (I needed write support) and tested my app with it.
It works great so far (good work ! And just when I needed this).
I have a few questions :
1) Is there a way to make desmume use long names instead/in complement of 8.3 filenames
(like having a hashmap that stores the long name and associates it with the 8.3 name) ?
It woul allow testing/developping my app further (it works in collaboration with a window app, so I don't really have the choice for the filenames)
2) Is there a way to make desmume write the files to the windows directory (I'm using the "path to repository" option) ?
I ported sqlite3 to the ds and it would be extremely usefull for testing/debugging purposes
3) to use googletest in my nintendo ds app inside devmume I hacked a previous desmume version :
My apps poke information at some point in memory and desmume listens/peek to these places.
when it finds relevant information there, it stops emulation, write some files on disk and exits.
Could there be a command line option, say "-exitwithnds" that tells desmume to exit when the rom exits and to return the error return code of the rom ?
Pages: 1