Backyard Baseball 2001 is immediately crashing in Wine on a black screen: https://paste.debian.net/1294999

This is on a dedicated 32-bit prefix with DirectPlay only installed via winetricks. The prefix is set to claim to be Windows 98. The exact same disc is confirmed to work if mounted in 86box (running Windows 2000)

Just before the crash, a printer error is thrown. The printer works fine in Linux, but such an error shouldn’t crash the game like this. And also, printing is not an integral part of the game (you can print an image of your team, but its optional.)

The game appears as Platinum rated on Wine AppDB: https://appdb.winehq.org/objectManager.php?sClass=application&iId=9088

I will add here. Apparently, I have fixed it by finding a workaround. Shutting down cups with sudo service stop cups has made the game run.

  • olof@lemmy.ml
    5·
    1 year ago

    Reading the logs, im curious what happens if you unplug the MG2900LAN printer? It seems to me as well to cause the crash.

    • SSUPII@sopuli.xyzOP
      5·
      1 year ago

      I will add here. Apparently, I have fixed it by finding a workaround. Shutting down cups with sudo service stop cups has made the game run.

    • SSUPII@sopuli.xyzOP
      1·
      1 year ago

      I don’t know why but ScummVM runs extremely poorly on my system. Despite it not being weak or old, audio is just very corrupted/distorted. Also, a couple of old games I tried in the past lost some features (like my copy of Sam and Max Hit the Road not rendering subtitles in ScummVM)

  • dark_stang@beehaw.orgEnglish
    3·
    1 year ago

    Wireless printers didn’t exist when this game came out. Network printers weren’t really a thing in homes. I wonder if it’s trying to probe the printer for some details, like margins or paper size, and crashes due to latency.

    Edit: Have you tried removing/renaming the wineps.drv file in this bottle?

    • SSUPII@sopuli.xyzOP
      1·
      1 year ago

      The game crashes instantly, so maybe not latency. Maybe a valid workaround would be to actually turn on the wireless printer, as all my tests were done with the printer turned off. That actually makes sense.

      When I will be able to again I will try to remove the driver too.