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.

Sign up for GitHub

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

Jump to bottom

Manager doesn't detect when a VM gets paused directly in 86Box #19

Closed
dhrdlicka opened this issue Oct 22, 2018 · 3 comments
Closed

Manager doesn't detect when a VM gets paused directly in 86Box #19

dhrdlicka opened this issue Oct 22, 2018 · 3 comments
Assignees
@daviunic
Labels
bug Something isn't working
Milestone
Version 1.1

Comments

@dhrdlicka
Copy link
Contributor

dhrdlicka commented Oct 22, 2018 •
edited
Loading

When a VM gets paused directly in 86Box, its status is still STATUS_RUNNING.

Furthermore, when the Manager's pause button is used on such Schrödinger's VM, the status gets updated to STATUS_PAUSED, but the machine actually gets unpaused.
@daviunic
Copy link
Contributor

daviunic commented Oct 23, 2018 •
edited
Loading

This happens because Window Message communication is a one way street apparently. If I could check some return value to see what state the VM is in on the 86Box side, that'd be nice. I'll look into this, though it will probably require some changes in 86Box as well.

@daviunic daviunic self-assigned this Oct 23, 2018
@daviunic daviunic added the bug Something isn't working label Oct 23, 2018
@daviunic
Copy link
Contributor

A temporary workaround is to not pause VMs in 86Box, only in the Manager, until something can be done about this. It's also easy to get out of this state if the Pause button in Manager is showing the wrong text. Just pause the VM in 86Box again, then resume it in Manager and it'll sync again.

@daviunic daviunic added this to the Version 1.1 milestone Oct 26, 2018
@daviunic
Copy link
Contributor

Fixed in 1.1.0. Because this required changes in both Manager and 86Box itself, the minimum required build of 86Box has been increased to 1799.

daviunic added a commit that referenced this issue Oct 26, 2018
@daviunic
First minor feature release
4abfbf8 
Added feature from issue #20.
Added features from issue #7.
Added -S command line argument to start a VM directly.
Added the option to reset settings to their default values.
Fixed issue #19.
Fixed issue #21.
Fixed a problem with displaying the version number in About dialog.
Various other UI and code enhancements.
notBald pushed a commit to notBald/Avalonia86 that referenced this issue Jan 7, 2025
@daviunic
First minor feature release
a8775b8 
Added feature from issue 86Box#20.
Added features from issue #7.
Added -S command line argument to start a VM directly.
Added the option to reset settings to their default values.
Fixed issue 86Box#19.
Fixed issue 86Box#21.
Fixed a problem with displaying the version number in About dialog.
Various other UI and code enhancements.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@daviunic daviunic

Labels
bug Something isn't working
Projects
None yet
Milestone
Version 1.1
Development

No branches or pull requests
2 participants
@dhrdlicka @daviunic