https://bugs.winehq.org/show_bug.cgi?id=48746
--- Comment #3 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Created attachment 66703 --> https://bugs.winehq.org/attachment.cgi?id=66703 nullDC 1.0.4 r136 backtrace wine 5.3
(In reply to starfirehyper from comment #2)
Not trying to be rude, but as I mentioned, I am running Crossover so that means I have no way of getting into the terminal. Is there a way to get to the terminal on Crossover? I have no idea how to get to the terminal and open it.
Hello,
--- quote from https://wiki.winehq.org/Bugs --- When to report a bug
You should report a bug when: (...) · You are not using a third party wrapper for Wine (e.g., Crossover, PlayOnLinux, PlayOnMac, Wineskin, Q4Wine, etc.) or custom patches. (...) --- end of quote ---
1. WineHQ.org doesn't offer support for CrossOver, so either someone confirm the issue with vanilla wine-devel/wine-staging (recent version), or you'll have to find support for CrossOver there: https://www.codeweavers.com/support
2. Unless the bug can be reproduced with vanilla wine-devel/wine-staging, it's pending to be resolved invalid.
3. I was not addressing you in particular. There may be other persons trying to run the application with Wine and experiencing the issue. Anyone affected by the issue stumbling on this bug can provide the required information.
4. Wine is a community and voluntary project. So users are expected to do as much diagnostic work as possible to give developers more time for actual development. If there is a free legal download of the application, a developer or contributor could try to reproduce the issue himself.
5. A few questions:
→ Is this the application? https://segaretro.org/NullDC
I tested that version. When I launch it, it opens a dialog about missing BIOS file and closes. Copying some distributed backup copy of bios files found on archive.org, I restarted the application, clicked on File → Normal Boot → No Disk, and got a crash.
→ Do you confirm that this reproduce the crash you reported?
→ Does the attached backtrace looks like what you get when you click on 'details' in the crash dialog?
If not, then use the 'details' button on the crash dialog, save the backtrace.txt file somewhere and then attach it to this bug.
Regards.