-
I have a Wineskin wrapper that worked perfectly under Mojave, and I'm trying to get it working on a new M1 Mac. I've installed the latest Wineskin Winery and downloaded the latest wrapper (2.9.0.9-4) and some recent Crossover engines. When I try to update my Wineskin (is that the right terminology?) to the latest wrapper, I get an error message – something about english.lproj, and the updated Wineskin doesn't run. I saw something at https://github.com/Gcenx/WineskinServer/releases about incompatibility between some previous wrapper versions. I assume it's the same issue here. Specifically, "the previous master wrapper Wineskin-2.9.0.7-rc1 won't be able to update to this master wrapper version as the structure has changed." I also see this immediately thereafter: "While it's technically possible to update a current wrapper to the rc2 I won't provide any support for this so please create the wrapper over and manually move over the wineprefix files currently located with the wrappers /Contents/Resources directory into the newly created wrapper. I'm afraid I don't really understand those instructions, which means I'm asking for support, I guess. I think a fresh install might work. But the Wineskin contains a program (Vocaloid) with multiple voice banks that were all installed from their respective DVDs and individually activated. It would be a big pain to have to do them all again. So I'm hoping there's a way to manually update the Wineskin rather than installing everything from scratch in a fresh wrapper. The previous wrapper version was 2.8.8. Could you (or anyone) clarify the instructions I quoted above? This is how I read them:
I have two problems with this. First, I don't know how to identify a wineprefix file. Do I move all the files in /Contents/Resources? Second, at no point do the instructions say to move the actual program and its associated files to the new wrapper. So I must be missing something. Finally, lest I appear ungrateful by appearing out of nowhere and asking for help, let me say that Wineskin has been very helpful for me, and I'm very grateful to doh123 and Gcenx for bringing it to life and keeping it alive, respectively. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
The following seems to resuscitate a wrapper that has failed its update process. Copy the following four items from a new blank wrapper to the corresponding locations in the broken one: PkgInfo, SharedSupport, Base.lproj, and en.lproj. Then choose the executable to run, if it's been changed incorrectly. |
Beta Was this translation helpful? Give feedback.
-
Firstly create a new blank wrapper with the desired name and Engine. From the new wrapper remove the following files from
Now copy the same files from the old wrapper into the same location in the new wrapper that you just removed. Please noteI've been slowly working on a new wrapper update that moves the prefix location again but this will hopefully make things simpler in the future. The included wineprefix will be installed into |
Beta Was this translation helpful? Give feedback.
The following seems to resuscitate a wrapper that has failed its update process. Copy the following four items from a new blank wrapper to the corresponding locations in the broken one: PkgInfo, SharedSupport, Base.lproj, and en.lproj. Then choose the executable to run, if it's been changed incorrectly.