lr-px68k Multidisk games problem

KrinaSam

@mitu this is all I found in the runcommand.log file. There is nothing else.

mitu

@krinasam said in lr-px68k Multidisk games problem:

.There is nothing else.

There should be - how are you looking/viewing the file ?

KrinaSam

@mitu said in lr-px68k Multidisk games problem:

There should be - how are you looking/viewing the file ?

WinSCP

mitu

Do you have enough disc space left on your sdcard ?
WinSCP should be able to look/transfer the file, try doing it after exiting RetroArch.

KrinaSam

@mitu I have enough disk space. After exiting retroarch, the contents of the file are the same. Can you show me yours runcommand.log file?

mitu

@krinasam said in lr-px68k Multidisk games problem:

Can you show me yours runcommand.log file?

It should look similar to this, including the messages showing the core shutdown:

...
[INFO] [Core]: Unloading core..
[INFO] [Core]: Unloading core symbols..

Your log stops before the core is loaded/game is started.

KrinaSam

@mitu I tried to run another system (psx) and runcommand.log looks like yours. It looks like lr-px68k doesn't write to the runcommand.log file.
in retroarch/options/logging i set verbose logging and logging to file.
/opt/retropie/configs.hdmi/all/retroarch/logs/retroarch.log
this is log when game won't run:
link text
and this is log file when i removed read permission, and game loads correct:
link text
I don't see any difference

mitu

I suspect the the folder override you saved for x68000 has an impact on the behavior and the logging file being smaller:

...
[INFO] [Overrides]: Content dir-specific overrides found at "/home/pi/.config/retroarch/config/PX68K/x68000.cfg".
...

Can you try renaming the file, just for testing, to see if this changes the core's behavior ?

KrinaSam

@mitu you were right. after deleting a file, the log is saved correctly. But this does not fix the problem with the sram.dat file

mitu

That was kind of expected and it looks like a core issue.
The logs show that the disc images are properly set into FDD0/FDD1, so the only explanation for your problem would be that the sram.dat is corrupted between games.
As a workaround, you could delete the sram.dat file between runs, using an onstart script for runcommand.

KrinaSam

@mitu Thank you for help. Could you please help me with the nds drastic emulator in my other thread?link text

mitu

@krinasam I'm not familiar with drastic, maybe other forum user has an idea.