Path: chuka.playstation.co.uk!news
From: Andrew Partington <andrew.partington@peregrine.com>
Newsgroups: scee.yaroze.freetalk.english
Subject: Re: Hey all!
Date: Tue, 18 Dec 2001 13:11:17 +0000
Organization: PlayStation Net Yaroze (SCEE)
Lines: 52
Message-ID: <3C1F4075.C94D812E@peregrine.com>
References: <9vklpa$4234@www.netyaroze-europe.com> <3C1F1F8B.753790C6@peregrine.com> <9vncvp$4238@www.netyaroze-europe.com>
NNTP-Posting-Host: 194.207.193.91
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en

Hi Max

When I installed these patches I reinstalled CW from scratch
beforehand.  Apparently there is a certain order in which you have to
apply the patches - I *think* you install the IDE/debugger patch after
the first one, although I couldn't swear to that in court :)

If you are using PSComUtil, then it doesn't exit back to the brick
screen like siocons does after your program has terminated.  I think
that it will still let you upload programs/data though even though it
looks like its hung.  I seem to remember some menu option somewhere
saying reconnect or reset or something, and some sort of text output
somewhere telling you the connection status?  I'm not 100% sure about
that either though (I personally use CW/siocons and avoid PSComUtil like
the plague, but then again i'm still running win98!)

Andy



Max wrote:
> 
> I am getting the same problems now, I have an AMD and when running a
> Codewarrior .pse file it
> freezes upon exit. I have tried first the first patch then the second then
> both together and not one of the
> combinations seems to work, I have no optimisation as I'm still operating in
> debug...
> 
> Any answers, clues?
> 
> Max
> 
> > Yeah, thats pretty much the situation with the patches.  I don't think
> > that the patch was a fix specifically for AMD machines though, just a
> > general CW patch.  The reason I thought it was an AMD issue is because
> > that was the 1st time for me to do anything with one (i'd been using
> > pentiums up until that point), it just turned out that I had kept my old
> > PC updated with the latest patches while my old desktop was just lying
> > around not getting used much, so it wasn't getting updated.  When I
> > swapped the drives over I forgot about this and thought it was a
> > hardware issue, duh!! :)
> >
> > Since I have installed the patch I can now exit cleanly back to the
> > brick screen with level 4 optimisation on, which definitely makes a
> > difference in GG [>240 VSyncs down to around 140 in the worst case :)].
> > But unfortunately it doesn't fix the assembler - CW doesn't seem to
> > recognise some of the opcodes that the debugger shows you, and as for
> > labels, forget it :(  [unless of course I am using it wrong, always a
> > possibility :)]
> >
> > Andy