Closed spiral009 closed 1 year ago
I tried running wine under blink and decided it was going to be an uphill battle. I fixed one issue (https://github.com/jart/blink/pull/118) and then came across the issue you're seeing as well as a few others (e.g. https://github.com/jart/blink/issues/73#issuecomment-1525468726). I have some local hacked-in patches for some of them, but it's still a long way from working.
The thing is, this is really early into the wine boot process. It fails when starting wineserver, which is an internal component of wine. It hasn't even started executing your Windows program or trying to draw it to screen (mom/Setup.exe
sounds like a graphical program).
My recommendation from here depends on what you're trying to do. You could:
If you go for option 3 I can share my hacks. I'd also recommend starting with trying to get console output from a program, e.g. xcopy /?
, before diving into graphical programs.
The release notes say that blink is great for running simple command line programs, because the goal is to be a simple emulator. For example, you can run coreutils, gcc, git, python, ruby, lua, etc. Wine is an entire platform for simulating Windows, and doing things like running World of Warcraft on Linux. Emulating platforms is difficult, because Blink is a platform, and platforms usually need to control the memory and system resources, and they both can't control it at once and have things go fast. Therefore using Blink to virtualize WINE isn't a good expectation to have at this stage of the project. Perhaps it'll happen in the future.