By the way, another improvement would be for beginners to have a "launch wizard" if it's the first time you launch it, and that it builds the command line for you (which you wouldn't need to see eventually if you don't want to) from the different file you give it (boot1, boot2, OS, etc.)

Ah, didn't see

But still, next step is to integrate it directly within the program. And graphically while we're are at it

Configuring nspire_emu for the first time took SO LONG!! 

Hi there,
I've been submitting my SkinEditor to some 'facelifting' because the previous code is somewhat dated.


New features: Something has been added that might interest you, namely:
a) a MRU (Most Recently Used) list of file paths. Handy when we work with several files at the same time;
b) the 'key' size is shown on the statusBar while selecting/defining it, making the design a little easier;
c) the (many) menu options can be accessed via a toolbar (faster) ;
d) the 'properties' dialog has been streamlined (no more alien useless entries).

I'm also attaching a (new) skin sample which i've used to test this version (v1.05) of the kArmTI Skin Editor.
Be warned that some new glitches may still appear. Please tell me and i'll be happy to fix them asap. Do not delete (not just yet) the old one v1.04.

LBNL, thanks to all kArmTI enthusiasts for the thumbs up .
Cheers,

EDIT: updated the image-link to ImageSchack (somehow they've changed it ).

Good to see progress on this continuing.
@SpiroH, I liked the older skins you provided in your v1.13 preview you gave me many months ago. They fit on my screen. The new ones don't have a NON-CAS TI-nspire version, and they go off my screen (1280x800).
So I wonder why they were changed? The old ones were perfectly fine...

Wow that animated gif maker is surely gonna be a good addition considering Calccapture produces absolutely horrible GIFs. How big are files, though?

Also, lol. The GIFS are fine in CalcCapture, it's that the program is outdated is what I find annoying.

Hi, a couple of kArmTI skins.
Just in case you get bored with the standard colors, try the next colorful kArmTI skins:




They were built from scratch (well almost) with Photoshop just for the hell of it. I'm not an expert, but aren't we all learners of new technologies...

Have fun,

At first SpiroH you are awesome to do such great skins and work *thumps up* (I love the brown skin and new logo)
Second I was shocked as i found out that the CX emulation has only 32mb storage.  I think it is an emulation of a CX so it has to be over 100mb
Third are you going to add the quick icons and features (like hiding the keypad) from onspire ?
Finally, is it possible to upload files from the emu to the pc?

At first SpiroH you are awesome to do such great skins and work *thumps up* (I love the brown skin and new logo)

Thanks!

Second I was shocked as i found out that the CX emulation has only 32mb storage.  I think it is an emulation of a CX so it has to be over 100mb

Answered by Franz.

Third are you going to add the quick icons and features (like hiding the keypad) from onspire ?

Probably not at this stage, sorry. I'm busy doing other things. But you should still be able to run 'onspire' .

Finally, is it possible to upload files from the emu to the pc?

Unfortunately not at this stage. It is not (yet) implemented in nspire_emu. It shouldn't be too difficult though...

Quote from: Wayne on August 03, 2012, 05:53:15 pm

Second I was shocked as i found out that the CX emulation has only 32mb storage.  I think it is an emulation of a CX so it has to be over 100mb

It's possible to get a 128MB CX if you create the flash-image (Flash_cx.bin) with the following command:
kArmTI_v27 /1=Boot1_cx.img /MXC /PB=Boot2_cx.img /PO=CXCAS.tcc /N /R /K4

Thanks Franz!

On the same note, let me try to explain to the less tech-savvy what is involved when you configure the emulator to use more NAND and more RAM.

1. NAND (Flash memory normally used to store program's code and read-only data but not modifiable data - slow access time)
N32MB:    17.0 MB out of 27.8MB  (normal 32MB system)

N128MB:   103.8MB out of 115.2MB  extended with Nand 128MB  = +96MB  extra (emulator /N switch)


2. SDRAM   = faster access RAM memory used to store program's data (emulator /R switch))

Normal: SDRAM Size: 32MB


Extra_SDRAM: SDRAM Size: 64MB


3. Flash_file size increases a lot too (eg. for T310CXCAS):

     from 33,792KB to 135,168KB (an extra ~+100MB)

4. Memory allocated in the running system (eg mine) :

    Normal NAND_32MB and SDRAM_32MB        ==> Required System Memory: 121,428KB
    Extended NAND_128MB and SDRAM_64MB   ==> Required System Memory: 288,604KB

So, unless you really need to use more NAND and RAM (and to run some 'memory hungry' apps you really do!), imo, you should abstain from using the extra switches /N /R.
Of course, if you understand what you're doing, prepare 2 flash images and boot the one you like/need.

I hope this clears up the extra NAND extra SDRAM questions.

Cheers,

EDIT:

Does the gbSP-Nspire work on your kArmTI?

No, not at all! It crashes up front and freezes the emulator! it's still just an alpha release, we need to be patient. gbc4nspire works perfectly well, though.
If you would to like to play a few GBA games, try this great emulator VBA (http://vba.ngemu.com) is the one i use (well, not so much these days) which is great with sound and everything you ever sought-after!