FlashToRam has the quirk that on the TI-83+SE/TI-84+SE, it can read from RAM pages 80h-87h, but not on the TI-84+ non-SE. However, on all models you can use it to copy from regular memory in the 8000h-FFFFh region. See also the Wiki page.

True. Also, you can tell _flashToRam to read ram from the $8000-$FFFF region and it will. At this point, it doesn't even matter what you set as the page to read from since it's not going to change the page swapped into $8000 or $C000. You could even use _flashToRam as a horrible replacement for ldir.

now that i think about it, you should get thepenguin to stick an incarnation of this in zstart. that way, people wouldn't be put off by other hooks being overwritten, and it would probably be very popular.

I could do it yes, but I don't know how I would do it and not mess up any of the current hooks (when I do that, people get angry).

You could do this (though not as nicely) by simply setting shortcuts for an entire menu in chronological order.

But what if you lose it? It's easier to get hold of a philips head screwdriver.

Find a flat head screwdriver that fits into the torx heads. (You can file it a bit if you need to). I have 1 screwdriver that can take out every single screw on my calculator.

I was wondering if it would be a good idea to connect the +5V and GND of the usb connection of a TI-84+ to the battery + and -. I would place a switch inbetween ofcourse (in case of willing to use with batteries and usb). The batteries deliver 4.8-6V (rechargeable and non-rechargeable), so the 5V of the usb would be the perfect voltage. I'm not really sure though, since it might maybe somehow destroy something, and I don't want that.

The reason I want to change this is because I only use my 84+ on my desk near my pc, and not even often, just sometimes for some gametesting for the forum here. I don't use it enough, so everytime I want to use it I have to begin a giant quest to find the needed batteries for it. With the usb connected, i'd just have to connect it to my pc and get started...

I'm a little confused as to what you are going to do exactly. I see two options:
1. Strip a USB cord and stick that straight into the battery cartridge of the 84+
2. Internally wire the calculator's own USB port into the battery cartridge

For option 1, it would totally work without any restrictions. I believe the 84+ uses a max current of like 42mA and the minimum for USB spec is 100mA, so you should be fine.

For option 2, I have no idea what would happen. The ground of the USB is probably the same ground as the battery cartridge, so that probably wouldn't be a problem. But when you wire the USB positive to the battery cartridge positive, weird stuff might happen. I guess the only way to find out would be to try it. If it doesn't end up working, you could install a hook (I could make it) so that you can selectively disable USB so that the calculator doesn't actually try to connect to the PC/wall.

Well, we can't just let a 0 reply post sit here, so here is my better version of your routine.

                                ;you don't need to do the $FF thing
        ld      a, $FD
        out     (01), a         ;once this is set, you don't have to reset it unless you change it
        ei                      ;this is for the halts
waitKey:
        halt                    ;this will lower battery usage (lol) and is roughly a 1/100 sec delay
        in      a, (01)
        add     a, a            ;moves bit 7 into carry position
        jr      c, waitKey
        halt                    ;this is known as debouncing, when keys are pressed, they often barely
        halt                    ; connect, disconnect, and then solidly reconnect
        halt                    ; without debouncing, you might accidentally press the button twice
        in      a, (01)         ; this is only needed in menus (and even then, it's optional)
        add     a, a            ; the .03 sec delay was rather arbitrary
        jr      c, waitKey

        ret

Not only does mine do key debouncing, but it ended up smaller

Could you find some repeatable way to trigger this? Or a screenshot perhaps? That would allow us to figure out what is actually happening.

That sounds fine to me. I gave it a 5-star for stability in my chart as well as a 4-star for collateral damage (but that was because I didn't actually know).

So I think you're good.

Quote from: Streetwalker on November 23, 2012, 02:43:02 pm

Well, when I use zStart 1.3.010 (the one linked in your sig), this problem doesn't exist. But with 1.3.010b (the one four posts above), any time a BASIC program calls input or prompt, the calc will freeze and I have to pull a battery.
Edit : It happens exactly when I press enter to confirm my input.

Just bumpin' this report as it seems like no one saw it.

I saw it, but I don't update zStart that often (I also didn't want to make a second sub-update). My only reply could have possibly been like "OK" or something. And since Hayleia's post started a new page, I didn't see it again to quote you.

But have no fear, every time I update zStart, I begin at the previous update and fix every problem that someone mentions.