Hello Guest it is April 13, 2021, 12:39:13 PM

Author Topic: Problems moving to 4.2.0.4517  (Read 239 times)

0 Members and 1 Guest are viewing this topic.

Problems moving to 4.2.0.4517
« on: August 09, 2020, 01:39:16 PM »
We recently had to move from Windows 7 to Windows 10 for one of our machines.  I saved the mach4 directory from the Windows 7 computer, copied it to the reformatted computer, and then installed 4.2.0.4517 over the top of it (as recommended here: http://support.machsupport.com/en/kb/articles/updating-mach4)

Everything was fine except that whenever I tried to open the screen editor to edit a screen that had been part of the old installation (a custom screen) it would crash Mach4. Editing standard screens that were part of the 4.2.0.4517 installation was not a problem.
 
I did the same thing with 4.2.0.4470 and everything worked fine so we are currently running 4.2.0.4470 on that machine.

I am worried that I will have the same problem again if we ever need to upgrade Mach4 beyond 4.2.0.4470. Does anyone have any ideas what might be happening?

The old version was 4.2.0.4300.

Thanks!
David

Offline Stuart

*
  •  260 260
    • View Profile
Re: Problems moving to 4.2.0.4517
« Reply #1 on: August 10, 2020, 12:53:16 AM »
I do not know why but I had the same problem

Mach4 517 would crash corrupt the ini file etc

I found out it it was my old industrial modified screen that caused the problem as the screen supplied was ok and ran fine .

But the problem was when I imported the prof file it had the link to my old screen thus crash , I had to do a clean install to 517 but not run it but open the ini file and alter the screen set in there ,then I could boot ok and run the mill , then alter the new screen to my needs

Note I was never able to find out what was in the old screen that caused it , the only clue I found was that a lot of addresses for vars had been changed
Re: Problems moving to 4.2.0.4517
« Reply #2 on: August 27, 2020, 08:57:27 AM »
I have had the same issue. Reported it to support. No resolution yet... I'm going back one rev. to see if it works ok.