https://youtu.be/6r7AYA5m4Vg
So is everything in the video completely wrong or did I actually do it at one point without realizing? A bit confused here
[SOLVED] nOver 3.0 | Frozen calculator
12 posts
• Page 2 of 2 • 1, 2
-
Guest121952
Niveau 2: MI2 (Membre Initié)- Posts: 3
- Joined: 09 Nov 2018, 12:16
- Location: USA
- Gender:
- Calculator(s):→ MyCalcs profile
Re: [SOLVED] nOver 3.0 | Frozen calculator
I don't really understand what you're trying to do in the video.
The best stable overclock setup for your calculator seems to be 234/234/78.
You can set this directly and then type
Then if nover is in the /ndless/startup/ folder, you don't need to deal with it again, it'll automatically set the nover.cfg setup at each Ndless installation.
If 234 is not perfectly stable, then 228 probably is.
Note that the freeze with the busy pointer in the middle of the screen is a bug with the SRAM which can also happen without Ndless.
It can be fixed either by launching the Diags software as you do, either by disconnecting the rechargeable battery for some seconds.
It can come from a too high Nover setup (234 instead of 228 for example), but also from the Ndless programs you are using (emulators). No way to be sure. It's just more likely to happen after an Ndless program freezes/crashes.
The best stable overclock setup for your calculator seems to be 234/234/78.
You can set this directly and then type
varto store this setup in nover.cfg.
Then if nover is in the /ndless/startup/ folder, you don't need to deal with it again, it'll automatically set the nover.cfg setup at each Ndless installation.
If 234 is not perfectly stable, then 228 probably is.
Note that the freeze with the busy pointer in the middle of the screen is a bug with the SRAM which can also happen without Ndless.
It can be fixed either by launching the Diags software as you do, either by disconnecting the rechargeable battery for some seconds.
It can come from a too high Nover setup (234 instead of 228 for example), but also from the Ndless programs you are using (emulators). No way to be sure. It's just more likely to happen after an Ndless program freezes/crashes.
-
critorAdmin
Niveau 19: CU (Créateur Universel)- Posts: 42263
- Images: 16840
- Joined: 25 Oct 2008, 00:00
- Location: Montpellier
- Gender:
- Calculator(s):→ MyCalcs profile
- YouTube: critor3000
- Twitter: critor2000
- GitHub: critor
12 posts
• Page 2 of 2 • 1, 2
Return to Native: Ndless, Linux, ...
Who is online
Users browsing this forum: ClaudeBot [spider] and 8 guests