TheBackShed.com

Forum Index : Microcontroller and PC projects : VAR CLEAR

Page 7 of 7

Author

Message

Grogster

Admin Group

Joined: 31/12/2012
Location: New Zealand
Posts: 9610

Posted: 01:53am 23 Jan 2019

Copy link to clipboard

Print this post

I was testing on Windows 10.

The problem is rather obscure, and you have to do a specific set of steps to make the error show up, so that was perhaps giving the impression that Windoze 7 was responsible somehow. Members probably tried your problem code, but got no error, so thought no more about it. It only becomes evident when you reflash MMBASIC into the chip and VAR RESTORE is used for the first time. It's quite a crafty one.

Smoke makes things work. When the smoke gets out, it stops!

PeterB
Guru

Joined: 05/02/2015
Location: Australia
Posts: 655

Posted: 02:30am 23 Jan 2019

Copy link to clipboard

Print this post

Thanks for that.
Now we know!

On any version of windows, loading V5.05.01 will corrupt that part of the chip used by VAR.
Trying to do VAR RESTORE or VAR SAVE xxxx will result in an error.
The problem can be fixed by clearing the corrupted memory by entering NEW or VAR CLEAR. Using MMedit automatically inserts NEW.

Would you agree with this?

Peter

Edit
please inset

after Now we know!

PEdited by PeterB 2019-01-24

Turbo46

Guru

Joined: 24/12/2017
Location: Australia
Posts: 1642

Posted: 03:24am 23 Jan 2019

Copy link to clipboard

Print this post

I'm not sure about the VAR SAVE xxxx but don't forget the OPTION AUTORUN ON has to go first then VAR RESTORE. You can then remove the OPTION AUTORUN ON and still get the error.

Geoff knows!

Bill

Keep safe. Live long and prosper.

PeterB
Guru

Joined: 05/02/2015
Location: Australia
Posts: 655

Posted: 05:42am 23 Jan 2019

Copy link to clipboard

Print this post

I thought I had got it down to a nice simple elegant description and was not even close.It's probably just academic now but I would really like to have it clear in my own mind. It's been bothering me now for the best part of 3 weeks. BUMMER.

Peter

Geoffg

Guru

Joined: 06/06/2011
Location: Australia
Posts: 3292

Posted: 10:18am 24 Jan 2019

Copy link to clipboard

Print this post

Thanks guys, that is a subtle bug.

If you use OPTION AUTORUN ON it will cause an error in any subsequent VAR RESTORE or VAR SAVE commands. The workaround is to use the following (at the command prompt) to set autorun:

OPTION AUTORUN ON
VAR CLEAR

Then you are good to go. I will fix it in the next release.

Geoff

Geoff Graham - http://geoffg.net

Page 7 of 7

Print this page

To reply to this topic, you need to log in.