hi
i got 5 of the dstt's and when i put the roms and latest firmware on the micro sd card (version 1.07)
is creates the sav file then just freezes on the loading
the only way i can get it going again is to format the sd card and put the roms on again
this happens all the time when i put another game on after it works ok
the only way i can get it to work better is to use 2gb card and only put 20 roms on
i usualy fill the card with roms and leave 30 to 40 mb free space for saves(512kb each)
i tryed kingstone integeral and peek micro sd's

any one having the same problems
is there a firmware update going to fix this?

 

all 5 are the same
i did have 10 but took some back
the kingston micros are from a good computer shop
also tryed 3 diferent types micro sd's
some times the odd micro sd would work ok first off
then if you put some different games on it would just cause it all to start freezing
there are lots of posts with the same problem
google (dstt games wont load)
they blame it on the sd card fragmentation
there is even a youtube clip showing a crappy so called fix

the dstt makers need to get a fix out soon or they will be going out of buisness

 

umm, you are suspicious.

your post, 5 cards all faulty, your nickname, flaming, not searching for answer and just blamin' ..., hope I'm wrong.

 

i chose the name as im pissed off with these things
its not just me theres loads of posts about this freezing on loading

also ive used r4's with the same computer and no problems
and m3 simplys

why dont they get effected with defragmentation?

surly some of you are having the same problems

here is the problem im having 43 seconds into the youtube clip
http://uk.youtube.com/watch?v=VUfFyr9Q0QA

 

Try using FAT16, it's faster and better.

Some reading: http://www.digit-life.com/articles/ntfs/index3.html

 

I have 2 NDSTTs ordered at the same time and have the same problem, but so far only on one of them.
I have now watched the Youtube video, and that is actually what I have been doing to fix the one I have that does this.
I don't think it is file fragmentation, as you would be able to copy all the files off, reformat and copy back on.
This does not work, you actually have to recopy the files from original source (as also shown in YouTube video).
I think it is more likely data corruption than fragmentation myself.
I have both Sandisk and Kingston 1G cards, and they both do it on one of them.
However, I have noticed that if the kids just load a game and play it for hours on end it seems fine, it is more likely to happen when opening a game, powering off, opening another game etc.
Also I noticed that the date on one of the TTMENU files changes (the .SYS file from memory) - not sure if that is normal, only noticed yesterday and haven't looked at the other to check.
(p.s. the one that hasn't played up yet usually gets used by a kid that just plays one game for hours, so that could be why it hasn't failed)

Anyway, would be interesting for those who haven't seen a problem to (back up the files first) start a game, shut down, power up, start a game multiple times and see if it also does that lock up on loading thing.

 

My TTDS (NeoFlash Version) and DSTT (DealExtreme) Both work Flawless

I've written miltiple times and rebooted alot, i've been using it since NeoFlash sendend me the sample

I swap my TF (FAT32 Formatted) between the Neoflash TTDS and DealExtreme DSTT, no problem whatsoever.


I noted and posted about a problem where you get an error, if the USRCHEAT.DAT is missing or you use by accident an Encrypted usrcheat.dat you can get 2 white screens or an error txt (dunno just what it is saying anymore)

 

Thanks Bri,
I was wondering if that could be a factor.

 

the ones i kept taking the games and the firmware on and off a few times
seem to have kept working now
but why doesnt the r4 or m3 simply suffer with this ?
they are too much headache for me

 

DSTTSTINKYCARD:
Did you try creating the sav files yourself instead of just leaving some free space and letting the OS do it? Even with R4 I always did that, as writing *new* files hasn't exactly ever been 100% reliable in any of the cards I have tried, while writing data inside of an existing files boundaries always seems to work just fine.

I for one would hate to stuff a bunch of files on a card without saves, only to find out after some hours playing on xx game that when I go to try a different one my card gets corrupted. And yeah, I have had that happen - even once on an R4.