I do not get the captcha on login.

I believe this started about the same time the bot filter was installed. What happens is that every now and then when I click on a link on omnimaga (just an ordinary link), omnimaga just becomes unresponsive. Stop/Refresh doesn't do anything at all and if I let it go long enough, chrome will ask me if I want to force close it. The only way I can get the page to load is to x out that tab and try again.

Also, it usually happens on the third omnimaga page I open. For instance, www.omnimaga.org > Forums > *click on topic in recent 15* <frozen> That topic will not open and the tab simply hangs on the Forum section.

Now, I hate to kind of be a jerk like this, but the routines you asked for are actually each major undertakings themselves. These aren't really things you just whip up. But, you are in luck because I have already written one of the more difficult ones.

Grouping/Ungrouping - This one sucked to make, but I actually did do it a long time ago. final version
Usage:
 Str3 = group name (all uppercase of course, 8 letter max) Ex: MYGROUP
 Str4 = list of programs to group with identifiers Ex: +A+B-IMPOSBLE-GROUP2
   Identifiers:
     + = regular program (you can edit it in the editor)
     - = protected program (you can't edit it in the editor)
 I'm not positive if it will work with the wrong identifier, never tried it.

Hex codes - Rather than giving you the hex codes, this program will spit out the hex code for a program name given in Str1. link
Usage:
  Str1 = name of program to unsquish with identifier padded to be exactly 8 characters with spaces (from above) Ex: -GROUP2__
  It will change the first letter of the program to an A and fill it with hex.
  To copy/paste the hex codes, just use RCL to recall the program. Ex: RCL prgmAROUP2

  However, turning already written assembly code back into hex is simply doubling the size.

Displaying Sprites - I'm sure you can find a program on ticalc.org.
Program list - That wouldn't be all that hard to make, but again, ticalc.org can probably help
Running a program - This is a serious undertaking. If you want to run simple unarchived basic programs and homescreen assembly programs, then I suppose you could probably find a 100 byte routine on ticalc.org. But if you want to start running ion, mirage, and dcs programs, then you are going to either need an app, or some serious hacking skills. Without hacking, (since the hacking would be unreliable), you are going to need to include all of the Mirage routines inside this subroutine and put them in the proper place. This really cannot be done without a shell. (zStart has an entry point for running programs, jussayin')
Getting program details - again, ticalc.org.

But honestly, like everyone has been saying, this is something you want to do in at least Axe. And really, axe isn't even designed for this kind of thing, asm is really the language that should be used for shells. If you are going to use BASIC, I would recommend you use the Celtic3 libs because they are included in DCS and requiring DCS isn't really the end of the world.

What kind of baud would the modem expect from the calculator and how accurate does it have to be?

The first problem is that the calculator only runs at 6MHz. This means your theoretical max baud would be 285Kb/s, the next would be 230, then, 206, 200, and then they get to more manageable increments. But, I guess if your expected baud is under 200Kb/s, you'd be ok.

However, a more severe problem is the lack of exact timing on the 83+, if your modem doesn't really care, it shouldn't be a problem, but no two calculators run at the same frequency. I can't give you exact numbers on the 83+ (because there's no timing system), but on the 84+ line, I've seen calculators all the way from 14.5MHz all the way to 17MHz. Since you are relying on the cpu to clock your data, you won't be able to get very precise timings.

However, if you sort out both of these issues, the rest should be relatively easy.

http://ourl.ca/3302/70956


I was trying to tell calc84 that TI-Boy should totally work on newer 84+'s. In hindsight, I was right

Now, this might be a stupid question, but if you removed that one component in the production Nspires, could you then modify boot 1?

Hardware hacks aren't really the best option for modding, but a simple desolder would be a cool alternative to constantly fighting TI. (Or even just breaking the component)

Edit:
    Nevermind, looking at datamath, I see that the extra component is on the prototype, not the production model. Adding components wouldn't really be a viable option for many people.

Fullrene has always worked on Wabbitemu. The problem was that it didn't work on some 83+BE's.

What needs to be changed that it works on a TI83Plus? There's no fast mode and I'm not sure about the $83 ram page, could you explain that?

You'll have a great deal of trouble get perfect grayscale on an 83+BE in the true sense with this method because there are several things at work against you.
1. Without fast mode, you're going to have to make a very optimized routine, this is totally possible
2. You don't need the extra ram page, it just makes things much cleaner for my grayscale routine. Writing your own routine would allow you to use whatever ram you want, (probably two $300 byte buffers) but if you insist on using mine, you can clear out the first $600 bytes of ram through some hackery (though, TI-OS won't work in this state.)
3. Finally, probably the one that really strikes down this method, is the fact that the 83+ does not have crystal timers. The best you could do on it (if you plan to do things besides display pictures) is to use the regular interrupts which default run at 118Hz. For very specific cases, you could use every other interrupt for grayscale, but this will only work at a screen refresh of exactly 59Hz. Most likely, you're going to want to go with the interrupts running at 560Hz. Using this method, you'd have to use variable skips and delays to ensure the grayscale draws occur at the proper time. This is possible with enough thought, but it would be very difficult.
(4). Combining problems 1 and 3, anything that runs with perfect grayscale is going to run very slow. The step 3 delay design is going to burn a lot of t-states waiting for the proper time to go. Then, since it's only running in 6Mhz mode, you can get way less done when the actual program is running.

So, verdict. Possible - in theory. Difficulty - high. To give you an idea, this ranks up there with calc84's sound routines in ti-boy.