Using Macro Sheduler 7.2.040 24/09/2003 on W2k Sp4 or XP pro Sp1
After reboot of PC the first time executing the macro over desktop-link it shows a Macro Sheduler Warning "Error Attempting to Read C:\". Next time the macro is executed it crashes with "Application Error". Newly executed after this, it runs without problems until Reboot of the PC.
Similar Problem: After a new Link on Desktop to the *.exe is arranged, the first time executing the Link a Macro Sheduler Warning "Error Attempting to Read C:\Dokume~1\Admini~1\Lokale~1\Temp" is shown. Next time the macro is executed it crashes with "Application Error". Newly executed after this, it runs without problems until Reboot of the PC.
Are there any suggestions to solve this problem?
Along the way: Are there any limitations on number of code-lines per macro?
thx
migro
Compiled Macro crashes
Moderators: JRL, Dorian (MJT support)
- Bob Hansen
- Automation Wizard
- Posts: 2475
- Joined: Tue Sep 24, 2002 3:47 am
- Location: Salem, New Hampshire, US
- Contact:
I don't recall the details, but there are some quirks with Windows creating shortnames, that are not always the same. Excellent details can be found in the documentation for xxcopy.
But I was just wondering what happens if you use long names for the folders vs. using the short names.
You can see the full names by using DIR in a command window.
And thinking a bit more about the message you describe, I suspect this will probably not correct your problem. I would expect a message like "File not found" or something similar. In any case, it is worthwhile to read the paper from xxcopy explaining the problem. I will try to return to this message with a link........please wait......
OK, back again. I decided to add this as a separate Subject under General Discussions. The Subject is: Problems in filename aliases (8.3 names) in Win32 - Paper.
Click here: http://www.mjtnet.com/usergroup/viewtopic.php?t=657
But I was just wondering what happens if you use long names for the folders vs. using the short names.
You can see the full names by using DIR in a command window.
And thinking a bit more about the message you describe, I suspect this will probably not correct your problem. I would expect a message like "File not found" or something similar. In any case, it is worthwhile to read the paper from xxcopy explaining the problem. I will try to return to this message with a link........please wait......
OK, back again. I decided to add this as a separate Subject under General Discussions. The Subject is: Problems in filename aliases (8.3 names) in Win32 - Paper.
Click here: http://www.mjtnet.com/usergroup/viewtopic.php?t=657
Hope this was helpful..................good luck,
Bob
A humble man and PROUD of it!
Bob
A humble man and PROUD of it!
Hi,
Please update to version 7.2.043. This problem was fixed in 7.2.043. You will see from the history at http://www.mjtnet.com/index.mv?mswhatsnew.html and in the announcements forum that problems like this with running compiled EXEs were fixed in 043.
You can update at http://www.mjtnet.com/dldregd.htm
Please update to version 7.2.043. This problem was fixed in 7.2.043. You will see from the history at http://www.mjtnet.com/index.mv?mswhatsnew.html and in the announcements forum that problems like this with running compiled EXEs were fixed in 043.
You can update at http://www.mjtnet.com/dldregd.htm
MJT Net Support
[email protected]
[email protected]
This issue is not Fixed in .043 it still occurs. First Try... Cannot Read C: Second Try... Nothing... Third Attempt works...
It takes launching the macro three times before success... and that is still only half way home because on the tenth run it will throw a random cannot read C:\Docume~1\ error up....
It takes launching the macro three times before success... and that is still only half way home because on the tenth run it will throw a random cannot read C:\Docume~1\ error up....