search

jason22plays / winetricks

Automatically exported from code.google.com/p/winetricks
0 stars 0 forks source link

OS X Winetricks doesn't wait for install #344

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Install msxml3 or ie7 on Mac OS X 10.8... all command line with a fresh 
wineprefix.  Tested both with winex11.drv and winemac.drv... no difference.

This may affect other verbs, I do not know... but in at least ie7 and msxml3 
Winetricks doesn't stop and wait for installation correctly.  It immediately 
says the installation finished but a file wasn't found... even though the 
installation hasn't even started yet.  In msxml3, it does this and says it 
installed, but the log file wasn't found... but then the msxml3 installer still 
pops up after that and installs.  ie7 just fails completely, but sometimes 
comes up with an IE7 installer error after Winetricks already said it had 
finished.

This was first reported to me from Wineskin users, but I reproduced it using 
standard command line Wine/Winetricks.  I'm assuming this is some type of OSX 
issue, but I have not looked at the code to see what is happening.

Original issue reported on code.google.com by doh...@gmail.com on 17 Aug 2013 at 5:23

GoogleCodeExporter commented 8 years ago 
You know.. ignore this for now, right after I submitted it I think i figured 
out what is going on.  I (and Wineskin) do not use standard "wine" and 
"wineserver" names, which Winetricks launches and waits for, but I do have 
batch files named that... so it goes ahead because it thinks Wine is no longer 
running, because "wine" and "wineserver" both did stop running, but the real 
wine and wineserver aren't done.  I think i can make Wineskin on Updating 
Winetricks to make sure Winetricks uses the right wine executable, and not the 
"wine" bash script... sorry for the bug report

Original comment by doh...@gmail.com on 17 Aug 2013 at 5:31

GoogleCodeExporter commented 8 years ago 
Yeah, just set the WINE and WINESERVER environment variables before calling 
winetricks.

Original comment by daniel.r...@gmail.com on 17 Aug 2013 at 5:41

GoogleCodeExporter commented 8 years ago 
Also, winetricks msxml3 just runs 
  $WINE msiexec /i msxml3.msi
This is a synchronous command.  If your wrapper script
is not synchronous (i.e. runs real wine in the background), that could cause 
problems.

Original comment by daniel.r...@gmail.com on 17 Aug 2013 at 5:45