Unsolved Amiga, Stand der Dinge?

[voljega]

@benuildo yes it seems to be still working on 4.1 and you can use still use my instructions to use it.

if they are too complicated for you, then you'll have to wait for official integration

[Wulfman]

@voljega said in Amiga, Stand der Dinge?:

@wulfman ok good

then if you modified line 88 in adflauncher.sh :

find "$romPath" -name "$prefix*" | sort | while read i

to :

find "$romPath" -maxdepth 0 -name "$prefix*" | sort | while read i

it should correct the bug. good catch !

WORKS! ... but ... for some reasons i've started a clean-install with Recalbox 4.1. I use your tut - your files (without any changes!)). No games won't start. Directly back to ES.

es_launch_stderr.log
rm: can't remove '/recalbox/share/ram/uae4arm/conf/adfdir.conf': No such file or directory
rm: can't remove '/recalbox/share/ram/uae4arm/conf/uaeconfig.uae': No such file or directory
./uae4arm: error while loading shared libraries: libsndfile.so.1: cannot open shared object file: No such file or directory

=> libsndfile.so.1 ?! Don't exist in your libs ...
=> can't remove ... you delete this files before create them. No Error.

I worked through the adflauncher.sh manually => no problems - until
./uae4arm
=> ./uae4arm: error while loading shared libraries: libsndfile.so.1: cannot open shared object file: No such file or directory

After the 4.1 >update< I had no problems. However, I noticed that the update is faulty (files were not copied etc.; kill gamepad-config etc.) so I made a clean-install (new microSD). Can it be that the update keeps the libsnd.1.o of 4.0.2, but cleaninstall doesn't have this file?

The 4.0.2 -> 4.1 MicroSD:
./uae4arm: /usr/lib/libasound.so.2: no version information available (required by /lib/libSDL-1.2.so.0)
./uae4arm: /usr/lib/libasound.so.2: no version information available (required by /lib/libSDL-1.2.so.0)
Amiberry build 2017-01-08, by Dimitris (MiDWaN) Panokostas and Olly Aigner
Works.

UPDATE
Recalbox 4.1 (update from 4.02)

find -name libsndfile.so.1 -maxdepth 100

./usr/lib/libsndfile.so.1

Recalbox 4.1 (cleaninstall)
find -name libsndfile.so.1 -maxdepth 100
=> nothing found

I've copied the libsndfile.so.1 from 4.02 to /usr/lib/ from 4.1
=> WORKs

Your Guide works only with 4.0x an update to 4.1. - not with clean install 4.1 ...

When is the official support coming?

[voljega]

@wulfman good catch again

Yes the version you're using was done for 4.0 and even started on 3.2..

Official integration is indeed coming somehow and much more stable and refined but maybe it's gonna take a while before recalbox team has time to look into it

If you know python a little and recalbox configgen too you can have an early glimpse of it on my github

[Wulfman]

I received requests for the file xxx. I will upload them somewhere today or tomorrow and post the link here.

If you still have an old Recalbox 4.02 lying around, you can copy the file from there by yourself. Path /usr/lib/ => libsndfile.so.1 ... Destination @ 4.1: /lib/

---

Mich erreichten Nachfragen zur libsndfile.so.1 ... ich lade diese heute oder morgen irgendwo hoch (vorher nicht in der nähe meiner recalbox) und stelle den Link dann hier ein.

Wer auf einer microSD noch die 4.02 hat, kann die sich dort selber rausziehen. Der Pfad: /usr/lib/libsndfile.so.1 .... Zielverzeichnis in 4.1 => /lib/

[Wulfman]

Hey

https://www.file-upload.net/download-12783351/libsndfile.so.7z.html

ONLY for Recalbox 4.1 cleaninstall. Update-Version from 4.0x to 4.1 has this file already!

1. download libsndfile.so.7z and extract
2. ssh (via WinSCP) to your Recalbox
3. /etc/init.d/S31emulationstation stop
4. mount -o remount, rw /
5. Copy libsndfile.so.1 to [ROOT]/lib/ ... [same directory which use by voljegas tutorial for "his" lib-Files]
6. shutdown -r now
   => Let's Play (i hope!)

@voljega : No ... i don't have know-how in python or configgen

Are "your" libs actually only used by uae? I unfortunately didn't check if something was "overwritten" during the upload... if the official support comes, I want to clean up /lib/G.

[voljega]

@wulfman yeah don't worry when the official support will come, uaerm binary will automatically draw its dependencies at compilation time, so no need to bother with missing libraries anymore

thank you for the lib

[danni]

Hi voljega, hubi, abunille, Wulfman and the others!

First of all I want to thank voljega for his work! I have read the whole thread, wich was very interesting.
Currently I am setting up a fresh install on a pi3 with 4.0.1 to get the amiga games runnig

I got a question regarding your guide @voljega :
"mkdir ram at /recalbox/share (this will be used by the script has a ram drive)" Does this mean, I have to create a directory named "mkdir" at the corresponding path?

Thank you for your help!
Danni

[abunille]

@danni

mkdir = make Directory
The Folder must have the name ram

[danni]

@abunille Aaaahhh, wie offensichtlich. hihi, danke!
Ich berichte später mal, ob es läuft.

[abunille]

@danni

lach
Viel Erfolg

[danni]

@abunille Hat super geklappt! Danke nochmal!

[abunille]

@danni

Gerne, viel Spaß beim zocken

[voljega]

@danni so I get everything's working fine then ?

[abunille]

@voljega

No, not only fine!
I would say, GREAT

[danni]

@voljega Yes, GREAT! :))) Thanks!

[voljega]

@danni cool ! Everything should be even simpler and more refined in a few months when official will finally come

[freaky69]

Hello Guys,

just one quick question. Do i need the original Amiga Roms to use @voljega exploit?? If not great. If yes i do have the original AMIGAFOREVER installed on my PC which contains the original Amiga Roms (500, 1200 aso)....

Any chance i could use them with recalbox? If yes how should they be renamed to work properly.

Excuse my bad english i'm a native german speaker

Noch mal auf Deutsch

Ich würde gerne wissen ob ich die originalen Amiga Roms benötige zum spielen? Wenn ja ich habe von Cloanta Amigaforever auf dem PC installiert und dort sind ja die originalen Roms enthalten. Kann ich die mit Recalbox benutzen? Wenn ja muss ich die irgendwie umbenennen???

Gruß

[abunille]

@freaky69

Guten Morgen,

in welchem Format liegen die Roms vor?
.adf und whdload sind kompatibel.

[freaky69]

@abunille Sorry for the missunderstanding... I meant BIOS Files for the AMIGA ;)... There Filename is .... .rom

[Wulfman]

Kickstart liegt dabei.