Menu

#1650 GTK3 3.6 fails with bounty bob strikes back, SDL2 ok

v3.6
closed-invalid
nobody
None
GTK3
x64sc
2021-12-30
2021-12-28
No

x64sc.exe - 3.6.0 (GTK3 3.24.31, GLib 2.70.2, Cairo 1.17.4, Pango 1.50.2)
Windows 10 x86_64 (64-bit)

OS info:
Edition Windows 10 Pro
Version 20H2
OS build 19042.1415
Experience Windows Feature Experience Pack 120.2212.3920.0

Using: https://sourceforge.net/projects/vice-emu/files/releases/binaries/windows/GTK3VICE-3.6-win64.zip/download

Attempting to run: https://www.kryoflux.com/download/BOUNTYBOBSTRIKESBACK.zip

set file to read-only in OS, attach g64 as read-only in Vice, also tried smart-attach, with and without autostart, or manual load,8,1 - all have same results

BBSB starts to load but then gives a "checksum error" at "code segments remaining: 75"
100% reproduceable.

However: SDL2 3.6 - https://sourceforge.net/projects/vice-emu/files/releases/binaries/windows/SDL2VICE-3.6-win64.zip/download

The SDL2 version of Vice works perfectly with the same BBSB image, same settings.

Discussion

  • Dan Gahlinger

    Dan Gahlinger - 2021-12-29

    adding log file just created

     
  • Marco van den Heuvel

    can you also please do a log for the sdl2 version you tried

     
  • Dan Gahlinger

    Dan Gahlinger - 2021-12-29

    Attaching log from 3.6 SDL - which works

     
  • Marco van den Heuvel

    The configs are not the same, for gtk3 there is a lot more already configured, please try gtk3 version again and use -default in the command line.

     
  • Dan Gahlinger

    Dan Gahlinger - 2021-12-29

    Ok, that's just spooky...

    I did -default and it all worked on gtk 3.6 so I then reran 3.6 gtk again and reset to defaults and of course it worked still.
    But then i changed the settings again to what I like:
    c64 (ntsc), 1541 instead of 1541-II, turn on drive sound emulation, etc.
    I even re-enabled the drive ram and parallel cable stuff

    and it still works!

    So since I didn't save my settings before resetting I'll never know what it was, nor do I care at this point

    I can NO longer replicate the issue - so close the ticket, resolved. My machine is haunted. :)
    thank you!

     
  • Marco van den Heuvel

    • status: open --> closed-invalid
     
  • Marco van den Heuvel

    thank you for taking the time to provide the logs, some people just post a bug and do not want to provide any further information or details to figure out if it is a bug and where the bug might be.

     

Log in to post a comment.