Path: chuka.playstation.co.uk!news From: daniel@reichardt.ch (Daniel Hartmeier) Newsgroups: scee.yaroze.programming.codewarrior Subject: Re: PSComUtil Date: Mon, 10 Aug 1998 08:15:10 GMT Organization: Reichardt Informatik AG Lines: 27 Message-ID: <35d2a9c5.6006336@news.reichardt.ch> References: <35C1ECA7.12DFD52F@ndirect.co.uk> <35C5D332.E2E678AA@easynet.co.uk> <01bdbefb$e9f5a2e0$f30b0a0a@Angela1.intelligent-group.com> <35C5F6A9.8BF63F43@ndirect.co.uk> <35C9AB72.9C1CFC68@nospam.easynet.co.uk> NNTP-Posting-Host: empty229.magnet.ch Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Newsreader: Forte Agent 1.5/32.451 On Thu, 06 Aug 1998 14:11:14 +0100, Phil Gooch wrote: > Anyway, is there a way of avoiding the PSComUtil message of the instruction > exception at address 0x0 when main() ends? Craig, you said that you can resend > the pxe, but I can't get this to work, because when main(), the Yaroze freezes > under PSComUtil I'm experiencing yet another behavior: when my program returns from main(), there is no exception, but main() is automatically _run_again_. Instead, I'd like to get to the brick screen. I couldn't find any documentation regarding this matter (is the return value of main() relevant?). The program is written in C++ with CodeWarrior. Do the changes I had to make to get C++ working in some way affect program termination? Is there a function I can call from within my program that returns the machine to the brick screen? Having to press the reset button every time is frustrating. Regards, -- Daniel Hartmeier PGP 6A3A7409 ICQ# 12742482 "The woods are lovely, dark and deep. But I have promises to keep, And lines to code before I sleep, And lines to code before I sleep."