Re: RFC: Re: Problem with COM (fwd)

[Gerard Patel]

At 10:05 PM 2/11/02 -0500, you wrote:
<snip>
(original poster)
> I must use 5726, 5760 and 9600. My app need this to work. On 4800
> and 9600 I got error.
> <snip>
> (Lawson)
> Now nobody is going to convince me there is any software that will make
> a normal 16550a run at 5726
> <snip>

You still don't have access to the world wide web ?
If you have access to Google, search for the following Usenet posting,
for example :

UnHy6.600095$JT5.16435354(a)news20.bellglobal.com

If you can't use Google, you could see that this is a common request 
under Windows. quite a few programmers need to access devices
with non-standard crystals, or even non 8251 chips with specific
drivers.
In this post, you could see that SetCommState accepts any baud 
rate up to 9600 bauds, and that over 9600 bauds the idea is that
the Windows driver should accept values that are inside a +-1% 
interval of the 'correct' value (although the poster says that the
calculation is bugged and works only for negative differences).

The Windows code for the 8251 family is probably always rounding
to the next integer value under 9600, and if the wanted rate falls
to +-1% of the 'normal' value over 9600. As I understand it, the 1%
tolerance is explained because such a small difference don't matter
for asynchronous serial  communication.

Gerard

RFC: Re: Problem with COM (comm, rather) (fwd)

On Tue, 12 Feb 2002, Gerard Patel wrote:
> You still don't have access to the world wide web ?

Say I'm not much inclined to use it, being GUI-challenged.  wget is my
browser of choice.
> If you have access to Google, search for the following Usenet posting,
> for example :
>
> UnHy6.600095$JT5.16435354(a)news20.bellglobal.com

Now what kind of an URL would I give wget to go after that?
http://groups.google.com/<something>=\
UnHy6.600095$JT5.16435354(a)news20.bellglobal.com

Well anyway, you have probably already distilled all the sense that is
to be made of it, thanks.  8251?  Isn't that what they used in 8-bit
PC's before the 16450?  8-/
> Gerard

Still, though, anything I could do with program code about this, I can
do with setserial, and even explain how to do it.  Isn't it reasonable
to expect that a programmer would be willing to learn how to use the
peculiar tools of its chosen OS?

OTOH she had warts, and if native SetCommState will take any dam'
bauderate and do something vaguely appropriate with it, maybe the
builtin one should too.

I guess I can take a bash at it, if no one else wants to.

Lawson
---oof---