X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	"PT" <ptalloen AT hotmail DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: PMCOM10 Stops working after a period ?
Date:	Tue, 27 Apr 2004 16:48:58 +0200
Organization:	Planet Internet
Lines:	41
Message-ID:	<c6lrma$ehd$1@reader13.wxs.nl>
References:	<c6atq1$5i5$1 AT reader11 DOT wxs DOT nl> <flbj80h4njcm8pt2v553k74sevhsujb662 AT 4ax DOT com> <c6igq2$t91$1 AT reader13 DOT wxs DOT nl> <dk3s80lq2gacms40d9ke56qr0vu518a8ag AT 4ax DOT com>
NNTP-Posting-Host:	u212-239-176-5.adsl.pi.be
X-Trace:	reader13.wxs.nl 1083077130 14893 212.239.176.5 (27 Apr 2004 14:45:30 GMT)
X-Complaints-To:	abuse AT planet DOT nl
NNTP-Posting-Date:	27 Apr 2004 14:45:30 GMT
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1409
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

My test program is allmost the same as given in an example!
The problem is not that it doesn't work, but that it stops working.
As soon as i add a printf after the COMReadBuffer, the com lib stops
receiving data after +-2K of data. (there is still data on the cable -
verified with a datascope) (pc2 tx 20byte every 500ms)

I still think it has something to do with the RM-PM switching.
i'm gonna try to add the  _go32_dpmi_allocate_iret_wrapper function...

Any other idea's ?





"Andrew Cottrell" <andspamtrap at swiftdsl dot com dot au> wrote in message
news:dk3s80lq2gacms40d9ke56qr0vu518a8ag AT 4ax 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
>

- Raw text -