-
-
Notifications
You must be signed in to change notification settings - Fork 170
folder mapping and driver mapping seems not work properly in Wrapper 3.0.X #577
Comments
Winery-2.0.1 requires Xcode Command Line Tools to be installed. Also this issue isn’t clear, are you saying you always have issues accessing |
Again, is this only happening with CustomEXE laununchers? |
sorry no, it is also happening with main wrapper app |
Try updating the new Winery version and then make a new wrapper using Wineskin-3.0.3 |
Using the new However, there is inconsistency between the folder mapping and the settings panel. such as |
So you'd like more granular control over the folder mappings? e.g, only mapping |
Environment:
Describe the bug
To Reproduce
creater a new blank wrapper
add some app, i added winscp (because it can test folder accessibility directly)
change os to Win7 (to use winscp)
open winecfg add driver
D
mapping to/Users/your/Downloads
mapping Download folder to MacOS's downloads folder
now run app
or,create CustomEXE and run
--> driver d can't access
$HOME/Downloads can't access
Expected behavior
Screenshots
driver D
does not display, because it can't be accessedC:\users\your\Downloads
,cant be accessed, returns "error -5 Access Denied"LastRunWine.log
not generated
Additional context
test with Wrapper 3.0.2
last working Wrapper is 2.9.2.1-rc9(Wineskin-2.9.2.1 seems temporary disabled the folder mapping feature)
but
2.9.2.1-rc9
mappings all folder's with default settings, not seetings displayed in setting panelas update instance's wrapper, seems may cause folder mapping settings can not be properly displayed in panel
see #574
Additional context
The text was updated successfully, but these errors were encountered: