Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: awanderin Newsgroups: comp.sys.apple2.programmer Subject: Re: Can anyone see a way to improve this ? Date: Mon, 27 Oct 2014 21:35:29 -0600 Organization: A noiseless patient Spider Lines: 50 Message-ID: References: <34030b70-c7cb-4b31-a99a-6b44c3877066@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="adfb6bbd1e1493191f3136a944e5344e"; logging-data="13563"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19tP4bFP0KYq2IQkVaHJUeQadgDU2pVjsY=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:zVVuqq1B81kbuq6SZDo+nPPCKNo= sha1:V7+El1FC8kGNHXPM6athHffdx6Y= Xref: csiph.com comp.sys.apple2.programmer:1374 mdj writes: > Hi, > > Below is a memory test loop for 1 page - assume the high order bytes > get replaced for each page being tested. Zero page is deliberately > avoided - this runs in either the language card or the $800-$BFFF area > of main memory, testing pages of auxiliary memory without assuming any > given byte of aux memory works. > > The obvious one is to unroll, which I'll do. Just wondering if I'm > missing something else obvious. > > Thanks, > > Matt > > > LDX #$00 > NEXTBYTE LDY #$08 > LDA #$01 > NEXTBIT EOR #$FF ; Set and check complement first > STA $2000,X > CMP $2000,X > BNE ERROR > EOR #$FF > STA $2000,X > CMP $2000,X > BEQ CONT > ERROR JSR FLAGERR > CONT ASL > DEY > BNE NEXTBIT > INX > BNE NEXTBYTE > RTS > FLAGERR RTS ; Record this meaningfully in the future > > > For a thorough discussion of strong memory-checkers, see this article: http://www.ganssle.com/articles/ramtest.htm I guess it depends on how confident you are in the machine's RAM in the first place. -- Jerry awanderin at gmail dot com