JK did mention this about two months ago. That error message shows up when
any number of communications failures occur.
It's not like JK to not respond--he may be on vacation. If that's the case,
his backup is probably just answering the tech support queue and not
following this mailing list.
-E
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Jim Schram
> Sent: Monday, December 06, 1999 6:22 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Fwd: Metrowerks?!? (was RE: BDWM)
>
>
> At 4:21 PM -0500 1999/12/06, Tom Frauenhofer wrote:
> >Having reported this problem, too, the silence is deafening..
>
>
> Perhaps you've all missed Jun-Kiat Lam's previous posts on this topic?
>
> >Date: Tue, 9 Nov 1999 13:42:49 -0600
> >...
> >The error message itself is a bug; however, it typically
> indicates that the
> >debugger failed to connect to POSE or the device. The cause of
> that could be
> >from a variety of reasons...
>
> >Date: Fri, 12 Nov 1999 15:06:10 -0600
> >The error message itself is a bug. Actually, what it indicates
> is that the
> >debugger has failed to connect to POSE. There could a number of
> reasons why
> >that happened, ranging from debugging to a Color ROM (debugger doesn't
> >support that yet), app overruning 64K per segment limit (illegal
> app will be
> >built and POSE will reject that) to a debugger failing to
> connect. Try the
> >'CW Debugging Cache' in c:\Windows\Metrowerks to see if it helps.
>
>
> I'll add that deleting the CodeWarrior preference file may also
> fix the problem.
>
> Regards,
>
> Jim Schram
> 3Com/Palm Computing
> Partner Engineering
>
>
>
>
