Path: chuka.playstation.co.uk!scea!greg_labrec@interactive.sony.com From: jamin1@psu.edu (Jamin Frederick) Newsgroups: scea.yaroze.programming.codewarrior Subject: Re: System memory Date: Wed, 23 Jul 1997 17:26:23 GMT Organization: SCEA Net Yaroze News Lines: 31 Message-ID: <33d63d08.2134142@news.scea.sony.com> References: <01bc957d$ffb78880$9fbf43ce@wkwerner> <01bc9580$b51472e0$9fbf43ce@wkwerner> <01bc96f0$7f4cfa80$9dbf43ce@wkwerner> NNTP-Posting-Host: nb6ppp250.cac.psu.edu X-Newsreader: Forte Free Agent 1.11/32.235 That's what I thought as well. You may still use PSComUtil without rebooting, but to use siocons, you need that "brick" screen. By the way, MAKE SURE you do not use PSComUtil if an MS-DOS prompt is currently active. On my system if you do, you can't use PSComUtil thereafter even if you close MS-DOS and reenter PSComUtil. It seems like it refuses to reidentify the serial connection, since it didn't work last time! My only resort is to reboot the computer. Can some Metrowerks guys confirm me on this?? Jamin On 22 Jul 1997 22:42:22 GMT, "Wayne K. Werner" wrote: >Joel Sumner wrote > >> Is there some reason that you really need the brick screen to come back? > >> You don't need to reset your Net Yaroze after running the program. The >> debugger will just re-run it for you (or run another program). >> >Don't need that screen... I just assumed that the system was not there if >the screen didn't return. As long as the console is still talking to me, >that's good enough. > >-- >Wayne K. Werner >wkwerner@con2.com