World Class Leaderbord HD issue

[StingRay]

Originally Posted by malko

Working like a charm, Sting. Thank you
Snoopdos don't even see the patch

My pleasure. Source can be found on my Github: PatchClose_WCLB.s

It may be interesting for people who need to patch dos.library functions on 1.xx machines.

[malko]

Here is a preview of an icon I have created for the occasion of this working HD version (used as a "disk.info") .
It is still a WIP though but will make it available when it will be ready (cf: FaeryTale Adventure & Dragon's Lair icons)


Adapted the "world class" text from the megadrive version ; slightly adapted a free font for "leaderboard" & a free image of a golf ball.

[malko]

Sting, I got a strange error* while creating a script (iconx) to launch the patch & the game.

* patch.68k failed returncode 12845056
(the number changes if I change the amount of RAM)

configuration A500 (1MB+512slow) - with the patch, the game doesn't load anymore with 512 + 512.

The first time I launch the script, only the message is displayed.
The second time, there is a software failure and then a GURU.



Since this crash the patch is not working anymore. When I load it manually from a shell, there is no error, but the game acts like without the patch...

I then have created a fresh HDF and reinstalled everything (have kept the patch to check if it get corrupted with the crash). No, working.

Do you have any idea why there is this returncode and error while loading the patch from a script ?

[StingRay]

Originally Posted by malko

configuration A500 (1MB+512slow) - with the patch, the game doesn't load anymore with 512 + 512.

Not true. The patch occupies the whopping amount of 18 bytes of memory.
I had no problem running the game from HD with 512+512 config.

Originally Posted by malko

Do you have any idea why there is this returncode and error while loading the patch from a script ?

Replace the patch with attached one. It will fix the return code error and also checks if it already has been installed and if so simply won't do anything, this fixes the crash.

[malko]

Originally Posted by StingRay

Not true. The patch occupies the whopping amount of 18 bytes of memory.
I had no problem running the game from HD with 512+512 config. [...]

I think some rewording is necessary : the game loads but display a message regarding ram fragmentation and it exits.
If it's not happening on your side, I am jealous...

Originally Posted by StingRay

[...] Replace the patch with attached one. It will fix the return code error and also checks if it already has been installed and if so simply won't do anything, this fixes the crash.

Thank you will do it this evenin when I return home

[StingRay]

Originally Posted by malko

I think some rewording is necessary : the game loads but display a message regarding ram fragmentation and it exits.
If it's not happening on your side, I am jealous...

There must be another reason for this. At least I can't see how the patch which requires 268 bytes when loaded and 18 bytes permanent memory causes memory fragmentation. I can play the game without any problem using 512k chip and 512k fast. I assume you may have too many things loaded when your workbench boots up which causes this problem.

[malko]

Returned from an excellent family week-end
Did some test with the new patch and it's working nicely Sting. No more crashes .
Again, a big thank you

Regarding the 512chip+512slow(or fast) message provided by the game while using the patch, the message is still appearing on my side.
Even gave a try with a the startup-sequence from the floppy disk and a single startup-sequence containing only "LoadWB & endcli". Still the message...

But for now, it's no big deal as my usual config is, as was my old A2000, 2MB chip + 8MB fast, and I can play WCLB from HD with your patch

[StingRay]

Originally Posted by malko

Again, a big thank you

My pleasure.

Regarding the 512chip+512slow(or fast) message provided by the game while using the patch, the message is still appearing on my side.

This actually makes me believe the game also has some bugs regarding memory allocation and free memory checks. I may have a look if I'm in the mood for a boring debugging session. If I find some problems with the memory handling routines I'll update the patch to fix these as well.

[malko]

Would be cool, but no hurry