Sharp ZQ-290s sync software

[Jad Naous]

On Wed, 2004-04-14 at 02:15, Jad Naous wrote:
> On Sat, 2004-04-10 at 02:30, Rein Klazes wrote:
> > On Fri, 09 Apr 2004 18:39:51 -0400, you wrote:
> > 
> > > fixme:comm:SetupComm insize 3102 outsize 3102 unimplemented stub
> > > err:dosfs:DOSFS_CreateCommPort Couldn't open device '/dev/ttyS1' !
> > > (check permissions)
> > > fixme:dosfs:DOSFS_OpenDevice device open L"COM2" not supported (yet)
> > > err:file:CreateFileW Couldn't open device L"COM2"!
> > > err:dosfs:DOSFS_CreateCommPort Couldn't open device '/dev/ttyS2' !
> > > (check permissions)
> > ...
> > > Now the other ports don't matter I guess, because my device is on ttyS0,
> > > but the software just says it can't find it.
> > > What to do next?
> > 
> > Some of these messages are not even present in the latest wine. Do
> > upgrade to wine20040408. 
> > 
> > If it still not works run wine as:
> > 
> > WINEDEBUG=+comm wine ....
> > 
> > or even:
> > 
> > WINEDEBUG=+comm,+file wine ....
> > 
> > and look for the part where it (tries to) open COM1.
> > 
> > Rein.
> 
> Thanks,
> I'll try it once I finish finals.
> Jad.

I've upgraded my wine package to 20040408, I'm running redhat 9 btw. I'm
still getting the same message:

$ WINEDEBUG=comm,file wine Desktop
(...)
trace:file:CreateFileW L"COM1" GENERIC_READ GENERIC_WRITE OPEN_EXISTING 
attributes 0x0
trace:file:CreateFileW opening device L"COM1"
trace:file:CreateFileW returning 0x48
fixme:comm:SetupComm insize 3102 outsize 3102 unimplemented stub
trace:comm:SetCommTimeouts (0x48,0x4074f4dc)
trace:comm:GetCommState handle 0x48, ptr 0x4074f4f0
trace:comm:GetCommState OK
trace:comm:GetCommState bytesize 8 baudrate 9600 fParity 0 Parity 0
stopbits 1
trace:comm:GetCommState ~IXON ~IXOFF
trace:comm:GetCommState ~CRTSCTS
trace:comm:SetCommState handle 0x48, ptr 0x4074f4f0
trace:comm:SetCommState bytesize 8 baudrate 9600 fParity 0 Parity 0
stopbits 1
trace:comm:SetCommState ~IXON ~IXOFF
trace:comm:EscapeCommFunction handle 0x48, function=5
trace:comm:EscapeCommFunction SETDTR
trace:comm:EscapeCommFunction handle 0x48, function=3
trace:comm:EscapeCommFunction SETRTS
trace:comm:PurgeComm handle 0x48, flags 5
trace:comm:PurgeComm handle 0x48, flags a
trace:comm:PurgeComm handle 0x48, flags 5
trace:comm:PurgeComm handle 0x48, flags a
(then a bunch of these ...)
trace:comm:ClearCommError handle 0x48 cbInQue = 0 cbOutQue = 0
trace:comm:ClearCommError handle 0x48 cbInQue = 0 cbOutQue = 0
(then)
trace:file:ReadFile 0x48 0x419f6aa0 1 0x4074f3f4 (nil)
trace:file:ReadFile 0x48 0x419f6aa1 1 0x4074f3f4 (nil)
trace:file:ReadFile 0x48 0x419f6aa2 1 0x4074f3f4 (nil)
trace:file:ReadFile 0x48 0x419f6aa3 1 0x4074f3f4 (nil)
trace:file:ReadFile 0x48 0x419f6aa4 1 0x4074f3f4 (nil)
trace:file:ReadFile 0x48 0x419f6aa5 1 0x4074f3f4 (nil)
trace:comm:PurgeComm handle 0x48, flags a
(then it does it again, and then)
trace:comm:EscapeCommFunction handle 0x48, function=6
trace:comm:EscapeCommFunction CLRDTR
trace:comm:EscapeCommFunction handle 0x48, function=4
trace:comm:EscapeCommFunction CLRRTS
(and afterwards it tries to detect the device on another port...)

I've tried out the device in windows, and used portmon to monitor the
serial port. The device usually sends out a specific string every time
it's ready to connect. The program then polls the serial port until the
signal is caught, and then does some more handshaking with the device.
It would seem from this that the software is not reading the correct id
string. Anything to do with "fixme:comm:SetupComm insize 3102 outsize
3102 unimplemented stub"? Is there anyway to monitor what's being sent
and read from the serial port under linux (like portmon for windows)?
Could it be a dll problem (though the program should be fairly simple,
and it should run under windows 98). I didn't see any errors on the
"file" debug channel, though there were some warnings with 32-bit dlls
not found.
I'd really appreciate any help with this...
Thank you, Jad.