Ted,

>From the information provided, I suspect that you are using a Palm OS 3.1 or
later ROM with POSE 2.0b3 which came with R5. 2.0b3 does not support those
ROMs. You should update your installation of R5 with patches from
www.metrowerks.com/download (search for CodeWarrior for Palm Computing
platform 5, install Patch 1 and Patch 2 in that order), as well update POSE
to version 2.1d29 from www.palm.com/devzone/pose/seed.html. You will also
need to install the debugger plugin from the same page - after you install
Patch 1 and Patch 2, of course. This should resolve the problem.

Rgds,
Jun-Kiat Lam
Metrowerks Technical Support

----- Original Message -----
From: Ted Lowery <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 02, 1999 8:48 PM
Subject: [Fwd: POSE Problems]


> I'm having major reliability problems using POSE.
>
> I am now working from a virgin install of Codewarrior (version 3.1 Build
> 0135), a virgin install of POSE (version 2.0b3), a rom I downloaded from
> a PalmPilotProfessional, and a virgin project that constructor built,
> I've added none of my own code.
>
> After I restart my computer, I can run POSE and debug my project ONCE.
> Everything seems to run ok.  After I kill the process, the next time I
> try to debug, I get one of 4 error messages:
>
> 1.  Failed to Connect to remote
> 2.  Transport timeout error
> 3.  Can't debug this executable because no appropriate debugger nub can
> be found.
> 4.  Unknown Error Code: 0x0408
>
> The frequency and pattern of error codes is somewhat reproducible.  No
> matter how many times I quit codewarrior, restart POSE, remove objects,
> rebuild, anything short of restarting the PC, nothing seems to help.
> Once I restart, the debugger will work flawlessly ONCE.
>
> I tried downloading POSE (version 2.1d29) to see if it gave me a
> different behavior.  I've also downloaded several other ROM files from
> the Provider pavilion, and I get the same behavior.
>
> I'm assuming needing to restart my computer after each use is not a
> "feature" of the debugger.
>
> Anybody seen a problem like this and have any suggestions for fixing?
>
> Incidentally, I'm running this on a Dell Optiplex, PII with 64MB RAM,
> nothing else running in the background.
>
> Any ideas?
>
> -Ted
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>

Reply via email to