Unofficial Wineskin Winery was working perfectly a few weeks ago, but today when I tried to run it (in High Sierra), it showed under Wrapper Version, "No Wrapper Installed" and said an update was available. When I clicked Update, the File Downloader said Wineskin-2.8.9 was available, but when I clicked OK, nothing happened. There is still no wrapper installed.
Is this a problem only on my system?
emendelson's Content
There have been 12 items by emendelson (Search limited from 01-March 20)
By content type
See this member's
#108153 Unofficial Wineskin Project
Posted by
on 26 February 2019 - 12:11 AM
in
Wineskin Development
#108072 Unofficial Wineskin Project
Posted by
on 10 February 2019 - 04:52 PM
in
Wineskin Development
I've got a DOSBox-based application for running WPDOS on the Mac, but DOSBox doesn't have scalable fonts and tends to be slower than vDos. (The DOSBox-based one is here: http://www.columbia....pdosboxmac.html
As for LibreOffice: it's completely inadequate for anyone who prefers to work in WordPerfect. And even if I wanted to use it with existing WP files, it's simply impractical. It crashes with most of the large WP files I try to open. When it does manage to open a complex WP file, it can't convert custom paragraph numbering; it destroys a lot of WP formatting; and I'm not interested in rewriting a hundred WPDOS macros into the LibreOffice macro language. Also, since I use WPDOS in Windows, I want to be able to save in WP format, and LibreOffice can't do that.
As for LibreOffice: it's completely inadequate for anyone who prefers to work in WordPerfect. And even if I wanted to use it with existing WP files, it's simply impractical. It crashes with most of the large WP files I try to open. When it does manage to open a complex WP file, it can't convert custom paragraph numbering; it destroys a lot of WP formatting; and I'm not interested in rewriting a hundred WPDOS macros into the LibreOffice macro language. Also, since I use WPDOS in Windows, I want to be able to save in WP format, and LibreOffice can't do that.
#108046 Unofficial Wineskin Project
Posted by
on 06 February 2019 - 03:01 PM
in
Wineskin Development
Gcenx, on 25 January 2019 - 03:31 PM, said:
Mind linking to the app? I’m curious.
What you said makes sense it should function that way, I will try and have that functioning that way in the next wrapper update.
What you said makes sense it should function that way, I will try and have that functioning that way in the next wrapper update.
Sorry for not responding sooner - I was away. Here's the page about the app. It lets you run your own copy of WordPerfect for DOS (I don't distribute WordPerfect for DOS for obvious copyright reasons, but it's easy to find):
http://www.columbia..../vdoswpmac.html
I haven't updated the released version of the app with your unofficial version, but of course I plan to do exactly that. My released version of the app uses a patched version of the keyboard driver that I built myself, but I'll use your new option to assign Alt to Option when I update the app. Thank you again!
#108034 Unofficial Wineskin Project
Posted by
on 25 January 2019 - 02:31 AM
in
Wineskin Development
Gcenx, on 24 January 2019 - 01:56 AM, said:
This one I’m aware of but honestly I didn’t think anyone would enable the option if they had it enabled systemwide, I guess people may get confused believing this option only affects Wineskin and not the entire system.
I will see about adding a check in a future wrapper update so if it’s already enabled Wineskin will skip the option on startup/shutdown.
I will see about adding a check in a future wrapper update so if it’s already enabled Wineskin will skip the option on startup/shutdown.
I distribute a Wineskin-based app that needs the F1-F12 keys, and I thought it would be a good idea to have this option turned on in the app, in case the user didn't have it turned on system-wide. If you can add a check in a future wrapper for the existing setting, that would be very helpful. Thank you again for this superb project.
#108032 Unofficial Wineskin Project
Posted by
on 24 January 2019 - 12:07 AM
in
Wineskin Development
One question about this excellent project.
If I use the option in Wineskin to use F1-12 as standard function keys, when Wineskin exits, it turns off that open in macOS. But I have the "Use F1-F12 as standard function keys" option turned ON in System Preferences, and I don't want it to get turned off when I exit Wineskin.
Can Wineskin test what the macOS F1-F2 setting is BEFORE it makes any changes? If F1-F12 is already turned on Wineskin should not make any changes to that setting when it starts or exits. Thank you for making this feature work correctly.
If I use the option in Wineskin to use F1-12 as standard function keys, when Wineskin exits, it turns off that open in macOS. But I have the "Use F1-F12 as standard function keys" option turned ON in System Preferences, and I don't want it to get turned off when I exit Wineskin.
Can Wineskin test what the macOS F1-F2 setting is BEFORE it makes any changes? If F1-F12 is already turned on Wineskin should not make any changes to that setting when it starts or exits. Thank you for making this feature work correctly.
#108017 Assign Alt to Option (not Cmd) in new versions
Posted by
on 17 January 2019 - 03:38 AM
in
Wineskin Development
You're right! I misunderstood. But your new options are EXACTLY what I was looking for, so I'm very happy to have this. Thank you again for this major improvement to Wineskin!
#108014 Assign Alt to Option (not Cmd) in new versions
Posted by
on 16 January 2019 - 01:31 PM
in
Wineskin Development
Gcenx, on 16 January 2019 - 04:15 AM, said:
If you think that’s handy use wine 3.17 or higher, Command key functions like it does on macOS.
Both options are enabled by default on wrapper creation.
Both options are enabled by default on wrapper creation.
Thank you for letting me know about that! I gave up hoping they would ever make this default. This saves an enormous amount of trouble.
Thank you again!
#108012 Assign Alt to Option (not Cmd) in new versions
Posted by
on 16 January 2019 - 03:32 AM
in
Wineskin Development
Gcenx, on 16 January 2019 - 02:37 AM, said:
You really don't need to go through all that trouble as the macDriver already has that feature since Wine 1.7.4, I verified that tonight and added it as a feature to Wineskin-2.8.9Beta2
Thank you! I just downloaded this from GitHub and the "Map Option as Alt" option finally works (I think for the first time). This will save an enormous amount of trouble. Thank you again!
#108009 Build engine from modified Wine source?
Posted by
on 15 January 2019 - 09:17 PM
in
Custom Wine Builds
Please ignore - I realized that this essentially duplicated my question in the Development forum...
#108004 Assign Alt to Option (not Cmd) in new versions
Posted by
on 15 January 2019 - 12:52 PM
in
Wineskin Development
It's very possibly the same. There's a description of the built-in Wine assignments here:
https://palant.de/20...ngs-on-mac-os-x
But the fix that he describes doesn't make option=Alt etc. This mods in this keyboard.c file (look for lines with "//was") certainly did work in the past:
http://www.columbia..../keyboard.c.zip
And again - are there any current instructions out there for building an engine? Probably the instructions are right in front of me, but I can't see them...
https://palant.de/20...ngs-on-mac-os-x
But the fix that he describes doesn't make option=Alt etc. This mods in this keyboard.c file (look for lines with "//was") certainly did work in the past:
http://www.columbia..../keyboard.c.zip
And again - are there any current instructions out there for building an engine? Probably the instructions are right in front of me, but I can't see them...
#108001 Assign Alt to Option (not Cmd) in new versions
Posted by
on 15 January 2019 - 03:29 AM
in
Wineskin Development
With older versions of Wineskin, I've been able to assign the Windows Alt key to the Mac Option key (instead of to the Mac Cmd key) by building wine using the modifications to the keyboard.c file that I've spelled out here:
http://www.columbia....winekeymap.html
Briefly, the method is this: modify keyboard.c to use the correct key-mappings, build, and replace winemac.drv.so in the Wineskin engine with the custom copy of winemac.drv.so that I built.
But this didn't work when I tried it Wine 3.0.
Are there current instructions for building an engine that I can use with High Sierra or Mojave? When I try building an engine with Wineskin Winery, I get an error when it tries to install gcc.
Thanks for any help...
http://www.columbia....winekeymap.html
Briefly, the method is this: modify keyboard.c to use the correct key-mappings, build, and replace winemac.drv.so in the Wineskin engine with the custom copy of winemac.drv.so that I built.
But this didn't work when I tried it Wine 3.0.
Are there current instructions for building an engine that I can use with High Sierra or Mojave? When I try building an engine with Wineskin Winery, I get an error when it tries to install gcc.
Thanks for any help...
#107531 Unofficial Wineskin Project
Posted by
on 10 June 2018 - 07:51 PM
in
Wineskin Development
Has anyone experimented with this under Mojave? It seems that we're going to need 64-bit versions of a lot of things before it will run without warnings (or run at all under the post-Mojave OS...).
