last night EVEK II saved my life

[marsares]

evek II is out and I think I'm gonna cry tears of joy.

16K EEPROM saves are gonna flow out so I suggest everybody who create a save adopt a standard extension for his filename.

purpose : to Windows-associate the extension with the appropriate evek2 command

I suggest :

Mario64.eep04 -l -e04
SWEP1.eep16 -l -e16
ZeldaOOT.sram -l -s32
Starcraft.flash -l -f01

FIFA99.mpack -l -c32


I think that Z64'ers won't agree but who cares, evekII is for us V64Jr's.

what do you think ?

[ss_forces]

why not just let people check the size of the save?

hmm, let's see
4 kbits = 512 bytes
16 kbits = 2 kbytes
sram = 32 kbytes (64 in the case of a z64 sram backup)

see, now that wasn't so hard

[Girth]

Does this util work ONLY for V64jr? Not my liddle old Dr64?????

[LaC]

no thats dumb. use .eep or .sav this is the standard eeprom filename extension.
.ram or .sra for sram or flash. and .mpk for mempacks.

[fab]

I agree with LaC; there's already a "standard" naming of save types.

As far as WT_Riker's suggestion that someone put together a common place (website) where SAVES can be consolidated and updated in a timely fasion, I nominate elitendo (I've got nothing better to do). I'll be revamping the save section tonight, so send any saves you have to saves@elitendo.com.

--
fab

[arrid]

There's a new Evek that supports 16kbit EEPROM?

[breathes in]

WOOOOOOOOOOOOOO HOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOOOOOO..........

[4 hours later]

.........OOOOOOOOOOOOOOOO!! http://www.dextrose.com/ubb/smile.gif

[Darkflame]

Well actually I doubt there would be a problem for us z64 users....after all, we are already running a ibm system on our z64's...all we need is someone to rewrite the program so that it will use the z64's internal cartridge routines to write the file...just a matter of time and patience...then we could have the z64 load the file and execute it from there, then again, i've never seen evek II so I don't know if it would fit, if anything, could just stick it on the disk and run it from there....who knows...

[marsares]

It seems no one here have an idea of what associate an extension with a command means.

you HAVE to differentiate 4K from 16K, sram from flashram since evekII have different param for each.

exemple of my rom assoc :

---------ROM.REG-----------------
REGEDIT4

[HKEY_CLASSES_ROOT\.v64]
@="ROMN64"

[HKEY_CLASSES_ROOT\.rom]
@="ROMN64"

[HKEY_CLASSES_ROOT\.z64]
@="ROMN64"

[HKEY_CLASSES_ROOT\ROMN64]
@="ROM N64"

[HKEY_CLASSES_ROOT\ROMN64\DefaultIcon]
@="C:\\BURO\\Emul.dll,40"

[HKEY_CLASSES_ROOT\ROMN64\shell]

[HKEY_CLASSES_ROOT\ROMN64\shell\Send]
[HKEY_CLASSES_ROOT\ROMN64\shell\Send\command]
@="SENDV64J.BAT %1 "
; @="elim.exe \"%1\" --nocrc "
; @="elim.exe \"%1\" --nocrc --verify"

[HKEY_CLASSES_ROOT\ROMN64\shell\SendVerif]
[HKEY_CLASSES_ROOT\ROMN64\shell\SendVerif\command]
@="SENDV64J.BAT \"%1\" --verify "
; @="elim.exe \"%1\" --nocrc --verify"
; @="jrsend.exe \"%1\""

[HKEY_CLASSES_ROOT\ROMN64\shell\SendFIX]
[HKEY_CLASSES_ROOT\ROMN64\shell\SendFIX\command]
@="PALSEND.BAT %1 /f"

[HKEY_CLASSES_ROOT\ROMN64\shell\SendFIXPAL]
[HKEY_CLASSES_ROOT\ROMN64\shell\SendFIXPAL\command]
@="PALSEND.BAT %1 /p /f"
---------------------------------------

------------SENDV64J.BAT---------------
@echo off
rem Automatically apply existing patch
rem Before sending with elim

if exist %1.aps goto APSPresent
goto NoAPS

:APSPresent
elim.exe %1 -p %1.aps --nocrc %2
goto fin


:NoAPS
elim.exe %1 --nocrc %2
goto fin

:fin
echo on
-----------------------------------