Moreover, nClock uses Ndless startup and hook features to save your clock setting. Meaning that your clock setting does survive a reboot!How does this work? I take it this is not using the RTC, since boot1/boot2 always reset it as far as I know and Ndless cannot prevent that. 900Cxxxx timers + spare SRAM?
Moreover, nClock uses Ndless startup and hook features to save your clock setting. Meaning that your clock setting does survive a reboot!How does this work? I take it this is not using the RTC, since boot1/boot2 always reset it as far as I know and Ndless cannot prevent that. 900Cxxxx timers + spare SRAM?
Nice!
Does it work with classic Nspires?
Two things :
- the RTC value is not reseted when the calc crashed (and still continue working even on the booting time). It resets only when you use the reset button.
- nClock just stores the last saved RTC value and ask if the time is correct on boot. But most of the time, since the RTC is not reseted, it is useless
How frequently is it written to NAND? Writing it to frequently would wear it excessively.
There are so many awesome things for the ti nspire cx (cas). It is a must have. Would somebody take my "old" ti nspire cas with touchpad charge into a cx?I've just said it works also for classic Nspires, what have I said wrong ?
But when is it backed up?How frequently is it written to NAND? Writing it to frequently would wear it excessively.
When you launch nclock =)
It reads the config file where all the stuff needed is stored, as well as the backuped clock.
The clock deficiency on the Nspire has been fixed.And as fairly often, deficiencies of the Nspire platform were fixed by third parties, through the power of native code :)
But coloured games or utilities like nclock are look awful on the classic nspire, aren't they?There are so many awesome things for the ti nspire cx (cas). It is a must have. Would somebody take my "old" ti nspire cas with touchpad charge into a cx?I've just said it works also for classic Nspires, what have I said wrong ?
But when is it backed up?How frequently is it written to NAND? Writing it to frequently would wear it excessively.
When you launch nclock =)
It reads the config file where all the stuff needed is stored, as well as the backuped clock.
When you launch nclock =)
There are so many awesome things for the ti nspire cx (cas). It is a must have. Would somebody take my "old" ti nspire cas with touchpad charge into a cx?I'll take it off your hands for you! :P
This is great! This way I can check the time during an exam! YAY! :DAs I think I explained in another thread, gbc4nspire would have to be completely rewritten to support the cartridge RTC, due to how the gameboy accesses the clock registers.
Next: making gbc4nspire to use the RTC (used by games such as pokemon, I think)...
If that happens, it'll be really nice! :D (Harvest Moon 1)This is great! This way I can check the time during an exam! YAY! :DAs I think I explained in another thread, gbc4nspire would have to be completely rewritten to support the cartridge RTC, due to how the gameboy accesses the clock registers.
Next: making gbc4nspire to use the RTC (used by games such as pokemon, I think)...
so I just delete ndless file and put the new one to update ndless?Yep, send ndless-ressources.tns and install ndless-installer it will reboot the Nspire, then send nclock.tns =)
ok. It was easier than I though. :D
Levak, what should happen when I run it? It shouldn't freeze should it :P
Doesn't seem to work for me. Hook installs, but calc freezes when the program is launched a second time.Update Ndless, and if it still bugs, what is your hardware model ? I mean CAS, non CAS + Clickpad/TouchPad/CX
yup, I tried esc-menu-minus, but after poking around, it looks like I should be using doc-enter-ee. Is this the case?
I am getting the same freeze thing, it loads the title bar fine however clicking on the file freezes the calc. Tried ndless build 617 and 620 and both freeze, however just before it freezes (or at the same time) the screens brightness goes down slightly. TI-nspire CX CAS. Never the less, very cool program.
np, but the sooner its fixed, the sooner I can continue work on the minecraft clone. Its stuck w/o trees...But can't you use already your calc ?
Oh, I am. I'm just hoping I won't have to worry of losing all my changes...On the endless startup loop (not the endless contrast loop I'm trying to fix), just use the Diags menu, you won't have to reformat the OS.
so just go to it, and quit?Just go to the Diags menu and it will say something like "error", press Esc, it will fill a progress bar and solve the problem. Then, Reset the calc.
(https://lh4.googleusercontent.com/-GNj31AZqV5Q/T4tF3pgOuNI/AAAAAAAAAPs/cZ709a5s6tI/h120/011.JPG)
(https://lh4.googleusercontent.com/-GNj31AZqV5Q/T4tF3pgOuNI/AAAAAAAAAPs/cZ709a5s6tI/h120/011.JPG)
Oh, this happens sometimes.
It is a part of my optimizations, I don't redraw/compute the entire screen/date.
Ok it works good now, did have to reboot twice, 1st because it looked like thisI found an easy way to fix this (as it happens to me alot) just press Esc until it goes away.
(https://lh4.googleusercontent.com/-GNj31AZqV5Q/T4tF3pgOuNI/AAAAAAAAAPs/cZ709a5s6tI/h120/011.JPG)
and 2nd because every time I would make a change (like mini clock location) it would say "times over" :P
but it now works very good, great work! ;D(http://www.omnimaga.org/Themes/default/images/gpbp_arrow_up.gif)
BTW, can ExtendeD make the key sequence a little more clear in the tutorial? I think it would help others than just me.
Lol nice pics. XD
Also does the Nspire have some sort of crystal timers or something, or is that clock program just made to be as accurate as possible? And if the Nspire crashes or reboot, will the time be preserved?
EDIT: Latest version crashes for me too. OS 3.1 on TI-Nspire CX. ???
Oh, then I guess I'll have to update to latest version. And I mean the calc reboots.Lol nice pics. XD
Also does the Nspire have some sort of crystal timers or something, or is that clock program just made to be as accurate as possible? And if the Nspire crashes or reboot, will the time be preserved?
EDIT: Latest version crashes for me too. OS 3.1 on TI-Nspire CX. ???
Crashed or Freezed ?
Crashes only appear if you're not running at least Ndless r611
Edit : Sorry, maybe you're refferring to the idle crash ?
So, is anyone going to port this?Maybe you? :P
Oh, then I guess I'll have to update to latest version. And I mean the calc reboots.Lol nice pics. XD
Also does the Nspire have some sort of crystal timers or something, or is that clock program just made to be as accurate as possible? And if the Nspire crashes or reboot, will the time be preserved?
EDIT: Latest version crashes for me too. OS 3.1 on TI-Nspire CX. ???
Crashed or Freezed ?
Crashes only appear if you're not running at least Ndless r611
Edit : Sorry, maybe you're refferring to the idle crash ?So, is anyone going to port this?Maybe you? :P
Oh, so the guy who made this isn't planning on porting it himself?
He doesn't own a PRIZM at all. Porting it without owning the actual calc would be hard. And I doubt anyone from TI-Planet that is under TI's NDA plans to work on Casio projects in long terms.
And I doubt anyone from TI-Planet that is under TI's NDA plans to work on Casio projects in long terms.
idk if anyone mentioned this before, but the clock displays 12:00 AM when it's supposed to be 12:00 PM.
Basically, I was running a timer. Before the timer ended, the screen went to sleep, and when it woke up, the calculator rebooted when I clicked OK on the five minute warning popup. It never fully booted. It probably is more like 65%, but it is definitely past halfway where I've seen all other hanging points.Ok, I get it now. This bug is explained at the end of the readme. But I thought you already had it ? This bug is exactly the one I had during developement and couldn't manage to reproduce. Try to launch the diags menu (not the maintenance menu). Then Press Esc, wait a bit unitl it shows the menu, then reset. It should work now=)
Edit : Wait I'm trying right now... I think I get it... just put the contrast to the minimum on CX while I'm getting rid of this evil endless loop.Agh. Four days and the thread is already 4 pages longer. I just want to confirm that this works.
I think he said he released a new version that fixes the bug.Yep, it was a non-handled contrast related case of epic-fading transitions :D
no message, and the solution posted didn't work for meI think I'm lost. Do you mean a 65% progress bar or 65% of the total time, that is, probably the dotted screen with the clittle waitting-clock ?
11:59 PMso dj what does this mean O.o
Next day:
12:00 AM
12:01 AM
1:00 AM
1:01 AM
[...]
11:59 AM
12:00 PM
12:01 PM
1:00 PM
[...]
I cant edit the time, when i try to edit it the calculator crashes.
Thanks for the time...just me or pun? :D
I cant edit the time, when i try to edit it the calculator crashes.
Hi,
Did you update your Ndless to a revision greater than the one indicated in the README ?
BTW, here is a message for everybody : nClock has some problems with daytime conversions, I'm aware of it but sadly have no time to solve it.
Basically there are three conversions, one is accurate (timestamp to day) but the two others are not (guessing weekday and day to timestamp) due to a float approximation : this is why you may enter two more days when configuring the time and may have a wrong weekday. Sorry about that..
"Is Tues -1, Jan 1970 correct?" (Whereas the actual time was set to 1 Jan, 1970).I love you.
static short year_codes[] = {5, 4, 2, 0};
static short month_codes[] = {0, 3, 3, 6, 1, 4, 6, 2, 5, 0, 3, 5};
static char months[][4] = {"Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec"};
static char weekdays[][4] = {"Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat"};
char * getWeekDay(int year, int month, int day) {
int d = (year>>2)/25;
int r = year - (d<<2)*25;
return weekdays[(year_codes[d&3] + r + (r>>2) + ((r&3)==0) + month_codes[month-1] + day) % 7];
}
Yep, you fixed it. Now the issue is that it says that today (21 May 2013) is a Monday (It's Tuesday).Fu**, I actually thought today was Monday >_>
I found out what might be causing all of these:Not "all of these" but only the bug you seem to have.
It crashes on start up on TI-nspire CX II CAS, the ndless dev says nClock needs to be updated.This thread is over 4 years old at this point. I'd suggest reaching out to the nClock author (@tangrs) instead of posting on a news article that they likely aren't looking at.