OT ops i'm too agressive, i have to change my behaviour or my DS will not work another time
most of the BUG include human behaviour though u don't seem to think that ALL of the bug in general are formed from human behaviour, hardware parts and software rules What the team is supposed to do is to hack the codes to find those bug, isolate and delete its
What i have to do is to say to whom in the other forum ask what is the last stable kernel is to say that the last is 1.72ob15; ironically more stable than the 1.80
i'm sorry of my cheeky behaviour, i will change it when my DS obey to me
Joined: Wed Jan 24, 2007 12:34 pm Posts: 5408 Location: Has left the place ...
ok. I have a wifi access where i am. So to go further with the /SAVE directory theory. Windirt please check this process : When there is no /SAVE directory on the microSD card, and you launch a game, the ez5 freeze. A /SAVE directory is created but when i check (chkdsk x: /f) my microSD on my PC, i have this error :
Code:
Lien perdu en référence croisée au cluster 255. Orphelin tronqué. Convertir les liens perdus en fichiers (O/N) ?
Perhaps the freeze bug is linked to this error ? I will try the same test but i will create a /SAVE directory manually on the PC.
Edit : Ok no freeze when cheat window open (Oh well ! this save bug is not fixed) , but the ez5 freeze when i scroll down and then up. The cheat mode bug is still here.
Edit 2 : when i duplicate the game in root, the cheat mode freeze bug disappear for the one in the /JEUX directory (sorry for my bad english but i do my best)
Edit 2 : when i duplicate the game in root, the cheat mode freeze bug disappear for the one in the /JEUX directory (sorry for my bad english but i do my best)
yes, I tested with this condition, and the bug gone, that's why I repack the 1.80, maybe I'll pull down the 1.80.
OT ops i'm too agressive, i have to change my behaviour or my DS will not work another time
most of the BUG include human behaviour though u don't seem to think that ALL of the bug in general are formed from human behaviour, hardware parts and software rules What the team is supposed to do is to hack the codes to find those bug, isolate and delete its
What i have to do is to say to whom in the other forum ask what is the last stable kernel is to say that the last is 1.72ob15; ironically more stable than the 1.80
i'm sorry of my cheeky behaviour, i will change it when my DS obey to me
no, the user behaviour which I mean is not blame you. I mean the operation behaviour.
Like me , I perfer directly extract the file to microsd, that's why I still can't reproduce the bug. some user like use the copy and paste. so they encouter the bug. I do same and reproduced the bug successfully.
before this bug happen, there is no think about the copy behaviour in my test procedure. nobody will relate it with a bug. but I'll put it in my new test procedure.
Users browsing this forum: Google [Bot] and 2 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum