28 Nov 2017, 00:05

@voljega said in [EMULATION] Amiga4Recalbox v0.8999999999, install in one click (or so):

@wulfman said in [EMULATION] Amiga4Recalbox v0.8999999999, install in one click (or so):

Custom/K, Custom1/K/N, Custom2/K/N, Custom3/K/N, Custom4/K/N, Custom5/K/N
These options are not used by WHDLoad itself, but can be tested by the Slave to control various Slave specific things. Custom/K can contain a string and Custom1-5/K can only hold an integer. Check the documentation of the specific install if it supports Custom options. "

please provide me the modified file with custom parameters used then.

ohhh i see ... custom isn't global optiion - it's local ... need to be set als parameter whdload game.slave preload; custom1=1 (untested! next few days)
your whdlGenerator.py: fStartupSeq.write("WHDload "+slaveFile+" Preload\n")
... that makes it even more complicated: ( I can't even think of an easy workaround - just quick&dirty ... 😞

But there was still something important in the file concerning savegames (the last few days I've read this several times). I'll test this for the next few days. With WHDload it is probably stored in the memory (?) and saved to file with exiting the program (see my Wings problem!).

To Wings: normally saved automatically. But also directly after the EARN WINGS. This doesn't happen here (and yes /tmp/amiga/whdload/data -> refresh is a very good friend of mine;).

I MUST kill uae4arm via SSH

There seems to be an issue when killing the emulator manually with the kill command, whdl games don't launch after that (unless you restart recalbox), but contrary to what you said files of previous/next games are not mixed up in the /tmp folder, please hit refresh before consulting it and confirm that it is the case.

Refresh is a good friend. 😉 But this problem was with your old install (sometimes it happends that an .adf copied into whdload-dir...). At the moment for this point no problem. The "question" was whether you are doing something different here than in the old version. If not, it is still vulnerable to error. But very hard to find it out 😐 [With the old installation the 5-6x happened ... in 2-3h testing!]

I think it's more an amiberry issue, didn't happen in the past on previous version of uae4arm or not exactly like that, but there was always an issue with this emulator, when it crash it can't manage to relaunch properly unless you relaunch the whole box

maybe you need to kill another task? I've already tried all those who looked clear - negative. Reboot is the best solution 😞 ...