Search

[The_Legend]

Hello there!

I've seen that the problem behind the problem with NDS Lite flashing is that people incidently push something other than the SL1, causing the system to turn off. a recomendation is to check is shorting the SL1 during a normal game turns off the system. but there's a problem in this method: how would I know that I'm really shorting the SL1? I could not be shorting the SL1 properly, then the system doesn't goes off, and I thing everything is fine, and when I get to the real thing, I could get a really expensive paper weight...

so, what I suggest for developer's to do is a tool that would just say if the SL1 is shortted or not. with this tool, we could know if the DS Lite can be flashed or not, and even better, if we end up turning the dawn thing off by shorting the SL1, we could try to make something different, to see if it gets shorted and continues on. I don't know if it's possible, but I guess it is and would make flashing the DS Lite much safier. I would do it myself, but I just don't know how to get the state of the SL1... (I only program to the DS using PA_Lib)

what do you thing of this idea?

[darkuni]

I mentioned this to Loopy - a "test mode" that does the WHOLE flashing process, but doesn't commit the code.  That way you can do some 'dry runs'.

I never heard back from him, though.

[The_Legend]

no one nows how to do this? come on!