Omnimaga
Calculator Community => TI Calculators => General Calculator Help => Topic started by: Nick on December 29, 2011, 07:25:22 pm
-
hi
i'm already having some troubles with my calc for quite a while, i don't know how, but these are the screen i get. I've already resent the os, and put in new batteries
it doesn't work to send files anymore, it gives "device doesn't recognize instruction".
I had a program TST, which you can see in the screenie, that was archived. Then i removed the "u" variable beneath it, got a RAM clear, and the content of the archived TST program was gone, although the program itself still existed.. all apps from archive are running normal
(http://img.removedfromgame.com/imgs/screen1.JPG) (http://img.removedfromgame.com/imgs/screen2.JPG) (http://img.removedfromgame.com/imgs/screen4.jpg) (http://img.removedfromgame.com/imgs/screen3.jpg)
these are the programs on the calc:
basic: counter, tst
other: axe, swords
thanks in advance
Nick
-
Do you have DCS7 in your calc?
-
nope, only:
basic progs: counter, tst
other: axe, swords
-
Hm this looks like what I've gotten multiple times..
That u var (one of the Y= vars), iirc, is created and written to if you try to modify something that comes after L1 and/or overflow L1. I'm guessing you tried to store something to the wrong part of the RAM :P
Not advised, but if you changed the mode of the calc from Func to Seq and pressed Y=, you'd see the var being written before a likely RAM clear.
Generally I've been able to get past the problem by archiving everything not archived (except for the u var) and clear ram.
-
That u var (one of the Y= vars), iirc, is created and written to if you try to modify something that comes after L1 and/or overflow L1.
Nope. u is one of the three variables the calculator uses during Sequential mode, like the Y0-Y9 variables it uses during Function mode. These three variables (u, v, and w) have nothing to do with lists.
Generally I've been able to get past the problem by archiving everything not archived (except for the u var) and clear ram.
This is what I'd suggest as well.
-
That u var (one of the Y= vars), iirc, is created and written to if you try to modify something that comes after L1 and/or overflow L1.
Nope. u is one of the three variables the calculator uses during Sequential mode, like the Y0-Y9 variables it uses during Function mode. These three variables (u, v, and w) have nothing to do with lists.
I was meaning L1 like how axe uses it as a pointer, so I'm guessing that if you write >714 bytes after saveSScreen it creates this (within a range anyway)?
-
That u var (one of the Y= vars), iirc, is created and written to if you try to modify something that comes after L1 and/or overflow L1.
Nope. u is one of the three variables the calculator uses during Sequential mode, like the Y0-Y9 variables it uses during Function mode. These three variables (u, v, and w) have nothing to do with lists.
I was meaning L1 like how axe uses it as a pointer, so I'm guessing that if you write >714 bytes after saveSScreen it creates this (within a range anyway)?
Ah, okay. I looked at it from a Basic perspective, not an Axe one. Sorry about that.
-
O.O this happened to me twice
I don't know what caused it, but it hasn't happened since then. :)
-
Axe syntax bugs can cause....interesting.....results. :P
-
it still is strange, but check the memory, not one byte is free. And when i archive a 12 byte prog, it has still 2 bytes left ???
an di'm able to send from calc to calc, but not from pc to calc (exccept for the os, that works..)
-
Do you use the command that moves the variable allocation position in axe? Putting that in the wrong place could easily cause what darl pointed out.
-
Well this happened to me a truckload of times while I was trying to make Tio have levelsets, it either overflowed the appvar I made or "L1" (Axe) and it would happen something like 8 times a day :P
...I'm guessing there's multiple ways to cause it?
-
Well, the VAT is a funny beast. I'm sure that it wouldn't be terribly difficult to corrupt.
-
well, i do no program in axe myself, so it must have something to do with the program that are in it then?
now he's totally screwed up, but i can still communicate with other calcs, but not with pc
it's really strange though
-
yay, my first calc works again, i can send files from and to pc again, everything works normally again..
don't ask me what i did exactly, i cleared ram 20 times, memory 100 times, archive 50 times etc etc lol
-
That's good to hear. It would suck if the calculator was defective or something. That reminds me... has p2 ever managed to fix his calc? If not, maybe he could try what you did?
-
well euh, like i told you, following me isn't such a great idea :) i just tried everything, and repeated that 100 times lol
but the last time, i cleared entire memory, than did Y1=2X, pressed graph, got memory error (not enough) than i cleared ram again, did Y1=2X again, and than it worked..
the last Y1=2X isn't needed xp that was just to proove