My apologies for the furious mail. It is one of those
days
Heather Tufts [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Does this mean your patches are mutually exclusive? and work
only on certain platforms and fail on others?
To answer your question - I am using NT 4 SP 6
Heather Tufts [EMAIL PROTECTED] wrote in message
Failed to Connect to Remote means just that -- something failed when the
debugger tried to connect to whatever it was trying to connect to.
Though English is a foreign language to me, I do know
enough of it to understand the literal meaning of
My apologies for the furious mail. It is one of those
days
"Heather Tufts" [EMAIL PROTECTED] wrote in message
news:28919@palm-dev-forum...
Does this mean your patches are mutually exclusive? and work
only on certain platforms and fail on others?
To answer your question - I am using NT
Your statement is incorrect. "Failed to Connect to Remote" does not always
mean "just that". I won't bore you with the details, but a quick inspection
with SoftICE shows that this symptom will show itself in response to 3
distinctly different problems in the tool set.
Let's review history -
Heather Tufts" [EMAIL PROTECTED] wrote in message
"Failed to Connect to Remote" means just that -- something failed when the
debugger tried to connect to whatever it was trying to connect to.
Though English is a foreign language to me, I do know
enough of it to understand the literal meaning
Does this mean your patches are mutually exclusive? and work
only on certain platforms and fail on others?
To answer your question - I am using NT 4 SP 6 on PII/128.
This is not the intent, though we are aware that fixes to one bug have
created new bugs in other parts of the software.
The
Does this mean your patches are mutually exclusive? and work
only on certain platforms and fail on others?
To answer your question - I am using NT 4 SP 6 on PII/128.
This is not the intent, though we are aware that fixes to one bug have
created new bugs in other parts of the software.
(snip)
It would be nice if people with complaints that go along the lines of
"Why doesn't Codewarrior or Constructor do blah blah blah" formatted
their complaints as "Feature requests" rather than just whining. It's
really irritating...maybe Metrowerks should put up a list of suggested
features
MW had been very quiet recently and it is time for their yearly update. It
is my wild guess (or whish?) that they are either hard working on a version
of the next CW for PalmOS4 or too busy to spend any time on development
whatsoever.
TO help your current problem, 3 things generally work:
1)
I have seen several postings in this newsgroup
regarding the same error message when we
try to debug a program ("Failed to connect to remote")
MW had blindly categorized it as a Win2K issue
providing a fix which breaks more than it fixes.
I have seen many suggestions too - everything from
10 matches
Mail list logo
