is the _DSMENU.DAT that was updated to 1.62 safe to use?? or should we stick to what gateway put together?
Somebody would have picked up on that being a part of the Gateway launcher's code. Whether it be a competing/clone team or tech-savvy individual user. The vast majority of reports about bricked consoles are coming from 3DSLink/R4i users, and we all know that their most recent firmware release was broken. Even their two releases prior to that may well have been ticking time bombs in the form of memory leaks, etc.It's starting to look that way to me too.
If it truly was a deliberate action to brick clone users' consoles, that's quite a low blow...
I'm curious to see what Normatt's response to Gateway will be.
No reports of bricking from that, only on 3DS mode carts. The blue card is DS mode.is the _DSMENU.DAT that was updated to 1.62 safe to use?? or should we stick to what gateway put together?
Assuming GW did this intentionally, it's not like letting someone else freely rip off their code would be any smarter a business move. These are piracy devices, I don't think "ethics" really have ground when Gateway wants to punish the "'so-called' competition", they didn't even force you to use the unofficially modified versions of their launchers originally designed for their hardware.If it truly was a deliberate action to brick clone users' consoles, that's quite a low blow...
No reports of bricking from that, only on 3DS mode carts. The blue card is DS mode.
It's entirely possible, but in so far as we know, the hardware architecture of the blue card indicates that it's only slightly modified from an R4 cart. Naturally Gateway isn't going to recommend you use R4's firmware updates on it, but I don't believe there's any chance that 1.62 will conflict with it.I know its a ds card im just wondering if we shouldn't alter something that wasn't done by gateway. I mean I understand the _dsmenu.dat file is a ds profile. I mean no one is telling anyone you have to use the updated dsmenu file I just figured that gateway didn't make it 1.62 for a reason
It's entirely possible, but in so far as we know, the hardware architecture of the blue card indicates that it's only slightly modified from an R4 cart. Naturally Gateway isn't going to recommend you use R4's firmware updates on it, but I don't believe there's any chance that 1.62 will conflict with it.
Your call. I understand the thought process that it's better to be safe with expensive hardware.I appreciate your input on the matter. I went ahead and went back to the _dsmenu.dat file that gateway put with its files and if they release a updated dsmenu file then ill use that. last thing I need is to brick my 3ds over a file that could or couldn't damage the system. I mean really we shouldn't be using the cards but what fun is it not
Your call. I understand the thought process that it's better to be safe with expensive hardware.
*sigh* My MicroSD got corrupted, I hope it's software related and not with the card itself (I bought it recently and I fear I could have been scamed). What happens is that I couldn't copy the NAND.bin file from the MicroSD to my computer (0x80070057) and also I can't paste anything on the MicroSD. I booted emuNAND again knowing this and everything went OK.
I'll try to reformat the card hoping this resolves the issue.
are you inserting the microsd card the card reader alone or putting in a sd card adapter? I know my wifes kids microsd cards were getting corrupt using the card reader for the microsd and I switched to using a sd card adapter and it seemed to work better. I also use the suggestion from http://gbatemp.net/threads/pokemon-white-2-not-working-on-new-r4i-3ds-gold-r4ids-cn-card.345099/ second post down formatting it exactly the way the suggest and never had a corrupt error problem worth a shot
Well I hope it was just a bug as opposed to something malicious from Gateway, but what about Normatt's region-free modification?Somebody would have picked up on that being a part of the Gateway launcher's code. Whether it be a competing/clone team or tech-savvy individual user. The vast majority of reports about bricked consoles are coming from 3DSLink/R4i users, and we all know that their most recent firmware release was broken. Even their two releases prior to that may well have been ticking time bombs in the form of memory leaks, etc.
I am under no illusion as to what these devices are intended for or the ethics of the type of people who design and profit from them are.It's not like letting someone else freely rip off their code would be any smarter a business move. These are piracy devices, I don't think "ethics" really have ground when Gateway wants to punish the "'so-called' competition", they didn't even force you to use the unofficially modified versions of their launchers built for their hardware.
What are people going to do, boycott Gateway and purchase an R4i/Link/Orange and brick their own 3DS just to prove a point? No, being aspiring pirates anyway, they'll go for the safest option that gives them the highest game compatibility.
And I sincerely doubt people working on homebrew would do anything significant in response to users of warez devices having their consoles bricked. It's not like they'd release a rom loader to spite Gateway or anything.
No reports that I've seen in relation to that patch and bricking. At the same time, my 3DS scene knowledge doesn't extend very far beyond this site. Seems like Gateway is just playing it safe, as I'm sure they haven't fully vetted that patch or any other launcher modifications for themselves yet.Well I hope it was just a bug as opposed to something malicious from Gateway, but what about Normatt's region-free modification?
It looks like it's a pretty simple patch that doesn't change much. Are there any actual reports of it causing bricking to occur as well, or is that just Gateway saying don't use it?
That's good. I hope this remains the case, as it seems (to me, at least) that this would point towards it just being a problem introduced by the R4i/3DSLink team.No reports that I've seen in relation to that patch and bricking.
At the same time, my 3DS scene knowledge doesn't extend very far beyond this site.
You're correct.There is no evidence about gw team bricking systems intentionally. Someone disassemble a decrypted gw launcher and show us all there was a time bomb hidden, please stop speculating and creating rumors until some proof is shown.
Also it is interesting that cloners didnt check this supposed bomb when copying, talk about incompetence