[Amiga] Amiberry + WHDLoad = Holy Grail - Amiberry's official thread

Marcoqwerty

@dudleydes said in [Amiga] Amiberry + WHDLoad = Holy Grail - Amiberry's official thread:

@marcoqwerty said in [Amiga] Amiberry + WHDLoad = Holy Grail - Amiberry's official thread:

but nothing was created (symlinks) in the dev folder

How are you checking this? If I use SAMBA shares, then the /amiberry/whdboot/save-data/Kickstarts folder is empty apart from the foo.txt file. If I check via the command line, then I see the symlinks:

It may be worth checking the contents of this folder on your system using the command line.

Thank you i will check on this way, im quite noob on these "linux tricks", i had checked files from WinSCP, maybe for that reason i did not find anything.
I should check these after pressing RESCAN PATH right?

It may also be worth checking the systems ROMs path in Amiberry by bringing up the configuration screen (press hotkey+X on a controller or F12 on a keyboard) and navigating to the Paths section. For reference, mine is /opt/retropie/emulators/amiberry/kickstarts which is the default when I first installed Amiberry

In the wiki looks under BIOS folder, i setup it launching the AMIBERRY EMULATOR...after setting up the path i rescan and quit the emu.

https://github.com/midwan/amiberry/wiki/Using-Amiberry-WHDBooter-with-RetroPie-(Step-2)

Yes, Linux is case-sensitive so it would need to be kick34005.A500.

i should change to .A500 to .a500 , sorry for all these stupid questions!

DarishZone

Seems speaked too soon... some lha games works, some not and i get a black screen after whload setup... it gave me "setpatch not found", it is relevant?
Tried to change bios path toward kickstart folder and now i get a sinister Aros splashscreen "waiting for bootable media" :/

dudleydes

@darishzone Could you tell the name of the lha file? I can take a look at it.

EDIT: I get the setpatch not found message during the WHDLoad autoboot process for each game I have tried and each one works fine. I don't believe it's an issue.

DarishZone

@dudleydes said in [Amiga] Amiberry + WHDLoad = Holy Grail - Amiberry's official thread:

@darishzone Could you tell the name of the lha file? I can take a look at it.

EDIT: I get the setpatch not found message during the WHDLoad autoboot process for each game I have tried and each one works fine. I don't believe it's an issue.

I see, me too, but you never know.
Can't see if my setup is wrong or there's issues with my lha set, guess if some game run it would be ok with my conf.
Oh and the file is Rise of the Dragon
RiseOfTheDragon_v1.1_1793

dudleydes

@darishzone Which game isn't working for you?

DarishZone

Sorry, added the title later
RiseOfTheDragon_v1.1_1793

for now, but i guess others will follow...

DarishZone

It also relevant Amiberry logo before hdload autoboot is green... and often red?

dudleydes

@darishzone You are most likely missing the Kickstart 1.3 rom.

If you take a look at the Debug script for Rise of the Dragon which you can find in the /opt/retropie/configs/amiberry/whdboot/save-data/Debugs folder, you should find the following (repeated many times):

DOS-Error #205
(object not found)
on reading "devs:kickstarts/kick34005.a500".

kick34005.a500 refers to the Kickstart 1.3 rom. Please refer to this page in Amiberry wiki for further info.

You need to have this file in the BIOS folder. The file I have in the BIOS folder is Kickstart v1.3 rev 34.5 (1987)(Commodore)(A500-A1000-A2000-CDTV).rom. This Kickstart rom is also needed for other games, e.g. Another World, North and South.

The different coloured logo splashscreen is a bit of fun. See this post.

The setpatch not found can indeed be ignored - see this post from the dev.

DarishZone

@dudleydes said in [Amiga] Amiberry + WHDLoad = Holy Grail - Amiberry's official thread:

post

Very good, thanks, i can confirm error on debug folder.
I have "kick13.rom" on bios folder, not sure if it is the right one.
I also reinstalled Amiberry and deleted configs, so it all returned to default paths, which is opt/retropie/emulators/amiberry/kickstarts/
Seems to me this path correlate to bios folder.

dudleydes

@darishzone It may be worth checking which kickstart roms you have on your system and making sure that symlinks are being created accordingly.

Could you run the following commands?

Contents in BIOS Folder

cd RetroPie/BIOS
ls | grep -i kick

This is my output:

pi@retropie:~/RetroPie/BIOS $ ls | grep -i kick
Kickstart v1.3 rev 34.5 (1987)(Commodore)(A500-A1000-A2000-CDTV).rom
Kickstart v3.1 rev 40.68 (1993)(Commodore)(A1200).rom

Symlinks in Amiberry WHDBoot configs

cd /opt/retropie/configs/amiga/amiberry/whdboot/save-data/Kickstarts
ls -lah

This is my output:

pi@retropie:/opt/retropie/configs/amiga/amiberry/whdboot/save-data/Kickstarts $ ls -lah
total 24K
drwxr-xr-x 2 pi pi 4.0K Jun  1 07:34 .
drwxr-xr-x 6 pi pi 4.0K Apr 19 15:07 ..
-rw-r--r-- 1 pi pi    1 Apr 19 15:07 foo.txt
lrwxrwxrwx 1 pi pi  112 Jun  1 07:34 kick34005.A500 -> /opt/retropie/emulators/amiberry/kickstarts/Kickstart v1.3 rev 34.5 (1987)(Commodore)(A500-A1000-A2000-CDTV).rom
lrwxrwxrwx 1 pi pi   97 Apr 19 15:08 kick40068.A1200 -> /opt/retropie/emulators/amiberry/kickstarts/Kickstart v3.1 rev 40.68 (1993)(Commodore)(A1200).rom

DarishZone

I'm confused now, however i got this
alt text

dudleydes

@darishzone In the Kickstarts folder, is the entry for kick34005.A500 in red? If so, this means that the symlink is broken.

I can't see all of the kickstart roms in the BIOS folder. You only need the two kickstart roms in my previous post so could you remove all kickstarts from the BIOS folder except these two and confirm that there are present by running the ls | grep -i kick command in the BIOS folder?

DarishZone

dudleydes

@darishzone I renamed my 1.3 Kickstart rom to Kickstart 1.3.rom to match yours and it broke the symlink.

We may be able to fix this by renaming the kickstarts but before we do, we should check that they are valid. Drag your kickstart file into an online CRC32 checker such as this one and check that the values given match those given on this page.

If they do, then try changing the file names as given on the Amiberry Wiki page linked above.

If they don't, then you will need to find valid 1.3 and 3.1 kickstart roms, appropriately named.

DarishZone

Ok, i've done it, it reports following codes

Kickstart 1.3: f6290043
Kickstart 3.1: fc24ae0d

I don't know what i'm doing, lol, but i suspect those files are corrupted?

dudleydes

@darishzone OK, your kickstart roms are not valid and will not work with Amiberry.

Your 3.1 kickstart rom may be fine as the symlink is there and you say some games work. Does Cannon Fodder work?

You will need to find 1.3 kickstart rom. Look for the TOSEC archive.

DarishZone

It seems every game that dsnt use kickstart 1.3 works, otherwise i get black screen.

HoraceAndSpider

My suggestion:

Delete all symlink files
Add all kickstarts to bios/ folder
Load Amiberry straight to the menu with Amiberry.sh
Select the paths panel
Reset the kickstarts path to the bios/ folder
Press “scan paths”
Enter emulation.
Go back to the menu
Quit Amiberry

Relaunch a game with WHDLoad (.lha file)
Symlinks should be fixed

DarishZone

Tested Cannon Fodder, it works.

HoraceAndSpider

Symlinking for th WHDLoad booter doesn’t care what file names you have.

It hadn’t occurred to me to add a check for “broken” symlinks, but I will look into that