Here you go; the password is same as the original. It might be best to avoid saving documents while editing a spreadsheet cell, to avoid this bug.

Edit: The bug is caused by the combination of two things: a colored row, and saving while editing a cell. Loading a spreadsheet that was saved while editing a cell somehow tries to retrieve the color of a cell in column -1, and if there exists a colored row, that crashes.

Anything larger than 4GB won't fit on the TI-Nspire anyway. I say just stick to the ANSI standard, universally available 32-bit functions on all platforms.

Two bugs related to replacing & and < in lua source with character entities:

* escape_special_xml_chars stops processing when it reaches the offset equal to the size of the original input ("p < in_buf + header_size + in_size"), not taking into account that the size is changing during the loop, so characters near the end of the program may not get escaped
* xml_compress copies the footer without taking into account the change in size ("memcpy(in_buf + header_size + in_size, lua_footer, sizeof(lua_footer));"), resulting in a truncated program and garbage at the end of the xml

...I don't like BASIC.
~ducks tomatoes/rocks surely being hurled~
I just mean, in order to introduce people to programming, you don't HAVE to use it. Show them console programs, echoing, then adding, then doing Fibonacci numbers, then blackjack... it's really not any more "fancy" than Basic if you're doing it right. (Just don't do Visual Whatever - those are the worst!)

Then, you can tell them more about how each thing is working lower down - maybe just gloss over compilation with something like, "What you type gets converted from English to numbers that the computer can understand" - since, for one function programs, that's pretty much all that's involved (what's a optimizing compiler?)...
You can delve as deep as you need to, but it's important to give people something they can work with at the same time. BASIC's syntax has also become a little arcane. Start them with C/C++/Java/Python, I say.

I learned programming with GW-BASIC and later QBasic, and I have since then never seen a programming language that beats QBasic for starting out.

C and its derivatives are awful first languages IMO because of how difficult it can be to debug problems. Write past the end of an array in C and the program will usually crash in some completely unrelated place; do the same in Basic and you'll get a "Subscript out of range" error on the exact line of the problem. I was an impatient kid; if I had started out with a C family programming language I probably would have given up on programming.

A problem with starting with Java and Python is they force you to use pointers all over the place (and they don't make this fact obvious) - in Java, a "Foo x;" variable doesn't really hold a Foo object, it holds a pointer to a Foo object, and in Python, every variable holds a pointer. I constantly see new programmers having trouble because they're confusing pointers with the objects they point to - which is very understandable when the language doesn't even make it clear that you're working with pointers. Just imagine being a beginning programmer trying to explain something like this:
>>> a = [1, 1]
>>> b = [a, a]
>>> b
[[1, 1], [1, 1]]
>>> b[0][0] = 2
>>> b
[[2, 1], [2, 1]]
Basic didn't have any pointer variables (well technically, string variables held a pointer, but since it was impossible to make two string variables point to the same string, this fact didn't cause trouble for the programmer). But it did have arrays (including real multidimensional arrays, something sorely missing in Java and Python). Any structure you might think you need pointers for - linked lists, binary trees, etc - can be done almost as easily with arrays; the downside is that you're stuck with a fixed array size, but when you're starting out, you don't really care about scalability. The great thing about arrays is that they're intuitive - even a beginner can understand that "I" isn't the same thing as "A(I)", and it's possible that "A(I)=A(J)" even when "I<>J". And once you've mastered arrays, pointers are easy - they're just indexes into that giant array we call "memory".

Why did you change the character constants 'w', 's', etc into their much-harder-to-recognize numeric values 119, 115, etc?

You may also have a look at nspire_emu's source code to understand low-level interactions with the flash chip.

That code is not based on any documentation or testing at all; it's just the bare minimum of accuracy to make TI's OS work. If you're not doing things exactly as the OS does, then emulation and reality will very likely differ.

Try "sudo chmod 777" in that directory.
Or, you can run a file browser as root

It should not be necessary to use sudo or run anything as root in order to change the permissions on a directory that you created.

Edit: On Linux, read permission on a directory means being able to list the files in it, while execute permission means being able to access the files in it (provided you also have access to the individual files). These are probably already both set. It's execute permission on the nspire-gcc file that might be missing.