Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken on Monterrey? There seems to be no drive_c folder #536

Closed
urraka opened this issue Jan 25, 2024 · 16 comments
Closed

Broken on Monterrey? There seems to be no drive_c folder #536

urraka opened this issue Jan 25, 2024 · 16 comments
Labels
bug Something isn't working

Comments

@urraka
Copy link

urraka commented Jan 25, 2024

Environment

  • OS: OSX Monterrey
  • Winery version: current (clean install, today)
  • Master Wrapper version: current (clean install, today) - Wineskin-2.9.2.0
  • Engine version: tried WS11WineCX64Bit23.7.1_D3DMetal-v1.1, WS11WineCX64Bit23.7.1 and WS11WineCX64Bit22.1.1-16
  • Hardware: old mac mini (don't have year/model right now)
  • Application/Game Name: couldn't get this far

What I did

  1. Installed brew (clean install on a new user)
  2. Installed Wineskin as explained in README (brew install --cask --no-quarantine gcenx/wine/wineskin)
  3. Installed engine
  4. Installed wrapper (update button)
  5. Created new blank wrapper

Problem
I can launch the Wineskin utility but nothing works. On the advanced options none of the windows utilities work (cmd, control panel, etc). Inspecting the folders I found there is a drive_c symlink but it points to a non-existing directory. Could not find the real drive_c folder anywhere. Symlink points to ./Contents/SharedSupport/prefix/drive_c. There's no prefix folder under SharedSupport. No drive_c in Resources folder either.

Any help appreciated!

@urraka urraka added the bug Something isn't working label Jan 25, 2024
@Gcenx
Copy link
Owner

Gcenx commented Jan 26, 2024

The current wrapper sometimes the wrapper is generated without issue & sometimes it fails.

I’ve resolved this issue for the next update.

@urraka
Copy link
Author

urraka commented Jan 26, 2024

I see, thanks for the quick reply! Anything I can do to work around the issue manually?

I'll probably have to resort to a VM. I've been given 1 day to make some windows software work on OSX and I don't even know if it runs with Wineskin yet. Still, if there's anything I can try to get this running I'll do it, so I'll be very grateful for any tips! Like.. any way to try a previous version?

@Gcenx
Copy link
Owner

Gcenx commented Jan 26, 2024

Run WineskinLauncher via terminal with the following command

WSS-wineboot

That should get you a working wrapper, might take two launches to complete.

I'll probably have to resort to a VM

That might be the safest option right now as there’s no guarantee the software will work with wine, as you have so little time.

@urraka
Copy link
Author

urraka commented Jan 26, 2024

Thanks for the tip! The software didn't work in the end (some error during the install) but at least I managed to get the wrapper going and give it a try.

I didn't see the WineskinLauncher binary the first time so I tried.. I think it was Wineskin WSS-wineboot, which failed saying it couldn't find WineskinLauncher although it was there, except all lowercase. Figured I would mention this in case it matters.

I used VirtualBox with a tiny10 image to get the software running. Not as good as the native experience but works just fine. Thanks again for the quick help!

@Gcenx
Copy link
Owner

Gcenx commented Jan 26, 2024

Yeah not everything works out of box and it can be a pita to get things working in wine sometimes and with a time crunch it’s even worse.

At least you gotten the app working.


As for Wineskin itself, I’ve managed to resolve most of the current weirdness so it always generates a viable wrapper. I’m waiting for another member to review the bugged function so I can have that enabled again.

Unlike other even recent projects I’ve been mostly a one man army.

@FunkyFr3sh
Copy link

FunkyFr3sh commented Feb 23, 2024

I got the issue too, do you need some testers for the new release?

BTW, this only happens with WS11WineCX64Bit23* and not with the older ones (22 and below are fine)

@Gcenx
Copy link
Owner

Gcenx commented Feb 23, 2024

@FunkyFr3sh this (and some other bugs) should already be resolved by using #530 and it’s Engines.

@FunkyFr3sh
Copy link

FunkyFr3sh commented Feb 23, 2024

@FunkyFr3sh this (and some other bugs) should already be resolved by using #530 and it’s Engines.

Just tested, still the same error:

image

image

image

@Gcenx
Copy link
Owner

Gcenx commented Feb 23, 2024

@FunkyFr3sh I have a feeling there some stuck processes on your end, on a cleanly rebooted system I’ve not seen this happen (M3 Max macOS Sonoma)

@FunkyFr3sh
Copy link

Tried after reboot, still the same

image

@Gcenx
Copy link
Owner

Gcenx commented Feb 23, 2024

Please ensure /tmp is also cleared out

@FunkyFr3sh
Copy link

FunkyFr3sh commented Feb 23, 2024

Please ensure /tmp is also cleared out

How exactly would I do that? I'm not really the biggest macOS expert (I only use it to build wineskin wrappers)

Edit:
Tried to google and only found ways to clear it via command line, not sure if there's a proper way to do it?

Cleared manually via command line:
/tmp
/var/tmp
/private/var/tmp
$TMPDIR

Still not working

@Gcenx
Copy link
Owner

Gcenx commented Feb 24, 2024

Is that an Intel Mac or an Apple Silicon Mac?

@FunkyFr3sh
Copy link

FunkyFr3sh commented Feb 24, 2024

OS: Monterey 12.0.1
Winery version: 1.8.4.2 and 1.8.4.3 (brew gcenx/wine/wineskin-devel)
Master Wrapper version: Wineskin-2.9.2.0 and Wineskin-2.9.2.1-rc6
Engine version: All 23* versions - both WS11 and WS12
Hardware: VMware Workstation 15 Player

All old Engines are working fine (Been using it for months without a single failure) - All 23* fail (Faulty drive_c)

@Gcenx
Copy link
Owner

Gcenx commented Feb 25, 2024

@FunkyFr3sh PaulTheTall still owns an Intel Mac that’s running macOS Catalina.
image

Looks like the issue your seeing is somehow related to being ran inside a VM, I know this has happened before and Brendan fixed it but I’ve not been testing wine inside a VM since moving to Apple Silicon.

@FunkyFr3sh
Copy link

@FunkyFr3sh PaulTheTall still owns an Intel Mac that’s running macOS Catalina. image

Looks like the issue your seeing is somehow related to being ran inside a VM, I know this has happened before and Brendan fixed it but I’ve not been testing wine inside a VM since moving to Apple Silicon.

Ah oh well.. It's not a big deal for now, I can just continue to use the older engines. But if you happen to have a test build or something then just @ mention me and I'll test. Thanks!

@Gcenx Gcenx closed this as completed Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants