Path: chuka.playstation.co.uk!scea!peter_alau@playstation.sony.com From: jamin1@psu.edu (Jamin Frederick) Newsgroups: scea.yaroze.programming.codewarrior Subject: Re: MW lib functions Date: Tue, 09 Jun 1998 22:10:06 GMT Organization: SCEA News Server Lines: 42 Message-ID: <357db28a.2397597@news.scea.sony.com> References: <35732b4e.21105758@news.scea.sony.com> <35756B94.EAF78E22@hinge.mistral.co.uk> <6l3ufs$6o11@chuka.playstation.co.uk> Reply-To: jamin1@psu.edu NNTP-Posting-Host: MAXWELL.hq.ensco.com X-Newsreader: Forte Free Agent 1.11/32.235 I'm very interested. Can you send it to jamin1@psu.edu? Jamin On Wed, 3 Jun 1998 17:13:50 +0100, "Steve Dunn" wrote: >Craigs ARS is excellent ;O Although I've never found any problems using the >serial MW functions. >I've recently added ARS to also include support for the MW reads and writes. >This addition also comes with a new windows front end, with the biggest bonus >being it also works on NT. The front end also includes facilities for doing >everything that can be done with an AR or GS via buttons, including viewing >registers and memory, sending bytes and long words, sending files, and >reflashing(with the Datel ROM obviously:) If anyone shows even the smallest >amount of interest in this, I'll upload it. > >Steve > >>Jamin Frederick wrote: >> >>> Has anyone gotten the MW file i/o functions (MWDebugIO.h or >>> something -- I forget, I'm mailing from work...) to work properly with >>> a relatively large program? I got the functions to read and write to >>> files on my PC with a bare-bones program, but when I copy the same >>> code to my project, which is considerably larger memory-wise, I get >>> hardware exceptions from within the MW functions -- I checked the >>> memory map and the error address. Anyone else successful or >>> experienced these problems?? >> >>The MW file i/o stuff is a tad unstable - that's why I wrote ARSto replace >>it........ >> >>> Jamin >>> jamin1@psu.edu >> >> >> > >