I've used them, I just didn't know what they were called.

I'll look into making it work when the edit buffer is open

If (cxCurApp) == $40 (homescreen)
ld hl, (editCursor)
ld de, (editTop)
or a
sbc hl, de
ld (op6Ext), hl

bcall(_closeEditEqu)


;do stuff

;#########################################
fixEditBuffer:
bcall(_closeEditEqu)

bit 5, (iy + $44)
jr z, notMathPrintEnabled

ld hl, saveSScreen
ld bc, 767
bcall(_memClear)

xor a
ld (menuCurrent), a
bcall(_clrLCDFull)
ld hl, cmdShadow
ld de, cmdShadow+1
ld bc, 127
ld (hl), $20
ldir
bcall(_clrTxtShd)
bcall(_homeUp)

ld hl, $40
bcall(_pullDownChk)
bcall($5125)
set curAble, (iy + curFlags)
res curLock, (iy + curFlags)
ret

notMathPrintEnabled:

bcall(_setupEditCmd)
tryIt:
ld bc, (op6Ext)
ld a, b
or c
jr z, bufferIsZero

ld hl, (editTail)
ld de, (editCursor)
ldir
ld (editTail), hl
ld (editCursor), de
bufferIsZero:

ret



In the ASM programs in which it does work, it carries the potential to break them if they expect OP1 to remain intact across a bcall(_GetKey)

;#########################################
pushOP1:
push af
push bc
push de
push hl

ld hl, -12
add hl, sp
ld sp, hl
ex de, hl

ld hl, 12
add hl, sp

ld bc, 10
ldir

ld hl, op1
ld bc, 12
ldir

pop hl
pop de
pop bc
pop af
ret

;##########################################
popOP1:
push af
push bc
push de
push hl

ld hl, 10
add hl, sp
ld de, op1
ld bc, 12
ldir

ld hl, 10+12-1
add hl, sp
ex de, hl

ld hl, 10-1
add hl, sp

ld bc, 10
lddr

inc de
ex de, hl
ld sp, hl

pop hl
pop de
pop bc
pop af
ret

That's how I do it. <.< >.>

Edit:
   Forgot about a prerequisite of the first routine, it's good now though.

There's one I bet not many people have seen on a real calculator.

There's a big bug with the Mathprint division thing, which most of the time crashes my calculator and some other times divide the screen into half, and the cursor blinks at the middle while everything else fill in the upper half of the screen. It's like you have Horiz on but worse. This bug only happens with Alpha F1, n/d, both in Mathrpint mode and in CLASSIC mode. Other Mathprint stuff is fine.

Yeah, this is actually hardware related, though, we're really not sure how. What's the serial number on the back of your calculator? Somehow Ti messed up pretty bad.

1. The first interrupt occurs from hardware timers as opposed to crystal timers.  I assume that it's normal and that there's nothing I can do about it?

You could turn the regular interrupts off. "XOR A \ OUT (03), A". After the out, you won't have another normal interrupt until you restart port 3.

2. The 84+ uses two of the three timers.  Which of the three is free to use?

All three are always free to use. The OS does use two timers, but that is only during USB stuff. I'm not really sure how the rumor got started that you can only use one of them, because you can use all three at any time. I guess the only time you couldn't is if you are in a hook, but you shouldn't use them in a hook anyways.

The run on home option appears to break the Basic Menu( command. It always gives Label errors even if the label is valid.

EDIT:
The calculator froze when I was at the bottom of the program and selected bottom from the ON+Vars lbl menu.

Noooooooooooooooooo. Darn, not bug proof. I'm not sure why the first one happens, but it's definitely true. The second one only happens if you are at the start of the last line though.

Also, I figured out that you can't edit programs in math print.


So... I guess that means there will be a 1.3.001, however, I'm going to wait a bit to release it, because I want to catch all of the errors. (I didn't find this stuff because I use basic at most once every two months)

Awesome. I wonder if this could fix Zeldaking/p2 issues?

This should be able to fix any problem with your archive. I believe the program is crash proof, so it should be able to recover any valid program in the archive.

On a side note, like the earlier version, this only saves programs, protected programs, appvars, and groups, everything else is ignored. So don't count on your archive pictures to still be there.

What is this wizardry?!
How does it work?

I'll explain the process.
1. Find the first page starting at the end of the archive that is not an app, AND it with $FC and store that.
2. Find a suitable swap sector.
    a. First scan the archive for a sector that starts with $FE (swap) or $FF (blank)
    b. If that didn't work, look for a sector that doesn't have any valid programs in it
    c. If that didn't work, screw it and use page 8.
3. Starting on page 8, and ending at the page found in step 1, begin copying everything to the swap sector.
    a. First, search the page for a program that has a valid header (valid meaning not erased, good type, good length, and 0 < (name length) < 9)
    b. Copy that program to the swap sector making sure to set the new address and page to where you are copying it
    c. When the end of a sector is reached, erase it and continue on to the next one
    d. If the swap sector runs out of space, just find a new one. (By this time, page $0C is guarenteed to be open.)
4. Find one last swap sector and copy sector 8 there (program by program because of the valid page thing)
5. Mark sector 8 as the swap sector and clear ram (to rebuild vat)

That's about it. I didn't include any code to try to optimize how the variables are stored in the archive, but, as you make new variables, they'll take up the little spots at the end. This was mostly done to increase speed, and because it would just be annoying to add.

Cool . I've never had issues, but I think I'll keep this topic in mind.
So, the TI-OS will claim another sector from the user sometimes? Interesting.

Ti-OS won't claim another sector, but some program might accidentally. If you write 00 to the first address of any sector, the OS will just stop using it. If it sees that the sector is invalid, rather than deleting it, it just ignores it.

Edit:
   Source attached for your enjoyment.