Had a problem with my MM2 G2 Version, which locks up when I enter the
command. Even after a reboot. Just wondering if anyone else has this same problem.

I haven't done anything to it besides adjust the resolution a handful of times, before finding what the monitor prefers (1024x768) Not sure where to go from here, besides maybe resetting it to default state using the pins on the back.

I was using version 5.07, and as I understand there is a newer version, so I suppose this would be a good time to update to it.

I also loaded a font using font tweak, which seemed to work.

The strange thing is that I didn't have this problem before, as I booted it the first time and read from the manual. Which is why I suspect the problem may have resulted from something that I had done.

Have you TRIED to update the firmware?

Remember that you have to REMOVE the button cell battery, if you do a FW update, as the battery not only backs up the RTC, but it also backs up some settings and all the options in the STM32 chip.

Updating the FW with the battery still in place, can cause lots of issues.
This is mentioned in the manual.

Otherwise, the bog-standard FW I ship in any CMM2 I sell, is the last STABLE, which has been v5.07.01, and it has never given me any issues.

What you do with the unit once you get your hands on it, is another story.      

You could try just reloading the FW I use, but remove the battery before you do that.  

Is it only the Memory command that locks it up? i.e. Can you load and run other programs fine?

Also is it only with the Defined Font loaded.
The memory command will read that to determine its size to include in the memory summary printout.

Thanks for the help, will try to update the firmware. I read in the release notes that there was an issue with the memory command,

  Quote  

Fixes bugs in VAR and MEMORY commands when the saved variable area is corrupted for any reason.

It is responsive to other commands, I don't have much for programs as of yet, but there are a few commands that give an error. mm.info(bcolour), and mm.info (fcolour). gives a syntax error.

I hope that the firmware update works and that windows can find the right driver this time, as last time some of my programs stropped working after I downloaded the driver manually. I then had to roll-back my system so I don't have that driver installed anymore.