HP Forums
HP Prime Restarts When Creating New File in Python APP - Printable Version

+- HP Forums (https://www.hpmuseum.org/forum)
+-- Forum: HP Calculators (and very old HP Computers) (/forum-3.html)
+--- Forum: HP Prime (/forum-5.html)
+--- Thread: HP Prime Restarts When Creating New File in Python APP (/thread-19005.html)



HP Prime Restarts When Creating New File in Python APP - Ioncubekh - 10-22-2022 09:22 PM

@HP Firmware 2.1.14603 (2021 12 02) CCAS Version:1.5.0 OS Version 0.050.640 2021

When ever I create a file from with 'Symbolic View' of Python APP my Prime restarts. I have tried creating new .py as well as binaryData file

Steps to reproduce

Quote:Launch Python APP
Press Symb (open a main.py editor)
Soft Key select 'More > Files > New Program'
Option dialog appears
Select Program Type : Python Program
Enter Name
Press OK (...Restarts...)

At next restart when you launch Python APP MSGBOX appears stating
Quote:Python Files have changed do you want to reimport and run the updated files
Then it tried to import the file I create earlier (say vzy.py). Then MSGBOX states
Quote:An error was found. Do you want to edit the file? SyntaxError: invalid syntax in file vzy.py Line 1
After pressing OK. The main.py file editor launches but main.py is absent! Rather vzy.py opens?? In More>Files There is no main.py but vzy.py??


RE: HP Prime Restarts When Creating New File in Python APP - Guenter Schink - 10-22-2022 10:08 PM

That's weird. Try to reset the PRIME with <on> <Symb> perhaps this helps.
If not than you probably have to do a hard reset with formatting the <disk>

Günter


RE: HP Prime Restarts When Creating New File in Python APP - Ioncubekh - 10-22-2022 10:38 PM

(10-22-2022 10:08 PM)Guenter Schink Wrote:  That's weird. Try to reset the PRIME with <on> <Symb> perhaps this helps.
If not than you probably have to do a hard reset with formatting the <disk>

Günter

@ http://www.hp-prime.de/files/composite_file/file/214-hp_prime_recovery_mode.pdf

Tried FCO method full format C:\...

Even after that problem persists; can I reinstall the firmware somehow