Omnimaga

Calculator Community => TI Calculators => General Calculator Help => Topic started by: helder7 on August 02, 2012, 07:21:40 pm

Title: TI Nspire reboot when i try to delete a specific file
Post by: helder7 on August 02, 2012, 07:21:40 pm

Hello, i have a problem with my nspire and i need help to fix it

when i try to delete a specific file, the calculator reboot and dont delete it

there are any way to fix it?

Title: Re: TI Nspire reboot when i try to delete a specific file
Post by: Scipi on August 02, 2012, 07:29:45 pm

What is the file you are trying to delete? You could probably remove it with the Student Software.

Title: Re: TI Nspire reboot when i try to delete a specific file
Post by: helder7 on August 02, 2012, 07:39:22 pm

Its a game rom, i also tried delete it with pc file transfer program, but calc reset.

There is no way to do Memory reset?

Title: Re: TI Nspire reboot when i try to delete a specific file
Post by: ExtendeD on August 03, 2012, 03:15:40 am

What is the name of the file?

Title: Re: TI Nspire reboot when i try to delete a specific file
Post by: Lionel Debroux on August 03, 2012, 03:16:45 am

Did you overclock the AHB frequency ?

Title: Re: TI Nspire reboot when i try to delete a specific file
Post by: helder7 on August 03, 2012, 07:25:38 am

I did overclock some hours ago, but now i have the default speed.

The file is named mario.gba.tns and is saved in folder gpsp... Aparently i can remane this file, but i cant delete it...

There are any way to delete all nspire Documents?

EDITED: problem fixed

here is how to fix is anywone will have this problem in future

1- Uninstall ndless and copy your actual files to computer (if you want restore it later)

2-Acess Ti-Nspire Maintenance Menu (Doc+EE+Enter), select Complete Format (for me the option delete Document folder content doesnt solve this problem)...

3-Wait and after install the os again

:D

Title: Re: TI Nspire reboot when i try to delete a specific file
Post by: Lionel Debroux on August 03, 2012, 10:25:05 am

Well, I think that the cure is simple: do not overclock the AHB frequency, at all.