Machsupport Forum

Mach Discussion => Mach Screens => CVI MachStdMill (MSM) => Topic started by: amisk on July 30, 2010, 09:28:42 AM

Title: error on line:393 Internal error
Post by: amisk on July 30, 2010, 09:28:42 AM
I got this message : error on line:393 Internal error

What I did, I press the reference label , I choose User manual or anythings other (nothing happens)

and when I return on other label I got this message.

Do you have any suggestion ?
Title: Re: error on line:393 Internal error
Post by: DaveCVI on July 30, 2010, 12:02:27 PM
Sorry, you seem to have found a bug.
I think that the PDF reader path is set to an .exe  file that does not really exist.

Please do this:
1) On the settings-common page, use the "Set Utility Paths" button - this will bring up two dialog boxes in sequence. The first is for the non-Gcode editor path - you can ok, or cancel this dialog since we don't need to change that path.
The second dialog will be for the PDF reader path. Make sure the PDF reader path is correct.
I suggest browsing to the pdf reader exe file rather than typing in the path manually as that will prevent a typo from causing the problem you are seeing.
2) after the PDF reader file path is corrected, click OK to save the path info.
3) then try to open a manual again - if this was the problem, manuals should now open when their buttons are clicked.

If this does fix the problem for you, please let me know that this was the situation.

I will add a path/filename error check to the next release to fix this bug.

Dave

I got this message : error on line:393 Internal error

What I did, I press the reference label , I choose User manual or anythings other (nothing happens)

and when I return on other label I got this message.

Do you have any suggestion ?

Title: Re: error on line:393 Internal error
Post by: amisk on July 30, 2010, 12:54:36 PM
I make the change and all is correct

Thank you very much
Title: Re: error on line:393 Internal error
Post by: DaveCVI on July 30, 2010, 02:13:23 PM
Thanks for letting me know.
I'll have this fixed in the next release.
Dave