DICUI hangs at "Running any additional tools... please wait!" on IBM PC DOS disc #214

New Issue

claunia · 2026-01-29T16:12:04Z

claunia commented

2026-01-29 16:12:04 +00:00

Originally created by @xperia64 on GitHub (Aug 9, 2020).

Originally assigned to: @mnadareski on GitHub.

I have attempted to dump a IBM PC DOS game on my cross-flashed WH16NS40, and while the DiscImageCreator step succeeds, the "Running any additional tools... please wait!" step hangs the entire DICUI application (which I see in the source code shouldn't do anything except for Sega Saturn discs). Buttons completely unresponsive etc. There is activity on the drive LED during this process. If I leave it running long enough, DICUI closes entirely. If I eject the disc, DICUI continues successfully and prompts me to fill out the information to submit.

Originally created by @xperia64 on GitHub (Aug 9, 2020). Originally assigned to: @mnadareski on GitHub. I have attempted to dump a IBM PC DOS game on my cross-flashed WH16NS40, and while the DiscImageCreator step succeeds, the "Running any additional tools... please wait!" step hangs the entire DICUI application (which I see in the source code shouldn't do anything except for Sega Saturn discs). Buttons completely unresponsive etc. There is activity on the drive LED during this process. If I leave it running long enough, DICUI closes entirely. If I eject the disc, DICUI continues successfully and prompts me to fill out the information to submit.

claunia added the wontfix question labels 2026-01-29 16:12:04 +00:00

claunia closed this issue

2026-01-29 16:12:04 +00:00

claunia commented

2026-01-29 16:12:05 +00:00

@mnadareski commented on GitHub (Aug 9, 2020):

This has come up quite a few times, and I've answered it all of those times. Copy protection scan, especially on older versions, would appear to freeze the application as it scanned. With discs that had a large enough number of files and/or a system with relatively little RAM, this would cause issues which could include DICUI crashing. More recent stable and WIP versions have alleviated that somewhat due to changes in design, including making it so the scanning should not freeze anything now.

With the above being said, copy protection scanning can just be turned off and something like PiD can be used after. It's not a required step. Please look at the options menu for more details.

@mnadareski commented on GitHub (Aug 9, 2020): This has come up quite a few times, and I've answered it all of those times. Copy protection scan, especially on older versions, would appear to freeze the application as it scanned. With discs that had a large enough number of files and/or a system with relatively little RAM, this would cause issues which could include DICUI crashing. More recent stable and WIP versions have alleviated that somewhat due to changes in design, including making it so the scanning should not freeze anything now. With the above being said, copy protection scanning can just be turned off and something like PiD can be used after. It's not a required step. Please look at the options menu for more details.

claunia commented

2026-01-29 16:12:06 +00:00

@xperia64 commented on GitHub (Aug 9, 2020):

Ah yeah, the AppVeyor builds work fine, and the disc I was dumping did indeed have many small files.

Still not sure why the old version crashed as it shouldn't have been anywhere close to OOMing, but I'll take it.

@xperia64 commented on GitHub (Aug 9, 2020): Ah yeah, the AppVeyor builds work fine, and the disc I was dumping did indeed have many small files. Still not sure why the old version crashed as it shouldn't have been anywhere close to OOMing, but I'll take it.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SabreTools/MPF#214