PCXT Zeliard Was Working but Now a Strange Bug Is Happening

[Texemosis]

Ever since there's been updates to PCXT, my Zeliard copy does a strange thing. I boot it up, the core stays frozen on the Dos bios, but I can hear the games music playing. I don't know how that happened, but it did.

[spark2k06]

From which release onwards did it stop working?

https://github.com/MiSTer-devel/PCXT_Mi ... n/releases

[Texemosis]

ah, that I don't know for sure. It was working for me on the first official release, then I got back to it after at least three updates happened.

[Texemosis]

okay I pinpointed it down. slight correction, my setup with Zeliard was working at update 20220821. After that, the updates made it so my VHD's wouldn't boot in Tandy mode anymore and that's when I couldn't launch Zeliard properly.

[spark2k06]

You are totally wrong, the game works correctly with the latest core version:

20220908_060307-screen.png (600.06 KiB) Viewed 1484 times

Please check the game configuration file (resource.cfg), and make sure that the TGA video card is selected:

Code: Select all

videoDrv:TGA

[Texemosis]

yeah that's the Tandy graphics card right? I used to be able to boot this game up in Tandy core setting before. I don't think the core likes something with my VHDs though because it stopped kicking those VHDs up in Tandy core settings. Time for me to find out what Dos command opens up the cfg file.

[Hodor]

yeah that's the Tandy graphics card right? I used to be able to boot this game up in Tandy core setting before. I don't think the core likes something with my VHDs though because it stopped kicking those VHDs up in Tandy core settings. Time for me to find out what Dos command opens up the cfg file.

It´s pretty easy: edit XXXX.cfg

[Texemosis]

maybe the version of Dos I have is different and doesn't work with that command line but anyways I have some good news. When I goofed off with settings on the MiSTer core menu, the issue was resolved and I don't know exactly what I did. It might have been after I switch my VHD to the IBM Dos 7 instead of the MS-Dos 622. However, after I switched back to MS-Dos 622, the problem stopped existing there as well. It could've been when I changed my bios setting.