|
272
|
Calculator Community / TI Z80 Calculator Projects / Re: zStart - an app that runs on ram clears
|
on: 26 July, 2011, 05:40:20
|
Actually, there's one thing CalcUtil does that zStart doesn't: allow log() to be used with arbitrary bases. I know MathPrint OSes have a logbase() function, but 2.53 was sooo buggy for me last I tried it.
Does your calculator have the full 128 K of RAM? It's a long shot, but what if MathPrint actually requires the host calculator to only have 48 K of RAM? Some people have reported that MathPrint works fine for them. |
|
|
|
|
277
|
Calculator Community / General Calculator Help / Re: My OS (2.43) is a heap of ruins!
|
on: 24 July, 2011, 22:05:53
|
|
It sounds like something got pretty seriously corrupted. You've already erased all your programs, appvars, et cetera? Do you mind resending all your apps and OS, too? Remove a battery for several seconds, hold MODE, and reinsert the battery. This will erase pretty much everything: the OS, all applications, and everything that was and is still in the archive. This is the boot code's self test function, which tests almost every sector of the flash chip.
|
|
|
|
|
278
|
Calculator Community / Lua Language / Re: Third-party ports of Lua to TI calculators...
|
on: 23 July, 2011, 00:04:51
|
Remember, the new 84+(SE) boot code is further proof that they're trying more actively than ever to lock things down.
I honestly think that TI doesn't understand the purpose of the RSA signature. I think they think of the signature as being akin to a real signature, and that factoring the keys means we can forge their real, legally binding signature. They upgraded to 2048-bit RSA because they don't want us forging their signature, not because they don't want us making 3rd-party OSes or patching the OS. Either that, or they actually don't understand that we had the ability to unlock flash years before we factored their keys, or the importance thereof. |
|
|
|
|
279
|
Calculator Community / Other Calculator Discussion and News / Re: Everyone Should Use Calcsys
|
on: 22 July, 2011, 07:30:35
|
Yeah. I got it cleared up with BrandonW. He says that he's not sure it'll work on all calcs, though.
MicrOS, by default, runs with flash unlocked. It also has a port monitor, so it's perfect for testing writes to protected ports. And the hex editor is way better than Calcsys's, in part because it was designed from the start to support flash editing. Calcsys should work fine on the Nspire. As far as I know, it really doesn't do anything strange; in fact, it tries to avoid modifying state unless you ask it to. |
|
|
|
|
281
|
General Discussion / Math and Science / Re: The Beauty of Mathematics
|
on: 22 July, 2011, 01:23:21
|
Make a plot of the length of all Roman numerals less than some value and you get a bell curve. EDIT: Code for the lazy: 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
| FUNCTION decToRom$ (num AS INTEGER)
DIM rom AS STRING
DIM dec AS INTEGER
DIM i AS INTEGER
DIM j AS INTEGER
DIM x AS INTEGER
dec = num + 1 - 1 ' Bonus points if you can explain why this is here.
IF dec < 1 OR dec > 3999 THEN ERROR 5
i = 1
DO WHILE dec / 10 > 0
x = dec - INT(dec / 10) * 10 ' Mod is for losers.
dec = INT(dec / 10)
IF x >= 1 AND x <= 3 THEN
FOR j = 1 TO x
rom = romchar(i) + rom
NEXT j
END IF
IF x = 4 THEN rom = romchar(i) + romchar(i + 1) + rom
IF x = 5 THEN rom = romchar(i + 1) + rom
IF x >= 6 AND x <= 8 THEN
FOR j = 1 TO x - 5
rom = romchar(i) + rom
NEXT j
rom = romchar(i + 1) + rom
END IF
IF x = 9 THEN rom = romchar(i) + romchar(i + 2) + rom
i = i + 2
LOOP
decToRom$ = rom
END FUNCTION
FUNCTION romchar$ (quark AS INTEGER)
romchar$ = MID$("IVXLCDM", quark, 1)
END FUNCTION |
|
|
|
|
|
282
|
Calculator Community / Other Calc-Related Projects And Ideas / Re: You can help us solve a few mysteries!
|
on: 19 July, 2011, 20:42:02
|
thepenguin77, your information is a little out-of-date. I did some more research on the flash chips: 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
| Known manufacturer IDs are
ID Manufacturer
01 AMD
04 Fujitsu
1C EON (read from 200h)
7F Extended code, read from 200h
C2 Macronix
Known device IDs are
ID Device
23 512 K (4 megabit) (5.0 V) (e.g. Am29F400B)
B9 512 K (4 megabit) (3.0 V)
C4 2048 K (16 megabit) (e.g. S29AL016J)
DA 1024 K (8 megabit) (e.g. S29AL008J) |
Notice how the TI-83+'s chip was originally a 5.0 V chip, but is now a 3.0 V chip? TI moved to 3.0 V logic. This means that the calculator will safely operate down to voltages of 3.0 V. (In fact, the flash chip data sheet says the maximum voltage you can safely supply to the flash chip is 3.6 V.) If you supply more than 3.0 V, the voltage regulator just converts the extra voltage into heat. TI really ought to update the TI-83+ OS not to signal low battery until 3.5 V, and redesign the case to accept only 3 AAAs---think of all the millions of batteries being wasted! The same goes for the TI-83+SE. It also seems that the serial port now operates at 3 V instead of 5 V. The TI-84+/SE will also operate at 3.0 V (confirmed with an assembly program running with interrupts disabled), but the USB port might not work right. |
|
|
|
|
283
|
Calculator Community / The Axe Parser Project / Re: Speed
|
on: 19 July, 2011, 06:59:08
|
I'm writing my first major Axe program and I noticed that the speed isn't much faster than BASIC. Is this because my TI-84+ is too old?  No it must be the way you are formatting your code. A 84+ runs at ~15MHz no matter how old it is. Maybe Er, no. The EOS kindly automatically reduces the CPU speed to 6 MHz before running assembly programs and applications so that any timing code runs the same. You're expected to explicitly set the CPU speed if you want to run at full speed. However, BASIC programs automatically run in fast mode. |
|
|
|
|
|
Powered by SMF 1.1.18 |
SMF © 2013, Simple Machines
Show Posts