I have an old model calc, though. =/

I do as well, and I've never encountered that problem.

I have had issues with Instant Goto and CalcUtil, but Darl has reported that before.

The nibble reading bug should pretty much never happen, since it will only occur if you try to read from one of 6 bytes inside the routine itself. I could see this bug maybe cropping up in something like a memory viewer program, but that's about it.

However, the old nibble reading routines were only 1-3 bytes larger than the current ones, so I think it may just be best to revert the changes. I would suggest reverting the $0000-$7FFF routine as well, because if the user had switched a RAM page into the $4000 slot with the help of assembly, the "application" nibble reading routine would have even worse effects than the RAM reading routine, as it would always corrupt the target data. Be sure to get the endianness of the old nibble-reading routines correct, though.

There isn't really a need to revert changes to the nibble writing routine, because if the user is writing a nibble inside of the routine, they're in trouble no matter what routine is being used.

Code: (Original routine: 18 bytes, ~72 cycles) [Select] p_Nib1: .db __Nib1End-$-1 scf rr h rr l ld a,(hl) jr c,__Nib1Skip rrca rrca rrca rrca __Nib1Skip: and %00001111 ld l,a ld h,0 ret __Nib1End:

Code: (Optimized routine: 17 bytes, ~105 cycles) [Select] p_Nib1: .db __Nib1End-$-1 xor a scf rr h rr l ld b,(hl) __Nib1Loop: rrd ccf jr c,__Nib1Loop ld (hl),b ld l,a ld h,0 ret __Nib1End:

Code: (Original routine: 18 bytes, ~68 cycles) [Select] p_Nib2: .db __Nib2End-$-1 srl h rr l ld a,(hl) jr c,__Nib2Skip rrca rrca rrca rrca __Nib2Skip: and %00001111 ld l,a ld h,0 ret __Nib2End:

Code: (Optimized routine: 15 bytes, ~77 cycles) [Select] p_Nib2: .db __Nib2End-$-1 xor a srl h rr l rrd jr c,__Nib2Skip rld __Nib2Skip: ld l,a ld h,0 ret __Nib2End:

Haha!  Interesting bug, unintentional self-modifying code... And Runer, isn't that 2nd piece of code only 17 bytes?  That's only a 2 byte total increase in size.

I count 18 bytes.

I've got a fake mem clear program compiled in 0.4.7 and it's now complete, but for some reason, it doesn't work when compiled in 0.5.1 and when I do a fake ram clear, the screen goes a little random.  NEED HELP (plus i need a few optimizations)

I've got a fake mem clear program compiled in 0.4.7 and it's now complete, but for some reason, it doesn't work when compiled in 0.5.1 and when I do a fake ram clear, the screen goes a little random.  NEED HELP (plus i need a few optimizations)

Can you post your source code? It would be helpful.

Umm, I just compiled Aslyum as an App, ran it, and my memory went down from 350 to 0 when it exited.