[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Decoding RamFactor's memory detection

Subject: Re: Decoding RamFactor's memory detection
From: Hot Rod <hotrod.apple2@gmail.com>
Date: Thu, 16 Aug 2012 09:34:21 -0700 (PDT)
Bytes: 1692
Complaints-to: groups-abuse@google.com
In-reply-to: <36ba4972-0b6b-434a-8e58-653ed3b943ad@googlegroups.com>
Injection-info: glegroupsg2000goo.googlegroups.com; posting-host=75.73.130.159; posting-account=NsBJFwoAAACliuoc2Cfykslw7D5NuJ4-
Newsgroups: comp.sys.apple2
Organization: http://groups.google.com
References: <25618992-ab99-4b1a-9796-32bf3c96afd9@googlegroups.com> <1f1c346f-7db9-472e-b87f-790db7295566@googlegroups.com> <36ba4972-0b6b-434a-8e58-653ed3b943ad@googlegroups.com>
User-agent: G2/1.0

On Thursday, August 16, 2012 11:17:32 AM UTC-5, BLuRry wrote:
> So that means there IS no ram size detection?  That's just bonkers!
> 

That's a bit more difficult to say; those SBC ops are against (presumably) some memory locations ($CBDE,X; $CBE3,X), which condition the carry bit.  Those could be the tests, but not enough context to tell.

But the code snippet provided has some funny addressing - it seems to be ascending, but then jumps backwards, skips ahead? Not sure what to make of that.

Follow-Ups:
- Re: Decoding RamFactor's memory detection
  - From: BLuRry <brendan.robert@gmail.com>
- Re: Decoding RamFactor's memory detection
  - From: gids.rs@sasktel.net

References:
- Decoding RamFactor's memory detection
  - From: BLuRry <brendan.robert@gmail.com>
- Re: Decoding RamFactor's memory detection
  - From: Hot Rod <hotrod.apple2@gmail.com>
- Re: Decoding RamFactor's memory detection
  - From: BLuRry <brendan.robert@gmail.com>

Prev by Date: Re: Decoding RamFactor's memory detection
Next by Date: Re: Do you own Byte Works ORCA Languages?
Previous by thread: Re: Decoding RamFactor's memory detection
Next by thread: Re: Decoding RamFactor's memory detection
Index(es):
- Date
- Thread