Alarm Siren wrote:
The BBSx part of said datastructure:
Code:
bbs0<NUL>.<NUL><NUL><NUL><NUL><SOH>Ÿ <-- $9F
bbs1<NUL>/<NUL><NUL><NUL><NUL><SOH>¯ <-- $AF
bbs2<NUL>0<NUL><NUL><NUL><NUL><SOH>¿ <-- $BF
bbs3<NUL>1<NUL><NUL><NUL><NUL><SOH>Ï <-- $CF
bbs4<NUL>2<NUL><NUL><NUL><NUL><SOH>ß <-- $DF
bbs5<NUL>3<NUL><NUL><NUL><NUL><SOH>ï <-- $EF
bbs6<NUL>4<NUL><NUL><NUL><NUL><SOH>ÿ <-- $FF
bbs7‡<NUL><NUL><NUL><NUL><BEL><LF>
(new lines added by me for clarity).
Cool. I didn't actually expect you to humor me! And I hope you don't mind doing so; I admit I'm way out on a limb with this goofy idea!
The bytes you listed do roughly match what I vaguely imagined -- an array of data structures. I see each instance has twelve bytes (including four bytes for the mnemonic). And indeed the opcodes are in there, too, as predicted! For example, what prints as the character ÿ is really $FF (as per the notations I added above), and $FF is the opcode for BBS7. Likewise ï is $EF which is BBS6, ß is $DF which is BBS5, and so on...
... all except $8F aka BBS0 which is missing. I think there's a framing error in the way you've added the new-lines. Unexpectedly, the four bytes for the mnemonic appear at the
end of each structure, not the beginning. For example I mentioned ÿ is $FF, which is the opcode for BBS7, and see how ÿ
precedes the mnemonic bbs7? I'm afraid that at the end you listed some bytes which aren't part of the array, and at the beginning you omitted eight bytes which are.
It's easy to work backwards and predict what "should" be there. If the hex bytes 00, 2D, 00, 00, 00, 00, 01, 8F are prepended to your listing then the resulting pattern is consistent across all eight 12-byte structures. My goal was to see if that consistency is intact. But the anomaly, if any, would appear in the portion you accidentally omitted, so now I'm in suspense!
Would you mind checking, please, to see if the pattern is intact?
-- Jeff
PS and slightly OT -- or maybe not:
while preparing this post I noticed I could copy and paste most of the unusual characters (the ¿ and the Ÿ and so on) without difficulty, but I wasn't able to copy and paste the character encoded by $8F (which is the opcode for our problematic BBR0). Probably there's a simple reason, although it's not known to me (7-bit ASCII is the only encoding I have a solid grasp on). But perhaps $8F's lack of pastability, or a closely related issue, has a bearing on the puzzle at hand. It may only be coincidence. But $8F stands out as a case of "one of these things is not like the others" -- and that aptly describes the BBS0 puzzle as well.
_________________
In 1988 my 65C02 got six new registers and 44 new full-speed instructions!
https://laughtonelectronics.com/Arcana/ ... mmary.html