Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Adding wine64 to wine installation (buster)
1,042 views
Skip to first unread message
Rick Macdonald
Mar 25, 2021, 2:00:05 PM3/25/21
to
I've been running a few 32bit Windows programs with wine for many years,
but now I need to run some 64bit programs.
The Debian wine wiki says "Users on a 64-bit system should make sure
that both wine32 and wine64 (or wine32-development and
wine64-development) are installed".
I have "deb https://dl.winehq.org/wine-builds/debian/ buster main" in
sources.lists. I installed "wine64". The package lists before and after
are below. When I try to install a 64bit program using "wine
64bitprogram.exe", I get the message:
"This program can only be installed on versions of Windows designed for
the following processor architectures: x64".
So then I ran "wine64 64bitprogram.exe" and I get the message:
"wine: '/home/myacct/.wine' is a 32-bit installation, it cannot support
64-bit applications."
Installing wine64 didn't create a .wine64 directory. It seems like I'm
close, but what am I missing? Something to do with WINEPREFIX?
Before installing wine64:
> # dpkg --get-selections|grep wine
> fonts-wine install
> libwine:i386 install
> libwine-cms:i386 install
> libwine-gphoto2:i386 install
> libwine-ldap:i386 install
> libwine-openal:i386 install
> libwine-print:i386 install
> libwine-sane:i386 install
> wine-stable install
> wine-stable-amd64 install
> wine-stable-i386:i386 install
> winehq-stable install
> winetricks install
After installing wine64:
> # dpkg --get-selections|grep wine
> fonts-wine install
> libwine:i386 install
> libwine-cms:i386 install
> libwine-gphoto2:i386 install
> libwine-ldap:i386 install
> libwine-openal:i386 install
> libwine-print:i386 install
> libwine-sane:i386 install
> wine-stable install
> wine-stable-amd64 install
> wine-stable-i386:i386 install
> winehq-stable install
> winetricks install
Thanks, Rick
but now I need to run some 64bit programs.
The Debian wine wiki says "Users on a 64-bit system should make sure
that both wine32 and wine64 (or wine32-development and
wine64-development) are installed".
I have "deb https://dl.winehq.org/wine-builds/debian/ buster main" in
sources.lists. I installed "wine64". The package lists before and after
are below. When I try to install a 64bit program using "wine
64bitprogram.exe", I get the message:
"This program can only be installed on versions of Windows designed for
the following processor architectures: x64".
So then I ran "wine64 64bitprogram.exe" and I get the message:
"wine: '/home/myacct/.wine' is a 32-bit installation, it cannot support
64-bit applications."
Installing wine64 didn't create a .wine64 directory. It seems like I'm
close, but what am I missing? Something to do with WINEPREFIX?
Before installing wine64:
> # dpkg --get-selections|grep wine
> fonts-wine install
> libwine:i386 install
> libwine-cms:i386 install
> libwine-gphoto2:i386 install
> libwine-ldap:i386 install
> libwine-openal:i386 install
> libwine-print:i386 install
> libwine-sane:i386 install
> wine-stable install
> wine-stable-amd64 install
> wine-stable-i386:i386 install
> winehq-stable install
> winetricks install
After installing wine64:
> # dpkg --get-selections|grep wine
> fonts-wine install
> libwine:i386 install
> libwine-cms:i386 install
> libwine-gphoto2:i386 install
> libwine-ldap:i386 install
> libwine-openal:i386 install
> libwine-print:i386 install
> libwine-sane:i386 install
> wine-stable install
> wine-stable-amd64 install
> wine-stable-i386:i386 install
> winehq-stable install
> winetricks install
Thanks, Rick
Alexander V. Makartsev
Mar 25, 2021, 2:10:05 PM3/25/21
to
On 25.03.2021 22:47, Rick Macdonald
wrote:
I've been running a few 32bit Windows programs with wine for many years, but now I need to run some 64bit programs.
The Debian wine wiki says "Users on a 64-bit system should make sure that both wine32 and wine64 (or wine32-development and wine64-development) are installed".
I have "deb https://dl.winehq.org/wine-builds/debian/ buster main" in sources.lists. I installed "wine64". The package lists before and after are below. When I try to install a 64bit program using "wine 64bitprogram.exe", I get the message:
"This program can only be installed on versions of Windows designed for the following processor architectures: x64".
So then I ran "wine64 64bitprogram.exe" and I get the message:
"wine: '/home/myacct/.wine' is a 32-bit installation, it cannot support 64-bit applications."
Installing wine64 didn't create a .wine64 directory. It seems like I'm close, but what am I missing? Something to do with WINEPREFIX?
You have to create a fresh prefix, since you have been using only
32-bit one.
It could be done by moving or renaming (for backup) existing one ".wine" and running:
$ wine --init
This command will create a default "$HOME/.wine" prefix that will run both 32-bit and 64-bit applications.
It could be done by moving or renaming (for backup) existing one ".wine" and running:
$ wine --init
This command will create a default "$HOME/.wine" prefix that will run both 32-bit and 64-bit applications.
-- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄⠀⠀⠀⠀
Alexander V. Makartsev
Mar 25, 2021, 2:20:05 PM3/25/21
to
On 25.03.2021 22:47, Rick Macdonald
wrote:
I've been running a few 32bit Windows programs with wine for many years, but now I need to run some 64bit programs.
The Debian wine wiki says "Users on a 64-bit system should make sure that both wine32 and wine64 (or wine32-development and wine64-development) are installed".
I have "deb https://dl.winehq.org/wine-builds/debian/ buster main" in sources.lists. I installed "wine64". The package lists before and after are below. When I try to install a 64bit program using "wine 64bitprogram.exe", I get the message:
"This program can only be installed on versions of Windows designed for the following processor architectures: x64".
So then I ran "wine64 64bitprogram.exe" and I get the message:
"wine: '/home/myacct/.wine' is a 32-bit installation, it cannot support 64-bit applications."
Installing wine64 didn't create a .wine64 directory. It seems like I'm close, but what am I missing? Something to do with WINEPREFIX?
Correction, command should be:
$ wineboot --init
$ wineboot --init
Rick Macdonald
Mar 26, 2021, 12:00:04 AM3/26/21
to
Thanks!
I ran the wineboot --init command and it worked, and I was able to install the 64bit program with "wine app64.exe", and it launches. Is there a difference between the commands wine and wine64?
Now, do I need to reinstall all my previous 32bit programs, or can I use WINEPREFIX pointing to the old .wine directory that I renamed ".wine32"?
Rick
I ran the wineboot --init command and it worked, and I was able to install the 64bit program with "wine app64.exe", and it launches. Is there a difference between the commands wine and wine64?
Now, do I need to reinstall all my previous 32bit programs, or can I use WINEPREFIX pointing to the old .wine directory that I renamed ".wine32"?
Rick
Alexander V. Makartsev
Mar 26, 2021, 2:00:04 AM3/26/21
to
On 26.03.2021 08:31, Rick Macdonald
wrote:
Thanks!
I ran the wineboot --init command and it worked, and I was able to install the 64bit program with "wine app64.exe", and it launches. Is there a difference between the commands wine and wine64?
Now, do I need to reinstall all my previous 32bit programs, or can I use WINEPREFIX pointing to the old .wine directory that I renamed ".wine32"?
Rick
"wine" command is a 32-bit ELF binary and "wine64" command is a
64-bit ELF binary.
In my experience it doesn't matter which one to use, as long as you run programs inside a prefix that supports both 32-bit and 64-bit (WoW64). [1]
You can use just one prefix for both 32-bit and 64-bit programs, or you can have as many prefixes as you want, each could be setup with different settings and\or DLLs, tailored specifically for some program.
It is up to you how to manage them all.
I use "q4wine" program (it could be installed from Debian repo) that helps to make some things easier.
There is also commercial software "CrossOver" [2] from the authors of WINE project, but I've never used it.
[1] https://wiki.winehq.org/Wine_User%27s_Guide#WINEARCH
[2] https://www.codeweavers.com/crossover
In my experience it doesn't matter which one to use, as long as you run programs inside a prefix that supports both 32-bit and 64-bit (WoW64). [1]
You can use just one prefix for both 32-bit and 64-bit programs, or you can have as many prefixes as you want, each could be setup with different settings and\or DLLs, tailored specifically for some program.
It is up to you how to manage them all.
I use "q4wine" program (it could be installed from Debian repo) that helps to make some things easier.
There is also commercial software "CrossOver" [2] from the authors of WINE project, but I've never used it.
[1] https://wiki.winehq.org/Wine_User%27s_Guide#WINEARCH
[2] https://www.codeweavers.com/crossover
Rick Macdonald
Mar 27, 2021, 3:20:05 PM3/27/21
to
On 2021-03-25 11:50 p.m., Alexander V. Makartsev wrote:
> "wine" command is a 32-bit ELF binary and "wine64" command is a 64-bit
> ELF binary.
> In my experience it doesn't matter which one to use, as long as you
> run programs inside a prefix that supports both 32-bit and 64-bit
> (WoW64). [1]
>
> You can use just one prefix for both 32-bit and 64-bit programs, or
> you can have as many prefixes as you want, each could be setup with
> different settings and\or DLLs, tailored specifically for some program.
> It is up to you how to manage them all.
> I use "q4wine" program (it could be installed from Debian repo) that
> helps to make some things easier.
> There is also commercial software "CrossOver" [2] from the authors of
> WINE project, but I've never used it.
>
>
> [1] https://wiki.winehq.org/Wine_User%27s_Guide#WINEARCH
> [2] https://www.codeweavers.com/crossover
Everything is working perfectly now. Thanks for the help.
> "wine" command is a 32-bit ELF binary and "wine64" command is a 64-bit
> ELF binary.
> In my experience it doesn't matter which one to use, as long as you
> run programs inside a prefix that supports both 32-bit and 64-bit
> (WoW64). [1]
>
> You can use just one prefix for both 32-bit and 64-bit programs, or
> you can have as many prefixes as you want, each could be setup with
> different settings and\or DLLs, tailored specifically for some program.
> It is up to you how to manage them all.
> I use "q4wine" program (it could be installed from Debian repo) that
> helps to make some things easier.
> There is also commercial software "CrossOver" [2] from the authors of
> WINE project, but I've never used it.
>
>
> [1] https://wiki.winehq.org/Wine_User%27s_Guide#WINEARCH
> [2] https://www.codeweavers.com/crossover
Rick
0 new messages