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 - Windows Release 6 is not only glaringly bug ridden (ex. the 'constructor' was incapable of properly editing bitmaps and creating small icons), it was/is user hostile. Selecting "help" produces an error (file not found) and the bug reporting links in the documentation are broken. What is clear to anyone who works with software is that no 'patch' is ever going to address this sorry state of affairs. Some of the bugs (ex. I can mess up all the menu bars by opening and closing a dialog box, progress indicators render differently from run to run, etc.) are clear indicators that the software is poorly designed and implemented. At a guess I would say, 'First attempt at a Windows app'. All the inherited Mac'isms would seem to indicate 'so-so port' as well. That is why every patch and incremental update has opened as many new problems as it closes. It is also why some bugs, like '100% CPU utilization', keep reappearing. What I think the other lister was really asking was 'When is Metrowerks going to produce a release that reliably runs and can edit large resource files safely? Say, quality on par with DevStudio for regular Windows...' I suspect that the answer is never. Microsoft is stupendously profitable and can afford large loss leader investments (like when they took on Borland to win back the Windows tools market). The Windows development market is also huge, which gives a very different investment/return formula than Palm OS tools. Personally, I'd be happy if you could get the quality to what I expect in embedded tools like SDS, Diab Data, and so on. With Motorola in the equation, that just might happen, we'll see. -jjf -----Original Message----- From: Heather Tufts [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 31, 2000 3:07 PM To: Palm Developer Forum Subject: RE: Tired of CW bugs - "Failed to connect to remote"!! > 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 > 'reboot every 2 seconds' to 'formatting & reinstalling windows' > Is there a less deadly solution? Is metrowerks ever going > to release a patch??? "Failed to Connect to Remote" means just that -- something failed when the debugger tried to connect to whatever it was trying to connect to. Several patches have been released to improve debugger stability, but it's hard to know how to help you specifically, when you don't provide any specifics (I guess you're on Win2k, but that's all I can figure out). I did check out database, and could not find an instance when you emailed [EMAIL PROTECTED] or [EMAIL PROTECTED], so I'm not sure when we "blindly categorized it as a Win2K issue." I'd be glad to help if I knew what the specific problem was. -hkmlt -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
