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

mitu

@mr-spoc Re-read the installation instructions and follow them, you've not executed the qt installation steps.

Mr Spoc

@mitu you are right i though i had done that step 2 months ago but its missing. I sciped it if thinking if i do sudo aptget update too the update my mess with my setup? In any case i will now back my SD up and try.

mitu

@mr-spoc apt-get update will not update any programs, it will only refresh the list of available packages so that apt-get has the correct list of package versions available.

Mr Spoc

@mitu @AnalogHero thanks for the support it is now scraping i hope it will finish soon.
When i run Skyscraper with no arguments i answred the questions about the cache with "No" and the question about video with "No" as all i want are the game cover pics or the games schreenshots and a basic description if they exist.
Whilst the Scyscraper is running now though i can see the following:
For any given game that Skyscraper has "found !" I get:
..............
"Cover: NO ()"
"Screenshot: NO ()"
"Wheel: NO ()"
"Marquee: NO ()"
All the games that Skyscraper found info for have the above lines. The tools has been running for almost 3 hours now i hate to see at the end that i have no game picures like a cover or a schreenshot for the games that Skyscraper found?

AnalogHero

@mr-spoc In simple mode Skyscraper will run several times using different sources.
For Amiga its OpenRetro, thegamesDB, screenscraper, and a final run with localdb. If you have a large collection of games or a slow internet connection, or maybe the servers of the databases are slow atm it can take a while.

If a source has not all metadata available, Skyscraper can still use bits and pieces it has collected (in some cases only a game name or a description). In the final localsb run it put all the data cached before together.

Mr Spoc

@analoghero thank you this is very useful to know. It all worked fine at the end and Skyscraper found images for 90% of the games. I am happy with that result.
@all this is a great forum that u for all the help.

Marcoqwerty

Anybody can run Amiberry directly with .lha files?

Can explain me how to test this trought command line? where put .lha files?

Actually i'm working some demo games with config (.uae mode with RetroPieAmigaSetup script) files, but i have hear from the developer this is no longer supported, so im looking to test this new option trought command line and after try to setup with Attract Mode front-end.

- Attract come lauch RUNCOMMAND

Generated by Attract-Mode v2.3.0

executable /opt/retropie/supplementary/runcommand/runcommand.sh
args 0 SYS amiga "[romfilename]"
rompath /home/pi/RetroPie/roms/amiga
romext .adf;.adz;.dms;.ipf;.lha;.sh;.uae;.zip;.ADF;.ADZ;.DMS;.IPF;.LHA;.SH;.UAE;.ZIP
artwork flyer $HOME/1a/boxart
artwork marquee
artwork snap $HOME/1a/videos;$HOME/1a/snap
artwork wheel

Runcommand launch AMIBERRY

amiberry = "/opt/retropie/emulators/amiberry/amiberry.sh -autowhdload=%ROM%"

I see the amiga Kickstart and stop

Log or retropie

Parameters: Executing: /opt/retropie/emulators/amiberry/amiberry.sh -autowhdload="/home/pi/RetroPie/roms/amiga/Capone_v1.1.lha"

Im totally lost, if i can check a way to test if AMIBERRY works correctly outside ATTRACT MODE i can investigate more about "how"to launch it trought attract mode!

DarishZone

I managed to install only by dragging the unpacked folders on WHDLoad folder, then generating uae files with autoconfig, no way to make it work lha files for me...

HoraceAndSpider

@darishzone @Marcoqwerty

The LHA files work “out of the box” if you install the latest Amiberry.

Perhaps you need to change some of your emulator paths (see the “paths” panel) back to the defaults. If you are using pre-built images etc then maybe hat is the problem.

If people are having issues they need to describe exactly what they have done, provide screenshots, demonstrate they are using up to date files and everything.

Quite simply, we wouldn’t release a feature of it just plain didnt work - I am using this system on no less that 3 different Pis now.

There is an extensive guide on this feature:

https://github.com/midwan/amiberry/wiki/Using-Amiberry-WHDBooter-with-RetroPie

Plus an FAQ:

https://github.com/midwan/amiberry/wiki/WHDLoad-Booter-(WHDBooter)-F.A.Q.

HoraceAndSpider

@dudleydes I have estabilished that the problem with North & South is the same as Jaguar XJ 220 , and is a bug in the WHDLoad slave, which is not 'friendly' to the booter.

I have reported this here:

http://mantis.whdload.de/view.php?id=3880

You can probably manully fix this by changing DATA="whdloadgame:NorthAndSouthImage/ to DATA="whdloadgame:NorthAndSouthImage/data on the WHDLoad exectution line in the north and south autoboot file. (NorthAndSouthImage.auto-startup)

DarishZone

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

@darishzone @Marcoqwerty

The LHA files work “out of the box” if you install the latest Amiberry.

Perhaps you need to change some of your emulator paths (see the “paths” panel) back to the defaults. If you are using pre-built images etc then maybe hat is the problem.

If people are having issues they need to describe exactly what they have done, provide screenshots, demonstrate they are using up to date files and everything.

Quite simply, we wouldn’t release a feature of it just plain didnt work - I am using this system on no less that 3 different Pis now.

There is an extensive guide on this feature:

https://github.com/midwan/amiberry/wiki/Using-Amiberry-WHDBooter-with-RetroPie

Plus an FAQ:

https://github.com/midwan/amiberry/wiki/WHDLoad-Booter-(WHDBooter)-F.A.Q.

Thank you for your response, i think i'm using last Amiberry version (2.20), but i used a pre made install config which is eventually obsolete. I will check the link!

dudleydes

@horaceandspider Thanks for looking into this.

I tried your manual fix suggestion, editing the autoboot file, and it worked fine.

Marcoqwerty

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

The LHA files work “out of the box” if you install the latest Amiberry.
Perhaps you need to change some of your emulator paths (see the “paths” panel) back to the defaults. If you are using pre-built images etc then maybe hat is the problem.
If people are having issues they need to describe exactly what they have done, provide screenshots, demonstrate they are using up to date files and everything.
Quite simply, we wouldn’t release a feature of it just plain didnt work - I am using this system on no less that 3 different Pis now.
There is an extensive guide on this feature:
https://github.com/midwan/amiberry/wiki/Using-Amiberry-WHDBooter-with-RetroPie
Plus an FAQ:
https://github.com/midwan/amiberry/wiki/WHDLoad-Booter-(WHDBooter)-F.A.Q.

There is a way to test "outside" frontend the correct launch of a game? trought cmd for example.

Can you make an example? just to be sure all the setting are correct and the issue not depends from the front-end.

Thank you for the link!

HoraceAndSpider

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

Can you make an example? just to be sure all the setting are correct and the issue not depends from the front-end.

cd /opt/retropie/emulators/amiberry/
./amiberry autowhdload="/home/pi/RetroPie/roms/amiga/Capone_v1.1.lha"

DarishZone

I've resolved the issue, now Amiberry start lha files like a charm, thank you.
Is so all the old install whdload system-uaeconfigmaker-autonistall obsolete?

Marcoqwerty

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

./amiberry autowhdload="/home/pi/RetroPie/roms/amiga/Capone_v1.1.lha"

Ok done all the steps but when i RESCAN PATH (after put all the .rom in the right folder) no one symlinks were created.

( so i copy manually the file and rename if following the FAQ naming convention)
but
If i load the command line i get this error (sended trought PuTTY console):

SDL could not itialize! SDL_Error: Unable to open a console terminal
Internal error; file/main.cpp, line 665
Aborted

UPDATE: copied the file from Devs:Kickstarts. to save-data/Kickstarts and whdload start but i read on the startup screen SETPATCH NOT FOUND and after black screen.
I have seen the name of the game and no other error. (slave found and files created)

Marcoqwerty

I get this error from the only log i had found (Debugs\AnotherWorldIt.whdscript_debug):

on reading "devs:kickstarts/kick34005.a500".
DOS-Error #219

I've made a quick search on internet and i look in the dev folder (i have all the files who needer for load amiberry) (also copied from the same PC EMULATOR Winuae).

The axtensiona and the names are correct ( .PAT .RTB .rom and no extension like amiga-os-120.rom )

What files i should need on the devs:kickstarts/ folder?

dudleydes

@marcoqwerty Do you have the Kickstart 1.3 rom in the BIOS folder? Check the Amiberry wiki for the file name you require.

Marcoqwerty

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

@marcoqwerty Do you have the Kickstart 1.3 rom in the BIOS folder? Check the Amiberry wiki for the file name you require.

Yes...i have all the Kistarts in the BIOS folder, but nothing was created (symlinks) in the dev folder, i have been copied manually the files in this folder.
This file is been found, if i removing it i get NOT FOUND on the log, maybe is not correct or missing some other Kickstarts...i will copy again new Kickstarters and rename these like the links.
Software is case sensitive? kick34005.A500 is different from kick34005.a500

I apologize all this mess, i had installed tons of emulators also Amiga likes, but i never had mess with these f***** kickstarters.

I'm sorry for the huge amount of these topics!

dudleydes

@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:

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

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

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

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

I agree Kickstart files can be frustrating but, after using FS-UAE on my desktop, I have found Amiberry on RetroPie to be as close to a plug-and-play Amiga experience as it's possible to get. Credit to the devs for this.