Hello Petr,
I have traced the following procedure as well:
procedure TBlockSerial.SetCommState;
begin
SetSynaError(sOK);
if not windows.SetCommState(Fhandle, dcb) then
SerialCheck(sErr);
ExceptCheck;
end;
The DCB now has been filled with the correct values but when I arrive
at the following line
windows.SetCommState
I get a -1 error, then I enter the SerialCheck function where the
if SerialResult = integer(INVALID_HANDLE_VALUE)
line is TRUE.
This occur also after I run hyperterminal, but in that case the
self.GetCommState;
fills the DCB with the correct values, probably left there by the
previous application (HyperTerminal) and I can't figure if the
following SetCommState does actually set the correct parameters or it
simply does nothing and everything runs fine because the correct
parameters have already been set previously.
----------------------------
Famous Sport Quotes:
"They shouldn't throw at me. I'm the father of five or six kids."
Baseball player Tito Fuentes, after getting hit by a pitch.
----------------------------
Steve IK4WMH
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
synalist-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synalist-public
