Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VDFS: Changing VDFS root isn't kept if the emulator doesn't exit cleanly #202

Open
mark-usher opened this issue Jun 2, 2023 · 2 comments

Comments

@mark-usher
Copy link

mark-usher commented Jun 2, 2023

If the VDFS root is changed it is not remembered by the emulator until the emulator is cleanly shut down. Thus if the VDFS root is changed, a program is run and it crashes, the emulator needs to have the VDFS root changed again when restarting.

@mark-usher mark-usher changed the title VDFS: Changing VDFS root doesn't read in the inf file for the root VDFS: Changing VDFS root isn't kept if the emulator doesn't exit cleanly Jun 2, 2023
@SteveFosdick
Copy link
Collaborator

I have pushed a commit, a55f951, to save the config file after a change of VDFS root. There are lots of other settings that are also not immediately saved - saving the config usually happens on exit and immediately before a change of model to the model-specific ROM config can be saved.

If you have found a reproducible way to crash the emulator itself so the config file is not saved then that would be worth reporting as a bug.

@mark-usher
Copy link
Author

Thank you Steve. Primarily it is a bad program in development crashing the emulator as it would a real machine, rather than the emulator itself. The other scenario was if the PC goes into sleep mode, the emulator shuts down and the settings aren't saved. Serves me right for not staying at the computer longer. Would it be possible for the VDFS root selection dialog box to open at the currently selected location, or if not available the B-em directory?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants