lr-px68k Multidisk games problem
-
@krinasam said in lr-px68k Multidisk games problem:
I must remove read access permission to pi user and game runs correctly
Then something else is broken in your setup, the emulators (including RetroArch) should always run as the
pi
user, so read/write access for thepi
user is normal.runcommand.log it is the same in both cases
That's not the entire log, just the beginning of it. Use pastebin.com if you wish to post the entire file.
-
@mitu this is all I found in the runcommand.log file. There is nothing else.
-
@krinasam said in lr-px68k Multidisk games problem:
.There is nothing else.
There should be - how are you looking/viewing the file ?
-
@mitu said in lr-px68k Multidisk games problem:
There should be - how are you looking/viewing the file ?
WinSCP
-
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. -
@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?
-
@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.
-
@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 -
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 ?
-
@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
-
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 thesram.dat
is corrupted between games.
As a workaround, you could delete thesram.dat
file between runs, using anonstart
script for runcommand. -
-
@krinasam I'm not familiar with
drastic
, maybe other forum user has an idea.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.