Mail Archives: djgpp/2002/01/07/11:25:12
--- Alex Oleynikov <alex AT compuweigh DOT com> wrote:
> Hi,
>
> I am also using PMCOM library and have gone thru
> many different situations.
> There are couple of things I would like to suggest
> you:
> 1.Instead of constant polling for content of RX
> buffer register a
> user-defined handler when opening the COM-port. This
> way PMCOM library will
> call your routine every time something came to the
> COM-port (make sure to
> check that your handler was invoked in response to
> the receiving event and
> not sending or timer events, since this handler may
> be also registered for
> timer operations).
Could you give me some sort of example of how to do
this? I'm not sure on how to do this...
> 2.Look at your crash dump and see where the
> termination occurs. It is
> possible, that you are working with debug release of
> PMCOM and it has a lot
> of
> assert( ) calls throughout the code to check for
> different conditions.
> For example, you are trying to read from a closed
> COM-port etc.
Well, at some point a graphical window comes up (not
mine, because my program is text-based) with the
following error-message:
The instruction at "0x0f00115e" referenced memory at
"0xffffffff". The memory could not be "read".
> Also, what version of PMCOM library are you using?
v1.0
Maybe you could tell me if there's a new version of
PMCOM, which has some improvements over this version?
Roland
__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/
- Raw text -