[Bug 2988] New: ERROR_IO_PENDING when reading from serial port
Wine Bugs
wine-bugs at winehq.org
Wed May 25 10:55:34 CDT 2005
http://bugs.winehq.org/show_bug.cgi?id=2988
Summary: ERROR_IO_PENDING when reading from serial port
Product: Wine
Version: 20040505
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P1
Component: wine-kernel
AssignedTo: wine-bugs at winehq.org
ReportedBy: lhouk at lesliehouk.com
I've got an old digital camera, an Olympus D-300L, that communicates with the
computer via a serial cable. It uses a Win95 application, C-W95.exe, to make
the connection. I've used this application successfully under Win98SE and
Win2K, but I can't make it work under Wine. The program starts fine, but
insists it can not find the camera.
I posted this problem previously in the Usenet group
comp.emulators.ms-windows.wine, where Rein Klazes was kind enough to help me
troubleshoot. He determined that WriteFile() was failing with error code 0x3e5,
ERROR_IO_PENDING. The specific debug log entries he identified as relevant are:
> 0009:Call kernel32.WriteFile(0000005c,42b938cc,00000001,4087fcb4,00000000)
> ret=00437de2
> trace:file:WriteFile 0x5c 0x42b938cc 1 0x4087fcb4 (nil)
> 0009:Call
ntdll.NtWriteFile(0000005c,00000000,00000000,00000000,4087fb9c,42b938cc,00000001,00000000,00000000)
> ret=404ab90c
> trace:ntdll:NtWriteFile
> (0x5c,(nil),(nil),(nil),0x4087fb9c,0x42b938cc,0x00000001,(nil),(nil))!
> trace:ntdll:NtWriteFile
> (0x5c,(nil),(nil),(nil),0x4087fb9c,0x42b938cc,0x00000001,(nil),(nil)),partial
> stub!
> 0009:Ret ntdll.NtWriteFile() retval=00000103 ret=404ab90c
> 0009:Call ntdll.RtlNtStatusToDosError(00000103) ret=404ab938
> 0009:Ret ntdll.RtlNtStatusToDosError() retval=000003e5 ret=404ab938
> 0009:Ret kernel32.WriteFile() retval=00000000 ret=00437de2
> 0009:Call kernel32.GetLastError() ret=00436b8d
> 0009:Ret kernel32.GetLastError() retval=000003e5 ret=00436b8d
Note that this is bug report may be the same issue as reported in bug #469,
which was just changed to status: resolved due to inactivity. Speeddymon asked
that a new bug report be opened on this issue, so I am doing so.
The original Usenet thread I started when I originally ran across this bug can
be viewed at
http://groups-beta.google.com/group/comp.emulators.ms-windows.wine/browse_thread/thread/de0e64016f4646f2/404fbf52c1a102ff?q=Leslie+Houk&rnum=1#404fbf52c1a102ff
if anyone needs or wants to examine it. Other Usenet threads that appear to
deal with the same bug (and some of which also propose actual code fixes) are:
http://groups-beta.google.com/group/comp.emulators.ms-windows.wine/browse_thread/thread/952220ed58a6465b/17fc046d0c2ffbdc?q=Leslie+Houk&rnum=2#17fc046d0c2ffbdc
http://groups-beta.google.com/group/comp.emulators.ms-windows.wine/browse_thread/thread/fcba28bcddcf2a4d/4e6d1c0c301ead28?q=Leslie+Houk&rnum=3#4e6d1c0c301ead28
http://groups-beta.google.com/group/comp.emulators.ms-windows.wine/browse_thread/thread/16f394b368e85b32/0ebab9aa87c4f551?q=Leslie+Houk&rnum=4#0ebab9aa87c4f551
http://groups-beta.google.com/group/comp.emulators.ms-windows.wine/browse_thread/thread/abe7fad564407a88/4ac9227bb67308a6?q=Leslie+Houk&rnum=7#4ac9227bb67308a6
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the wine-bugs
mailing list