Jump to content


  • Posts

  • Joined

  • Last visited


10 Good

About Pokedoc

  • Birthday 05/23/1976

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It took longer than expected, but the next version is finally here. Version 0.3.0 RC1. This version is essentially feature complete, it does everything I know how to do. Unfortunately, all my attempts to get it working on the DSi have failed. DLP mode should have worked, but unfortunately, you can't run homebrew via DLP on the DSi, and no one bothered to update this method after the success of Flash Cards. Some other ideas also didn't work as expected, and now I am 99% sure that we will need a System Menu/Launcher-level exploit to get it working on the DSi (or the 3DS). Nintendo did indeed learn its lessons, pretty much everything that is not required by an official game/app is simply switched off. But enough bad news, here is what is new in this version: - Adds the ability to translate most parts of the user interface. - Adds Slot 2 backup mode (you will need a Slot 2 flash card; anything that has a DLDI driver should be supported). - Enables FTP restore mode for saves bigger than the memory buffer (usually 2 MB), it now uses multiple passes in this case. - Various stability fixes, especially aimed for R4 clones. - Adds a list of unsupported games to the instruction file. So far, these games are: Band Bros DX, WarioWare Inc ("big" saves, 8MB+), Pokemon Typing DS (Bluetooth device?) If anybody figures out something new, wants to start his own fork or try something out, or knows how to access one of the few remaining unsupported games, I would say that the time to start doing these things has finally come. The code is sufficiently stable so that I will not refactor significant sections of the program in the forseable future. You can still expect bug fixes though, and I intend to collect translations and pack them in the official release at some time in the future. Switching languages is as easy as adding a line to your ini file and copying an additional file to your folder. Adding a translation simply requires to take the template file included in the archive and translate the lines. I have commented the template quite heavily, so you should be able to see what the individual lines do. Unfortunately, I do not know if special, language-specific signs are available in the default font used by the program. German Umlaute (Ä,Ö,Ü) do not work, and I am afraid that other specific letters might be missing as well. Anyway, this should only be a small nuisance, so feel free to translate anyway. (If somebody knows how to use a custom font font, or maybe even how to add color in the test, please contact me.)
  2. Okay, it has been a busy time during the last weeks. I am just recovering from a (business) trip to the States, and getting past the jet-lag is not nice. And then I had to reset my password... Anyway, here's the latest news. I have set up a project at google code hosting (http://code.google.com/p/savegame-manager/), where the tool will be hosted from now. So far, I have placed the source code of the previous versions in the SVN repository, with more to come in the next weeks. This has the advantage that everybody who wants to donate code, report bugs, etc. can (will be able to) use the more centralised facilities over there now (soon). I am also going to sift this thread for anything useful that has not found its way in the code yet, remove obsolete attachments and clean up in general. The latest version(s) of the program will still be available from the first post in this thread, though. It will soon be possible to translate the program into your own native languages; I will publish instructions after I have finished everything. I'll do the German translation myself - it's my native language, and I can nicely use it to test everything. I have also started touching Slot 2 mode, but I wasn't able to launch NDS files from my EZFlash IV yet (flash cards keep complaining that it is not a supported device). And finally, I have started experimenting with what might become the first save backup tool working on the DSi - once I got everything worked out, you *might* be able to run the program as a download play game, very similar to the transfer machine in B/W. (Don't count on it, though. There is still a myriad of difficulties to overcome, including getting a download play server running at all.) And finally, I had to change my archive tool again - seems like TUGZip quitely drops empty folders, which is not good if you compress a checked out SVN repository.
  3. Version 0.2.4 is out. This is a new snaphshot that primarily addresses an issue with dead 3in1 batteries, which causes the dump process not to continue after rebooting the DS. About 50% of the user interface has been reworked, and the ability to translate it will be coming soon. And there is now a Readme file, which gives instructions how to set up most things - even though it is not finished yet (no proofreading, some missing bits), it should be mostly usable. Several small things are yet to come (and I haven't found the time to look into some R4-related issues yet). Nevertheless, the current version should be stable on most flash cards. Switched from IZArc to TUGZip, which should fix slash-versus-backslash issues on Linux/Macintosh (according to my hex editor). I like the video on Youtube, will definitely add a link in the readme file. Otherwise, I am quite swamped with work in the following weeks, but more updates will come - I definitely intend to finish that stable version 0.3.0, which will contain everything that is still missing (and for which a solution exists).
  4. Finally found the time to check the last few pages, and collect feedback for the latest version. It seems like there are two remaining major issues: 1) setting everything up correctly (which is not a bug in the program), and 2) various clones of popular cards that do not work as expected (especially R4 clones). Plus some minor glitches, such as the FTP connection still not working on some occasions. Some answers to questions that pop up regularly (I may edit something in the first post): It does *not* work on the DSi/XL. I spent some time trying to figure out why, and it seems like the DSi cuts off the power to Slot1 after switching the cartridge. To restore power, one has to run the program in DSi mode, and even then, one has to figure out how precisely this works. It might be possible to reverse engineer this from the DSi System Menu, but unfortunately, the binaries are protected by an additional encryption. So, in a nutshell: it does not work on the DSi. It might be possible to get it working on the iEvolution, but no one knows how. DSi mode detection is already in the program mainly to warn people that it does not work. And the SD-slot is locked out as well (but this may not be the final word on this issue). Almost the same can be said about the 3DS, but it is a little bit worse. The iEvolution does not work in DSi mode on the 3DS, so even if it did work on the DSi, it would still not work on the 3DS. And finally, a small outlook what I am currently working on. First, an extensive Readme file that will give detailled instructions on how to set everything up. It will come in odt (editable)/pdf (easily readable) format, and is supposed to include screenshots, so that everything should be clear even if your English is weak. I am also intending to add a list of FTP servers that are verified to work (since the program only uses a very rudimentary FTP client - Google was not helpful in finding something better, other than "use your operating system/Firefox"). And finally, I intend to increase the verbosity of the program, making use of the lower screen to display longer, more useful texts. And actually, I have even started thinking about exporting all messages to an external ini file, so one can actually translate the program. (Plus an asortment of minor improvement, such as checking that your DS has enough power, and that your 3in1 battery has not run dry.) The next update will most probably be the first usable version of the Readme file, and after this, my work order is still undecided. @Morfeo, marc_max: Funny that you mention Slot2 support, I did buy an EZFlash IV some time ago, and now that most of the major issues are ruled out, I want to start working on these features as well. @Balrog: I am getting increasingly angry with IZArc and its weird slashes as well (another, non-handheld project of mine also ran into this issue), but I have not found a suitable replacement yet. @all: If you have issues with the "B" button, the program working once and then no longer, or something else, please post the specific Flash Card/Firmware you are using. It seems that various (R4) clones have more issues than expected. This should be useful for the Readme file.
  5. I really wish I would find more free time to post/update more often, but Real Life keeps eating my nerves (full-time job, spending hours in traffic jams, having to support two residences... a day sometimes does not have enough hours). Anyway, here is the next release, mainly bugfixes. (At least I could reproduce *these* bugs reliably.) This re-fixes 3in1 backup mode (forgot to update one line in the last version, so it worked exactly once; tested once on both of my 3in1s, so I didn't catch it earlier... :mad:). It also improves WiFi connectivity. After trying everything, debugging other peoples source code, I found that a "brute force" way actually works. (For those who care: I read from/write to the FTP server in packets of 512 bytes, and sometimes, not all of these bytes "make it". Since I could find no documentation on how to proceed in this case, I did go the "safe" way and just stopped everything. I could still not find any information, but after much experimenting, I found out I could simply retry until I got all data. In the new version, the screen will display "!!!" in the bottom left corner if such interruptions emerge - a remnant of my own debugging sessions.) Today, I got my European (German) Black/White games, and I can verify that they work with the tool, IR device is detected and addressed correctly and everything works (if you don't happen to run into a new bug). Oh yeah, before I forget: this thread is getting a bit difficult to oversee, could you repost any issues that you may experience with the latest version (0.2.3, attached to the first post)? I am currently working to stabilize my tool, i.e. to release the first non-beta version.
  6. (I was going to post this yesterday evening, but my internet didn't like me, so sorry for the small delay.) I've just finished the next version. I still do not understand the random data corruption in the first 256 bytes (with the 3in1 method), but I fixed it anyway. I am simply leaving the first 256 bytes untouched, and write the save to a different location on the 3in1. Poryhacks save now dumps/restores correctly (and those who had still issues with the 3in1 should also try this version). Version 0.2.2 is available at the first post. (I really wonder how flash cards work around this issue?) I have also modified the WiFi backup method; the program will now try to load the entire save from your FTP server before touching your game cartridge. If your save is larger than 2MB, you will get a warning that restoring is insecure (and the program will stop, just to be sure). This should prevent any more damage until the transfer itself is fully fixed. If your file is at most 2MB (which should be the case for HG/SS, and at least 99% of all DS games), the program will stop if there is an error while loading the save, and your original game will not be touched. In this case, try again and get REALLY CLOSE to your access point; this seems to fix a glitchy connection in most cases. During my own experiments, connection failures already started at about 40-50 cm. (The glitchy connection will be fixed in a later version, I have to try out several things, but if you just keep trying with the current version, it should work anyway.)
  7. Thanks everybody for the feedback. I am still working on what I hope to be the last glitches in 3in1 mode (and then I will release a new version, probably this weekend). In fact, I decided to go with snapshots since the bugs reported by some people do not seem to appear for everybody (and I did not want to release new versions that did not fix anything...). During the last weeks, I learned a lot on how the 3in1 actually works, and what kind of stuff is glitched in the standard code provided by Team EZFlash. (For those technically interested: the 3in1 NOR is almost identical to Flash saves on GBA games, down to the way to address it. Using this background, I was quite surprised on what the standard library did not do.) @everybody who has issues with a 3in1: During an early development stage, my own SS did result in bad dumps, with only *two bytes* being off. It disappeared later, so I thought it was fixed, but now that Poryhack is observing pretty much the same, it seems to be different. In the snapshots, I had added code to verify that everything that gets written to the 3in1 correctly (by reading it back), and now this older bug seems to be back. I am currently working on a fix, which will lead to a final version of 0.2.2, which should be ready later this weekend. @Zelda4 and everybody who has issues with WiFi mode: I have decided to replace the WiFi code with something less glitchy, and I will also try to make it more save for existing saves (i.e. get the entire save before writing to the game cartridge). This will probably not make it into 0.2.2, though (sorry). @specialmias: I have also started writing on a readme file myself, giving instructions how to set everything up, and general things. Since I have not yet found the time to write the paragraph on WiFi mode, I would like to copy what you wrote (with your permission, of course). Black/White *should* work, assuming that they are using the same cartridge layout, but before the localised versions reach Europe, I can't test it myself. (In other words: Wait for a month or so, then I can test it myself.) @claudekennilol: If you still have issues with ini file not found, you need to drop it into one of two positions: either your root folder (which should always work), or the same folder where your nds file is placed (only works if your flash card supports "argv", which tells the program what directory it is running from - but this depends on your flash card firmware). If you keep having issues, I may make the ini file optional - it is only used for WiFi mode, anyway. Where the nds file is found *should* not matter. @ZeroManArmy: The AR DSi seems to be a problem in itself. You need a DLDI patch to get this program running (essentially a driver for the microSD card on your hardware). Pretty much all moderately recent flash cards do this automatically, except (i believe) the AR DSi and similar devices. I never needed to do this myself, so I can't give you too many hints, but Google says that you need the "GMTF DLDI driver" (no idea where to get it, or actually, what "GMTF" stands for). Since Datel devices are slightly different from classical flash cards (in terms of blocking piracy), it might still not work then. And if you are trying to run it on a DSi/XL, it will not work anyway, since the DSi messes with the hardware required to access slot-1. (When this gets finally figured out, I will adde is asap.) Random questions, which keep popping up: Slot 2 cartridges are not officially supported (yet). If it works for you, good; if not, bad luck. I don't have any slot-2 cartridge to test it myself (but I have finally found a store that still sells Supercards), and currently, I am focusing on stabilizing the 3in1 and WiFi backup modes. In other words: it is on my list, but not quite at the top. If you are wondering why this is the only tool that works: HG/SS have the infrared device used to speak to the Pokewalker. Since slot-1 does not grow additional pins to talk to the new hardware, Nintendo had to change the game card, so it is able to switch between the save chip and the IR device. This also needs a slightly different strategy to address this chip (and I seem to be the first person to figure it out). If you use standard methods, you will get random garbage, since the chip does not know which device to address. And personally, I still believe that this is the reason why Nintendo decided to recycle the IR device for Black/White - to protect their precious saves. 4-way video chat with a device that requires a clear line-of-sight is quite pointless, imho.
  8. I have finally found the time to extract some German Events from saves I have been collecting for almost half a year. I have browsed through the last 20 (or so) pages, and found that several events (especially the European Ranger 3 events ripped by herooftimedark) already seem to be there, but I could not find them either in the zip file or the event download section on this page. So I apologize in advance for any duplicates in this collection. So here you go, German versions of: - the Enigma Stone - the 10th Anniversary Mew - all Oblivia Pokemon (you won't have to edit dates this time) Hope it helps, and that you still find something useful. German Events.zip
  9. This is good to hear, I have been doing my last tests with a Platinum cartridge (without errors), and I'll need to re-test it with my own SS. Since you are using Acekard/AKAIO (V 1.8.5?), it should be easy to reproduce, since I have this card myself. The warning you are getting is actually a new safeguard added in this section. After the program writes a block to the 3in1, it immediately reads it back and verifies that the data is still the same, i.e. without random garbage appearing again. But I already have an idea how to fix this - I'll try to extract those commands that banished the garbage data from the format procedure and call it each time before reading something. @Zelda4: If I understand you correctly, you are using WiFi mode, on an M3, and you edited your save using one of the tools from this site. Then you restore your save (again using WiFi, I assume), and your edited save never seems to arrive? Please give me the following informations: The version of your M3 firmware (and if you are using the DS-sized version of the M3 or the GBA-sized version, just to be sure), and the save you are trying to restore (just to be sure that your edited file is sane). It would also be helpful to know what WiFi AP you are using, and which driver. This should help me reproduce the bug (or at least narrow it down). Oh yes, if you prefer writing in French, just keep doing so. I had French as my first foreign language (many years ago), and even though I would no longer dare to write in this language, I can still follow what you are saying. EDIT: I have finally understood where the garbage data is coming from. The NOR memory on the 3in1 works very similar to the Flash saves found on GBA games. This includes an "ID mode", where the device is giving out an endless stream of its hardware ID. Seems like the EZFlash sample code for old devices enters this mode, but it gets never switched off. And this places the weird periodic pattern over the data we want to read. I have fixed this, and it now works without having to format anything. Poryhack, unfortunately, I was unable to reproduce the final bug with your SS. I am attaching a second snapshot, where the other bug is fixed "correctly", maybe it also fixes your issue (hardware running outside the specifications could result in weird behaviour, after all). If you are still getting errors during the backup process, then I have to ask you to dump your save using WiFi (or one of these USB sticks), if possible, so I can work exactly under the same parameters as you. (I hope that this will not be required, though.) snapshot 2.zip
  10. Yeah, I did't experience anything like this either. But then, who knows what Rudolph had to go through to get it working correctly; his program is not open source, unfortunately, so we can't check. Anywaqy, I just made some progress on the 3in1 issues that still seem to persist. Placing the code aside for a few days really helps to make place for new ideas, and I think I may have fixed it this time. Essentially, there are *two* bugs which appear when addressing the 3in1. The first bug (which was fixed in 0.2.1) happens on *some* (but not all) flash cards and produces random garbage in the save file. This means that your flash card is doing some stuff with the 3in1 all by itself; it should be fixed by disabling interrupts while accessing the 3in1. This allowed me to finally reproduce the second bug, which appears on *some* (but not all, "plus"-version seems to be clear) hardware revisions of the 3in1, and which inserts non-random data at regular intervals (as reported earlier in this thread). Now that I could reliably reproduce the bug, I *hope* I finally managed to fixed it. (In a nutshell, I had to *format* an unrelated region of the 3in1 if I wanted to *read* anything on a freshly initialised 3in1. Not quite the most obvious thing to do. Probably some initialisation stuff that was missing from the 3in1 "read" code.) Anyway, here is a snapshot of the program. I have just finished seting up my iEvolution, and I want to do some tests this weekend. Therefore, I am releasing not a "full" new version, but only a development snapshot; the source will follow in a few days. Since this is not an official release, I am attaching the file here instead at the first post. Tested and working on: - Cyclops Evolution, Cyclops iEvolution (on a DS) EZFlash Vi, M3 Real, Acekard 2i, on 256M and 512M versions Tested and sort-of working on: - Cyclops iEvolution (in DSi mode on a DSi, results in freezes, needs more tests) I seriously hope that the 3in1 method now (finally) works. Oh, btw, some more breaking news from GBAtemp. Team Twiizers have released the first DSi-mode exploit that allows you to launch nds files from the SD card. You just need a certain DSi-ware game (Sudoku by EA), patch it with the exploit, and you can start a random application from the SD card. Full SD support is siupposed to be entering libnds while I write this. Unfortunately, Nintendo has already taken this game down before I could get it snapshot.zip
  11. Yesterday my free Cyclops iEvolution sample arrived. Well, at least I think it did, 'cause I won't get my hands on this package until Friday evening (but it is from the correct region of the world). There is already a shiny new microSD-card waiting for its slot to arrive. This weekend, I will have a look into everything and see what can be improved without too much work. Other than this, I did not make much progress in the past weeks (as this is not my only pet project). I have tried out some ideas to get the current code working on the DSi, but it did not work. I have a few more things to try out, but it may still take some time before everything falls in place. As usual, I can't promise any fixed dates, but I hope to get something working in the next two weeks. Still looking into various other issues, too. Other than this, I have started to write a Readme file, including a list of flash cards which do work and those which don't, which ones don't automatically apply DLDI patches, where to get exotic DLDI drivers, etc. If you can contribute anything, it would be great - in these days, you just can't afford do buy every possible piece of hardware yourself. This should help preventing people from blindly trashing their saves. @Aroenai: Funny that you mention this, I experienced the same issues during my own experiments. I'll add it to the readme file I am working on. @Eon-Rider: This (WiFi) error means that your connection did get a damaged packet (i.e. it tried to read 512 bytes, but got a different number). I encountered the same issues during development of this mode, but it seemed to disappear after some time. Maybe you could try the following: Don't have anything running in the background that might interfere with your FTP server. Get as close as possible to the antenna of your AP. Or: restart Windows or at least your FTP server, its networking subsystem can be quite weird sometimes. And finally, please try to restore it again, maybe the glitch automagically vanished in the meantime. Windows can be really weird sometimes. And on your issues with the 3in1: weird, it did work on my own 3in1-non-plus. I'll try and look into it again. (Since you are also using an Evolution: did you change any settings related to the 3in1, such as rumble mode?) @Zelda4: So, you say you were able to rip the file correctly, but not get it back, right? And you seem to be using WiFi mode? Are you getting error messages during the restore process, does your original cartridge come up with a blue screen claiming your save is corrupted/deleted/anything, or does your original game restart as if fresh out of the store? @Poryhack: I thought I had tracked it down to the DLDI driver doing weird things with Slot-2. Every time some file-related function was run, the following 3in1 accesses turned out garbled. It does work now on my own EZFlash Vi. Anybody still experiencing these issues? @Pingouin7: Okay, in this case I need more information to pinpoint the problem. Did you try WiFi mode, 3in1 mode, or both? Did the tool give any error messages? Does it freeze (if so, what it the last thing it is telling you), or does it simply dump garbage files?
  12. Thanks for all the feedback, good to know that FTP mode is more reliable than 3in1 mode. However... I have found an old MicroSD card while cleaning and used it to revived my old (back-up) EZFlash Vi. This allowed me to nail down the reason why 3in1 mode does not work here - it's an issue with the EZFlash DLDI driver, which is continuously stealing access rights to the 3in1. Maybe it is looking for a slot 2 DLDI-able device (EZFlash IV perhaps?), maybe it is using the extra RAM to cache something, or maybe it is simply a bug in the driver. Fortunately, fixing it was quite easy. So here (i.e. at the first post) is the latest release, V0.2.1, that fixes 3in1 mode on an EZFlash Vi (and perhaps some other cards exhibiting similar issues as well). I have tested 3in1 mode on my collection of Flash cards, and it should now work on the M3 Real, Cyclops DS Evolution, EZFlash Vi and Acekard 2i. (And that's my own small collection of cards. M3 for Ruby/Saphire/Emerald, Cyclops because it is much better, EZ Vi because it got the earliest fix for DSi firmware 1.4, and Acekard for AKAIO.) @Soladept: Action Replay DSi... now that is an interesting question. I know that the ARs ship with their own microSD slot, but afaik, no one knows how to access it. All I know is that the AR is somewhat different from regular flash cards, so I'm inclined to say no, it is not possible. @barklight: If it doesn't work on your R4, I am afraid I do not know what might be going wrong. I have heard too many different things about R4 and its various clones, maybe you have a "bad" clone. I have never heard of *buttons* not working, though. @Pingouin: No, "save too small or no save chip" is a part of a security mechanism I have put in to prevent people from flashing a wrong file to a game cartridge. It means either of two things: a) you have a flash cart inserted (i.e. "no save chip"), which always comes up after restarting the tool, or b) you are trying to write a file that is too small to your cartridge (e.g. a 247 bytes-file to a 512 kB save chip). In this case, just eject and reinsert the target game cartridge, press "a" again and it should work. @harryohh: I'm afraid that this tool does not yet work on a DSi yet, and no one seems to understand why. I have done some preliminary research into this, and it seems like the different DSi Bios/Firmware is to blame. When you swap a cartridge on the DSi, the device automatically does some initialisations that are missing on the old DS. Somehow it manages to lock out the entire hardware required to access the save chip. In the future, when the iEvolution is released, I expect that the community can figure out how it ticks, and how to unlock the same cartridge, but at the moment, you are out of luck. @Aroenai: WiFi mode should give you a rather exhaustive feedback on what stage the backup mechanism currently is in. The backup process works roughly in the following order: 1) Login to the AP. This uses your DS WiFi connection settings. 2) Connect to the FTP server. This makes use of the IP address in the ini file. If it fails here, you may have typed in the wrong address - it must be the address of the computer on which the FTP server is running, not the IP address of your AP. Or you may have to verify that the port at which the FTP server is running is not blocked by your AP, and that you are using the correct port. 3) Login to the FTP server. This is where your username/password from the ini file are used. After this, everything should be up and running. @Noko: Deleting the savegame is intentional; it is the first part of the restore process. On large save chips (such as those used by Pokemon games), the save must be deleted first before a new game may be written (it's for technical reasons). After this, the new save should be written to the freshly erased chip. Are you using the 3in1 restore mode? Do you get the "blue screen of corrupted save", or does your cartridge beheave as freshly out-of-the-box? If you are using a 3in1, then maybe your flash card is messing around with slot 2 as well. In this case, you should try the latest version and restore again.
  13. A new version of the tool is available (see first post), which I hope will fix most issues with the 3in1 some people are experiencing. Version 0.2 introduces the following new features: - An ini file. If your flash card supports "argv", you can drop it in the same folder as the nds file. If you get an error, place it in the root folder. (The tool will complain if no ini file is found.) - [Needs the ini file.] WiFi/FTP save dumping/restoring. Tested with smallftpd-1.0.3 and a Ralink-based WiFi stick in SoftAP mode. - File browsing is now fully functional, both in FTP and 3in1 mode. - First attempt to identify Slot-2 DLDI flash devices. (Based on your Slot-2 device returning a correct "argv" value. Please test this!) - Added menu to GBA backup mode (it still does not do anything, though) - Made some modifications to the 3in1 code, I hope that the glitches related to bad dumps are gone now. As usual, feel free to test the new features. I didn't find the time yet to test it on any other card than my good old Cyclops DS. However, with the new WiFi mode and improved file browsing, there should be something for everybody now. Barring critical bugs (or a sudden rush in inspiration), this will be the last update for some time. When I get my iEvo from Team Cyclops, I will see what can actually be done on the DSi. According to a news post on gbatemp, TC anounced to release "information and code snippets" so that the new DSi features should be ready for use soon, and that "Changes required to get homebrew functioning properly in DSi mode are actually quite minimal", so *crosses fingers* DSi support should be not too far down the road. At the very least, I hope to get WPA encryption in the WiFi mode up and running, so you don't need to buy a new WiFi stick (well, you do need an iEvolution, or maybe not - just read the latest news). Now all that remains is for TC to actually ship their samples. And quite interestingly, another hacking group announced a new exploit which allows access to the NAND, install custom channels and finally access the DSi SD-Slot, so there are certainly interesing times ahead.
  14. That is funny. You seem to have two versions of the 256M cart, and I have the C11 as well, which seems to be working fine for me. @Balrog: Yes, I am deleting the NOR before using it. The main difference between my tool and other tools seems to be that I do not delete the entire 256/512M range, just as many pages as I need to fit in the save (which shouldn't affect anything). If there are indeed some hardware revisions which refuse to work, the best way might actually be to disable them or at least place a warning. Maybe I'll add a quick way to identify the hardware revision of the 3in1 in the regular tool. @Bond697: Maybe something in your 3in1s is set by your flash card, but not by mine? I have tested the tool on my old CyclopsDS and my new(er) Acekard2i, and neither of them seem to mess something up. What flash card are you using? I am getting more and more dissatisfied when it comes to this hardware. Right after flashing something to the NOR memory, I was unable to read back some of the data (two bytes!) I had just written there, which is why I included the "you need to restart" step while restoring data. If this bug appears even with non-IR cards, then it is definitely the 3in1 which is to blame. I'll try and experiment some more and try to understand it better. @evandixon: I tried to get the file browser working for the current release, but it is considerably more complicated than expected. Unfortunately, the DS does not provide a built-in GUI toolkit where you can simply call "SelectFile(...)", but everything needs to be coded from hand. I am still hoping to get it working at some time, but I wouldn't count on it happening anytime soon. On another note, I have successfully applied for a developers iEvolution, and will get it when it is available. Unfortunately, the very latest rumors from gbatemp seem to hint that the SD-slot is locked out by hardware. It is claimed that as soon something is executed from Slot-1 (i.e. the flash card), the SD-slot becomes unavailable, and that it is only available to the NOR. Well, we will have to see what it really looks like when the hardware is finally in our hands.
  15. Thank you everybody for your feedback, so it seems like only one of the three 3in1 HW revisions refuses to work. To support additional testing, I have prepared a quick-and-dirty testing tool that reads the same magic values used by the default 3in1 detection code. Those of you who have a 3in1 that does not work: could you download and run the tool attached to this post, insert the 3in1 that is not detected and post the values it did dump? Just for clarification: my own devices detect as the 512M-version (slim size) and one of the two 256M-versions (big site, not sure which hw version, though). I vaguely remember reading somewhere that the EZFlash demo code might be incomplete, maybe this helps in eliminating the last glitches. Anyway, it is good to read that it does work for some of you. And on the Cyclops iEvolution: I did actually read about this new revision, as well as the rumors that it will support DSi mode. Since this seems to be verified now, this should help to support Team Cyclops as well. Let us just hope that somebody figures out why the classical backup methods collectively fail on the DSi when running in DS mode (and that the homebrew toolchain gets updated in time). TC giving out devices for free would fit quite nicely in my own scheme, actually: I have not yet bought a SC DSTwo and was already aiming towards an iEvolution (my current Evolution is starting to act strangely, sometimes not accepting regular cards). @whatever: You were asking for support of other Slot-2 devices, and while it should be possible to do this, I am not sure if it is completely feasible. This weekend, I happened to come across a library that is supposed to add support for various Slot-2 devices when it comes to using them as a RAM expansion tool, but there seems to be no support for other functionality (and frankly, the code found there is already quite ugly). Due to a lack of the necessary hardware, I also do not have the abilities to test it myself (only got two 3in1 cards and an M3 GBA expansion pack myself). But you are right: in principle, it should be possible. hwtest.nds.zip
  • Create New...