Okay - just playing around with the SuperPro with the updated firmware
AND BT5.44 and then I loaded BT.5.55 from a today's download from the tech support page.
They both failed.
'
was checking out the memory map/locations for different variables --as there was a note on the S'Pro memory map
referring to "firmware before 8.15...". I am using 8.36a IIRC.
'
so I put in the "const w="a string" and no problems
I put in "const t$="also a string" and I get a message that "__temp.out is locked by another process...reboot may..."
'
That particular error message seems out of place for an improperly designed name for a CONST [the '$"].
I would expect something like this [although this is not correct either - no duplication in mentioned file].
::
Programming (prompt but no +*+* symbols ,just some blank lines and then the following lines)
const t$="also a string"
-ERROR C:/Users/Olzeke51/AppData/Local/Temp/Coridium/__user.bas: 8: Duplicate Name
const t$="also a string"
-First ERROR at line :8
::
(I went ahead and tried to <RUN> it anyway, and it ran what was previously loaded okay)
SO___ maybe next time you are in the BT you could look at the error path/message
when a '$' (dollar sign) is used in a CONST ; it seems okay when it is in a DIM.
'
BTW I do have the /TEMP/files that BT creates - error.tmp is empty!!
'
This is just a maybe fix -- I tend to stretch the limits!!!!!
Gary Olzeke51
I
questionable error message??
Re: questionable error message??
This is some Windows issue, and I see it from time to time and is mostly unrelated to anything inside the BASICtools.
I really have no fix for Microsoft bugs, and I usually have to restart the tools. On Win10 I have seen scarier issues, where Win10 seems to get confused on its own file system, and have actually lost files. A system restart is required at that point.
I really have no fix for Microsoft bugs, and I usually have to restart the tools. On Win10 I have seen scarier issues, where Win10 seems to get confused on its own file system, and have actually lost files. A system restart is required at that point.
Re: questionable error message??
upon further playing around - -
this appears to be caused by not using the <RESET> button after loading a program from a file.
'
if I manually enter the program and do RUN - no issue
usually if I load a file-program and do RUN I will get the '__temp.out file is locked'
doing the <RESET> hasn't caused the error
'
not 100% reproducable - about 80% though -- ?size of program/contents of program could be ???
FWIW - Olzeke51
this appears to be caused by not using the <RESET> button after loading a program from a file.
'
if I manually enter the program and do RUN - no issue
usually if I load a file-program and do RUN I will get the '__temp.out file is locked'
doing the <RESET> hasn't caused the error
'
not 100% reproducable - about 80% though -- ?size of program/contents of program could be ???
FWIW - Olzeke51