Hi JB,

Actually, I think R6 will _not_ work with the latest Pro 5 patch (Pro 5.3).
It will work with a merged CW Pro 5 up to Patch 5.2, but Pro 5.3 had some
significant changes that breaks the R6 components. Sorry, you will probably
need to either stick to Pro 5.2 for merged, or separate folders.

Jun-Kiat Lam
Metrowerks Technical Support

----- Original Message -----
From: "JB Parrett" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 03, 2000 6:32 PM
Subject: Re: CodeWarrior R6/Mac Problems


> >Because of my previous problems getting R6 to run on a Mac (OS 8.5.1) I
> >just uninstalled and restalled with a complete standard installation, and
> >then tried to run the IDE with all extensions off. It successfully
launched
> >and exited, but when I tried to launch it a second time, I got a Type 3
> >error. Based on this any my previous problems, it appears that
CodeWarrior
> >R6 for the Mac is so unstable as to be unusable. Has anyone gotten it to
> >run successfully (such that it can be used for real development) on a
Mac?
> >Thanks.
>
> Steve (and other Mac users),
>
> I may have spoken too soon in my last post concerning CW6 on the Mac.
> It was working fine merged with CW Pro 5 until I updated with the
> latest Pro 5 patch. It now crashes on every other download to the
> debugger or every other edit/link/compile cycle.
>
> Sigh - I think the Mac version has finally reached parity with the
> Windows version... :-)
>
> I will go back and reinstall CW6 on one volume and Pro 5 on another
> (just like the old days).
>
> JB
>
>
> ----------------------------------------------------------------------
> JB Parrett                         603-673-5046
> True North, Inc.                   603-673-5035 FAX
> 9 Pulpit Run                       [EMAIL PROTECTED]
> Amherst, NH 03031-1510             http://northisup.com
>
> Tranquilo Pa: A wise Paraguayan phrase that means 'you might as well
> just bask in the sheer weirdness of it all.'
> ----------------------------------------------------------------------
>

Reply via email to