programs them and sent them out to the retailers where they get labled with "Gateway" stickers etc. It looks like the GW3DS Team buys the PCBs. I think at a certain point they began to identify those carts by altering the markings on them, as you can see on the following pictures, where the "X" in the "X-B" marking is blacked out: I don't know if both names are accepted or not, but to me it was a clue that the GW3DS Team is buying the DS cart hardware from different teams and installing their custom bootstrap onto them to somehow make it unique / not of the shelf. dat file is, that its the first file the bootloader/bootstrap is looking for, if it can't be found you get an error during startup. The GW3DS Team uses the name "_DSMENU.DAT", while the Ace3DS+ Team uses "_DS _MENU.DAT". One thing that caught my attention was the menu file. Now that I knew what cart it is, I tried to compare the files that the GW3DS and Ace3DS+ Teams are offering to see if there is anything suspecious in there. The PCB from the blue cart had this "X-B" marking close to its pins, which I tried to use as a reference on my search and found out that the Ace3DS+ has to be the manufacturer for these carts. I looked around several sites and reviews of the GW3DS and saw pics of the PCB from the blue cart.Īfter reading through the review and inspecting the GW3DS firmware folder I understood that the cart is a R4i clone, so I got my first clue to look for further information about the cart, since I knew that the GW3DS Team wasn't building those carts themselfs. On my journey to figure out the whole NDS scene, I first tried to understand what I actually got with my Gateway 3DS. Which is fine actually, but also wrong, in case you ever decide to check whats going on and find yourself in the same situation as me and realise pretty quick that there is way to much information to keep track of everything.īut lets get to the goal of this thread, I just wanted to share my point on things first and show that it isn't easy for someone whos is completly new to the whole thing, but I think I got my around all that stuff pretty well. I'm that kind of person who wants to know everything about each of my devices, to see whats possible and what is not.īut I also know that there are peeps out there who just want to play their games and don't give a damn about how the stuff works, as long as it works, tell them what to do and of they go. Now the thing is, everytime I buy a new console which has a huge community behind it and an ongoing hacking scene which I never cared about, I find myself lost in all of the information which is available for the specific device, I'm pretty sure we've all been there once.įor the 3DS part of the Gateway 3DS it's a piece of cake, since this thing is "brand new" and the news and information about it can be overwatched.īut a few days ago the DS part of the Gateway 3DS (the blue cart) got some of my attention, so I set out to check whats the deal with DS flashcarts and found myself in a chaos of information.įrom Wood Firmware, to 2000 R4 clones, over words like DLDI, Bootstrap, Kernel and whatnot my brain began to crack my skull in order to break out because it didn't fit anymore. I knew such things existed because a lot of my buddies got Nintendo DS' with flashcarts, but I never realy bothered about the Nintendo world that much, since I'm more into the PlayStation scene.īut every now and then I buy a new console just for fun and so I got myself a 3DS XL together with the Gateway 3DS flashcart. I'm pretty new to this whole DS flashcart thing. My goal might not be clear at first, but the text is about getting to know what the blue cart bundled with the Gateway 3DS actually is and if there might be way to update it, to support later 3DS firmwares, since I read that the bootstap can't be updated, yet I found "proof" that it might work. There was so much I wanted to say that I completely lost track and messed up the structure pretty good. WARNING: This thread got pretty long while I was writing it.
0 Comments
Leave a Reply. |