O.K. I figured out how to do this. It wasn't that hard. I WAS able to load this software successfully on one computer, but on a different model, same manufacturer (Dell) it did not work.

Would like to try to load Topaz Denoise version 3.2 under wine. WineHQ database says it works if this dll is added to the winecfg. How does one do that?

Last post. I believe this card is a lost cause. I checked the bios to make sure the computer would allow the AMD card to take over the GPU function from the Intel graphics. Such a setting did exist, I set it the right way, thinking that would do the trick as I've tried everything else. No dice. Then...

[mark2@mark2-optiplex790 ~]$ inxi -CG CPU: Info: Quad Core model: Intel Core i5-2400 bits: 64 type: MCP cache: L2: 6 MiB Speed: 1596 MHz min/max: 1600/3400 MHz Core speeds (MHz): 1: 1596 2: 1596 3: 1596 4: 1596 Graphics: Device-1: AMD Caicos XT [Radeon HD 7470/8470 / R5 235/310 OEM] driver: radeon ...

Finally realised I should look in the registry to see what it said about my video card. Duh.

It doesn't know I have one. It's not detected at all, which explains everything, except what I can do about it.

While I experiment with shell scripts to use wine outside of the playonlinux environment, I have found by looking at the available log files, that one error that continually shows up no matter what I try, is this alert about wglGetPixelFormatAttribivARB, over and over. This is provided through the a...

Might have found the answer. Package called Firejail Sandbox. Had to ask the question how is wine dealing with a sandboxed application? How is wine creating a sandboxed application? Apparently through Firejail. Will now practice running wine under this app to see how it behaves, most likely this is ...

O.K. so this program is containerized in a sandbox and has a start.exe file placed twice, once in /usr/lib/wine and once in /usr/lib32/wine . I cd to the former location and ran wine start.exe and it opened up another terminal with Microsoft Windows 6.1.7601 (?) and skips a couple of lines and gives...

Here is the result of setting a Core GL Profile (3.3) for the graphics card after a fresh install of both playonlinux/wine 6.6 and the application itself, application seemed to almost start, but crashed right away, just as before: [04/24/21 21:46:44] - Running wine- --version (Working directory : /u...

Just to mention, using mesa 21 with this application on wine takes you to this discussion, which I've been tracking for weeks. https://forum.winehq.org/viewtopic.php?f=8&t=34889 The error you get, which is a mesa bug that they're in no hurry to fix, crashes the application with an GLXBadFBConfig...

I did see the references to Lutris a few days ago while trying to understand my issues with this install. Wasn't sure if Lutris is an environment that would work for anything other than games though in many ways by providing custom environments for applications, it seems superficially similar, in a ...

Wine 6.7 was just released, Manjaro will have it available within a couple of days. I'll run the tests and produce the logs as soon as it I can get 6.7 loaded for both recent versions of Mesa.

[mark2@mark2-optiplex790 ~]$ inxi -CG CPU: Info: Quad Core model: Intel Core i5-2400 bits: 64 type: MCP cache: L2: 6 MiB Speed: 1596 MHz min/max: 1600/3400 MHz Core speeds (MHz): 1: 1596 2: 1596 3: 1596 4: 1596 Graphics: Device-1: AMD Caicos XT [Radeon HD 7470/8470 / R5 235/310 OEM] driver: radeon ...

Here is the log. I have noticed the closing error is associated with a recent bug, but I don't know if my error has the same cause.

I have just noticed that there is an error at the end of the error log I missed, with no fixme attached.

It is this: 0094:err:rpc:I_RpcReceive we got fault packet with status 0x1c010003

I have a truly remarkable program running under wine, Topaz Denoise AI, flat amazing for taking noise out of digital photos. I got it running just using defaults in a manual install under Playonlinux, using default integrated Intel graphics on a 10 year old Dell with an I5-2400. Of course it is quit...

O.K. I have success. I found this excellent and simple tutorial on how to downgrade packages on Arch based systems (I'm on Manjaro) and it worked like a charm.

https://averagelinuxuser.com/downgrade- ... x-manjaro/

The temporary fix specified "export MESA_GL_VERSION_OVERRIDE=4.5" possibly can't be run from just anywhere. I'm not sure which directory to run it in. I'm running an application rather than a game. Tried it from the default prompt, no success.

I saw that too, and tried the temporary fix of just typing 'export MESA_GL_VERSION_OVERRIDE=4.5' from the terminal as suggested in the post.. Made no difference, so I had no confidence that this is the universal fix. For what it's worth the Mesa developer assigned to this bug has been getting helpfu...

Since the MESA 21.00 install, a Windows application I had working just fine stopped working under Wine. On a board I saw this comment: "Going back to $ pacman -Q | grep mesa mesa 20.3.4-3 solved the issue." Anyone here tried this? Is this recommended, or can this get someone over there head?

There is someone working on this, but it looks like it will take co-operation from the Wine side and the Mesa side, which may or may not not be happening.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/3969