TIP: Click on subject to list as thread! ANSI
echo: telix
to: STEPHEN JURBALA
from: RICK COLLINS
date: 1997-03-30 08:10:00
subject: Telix and Windows

-=> Quoting Stephen Jurbala to All <=-
-=> FidoMail to 1:163/215, please.-=<
sj> I've recently started using Telix through Windows instead of in
sj> DOS but every now and then I have a problem downloading mail
sj> packets. I get a "Bad CRC" error and then a lot of garble when
sj> I abort. I never had that problem while in DOS. Does anyone
sj> have any idea what might be causing it and how I can correct it?
It's usually caused by interrupt latency: the inability of the PC to
read data from the comm port quickly enough in some conditions.  The
fix is to use a 16450 UART on the comm port (you can check for this
type of UART with MSD - look under "Ports").  It's also possible you
need a better comm driver than the Windows 3.x standard COMM.DRV,
_especially_ if you're using Telix for DOS in a Windows DOS box.
I'd suggest CYBERCOM.DRV, available on BBS systems everywhere.
TTFN. Rick.
Ottawa, ON 30 Mar 8:13 
--- Blue Wave/DOS v2.20
---------------
* Origin: BitByters BBS, Rockland ON, Can. (613)446-7773 v34, (1:163/215)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.