Joined in 2023 
82 
63 About this deal
The default full firmware for the SF2000 comes with over 6000 ROMs across the seven supported systems. The manual suggests these are for "demonstration purposes" only, and should be deleted by the owner (with any failure to do so not being their responsibility) - despite the fact that the SF2000's menus are hard-coded for this specific list of ROMs. The ROM files themselves are a custom bundle format; the first 59,904 bytes are an RGB565 image shown as a thumbnail beside the game when selected in a game-list, and the remainder of the file is a slightly mangled/obfuscated ZIP file containing the game's single ROM file. The only exception to this format are the arcade ROMs, which consist of a plain-old Final Burn Alpha ROM zip file, coupled with a .zfb file containing the thumbnail image and a pointer to the ROM zip file name. The device advertises support for arcade, NES, SNES, Genesis/Mega Drive, Game Boy, Game Boy Color and Game Boy Advance; it also supports loading Master System ROMs. SNES and GBA performance are very hit-or miss (more miss than hit, really); the other consoles actually perform fairly well. All consoles currently stretch their output to fill the display, and do not maintain aspect ratio. The next sequence of bytes is the name of a .zip file in the bin folder, without any path (SF2000's firmware automatically looks for the .zip in a bin subfolder relative to where the .zfb file is stored - thanks .ericgoldstein for the testing!), e.g. gamename.zip The first official firmware update; fixed some button mappings for Genesis, added support for 15 new languages. Also partially broke SNES compatibility - many SNES games will run very slowly on first launch, but quitting and immediately re-launching the game will have it run at normal speed (normal for the SF2000, anyway)
The Resources folder on the microSD card contains all of the resources used by the device's firmware to construct the user interface at runtime. The following tables list the files from various firmware versions (the numbered columns, in approximate mm.dd format for firmwares we don't have official version numbers for, and regular version numbers for the rest) and what they are used for, grouped by broad categories. Resolution and format given are for the latest firmware version only; details may be different for older firmwares. The icons in the firmware columns have the following meanings: NOTE: Once you get your SF2000 booting again, I strongly suggest you perform the permanent fix to the bug to prevent from getting into the same situation again in the future. All of the above emulators support stave sates natively through an interface that is accessed by pressing SELECT + START simultaneously in-game. Four save state slots are provided per-game; the files have the extensions .sa0, .sa1, .sa2 and .sa3 depending on which slot they're for, and are stored in a save subfolder along-side wherever the game's ROM file is stored. The extension is appended to the name of the ROM file the save state is for; for example, if the ROM is called SD:/ROMS/Apotris.gba, and the save state is for slot 2, then the save state file name will be SD:/ROMS/save/Apotris.GBA.sa1. One weird note is that save states created for ROMs stored in the user ROMS folder on the device get their ROM file extension capitalised when a save state is created (as per the previous example with Apotris, where .gba became .GBA); this does not happen with save states created in the other ROM folders. The capitalisation doesn't appear to matter - the SF2000 successfully loads save states with any extension capitalisation in any folder.
These are files that I have not Added my own version of bnister's button mapping tool at their request, and changed the link in the Key Mapping section accordingly. I would say that almost all of the hype is because the Data Frog SF2000 is so incredibly cheap and it can still play games semi-decent. Currently there is a premade executable for Windows, but the code has been written to be platform agnostic so you should be able to run it directly from the python source on Linux or Mac.
Number of different versions of Street Fighter 2: 60+ 😵💫 [Von Millhausen: I think this stat is only half a joke!]Added a note to the Game Boy Advance section about the newly discovered gba_bios.bin loading bug, and how to work around it (thanks bnister!)
Also note that while you can technically charge the SF2000 while it is powered on, doing so using a charger that supports fast charging or power delivery has a high chance of blowing the charging module IC and killing the device (multiple community reports). For safest charging, use a charger that only supports a maximum output of 5v. The SF2000 does not feature WiFi or Bluetooth, but it does have a 2.4Ghz antenna to support local wireless multiplayer using a compatible 2.4Ghz wireless controller for Player 2. The Y2 SFC wireless controller and the SF900 wireless controller have both been reported to work fine. A/V Output These are other files that have been identified, which don't fit into the other categories. Non-Latin characters in the files are encoded in UTF-8. FilenameMany of the above tasks can be done using Tadpole, a general management tool for the SF2000 developed by .ericgoldstein and jasongrieves_02643. How do I install new menu themes? So, for example: if your most recently played game (first in the history list) was "Batman - The Video Game" for Game Boy, and that game happened to be the ninth game listed in the Game Boy section on your device, the fifth and sixth bytes in your History.bin would be 0x04 0x00 (which is 4 in decimal, i.e. the "Game Boy" ROM list), and the seventh and eighth bytes would be 0x08 0x00 (which is 8 in decimal, i.e. the 9th game in the 0-based list of Game Boy games). The Favorites.bin file works exactly the same way, just with games you've favourited rather than played recently. Well a lot of us in the emulation community were a bit surprised to hear so many of our peers talking about a brand new budget handheld that they actually liked.
bnister discovered that the OS supports loading game-specific key bindings from .kmp files, stored in the save folder for each system and named after a game's ROM file (e.g., /FC/save/Game Name.EXT.kmp). They also discovered where in the bisrv.asd file the default mappings for each emulator are stored. Working with this information, notv37 worked out what bits related to what buttons for each emulator. Using both their findings, we now have a tool which can be used to update both the global button mappings for the emulators, as well as create per-ROM mappings - you can find this tool here. I can confirm that this seems to work. Not sure if the file needs to be there permanently, but I left it permanently and it does not cause any problems. This results in most games being a bit soft looking, and you lose all of that pixel goodness of retro games. DATAFROG-SF2000-08.03-OS-Files-Only-VANILLA.zip - Only the OS files from the above .IMG file - copy to a newly formatted microSD The last four bytes are a little-endian Uint32 storing the offset within the file of where the thumbnail metadata starts (i.e., the offset of the first byte of width data)
built in games, in fact. Less than half of those are worth the space they occupy, and you’ll probably only ever want to play about 100 of those. Due to the different nature of arcade emulation compared to any of the other systems the SF2000 supports, the ROM layout for the arcade section is different as well. Inside the /ARCADE folder in the root of the microSD card you'll find a bin subfolder, and a bunch of .zfb files. The bin folder contains .zip files with an enforced 8.3 file naming scheme, and they contain the actual ROM data for the FBA emulator. The .zfb files are used to populate the arcade game list when you go into the arcade section on the SF2000's menu, and their file structure is as follows:
Great Deal 
New Comment