Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Benoit0123 Newsgroups: comp.sys.apple2.programmer Subject: Re: Query about ProDOS 8 Date: Sun, 3 Sep 2017 09:34:34 -0000 (UTC) Organization: Mac GUI Lines: 44 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sun, 3 Sep 2017 09:34:34 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="0561f52aa4ed808c6529d56d790d6d68"; logging-data="3458"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18bisJwCh7i0qESUH/cnYcY" User-Agent: Mac GUI Usenet In-Reply-To: Cancel-Lock: sha1:Y9z6g1SHw+C8g82mxUOPFGiMvgc= Xref: csiph.com comp.sys.apple2.programmer:3900 Thank you John and Roger for the advice which I am already following (cf. previous csap post on the subject). John Brooks wrote: > Out of curiosity, what ProDOS calls are being made in the IRQ handler and > why? It sounds like a pretty unusual use-case. > > -JB > @JBrooksBSI > John for your curiosity: I am using the SET_MARK/READ and SET_MARK/WRITE MLI calls to read/write an already opened ProDOS file on a big proDOS device (Omnidisc in my dev env. but this likely a RAMFactor RAM memory card or other slinky Apple //e memory card) in the "end user" environment). This is for getting a detailed (ie. per module beginPC, endPC) ) gathering of application performance and being able to gather data that would be analyzed afterwards in an "offline" mode. Two external commands one for creating and pre sizing the big data file, looking up an interrupt source (preferably 1millisecond but defaulting to mousecard VBL (50/60ms)) and finally (second BI external command duties) inhibiting the source, deallocating the interrupt service routine from ProDOS chain and closing the file. I presume this to be run on a slotted Apple //e (enhanced ROM), a memory expanded ROM Apple //c or a 2GS. John, as you're quoting the /RAM[3] device driver you're designing for next ProDOS kernel version, please would you setup a way for such driver to not take over the whole set of memory banks (configuration option) and this let part of the RAM works compatible card usable by other third party utilities (like a memory storage for Applesoft arrays, a spooler for "old" printers, and other "exotic" ways of using it (I'm sure the community at large will make creative use of this available space in the future ;-) ). Best regards, Benoît -- Growing old is mandatory.. growing up is optional.. But the other way round is as true.