And "how do I install cfw on 10.4???" and "why won't gateway/pasta/ntr/rxtools launch on 10.4??"welp, GBAtemp needs to prepare for the inevitable slew of topics like "I softbricked with KTM, booted into recovery and updated to 10.4, am I screwed?"![]()
And "how do I install cfw on 10.4???" and "why won't gateway/pasta/ntr/rxtools launch on 10.4??"welp, GBAtemp needs to prepare for the inevitable slew of topics like "I softbricked with KTM, booted into recovery and updated to 10.4, am I screwed?"![]()
https://twitter.com/JustPingo/status/686331797731446784
What kind of people would overwork a programmer for some release that one does not get paid for all the time, and cursing him for anything wrong one did?
Are you saying this is expected behaviour in the 3ds modding scene? I've never heard of any respected devs doing this. In fact I've never heard of any other devs doing this (with the exception of hykem but I don't know anything about the Wii U scene so can't judge).
Not just the psp. Until recently the whole point of cracking a system was to enable piracy, then homebrew came second. The original playstation started with discswapping, rom dumpers evolved into flash carts, he'll even the 360 from not long ago got its start with fw flashing the disc drive to enable piracy. Funny that all those systems flurished too. I think the 360 would have tanked if not for piracy, given the issues and set backs it had with red ring at release. But people don't want to hear that shit. They believe companies won't make games if there is piracy, like they're gunna give up millions of dollars worldwide on console and software sales.Actually, something just like this happened back in the PSP days with a couple devs working on a new CFW. Their story was exactly the same, too. "Since everyone's so impatient, we quit. Bawww." It's nothing new. New generations of devs try to follow in the steps of older ones just for notoriety, and then drop out blaming the community. Though my favorite kind of dev is the "we have this thing everyone wants but we're not going to enable piracy" asshole. It's that kind of self righteous bullshit that kills off a scene, not piracy. When other devs see others saying that, they lose ambition to progress, thus resulting in the decline of new homebrew and even the scene itself. The PSP was full of piracy, yet the homebrew lived on, with some amazing things getting recreated there at the end (like CS 1.6).
And "how do I install cfw on 10.4???" and "why won't gateway/pasta/ntr/rxtools launch on 10.4??"
I mean, simply checking what memory range is mapping to userspace could fix memchunkhax2. Also there's GW claiming 10.3 kernel support.
Even simpler, load the memchunkhdr's next pointer before mapping the page to userland (thus removing the race condition). And I think GW is working on its own implementation of mch2.
I don't think it would require much work: you just need to store the value of mch_hdr->next in a local variable; that's like, one or two lines.
He claimed that it was more safer than sysupdater and told people to wait. He basically instilled fear to people's hearts that sysupdater isn't safe and led them to believe a better downgrader will be released. The scary thing is, there are still people out there waiting for his KTM even after 10.4
So you're basically saying his build destroyed the purpose of KTM (which, at the time, promises better stability)? If so, then the right thing to do then was to inform the public that KTM just hash checks the files to prevent hard bricks.The thing is that at that time sysUpdater actually didn't work. And then after TuxSH's build I had a completely objective point of view: use it if you feel like you can.
So you're basically saying his build destroyed the purpose of KTM (which, at the time, promises better stability)? If so, then the right thing to do then was to inform the public that KTM just hash checks the files to prevent hard bricks.
So if you haven't informed anyone, means to say that you have something more to offer. The problem begins at you being to vague and 'mysterious'. Which adds more unnecessary hype.
I believe you didn't get the purpose of KTM in the first place.
It is meant for those people that does not follow the 3DS scene, mostly.
People that want to be reminded to what not to do and what to do, and with the easiest setup possible.
Install HBL. Drag KTM in the 3DS. Drag the downgrade pack in the folder. Pretty straight forward.
Also for people that have high level of paranoia.
And by the way, I'm not blaming the community for what happened to KTM. It won't be in time because the deadline imposed by Nintendo is too short.
What I'm blaming a part of the community for is not much, I usually don't care about it anyway.
But alas, people still thought that it's 'safer' than sysupdater. Safer in a way that there is 100% chance that you wont get softbricks and/or hardbricks for that matter. The thing you said about KTM now is contrary to what people currently know about KTM. You should've been more clear. Even the people at reddit thought it was safer. Bad PR work.
I just can't fathom how much more flak you'd be getting when KTM produces a soft-brick later on with live 10.4It is still safer. For some reasons you can find in the source code.
But this is not very important as it handles only very rare cases.
I just can't fathom how much more flak you'd be getting when KTM produces a soft-brick later on with live 10.4