EZ-Flash USA Forum

http://blog.so-net.ne.jp/Rudolph/2007-05-18
Warning! see ghostie's post:
viewtopic.php?p=34563#34563

Not tested on light/miniSD versions. If you have them, back up your current save from SRAM (just in case) and give it a whirl to see if it works. Apparently PSRAM is slower on EZ4 than on 3in1... I don't notice much of a difference considering how slow the browser is anyway.

Not sure if it is just deluxe that supports it or what. Still need to run the browser from a slot 1 card. Can't take much credit for the patch below, though all that is different from the 3in1 patch is where the expansion header data is put on the GBA bus. No clue why it works, everything I know says that is writing to NOR and not PSRAM.

Standalone patch for clean EU browser in case you don't have R4 or DSLink or don't wish to use Rudolph's tool (by me via a short bit of asm to enter the browser card's header in the right place borrowed from Rudolph's tool - marked as such in included source):

can you explain step by step how i make it works?
i tried somethings here but i guess im doing something wrong XP

Wait, so you're saying you can run the Opera Browser from the Slot-2 with this patch? Or do you need to use a Slot-1 to boot it?

Nice work as usual cory1492.

No, I said:

if you don't want/have a card that is supported for enable RAM expansion, you can use the standalone patch for the .nds, so it works alone.

Red Dragon: if you have a soft reset supported slot 1, put the clean browser on your card, put EZ4 deluxe in slot 2, run Rudolphs program and read onscreen. RAM enable should be R shoulder. If you are using the patch, read the nfo with it, it tells you what to do to patch it.

Ah, okay. The way you worded it was a little confusing.

I cant read any of that stuff on the site. I have an R4 and a EZIV lite deluxe. From what I gather, you place the opera rom on the slot one, along with the EZ4 2in1 Tool? Then run the 2in1 tool? Some help would be great thank you.

I can confirm that this does indeed work with the EZIV lite deluxe (miniSD version) A little trial and error and I got it working with my R4 and my EZIV lite deluxe. This is how:

1. Place clean browser rom on R4.
2. Download the EZ4_2in1_tool from the link in the first post.
3. Place the EZ4_2in1_tool on the R4 and run it.
4. In the menu, press the R button. This will do a soft reset.
5. Load the browser from the R4 menu.

-in order to use the browser, you must load the 2in1 tool everytime before you launch the actual browser

The browser works great! A bit slow, but working. I was even able to sign into xbox.com with my .net passport to check my section over there.

Good work guys! Now if we could just get a bigger ram expansion for the slot 2 to speed this thing up, that would be even better.

nice, the browser works with ezv + eziv.

the 2 in 1 doesnt reboot the ezv properly for the browser, the power just turns off, but the patch does the job!

It worked for my EZIV Lite Deluxe MicroSD and my R4 as well.

Thank you, Cory, for posting the info.

Warning!

The browser works, but it seriously screws with your SRAM.

I had been playing Shining Force on my EZ4L Deluxe (using a NOR slot and the NDS loader). Before I ran the posted app, I made sure that my SF save was written to the MicroSD card.

I ran the app as posted, pressing R when appropriate.

Now, whenever I try and load SF, my save is ignored and I have to start a new game. If I just reset at this point, I get a "Battery is dry or first in" error. (My battery is fine.)

What is even more puzzling is that if I import my "battery" save via VBA and run the patched copy of SF, I get an error (can't load), but I can play a VERY old save. (This was the first time I used VBA with SF.)

(EDIT) Only SF is doing this. I haven't run into any other games with the same problem.

Did you try just the patched browser instead of the app with the same effect, or are you saying the effect seems to not be reversible (if so I will try to replicate it on my card adn come up with a fix)? It could be Rudolph's app, which is essentially experimental anyway, is not handling SRAM properly (giving "first in" messages, which I discovered as well). I will add your warning to the first post though, and thanks for mentioning it.

I haven't tried your patched code yet. I was under the impression (from your initial post) that it was for people without an R4. After reading your NFO, I see that it was a general patch that would work on all slot 1 cards. You might want to edit your post.

I will see if I can replicate the failure with Rudolph's app and your patched browser.

I will also check to make sure games with large saves work properly on my hardware. This will rule out hardware damage.

The 2-in-1 app causes one of the two "first in" messages to appear after every launch. It also caused my SF game stored in NOR flash to black-screen. I wasn't able to get it to corrupt my save again, but it looks like there's a potential there.

Your patcher app worked like a charm. I didn't get any "first in" messages or lockups. The only thing I saw was that the R4 wouldn't detect the EZ4 after an IGR. This is understandable. It took a power-cycle to get things back to normal.

Thanks again ghostie

Rudolph's tool (by deduction) must be writing something to SRAM even when it is should have done nothing to SRAM at all. I am just glad to know that the results I got with the patched browser are not replicating this, though I am still somewhat mystified as to exactly where the RAM cart header is getting written - at least it's not being written to SRAM.