James Courtier-Dutton a écrit :
The serial port problem has now been fixed.
It is not in the CVS yet, but the patches attached to previous emails in
this thread, when applied to the current CVS, make serial comms work.
I hope this gets all your "serial fiscal printers" working with the
latest wi
Raul Dias wrote:
Hi,
I have problems with wine serial code since 2000/2001.
I think this might be related to your problem.
In my situation, I have a bunch of stores that runs linux.
Their sales sistem is remote application that can be run thru
ssh/telnet/...
Unfortunally they are required to use ex
Eric Pouech wrote:
Izak Burger a écrit :
Hello,
Perhaps I should appologise, I have been lurking on the list way too
long and this message just passed by while I was messing arround with
the next project, which gladly does not involve serial comms and wine :-)
does this fix it ?
A+
This works fo
does this fix it ?
;A+
<< async_ser.diff >>
Yes, it does!!! Thank you very much.
Also thanks to [EMAIL PROTECTED] for his diagnostic efforts, nice
teamwork.
Wow
_
MSN Toolbar provides one-click access to Hotmail from any Web page
Eric Pouech a écrit :
Izak Burger a écrit :
Hello,
Perhaps I should appologise, I have been lurking on the list way too
long and this message just passed by while I was messing arround with
the next project, which gladly does not involve serial comms and wine :-)
does this fix it ?
A+
(don't forg
Izak Burger a écrit :
Hello,
Perhaps I should appologise, I have been lurking on the list way too
long and this message just passed by while I was messing arround with
the next project, which gladly does not involve serial comms and wine :-)
does this fix it ?
A+
Name: async_ser
ChangeLo
Hello,
Perhaps I should appologise, I have been lurking on the list way too
long and this message just passed by while I was messing arround with
the next project, which gladly does not involve serial comms and wine :-)
I had a similar problem (characters go out, nothing gets in) and it
turned
Eric Pouech wrote:
The next time the app calls read, wine sets off a new (now making it
two) FILE_AsyncReadService, but clears the buffer first, so all the
characters received from the previous FILE_AsyncReadService get lost.
it seems the event to be signaled when something is done in the first
The next time the app calls read, wine sets off a new (now making it
two) FILE_AsyncReadService, but clears the buffer first, so all the
characters received from the previous FILE_AsyncReadService get lost.
it seems the event to be signaled when something is done in the first
read is never set,
I have looked into the wine code now, and async reads from the COM port
are just broken.
The app calls read, wine sets off the FILE_AsyncReadService, and then
returns to the app.
FILE_AsyncReadService is called each time a character is received from
the COM port, and it buffers up the received
Eric Pouech wrote:
So, WINE should be "return immediately with the characters that have
already been received, even if no characters have been received."
does this help ?
A+
Yes and no. The read call does return quicker, but no actual characters
get to the application if it returns quickly. char
So, WINE should be "return immediately with the characters that have
already been received, even if no characters have been received."
does this help ?
A+
Index: dlls/kernel/comm.c
===
RCS file: /home/cvs/cvsroot/wine/wine/dlls/kernel
Eric Pouech wrote:
James Courtier-Dutton a écrit :
I attach two logs taken with the command: -
WINEDEBUG=+comm wine ttermpro.exe
WINEDEBUG="+comm,+file,+ntdll" would be more helpful. TIA.
In addition, ttermpro.exe is setting the following: -
memset(&ctmo,0,sizeof(ctmo));
ctmo.ReadIntervalTime
Eric Pouech wrote:
James Courtier-Dutton a écrit :
I attach two logs taken with the command: -
WINEDEBUG=+comm wine ttermpro.exe
WINEDEBUG="+comm,+file,+ntdll" would be more helpful. TIA.
In addition to my last response regarding the 1024 buffer threshold,
this web page might help.
http://msdn.
Eric Pouech wrote:
James Courtier-Dutton a écrit :
I attach two logs taken with the command: -
WINEDEBUG=+comm wine ttermpro.exe
WINEDEBUG="+comm,+file,+ntdll" would be more helpful. TIA.
I linked two computers together.
ttermpro on one, and kermit on the other.
When I type characters on the tter
James Courtier-Dutton a écrit :
I attach two logs taken with the command: -
WINEDEBUG=+comm wine ttermpro.exe
WINEDEBUG="+comm,+file,+ntdll" would be more helpful. TIA.
David Purucker wrote:
Hello,
I have tried several terminal programs (Hyperterm and TeraTerm) under
several builds of
Wine including Wine-20040505 and they seem to have the same generic
problem.
They all exhibit the same situation, DATA seems to go OUT, but never
seems to come IN.
Several other
Raul Dias a écrit :
I am not a serial expert, but I don't understand what can change in the
serial communication to work with one printer and not work with another
(that use to work).
For me serial is TX, RX and a few control pins and that's it.
there's lot of stuff in between the physical interfac
Hi,
I have problems with wine serial code since 2000/2001.
I think this might be related to your problem.
In my situation, I have a bunch of stores that runs linux.
Their sales sistem is remote application that can be run thru
ssh/telnet/...
Unfortunally they are required to use expensive serial
On Mon, May 24, 2004 at 05:06:49PM +, David Purucker wrote:
> Hello,
>
> I have tried several terminal programs (Hyperterm and TeraTerm) under
> several builds of
> Wine including Wine-20040505 and they seem to have the same generic problem.
Teraterm worked almost 100% ok a few months back f
I have tried several terminal programs (Hyperterm and TeraTerm) under
> several builds of
> Wine including Wine-20040505 and they seem to have the same generic
problem.
We are using serial ports under Wine for a current project, and they
work OK (apart from a few warnings). The machine I'm usin
"David Purucker" <[EMAIL PROTECTED]> writes:
> Hello,
>
> I have tried several terminal programs (Hyperterm and TeraTerm) under
> several builds of
> Wine including Wine-20040505 and they seem to have the same generic problem.
We are using serial ports under Wine for a current project, and they
Hello,
I have tried several terminal programs (Hyperterm and TeraTerm) under
several builds of
Wine including Wine-20040505 and they seem to have the same generic problem.
They all exhibit the same situation, DATA seems to go OUT, but never seems
to come IN.
Several other people have experienced
23 matches
Mail list logo