Path: csiph.com!news.swapon.de!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: mmphosis Newsgroups: comp.sys.apple2.programmer Subject: Re: Using ProDOS DOSCMD Date: Sat, 21 May 2016 01:06:25 -0000 (UTC) Organization: Mac GUI Lines: 23 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sat, 21 May 2016 01:06:25 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="ac9e0e4d7dd3957fb97803ee6801bab8"; logging-data="17373"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/VwEw7N7qookJpQ/AJJ9G0" User-Agent: Mac GUI Usenet In-Reply-To: Cancel-Lock: sha1:aiPBV96uFJv7HFOWAnrnI+wwDTs= Xref: csiph.com comp.sys.apple2.programmer:2737 I am not familiar with DOSCMD, but this is what I would do... JSR save80toCA ; at the beginning of your program ; ... your code that disturbs 80 to CA JSR swap80toCA ; before calling DOSCMD ; call DOSCMD JSR swap80toCA ; after calling DOSCMD ; ... more of your code that uses 80 to CA JSR swap80toCA ; might want to do this again before quitting your code. I did something similar to this in "Apple-1 for Apple II" to save and restore critical pages of memory that I clobber with my code.