This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - ParkerR
2
« on: November 02, 2012, 04:09:21 am »
Look at what you have done! (Hehe) http://i.minus.com/ib2FnBXqutLXmp.jpgIn all seriousness, I think a text terminal would work quite nicely on the old models. Wouldn't use it for video playback as much as just something to show to friends and maybe type some notes on. I say if you can add a few more functions to a device, no matter how mundane, it's worth doing. Looks very promising and can't wait to see what's in store!
3
« on: November 02, 2012, 03:45:52 am »
It's certainly possible to port Linux on the Clickpad and Touchpad, but those have less RAM (and a terrible screen), so the resulting Linux + userspace would be able to do less than on the CX. The CM and CX are (normally) extremely similar, and porting is bound to be straightforward, but very few people in the community have them.
Terrible screen? Yes it does ghost, as do most greyscale screens, but I wouldn't go as far as it being terrible. I would love to see some linux on my old blue non-CAS.
4
« on: August 05, 2012, 12:34:01 pm »
Seems like a version for the people on a budget. I like it.
5
« on: July 05, 2012, 11:53:21 pm »
....Ok so I went back to Skin1.skn and Texas-Instrument-Ti-Nspire_CX_CAS.png. I set the skin name in the skin editor to Texas-Instrument-Ti-Nspire_CX_CAS and set the Texas-Instrument-Ti-Nspire_CX_CAS.png as all three button states. Still doesnt show up.
I dunno what exactly you're doing to have problems. I would suggest the following: 1. I wrote a small skin tutorial you may check here: http://ourl.ca/9360;msg=253270 (3rd attachement) 2. I've used your 'skin1.skn', added a picture of mine renamed to 'Texas-Instrument-Ti-Nspire_CX_CAS.png' 3. Rearranged sligthly the positions of the LCD+buttons (so they fit inside the png i've used) 4. Saved the file which i'm posting for you to test (renamed to ParkerR_Skin1.skn). Please check attachment. 5. The skin named 'hyhyh' appears perfectly under: Keypad->Skins... popup (at the bottom of the list). 6. LBNL, for all that to happen, you need to: a) Place both files: ParkerR_Skin1.skn + Texas-Instrument-Ti-Nspire_CX_CAS.png in the 'SKINS' directory; b) Under Keypad menu: b1. Select the Touchpad keypad b2. Under Skins... select your skin 'hyhyh'. BTW: i've used Skin editor version, v1.04 (also at the bottom of the post mentionned above). You can download it and open the skin i've prepared for you. Under 'View' there's even an option to preview your skin (Review: Ctrl+R). Hope it helps.
I don't know if I completely missed it or what, but I didn't remember seeing a mention of having to put it in a folder named skins. Thank you so very much. PS. Love the work that you are doing. Great job. I've kinda been following along http://i.minus.com/iUmr4Qf5Hw3MB.png
6
« on: July 05, 2012, 01:27:49 am »
I made a skin for kArmTI. I set both the skin and the emulator to touchpad. The emulator doesn't show it under the skins section. Skin attached.
Hi ParkerR: You need to put the skin file: "Texas-Instrument-Ti-Nspire_CX_CAS" in the same directory! You've just missed it . Good first try, though. Btw: make a shorter 'skin-file-name'.
Ok I renamed the image file to nspire.png and the skin file to nspire.skn. It still doesn't show up in the program.Ok so I went back to Skin1.skn and Texas-Instrument-Ti-Nspire_CX_CAS.png. I set the skin name in the skin editor to Texas-Instrument-Ti-Nspire_CX_CAS and set the Texas-Instrument-Ti-Nspire_CX_CAS.png as all three button states. Still doesnt show up. Edit: Uploaded the files.
7
« on: July 03, 2012, 11:21:47 pm »
I made a skin for kArmTI. I set both the skin and the emulator to touchpad. The emulator doesn't show it under the skins section. Skin attached.
8
« on: June 04, 2012, 08:46:39 am »
A feature I would like to see is instead of having to use the arrow keys to move the mouse, maybe have it to where you can move the mouse over the screen and be able to interact with it 1:1.
9
« on: June 04, 2012, 08:38:41 am »
Ok very weird. Crashes when I put in those arguments through the GUI but if I launch it from the command line with SpiroH_v17.exe /1=boot1.img /F=flash.img it works.
Well, if you enter the arguments in the GUI boot-options dialog, then they are used only at the next start.
But if these arguments are already correctly stored in the registry (as it should be after you've started it with commandline parameters), then the next start of SpiroH should work fine (also without having to enter any parameters again).
PS: And BTW, you shouldn't use SpiroH v15 - that's just an intermediate version where not all keys work. Better use v17_2 (or v14 which has a different touchpad handling).
Yeah I just was trying the different versions to see if one would not crash. And now that I did it on the command line it seems to have stuck. I can just launch it now. Great work SpiroH
10
« on: June 04, 2012, 08:23:48 am »
Ok very weird. Crashes when I put in those arguments through the GUI but if I launch it from the command line with SpiroH_v17.exe /1=boot1.img /F=flash.img it works.
11
« on: June 04, 2012, 08:16:43 am »
I can't get v15 or v17 to load my image. I put in this for the command line "/1=boot1.img /F=flash.img" and when I click "Ok" it starts to load then crashes. Windows 7 64bit if that makes a difference. TI-Nspire OS 3.1 CX Loads fine in nspire_emu with the same parameters.
I don't think that 64bit would be the problem. Which nspire_emu version do you use (when you say your image loads fine)? SpiroH is based on nspire_emu 0.60.
I'm using 0.60
12
« on: June 04, 2012, 08:14:04 am »
so will this os be installed forcefully? (force update)
I haven't heard of them doing forceful installs in the past, so I wouldn't think so. It'll most likely just do a popup saying there is an update.
13
« on: June 04, 2012, 07:36:32 am »
I can't get v15 or v17 to load my image. I put in this for the command line "/1=boot1.img /F=flash.img" and when I click "Ok" it starts to load then crashes. Windows 7 64bit if that makes a difference. TI-Nspire OS 3.1 CX Loads fine in nspire_emu with the same parameters.
Edit: So many spelling errors.
|