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 the above statement. I really appreciate your translation. > 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 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. The issue is not about whether your software has bugs or not. Why can't you just have two versions of the software - "Most stable version" (say 5.1.2...) and the "Latest version" (6.0.3) etc... I am ready to work with something that doesn't support multiple code segments, doesn't have syntax highlighting, and doesn't have "fast-link" ( does that really work? ) but compiles a given source reliably every time to a PRC and will never destroy my source. (before someone suggests gcc... don't, I already use it & I am happy with it) You guys were not able to make even the compiler stable (forget the IDE which may be a really complicated piece of software). How could we trust anything generate by the compiler which swaps numerator with denominator in a division!!, corrupts a bitmap while it is being linked in, and a linker which generates a GPF once in a while. Anyways, I use gcc on linux more often than CW on win. But once in a while (because of work), I have to jump in and work on a project that was developed on CW. -- Hari Warrier "Heather Tufts" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > > 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 ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
