News from Mac OSX - Mysterious Serial Port

[R. Hillen]

Hello list,

some time ago I asked this or that re Mac OSX Serial Port.

Sarah and others sent usefull tips, thank you all. Now I want to tell 
about what happened:

On my Mac G4 I use the GPort from GriffinTechnologies, which replaces 
the build in modem. On Griffins website I found a driver for OSX.

Using OSX 10.2.6, Rev 2.1 RC1 (and earlier)
I first got drivernames()"   ->   "gPort,/dev/tty.gPort,/dev/cu.gPort".
The third item is the driverName, "/dev/cu.gPort".

Then I wrote a simple teststack
with a button "Send" and a field "SendField".
Button "Send" owns this script:

-----
on mouseup
   put "/dev/cu.gPort" into DriverName

   put "BAUD=9600  PARITY=N  DATA=8  STOP=1" into serial
   set the serialControlString to serial

   open driver DriverName for text update

   if the result is not empty then
     answer the result
   end if

   write fld SendField  & linefeed & return to driver drivername

   close driver drivername

end mouseup
-----

To read the sent serial data I used a Windows Hyperterminal running on 
a Win-Laptop.

What happened:

I typed "12345" into field SendField, pressed button "Send" and got 
garbage in the terminal, 1 or two chars, nothing of "12345".


I typed "1234567890" and got two garbage chars
I again typed "1234567890" and got two garbage chars
I again typed "1234567890" and got about 12 garbage chars.

This cycle was repeatable.


I typed "1234567890123456789012345678901234567890 1234567890" and got:
"12345678901234567890123456789012345678901234567890", followed by 
NewLine.

After that, I tried again with "12345" and got garbage (see above)

I dont know at this time, if it is a revolution- or a griffin-problem.
Next I will bugzilla it.

I hope to get next week a USB2Serial adapter with OSX-drive, so I will 
try again.
Probably someone of you may test it also?

Thanx.

Richard Hillen.