X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Andrew Cottrell <andspamtrap DOT at DOT swiftdsl DOT dot DOT com DOT dot DOT au AT unknown DOT addr>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: PMCOM10 Stops working after a period ?
Date: Tue, 27 Apr 2004 17:46:51 +1000
Organization: HOME
Message-ID: <dk3s80lq2gacms40d9ke56qr0vu518a8ag@4ax.com>
References: <c6atq1$5i5$1 AT reader11 DOT wxs DOT nl> <flbj80h4njcm8pt2v553k74sevhsujb662 AT 4ax DOT com> <c6igq2$t91$1 AT reader13 DOT wxs DOT nl>
X-Newsreader: Forte Agent 1.93/32.576 English (American)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 21
NNTP-Posting-Host: 202.154.115.197
X-Trace: 1083051477 news.syd.swiftdsl.com.au 27647 202.154.115.197
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

>Version 1.1 beta still doesn't work whith my application !
Have a good look a the source code and you will find that you have a
buffer overrun problem with one of the PMCOM funcitons. A hint is to
look at COMReadBuffer definition, especially the nCount variable!!!1

>What happens if a interrupt can't be handled in protected mode ? (eg using
>high speed+ function in RM)
Give DSCOPE a try to see what the comms is. It supports sniffing on
two com ports so you can see the TX and RX. This is assuming you build
the sniffer cabling correctly:-
	TX => Sniffer Com Port #1 RX
	RX => Sniffer Com port #2 RX
	Signal GND connected to Signal GND on poth COM Port #1 & #2

#1 and #2 could be any com port, but you may have to modify the code
as there are some assumption that may not be correct if you have 4+
ports.


Andrew