How to check if my Wine prefix is 32 bit or 64 bit?
I saw tons of threads explaining how to create a 32 bit prefix, but I want to check if the prefix I'm using is 32 bit or 64 bit. The reason I'm asking is that I'm using PlayOnLinux, and I've created a 32 bit virtual drive (for example X). Now when I open winetricks in the folder ~/.PlayOnLinux/wineprefix, wineprefix gives me the message
You are using a 64-bit WINEPREFIX. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
But, when I opened wineprefix in ~/.PlayOnLinux/wineprefix/X, the message didn't appear.
How can I check if the prefix is 32 vs 64 bit?
wine 64-bit 32-bit playonlinux
add a comment |
I saw tons of threads explaining how to create a 32 bit prefix, but I want to check if the prefix I'm using is 32 bit or 64 bit. The reason I'm asking is that I'm using PlayOnLinux, and I've created a 32 bit virtual drive (for example X). Now when I open winetricks in the folder ~/.PlayOnLinux/wineprefix, wineprefix gives me the message
You are using a 64-bit WINEPREFIX. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
But, when I opened wineprefix in ~/.PlayOnLinux/wineprefix/X, the message didn't appear.
How can I check if the prefix is 32 vs 64 bit?
wine 64-bit 32-bit playonlinux
add a comment |
I saw tons of threads explaining how to create a 32 bit prefix, but I want to check if the prefix I'm using is 32 bit or 64 bit. The reason I'm asking is that I'm using PlayOnLinux, and I've created a 32 bit virtual drive (for example X). Now when I open winetricks in the folder ~/.PlayOnLinux/wineprefix, wineprefix gives me the message
You are using a 64-bit WINEPREFIX. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
But, when I opened wineprefix in ~/.PlayOnLinux/wineprefix/X, the message didn't appear.
How can I check if the prefix is 32 vs 64 bit?
wine 64-bit 32-bit playonlinux
I saw tons of threads explaining how to create a 32 bit prefix, but I want to check if the prefix I'm using is 32 bit or 64 bit. The reason I'm asking is that I'm using PlayOnLinux, and I've created a 32 bit virtual drive (for example X). Now when I open winetricks in the folder ~/.PlayOnLinux/wineprefix, wineprefix gives me the message
You are using a 64-bit WINEPREFIX. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
But, when I opened wineprefix in ~/.PlayOnLinux/wineprefix/X, the message didn't appear.
How can I check if the prefix is 32 vs 64 bit?
wine 64-bit 32-bit playonlinux
wine 64-bit 32-bit playonlinux
asked Jul 19 '14 at 23:43
aaldilaiaaldilai
902613
902613
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
All you have to do is, Browse the PlayonLinux's Virtual Drives. Go to the WINEPREFIX/drive_c/ folder and look for Program Files folder.
If you only see the Program Files and no ProgramFiles(x86) Then you are using 32 bit Wine Prefix. If you see both then you are using 64 Bit Wine Prefix.
Hope this helps !!
This is not true. I just had a situation where the prefix was generated without an x86 directory but it was 64-bit as is shown by the fact that it contained drive_c/windows/syswow64.
– Duncan X Simpson
Dec 30 '17 at 4:06
add a comment |
If you are using PlayOnLinux, you can check which version using the GUI - open PlayOnLinux, click 'Configure' on the relevant program, and look at the pane on the left:
Alternatively, you can do what winetricks does (in version 20140817
, circa line 3600), which is check the wineprefix for the presence of the directory WINEPREFIX/drive_c/windows/syswow64
, which should be found in 64bit windows/wineprefix, but not 32bit versions. This should work for ordinary wineprefixes and those under PlayOnLinux.
add a comment |
I needed something similar in a script so made this script based on @wilf's answer:
#!/bin/bash
## Wine can spam stderr
ERRLOG=/tmp/dllerrlog.log
WINESYSDIR=$( winepath -u c:\windows\system32 2> $ERRLOG )
if [[ ${WINESYSDIR} == *"/system32" ]]; then
echo "Prefix is 32 bit"
# do 32 bit stuff here...
elif [[ ${WINESYSDIR} == *"/syswow64"* ]]; then
echo "Prefix is 64 bit"
# do 64 bit stuff here...
else
echo "Unknown wine architecture"
fi
And here is some output:
$ ./winearch.sh
Prefix is 64 bit
And on a 32 bit wine prefix I have:
$ WINEPREFIX=~/.wine32 ./winearch.sh
Prefix is 32 bit
add a comment |
Thanks to @wilf's for 'WINEPREFIX/drive_c/windows/syswow64' (it works)..
but i have been editing the wine registry to find any entry that reveals
what winearch the system is using (win32 or win64), and i have found it in:
cat /root/.wine/system.reg | grep -m 1 '#arch' | cut -d '=' -f2
This command displays: win32 (32 bit) or win64 (64 bit)
Bellow its one example how to use this in scripting:
#!/bin/sh
HkLm=$(cat /root/.wine/system.reg | grep -m 1 '#arch' | cut -d '=' -f2) > /dev/null 2>&1 # winearch (regedit)
if [ "$HkLm" = "win64" ]; then
echo "[x] winearch config: $HkLm (64 bits)"
echo "[i] Please run:$IPATH/bin/enable_x32bits_wine.sh"
exit
fi
Final notes: i have tested this on kali linux..
if WINEPREFIX=/root/.wine32 then cat command must contain that directory
to be able to read inside folder for regedit winearch settings.
1
You shouldn't run wine as root so maybe use~/.wine
instead of/root/.wine
– Olivier G
Feb 18 at 10:10
add a comment |
You could install winetricks, and type this in the terminal:
sudo apt-get install winetricks
and then run winetricks, and then you can see it in preference.
1
When I run winetricks, there is no option for "preference".
– Organic Marble
Sep 4 '15 at 13:22
There is no preference.
– Karl Morrison
Mar 17 '16 at 16:31
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f500069%2fhow-to-check-if-my-wine-prefix-is-32-bit-or-64-bit%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
All you have to do is, Browse the PlayonLinux's Virtual Drives. Go to the WINEPREFIX/drive_c/ folder and look for Program Files folder.
If you only see the Program Files and no ProgramFiles(x86) Then you are using 32 bit Wine Prefix. If you see both then you are using 64 Bit Wine Prefix.
Hope this helps !!
This is not true. I just had a situation where the prefix was generated without an x86 directory but it was 64-bit as is shown by the fact that it contained drive_c/windows/syswow64.
– Duncan X Simpson
Dec 30 '17 at 4:06
add a comment |
All you have to do is, Browse the PlayonLinux's Virtual Drives. Go to the WINEPREFIX/drive_c/ folder and look for Program Files folder.
If you only see the Program Files and no ProgramFiles(x86) Then you are using 32 bit Wine Prefix. If you see both then you are using 64 Bit Wine Prefix.
Hope this helps !!
This is not true. I just had a situation where the prefix was generated without an x86 directory but it was 64-bit as is shown by the fact that it contained drive_c/windows/syswow64.
– Duncan X Simpson
Dec 30 '17 at 4:06
add a comment |
All you have to do is, Browse the PlayonLinux's Virtual Drives. Go to the WINEPREFIX/drive_c/ folder and look for Program Files folder.
If you only see the Program Files and no ProgramFiles(x86) Then you are using 32 bit Wine Prefix. If you see both then you are using 64 Bit Wine Prefix.
Hope this helps !!
All you have to do is, Browse the PlayonLinux's Virtual Drives. Go to the WINEPREFIX/drive_c/ folder and look for Program Files folder.
If you only see the Program Files and no ProgramFiles(x86) Then you are using 32 bit Wine Prefix. If you see both then you are using 64 Bit Wine Prefix.
Hope this helps !!
answered May 19 '15 at 6:52
Rajat PanditaRajat Pandita
79413
79413
This is not true. I just had a situation where the prefix was generated without an x86 directory but it was 64-bit as is shown by the fact that it contained drive_c/windows/syswow64.
– Duncan X Simpson
Dec 30 '17 at 4:06
add a comment |
This is not true. I just had a situation where the prefix was generated without an x86 directory but it was 64-bit as is shown by the fact that it contained drive_c/windows/syswow64.
– Duncan X Simpson
Dec 30 '17 at 4:06
This is not true. I just had a situation where the prefix was generated without an x86 directory but it was 64-bit as is shown by the fact that it contained drive_c/windows/syswow64.
– Duncan X Simpson
Dec 30 '17 at 4:06
This is not true. I just had a situation where the prefix was generated without an x86 directory but it was 64-bit as is shown by the fact that it contained drive_c/windows/syswow64.
– Duncan X Simpson
Dec 30 '17 at 4:06
add a comment |
If you are using PlayOnLinux, you can check which version using the GUI - open PlayOnLinux, click 'Configure' on the relevant program, and look at the pane on the left:
Alternatively, you can do what winetricks does (in version 20140817
, circa line 3600), which is check the wineprefix for the presence of the directory WINEPREFIX/drive_c/windows/syswow64
, which should be found in 64bit windows/wineprefix, but not 32bit versions. This should work for ordinary wineprefixes and those under PlayOnLinux.
add a comment |
If you are using PlayOnLinux, you can check which version using the GUI - open PlayOnLinux, click 'Configure' on the relevant program, and look at the pane on the left:
Alternatively, you can do what winetricks does (in version 20140817
, circa line 3600), which is check the wineprefix for the presence of the directory WINEPREFIX/drive_c/windows/syswow64
, which should be found in 64bit windows/wineprefix, but not 32bit versions. This should work for ordinary wineprefixes and those under PlayOnLinux.
add a comment |
If you are using PlayOnLinux, you can check which version using the GUI - open PlayOnLinux, click 'Configure' on the relevant program, and look at the pane on the left:
Alternatively, you can do what winetricks does (in version 20140817
, circa line 3600), which is check the wineprefix for the presence of the directory WINEPREFIX/drive_c/windows/syswow64
, which should be found in 64bit windows/wineprefix, but not 32bit versions. This should work for ordinary wineprefixes and those under PlayOnLinux.
If you are using PlayOnLinux, you can check which version using the GUI - open PlayOnLinux, click 'Configure' on the relevant program, and look at the pane on the left:
Alternatively, you can do what winetricks does (in version 20140817
, circa line 3600), which is check the wineprefix for the presence of the directory WINEPREFIX/drive_c/windows/syswow64
, which should be found in 64bit windows/wineprefix, but not 32bit versions. This should work for ordinary wineprefixes and those under PlayOnLinux.
answered Dec 22 '14 at 21:57
WilfWilf
21.8k1167131
21.8k1167131
add a comment |
add a comment |
I needed something similar in a script so made this script based on @wilf's answer:
#!/bin/bash
## Wine can spam stderr
ERRLOG=/tmp/dllerrlog.log
WINESYSDIR=$( winepath -u c:\windows\system32 2> $ERRLOG )
if [[ ${WINESYSDIR} == *"/system32" ]]; then
echo "Prefix is 32 bit"
# do 32 bit stuff here...
elif [[ ${WINESYSDIR} == *"/syswow64"* ]]; then
echo "Prefix is 64 bit"
# do 64 bit stuff here...
else
echo "Unknown wine architecture"
fi
And here is some output:
$ ./winearch.sh
Prefix is 64 bit
And on a 32 bit wine prefix I have:
$ WINEPREFIX=~/.wine32 ./winearch.sh
Prefix is 32 bit
add a comment |
I needed something similar in a script so made this script based on @wilf's answer:
#!/bin/bash
## Wine can spam stderr
ERRLOG=/tmp/dllerrlog.log
WINESYSDIR=$( winepath -u c:\windows\system32 2> $ERRLOG )
if [[ ${WINESYSDIR} == *"/system32" ]]; then
echo "Prefix is 32 bit"
# do 32 bit stuff here...
elif [[ ${WINESYSDIR} == *"/syswow64"* ]]; then
echo "Prefix is 64 bit"
# do 64 bit stuff here...
else
echo "Unknown wine architecture"
fi
And here is some output:
$ ./winearch.sh
Prefix is 64 bit
And on a 32 bit wine prefix I have:
$ WINEPREFIX=~/.wine32 ./winearch.sh
Prefix is 32 bit
add a comment |
I needed something similar in a script so made this script based on @wilf's answer:
#!/bin/bash
## Wine can spam stderr
ERRLOG=/tmp/dllerrlog.log
WINESYSDIR=$( winepath -u c:\windows\system32 2> $ERRLOG )
if [[ ${WINESYSDIR} == *"/system32" ]]; then
echo "Prefix is 32 bit"
# do 32 bit stuff here...
elif [[ ${WINESYSDIR} == *"/syswow64"* ]]; then
echo "Prefix is 64 bit"
# do 64 bit stuff here...
else
echo "Unknown wine architecture"
fi
And here is some output:
$ ./winearch.sh
Prefix is 64 bit
And on a 32 bit wine prefix I have:
$ WINEPREFIX=~/.wine32 ./winearch.sh
Prefix is 32 bit
I needed something similar in a script so made this script based on @wilf's answer:
#!/bin/bash
## Wine can spam stderr
ERRLOG=/tmp/dllerrlog.log
WINESYSDIR=$( winepath -u c:\windows\system32 2> $ERRLOG )
if [[ ${WINESYSDIR} == *"/system32" ]]; then
echo "Prefix is 32 bit"
# do 32 bit stuff here...
elif [[ ${WINESYSDIR} == *"/syswow64"* ]]; then
echo "Prefix is 64 bit"
# do 64 bit stuff here...
else
echo "Unknown wine architecture"
fi
And here is some output:
$ ./winearch.sh
Prefix is 64 bit
And on a 32 bit wine prefix I have:
$ WINEPREFIX=~/.wine32 ./winearch.sh
Prefix is 32 bit
answered Sep 4 '15 at 11:35
Stuart AxonStuart Axon
311
311
add a comment |
add a comment |
Thanks to @wilf's for 'WINEPREFIX/drive_c/windows/syswow64' (it works)..
but i have been editing the wine registry to find any entry that reveals
what winearch the system is using (win32 or win64), and i have found it in:
cat /root/.wine/system.reg | grep -m 1 '#arch' | cut -d '=' -f2
This command displays: win32 (32 bit) or win64 (64 bit)
Bellow its one example how to use this in scripting:
#!/bin/sh
HkLm=$(cat /root/.wine/system.reg | grep -m 1 '#arch' | cut -d '=' -f2) > /dev/null 2>&1 # winearch (regedit)
if [ "$HkLm" = "win64" ]; then
echo "[x] winearch config: $HkLm (64 bits)"
echo "[i] Please run:$IPATH/bin/enable_x32bits_wine.sh"
exit
fi
Final notes: i have tested this on kali linux..
if WINEPREFIX=/root/.wine32 then cat command must contain that directory
to be able to read inside folder for regedit winearch settings.
1
You shouldn't run wine as root so maybe use~/.wine
instead of/root/.wine
– Olivier G
Feb 18 at 10:10
add a comment |
Thanks to @wilf's for 'WINEPREFIX/drive_c/windows/syswow64' (it works)..
but i have been editing the wine registry to find any entry that reveals
what winearch the system is using (win32 or win64), and i have found it in:
cat /root/.wine/system.reg | grep -m 1 '#arch' | cut -d '=' -f2
This command displays: win32 (32 bit) or win64 (64 bit)
Bellow its one example how to use this in scripting:
#!/bin/sh
HkLm=$(cat /root/.wine/system.reg | grep -m 1 '#arch' | cut -d '=' -f2) > /dev/null 2>&1 # winearch (regedit)
if [ "$HkLm" = "win64" ]; then
echo "[x] winearch config: $HkLm (64 bits)"
echo "[i] Please run:$IPATH/bin/enable_x32bits_wine.sh"
exit
fi
Final notes: i have tested this on kali linux..
if WINEPREFIX=/root/.wine32 then cat command must contain that directory
to be able to read inside folder for regedit winearch settings.
1
You shouldn't run wine as root so maybe use~/.wine
instead of/root/.wine
– Olivier G
Feb 18 at 10:10
add a comment |
Thanks to @wilf's for 'WINEPREFIX/drive_c/windows/syswow64' (it works)..
but i have been editing the wine registry to find any entry that reveals
what winearch the system is using (win32 or win64), and i have found it in:
cat /root/.wine/system.reg | grep -m 1 '#arch' | cut -d '=' -f2
This command displays: win32 (32 bit) or win64 (64 bit)
Bellow its one example how to use this in scripting:
#!/bin/sh
HkLm=$(cat /root/.wine/system.reg | grep -m 1 '#arch' | cut -d '=' -f2) > /dev/null 2>&1 # winearch (regedit)
if [ "$HkLm" = "win64" ]; then
echo "[x] winearch config: $HkLm (64 bits)"
echo "[i] Please run:$IPATH/bin/enable_x32bits_wine.sh"
exit
fi
Final notes: i have tested this on kali linux..
if WINEPREFIX=/root/.wine32 then cat command must contain that directory
to be able to read inside folder for regedit winearch settings.
Thanks to @wilf's for 'WINEPREFIX/drive_c/windows/syswow64' (it works)..
but i have been editing the wine registry to find any entry that reveals
what winearch the system is using (win32 or win64), and i have found it in:
cat /root/.wine/system.reg | grep -m 1 '#arch' | cut -d '=' -f2
This command displays: win32 (32 bit) or win64 (64 bit)
Bellow its one example how to use this in scripting:
#!/bin/sh
HkLm=$(cat /root/.wine/system.reg | grep -m 1 '#arch' | cut -d '=' -f2) > /dev/null 2>&1 # winearch (regedit)
if [ "$HkLm" = "win64" ]; then
echo "[x] winearch config: $HkLm (64 bits)"
echo "[i] Please run:$IPATH/bin/enable_x32bits_wine.sh"
exit
fi
Final notes: i have tested this on kali linux..
if WINEPREFIX=/root/.wine32 then cat command must contain that directory
to be able to read inside folder for regedit winearch settings.
edited Jan 28 at 13:20
answered Jan 28 at 11:43
r00t-3xp10itr00t-3xp10it
112
112
1
You shouldn't run wine as root so maybe use~/.wine
instead of/root/.wine
– Olivier G
Feb 18 at 10:10
add a comment |
1
You shouldn't run wine as root so maybe use~/.wine
instead of/root/.wine
– Olivier G
Feb 18 at 10:10
1
1
You shouldn't run wine as root so maybe use
~/.wine
instead of /root/.wine
– Olivier G
Feb 18 at 10:10
You shouldn't run wine as root so maybe use
~/.wine
instead of /root/.wine
– Olivier G
Feb 18 at 10:10
add a comment |
You could install winetricks, and type this in the terminal:
sudo apt-get install winetricks
and then run winetricks, and then you can see it in preference.
1
When I run winetricks, there is no option for "preference".
– Organic Marble
Sep 4 '15 at 13:22
There is no preference.
– Karl Morrison
Mar 17 '16 at 16:31
add a comment |
You could install winetricks, and type this in the terminal:
sudo apt-get install winetricks
and then run winetricks, and then you can see it in preference.
1
When I run winetricks, there is no option for "preference".
– Organic Marble
Sep 4 '15 at 13:22
There is no preference.
– Karl Morrison
Mar 17 '16 at 16:31
add a comment |
You could install winetricks, and type this in the terminal:
sudo apt-get install winetricks
and then run winetricks, and then you can see it in preference.
You could install winetricks, and type this in the terminal:
sudo apt-get install winetricks
and then run winetricks, and then you can see it in preference.
answered Jun 27 '15 at 10:26
MichaelMichael
1,05131423
1,05131423
1
When I run winetricks, there is no option for "preference".
– Organic Marble
Sep 4 '15 at 13:22
There is no preference.
– Karl Morrison
Mar 17 '16 at 16:31
add a comment |
1
When I run winetricks, there is no option for "preference".
– Organic Marble
Sep 4 '15 at 13:22
There is no preference.
– Karl Morrison
Mar 17 '16 at 16:31
1
1
When I run winetricks, there is no option for "preference".
– Organic Marble
Sep 4 '15 at 13:22
When I run winetricks, there is no option for "preference".
– Organic Marble
Sep 4 '15 at 13:22
There is no preference.
– Karl Morrison
Mar 17 '16 at 16:31
There is no preference.
– Karl Morrison
Mar 17 '16 at 16:31
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f500069%2fhow-to-check-if-my-wine-prefix-is-32-bit-or-64-bit%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown