EZ-Flash USA Forum

Mbmax or windirt, do you know what the "minor bug" is? =O

I don't really know what was this minor bug but i think i've found another one.
It's in manual saving process on 3in1.
When it's an automatic saving process (changing gba rom in 3in1), the save name is correct internal_name+serial+maker.sav.
But if i press R+X to backup save from 3in1, save name changes into internal_name.sav

Exemple : GBAZELDA MC BZMP01.SAV is the save name writes by automatic process saving
and GBAZELDA MC.SAV is the one with manual saving process (R+X)

nah, not really...

i have a 2GB card and it works fine with every game except POR

I noticed some annoying things/bugs in 1.40 and thought that 1.41 would fix them, but didnt.

One thing is the settings in chinese even though you have english selected, this has already been commented on previously.

The other thing is, still in the settings (L+R), if you move the marker down, to change rumble settings for example, your manual speed setting will be changed to auto speed setting when you go past it. Annoying.

I would also like to see an option to be able to erase the save-chip...

Shizelo

is it the saves dont actualy write to the miroSD until you load another game??
it seams no save until you load another game after i really prefer the save writes on reboot
becuz i (and probably many) have multiple microSDs and hate if a save ends up on a differnt microSD
i like the EZ3 style you finish playing you save then you reboot to write the save on reboot

L+SELECT will write the save, I think?

Many were complaining about the slow start time, and backing up the save every time even when not needed was part of that. Using the previous method you'd get the save data on your other SD anyway, without really any choice... not sure if the manual write saver option solves that though.

http://ezflash.sosuke.com/viewtopic.php?t=3199

oh i see you do that once its loaded i thought you hold it on boot up so i thought iw asnt working
cool thanks guys that works good enough!!

Another minor bug:

4KB files are incorrectly reported as being 0KB in size.

ignore me with ease if you please
however as a attempt to reqeust features for future kernels??
if you can patch comercial roms to hybrid from the EZV shell
couldnt you be able to patch homebrew roms to EZV-DLDI from the EZV shell??
that would be awesome and make it hell easy
can download homebrew off the net all over the place without needing to run weird BAT files on different PCs
(note to self store EZV-DLDI.zip on your microSDs its 64kb ffs)

though wouldnt be helpful on a mac

Slothette64: that was part of chishm's intention with dldi... give flashcart makers a standard in homebrew along with example source for them to be able to do easy on the fly dldi patching without having to release source code or any even close to proprietary information. It would be easy to do with moonshell, but IMHO they haven't even fixed the homebrew detection itself well enough (using the homebrew markers in a reserved area of pretty much *all* homebrew headers instead of specific gamecodes "PASS" and "####", or the alternate which is that all homebrew binary data starts at before 0x4000 bytes). I will try one more time to show them how though, after that we are likely hooched.