Installation help!

[vomberg]

I hate to bother you with this, but I've read over your thread on winehq a dozen times and cannot for the life of me, figure out how to install this correctly. Could you please break it down for installing to a basic wine prefix? I'm totally lost :/

https://forum.winehq.org/viewtopic.php?f=8&t=33555&start=50

[cschuls]

Hello. Here is a link that might help. https://linuxconfig.org/using-wine-prefixes All you should have to do is launch a command in a terminal such as this example: WINEPREFIX=~/Wine32 WINEARCH="win32" winecfg That would build a prefix and environment called "Wine32" (you can use whatever name you want for your prefix though). That would build a 32-bit Wine environment/prefix. If you need another prefix/environment for 64 bit applications a similar command would be used. WINEPREFIX=~/Wine64 WINEARCH="win64" winecfg Again, the name "Wine64" is just an example name. You can call it whatever you want. Both of these examples assume that you are creating a prefix whilst launching the command from your home folder (which is customary). In either case, once the prefix/environment is built, you would then launch your applications by either manually entering in your command on the terminal or include it in a script that would have the following structure: WINEPREFIX=~/Wine32 wine application_executable.exe Once you have your prefix set up, you don't need to include the "WINEARCH" portion at that point. That, I believe this is the extent of knowledge I can pass on to you. Regards.

…

On Fri, Aug 12, 2022 at 11:48 PM vomberg ***@***.***> wrote: I hate to bother you with this, but I've read over your thread on winehq a dozen times and cannot for the life of me, figure out how to install this correctly. Could you please break it down for installing to a basic wine prefix? I'm totally lost :/ https://forum.winehq.org/viewtopic.php?f=8&t=33555&start=50 — Reply to this email directly, view it on GitHub <#1>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEVIAYEEOZVIBGC3IJNNPQLVY4SK7ANCNFSM56NQME3Q> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[vomberg]

I appreciate the information but I was referring to installing "wine-devel". Guessing by the support pdf, loader.c is compiled with wine as opposed to patching an existing installation? Do the dlls belong anywhere particular after install?

[cschuls]

Okay. For that bit, the way I utilize the enhanced "loader.c" file is that I download the source code for the current developer version of Wine (for example, version 7.14), install the source code on a virtual machine, add the modifications to the "loader.c" file, then build the wine version with those modifications utilizing the steps noted in this link. https://wiki.winehq.org/Building_Wine Once the wine build is done, there should be a "kernelbase.dll" built for the 32-bit version of Wine and for the 64-bit version of Wine. Once those "DLL" files are built, one would place them into the directories on the system to be used in lieu of the standard "kernelbase.dll" files. Usually, the safest thing to do would be: - Locate the current version of "kernelbase.dll" for the 32-bit environment. - Rename the current version to some backup name like "kernelbase.dll.bak" in case one needs to revert back to the standard "DLL" file. - Copy in the enhanced/built version of the "kernelbase.dll" file into that directory. - Repeat the above steps for the 64-bit version of the "kernelbase.dll". Of course doing all of these steps requires either having root authority or using the "sudo" operation with the renaming and copying. Also, "chmod" may need to be executed to make sure the read/write/execute flags match up to the standard "DLL" files. I think that's it. The key takeaway would be to build a version of Wine with the enhanced "loader.c" file on a virtual machine so as to not mess up your production system. Regards

…

On Sat, Aug 13, 2022 at 12:29 PM vomberg ***@***.***> wrote: I appreciate the information but I was referring to installing "wine-devel". Guessing by the support pdf, loader.c is compiled with wine as opposed to patching an existing installation? Do the dlls belong anywhere particular after install? — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEVIAYFZQDPSFP5LGK4CQU3VY7LPHANCNFSM56NQME3Q> . You are receiving this because you commented.Message ID: ***@***.***>