Instead of declaring the new serial buffer within the function, declare a
pointer and call MemPtrNew with the size you need, use it, free it and be
done. This works fine for me. Throwing a 1k buffer on the stack while you
call the subsequent serial port functions that use it is asking for
trouble...
/// Chris Terwilliger
/// Motorola - iDEN Software Development
/// office: 954-723-5318
/// mobile: 954-325-0345
/// [EMAIL PROTECTED]
/// http://www.idendev.com
-----Original Message-----
From: Mike Musick [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 25, 1999 1:48 AM
To: [EMAIL PROTECTED]
Subject: SerSetReceiveBuffer vs. OS 3.3
Under 3.0 and 3.1, this was fine:
char serPortBuf[1024];
...
SerSetReceiveBuffer(serialPortRef,&serPortBuf,sizeof serPortBuf);
However, POSE with a 3.3 debug ROM is claiming that serPortBuf is in low
memory, and this seems to follow user reports that the app isn't stable
under 3.3.
Any ideas (outside of NewSerialMgr) ?
...mike
------------------------------------------------------------------------
pocketAPRS - APRS for the Palm Connected Organizer
Website: http://www.pocketaprs.com
Application: ftp://ftp.tapr.org//aprssig/palmstuff/palmaprs/pcktaprs.zip
Map Files: ftp://ftp.tapr.org//aprssig/palmstuff/palmmaps/
------------------------------------------------------------------------
