| Re: [hatari-devel] Relocation warning + program failing when run from GEMDOS HD |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Relocation warning + program failing when run from GEMDOS HD
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Sun, 25 Sep 2022 08:58:45 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1664096327; bh=38fDWLEOA2ye1td0EO7gsAKQv4ZfkXH/EonlRmhZ4G8=; h=Date:From:To:Subject:From; b=fZyDcGV3ACGf2qZcrs47HU8zLTMV550M60P9Ze8083J18ryGhhKjjuYb+LO0zR2UV EBn6+TkwtZu23aGZhhuDzNvpXWPR0xA1dNTXrvoQg6f9+976UutaSV3a1FXZqlRaYf JQQw9L3Zk6O2n8/XU3tVLyCU9ig2DwvPrNA1ENvND26VOGL8csei9/Pp9+lI47m9qj 1FpiaXV0Q0322lwRp4zJnxGF6r/vn0Upj27OLxtckrwKEq7umCyTK1v/jurXl2lajx jgNZKYCdzp6OCv6llvcd2iN1yB4FN40eeaAn08ykn+jn2FPQmGvZVUptLrWbDNIf/f IyfKAa/+aDr6Q==
Am Sat, 24 Sep 2022 20:51:46 +0300
schrieb Eero Tamminen <oak@xxxxxxxxxxxxxx>:
> Hi Thomas,
>
> I found a program that may not work correctly with the GEMDOS HD
> relocation code. It's the "c64_show" from "Mono collection #01":
> https://www.pouet.net/prod.php?which=54828
>
> I've attached that monocrome slideshow program here. Its pictures are
> not included (to keep zip size <100KB), but they're loaded after the
> issue happens, so that should not matter.
>
> Currently program works only with real TOS v1.0x, and only when loaded
> from a floppy disk.
>
> When run from GEMDOS HD, program exits instead, after Hatari gives
> relocation warning:
> -------------------------
> GEMDOS 0x4B Pexec(0, "C:\C64_SHOW.PRG", [0]"", 0x0) at PC 0xFDD2DA
> GEMDOS 0x4B Pexec(5, 0x0, 0xa542, 0x0) at PC 0xFA003A
> C64 SLIDESHOWV1.0 LOADING ! GEMDOS 0x4B Pexec(0,
> "C64_DATA.BSW", [0]"", 0x12824) at PC 0x125D2
> GEMDOS 0x4B Pexec(5, 0x0, 0x12824, 0x12824) at PC 0xFA003A
> ERROR: Failed to parse relocation table of 'c64_data.bsw'.
Which version of Hatari are you using? That error message has been removed
more than a year ago already. I assume it has been fixed with the related
commit 22798befdd7462b01 ... can you please check with current version from
the master branch instead?
Thomas