Skip to content

[DOS] BizHawk crashes on the next session after preserving a high-volume HDD #4296

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

Closed
MoskovchenkoD opened this issue Apr 25, 2025 · 1 comment · Fixed by #4294
Closed

[DOS] BizHawk crashes on the next session after preserving a high-volume HDD #4296

MoskovchenkoD opened this issue Apr 25, 2025 · 1 comment · Fixed by #4294
Labels
Core: DOSBox-X MS-DOS/Win9x and PC-98 core Repro: Fixed/added in 2.10.1 dev Fixed in dev builds, see readme for download

Comments

@MoskovchenkoD
Copy link

MoskovchenkoD commented Apr 25, 2025

Summary

BizHawk crashes on the next session after preserving a big HDD (504 Mb and above).

Repro

  1. Launch DOS (DOSBox-X) core using any game (CD or floppy image)
  2. In the menu bar, select "DOS"
  3. Set "Preserve Hard Disk Contents" to True and "Mount Writable Hard Disk Drive" to "504 Mb (FAT16)".
  4. Reset the core or re-launch Bizhawk and select a DOS game (repeat point 1)
  5. Wait for a while. The core launches in ~25 secs and throws an exception in a few seconds.

I tried typing DOS commands, installing games again and launching games (if those were installed in the initial session), but this exception is still thrown.
I also tried recording Bizhawk movies:

  1. In movie 1 from "Power-on (clean)" I install the game, save the movie and exit Bizhawk.
  2. In movie 2 from SaveRAM, I try to do... whatever. Even if I manage to launch the game in slow motion, the exception is still thrown.

Note: for smaller HDD volumes (21, 41 or 241 Mbs), this issue doesn't reproduce.

Output

System.InvalidOperationException: Waterbox Error: Callback signaled abnormal failure
   at BizHawk.Emulation.Cores.Waterbox.WaterboxHostNative.ReturnData.GetDataOrThrow() in /src/BizHawk.Emulation.Cores/Waterbox/WaterboxHostNative.cs:line 21
   at BizHawk.Emulation.Cores.Waterbox.WaterboxHost.SaveStateBinary(BinaryWriter bw) in /src/BizHawk.Emulation.Cores/Waterbox/WaterboxHost.cs:line 349
   at BizHawk.Emulation.Cores.Waterbox.WaterboxCore.SaveStateBinary(BinaryWriter writer) in /src/BizHawk.Emulation.Cores/Waterbox/WaterboxCore.cs:line 304
   at BizHawk.Client.Common.ZwinderBuffer.Capture(Int32 frame, Action`1 callback, Action`1 indexInvalidated, Boolean force) in /src/BizHawk.Client.Common/rewind/ZwinderBuffer.cs:line 243
   at BizHawk.Client.Common.Zwinder.Capture(Int32 frame) in /src/BizHawk.Client.Common/rewind/Zwinder.cs:line 61
   at BizHawk.Client.EmuHawk.MainForm.CaptureRewind(Boolean suppressCaptureRewind) in /src/BizHawk.Client.EmuHawk/MainForm.cs:line 4510
   at BizHawk.Client.EmuHawk.MainForm.StepRunLoop_Core(Boolean force) in /src/BizHawk.Client.EmuHawk/MainForm.cs:line 3138
   at BizHawk.Client.EmuHawk.MainForm.ProgramRunLoop() in /src/BizHawk.Client.EmuHawk/MainForm.cs:line 954
   at BizHawk.Client.EmuHawk.Program.SubMain(String[] args) in /src/BizHawk.Client.EmuHawk/Program.cs:line 385

Host env.

  • BizHawk 2.10.1 dev build at 236ff74; Win10 Pro 22H2; AMD/Nvidia

Demonstration Video

@SergioMartin86

This comment has been minimized.

@YoshiRulz YoshiRulz added Repro: Fixed/added in branch/fork Repro: Affects 2.10.1 dev Reproducible in current dev builds Core: DOSBox-X MS-DOS/Win9x and PC-98 core labels Apr 25, 2025
@YoshiRulz YoshiRulz linked a pull request Apr 29, 2025 that will close this issue
13 tasks
@YoshiRulz YoshiRulz added Repro: Fixed/added in 2.10.1 dev Fixed in dev builds, see readme for download and removed Repro: Fixed/added in branch/fork Repro: Affects 2.10.1 dev Reproducible in current dev builds labels Apr 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core: DOSBox-X MS-DOS/Win9x and PC-98 core Repro: Fixed/added in 2.10.1 dev Fixed in dev builds, see readme for download
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants