this post was submitted on 01 Sep 2024
27 points (96.6% liked)
techsupport
2469 readers
4 users here now
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No I mean read data out of the file with another program like a video player or emulator, or just open it in a text editor.
I was thinking this would test whether the problem is with reading from that NTFS partition, which the error message points to.
I just download the appimage version of duckstation on the Linux side to see if it could run the game but it was unable to find my games in the ROMs Directory. Then I tried going to System > Start File and When I tried to launch the game that way I got this error.
What is even more weird is that I was able to launch the copy on my ext4 partition despite the fact the the BIOS I selected is in the ntfs partition.
Edit: I just tried opening the BIN and CUE files from the ntfs partition and got on error saying that the file does not exist despite the file being visible from the file manager. I also noticed that the one on the ntfs partition had some lock icons while the ext4 one did not. I also saw a windows directory in the cue file on the windows C: drive which I found very weird because I usually store all my games on the D: drive of my system. The copy on my ext4 also how this Windows Directory.
How are you mounting your NTFS disk? If you're using the mount cli as root you may need to add the uid mount option
I mounted it using fstab
Ah definitely add some mount options to give yourself access, uid and gid would be a good place to start, I think there may be others.
Some info https://askubuntu.com/questions/113733/how-to-mount-a-ntfs-partition-in-etc-fstab
Thanks for linking me to the to this page. I did some more diging and I managed to figure out the actual problem. I was using a program called CompactGUI2 which allows you to use the NTFS file comprssion to save space. The minute I uncompressed the files from the Windows side I saw the Lock icons go away when I booted back into Linux.
Cool! That's new to me, thanks for sharing your solution!
I think the icons on NTFS mean your user does not have permitted read the bin file. I think the cue files need to have the path updated, but I'm not super familiar