So technically there's no way to get rid of the problem other than avoid it and hope a ROM comes out later that will work.QUOTE said:Recently I saw a post on the DSLinker forum that was talking about the LASTSAVE.sdb ( kudos to whoever told me about this on the DSLinker forum, I wish I knew who posted it ) that made me realize that there is a LOT easier way to fix this.
First of all, if you don't have a "Games" folder, make one now, as it will be much much easier to diagnose problems. Just make a folder called "Games" in the root directory, and put all of your .nds and .sav files in there.
Now, start your DSLinker in USB mode, and look for the file with multiple copies of .sav
Delete all of the .sav files from the Games directory, and the ROM, it's bad. As far as I know, there is no way to fix it.
Now go into your DSYSTEM directory and delete the LASTSAVE.sdb and restart the DSLinker.
I have Stable2.54 running on my N-card (bought 3 months ago) and this problem with "File Write Error" occured 3 times so far. Today was the last time.sidneyyoung said:I have only had an N-card a few days but i have run into this error twice already on only 20 random roms.
On those games that 'file write error' I have been using a sc-slot2 save file for that game and it seems to work so far, but i haven't fully tested it.
example.. I got Zelda PH set to 4mbit flash and used a SC-Slot2 generated save file, hopefully it wil hold up.... /crosses fingers
I did try setting it to 4mb flash set in the menu and let the n-card create the save file as suggested in the FAQ thread, but after a couple of saves the write-error turned up again.. i hope new software comes out to fix this issue... the other rom that played up was Juice2, again i used a sc-slot2 save file and set the save to eeprom64kb, and again so far seems ok.