tested it on my pal n64 with 1.23 f2 U loads with force sram i still am to test save but how far into the game do i need to get to test it? If u give me a guideline ill give it a test and see if it maintains save. will have to get f1 pal and try that for you also.
mine booted fine tried about 5 times turning on machine and off again to make sure i didnt make any mistakes. but now i have played through 3% of it and saved it wont load anymore with force sram will try deleting the save and see if it works again. Edit : ok before it loaded 5 times in a row now it loaded about 1 in 5 other times locked up at dextrose but it still loads randomly and no idea why.
Okay, now i can say for sure, the PAL F1 Boot & Save Version works very well with force SRAM, played 6:30h with several times turn on off my n64 to test, the save is still there, seems no problem @ all. I'am @ ED64 V1 FW 1.2 OS 1.23 =)
OS1.23; same MD5 Checksum. I retried it without any luck so far. I also forced SRam and pressed Start. Strange, since the game remembers my selected language. //Edit// I formatted my SD Card and downloaded a new copy of OS1.23. This time I saved the game 3 times at the beginning and reseted the console. This save has not yet been deleted as of now. I will play through level 1 and save 3 times again. Maybe it works thus time.
Hey krikzz, dk64 won't load for me unless I'm using force sram 128. Using the f2 U rom. Also, not sure if os 1.23 broke jet force gemini? Before sometimes it would take a couple resets to get JFG working but I've reset 5 times and it keeps freezing on the dextrose screen.
U F2 does not boot on PAL when you have OS1.22 or 1.23. It boots fine with 1.21 and below when using Force SRAM ( Not 128). PAL F1 Save and Boot works when using Force SRam and Pressing Start every time you load the game. Try saving a few times before you press Reset, then the save game should backup fine.
yeah, runs only because forced sram for DK does not work at all in 1.21. i said many times, but looks like nobody wants to hear me
Did SRam work on 1.13, or not at all before 1.23? Please do not get me wrong. I am very thankful for your work and my knowledge of how everything works is very limited. I just wanted to get the NTSC game working on the pal system and since it did not work for me, I tried to find out why. When I read that the U F2 was working for some other people, I thought that I must have something wrong. When OS 1.13 booted it, I thought that it was a Software problem. I did really not want to annoy you, just tried to find bugs. Do you think that because of the Fix the US Rom does not work on Pal or should the [!] EEP16K version also not boot?
just try to save with os 1.13 and you will see if sram saves works or not. i belive that impossible to run DK f2 U on pal system in case if sram works fine, so better forget about this idea and use E version. DK f2 U + ntsc n64 + sram = all fine DK f2 U + pal n64 + sram = hang on dextrose intro DK f2 U + pal n64 + buggy sram, or dissabled sram = game works, but not save at all or use eeprom for save DK f1 E + pal n64 + sram = happiness? by te way, results can be different for ED64 v1 and v2, cuz v1 can not load new firmware with new OS from SD. so new OS for v1 is a just new OS, but new OS for v2 it is new OS + new firmware
Thank you for the constant support and updates! Are you still planning on working on a faster SD driver for ED rev 1.01? Not that I can really complain, my ED works great. It's just that it would give me a reason to use my newly built Altera Bus Blaster clone! Thanks!
Just to clarify Krikzz, I'm using U roms on NTSC system with 1.23 and dk64 freezes with force sram. So DK f2 U + ntsc n64 + sram = freeze for me anyway. It works with sram128 but I don't know if it saves. Also, JFG won't load (U rom as well). It would load on 1.22 with a couple resets usually. I guess I'm going back to 1.22 Edit: Ok now this is weird. When I put the new OS on my SD card yesterday, at first I got the screen saying my OS was missing when I booted my everdrive. So I popped the SD card back in and re-arranged the file structure of the ED64 folder. Then it booted. Then thats when DK64 with sram would lock up at Dextrose as well as JFG. I went and re-arranged the files once again tonight and tried DK64 with SRAM, and what do you know? It boots! However, I'm still getting lockups with JFG. I'm gonna rearrange some more and see if I can get them both to boot. Very strange?
Well as I said I now have dk64 working after arranging some files. I still can't get JFG to boot. I tried formatting the SD card but it still won't boot. I also noticed after formatting that it takes longer at the "initializing SD" screen.
OS scans fat system to find free cluster when need to create some file or dir. some condition may slow down this operation. some of them: 1) small cluster size 2) tonns of files on SD occupy a lot of free space in beginning of sd space. simple tricks may accelerate initialization a lot. for example i can put huge dummy file before than copy roms on sd card, then copy all roms and after that delete those dummy file. after this trick i still have a lot of free space in beginning of sd card. and of course i always choose 32kbyte cluster size when i formatting my sd cards, or biggest available, in case if i can't choice 32kb
hi krikzz, did you remember the sram loading error in 1.21 you fixed 1.22 - i have some sort of that save issue in 1.23 again my converted "super smash brohters" sram savegame in loading fine if i save in "kirby 64" a eep savegame it's ok, too but if i save in "ocarina of time" the savegame is written on the sd card but it's not loading if i start the game same issue on c&c a fla game could you please take a look at it? ^^ cheers saturnu
amazing fast as always edit: after testing: - i can't save anymore :> i think the old savegame hasn't been overwritten
