gilles wrote:
>> The even bytes are junk, usually 0xFF is a good value to return there. >> Offset 24 is the even byte for 0xfcc017, >>
Ah... ok... 0xfcc049 means "drive present (FF=yes)" - so you'll want to return 0xffff if it's read as a word... I think I recall Xenix checked for this sort of thing too - but for the disk present flag at 0xfcc041 instead.
I pretty much return 0xff or 0xf-something for non-implemented memory as a rule (except for those spaces that should cause bus errors.) I sometimes use 0xf7 or some other value, but almost always use odd values incase there's a bug that uses that as a pointer - in which case, it'll get caught as an odd-address exception.
Also be aware that some I/O spaces repeat, for example the VIA and SCC
regs show up at multiple addresses so you need to figure out a binary
AND mask when accessing them...
i.e. (addr & 0x79)
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "LisaList" group. To post to this group, send email to lisalist_at_email.domain.hidden To unsubscribe from this group, send email to lisalist-unsubscribe_at_email.domain.hidden For more options, visit this group at http://groups.google.com/group/lisalist?hl=en -~----------~----~----~----~------~----~------~--~--- Received on 2008-03-20 08:47:39
This archive was generated by hypermail 2.4.0 : 2020-01-13 12:15:21 EST