Valve/Proton
1
0
Fork 0
mirror of https://github.com/ValveSoftware/Proton.git synced 2025-02-05 02:00:44 +03:00
Code Issues Packages Projects Releases Wiki Activity

NTFS read errors: A semikolon isn't an invalid char; rephrased it to be more clear; added link with more details

DanMan 2022-05-02 12:31:26 +02:00
parent e0524828df
commit 642af5f8e5
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Using-a-NTFS-disk-with-Linux-and-Windows.md

@ -87,9 +87,9 @@ To prevent that, consider to disable it. Example tutorial: [PassFab: Disable Fas
## Preventing NTFS Read Errors
**THERE HAS BEEN A REPORT THAT THIS MAY CAUSE DATA LOSS**
Due to the nature of NTFS, creating files/folders with characters Windows cannot read will cause disk errors (leading to games that don't launch), the most common issue is a `;` character in filenames that Proton creates on the NTFS disk.
Due to the nature of NTFS, creating [files/folders with names that are invalid on Windows](https://docs.microsoft.com/windows/win32/fileio/naming-a-file#naming-conventions) will cause disk errors (leading to games that don't launch). The most common issue is a `:` (colon) character in filenames that Proton creates on the NTFS disk.
Fixing this is pretty simple. Create a symlink from the `/compatdata` folder on Linux to the mounted NTFS disk.
Fixing this is pretty simple: create the `/compatdata` folder on the mounted NTFS disk as a symlink that points to a folder on a Linux partition.
Creating the symlink:
@ -100,9 +100,9 @@ $ ln -s ~/.steam/steam/steamapps/compatdata /media/gamedisk/Steam/steamapps/
*If the `/compatdata` folder already exists on the mounted disk BEFORE the symlink, DELETE IT!*
## Turning off Case-Sensitivity in file names
## Turning off case-sensitivity in file names
Sometimes Case-Sensitivity can be an issue and lead to files not being found, because their names differ in case from what is expected. In such cases, mounting the ntfs partition with `lowntfs-3g` may solve the problem (source: https://serverfault.com/questions/901855/ntfs-3g-ignore-case).
Sometimes case-sensitivity can be an issue and lead to files not being found, because their names differ in case from what is expected. In such cases, mounting the NTFS partition with `lowntfs-3g` may solve the problem (source: https://serverfault.com/questions/901855/ntfs-3g-ignore-case).
To do that, edit the entry in `/etc/fstab` as follows:
```