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 - critor
Pages: 1 ... 52 53 [54] 55 56 ... 137
796
« on: March 31, 2012, 08:33:12 pm »
No, as you can see it isn't - and fortunately! 
798
« on: March 31, 2012, 06:28:26 pm »
Like on classic Nspire handhelds, CX Nspire handhelds feature a diagnostic software which can be triggered at boot time with    . On classic Nspire, that software was pretty useless for the end-user. But on CX Nspire it's not the same at all... For exemple, if you delete Ndless folder/files without uninstalling it, the calcultor will enter and endless reboot loop. You need to access the maintenance menu to remove the OS and reinstall it. But if your rechargeable battery is too low, the Nspire CX won't let you use that menu! And the battery cannot be charged if the OS doesn't start... Fortunately the diagnostics software will let you charge the battery: Source: http://tiplanet.org/forum/viewtopic.php?t=8713Another example, sometimes your Nspire CX OS just won't start and will freeze at the following screen: This means the SRAM chip contains bad data.It can happen after launching a buggy Ndless program, but I also got this problem on brand new Nspire CX before Ndless 3.1 release date. So it's an OS bug. Whatever you do won't solve the problem (reset, maintenance menu, delete os, reinstall os, upgrade/downgrade os...). The only known way to clean the SRAM was to unplug the rechargeable battery. Launching the diagnostics software will easily detect and fix the problem: Source: http://tiplanet.org/forum/viewtopic.php?t=8945So the CX diagnostics software is very usefull. But unlike the Boot2, it is not updated by the OS...  And it's too easy to remove it by mistake by pressing at boot time   . Without a properly updated diagnostics software or with no diagnostics software at all, your Nspire CX might remain stuck forever in the above situations Fortunately, I'm releasing FlashDiagsCX this evening, a Ndless 3.1 tool based on FlashBoot2CX source code!   You can now reprogram a deleted diagnostics software, and update it! Download from the TI-Planet news: http://tiplanet.org/forum/viewtopic.php?f=43&t=8976&p=122307#p122307
799
« on: March 31, 2012, 04:03:39 pm »
Your Nspire OS can upgrade your Boot2 with the one it does include, but never downgrade it. The only way to downgrade your Nspire CX Boot2 up to now was to use an external RS232 adapter.  But like we did for classic Nspire in a previous news, Bsl and me have just released Boot2FlasherCX! No need to deal with an RS232 interface anymore! By just pressing a single key you can freely upgrade/downgrade your TI-Nspire CX Boot2 with the 3 released versions up to now: 3.0.1, 3.0.2 and 3.1.0.  Of course you can flash development Boot2, Boot2 from another model, modified Boot2, 3rd-party Boot2... Possibilities are endless! Just be sure of what you are doing, because if your Boot1 does reject your Boot2, you'll end up needing the RS232 interface to repair your Nspire!... Download from the TI-Planet news: http://tiplanet.org/forum/viewtopic.php?t=8973
800
« on: March 30, 2012, 12:28:58 pm »
Since there has been recent news about flashing boot2's and changing prototype to retail, is there any way to downgrade the nspire from 3.1 to a 2.x?
Kevin Lopez
Not easily for now, as no Ndless 3.1 Boot2 flashing and downgrade programs have been released for classic Nspire up to now. The only way for now is my old trick with the external RS232 adapter...
801
« on: March 29, 2012, 07:44:52 am »
You can only complete the 1st episode of Doom by dying.
You mean Doom Ultimate, right? Because for me I got no problem in Doom 1's first level
Doom Shareware = Doom1 episode 1 I don't remember if the ending credits are different.
802
« on: March 29, 2012, 01:31:10 am »
You can only complete the 1st episode of Doom by dying.
And the screen is red when you take damage.
So a little bug just gives you red credit screens.
On the real Doom, there is nothing you can do at the credit screens - you have to use the menu to run a new game with the same or another episode.
It seems that the credit screens script isn't very well supported for now, like the menu and the automatic demo when you run the game (Mrakoplaz has left several comments about these in the code).
So without the menu support, all you have to do at the credit screen is to exit and relaunch nDoom.
803
« on: March 28, 2012, 12:19:31 pm »
I think it's too close to the board surface, but I haven't "really" tried.
Maybe someone who did try could tell us?
804
« on: March 27, 2012, 03:02:06 pm »
Is there a version for non-CX or do we have to use downgradefix ?
It has not been adapted for non-CX yet, meaning that you still have to stick with downgradeFix + Boot2 1.4 (to flash through RS232 - as no FlashBoot2 has been released for Ndless 3.1 either).
805
« on: March 27, 2012, 04:51:46 am »
Since OS 3.0.2.1791, minimal installable OS version was set to 3.0.2.1785. This number is written in NAND outside the filesystem, and is not cleaned by any official menu. It was impossible for your Nspire to go back to OS 3.0.1.1753 for example. But some of us wanted to keep the possibility to go back to that OS. Indeed, OS 3.0.1 had: - some flaws fixed on newer versions
- the possibility to open partialy encrypted Lua scripts
- a working Lua print() function which let you control external peripherals thanks to the RS232 port of the dock connector
Today thanks to Bsl and TI-Planet, you've got the choice with our new Ndless program: downgradeCX! Like Nleash and downgradeFix, downgradeCX just erases the NAND page containing the minimal installable OS version. But it's also better in the following ways: - Unlike Nleash, downgradeCX doesn't remove the OS. You can go on using the OS untill you decide to downgrade, or even change your mind and in the end not downgrade at all.
- Unlike downgradeFix, downgradeCX doesn't need the OS to be removed or a specific Boot2 version to be flashed - which required an external USB/TTL2 interface!
Note that the downgrade protection is only temporarily removed. If the calculator does reboot before you downgrade, you'll have to run downgradeCX again. Also, downgradeCX needs Ndless 3.1. It won't be able to save you if you upgrade to OS 3.2 which will block Ndless. But the downgrade source code now publicly exists, and you'll just need to inject it with a flaw, if such a flaw still exists in the next OS...Download from the TI-Planet news:http://tiplanet.org/forum/viewtopic.php?p=122163#p122163
806
« on: March 26, 2012, 07:35:25 pm »
Now, this might be a stupid question, but if you removed that one component in the production Nspires, could you then modify boot 1?
Edit:
Nevermind, looking at datamath, I see that the extra component is on the prototype, not the production model. Adding components wouldn't really be a viable option for many people.
Yes, sorry - the prototype is on the left in the picture. So in theory, on production TI-Nspire ClickPad, if you manage to connect the Flash NOR "magic" pin, you'll be able to reflash the Boot1 with anything you want. Meaning that you could then freely load modified or 3rd party Boot2, and then modified or 3rd party OSes.
807
« on: March 26, 2012, 06:45:42 pm »
Last year, many Nspire prototypes were sold online as if they were real Nspire. But those prototypes were using development RSA keys different than production RSA keys: you couldn't update them with any of the production Nspire OSes available on TI website. If you had bought such a prototype, you ended up stuck with an ancient development OS in version 1.1 or 1.2, and couldn't do much with it... It was unfair... On TI-Planet, we wanted to fix that. After months of constant research and development, we told you we achieved the impossible upgrade in a previous news, installing an OS 3.X on a prototype! How was it possible? It's normally impossible to install a production OS on those prototypes, because the Boot2 checks the OS signature with the development RSA keys, and rejects all OSes from TI website which are signed with production RSA keys. In a similar way, it's impossible to alter the Boot2, as its signature is checked by the Boot1 with the development RSA keys. But the Boot1 is not checked by anything. On TI-Nspire ClickPad, it's stored in a specific Flash NOR chip: SST 39WF400A. Thanks to a different connection of just one pin, that chip is write protected on production Nspire, but not on development Nspire! So using a special Ndless version for prototypes, you'll have to perform the following tasks in order: - reprogram the Boot1 with the production version 1.1.8916
- reprogram the Boot2 with a production version
- install a production OS
The method has been proven very reliable, tested with 100% success rate on all my 10 Nspire prototypes! Moreover, if your prototype OS is recent enough and does support the USB, you won't need any special external hardware! It's for everybody! Tonight at last comes the tutorial to upgrade your Nspire prototype! With many details, explanations and images! A step by step for everybody! Tonight it's the happy end of 1 year of work on Nspire prototypes: research and development of various tools which revealed much more usefull that what we thought at the beginning, and which are working great together in the end although we really didn't anticipate everything! Tonight, you can finally perform... the impossible upgrade! Many thanks to:
- Bsl who has developped allmost all the needed tools
- Levak, Adriweb and Lionel Debroux, who have tested on their own prototypesCross-posted from TI-Planet.Download the tutorial from the TI-Planet news, in french:http://tiplanet.org/forum/viewtopic.php?p=122160#p122160If someone wants to translate it to english, just contact me for an editable version of the file.
808
« on: March 24, 2012, 06:37:31 am »
Cross-posting from TI-Planet.When Nspire OS 3.1.0.392 was released in september, we discovered that the standard Lua print() function had been removed. This function made it possible to output data to the RS232 port of the Nspire, thereby enabling control of external peripherals, sound output, or whatever you see fit. It was already used in the wild when TI removed it...   This mis-feature of TI-Nspire OS 3.1.0.392 can now be fixed, thanks to fixprint. Fixprint hot-patches the OS in RAM to restore the funtionnality which was removed by TI, and can be launched automatically on boot by Ndless 3.1 This program is yet another compelling showcase of the endless possibilities offered by native code - including hotfixes to TI's OS (fixprint can be considered as such). Sadly, TI is dead set on shutting the door to native code on the Nspire platform... Download from the TI-Planet news: http://tiplanet.org/forum/viewtopic.php?t=8931
809
« on: March 19, 2012, 02:20:12 pm »
Be sure to use brand new batteries.
TI-Nspire Clickpads stubornly refuse to boot if they don't like your batteries.
810
« on: March 16, 2012, 02:30:39 am »
Cool! Ofc, this won't work on CXs.
It won't work on CX until the code is adapted (the dialog box function needs to be replaced, the boot2 size and offset need to be changed, and the write_nand sycall address needs to be found in both 3.1 CX OSes). But it won't help you downgrading a CX to 1.X/2.X as those versions are incompatible with the CX hardware. It'll just help you switching between CX 3.0.1/3.0.2/3.1.0 Boot2 versions easily.
Pages: 1 ... 52 53 [54] 55 56 ... 137
|
Show Posts
), we hope you enjoyed our annual prank! Huge thanks to the TI-Planet staff for making this possible. Seems 
