Discussion:
[Wine] 'Program Error' dialog box
Boryeu Mao
2012-03-11 01:19:24 UTC
Permalink
I am running a windows executable, using wine, in a 'batch mode' - ie multiple times with different command parameters to the executable. For some parameters, the 'Program Error' dialog box appears and the wine process does not continue until the dialog box is closed. Is it possible to suppress the dialog box such that the entire batch can be completed without intervention?

wine-1.2.3
CentOS 6.2

Thank you in advance.

Boryeu Mao

<html>
<font face="Century Gothic" color="red">
<b><u>Disclaimer</u></b></font><font face="Century Gothic">
This message, including any attachment, is intended for the use of the individual or entity to which it is addressed.
It is therefore to be considered as a private correspondence which may contain confidential information. If you are
not the intended recipient, please advise the sender immediately delete this message and any attachment there to
without retaining a copy.
</font>
</html>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-users/attachments/20120311/8540cb31/attachment.html>
dimesio
2012-03-11 01:26:09 UTC
Permalink
Post by Boryeu Mao
Is it possible to suppress the dialog box such that the entire batch can be completed without intervention?
winetricks nocrashdialog
Boryeu Mao
2012-03-11 18:16:38 UTC
Permalink
Thanks very much!!

-----Original Message-----
From: wine-users-***@winehq.org [mailto:wine-users-***@winehq.org] On Behalf Of dimesio
Sent: Saturday, March 10, 2012 5:26 PM
To: wine-***@winehq.org
Subject: [Wine] Re: 'Program Error' dialog box
Post by Boryeu Mao
Is it possible to suppress the dialog box such that the entire batch can be completed without intervention?
winetricks nocrashdialog






<html>
<font face="Century Gothic" color="red">
<b><u>Disclaimer</u></b></font><font face="Century Gothic">
This message, including any attachment, is intended for the use of the individual or entity to which it is addressed.
It is therefore to be considered as a private correspondence which may contain confidential information. If you are
not the intended recipient, please advise the sender immediately delete this message and any attachment there to
without retaining a copy.
</font>
</html>
Boryeu Mao
2012-03-11 20:04:48 UTC
Permalink
I am using wine to run a windows executable from a java program under linux (via java ProcessBuilder, jdk1.6.0_13) and collect the output (via InputStreamReader/BufferedReader). The java program was working with wine-1.0.1 (under Debian 4), but is broken after migration to CentOS 6.2 with wine-1.2.3. For certain input data to the windows executable, wine-1.2.3 now generates a Program Error and only partial output gets read back into java. (For the offending input data, on the linux command line however, wine-1.2.3 could generate the file with the complete output from the windows executable).

In several test cases, the mis-behavior occurs when more output is generated.

Is it possible that some program settings are different from wine-1.0.1 to wine-1.2.3 that could cause this behavior? Perhaps there may be verbs in winetricks that can 'flush the output' notwithstanding the condition giving the Program Error?

Any suggestions/pointers/help would be greatly appreciated.


<html>
<font face="Century Gothic" color="red">
<b><u>Disclaimer</u></b></font><font face="Century Gothic">
This message, including any attachment, is intended for the use of the individual or entity to which it is addressed.
It is therefore to be considered as a private correspondence which may contain confidential information. If you are
not the intended recipient, please advise the sender immediately delete this message and any attachment there to
without retaining a copy.
</font>
</html>
Frédéric Delanoy
2012-03-15 08:03:57 UTC
Permalink
I am using wine to run a windows executable from a java program under linux (via java ProcessBuilder, jdk1.6.0_13) and collect the output (via InputStreamReader/BufferedReader).  The java program was working with wine-1.0.1 (under Debian 4), but is broken after migration to CentOS 6.2 with wine-1.2.3.
1.0 and 1.2 are rather old.
Please retry with current wine (1.4)

dimesio
2012-03-11 20:10:25 UTC
Permalink
Post by Boryeu Mao
Is it possible that some program settings are different from wine-1.0.1 to wine-1.2.3 that could cause this behavior?
Both versions are obsolete and no longer supported here. The current stable release is 1.4; try that with a clean wineprefix. If it doesn't work, post terminal output (if long, use pastebin and post a link).
Continue reading on narkive:
Loading...