November 2005 - Wine-Devel - list.winehq.org

Re: msvcrt incompatibility in Origin 6.0 when saving documents

by Tobias Burnus

Hello, Olaf Leidinger wrote: > I'm testing Origin 6.0 using wine-0.9.1 and everything is really fine except saving documents. I'm getting a crash here. Just before that crash there is a dialog telling me: "File not saved. Please ensure that the disk isn't full" (roughly translated). Using a native version of msvcrt everything works fine. So I suppose that the problem lies in the builtin msvcrt ;-) > Running origin60.exe using +relay, I also get the message dialog, but the app doesn't crash. (Timing problem?) > Perhaps anybody could tell me where to start looking for the problem. Going trough the +relay-logs I can't find anything suspect. But I'm not very familliar with the win32 api ;-( Just for information: Using CrossOver Office (at least since their nightlies of approx. 2005-06-28) it works. There is something strange: If I install using CrossOverOffice and point Wine 0.9.1 that installation (ln -s ../.cxoffice/default/* ~/.wine) then I can save using Wine 0.9.1. That means that either the installation needs a feature CXO provides or some files on the harddisc have the needed feature (I'm currently not sure whether DCOM needs to be installed, I think it is not.) Tobias

Nov. 29, 2005

Please HELP, info required about 'DIB_Status_GdiMod' and 'DIB_Status_AppMod'

by Marinescu-Ghetau Iulian

Hello, Could anyone give me some more info on X11DRV_CoerceDIBSection function and the logic behind using 'DIB_Status_GdiMod' and 'DIB_Status_AppMod' stats? I am trying to repair a bug (3902) that has to do with application waiting exccessivly on some locks and i am kind of lost ;( Any help would be greatly appreciated! Iulian

Nov. 29, 2005

Re: Problem with serial port

by Uwe Bonnes

>>>>> "Félix" == Félix Ortega <guile-listas(a)hispafuentes.com> writes: Félix> I'm starting to thing that there is a problem with the way the Félix> serial port is initialized, but I don't have any proof of that. Didn't Cihan already found some mismatches in initialization. Perhaps there is more mismatch lingering around. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Nov. 29, 2005

Re: Problem with serial port

by Félix Ortega

Quoting Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de>: >>>>>> "Félix" == Félix Ortega <guile-listas(a)hispafuentes.com> writes: > > Félix> Sorry, with my desesperation I forgot to tell you the version of > Félix> wine I'm running is the 0.9.2 version. I have tried 0.9.0 and > Félix> 0.9.1, with the same result. The strange thing is the driver does > Félix> not use the WaitCommEvent call, tha I think is work in progress > Félix> now. > > No, most WaitCommEvent functionality is there. Maybe heavy use of threads > and some special case still cause trouble. Ok, I think the problem with the other driver is essentially the same, but the second driver uses WaitCommEvent (with events) and the first driver uses timeouts (polling). But the problem I think is the data never gets written to the port (something related to flow control?) > > Félix> I have another driver for a similar printer that does use > Félix> this call, and doesn't work neither. I'm studying the windows > Félix> source code of this second driver (I have access to it) to make a > Félix> linux program that at least initialize the printer. I will keep > Félix> you informed on this second project. > > Look at the test directories and try to create tests mimicing your error. I will try to do that, I haven't looked the test dir too much. > > Félix> For the olivetti printer, I > Félix> don't know what is the problem, and I don't know where to look > Félix> for :(. > > Perpaps some serial spy would be of help. Capture the communication of the > windows program with the device, do the same under wine and compare. > I have done that, with portmon on the windows side and with some patches that you (I think) sent to the list, so the write and read operations log the contents. The data is the same, and the sequence also, but on wine the data never gets to the printer, It stalls on the buffer and after a timeout the program clears the output buffer and starts again. At first I thought that the problem was related with the asynchronous I/O (somehow the timeout fires before the data gets written), so I disabled the asynchronous write for ports, as said on a thread I found on google. The diff was something like changing the line if (flags & (FD_FLAG_OVERLAPPED|FD_FLAG_TIMEOUT)) with if (flags & (FD_FLAG_OVERLAPPED)) at function NtWriteFile on ntdll/file.c file, so the write never gets its own thread unles specified. But the problem remains the same, but the timeout never get's fired and the program hangs trying to write on the serial port. I'm starting to thing that there is a problem with the way the serial port is initialized, but I don't have any proof of that. Thanks! > However I don't have a suggestion for a serial caputure program for you :-( > -- > Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de > > Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt > --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

Nov. 29, 2005

Re: Problem with serial port

by Cihan Altinay

Uwe Bonnes wrote: > Perpaps some serial spy would be of help. Capture the communication of the > windows program with the device, do the same under wine and compare. > > However I don't have a suggestion for a serial caputure program for you :-( How about the freeware Portmon from sysinternals: http://www.sysinternals.com/Utilities/Portmon.html It helped me a lot... Cheers, Cihan

Nov. 29, 2005

Re: Problem with serial port

by Uwe Bonnes

>>>>> "Félix" == Félix Ortega <guile-listas(a)hispafuentes.com> writes: Félix> Sorry, with my desesperation I forgot to tell you the version of Félix> wine I'm running is the 0.9.2 version. I have tried 0.9.0 and Félix> 0.9.1, with the same result. The strange thing is the driver does Félix> not use the WaitCommEvent call, tha I think is work in progress Félix> now. No, most WaitCommEvent functionality is there. Maybe heavy use of threads and some special case still cause trouble. Félix> I have another driver for a similar printer that does use Félix> this call, and doesn't work neither. I'm studying the windows Félix> source code of this second driver (I have access to it) to make a Félix> linux program that at least initialize the printer. I will keep Félix> you informed on this second project. Look at the test directories and try to create tests mimicing your error. Félix> For the olivetti printer, I Félix> don't know what is the problem, and I don't know where to look Félix> for :(. Perpaps some serial spy would be of help. Capture the communication of the windows program with the device, do the same under wine and compare. However I don't have a suggestion for a serial caputure program for you :-( -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Nov. 29, 2005

Re: Problem with serial port

by Félix Ortega

Sorry, with my desesperation I forgot to tell you the version of wine I'm running is the 0.9.2 version. I have tried 0.9.0 and 0.9.1, with the same result. The strange thing is the driver does not use the WaitCommEvent call, tha I think is work in progress now. I have another driver for a similar printer that does use this call, and doesn't work neither. I'm studying the windows source code of this second driver (I have access to it) to make a linux program that at least initialize the printer. I will keep you informed on this second project. For the olivetti printer, I don't know what is the problem, and I don't know where to look for :(. Thanks to all. Quoting Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de>: >>>>>> "Félix" == Félix Ortega <guile-listas(a)hispafuentes.com> writes: > > Félix> Quoting Cihan Altinay <cihan(a)uq.edu.au>: > >> Quoting Félix Ortega <guile-listas(a)hispafuentes.com>: > >> > >>> I'm trying to make work a driver for a financial printer (Olivetti > >>> Pr20) on wine. I'm having problems with the serial port, it seems > >>> that no data is written to the device. I have tried everything I > >>> have thinked, searched on > >> Please try the attached patch with the latest cvs. It is a > >> workaround for a symptom where data is flushed away in wine but not > >> in Windows. It would be interesting to know if that works for you as > >> well. > >> > Félix, just to make things sure, are you running a recent wine? > -- > Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de > > Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt > --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

Nov. 29, 2005

Re: Problem with serial port

by Uwe Bonnes

>>>>> "Félix" == Félix Ortega <guile-listas(a)hispafuentes.com> writes: Félix> Quoting Cihan Altinay <cihan(a)uq.edu.au>: >> Quoting Félix Ortega <guile-listas(a)hispafuentes.com>: >> >>> I'm trying to make work a driver for a financial printer (Olivetti >>> Pr20) on wine. I'm having problems with the serial port, it seems >>> that no data is written to the device. I have tried everything I >>> have thinked, searched on >> Please try the attached patch with the latest cvs. It is a >> workaround for a symptom where data is flushed away in wine but not >> in Windows. It would be interesting to know if that works for you as >> well. >> Félix, just to make things sure, are you running a recent wine? -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Nov. 29, 2005

Re: msvcrt incompatibility in Origin 6.0 when saving documents

by Uwe Bonnes

>>>>> "Olaf" == Olaf Leidinger <leidola(a)newcon.de> writes: Olaf> Hello again! >> Try running the application with the debugger and builtin >> msvcrt. Perhaps you get a backtrace of the crash. Otherwise try in >> the relay trace (builtin msvcrt, showing the messagebox but not the >> crash) to find where the messagebox is called. You can seach for the >> message text. Now work up the log and try to find why the program >> decides to emit the messagebox. >> Olaf> Well, the debugger doesn't tell me anything, as the backtrace is Olaf> only one line long and it doesn't contain any information. I Olaf> digged a bit deeper in the relay-log. After the save-file dialog I Olaf> found this: If it is a heap overwrote, try running with WINEDEBUG=+heap. This will check the heap with each heap operation and will immediately tell you when something hag gone wrong (but not where). Otherwise perhaps try running with WINEDEBUG=+snoop,+relay and compare each msvcrt call. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Nov. 29, 2005

Re: Problem with serial port

by Félix Ortega

Quoting Cihan Altinay <cihan(a)uq.edu.au>: > Quoting Félix Ortega <guile-listas(a)hispafuentes.com>: > >> I'm trying to make work a driver for a financial printer (Olivetti Pr20) on >> wine. I'm having problems with the serial port, it seems that no data is >> written to the device. I have tried everything I have thinked, searched on > > Please try the attached patch with the latest cvs. It is a workaround for > a symptom where data is flushed away in wine but not in Windows. It would > be interesting to know if that works for you as well. > > Cheers, > Cihan > It does not work :( The test program freezes trying to flush the serial port (at function PurgeComm). Just before that the trace says that the cbOutQue has 6 elements (at function ClearCommError). I think the program writes on the serial port, but for any reason the writing operation doesn't succeed and the writing operation stalls trying to do the tcdrain part. The program does not stops with tcflush because tcflush discards the buffers. Perhaps is something related to the line discipline of the port, somehow the port doesn't accept input. I keep investigating, many thanks! ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

Nov. 29, 2005