lol
Can you also do something like NoDone EQU FDCB00AEC9?
That would be useful to add to the ti83plus.inc.

Not really at all, because in ASM, it's just easier to say res 5,(IY+0).  *shrugs*  I mean it's easier for me at least.

Quote from: Deep Thought on March 23, 2011, 10:25:19 am

Yep, that's exactly what http://tibasicdev.wikidot.com/hexcodes#toc9 does, but more readable
EDIT: ...for everyone except Xeda112358

Why do you say that?

Xeda112358 has the uncanny ability to only be able to understand the stuff if it's in hex form.

Well, the temporary, ie not PrizmSuite, one is going well.  I'm trying to finish it asap.

Quote from: graphmastur on March 22, 2011, 07:23:04 pm

Quote from: Eeems on March 22, 2011, 07:21:16 pm

Quote from: graphmastur on March 22, 2011, 07:13:30 pm

Yeah, I found out it won't work because my CPU doesn't support PAE.  So, awesome.  I'm going to try downloading/burning for my other computer.

PAE same here

Hm. Well, it's obviously the kernel you are using that's the problem, but PAE should run fine on my CPU.

Apparently, although I don't know why this would happen.
I myself use the most recent linux kernel (albeit the ubuntu branch) with no problems. I guess I'll have to rebuild this and see if I can fix it or something.

Strange.  Both Ubuntu PAEs work on my computer. (Desktop and Server)

Yeah, I found out it won't work because my CPU doesn't support PAE.  So, awesome.  I'm going to try downloading/burning for my other computer.

What's "op4"

It's a 11 byte location in memory.  There are OP1 through OP6.  Thy are used to store names, and such.  It's really an ASM thing.  Look here: http://wikiti.brandonw.net/index.php?title=83Plus:RAM:8478

And it also explains why I still haven't figured it out.  Okay, so let me look....

So Qwerty.55 gave me this:
Loop:
   MOV.W @R1,R4
   ADD $FF,R1
   ADD $FF,R3
   TST R2,R2
   BF/S Loop
   MOV.W R4,@-R2
and said it compiled into:
   6411
   71FF
   73FF
   2228
   8FFA
   2245
The 8FFA being the BF/S statement.  So FA == -6 right?  So that's per instruction, meaning 12 bytes back, or 6 instructions back.  So, from the 6411 to the 8FFA is 8 bytes.  Okay, and 4 bytes ahead makes it 12.  I see.  Well that's not stupidly complicated.  I just kinda had to put that out there in writing and I guess it made sense.

I still don't see why you &'d $FFFFFFFE though.  Wouldn't it already be even no matter what?  Considering if you reference the number of instructions with displacements. IE. Function B references to go back to Function A.  Function A and B are both on an even displacement.  Function B references A, which is, let's say, 5 instructions back.  Since you multiply it by two to get the bytes, you always get an even number of bytes back, and instructions always start at even numbers.  So yeah, why did you & $FFFFFFFE?

That isn't really a necropost at all, for the record.

And is there somewhere online where these are all hosted together?  Like 83 plus in 28 days was hosted on dragonfire, I think.

So, is that a concept screenshot, or what?  Any progress on this?