EZ-Flash USA Forum

Okay, looking a bit more closely at flash_ez1.sub, it appears that it's not exactly the same as the ez-flash 4 reset code. Shame too. Anyways, as a second guess, I'd recommend taking from exit_patched_5-23-08.zip, reset_ez4.bin and overwriting hvca/bin/flash_ez1.sub then trying again (that's the quick hack approach; feel free to alter merge.bat instead to add an extra option for flash_ez4.sub (or whatever you wish to call it)).

Having said that, I'd also recomemnd using gbata to fix the header on hvca/bin/base.bin, then using EZ4-64 on base.bin and renaming the resulting base.bin.bin to base.bin. Then you shouldn't have to do any more patching through the EZ 4 Client.

Silly me. I just found out how to actually use the reset feature in HVCA! (Hold the L and R Buttons when returning to the game screen until you're prompted to release them.) I found out about that by testing a newly created VS Excitebike, by renaming that reset_ez4.bin file to flash_ez1.sub, which I hope to God that's what I was supposed to do. The reset actually worked! Next, I tried a ROM that wasn't as fresh. It did reset, but to Pokemon Mystery Dungeon in the NOR flash! But I reset out of that, and it saved the HVCA data just fine. EDIT: They all work now, the reset and everything. Thanks a bunch! Now to get the same ROMs on the M3Lite to reset properly...

As for the whole base.bin thing, I tried that a while ago. Long story short, I'll stick to fixing the headers individually.

Will Goomba Color emulator be added to these releases?

I hope this is okay to revive a very old thread, but I would like to know how it might be possible to run PocketNES (with save working) from the EZ-IV?

I have downloaded the file from the first post, copied Pocketnes.gba to my SDMicro card, and the .sav file to the SAVER folder. I opened the GBA file and though the file boots, it flickers blue, then black and nothing.

I do apologise for what is probably a very basic, easily answered question but I would love to play some of the old classics on the EZ-IV.
Thanks.

Also: Should I try downloading the official PocketNES release, patching using the client and copying to SDMicro?

You don't need to patch the rom with the EZ4_client but you do need to build a proper GBA ROM file by adding some NES ROMs to the emulator.


Just grab the PocketNES Menu Maker 1.2a from: http://www.pocketnes.org/downloads.html

Put your new emulator file into the same dir as the menu maker and then configure the menu maker to use that file as the "pocketnes rom"

There are other tools that do the same thing and you can do it manually using the msdos 'copy -b' command.

A small point, but you can only use "copy /b" with goomba and goomba color (this is because gameboy [color] roms include a size field in the rom). Every other emulator requires a header for each rom to be built. So, you can use PocketNES Menu Maker or you can use the pocketnes_compile.py file (assuming you have or are willing to install python from http://www.python.org (v2.x should work)).

Okay, I found the latest version of Pocketnes (11-10-08) that is Sram/exit patched thanks to Kuwanger. Quite a ninja find imo

http://www.kuwanger.net/pocketnes_11_10_08_ez4.zip

This is just a small FYI. Apparently, the EZ-Flash IV writes to PSRAM in 128KB increments. This is the main reason that the loading percentage can go over 100%. It also introduces a possible bug. Goomba, PocketNES, etc all look progressively through the ROM address space for a signifier of a ROM. For Goomba, this means looking for a 4 byte identifier at 0x104 bytes past the end of the goomba.gba or any subsequently found ROM. Because of the afformentioned 128KB copies, the buffer that reads in each chunk can look progressively like this for a 128KB ROM:

[goomba.gba start_of_rom.gb]
[end_of_rom.gb start_of_rom.gb]

Resulting in this being in PSRAM:

[goomba.gba start_of_rom.gb end_of_rom.gb start_of_rom.gb]

So, 128KB Gameboy roms will appear twice, as far as goomba is concerned. The second copy will only be a partial copy, though.

Having said all that, there's three possible solutions to this problem: pad a goomba compilation to a multiple of 128KB, pad the compilation with 0x105 bytes, overwriting any possible identifier in the buffer, or fix ezfla_up to overcome this limitation. I'd recommend option b (my work on option c is stalled, at the moment, as a little trial and error to try to fix the problem nearly rendered my EZ-Flash IV unbootable). The simplest way to do that is to make a 0x105 byte empty file and append it to the end:

copy /b goomba.gba+file.gb+empty105.bin file.gba

Creating a text file with 261 spaces in notepad should be close enough for the empty105.bin file.

Bumping this thread because it's already stickied.
Can someone apply these patches to the newest PocketNES build?
http://gbatemp.net/t310827-pocketnes-10-5-2011