Page 2 of 2

Re: '...' invalid name Error.

Posted: Mon Oct 21, 2019 2:30 pm
by marcogpalladino
Hi,

When running

Code: Select all

program runmlwin_getversion, plugin
I get the following error message:
Could not load plugin: c:\ado\plus\r\runmlwin_getversion.plugin

Yes, even when running examples I get the
The model did not run properly in MLwiN. You most likely clicked the 'Abort Macro' button in MLwiN, rather than the 'Resume Macro' button.


No, the program does not start correctly when I use shell. Indeed, a blue window very quickly pops up and then disappears. Same thing that happens after I run the runmlwin command.

Re: '...' invalid name Error.

Posted: Mon Oct 21, 2019 2:35 pm
by ChrisCharlton
Can you confirm that running MLwiN directly from Windows (i.e. running C:\Program Files (x86)\MLwiN trial\i386\mlwin.exe) works for you?

Re: '...' invalid name Error.

Posted: Mon Oct 21, 2019 2:41 pm
by marcogpalladino
Yes, that works

Re: '...' invalid name Error.

Posted: Mon Oct 21, 2019 2:49 pm
by ChrisCharlton
The shell command ought to be doing the same as running the file directly, so that's odd. Could you try running:

Code: Select all

shell cmd /k "C:\Program Files (x86)\MLwiN trial\i386\mlwin.exe"
as this should leave the blue window afterwards in case there are any useful messages there.

Re: '...' invalid name Error.

Posted: Mon Oct 21, 2019 3:01 pm
by marcogpalladino
I apparently have a problem with command prompt which I was not aware of. Basically, it does not start, even if I try with administrator rights. I guess I will to solve first this and then be back on the mlwin issue, as the two things are likely to be correlated. I will let you know.

Re: '...' invalid name Error.

Posted: Tue Oct 22, 2019 9:40 am
by marcogpalladino
Indeed, it was a problem related to command prompt. Now everything is working fine... sorry for that, and many thanks for your help.

Re: '...' invalid name Error.

Posted: Tue Oct 22, 2019 1:11 pm
by ChrisCharlton
Would you be able to provide any details as to what the problem with the command prompted was, for the benefit of anyone else who might have the same problem in future?