Difference between revisions of "Talk:83Plus:Ports:21"
From WikiTI
Thepenguin77 (Talk | contribs) |
|||
Line 35: | Line 35: | ||
I said it very sneakily. Unless you specifically know what you are looking for, it won't mean anything to you. If it's too early though, feel free to change it back. --[[User:thepenguin77|thepenguin77]] 14:00, 1 October 2011 | I said it very sneakily. Unless you specifically know what you are looking for, it won't mean anything to you. If it's too early though, feel free to change it back. --[[User:thepenguin77|thepenguin77]] 14:00, 1 October 2011 | ||
+ | :Er, it's not quite right. 02 does not lock 2C. |
Revision as of 08:06, 3 October 2011
I've been looking into this port a bit more, it seems to control ram execution restriction. Only bits 0,1,4, & 5 do anything. I 'm not exactly sure what the lower nibble does but I have looked into the upper one.
Upper Nibble | Page 87 | Page 85 | Page 83 | Page 81 |
3 | Restricted | Restricted | Restricted | Allowed |
2 | Restricted | Restricted | Restricted | Allowed |
1 | Restricted | Allowed | Restricted | Allowed |
0 | Allowed | Allowed | Allowed | Allowed |
I post this on the talk page because I don't think there is enough yet and I haven't tested on the 84+SE. Also the 84+ has this port set as 0, yet that seems to crash the 83+se. Hopefully someone has a better clue than me.--Jim e 22:00, 19 Aug 2005 (PDT)
I said it very sneakily. Unless you specifically know what you are looking for, it won't mean anything to you. If it's too early though, feel free to change it back. --thepenguin77 14:00, 1 October 2011
- Er, it's not quite right. 02 does not lock 2C.