Proceeding step by step, and selecting install from an exe installer, Lutris is asking…
- User
Proceeding step by step, and selecting install from an exe installer, Lutris is asking for the installation location. But this location appears to be for the prefix. Is that what it is asking for?
- Assistant
Yes, exactly. When Lutris asks for the "installation location" during the setup process (before launching the
.exeinstaller), it is asking for the location of the Wine prefix—the folder that will contain the Wine environment, including the virtualC:\drive, registry files, and other Wine-specific data.Step-by-Step Clarification
-
Lutris "Installation Location" Prompt
- This is the Wine prefix location (e.g.,
~/Games/my-game). - It is not the final location of the application's files as seen by the Windows installer (e.g.,
C:\Program Files\MyGame). - The prefix folder will contain:
drive_c/(the virtualC:\drive)dosdevices/(drive letter mappings)system.reg,user.reg, etc. (Wine registry files)
- This is the Wine prefix location (e.g.,
-
What Happens Next
- After you specify the prefix location, Lutris launches the
.exeinstaller within that Wine prefix. - During the execution of the Windows installer, it will ask for the application installation location—this is the path inside the Wine environment (e.g.,
C:\Program Files\MyGameor a custom path likeD:\MyGameif you set up additional drive letters). - The application's files will physically reside inside the prefix folder (e.g.,
~/Games/my-game/drive_c/Program Files/MyGame) unless you map a different drive letter to an external location, as described in my previous response.
- After you specify the prefix location, Lutris launches the
-
Why This Distinction Matters
- The prefix location (chosen in Lutris) determines where the Wine environment is stored on your Linux filesystem.
- The application installation location (chosen in the Windows installer) determines where the application's files are placed within the Wine environment.
- If you want the application's files to reside on a different filesystem (e.g., a large HDD), you need to map a Wine drive letter (e.g.,
D:) to that filesystem before running the installer, as outlined in my previous response.
Example Workflow
-
Lutris Prompt
- Lutris asks: "Select the installation location" (this is for the Wine prefix).
- You enter:
/home/user/Games/my-game(or wherever you want the prefix to be).
-
Set Up Additional Drive Letter (Optional)
- If you want the application's files to go to a different filesystem (e.g.,
/mnt/bigdisk/WindowsGames), you need to map a drive letter (e.g.,D:) to that location. - Use
winecfgor manually create a symlink in the prefix'sdosdevices/folder (as described in my previous response).
- If you want the application's files to go to a different filesystem (e.g.,
-
Windows Installer Prompt
- The
.exeinstaller runs and asks: "Where do you want to install the application?" - You select:
C:\Program Files\MyGame(default, files go to/home/user/Games/my-game/drive_c/Program Files/MyGame) orD:\MyGame(if you set upD:to point to/mnt/bigdisk/WindowsGames, files go there instead).
- The
Key Takeaway
At the step where Lutris is asking for the "installation location," it is indeed asking for the Wine prefix location. The actual application installation path (e.g.,
C:\orD:\) is chosen later, inside the Windows installer, and can be directed to a different filesystem by setting up additional Wine drive letters. -
- User
There seems to be a catch 22. The prefix doesn't exist prior to clicking on the
+icon. But once I click the+icon the wizard starts but never gives me the opportunity to create a 'dosdevices' drive mapping to elsewhere on my system. How can this be resolved? - Assistant
You're absolutely right—there is a bit of a "catch-22" in the Lutris workflow because the Wine prefix is created as part of the installation wizard, but the wizard doesn't provide a built-in step to configure drive mappings (e.g., via
dosdevices) before running the installer. However, this can be resolved by taking control of the process and setting up the drive mapping either before or during the installation process. Below, I'll outline a step-by-step solution to ensure you can map a drive letter to a different filesystem before the Windows installer runs.
Solution: Set Up Drive Mapping Before or During Installation
To resolve this, you can either:
- Pre-create the Wine prefix and configure the drive mapping before starting the Lutris wizard, or
- Pause the Lutris wizard after the prefix is created but before the Windows installer runs, and configure the drive mapping at that point.
I'll explain both approaches in detail.
Approach 1: Pre-Create the Wine Prefix and Configure Drive Mapping
This approach involves manually creating the Wine prefix and setting up the drive mapping before starting the Lutris wizard. This gives you full control over the prefix configuration.
Steps:
-
Manually Create the Wine Prefix
- Open a terminal and create a new Wine prefix in the desired location. For example:
WINEPREFIX=/home/user/Games/my-game wineboot- Replace
/home/user/Games/my-gamewith the path where you want the Wine prefix to reside. - The
winebootcommand initializes the prefix, creating the necessary folders (drive_c,dosdevices, etc.).
- Replace
- Open a terminal and create a new Wine prefix in the desired location. For example:
-
Set Up the Drive Mapping
- Use
winecfgto add a drive letter mapping to your desired filesystem (e.g.,/mnt/bigdisk/WindowsGames):WINEPREFIX=/home/user/Games/my-game winecfg- In the
winecfgGUI, go to the "Drives" tab. - Click "Add..." to create a new drive letter (e.g.,
D:). - Set the "Path" to your desired location (e.g.,
/mnt/bigdisk/WindowsGames). - Click "OK" to save and close
winecfg.
- In the
- Alternatively, you can manually create the symlink without using
winecfg:mkdir -p /mnt/bigdisk/WindowsGames ln -sf /mnt/bigdisk/WindowsGames /home/user/Games/my-game/dosdevices/d:
- Use
-
Start the Lutris Wizard
- Open Lutris and click the
+icon to add a new game. - Choose "Install a Windows game from an executable."
- When prompted for the "Installation location" (Wine prefix), select the prefix you just created (e.g.,
/home/user/Games/my-game). - Proceed with the wizard, and when the Windows installer runs, choose
D:\MyGame(or similar) as the installation path to ensure the application's files go to/mnt/bigdisk/WindowsGames.
- Open Lutris and click the
-
Finish the Installation
- Complete the Lutris wizard as normal. Lutris will use the pre-configured prefix, and the drive mapping will already be in place.
Approach 2: Pause the Lutris Wizard and Configure Drive Mapping
If you prefer to use the Lutris wizard from the start, you can pause the process after the prefix is created but before the Windows installer runs, and then configure the drive mapping. This approach is slightly more manual but works well if you don't want to pre-create the prefix.
Steps:
-
Start the Lutris Wizard
- Open Lutris and click the
+icon to add a new game. - Choose "Install a Windows game from an executable."
- When prompted for the "Installation location" (Wine prefix), enter your desired prefix location (e.g.,
/home/user/Games/my-game). - Proceed to the step where you select the
.exeinstaller file, but do not click "Install" yet.
- Open Lutris and click the
-
Locate the Prefix
- At this point, Lutris has already created the Wine prefix folder (e.g.,
/home/user/Games/my-game), even though the Windows installer hasn't run yet. - Open a terminal or file manager and navigate to the prefix folder to confirm it exists.
- At this point, Lutris has already created the Wine prefix folder (e.g.,
-
Set Up the Drive Mapping
- Use
winecfgto add a drive letter mapping to your desired filesystem (e.g.,/mnt/bigdisk/WindowsGames):WINEPREFIX=/home/user/Games/my-game winecfg- In the
winecfgGUI, go to the "Drives" tab. - Click "Add..." to create a new drive letter (e.g.,
D:). - Set the "Path" to your desired location (e.g.,
/mnt/bigdisk/WindowsGames). - Click "OK" to save and close
winecfg.
- In the
- Alternatively, you can manually create the symlink without using
winecfg:mkdir -p /mnt/bigdisk/WindowsGames ln -sf /mnt/bigdisk/WindowsGames /home/user/Games/my-game/dosdevices/d:
- Use
-
Resume the Lutris Wizard
- Go back to the Lutris wizard and click "Install" to proceed.
- When the Windows installer runs, choose
D:\MyGame(or similar) as the installation path to ensure the application's files go to/mnt/bigdisk/WindowsGames.
-
Finish the Installation
- Complete the Lutris wizard as normal. The drive mapping will now be in place, and the application's files will reside on the external filesystem.
Which Approach Should You Use?
- Approach 1 (Pre-Create the Prefix) is better if you want full control and plan to reuse the same prefix configuration for multiple games or installations. It also avoids any potential timing issues with the Lutris wizard.
- Approach 2 (Pause the Wizard) is more convenient if you're already in the middle of the Lutris wizard and don't want to start over. It's also useful if you're setting up a one-off installation.
Additional Notes
-
Automating Drive Mappings (Optional)
- If you frequently need to map drive letters to external filesystems, you can create a script to automate the process of initializing a Wine prefix and setting up drive mappings. For example:
#!/bin/bash PREFIX_PATH="$1" EXTERNAL_PATH="$2" DRIVE_LETTER="d:" # Create the prefix WINEPREFIX="$PREFIX_PATH" wineboot # Create the external directory if it doesn't exist mkdir -p "$EXTERNAL_PATH" # Map the drive letter ln -sf "$EXTERNAL_PATH" "$PREFIX_PATH/dosdevices/$DRIVE_LETTER" echo "Prefix created at $PREFIX_PATH with $DRIVE_LETTER mapped to $EXTERNAL_PATH"- Save this as
create_wine_prefix.sh, make it executable (chmod +x create_wine_prefix.sh), and run it like:./create_wine_prefix.sh /home/user/Games/my-game /mnt/bigdisk/WindowsGames
- Save this as
- If you frequently need to map drive letters to external filesystems, you can create a script to automate the process of initializing a Wine prefix and setting up drive mappings. For example:
-
Lutris Configuration
- After the installation, Lutris will store the prefix location in its configuration for the game. If you ever move the prefix or the external filesystem, you'll need to update the game's configuration in Lutris (right-click the game → "Configure" → "Game options" → "Wine prefix").
-
File Permissions
- Ensure that the user running Lutris has read/write permissions to both the prefix location and the external filesystem (e.g.,
/mnt/bigdisk/WindowsGames). You may need to adjust permissions or ownership if necessary:sudo chown -R $USER:$USER /mnt/bigdisk/WindowsGames chmod -R u+rwX /mnt/bigdisk/WindowsGames
- Ensure that the user running Lutris has read/write permissions to both the prefix location and the external filesystem (e.g.,
Summary
The "catch-22" can be resolved by either pre-creating the Wine prefix and setting up the drive mapping before starting the Lutris wizard, or by pausing the wizard after the prefix is created to configure the drive mapping. Both approaches allow you to map a drive letter to a different filesystem, ensuring the application's files can reside outside the prefix while still being accessible to the Windows installer.
- User
In Arch Linux, does Lutris use the system-wide install of Wine or does it use its own wine versions. It seems to me that I can choose the runners to be
systemor proton or glorious eggrollgerunners. Then, if the latter is true and it doesn't use thesystemwine, will using the system wine as you describe above by runnng winecfg still work if proton or ge versions are later chosen ? - Assistant
Let’s break this down step by step to clarify how Lutris interacts with Wine, the role of runners, and how your choice of runner affects the use of
winecfgor other Wine tools.
1. Does Lutris Use the System-Wide Wine or Its Own Wine Versions?
Lutris does not use the system-wide Wine installation by default, unless you explicitly configure it to do so. Instead, Lutris manages its own Wine versions, known as "runners," which are downloaded and stored in
~/.local/share/lutris/runners/wine/. These runners are isolated Wine builds that Lutris uses to ensure compatibility and consistency across different games and applications.However, Lutris provides flexibility in choosing which Wine version (or runner) to use, including:
- Lutris-Managed Wine Runners: These are specific Wine builds downloaded by Lutris, such as
lutris-7.2,lutris-ge-8.0, etc. These are stored in~/.local/share/lutris/runners/wine/. - Proton Runners: These are Valve’s Proton builds (often used for Steam games), adapted for use in Lutris. They are stored in
~/.local/share/lutris/runners/wine/as well, under names likelutris-proton-8.0. - Glorious Eggroll (GE) Runners: These are custom Wine or Proton builds by GloriousEggroll, optimized for gaming. Examples include
lutris-ge-8.0(Wine-based) orlutris-ge-proton8-25(Proton-based). These are also stored in~/.local/share/lutris/runners/wine/. - System Wine: This option tells Lutris to use the Wine installation provided by your system (e.g., the
winepackage installed viapacmanon Arch Linux). When you selectsystemas the runner, Lutris uses the Wine binary located in/usr/bin/wine.
When you configure a game in Lutris, you can choose the runner under the "Runner options" tab in the game’s configuration. By default, Lutris will suggest one of its managed Wine runners, but you can change it to
system, Proton, or GE runners as needed.
2. How Does the Choice of Runner Affect Using
winecfg?The key to understanding this lies in how Wine prefixes work. A Wine prefix is a self-contained environment that stores the Windows-like filesystem (
drive_c), registry files, and configuration settings. The prefix is independent of the Wine version (or runner) used to create or interact with it, as long as the Wine version is compatible with the prefix’s configuration.When you run a Wine tool like
winecfg,wineboot, orwine, the tool interacts with a specific Wine prefix, which is determined by theWINEPREFIXenvironment variable. For example:WINEPREFIX=/home/user/Games/my-game winecfgThis command tells Wine to use the prefix at
/home/user/Games/my-game, regardless of which Wine binary is being used. The Wine binary itself (whether it’s the system Wine, a Lutris-managed Wine, or a Proton/GE runner) is just the tool that interprets and modifies the prefix.Key Points About Wine Prefix Compatibility:
- Wine prefixes are generally compatible across different Wine versions, including system Wine, Lutris-managed Wine, Proton, and GE runners. This means you can create a prefix with one Wine version (e.g., system Wine) and later use it with a different Wine version (e.g., a GE runner).
- Proton and GE runners are still Wine under the hood, but they may include additional patches, configurations, or compatibility layers (e.g., for Steam or DirectX). Despite these differences, they can still interact with standard Wine prefixes, as long as the prefix is properly configured.
- Drive mappings (via
dosdevices) are stored in the prefix, not in the Wine binary. This means that if you set up a drive mapping (e.g.,D:pointing to/mnt/bigdisk/WindowsGames) usingwinecfgwith system Wine, that mapping will persist in the prefix and be recognized by any other Wine version (including Proton or GE runners) that uses the same prefix.
3. Will Using System Wine to Configure the Prefix Still Work If Proton or GE Runners Are Later Chosen?
Yes, it will work, as long as the prefix is properly configured and the Proton or GE runner is compatible with the prefix’s configuration. Here’s why and how to ensure it works:
- Drive Mappings Are Stored in the Prefix: When you use
winecfg(with system Wine) to add a drive letter mapping (e.g.,D:pointing to/mnt/bigdisk/WindowsGames), the mapping is stored in the prefix’sdosdevices/directory as a symlink. This mapping is not tied to the specific Wine version used to create it, so it will be recognized by any Wine version (including Proton or GE runners) that uses the same prefix. - Prefix Compatibility: Proton and GE runners are based on Wine, so they understand standard Wine prefixes. If you create a prefix with system Wine and configure it (e.g., add drive mappings, install dependencies, etc.), a Proton or GE runner can later use that prefix without issues, as long as the runner supports the features and configurations in the prefix.
- Potential Caveats:
- Some Proton or GE runners may include patches or configurations that are not present in system Wine, which could affect compatibility in rare cases (e.g., if a game requires a specific patch only available in a GE runner). However, this is unlikely to affect basic prefix configuration like drive mappings.
- If you use a very old system Wine to create the prefix, a newer Proton or GE runner might need to update the prefix’s configuration (e.g., registry settings or system files) the first time it runs. This is usually handled automatically by Wine/Proton and does not affect drive mappings.
Practical Example:
-
Create and Configure the Prefix with System Wine
- Use system Wine to create the prefix and set up the drive mapping:
WINEPREFIX=/home/user/Games/my-game wineboot WINEPREFIX=/home/user/Games/my-game winecfg- In
winecfg, add a drive letterD:mapping to/mnt/bigdisk/WindowsGames.
- In
- Use system Wine to create the prefix and set up the drive mapping:
-
Install the Game with System Wine
- Run the installer using system Wine, selecting
D:\MyGameas the installation path:WINEPREFIX=/home/user/Games/my-game wine /path/to/installer.exe
- Run the installer using system Wine, selecting
-
Switch to a Proton or GE Runner in Lutris
- In Lutris, configure the game to use the prefix at
/home/user/Games/my-game. - Under "Runner options," select a Proton runner (e.g.,
Proton-8.0) or a GE runner (e.g.,lutris-ge-8.0). - Launch the game. The Proton or GE runner will use the existing prefix, recognize the
D:drive mapping, and run the game from/mnt/bigdisk/WindowsGames/MyGame.
- In Lutris, configure the game to use the prefix at
4. Best Practices to Avoid Issues
To ensure smooth operation when switching between system Wine, Lutris-managed Wine, Proton, or GE runners, follow these best practices:
- Use a Compatible Wine Version for Initial Setup: If you plan to use a Proton or GE runner later, it’s a good idea to use a relatively recent system Wine version to create the prefix. This minimizes the chance of compatibility issues. On Arch Linux, you can ensure your system Wine is up to date by running:
sudo pacman -Syu wine - Test the Prefix with the Chosen Runner: After configuring the prefix with system Wine, test it with the Proton or GE runner you plan to use. For example:
WINEPREFIX=/home/user/Games/my-game ~/.local/share/lutris/runners/wine/lutris-ge-8.0-x86_64/bin/winecfg- This ensures the runner can read the prefix and recognize the drive mappings.
- Install Dependencies in the Prefix: Some games require specific Windows dependencies (e.g., DirectX, Visual C++ Redistributables). You can install these using
winetrickswith system Wine, and they will persist in the prefix for use with Proton or GE runners:WINEPREFIX=/home/user/Games/my-game winetricks d3dx9 vcrun2019 - Backup the Prefix: Before switching runners, make a backup of the prefix folder (e.g.,
tar -czf my-game-prefix.tar.gz /home/user/Games/my-game). This allows you to restore it if something goes wrong. - Avoid Mixing Runners Unnecessarily: While prefixes are generally compatible across runners, it’s best to stick to one runner for a given game once it’s set up, unless you have a specific reason to switch (e.g., better performance with a GE runner).
5. Summary
- Lutris Runner Choice: Lutris uses its own managed Wine versions (runners) by default, stored in
~/.local/share/lutris/runners/wine/. You can choosesystemto use the system-wide Wine, or select Proton or GE runners for specific compatibility or performance needs. - Using System Wine for Prefix Setup: You can use system Wine to create and configure a Wine prefix (e.g., with
winecfgto set up drive mappings), and this configuration will persist in the prefix and be recognized by Proton or GE runners later, as long as the prefix is compatible. - Compatibility: Wine prefixes are generally compatible across different Wine versions, including system Wine, Lutris-managed Wine, Proton, and GE runners. Drive mappings and other configurations (e.g., registry settings) are stored in the prefix, not the Wine binary, so they work regardless of the runner used.
By following the steps and best practices outlined above, you can confidently use system Wine to set up a prefix and then switch to a Proton or GE runner in Lutris without issues.
- Lutris-Managed Wine Runners: These are specific Wine builds downloaded by Lutris, such as
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.