This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - flarn2006
1
« on: July 29, 2017, 11:17:30 pm »
Lionel Debroux would be best to explain this since my memory is fuzzy. I think part of it may be that historically, TI was pretty stingy about signing third-party flash apps so people could release them (it was only until more recently that the community cracked all the signing keys themselves, and by this time 68k development was much less active), and TI's official dev tools were rather awful.
Another guess is that I would assume that making apps that fully interface with the OS might involve a lot more work and overhead and may require calling OS routines that are much slower than simply rendering to the screen oneself. I could be wrong on this, though.
Wait, they had to be signed by TI? So each individual app had to be approved? That sucks...though I guess not much anymore now that the keys are ours  I never understood why TI was like that, not allowing the installation of OSes or Flash apps that haven't been signed even on non-Nspire calculators. On the Nspire I can understand they may have something to gain because the OS does restrict what you can do with the calculator (though I don't see what reason there is beyond preventing bypassing PTT and even then I doubt the testing organizations would insist they be as hostile as they have been) but the other calculators already give you full access to the system by way of ASM programs. What reason could they possibly have for not allowing third party operating systems and requiring applications in a specific format to be signed, if they're still fine with letting you run whatever unsigned code you want in the stock OS just by using a different application format that has the same level of access to the system as everything else? If they don't have any problem with people running unsigned code with full access on their calculators, why would they care more about one format or method of execution than another?
2
« on: July 29, 2017, 07:55:12 pm »
Just wondering, why is it that on ticalc.org there's so few Flash apps for the TI-89 (Titanium)/TI-92 Plus/Voyage 200? Are they like super hard to write or something? They seem much more user-friendly than ASM.
I know they're ASM programs technically; I meant the kind that are installed and run like BASIC programs are. And Flash apps have many benefits that those don't. Like how you can switch between apps, run them in split screen, etc. I can't really think of anything ASM programs can do that Flash apps can't (not even being run as functions; Flash apps can do that too.) So why aren't Flash apps the more popular one? Aren't they better anyway, even without RAM limits on non-Flash apps?
3
« on: July 29, 2017, 04:32:26 pm »
Just wondering, why is it that on ticalc.org there's so few Flash apps for the TI-89 (Titanium)/TI-92 Plus/Voyage 200? Are they like super hard to write or something? They seem much more user-friendly than ASM.
4
« on: November 06, 2014, 11:47:23 pm »
I'm bumping this because I think I may have found a solution. I've been able to get it working again briefly by leaving the batteries out for a while, but that had always been a temporary solution. I eventually decided to open it up to see if there was any obvious hardware damage. I opened it, no obvious damage. But apparently the simple act of opening the calculator itself did something that fixed the problem. Not only does it seem to be running noticeably faster, but the ON+F4 menu works as well; since I ran that code none of the menu options had done anything until now. It's not immediately obvious how to open it, but easy when you know how. In case anyone else is having that problem, open the battery compartment, and you'll see these two light-grayish rivets. Take a screwdriver or a knife or something and pry at them until the wide part of the rivet comes off (just the part that sticks out past the black surface it's on) and then you'll be able to easily pry it open by sticking a screwdriver in the seam between the middle silver part and the black part on the back, when looking at it from the side. Then just snap the cover back on, and hopefully whatever happened to fix it for me will work for you as well. EDIT: Never mind, it still seems to be intermittently having that problem 
5
« on: May 21, 2013, 07:55:06 pm »
Oh okay, I didn't notice the edit button at first. Thanks!
7
« on: May 21, 2013, 07:47:12 pm »
You know that thread where the signing key for the TI-83 Plus was revealed? It was called "Fun Number Theory Facts". I've been unable to find an archived version of it. Here's the link to the thread, which is now broken. Looking on web.archive.org gives me most of the thread, but the earliest version has the OP removed.
8
« on: July 13, 2011, 09:38:38 pm »
I was fooling around with the built-in assembler on my 49g+, and ran this program: !ASM
LDR R0,[R1]
@It reset and the memory was cleared, but it was suddenly very slow. I did a soft reset (ON+F3) to see if that would help, but now the screen is blank. I tried leaving the batteries (including the memory backup battery) out overnight, and that didn't work. I also tried following the instructions at http://www.hpcalc.org/hp49/pc/rom/ under "If it fails:" in case the firmware was erased, but no menu appeared. More than a month later, I tried turning it on, and it appeared to work fine. I was able to perform several soft resets. Eventually, however (the next day) it started getting very slow again, and now the screen is blank again. What should I do? To reproduce what I did (at your own risk!): 256 ATTACH "!ASM
LDR R0,[R1]
@" ASM EVAL
9
« on: July 11, 2011, 01:17:00 am »
That's pretty useful stuff, actually.
I don't see how it would be useful for hacking the calculator other than the software version, which you can get without going into the diagnostic menu.
10
« on: July 10, 2011, 11:58:51 pm »
There are some interesting features in them though. Search for the threads on the diagnostic menu for the nspire and you'll see what I mean.
I just looked up the thread on how to access it, and I did it on my 1st-gen CAS, and I don't really see anything in there except for the basics--testing memory, display patterns, keyboard test, SW version; stuff like that.
11
« on: July 10, 2011, 09:52:16 pm »
Um, most diagnostic menus are "For Factory use only." It just means there are diagnostic features in there that no user is ever supposed to need. You can ignore the message.
It's just that the way it's worded makes me think Casio would rather users not do that. And I ignore the message anyway; they can't tell me what I can and can't do with my own calculator, lol.
12
« on: July 10, 2011, 08:53:17 pm »
When you press the key combination to trigger the diagnostic menu (calc off, hold OPTN+EXP+AC/ON) the following popup appears:
=DIAGNOSTIC MODE=
Factory Use Only!
Press : [EXIT]
The way it says it's for factory use only, coupled with the fact that it tells you to press EXIT and gives no indication on how to open the actual menu (F1, 9) makes me think Casio has some reason why they wouldn't want the end user entering the diagnostic menu. Why would this be? Sure, it clears the main memory, which could be an inconvenience, but as soon as you press F1 it asks you to confirm.
13
« on: July 10, 2011, 05:02:46 am »
...can you please remove that annoying loading animation from Insight? I doubt anything is actually being loaded.) cfxm asked me once how to draw outside of the regular display bounds. This animation is only a demo, how to achieve this (as most of INSIGHT is how-to-do source). I can implement it as separate menu item. Until the next release of INSIGHT you can cancel the loading animation with EXIT.
Thanks; I don't know why I didn't try that. BTW, you should add editing capabilities to the memory viewer. Maybe also add a feature to hex-edit files/variables without using a computer. Also, somebody mentioned using the -m3 flag in gcc, but not only doesn't the man page mention that flag, but if I google "gcc m3" (no dash in the search, as that would be interpreted as without m3) all I find is stuff about using GCC to compile for some processor called the Cortex M3.
14
« on: July 10, 2011, 03:56:58 am »
We've come a lot farther with the Prizm in six months compared to what was done to the Nspire - it took years before code could be executed on it! Also, some of the activity has been on other forums and IRC, which is why you don't see a lot of topics here. Most of the things that we've been focusing on is opening up the Prizm, not actually creating games and programs for it. The game development is probably going to bet a boost during the summer (at least I hope so...)
Oh, okay, that makes sense. I don't think Casio actually tried to lock anything up or prevent third-party development though, as TI did, so that's probably why the nSpire took so much longer to hack. (Why would TI want to do this, anyway?)
15
« on: July 10, 2011, 03:51:18 am »
Well, you'd have to use GCC and the -m3 flag to compile C programs for the Prizm with a Mac.
Is there any tutorial available? I don't know much about GCC or compiling on the command line; I can compile a simple C program using GCC but that's about it.
|
Show Posts