EverDrive Forum

General => EverDrive N8 => Topic started by: leosmendes on December 26, 2019, 05:01 PM

Title: Everdrive N8 with problems in version 1.20 (NOT SOLVED FOR ALL)
Post by: leosmendes on December 26, 2019, 05:01 PM
I am also having problems with version 1.20, constants IO erros making it almost impossible to load a rom with the 2gb sd patriot card, let some IO errors with 8gb sandisk. many IO errors when browsing folders with sd pratriot, and rarely, but happens, with sd sandisk . I have no problem with version 1.16. Whith the rom already loaded in memory, when the O.S. loads, pressing start had no problem running (for the time I tested). Have any sd card read and write routines changed in version 1.20? Igor, do you recommend any sd cards?
Title: Re: Everdrive N8 with problems in version 2.0
Post by: Link83 on December 26, 2019, 07:07 PM
Sorry but i'm having trouble understanding which EverDrive and OS your using?

OS v2.0 is only for the EverDrive N8 PRO, not the original EverDrive N8.

The last two OS revisions for the original EverDrive N8 are v1.16 and v1.20:-
http://krikzz.com/pub/support/everdrive-n8/original-series/OS/
Are these the two OS versions you meant?
Title: Re: Everdrive N8 with problems in version 1.20
Post by: leosmendes on December 26, 2019, 07:57 PM
Forgive me, I corrected my post
Title: Re: Everdrive N8 with problems in version 1.20
Post by: Aether Knight on December 27, 2019, 12:17 AM
One thing to note when upgrading the FW from to 1.16 to ANY of the test FW or the latest 1.20 is to not have the files copy and rewrite over old. The only thing you would want to save is the SAVE folder, so set that one aside and delete that entire EDFC folder and copy the new one to your card. After that, drop your previous SAVE folder and it *should run ok. I'm using an off-brand sd card but I've used Sandisk in the past and it seems to work fine.

One thing to note, and this may not affect you but I found the jump from 1.16 to 1.20 caused some of my save states to be all wonky. Looks like it's most of the Mega Man games. Others I've tried seem to load fine. These were all made from 1.16 FW. Save RAM on the other hand, seems to work fine as in previous FWs
Title: Re: Everdrive N8 with problems in version 1.20
Post by: leosmendes on December 27, 2019, 12:29 AM
I did a clean install, format, copied our operating system and then copied the roms on both cards
Title: Re: Everdrive N8 with problems in version 1.20
Post by: ubersaurus on December 27, 2019, 04:35 PM
I just wanted to hop in and say that I've also been having i/o errors on the menu that I didn't notice with 1.16 or the beta release candidates. Tried reformatting my SD card and still getting them.

Bought the unit from SAG last November, not sure which revision it is specifically but it is the Famicom version.
Title: Re: Everdrive N8 with problems in version 1.20
Post by: leosmendes on December 27, 2019, 11:50 PM
I just wanted to hop in and say that I've also been having i/o errors on the menu that I didn't notice with 1.16 or the beta release candidates. Tried reformatting my SD card and still getting them.

Bought the unit from SAG last November, not sure which revision it is specifically but it is the Famicom version.

I remember testing one of 1.20 betas version, and going through the same issues ... if they are still available I will do some test work from the first release to try to find a possible modification that may have caused these problems.
Title: Re: Everdrive N8 with problems in version 1.20
Post by: Torgod13 on December 28, 2019, 04:33 AM
No IO errors on my side but just ested a few roms and Tetris and Rampage boot to black screens.  Tried a few revisions of Tetris. All responded the same.
Title: Re: Everdrive N8 with problems in version 1.20
Post by: Torgod13 on December 28, 2019, 04:42 AM
Never mind...   Did a clean install.. all working.. Sorry :(
Title: Re: Everdrive N8 with problems in version 1.20
Post by: gda.balada on December 30, 2019, 02:27 AM
Is anyone else besides me having trouble with the save state function on N8 with version 1.20? Since I put the new version I can no longer save state in games.
Title: Re: Everdrive N8 with problems in version 1.20
Post by: leosmendes on December 30, 2019, 08:06 PM
Is anyone else besides me having trouble with the save state function on N8 with version 1.20? Since I put the new version I can no longer save state in games.
Ideally, back up the EDFC folder and erase the old one from the card before copying the new one, did you do this? as it has been reported that old save estates should not be compatible. Another detail is that you need to map the save buttons again. giving sequence, someone there would have backup betas versions?
Title: Re: Everdrive N8 with problems in version 1.20
Post by: Greg2600 on December 30, 2019, 08:37 PM
Never mind...   Did a clean install.. all working.. Sorry :(

Unfortunately ANY type of update has required me to reformat my SD card, which is unbelievably frustrating. 
Title: Re: Everdrive N8 with problems in version 1.20
Post by: KRIKzz on December 30, 2019, 11:04 PM
Never mind...   Did a clean install.. all working.. Sorry :(

Unfortunately ANY type of update has required me to reformat my SD card, which is unbelievably frustrating. 

Unfortunately OG N8 does not support mapper files fragmentation and this make such problems. Whole onboard memory not available during mapper reconfig and this is why OG-N8 can't handle file system fragmentation when it loads mapper. As compromise solution you may try to avoid files removing from SD, this prevent file system fragmentation. You can make folder like "OLD-OS" or something and move old files to this folder instead of removing.
Title: Re: Everdrive N8 with problems in version 1.20
Post by: leosmendes on January 11, 2020, 08:49 PM
problem apparently solved. I can't say why versions after 1.16 may require more from the SD card. only Igor could say what was changed after this release that could be causing this instability when reading and writing to SD. I could tell from my simple knowledge that something may have changed in the operating system that could force SD readings and writes above the speed previously performed. I tested with several SD cards, which may be suspicious as to quality or originality, here in Brazil, there are many fake cards, but they worked well with version 1.16. I found a card that looks like original sandisk, and with it version 1.20 and 1.23 is apparently working properly. I tested for some time and got no errors. version 1.23 is very interesting, with save state working correctly at least in the games I've tested, not getting a black screen when loading a save in some games. Thank you Igor and forum members.
Title: Re: Everdrive N8 with problems in version 1.20 (SOLVED)
Post by: ubersaurus on January 15, 2020, 03:28 AM
Unfortunately my issue is still happening. I replaced the micro SD card with a Sandisk 16gb SDHC one, which has reduced the number of errors to the point where I can actually use the thing, but I still got several error 62s and one error 51 while using it just now. I have no idea what the issue could be.
Title: Re: Everdrive N8 with problems in version 1.20 (SOLVED)
Post by: leosmendes on January 15, 2020, 04:26 AM
Unfortunately my issue is still happening. I replaced the micro SD card with a Sandisk 16gb SDHC one, which has reduced the number of errors to the point where I can actually use the thing, but I still got several error 62s and one error 51 while using it just now. I have no idea what the issue could be.
do you have problems with version 1.16?
Title: Re: Everdrive N8 with problems in version 1.20 (SOLVED)
Post by: ubersaurus on January 15, 2020, 08:47 PM
Unfortunately my issue is still happening. I replaced the micro SD card with a Sandisk 16gb SDHC one, which has reduced the number of errors to the point where I can actually use the thing, but I still got several error 62s and one error 51 while using it just now. I have no idea what the issue could be.
do you have problems with version 1.16?

Nope. Like I said in my first post, 1.16 works just fine, no errors. Not sure what changed between these versions that introduced these issues.