Wine won't run in Buster 64 puppy

[linux28]

0055:fixme:win:EnumDisplayDevicesW ((null),0,0x7fef41c,0x00000000), stub!
006d:fixme:file:FindFirstFileExW flags not implemented 0x00000002
0055:fixme:win:RegisterDeviceNotificationW (hwnd=0x40094, filter=0x7fef9a0,flags=0x00000000) returns a fake device notification handle!
0055:fixme:win:RegisterDeviceNotificationW (hwnd=0x40094, filter=0x7fef9a0,flags=0x00000000) returns a fake device notification handle!
0043:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0
0043:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0
0043:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0
0079:fixme:wlanapi:WlanEnumInterfaces (0x1, (nil), 0xb60fe1c) semi-stub
0079:fixme:wlanapi:WlanGetAvailableNetworkList (0x1, {00000000-0000-0000-0000-000000000000}, 0x1, (nil), 0xb60fe14) stub
0043:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0
0047:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0
0047:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0
0047:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0
0047:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0
0047:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0
0043:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0
0043:fixme:win:IsTouchWindow (0x40058 (nil)): stub
0055:fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
0055:fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
0055:fixme:iphlpapi:CancelIPChangeNotify (overlapped 0x27c147c): stub
0043:fixme:ntdll:EtwEventUnregister (deadbeef) stub.
0043:fixme:ver:GetCurrentPackageId (0x33fe34 (nil)): stub

0032:err:winediag:gnutls_initialize failed to load libgnutls, no support for encryption
0032:err:winediag:gnutls_initialize failed to load libgnutls, no support for encryption
0033:fixme:ver:GetCurrentPackageId (0x1adfe9c (nil)): stub
0033:fixme:sync:SetWaitableTimerEx (0xa8, 0x1adfd24, 0, (nil), (nil), (nil), 45000) semi-stub
003d:fixme:iphlpapi:NotifyAddrChange (Handle 0x29cfeac, overlapped 0x29cfe94): stub
0032:fixme:win:RegisterTouchWindow (0x1005e 00000000): stub
0038:err:winediag:gnutls_initialize failed to load libgnutls, no support for encryption
0038:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
0038:fixme:toolhelp:Heap32ListFirst : stub

003e:err:winediag:gnutls_initialize failed to load libgnutls, no support for encryption
0036:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0

Buster 64 puppy

[s243a]

You can download it from:
https://packages.debian.org/jessie/libpng12-0

or by adding the Jessie repo to pkg and then doing the command:

Code: Select all

pkg --get libpng12-0

However, I suggest using a newer version of wine. So I suggest uninstalling the version you have and then doing the command

Code: Select all

pkg --names-all wine

then when you see the version that you want do the command:

Code: Select all

pkg --getlibpng12-0 full-wine-pkg-name

where "full-wine-pkg-name" is the full package name (includes version number) of the version of wine that you want.

However, before doing this you should add the wine repos with the command "pkg --repo-add", so that you will see the latest version of wine for buster.

However, this won't get you 32 bit wine which you might need. So alternatively you can find a version that someone on this forum compiled for buster or run the 32bit version of buster as an underdog:

See thread:
http://murga-linux.com/puppy/viewtopic.php?t=118166
** I'll provide better instructions later. I'm typing on my phone now.

[linux28]

You can download it from:
https://packages.debian.org/jessie/libpng12-0

or by adding the Jessie repo to pkg and then doing the command:

Code: Select all

pkg --get libpng12-0

However, I suggest using a newer version of wine. So I suggest uninstalling the version you have and then doing the command

Code: Select all

pkg --names-all wine

then when you see the version that you want do the command:

Code: Select all

pkg --getlibpng12-0 full-wine-pkg-name

where "full-wine-pkg-name" is the full package name (includes version number) of the version of wine that you want.

However, before doing this you should add the wine repos with the command "pkg --repo-add", so that you will see the latest version of wine for buster.

However, this won't get you 32 bit wine which you might need. So alternatively you can find a version that someone on this forum compiled for buster or run the 32bit version of buster as an underdog:

See thread:
http://murga-linux.com/puppy/viewtopic.php?t=118166
** I'll provide better instructions later. I'm typing on my phone now.

Sorry, I didn't make it clear
Debian wine installed, can not run as root, no need
Installed wine, libpng installed, even 32-bit installed, but wine appears as an unrecognized prompt above, some software can not run, just such a prompt, and some windows software appears black frame, doubt It is related to the lack of recognition of libpng. I don't know how to solve it.

[s243a]

Sorry, I didn't make it clear
Debian wine installed, can not run as root, no need
Installed wine, libpng installed, even 32-bit installed, but wine appears as an unrecognized prompt above, some software can not run, just such a prompt, and some windows software appears black frame, doubt It is related to the lack of recognition of libpng. I don't know how to solve it.

The libpng that you installed might not be libpng12-0 but if you are still getting the following error:

Code: Select all

0043:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0 

then you likely didn't install libpng12-0. Newer versions of debain have libpng16-16 instead, and if wine was compiled for a newer version of debian it would be compiled against libpng16-16 rather than libpng12-0. Both of these packages can coexist in buster but libpng12-0 is not part of the buster repos.

[linux28]

Sorry, I didn't make it clear
Debian wine installed, can not run as root, no need
Installed wine, libpng installed, even 32-bit installed, but wine appears as an unrecognized prompt above, some software can not run, just such a prompt, and some windows software appears black frame, doubt It is related to the lack of recognition of libpng. I don't know how to solve it.

The libpng that you installed might not be libpng12-0 but if you are still getting the following error:

Code: Select all

0043:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0 

then you likely didn't install libpng12-0. Newer versions of debain have libpng16-16 instead, and if wine was compiled for a newer version of debian it would be compiled against libpng16-16 rather than libpng12-0. Both of these packages can coexist in buster but libpng12-0 is not part of the buster repos.

libpng12-0 64
Not installed, I installed 32, still not

[s243a]

Sorry, I didn't make it clear
Debian wine installed, can not run as root, no need
Installed wine, libpng installed, even 32-bit installed, but wine appears as an unrecognized prompt above, some software can not run, just such a prompt, and some windows software appears black frame, doubt It is related to the lack of recognition of libpng. I don't know how to solve it.

The libpng that you installed might not be libpng12-0 but if you are still getting the following error:

Code: Select all

0043:err:wincodecs:PngDecoder_CreateInstance Failed reading PNG because unable to find libpng12.so.0 

then you likely didn't install libpng12-0. Newer versions of debain have libpng16-16 instead, and if wine was compiled for a newer version of debian it would be compiled against libpng16-16 rather than libpng12-0. Both of these packages can coexist in buster but libpng12-0 is not part of the buster repos.

libpng12-0 64
Not installed, I installed 32, still not

In /var/packages look for a file with libpng12-0 in it's name. That will tell you what files were installed by this package. We're looking for one called, "libpng12.so.0". Your class loader has to be able to find this file and if the path isn't hard-coded, then your classloader will like in the folders specified by "LD_LIBRARY_PATH". To see what folders are in this variable do the command:

Code: Select all

echo $LD_LIBRARY_PATH

The other way to tell you class loader where to look is to put the folder path in /etc/ld.so.conf and then run the command "ldconfig".

See:
http://man7.org/linux/man-pages/man8/ld.so.8.html

Anyway, also check if the file is 32bit or 64bit. You can do this in rox by right clicking on it and looking at the ELF Type. If you are running 32bit wine then you want the 32bit lib. I don't believe either the ppm (puppy package manager) or pkg (Scottman's package manager) has good multi-arch support.

To get 32bit support in a 64 bit system puppy users usually load an sfs by the name multi-arch or 32-bit-compat (something like that I'll look it up) alternatively you can run a 32bit pup in a layer underneath your 64bit pup.

[s243a]

0032:err:winediag:gnutls_initialize failed to load libgnutls, no support for encryption

I googled this error:

ake sure the version of libgnutls you have installed on Arch is the same as the version your Wine was compiled with.

https://forum.winehq.org/viewtopic.php?t=30962

and as I noted in the original post, it looks like you are running a version of wine that was compiled on either Debian Jessie or Ubuntu Tahr...or the equivalent puppies to these. This will make getting wine working correctly more challenging and as I recommend in the original post you should use one compiled on debian buster (or the puppy equivalent).

It looks like the lib names for these packages are the same in Jessie and buster:
https://packages.debian.org/jessie/i386 ... 7/filelist
https://packages.debian.org/buster/i386 ... 7/filelist

Therefore, I'd probably try the Buster version of this package. I'm guessing you need the 32bit version because I presume that buster already has the 64bit version of this package. If that doesn't work you can try an older version of this package libgnutls26..etc but understand that older versions of openssl will have weaker security.

Version 27 of this package seems to be the last version for Jessie in the debian repos so, I suggest installing the buster version of libgnutls-openssl27.

[s243a]

I was asked for the following download file:

32bit_compatibilty_dpupbuster64.sfs
** which is on https://sourceforge.net/projects/dpup/files/64bit/

However, judging by the error output in the original post, it looks like the wine version being used was compiled on tahr. For this reason one might have better luck with the tahrpup version of this sfs:

32bit_compatibility_libs_tahr64.sfs
**availavle on ibiblio.org

To load the sfs just right click on it and select load_sfs. Do the same thing to unloaded it. One great thing about sfs files, is that it will be easy to try each version of these 32bit_compatibility libs.

[mikeslr]

Hi linux28,

As he has far more knowledge than I, I usually defer to s243a's analysis. But in this case, I find it necessary to note that for applications to function "the stars must align": all pieces of the assemblage must communicate directly or indirectly with each other. To run a 32-bit Windows program under Busterpup64, its 64-bit operating system must communicate with Linux 32-bit compatibiity libs which communicates with the Wine Application which communicates with the Windows program. It is highly unlikely that debian Buster64 binaries published this year can communicate with Ubuntu Tahr libs published 4 years ago.

Did you try any of the suggestions to your previous thread, http://murga-linux.com/puppy/viewtopic. ... 98#1049798? Exactly what Window programs do you want to run under Wine 5 which don't run under Wine 4?

[bigpup]

I suggest you totally remove everything about Wine you have installed.

Start over.

For Wine.

Make sure you have the latest version of Wine.
Good place to get Wine for Puppy.
http://murga-linux.com/puppy/viewtopic.php?t=88711

Also, look on the first post of the Wine topic for a added 'wine_extras-v2.1.pet' that puts Wine entries in the menu.

When you get Wine installed and the Wine menu entries.
Run Wine config to setup Wine.
It will probably offer you a few more programs needed for Wine to run properly.
Should download and install them as part of the initial config.

Also, in Wine config->Drivers Select autodetect to get all the driver locations loaded in Wine.

A lot of settup options in Wine config, so check them all.

What version of Windows you want Wine to mimic can affect how a program runs. Wine Config->Applications.

About specific programs running in Wine.
Go to the Wine web site and see what it says about a specific program and issues.
http://www.winehq.org

Using Wine is almost like learning a new operating system.
Takes a while to learn how to use Wine and to get things working properly.

[linux28]

I suggest you totally remove everything about Wine you have installed.

Start over.

For Wine.

Make sure you have the latest version of Wine.
Good place to get Wine for Puppy.
http://murga-linux.com/puppy/viewtopic.php?t=88711

Also, look on the first post of the Wine topic for a added 'wine_extras-v2.1.pet' that puts Wine entries in the menu.

When you get Wine installed and the Wine menu entries.
Run Wine config to setup Wine.
It will probably offer you a few more programs needed for Wine to run properly.
Should download and install them as part of the initial config.

Also, in Wine config->Drivers Select autodetect to get all the driver locations loaded in Wine.

A lot of settup options in Wine config, so check them all.

What version of Windows you want Wine to mimic can affect how a program runs. Wine Config->Applications.

About specific programs running in Wine.
Go to the Wine web site and see what it says about a specific program and issues.
http://www.winehq.org

Using Wine is almost like learning a new operating system.
Takes a while to learn how to use Wine and to get things working properly.

Buster 64 puppy
http://murga-linux.com/puppy/viewtopic.php?t=88711

32bit_compatibilty
Ca n’t use it, 32bit_compatibilty is not suitable

There was a problem with the original 32bit_compatibilty, and I don't know how to find a new one

32bit_compatibilty
libpng12.so.0
0032:err:winediag:gnutls_initialize failed to load libgnutls, no support for encryption

Reinstalled, but wine does not recognize




Buster 64 puppy
Usable wine, can you test it?

[s243a]

I suggest you totally remove everything about Wine you have installed.

Start over.

For Wine.

Make sure you have the latest version of Wine.
Good place to get Wine for Puppy.
http://murga-linux.com/puppy/viewtopic.php?t=88711

Also, look on the first post of the Wine topic for a added 'wine_extras-v2.1.pet' that puts Wine entries in the menu.

When you get Wine installed and the Wine menu entries.
Run Wine config to setup Wine.
It will probably offer you a few more programs needed for Wine to run properly.
Should download and install them as part of the initial config.

Also, in Wine config->Drivers Select autodetect to get all the driver locations loaded in Wine.

A lot of settup options in Wine config, so check them all.

What version of Windows you want Wine to mimic can affect how a program runs. Wine Config->Applications.

About specific programs running in Wine.
Go to the Wine web site and see what it says about a specific program and issues.
http://www.winehq.org

Using Wine is almost like learning a new operating system.
Takes a while to learn how to use Wine and to get things working properly.

Buster 64 puppy
http://murga-linux.com/puppy/viewtopic.php?t=88711

32bit_compatibilty
Ca n’t use it, 32bit_compatibilty is not suitable

There was a problem with the original 32bit_compatibilty, and I don't know how to find a new one

32bit_compatibilty
libpng12.so.0
0032:err:winediag:gnutls_initialize failed to load libgnutls, no support for encryption

Reinstalled, but wine does not recognize




Buster 64 puppy
Usable wine, can you test it?

I'm not sure why it's not finding libpng12 because I think that would be in your tahrpup 32bit compatibility layer although I don't know if the error is related to a missing 32bit lib or a 64bit lib. Right click on the file you are trying to run in wine. If it says "PA32" then you'll be running 32bit wine. Otherwise perhaps your trying to run this .exe via 64bit wine in which case you could install the 64bit version of libpng12-0 as follows:

Code: Select all

pkg --add-repo http://deb.debian.org/debian/ jessie main
pkg --get libpng12-0 

** I'm assuming your are running the 64bit version of buster here in which case the above commands will give you the 64bit libs. If you are running the 32bit version of buster then the above commands will give you the 32bit libs.

However, if you want the 32bit version of this lib then you sould run 32bit buster instead. Once you install the correct libs you can run 32bit buster as an underdog with your 64bit bit buster running in the upper layers. However, if you just want to run a 32bit wine ap then there is no need to run the 64bit version of buster. You can just use the 32bit version of buster instead.

Regarding your no-encryption error, I'm thinking it might be a certificate issue. See posts:
"Certificate Authorities in Wine"
"Draft: Install Let's Encrypt Root CA on Precise Light"
some notes about updating the certificates on precise light (no longer necessary)

[linux28]

I suggest you totally remove everything about Wine you have installed.

Start over.

For Wine.

Make sure you have the latest version of Wine.
Good place to get Wine for Puppy.
http://murga-linux.com/puppy/viewtopic.php?t=88711

Also, look on the first post of the Wine topic for a added 'wine_extras-v2.1.pet' that puts Wine entries in the menu.

When you get Wine installed and the Wine menu entries.
Run Wine config to setup Wine.
It will probably offer you a few more programs needed for Wine to run properly.
Should download and install them as part of the initial config.

Also, in Wine config->Drivers Select autodetect to get all the driver locations loaded in Wine.

A lot of settup options in Wine config, so check them all.

What version of Windows you want Wine to mimic can affect how a program runs. Wine Config->Applications.

About specific programs running in Wine.
Go to the Wine web site and see what it says about a specific program and issues.
http://www.winehq.org

Using Wine is almost like learning a new operating system.
Takes a while to learn how to use Wine and to get things working properly.

Buster 64 puppy
http://murga-linux.com/puppy/viewtopic.php?t=88711

32bit_compatibilty
Ca n’t use it, 32bit_compatibilty is not suitable

There was a problem with the original 32bit_compatibilty, and I don't know how to find a new one

32bit_compatibilty
libpng12.so.0
0032:err:winediag:gnutls_initialize failed to load libgnutls, no support for encryption

Reinstalled, but wine does not recognize




Buster 64 puppy
Usable wine, can you test it?

I'm not sure why it's not finding libpng12 because I think that would be in your tahrpup 32bit compatibility layer although I don't know if the error is related to a missing 32bit lib or a 64bit lib. Right click on the file you are trying to run in wine. If it says "PA32" then you'll be running 32bit wine. Otherwise perhaps your trying to run this .exe via 64bit wine in which case you could install the 64bit version of libpng12-0 as follows:

Code: Select all

pkg --add-repo http://deb.debian.org/debian/ jessie main
pkg --get libpng12-0 

** I'm assuming your are running the 64bit version of buster here in which case the above commands will give you the 64bit libs. If you are running the 32bit version of buster then the above commands will give you the 32bit libs.

However, if you want the 32bit version of this lib then you sould run 32bit buster instead. Once you install the correct libs you can run 32bit buster as an underdog with your 64bit bit buster running in the upper layers. However, if you just want to run a 32bit wine ap then there is no need to run the 64bit version of buster. You can just use the 32bit version of buster instead.

Regarding your no-encryption error, I'm thinking it might be a certificate issue. See posts:
"Certificate Authorities in Wine"
"Draft: Install Let's Encrypt Root CA on Precise Light"
some notes about updating the certificates on precise light (no longer necessary)

pkg --add-repo http://deb.debian.org/debian/ jessie main
Unknown option '--add-repo'



jessie libpng12-0
32 64 are installed, still not work, the problem still cannot be solved


Buster 64 puppy No way

EasyOS Does not work

EasyOS 32bit_compatibilty
Where can I download it?


EasyOS Where is the wine package available?

[s243a]

pkg --add-repo http://deb.debian.org/debian/ jessie main
Unknown option '--add-repo'

Then try instead:

pkg add-repo http://deb.debian.org/debian/ jessie main
Unknown option '--add-repo'

I'm guessing, you are running an older version of pkg than I am.

[s243a]

I just checked and there is a version of wine built specifically for dpup buster:
wine64-5.0-rc1_v4.1.pet
and if you use this version of wine you should also use the 32bit compatibility layer built specifically for buster:
32bit_compatibilty_dpupbuster64.sfs

You'll need to do this all in a new save file (kind of like a clean install of buster) because anything that you tried trying to get this version of wine to work that was built for tahr, could mess up getting the proper version of wine to work that was built for buster.

Actually though, a completely clean install of buster might be even better because it will be more up to date.

[linux28]

I just checked and there is a version of wine built specifically for dpup buster:
wine64-5.0-rc1_v4.1.pet
and if you use this version of wine you should also use the 32bit compatibility layer built specifically for buster:
32bit_compatibilty_dpupbuster64.sfs

You'll need to do this all in a new save file (kind of like a clean install of buster) because anything that you tried trying to get this version of wine to work that was built for tahr, could mess up getting the proper version of wine to work that was built for buster.

Actually though, a completely clean install of buster might be even better because it will be more up to date.

wine64-5.0-rc1_v4.1.pet
Already tried it, can't use it,
the wine program is wrong
Would you please give it a try?


wine64-5.0-rc1_v4.1.pet
Not available at all, no software
wine64-5.0-rc1_v4.1.pet
There is a problem with this package and it cannot be used


http://murga-linux.com/puppy/viewtopic.php?t=88711
Some of them are OK, but others are not.

[linux28]

Buster 64
EasyOS
Normal use of wine
Is it useless?

[s243a]

I just checked and there is a version of wine built specifically for dpup buster:
wine64-5.0-rc1_v4.1.pet
and if you use this version of wine you should also use the 32bit compatibility layer built specifically for buster:
32bit_compatibilty_dpupbuster64.sfs

You'll need to do this all in a new save file (kind of like a clean install of buster) because anything that you tried trying to get this version of wine to work that was built for tahr, could mess up getting the proper version of wine to work that was built for buster.

Actually though, a completely clean install of buster might be even better because it will be more up to date.

wine64-5.0-rc1_v4.1.pet
Already tried it, can't use it,
the wine program is wrong
Would you please give it a try?


wine64-5.0-rc1_v4.1.pet
Not available at all, no software
wine64-5.0-rc1_v4.1.pet
There is a problem with this package and it cannot be used

Can this wine package not be used or does the software that you are trying to use not run on wine? I don't think that you told us what software that you are trying to run with wine.

http://murga-linux.com/puppy/viewtopic.php?t=88711
Some of them are OK, but others are not.

I think the ones in this thread are built in tahrpup, but there is also instructions I think in the same thread on how to compile it for your system.

[s243a]

Buster 64
EasyOS
Normal use of wine
Is it useless?

I know that fatdog64 has a wine.sfs and a 32bit_compat.sfs (not exact names). However, if you don't like the wine pet provided for buster, then you can instead use the wine packages from the official wine repos. Here are some instructions:

Insall Wine from Offical Repos Using "pkg"

[TiredPup]

If I start the winetricks gui it opens as expected. I make a selection and then the gui disappears and no other activity is noted. I launched the GUI from terminal and recorded this to clipboard:

Quote:
[root@dpupbuster64 ~] $ winetricks
------------------------------------------------------
Running Wine/winetricks as root is highly discouraged. See https://wiki.winehq.org/FAQ#Should_I_ru ... as_root.3F
------------------------------------------------------
------------------------------------------------------
You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Using winetricks 20190615-next - sha256sum: 5bcdadda63aa02330e33861197bfbcb3d72711ca6ca1f5d87e03f6953ca764d8 with wine-4.13 and WINEARCH=win64
winetricks GUI enabled, using zenity 0.40.3 (GTK+ 2.24.32)
Unknown arg TRUE
Usage: /usr/sbin/winetricks [options] [command|verb|path-to-verb] ...
Executes given verbs. Each verb installs an application or changes a setting.

Options:
--country=CC Set country code to CC and don't detect your IP address
--force Don't check whether packages were already installed
--gui Show gui diagnostics even when driven by commandline
--isolate Install each app or game in its own bottle (WINEPREFIX)
--self-update Update this application to the last version
--update-rollback Rollback the last self update
-k, --keep_isos Cache isos (allows later installation without disc)
--no-clean Don't delete temp directories (useful during debugging)
-q, --unattended Don't ask any questions, just install automatically
-r, --ddrescue Retry hard when caching scratched discs
-t --torify Run downloads under torify, if available
--verify Run (automated) GUI tests for verbs, if available
-v, --verbose Echo all commands as they are executed
-h, --help Display this message and exit
-V, --version Display version and exit

Commands:
list list categories
list-all list all categories and their verbs
apps list list verbs in category 'applications'
benchmarks list list verbs in category 'benchmarks'
dlls list list verbs in category 'dlls'
games list list verbs in category 'games'
settings list list verbs in category 'settings'
list-cached list cached-and-ready-to-install verbs
list-download list verbs which download automatically
list-manual-download list verbs which download with some help from the user
list-installed list already-installed verbs
arch=32|64 create wineprefix with 32 or 64 bit, this option must be
given before prefix=foobar and will not work in case of
the default wineprefix.
prefix=foobar select WINEPREFIX=/root/.local/share/wineprefixes/foobar
annihilate Delete ALL DATA AND APPLICATIONS INSIDE THIS WINEPREFIX


Wine itself is working. I installed Angel Writer which is an RTF editor.

Wine iexplore opens to an empty window. Wine complains about Winbind and libgnutils in the background.

The above reflects my issue with the use of wine built for DPUP Buster 64. josepjp2424 acknowledged the post and replied that he would look into it. It does not appear that he ever posted on the subject again. I did not use the package long term as I was simply testing it for josepjp2424 and because I had not used wine in a long time. I wondered how useful it might be. I had hoped to be able to use winetricks as that had proved quite useful in the past.