> > > But, as I posted earlier: it does not. After the interrupt caused by
the
> > > control line change occurs no additional characters will be written to
> the
> > > PC's UART. However any characters still remaining in the PC's
> transmitter
> > > shift register, buffer, or FIFO will still come blasting down the
wire.
> > This
> > > could be quite a few characters with deep FIFOs.
> >
> > OK, I see...then you also have to program the PC to not use the
FIFO...it
> > does seem a bit silly to use a FIFO on the output if you need to be sure
> > that all the characters are accepted at the other end.
> >
> > /\/\/\/*=Martin
>
> Right, and telling the PC not to use the FIFO can be problematic. I am not
> at all sure of the correct incantations, assuming there are such, to do
this
> under Windows.
>
> I generally send a small packet of data to the PIC and then wait for a
> acknowledge before sending the next packet.
>
> It is really the only way to be sure the other end got the data
>

In Windows98 you can Do ControlPanel->System->DeviceMangaer->Ports and so on
to get to the advanced properties for a serial port and switch off the FIFO,
but probably a serial program can override all these settings. I seem to
remember having done that but it will take me some time to find the info on
MSDN...there is an iocontrol struct you can configure somewhere to use
specific hardware handshake lines and possible control the FIFO use.
/\/\/\/*=Martin

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads