MiSTer-devel / ZXNext_MISTer

GNU General Public License v2.0
27 stars 12 forks source link

Error writing configuration after resolution selection #4

Open Paradox opened 3 years ago

Paradox commented 3 years ago

This only happens when boot.vhd is in usb0/games/ZXNext/ works fine in fat/games/ZXNext/ and, since i keep all my roms/games on usb and only use SD for cores, this is a big deal, for me. I use the 8GB card that came with the MiSTer, and, don't have room to keep a 2GB (or bigger) file there.

sorgelig commented 3 years ago

try this version: ZXNext_3.zip

Paradox commented 3 years ago

Sorry, I've been really busy, and didn't check back, is this included in the latest release, or do I still need to try it?

Paradox commented 3 years ago

Just updated, and tested the new release, same issue, so, I'll try this, and see if it helps.

Paradox commented 3 years ago

Tried it, and, didn't change a thing.

sorgelig commented 3 years ago

i don't know what causes this issue. I also use USB (USB stick 512GB) for ZXNext and don't have this issue (even before fix). So it's unclear what causes this issue. Need to gather more info about it.

Paradox commented 3 years ago

Well, since you are using a flash drive, it's still solid state, like the sd card, try with an external 2.5" mechanical hdd, which is what I use.

antoniefourie commented 3 years ago

Hi @sorgelig,

Here is more detail:

On release 20210409 (Test:30110.xyz.VGA0+memExt 2.06N of the specnext core), VHD on primary SD:

Create a Basic file save save to the VHD/specnext root, the following error appears:

"Not ready, 0:1"

The file is listed in the Browser but is inaccessible.

Replaced 20210409 with 20210407 core:

Create a new Basic file and it is saved normally. It can also be reloaded from the Browser.

When attempting to access the file created with the previous core, the following error is displayed:

"b Wrong file type, 0:1"

Note: I updated Mister prior to this test.

Rushor commented 2 years ago

@Paradox you are still interested in trinitycore?

ArKay74 commented 2 years ago

Nearly 1 year has passed, issue still seems to exist? It does for me. Maybe it has to do with the filesystem used on the external drive? I formatted mine with ext4 since a FAT filesystem always was corrupted when I checked it on my PC. Not very reassuring.