Followed the following guide to install Wine under antiX 13.2 Full AMD64 using Testing repos:

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://wiki.debian.org/RunningWindowsPrograms"
linktext was:"https://wiki.debian.org/RunningWindowsPrograms"
====================================


There is no package called lib32bz2-1.0 in the repos.

Running WINEARCH=win32 winecfg results in the following error message:

/usr/bin/winecfg: 32: exec: wine32: not found

Wine v1.6.2-17 is installed.

Next, I attempted to install a windows program by right-clicking on the installation file and selecting open with and selecting /usr/bin/wine to run it.

Wine window appeared stating that the wine configuration was being updated.

Was asked twice about installing Mono, but I clicked the Cancel button both times.

Wine window disappeared. .wine64 folder created under /home/<user> folder.

I then attempted to install a windows program from the command line:

xxx@antiX:~/downloads/ExamDiff--Pro_v7.0.1.7_64bit_setup
$ /usr/bin/wine64 setup_64bit.exe
wine: created the configuration directory '/home/xxx/.wine'
fixme:storage:create_storagefile Storage share mode not implemented.
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:iphlpapi:NotifyAddrChange (Handle 0xede338, overlapped 0xede350): stub
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
fixme:iphlpapi:NotifyAddrChange (Handle 0xeee338, overlapped 0xeee350): stub
wine: configuration in '/home/xxx/.wine' has been updated.
wine: Bad EXE format for Z:\home\xxx\downloads\ExamDiff--Pro_v7.0.1.7_64bit_setup\setup_64bit.exe.

Wine window appeared stating that the wine configuration was being updated.

Was asked twice about installing Mono, but I clicked the Cancel button both times.

Wine window disappeared. .wine folder created under /home/<user> folder.

Is wine currently broken under Testing or am I not understanding something. I didn't experience this much trouble installing and running wine under Debian Stable.

I think part of the problem is that I installed wine prior to activating multiarch and performing a dist-upgrade. I thought I could just re-install wine, but I ended up uninstalling everything wine related and then installed again. Afterwords, I was able to install wine32:i386.

I now have a new problem. Per the Debian guide referenced above, you should install p11-kit:i386. Unfortunately, that package conflicts with the 64-bit version of the same package. The suggested solution is to remove p11-kit:amd64 and gnome-keyring. gnome-keyring is a recommended package for network-manager-gnome and also depends upon p11-kit:amd64. I don't desire to remove the gnome-keyring package based on the package description and the fact that I use network-manager.

Has anyone else ran into this issue and found a work around other than removing gnome-keyring and p11-kit:amd64?

User error...to install wine:

01) sudo apt-get (or aptitude) install wine
02) sudo dpkg --add-architecture i386 (enables multiarch)
03) sudo apt-get (or aptitude) update
04) sudo apt-get (or aptitude) install wine-bin:i386