Update your version of Metrowerks since some bugs have been fixed in the
post linker.
You could try turning off the redirect netlib option. Some have seen
success if you keep POSEr in the foreground during a download and tap the
Graffiti area repeatedly just as POSEr's screen goes blank. If that doesn't
work, you're SOL. Its a known bug and still exists in R6 I hear its fixed
if you use NT and doesn't exist on the Mac side. I've found I need to close
Metrowerks and POSEr after each debug session and before starting a new
session, otherwise I run the risk of totally locking up my system. I've
tried it on 95, OSR2, 98 98OSR2 with little improvement. If you find a
work-around for this annoying bug, please post it.
Dave
-----Original Message-----
From: Ted Lowery <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, November 02, 1999 9:53 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]
>
