ED64 Plus... my impressions. Any Owners around here?

kuwanger

Well-Known Member
Member
Joined
Jul 26, 2006
Messages
1,510
Trophies
0
XP
1,783
Country
United States
always wondered why most of the flash carts wont write the save file in real time. when the hardware sees a write it should dump it as the game is saving. Or alteast dump the sram written data to the sd card after the save is completed.

The simplest guess explanation comes in three parts: it was probably easier, cheaper, and safer. It was easier because it meant simply patching games to have consistent save types or having the hardware support different save types natively then writing the load/save routine entirely in the boot loader in software. Having to do it in real time means either stealing CPU cycles from the CPU to do the writes or having the necessary hardware on the cart to do it behind the CPU's back. The former risks incompatibilities and the latter requires more expensive, complex hardware*. Both also might require a second save buffer (when RAM wasn't cheap) so you wouldn't get a mixed save--not really sure since if it's stealing CPU time it can just delay further progress in the game until the save is written. The last part is writing to SD, especially on a slow CPU, can take a while so the risk of corruption goes up a lot. It's really hard to do any sort of sanity checks*. To be really safe you'd want something like a capacitor in the cart to hold enough charge to fully do the write to SD even if power was suddenly lost*.

The ds flash carts have real time saves....

The DS, unlikely most systems, doesn't directly map a ROM into the memory area. Hence the whole interface is predicated upon streaming content in from the cartridge and writing out content. Hence, it's conducive to having wait checks in allowing a flash cart to write out a save and say "everything saved fine". It also discourages constant writes to save memory. Basically, DS games behave more like CD-ROM games or cassette games so can get around most the hassle of direct rom/ram mapping. I presume these properties hold true for most modern systems, even those which have built-in storage.

* The EZ Omega actually uses an FPGA to writes saves behind the CPUs back, but it still has issues because some games want to save near constantly. Hence some games are patched. It's also why it's such a headache for saves on the EZ Omega. You basically need something like multiple scratch files with hashes, you always have to worry about partial/mixed saves, and a power loss can cause massive filesystem corruption. And that's presuming you're not having issues like bad/questoinable contacts--which has seem to plague the EZ-Flash cards forever.
 

MrCokeacola

The Xbox Guy
Member
Joined
Feb 26, 2018
Messages
939
Trophies
0
XP
2,067
Country
Canada
Hi All,


Ok so I just picked up two of these ED64Plus carts with the N and P switch on top.

It came preloaded with the Chinese firmware and roms.

It boots perfectly and plays games on a USA console, but does absolutely nothing on a PAL console.

I've tried the NTSC and PAL switch for each console, but literally nothing happens on the PAL hardware.... Yes the pal console boots genuine games fine.


I bought two carts for this kinda reason, in case one was faulty but both work fine on NTSC.

Is there a trick to this for PAL hardware?

PS. I also tried the custom firmware option... same result.

thanks
Stupid question but are you trying to boot PAL roms or NTSC roms on the PAL console?
 

bbsan2k

Well-Known Member
Newcomer
Joined
Jul 6, 2019
Messages
83
Trophies
0
Age
34
XP
1,444
Country
Germany
I'll give it a test on my ED64+ when I get the chance.

--------------------- MERGED ---------------------------

Screen of static follow by black screen. Didn't work for me.
Damn OK then there might be something else that is breaking compatibility...

EDIT:
Could somebody please try, whether the original release of altra is booting up on the plus? If so, my build might just have some toolmaking issues
 
Last edited by bbsan2k,

gtranche

New Member
Newbie
Joined
Jan 21, 2017
Messages
2
Trophies
0
Age
41
XP
59
Country
France
Altra works on ED64+, for PAL rom you have to go in settings (right cross) and activate PAL for TV and sometime force NTSC or PAL mode, even if it's PAL rom sometime NTSC works.
I have a problem with long filename .... if the filename is more than 64 caracs the rom won't load ...
 
  • Like
Reactions: bbsan2k

bbsan2k

Well-Known Member
Newcomer
Joined
Jul 6, 2019
Messages
83
Trophies
0
Age
34
XP
1,444
Country
Germany
Altra works on ED64+, for PAL rom you have to go in settings (right cross) and activate PAL for TV and sometime force NTSC or PAL mode, even if it's PAL rom sometime NTSC works.
I have a problem with long filename .... if the filename is more than 64 caracs the rom won't load ...
Hey,
Did you try the version I linked above or the original version?
 

bbsan2k

Well-Known Member
Newcomer
Joined
Jul 6, 2019
Messages
83
Trophies
0
Age
34
XP
1,444
Country
Germany
the original version.
What is the protection you talk about ?
It’s the thing that saturnu mentioned some posts earlier. If you try to flash to SRAM, it will probably corrupt half the way through it, as there is some check for the existence of the OS64p file (which is only there on ed64+)
I‘m gonna try compiling the latest release version again, as I just compiled the HEAD version from altra64 git
 

bbsan2k

Well-Known Member
Newcomer
Joined
Jul 6, 2019
Messages
83
Trophies
0
Age
34
XP
1,444
Country
Germany
Hey everybody,
I just re-build again 2 versions:
#1 (altra64_bbsan) is my latest build with complete removal of the lockout
#2 (altra64_nwfusion) is networkfusions latest build + simple removal of the lockout

Would someone please try if it works and report back?
Thanks a lot!

Please note:
AFAIK you need to rename the OS64.v64 into OS64P.v64 to use it with ed64p
 

Attachments

  • altra64_bbsan.zip
    2.5 MB · Views: 369
  • altra64_nwfusion.zip
    2.5 MB · Views: 293

MrCokeacola

The Xbox Guy
Member
Joined
Feb 26, 2018
Messages
939
Trophies
0
XP
2,067
Country
Canada
I don't know if it was user error but I could not get both to work. I renamed the one main V64 file but didn't touch the other 3 files just copied them over.

bbsan: Was not detected at all brought to boot files not found screen
nwfusion: just a black screen

edit: tried bbsan again and got a black screen
 
Last edited by MrCokeacola,

enarky

owls?
Member
Joined
Jul 31, 2003
Messages
1,239
Trophies
2
XP
2,335
Country
Afghanistan
Hey everybody,
I just re-build again 2 versions:
#1 (altra64_bbsan) is my latest build with complete removal of the lockout
#2 (altra64_nwfusion) is networkfusions latest build + simple removal of the lockout

Would someone please try if it works and report back?
Thanks a lot!

Please note:
AFAIK you need to rename the OS64.v64 into OS64P.v64 to use it with ed64p
Looking forward to the results, currently away for work for the week but will definitely try it saturday. I have the original ED64+ with cart slot on top and installed an UltraCIC myself.
 

bbsan2k

Well-Known Member
Newcomer
Joined
Jul 6, 2019
Messages
83
Trophies
0
Age
34
XP
1,444
Country
Germany
I don't know if it was user error but I could not get both to work. I renamed the one main V64 file but didn't touch the other 3 files just copied them over.

bbsan: Was not detected at all brought to boot files not found screen
nwfusion: just a black screen

edit: tried bbsan again and got a black screen
Ok, then I don‘t have a clue what could be wrong. Maybe some issues with my build system, but debugging this without a working ED64P will not be possible for me.
That’s a shame:/

If anybody is getting different results with these build, please keep me posted.
Eventually something else might be missing on the SD card, so maybe someone can first try to use official (e.g. not built by me) altra release and confirm it working and try my build afterwards.
 

MrCokeacola

The Xbox Guy
Member
Joined
Feb 26, 2018
Messages
939
Trophies
0
XP
2,067
Country
Canada
Ok, then I don‘t have a clue what could be wrong. Maybe some issues with my build system, but debugging this without a working ED64P will not be possible for me.
That’s a shame:/

If anybody is getting different results with these build, please keep me posted.
Eventually something else might be missing on the SD card, so maybe someone can first try to use official (e.g. not built by me) altra release and confirm it working and try my build afterwards.
If you could just to make sure it's not user error could you give me the whole ED64P folder with all files needed and renamed.
 

enarky

owls?
Member
Joined
Jul 31, 2003
Messages
1,239
Trophies
2
XP
2,335
Country
Afghanistan
Could
Hey everybody,
I just re-build again 2 versions:
#1 (altra64_bbsan) is my latest build with complete removal of the lockout
#2 (altra64_nwfusion) is networkfusions latest build + simple removal of the lockout

Would someone please try if it works and report back?
Thanks a lot!

Please note:
AFAIK you need to rename the OS64.v64 into OS64P.v64 to use it with ed64p
Couldn't get it to work, either. I used the Alt64 configuration I still had from the reddit post. Keep in mind I used an original ED64+ that's not very compatible with the patched Alt64 Firmware, though.
 
  • Like
Reactions: MrCokeacola

bbsan2k

Well-Known Member
Newcomer
Joined
Jul 6, 2019
Messages
83
Trophies
0
Age
34
XP
1,444
Country
Germany
Hmmm I also don't have a complete SD card file structure at hand for this, but over all this should be working in the same structure the previous alt64 was working.
If it doesn't, I guess there may still be sth wrong with my compiler setup - but if so I think I need to step back from this, as without having an ed64+ it doesn't make sense for me to continue.

@enarky @MrCokeacola : Do you have expansion pack installed? Has the previous alt64 (not by me) build worked for you?

Btw:
If there's anybody with a Everdrive v3 or 2.5, please go ahead and test this as well, as if it is working with those, there may be something "wrong" with the altra64 on Everdrive v1/ed64+ at all.
 

bbsan2k

Well-Known Member
Newcomer
Joined
Jul 6, 2019
Messages
83
Trophies
0
Age
34
XP
1,444
Country
Germany
1:Keep the ed64p folder with the os.z64 in it at sd card root

2Download and extract the alt64 files and drag and drop the folders onto the root of your sd

3: Copy the OS64.v64 file from the ED64 folder and paste it into the ED64P folder, then with the OS64P.V64 file, rename it to anything you want

4:With OS64.v64 file from the ed64 folder file rename it to OS64P.V64

This somehow trick the cart into loading the alt64 or official everdrive os's

You need to do the quoted above to setup an environment for altra
 
  • Like
Reactions: MrCokeacola

MrCokeacola

The Xbox Guy
Member
Joined
Feb 26, 2018
Messages
939
Trophies
0
XP
2,067
Country
Canada
You need to do the quoted above to setup an environment for altra
Tried putting the files on the root, their own alt64 folder and in the ED64P folder. Black screens all around for both versions.
Edit; Re-read the thread again. Grabbed the files from this video.

Replaced them with the new files. It works but still the same issue as before I can't for the life of me figure out where Alt64 puts its saves I put my old saves in the saves folder but it doesn't use them and I don't see it generating a new save file anywhere else. Oh well a new mystery.
 
Last edited by MrCokeacola,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    SylverReZ @ SylverReZ: Looks like a Famicom handheld