0 Members and 1 Guest are viewing this topic.
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.
Generally I've been able to get past the problem by archiving everything not archived (except for the u var) and clear ram.
Quote from: Darl181 on December 29, 2011, 07:45:54 pmThat 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.
Quote from: ztrumpet on December 29, 2011, 08:57:22 pmQuote from: Darl181 on December 29, 2011, 07:45:54 pmThat 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)?