DSmaps

  • Thread starter Thread starter Urza
  • Start date Start date
  • Views Views 8,241
  • Replies Replies 36
R4
1.14 I guess

Kingston JP 1 gb

Fat32

Still searhcing pc for back ups of my savesÂ
cry.gif

OK, thanks. I'm also on an R4 with 1.14, but my Sandisk 2 GB came pre-formatted with FAT16, and I just left it at that. I'll reformat and see if I can repro.

I feel your pain re the backups!
 
@dsmaps

May I make some suggestions?
- Better GUI (everyone loves a nice GUI
tongue.gif
)
- Touch screen navigation (for precision)
- The ability to download every single map available on Google Maps for on the road usage (a little ambitious but great to have)

All in all, a very good application that does what its supposed to do. It worked great and didnt corrupt my card. I'm using R4, firmware 1.14 with a Kingston 2GB card formatted to FAT16 with 64KB clusters.
 
It may be the single folder creation that screws it up. The same thing happened to me when DSReader created its own folder and corrupted my entire card.

A better approach might be to include the empty folder for people to copy to their card, or keep one dummy file inside the folder so that it gets included in the .zip file.
 
What about a small area? This would work great at work if it had an offline mode.

Edit: I'm talking about a 3200x3200 area
 
It's great!! much quicker than Treasure of Gaia and I didn't found any file corrupt.

I'm using...
R4 1.16
Kingston 2GB(J)
FAT32
with around 120+MB of free space
 
Thanks for the comments and suggestions everyone. The Future Plans page on the website is where I'm tracking everything that I intend to add, so that would be the best place to post suggestions.

@DanTheManMS The creation of the single folder in the root is what's causing the corruption problem - libfat seems to have some issue in this area. I've noticed for example that DSOrganize had similar problems prior to 3.1 and I'm investigating how they worked around it. They seem to use relative paths rather than absolute paths for one thing...
 
Yeah, this file system corruption can be a problem with any libfat homebrew that creates files. I'm not sure if including an empty file or folder in the download would solve the problem entirely because sometimes it seems to happen even when you're just saving new data to a file that already existed. That's a lot less common, though, so including all the needed files in the download is defintiely a good idea anyway.

However, everyone who uses homebrew should know that when this kind of corruption happens, it's not really a big problem. There has been no corruption of the actual data on the card, only the table of contents gets corrupted. So if you run Scandisk on the card, it will recover everything. The files and folders in the root will have dummy names, so you'll have to figure out their proper names, but all the other files and folders that were in subfolders from root will be totally recovered and named correctly.

It seems like I've posted this info a thousand times to a hundred different forums, but the word doesn't seem to be spreading. Everyone always just immediately formats their card when this happens and so they lose all their saves.
 
It's great!! much quicker than Treasure of Gaia and I didn't found any file corrupt.

I'm using...
R4 1.16
Kingston 2GB(J)
FAT32
with around 120+MB of free space
Thanks, but if you are using FAT32, I'd bet anything that you have been corrupted - it just hasn't bitten you yet! To check, pop the microSD card into a PC and run a chkdsk on it from the command line. If the first line says "FAT32" rather than "FAT" then it should report "Errors with . and/or .." on the DSMAPS folder further down. To fix, run chkdsk again with the /F switch.

See my latest posting on the website for more details.
 
I really hope it will come to a point where it will allow us to download maps to the card for using them on the road.

BTW: Urza... this has been bothering me for quite a while... your Avatar is kinda weird... Mind changing it ? It really drives me crazy everytime I see it. Sorry...


I strongly agree with you on this! BTW: Urza... this has been bothering me for quite a while... your Avatar is kinda weird... Mind changing it ? It really drives me crazy everytime I see it. Sorry...
 
It's great!! much quicker than Treasure of Gaia and I didn't found any file corrupt.

I'm using...
R4 1.16
Kingston 2GB(J)
FAT32
with around 120+MB of free space

Thanks, but if you are using FAT32, I'd bet anything that you have been corrupted - it just hasn't bitten you yet! To check, pop the microSD card into a PC and run a chkdsk on it from the command line. If the first line says "FAT32" rather than "FAT" then it should report "Errors with . and/or .." on the DSMAPS folder further down. To fix, run chkdsk again with the /F switch.

See my latest posting on the website for more details.

What's this actually do?
I try and it said error in many of my homrbrew&game (DSmap/Pocketphisic/GBA Explorer folder/Jet impulse/etc.)
 
What's this actually do?
I try and it said error in many of my homrbrew&game (DSmap/Pocketphisic/GBA Explorer folder/Jet impulse/etc.)
When run without switches, chkdsk checks the logical integrity of the file system. In other words, it recursively checks that all directory entries make sense and that there is consistency between directory entries and the file allocation table (the thing that gives FAT its name!). Run with the "/F" switch, it attempts to restore the consistency of the file system if problems are detected. There are also various other switches that make it do tests on the physical integrity of the disk.

I've found and fixed a bug in libfat (the library used by almost all homebrew apps to interact with the file system) and notified the guy responsible for it. For more details, see the latest posting on www.dsmaps.com. You can also download the latest 0.2.1a service release of DSmaps, which includes the fix for the libfat bug.
 

Site & Scene News

Popular threads in this forum