Wine aborts setup.exe for weird reason: Need a FIX

Rising Eagle · Post by **Rising Eagle** » Fri Aug 05, 2011 1:51 am

Wine aborts setup.exe: Why?
WINE can't see setup.LST file during installation of simple win ME app

I'm installing eX-Sense Pro under wine in Natty. It's a simple win me/win xp application.

The setup.exe runs fine, but wine seems to not see setup.LST - another file in the same directory:

Setup cannot find C:\users\redwood\Temp\boom1000\setup.LST.
Setup is aborting...

During installation, the boom1000 directory is created and setup.exe is copied into it, but setup.LST is not copied. When I set up boom1000 and copy setup.LST into it, the install process creates boom1001 and repeats the same mistake.

Any ideas? Thx.

Post by **dimesio** » Fri Aug 05, 2011 8:18 am

Wine version? If it's not the latest development release, upgrade. If that doesn't fix it, post complete terminal output, including the command used to run the installer. If the output is long, use pastebin and post a link.

Rising Eagle · Post by **Rising Eagle** » Fri Aug 05, 2011 12:55 pm

This build is called 1.3.25 and is built specifically for Ubuntu Natty by Mathew Young and includes the patches needed to enable USB support. The repository is given below:

PPA for extra packages:

https://launchpad.net/~gtrsdk/+archive/extras

I cannot provide additional execution information since I double clicked on setup.exe from Nautilus. The exact error message and behavior is described fully above.

I have installed another package this way under wine (double click on setup.exe) and it worked fine. In this particular case, my guess is that wine creates a temp directory and copies setup.exe to it, but is unaware of the dependence on setup.LST and therefore does not copy it to the temp directory. If I could create a temp directory with all needed files and force wine to install from there, it might solve the problem.

John Drescher · Post by **John Drescher** » Fri Aug 05, 2011 1:08 pm

I cannot provide additional execution information since I double clicked on setup.exe from Nautilus.

Please stop double clicking and provide a proper logging file.

http://www.winehq.org/FAQ#get_log

John

Rising Eagle · Post by **Rising Eagle** » Fri Aug 05, 2011 1:31 pm

I followed the example in FAQ 6.1 as you requested and the log.txt file is completely empty, so I created a debug listing as described in FAQ 7.19.

The log.txt is now almost 103 thousand lines long. How do I post it for you?

John Drescher · Post by **John Drescher** » Fri Aug 05, 2011 1:34 pm

I followed the example in FAQ 6.1 as you requested and the log.txt file is completely empty, so I created a debug listing as described in FAQ 7.19.

The log.txt is now almost 103 thousand lines long. How do I post it for you?

Normally you place these on pastebin.com but that is probably larger
than they handle. Are all the lines repeated?

John

John Drescher · Post by **John Drescher** » Fri Aug 05, 2011 1:35 pm

Normally you place these on pastebin.com but that is probably larger
than they handle. Are all the lines repeated?

I meant most of the lines repeated..

John

--
John M. Drescher

Post by **dimesio** » Fri Aug 05, 2011 2:17 pm

Rising Eagle wrote:This build is called 1.3.25 and is built specifically for Ubuntu Natty by Mathew Young and includes the patches needed to enable USB support. The repository is given below:

Those patches are not supported here. Retest in plain Wine.

Rising Eagle · Post by **Rising Eagle** » Fri Aug 05, 2011 3:30 pm

You are right, pastebin wouldn't allow it. However, I did post the last 20 or so lines at http://pastebin.com/SkVQg3aL if that helps. I will post more if you can specify what you need.

The lines are not repeating, nor is there an infinite loop of some kind. It all looks like normal calls and returns with values. No errors or tracebacks are present. It just abruptly ends at the point it opens a dialogue box, gives the error about missing file and an OK button.

I am aware that the patches are not supported as you guys are working on a more robust USB support project which is not ready for prime time yet. Unfortunately, my reverting to a nonUSB version defeats the purpose of using the package I wish to install.

It is my belief, however, that it is the installation process that is under suspicion here. Both wine versions would behave identically in this case: this problem affects your stable version as the installation process is not changed in any way by the USB patches. I don't believe reversion will solve the problem nor provide additional clues. Though you cannot make mods to the USB version that solves the problem, my guess is that there is a manual workaround that will work for both versions and that me running experiments of your suggestion under the USB version, and you having access to the code of its equivalent stable version (from which the USB version is built) will lead to a solution for me and a bug fix for all future stable versions.

If you still believe I must revert to stable to find an answer and then revert back to USB and apply the solution we find, tell me how to do so without messing up the packages already installed under wine with USB.

Post by **dimesio** » Fri Aug 05, 2011 4:13 pm

Rising Eagle wrote: the installation process is not changed in any way by the USB patches.

We don't know that. You need to verify that the problem isn't caused by the unapproved patches. Since there is no free demo for this app, you are the only one who can do that.

If you still believe I must revert to stable to find an answer

Not stable; you need to test the latest development release. The best way to test would be to build plain Wine yourself and run it from the build directory (don't install it). The other way is to simply uninstall the patched package you're using now, then install the official Ubuntu Wine 1.3 package and test your app in it. You can easily uninstall the regular package and reinstall the patched version after you're done testing.

Rising Eagle · Post by **Rising Eagle** » Fri Aug 05, 2011 5:38 pm

I uninstalled WINE USB and installed WINE 1.3 from natty/universe repository and got the exact same result. Same dialog, same behavior

Rising Eagle · Post by **Rising Eagle** » Fri Aug 05, 2011 5:57 pm

Although the application must be registered to run, its installation is performed completely independently of that. Registration occurs the first time you run it. If you like, I could email you all the relevant files so you can try installing it yourself.

Post by **dimesio** » Fri Aug 05, 2011 9:21 pm

Rising Eagle wrote: The log.txt is now almost 103 thousand lines long. How do I post it for you?

Compress it with bzip and attach it to the bug report you opened for this.

I uninstalled WINE USB and installed WINE 1.3 from natty/universe repository and got the exact same result. Same dialog, same behavior

State that in the bug report.

If you like, I could email you all the relevant files so you can try installing it yourself.

No. You don't have the legal right to distribute the software.