Page 1 of 1

Identifying Oric-1

Posted: Fri Dec 15, 2017 3:25 pm
by polluks
Hi!
Do you know a suitable zero page address to identify an Oric-1?

Thanks,
Stefan

Re: Identifying Oric-1

Posted: Fri Dec 15, 2017 3:35 pm
by Chema
I cannot tell by memory but I think I once checked using the address of the interrupt Vector in ROM.

I am nearly sure I did it in Oricium so you can have a look at the sources. Check the keyboard.s file... just in case.

When I get to a computer I may have a look at it.

Re: Identifying Oric-1

Posted: Fri Dec 15, 2017 5:33 pm
by iss
Take a look in Atmos ROM disassembly: http://www.defence-force.org/ftp/oric/d ... sembly.pdf
There are lot places marked with V1.0 and V1.1 which show differences in both versions - most are in page 2.
If the question is exactly for a zero page address then you can use $31 - Screen line width.
In Atmos ?PEEK(#31) returns always 40, in Oric-1 - 80 (or 93 if DOS is loaded) (which is actually BUG :)).
BTW, this is used in SEDORIC too.

Re: Identifying Oric-1

Posted: Fri Dec 15, 2017 9:07 pm
by polluks
iss wrote:
Fri Dec 15, 2017 5:33 pm
Take a look in Atmos ROM disassembly: http://www.defence-force.org/ftp/oric/d ... sembly.pdf
There are lot places marked with V1.0 and V1.1 which show differences in both versions - most are in page 2.
If the question is exactly for a zero page address then you can use $31 - Screen line width.
In Atmos ?PEEK(#31) returns always 40, in Oric-1 - 80 (or 93 if DOS is loaded) (which is actually BUG :)).
BTW, this is used in SEDORIC too.
Perfect, I will use this.
I can even code:

Code: Select all

BIT $31
BVS ORIC1