quickpet fossa wine not launching WoW.exe (1.12) (solved)

[NutButterPea]

Hello everyone.

I downloaded wine from the quickpet and so far it's worked great, but I just downloaded world of warcraft 1.12 and it does not launch. The installed version of wine is 5.5 and I am live booting. Does anyone have any idea why this might be happening and how I could solve it?

Attached is an image of the terminal's output.

[mikeslr]

It's pre-1st cup of coffee. So I'm barely functional. But my best guess is that the version of Wine offered by Quickpet --it hasn't been changed in 3 years is -- like me -- not adequate for the task.
Always check WineHq for recommendations, for example. https://appdb.winehq.org/objectManager. ... n&iId=1922.

Uninstall your current version of Wine. To obtain a newer version you have 4 choices. IMHO, the easiest to set up would be MikeWalsh's Wine-portable, but it only uses Wine Version 5.11, https://www.forum.puppylinux.com/viewto ... 191#p68191. I'd try that first since, if it can't do the job removing only requires that first you run the menuremove script, then deleting the Wine-5.11-portable64 folder.

The next easiest would be to install version2013's wine64-8.0_v6.1.pet or wine64-8.5_v6.1.pet from here, https://version2013.yolasite.com/page1.php#wine. [These versions of Wine received, respectively, gold and platinum ratings from WineHQ]. If I understand correctly, Version2013 now locates the Wineprefix on /mnt/home [so it doesn't have to be removed from /root where it would use RAM just to store files]. So the only complications would be following the links to download the pet [read the instructions here, https://www.forum.puppylinux.com/viewto ... 776#p63776 and (I believe) Version2013's Wine_extras pet from here, viewtopic.php?p=62489#p62489 may still be needed/useful to create a wine-menu entry. Ask for instruction on how to create a menu entry for a specific program to run under Wine. [There's a post somewhere, but 'Breakfast calls'.]

More complicated would be to download* and make executable a Wine-AppImage from here, https://github.com/mmtrt/WINE_AppImage. OOTB, it will not have a menu listing and will locate the wineprefix in RAM. Ask for instructions, or better yet...

The 4th possibility. Download, make executable and rename such AppImage to just and exactly WINE64 and drop it into the Framework you'll find here, https://www.forum.puppylinux.com/viewto ... 075#p68075

* IIRC, palemoon web-browser doesn't work well with github; it doesn't enable you to see the "asset' you have to download.

[mikewalsh]

@mikeslr :-

I'm a-wondering, Mike. Is the OP actually calling WINE to launch it with?

Like, open a terminal within the folder that contains the WoW .exe file......then enter

Code: Select all

wine ./WoW.exe

.....hit "Enter", and see what happens? I don't know about you, but I've not found too many Windows apps that will launch directly under WINE simply by clicking on their '.exe' file. Most need a launch script of some kind to call wine, THEN launch the application....

T'other Mike.

[mikeslr]

Hi, T'other Mike. Good question. But I've never used just the 64bit Wine. So I'm not sure that the appropriate command might not be like that of you're portables when there's the need to open a 64-bit program: to wit, wine64 ./WoW.exe.

For most window programs, using either your portable or otherwise, I usually just file-browse to their executable and Left-Click it. But that requires the exe be recognized. Your portable went a long way to automating that. But under some Puppys, I still had to set it up manually:

Right-Click the exe, and from the pop-up menu select Set-Run-Action, and type the appropriate command in front of "$@"

Set-Run-Action.png (23.82 KiB) Viewed 513 times

I think your Post here, https://oldforum.puppylinux.com/viewtop ... 66#p979566 and the replies to it covers how to create menu entries for specific programs except if only a Wine-AppImage [not via your frame-work] is used. The thread predates their use under Puppys. The "$@" isn't used with AppImages. I'm guessing but I think the argument to open a specific 64bit Windows program might be something like:

FULL-PATH-TO*-WINE-APPIMAGE, name-of-Wine-AppImage*/ FULL-PATH-TO-Window's program/name-of-Windows-program.

* You're not stuck with the often long and complex name of any AppImage. That name was given to distinguish it from other, similar AppImages. As my previous post suggested, you can Right-Click an AppImage and rename it. It doesn't care to what. And symlinking the AppImage to somewhere 'on the path', e.g. /usr/bin, would eliminate the need to specify its location.

[NutButterPea]

Thanks for the responses.

I think it was myself not understanding how wine works, just being a general potato. After going through the posts mentioned in the first reply, I decided to retry my original method for the last time, which was simply installing wine and the 32bit-compatibility from quickpet, but since I had downloaded the 32bit-compatibility.sfs before, I realised I don't need to redownload it to install it which I had been doing since the first time getting wine working... I just need to use SFS-Load on-the-fly to load it, go figure.... and from a fresh boot I installed wine and then loaded the 32bit-compatibility.sfs, and successfully had the .exe run action prefixed with "wine" and when launching it by left clicking, wine informed me of additional downloads that needed to occur, and after proceeding, I had successfully launched World of Warcraft 1.12.

I was mucking around and trying whatever I could think of until then but nothing I was trying worked, even though I had, albeit redownloaded, loaded the 32-bit-compatibility.sfs automatically as part of the quickpet download process likely rewriting the file with each attempt after a fresh boot. You could note I had been using the root of my usb from which I booted to store the .sfs, and misunderstood thinking the .sfs would be loaded automatically even when booting into a live environment on a number of original attempts to get it working before reloading the .sfs with quickpet instead of SFS-Load on-the-fly

I am just starting to learn most of this so I am still very noob
That portable by MikeWalsh seems excellent though, since I got it working with my original method I will continue to implement that, but I am going to test out that portable on the next boot. Thanks again everyone

[bigpup]

check your configuration of Wine and see if it is set the way you want it.

In a terminal enter:

Code: Select all

winecfg

Under drives:
Select autodetect to get all the drive locations set for Wine to use.

Under applications:
What Windows version you have set to emulate, can affect how it works for specific Windows programs.

Most other settings are OK the way they are, but can be changed if needed.