Omnimaga

Calculator Community => Other Calculators => Topic started by: Munchor on May 31, 2011, 06:03:29 pm

Title: CX Memory
Post by: Munchor on May 31, 2011, 06:03:29 pm

I'd like to know how much memory the CX has and how much is free (let's say only the OS is there). Thanks

Title: Re: CX Memory
Post by: Ashbad on May 31, 2011, 06:21:07 pm

iirc, I think it has 64MB RAM and something like ~100MB storage, with the OS taking up 25-28MB in storage.

Title: Re: CX Memory
Post by: Levak on May 31, 2011, 06:26:27 pm

ROM : 115Mo for user (seems to be a 128Mo chip)
As said Ashbad, 64Mo of RAM

Title: Re: CX Memory
Post by: BrownyTCat on May 31, 2011, 06:33:37 pm

Quote from: Levak on May 31, 2011, 06:26:27 pm

ROM : 115Mo for user (seems to be a 128Mo chip)
As said Ashbad, 64Mo of RAM

HOLY-

Title: Re: CX Memory
Post by: AGVolnutt on May 31, 2011, 09:49:07 pm

Windows 95, anyone?

But that is a lot of ram for a calculator. Storage space seems par.

Title: Re: CX Memory
Post by: pianoman on May 31, 2011, 10:17:21 pm

64 Megs of RAM???
Holy Bananas!!!

Title: Re: CX Memory
Post by: ruler501 on May 31, 2011, 10:26:08 pm

That is excellent for a calc

Title: Re: CX Memory
Post by: Lionel Debroux on June 01, 2011, 01:56:20 am

64 MB of RAM is great, but they have cheaped out on storage...

Title: Re: CX Memory
Post by: Munchor on June 01, 2011, 02:47:35 am

Woah! O.O 64 MB of RAM is so much, we have 24 MB in the 84+ :P

That's just great :) Thanks for the info.

Title: Re: CX Memory
Post by: JosJuice on June 01, 2011, 04:44:46 am

Quote from: Scout on June 01, 2011, 02:47:35 am

Woah! O.O 64 MB of RAM is so much, we have 24 MB in the 84+ :P

Not really. The 84+ has 24 KB. :P

Title: Re: CX Memory
Post by: ruler501 on June 02, 2011, 02:19:23 pm

so Nspire is 1000x more RAM :O

Title: Re: CX Memory
Post by: z80man on June 02, 2011, 03:17:16 pm

Well that's not all that surprising as the screen is 16 bit color and is a much higher resolution than the 84+. Also code size is significantly higher too. I'm just wondering if the OS ever uses all of that ram though.

Title: Re: CX Memory
Post by: ruler501 on June 02, 2011, 03:20:32 pm

I wonder if its possible to use all of that memory

Title: Re: CX Memory
Post by: Levak on June 02, 2011, 03:22:56 pm

It was the fact for the half RAM space (32Mo) on the TI Nspire non-CX

Title: Re: CX Memory
Post by: Ashbad on June 02, 2011, 03:23:51 pm

most likely, Lua programs would only be able to use a small fraction of that 64MB, since that's too much and TI isn't THAT generous.  Plus, the OS looks like it would need a lot more RAM than previous OSes.

Title: Re: CX Memory
Post by: ruler501 on June 02, 2011, 03:24:52 pm

what if we were able to use the Nspire to its full potential...
*ruler likes this dream

Title: Re: CX Memory
Post by: z80man on June 02, 2011, 03:25:11 pm

I have heard though that the stack can be overflowed in Lua. That's were the possibility of an ndless exploit is right now.

Title: Re: CX Memory
Post by: Ashbad on June 02, 2011, 03:27:48 pm

That's very true.  In Lua to overflow the stack all you need to do is something highly recursive:

Code: [Select]

function foo()
  foo()
end
I don't remember the procedure from there, but from there you have only a slight-limit of writing space where you can write to memory unchecked for a bit.  Using the stack overflow procedure to run/load Ndless programs would be a bit slow, though.

Title: Re: CX Memory
Post by: ruler501 on June 02, 2011, 03:29:02 pm

Maybe they could make it so that when ndless loads you can just run the programs without needing that overflow anymore. You'd just need it to load ndless

Title: Re: CX Memory
Post by: Ashbad on June 02, 2011, 03:37:03 pm

Well, I think a good idea (in theory) would be this approach:

1. Keep the compiled binary data for the C/ASM program in an undisturbed format in a fake Lua file.
2. Change around an area of RAM so that the instructions in it allow for executing of assembly code.
3. Exit the Lua version of Ndless and if placed in the right location, the OS will trigger the binary calling routine you embedded and will run the C program.