Can't go into C: folder

[orbiterrr]

Trying to access my save game, but when I go into the dosdevices folder, only the Z folder can be opened. For some reason the C folder has the "there's nothing associated with this file type" icon. When I try to force dolphin to open it, I get a "the folder doesn't exist" error

[thetargos]

You have to go into the drive_c directory in a higher level rather than the synlink to the 'c:' drive, Z: maps to the equivalent of / in Linux.

[orbiterrr]

Originalmente postado por thetargos:

You have to go into the drive_c directory in a higher level rather than the synlink to the 'c:' drive, Z: maps to the equivalent of / in Linux.

I understand all those words individually lol.

Sorry I should have specified that I'm very new to Linux (the deck is my first experience with the OS). Is their a way you could explain that like I'm a 5 year old?

Baring that, maybe a link you can throw my way that goes into the concept you're explaining?

[Mahjik]

Try this:

https://linuxhint.com/locate_linux_steam_game_file/#:~:text=All%20Steam%20Play%20prefixes%20are,%2Fsteamapps%2Fcompatdata%E2%80%9D%20directory.

[thetargos]

I will do my best.

You will often see interchangeably people calling Wine and Proton the same thing, while they are, think of them as different implementations of the same techologies. For all intents and purposes, all those concepts that apply to Wine also apply to Proton.

So Wine (and hence Proton) is a compatibility layer that implements Windows specific system and application programming interfaces (APIs) under a different system, in this case Linux (but can be any other version of Unix or similar). Since in the great majority of cases, the underlying hardware is the same (x86-[64] based computers), there is no real "emulation" involved.

With that out of the way I hope you can understand a bit easier how it is implemented. So basically these programs present to the application you want to run, a kind of Windows environment (filesystem and directory structure), which is simply a directory in your hard drive (it can be in any location) and the instance of the program (wine or Proton) that runs the application you want to execute, presents the environment in a given directory (any directory). These are called prefixes There are some defaults, for instance, in the case of wine, the default prefix is located at the root of the user's home directory and it is simply called .wine (in Linux and Unix[-like] OSes, a dot preceding a name makes the file or directory hidden)

You can have multiple prefixes (and actually is the preferred way to run applications) since the fixes or tweaking tailored specifically for one application, can brake others, so it is usually advised to use one prefix per application. And that is exactly what Proton does, though it does it in a specific location within the Steam directory hieriarchy, which is in a directory called compatdata located at the same level of the common directory within steamapps. The default (though these paths can change) is usually ~/.steam/steam/steamapps/compatdata, here the ~/ is a shortcut for /home/$USER/ ($USER is the evaluation of the variable USER, so in this context the $ tells the contents of the USER variable). There the different prefixes are arranged by their Steam APP ID number, so a given game will have its prefix in the form of APPID/pfx.

In order to access the prefix (and hence save data, configuration, etc) of individual games, you have to access the prefix of said game in the aforementioned path.

Edit
Just noticed that I missed that within the pfx directory (the actuall "prefix") you will fiund an assortment of files and directories some .reg files which are what they look like, and refer to different registry options, and a directory called drive_c, which is the ewquivalent of the C: drive for that prefix. The special directory dosdevices contain links for other drives, usually the c: drive is a link to the upper drive_c, but not always

I hope this information is not too complicated (yes, it is complex in that it is different from Windows, but rather simple in its underlying logic.)

[orbiterrr]

Originalmente postado por thetargos:

I will do my best.

You will often see interchangeably people calling Wine and Proton the same thing, while they are, think of them as different implementations of the same techologies. For all intents and purposes, all those concepts that apply to Wine also apply to Proton.

So Wine (and hence Proton) is a compatibility layer that implements Windows specific system and application programming interfaces (APIs) under a different system, in this case Linux (but can be any other version of Unix or similar). Since in the great majority of cases, the underlying hardware is the same (x86-[64] based computers), there is no real "emulation" involved.

With that out of the way I hope you can understand a bit easier how it is implemented. So basically these programs present to the application you want to run, a kind of Windows environment (filesystem and directory structure), which is simply a directory in your hard drive (it can be in any location) and the instance of the program (wine or Proton) that runs the application you want to execute, presents the environment in a given directory (any directory). These are called prefixes There are some defaults, for instance, in the case of wine, the default prefix is located at the root of the user's home directory and it is simply called .wine (in Linux and Unix[-like] OSes, a dot preceding a name makes the file or directory hidden)

You can have multiple prefixes (and actually is the preferred way to run applications) since the fixes or tweaking tailored specifically for one application, can brake others, so it is usually advised to use one prefix per application. And that is exactly what Proton does, though it does it in a specific location within the Steam directory hieriarchy, which is in a directory called compatdata located at the same level of the common directory within steamapps. The default (though these paths can change) is usually ~/.steam/steam/steamapps/compatdata, here the ~/ is a shortcut for /home/$USER/ ($USER is the evaluation of the variable USER, so in this context the $ tells the contents of the USER variable). There the different prefixes are arranged by their Steam APP ID number, so a given game will have its prefix in the form of APPID/pfx.

In order to access the prefix (and hence save data, configuration, etc) of individual games, you have to access the prefix of said game in the aforementioned path.

Edit
Just noticed that I missed that within the pfx directory (the actuall "prefix") you will fiund an assortment of files and directories some .reg files which are what they look like, and refer to different registry options, and a directory called drive_c, which is the ewquivalent of the C: drive for that prefix. The special directory dosdevices contain links for other drives, usually the c: drive is a link to the upper drive_c, but not always

I hope this information is not too complicated (yes, it is complex in that it is different from Windows, but rather simple in its underlying logic.)

Thank you for this!!!!

Lots of great information and very easy to follow.

[orbiterrr]

Originalmente postado por thetargos:

I will do my best.

You will often see interchangeably people calling Wine and Proton the same thing, while they are, think of them as different implementations of the same techologies. For all intents and purposes, all those concepts that apply to Wine also apply to Proton.

So Wine (and hence Proton) is a compatibility layer that implements Windows specific system and application programming interfaces (APIs) under a different system, in this case Linux (but can be any other version of Unix or similar). Since in the great majority of cases, the underlying hardware is the same (x86-[64] based computers), there is no real "emulation" involved.

With that out of the way I hope you can understand a bit easier how it is implemented. So basically these programs present to the application you want to run, a kind of Windows environment (filesystem and directory structure), which is simply a directory in your hard drive (it can be in any location) and the instance of the program (wine or Proton) that runs the application you want to execute, presents the environment in a given directory (any directory). These are called prefixes There are some defaults, for instance, in the case of wine, the default prefix is located at the root of the user's home directory and it is simply called .wine (in Linux and Unix[-like] OSes, a dot preceding a name makes the file or directory hidden)

You can have multiple prefixes (and actually is the preferred way to run applications) since the fixes or tweaking tailored specifically for one application, can brake others, so it is usually advised to use one prefix per application. And that is exactly what Proton does, though it does it in a specific location within the Steam directory hieriarchy, which is in a directory called compatdata located at the same level of the common directory within steamapps. The default (though these paths can change) is usually ~/.steam/steam/steamapps/compatdata, here the ~/ is a shortcut for /home/$USER/ ($USER is the evaluation of the variable USER, so in this context the $ tells the contents of the USER variable). There the different prefixes are arranged by their Steam APP ID number, so a given game will have its prefix in the form of APPID/pfx.

In order to access the prefix (and hence save data, configuration, etc) of individual games, you have to access the prefix of said game in the aforementioned path.

Edit
Just noticed that I missed that within the pfx directory (the actuall "prefix") you will fiund an assortment of files and directories some .reg files which are what they look like, and refer to different registry options, and a directory called drive_c, which is the ewquivalent of the C: drive for that prefix. The special directory dosdevices contain links for other drives, usually the c: drive is a link to the upper drive_c, but not always

I hope this information is not too complicated (yes, it is complex in that it is different from Windows, but rather simple in its underlying logic.)

So finally had a second to really read through this. a great explanation of Proton/Wine!

That being said, I think I still have some questions

I'm currently in home>(USER)>.steam>Steam>steamapps>compdata>(game id)>pfx>dosdevices

I also gone into home>(USER)>.local>share>Steam>steamapps>compdata>(game id)>pfx>dosdevices

In both paths there are two items. one is a folder labeled "z:"the other is "c:"

while I can open and explore the z drive easily, the c drive is still showing a question mark icon.

Edit: It doesn't seem to see "c:" as a folder. is it a permissions thing? or is there additional software I would need to explore this folder? would something I downloaded prevent me from viewing the contents of this folder?

Thanks again for you help :D

Edit 2: when I go into the properties of the c: and go to the "Points to" option, it says that "the file or folder home>(USER)>.steam>Steam>steamapps>compdata>(game id)>pfx>drive_c doesn't not exist"

[thetargos]

The issue with the c drive could be simoly a broken link (i. e, the link points somewhere else than ../drive_c, you can corroborate opening a konsole within the dosdevices directory and running ls -l to see where the different links point to, z: will most likely point to /, while c: should point to ../drive_c or the absolute (complete) path. I suspect it does not point to a valid location (broken link)