Be careful with CONTINUE=0 on an executable as no other auto launched applications will be run until Wavelink gets CLOSED! In your example, if some other application(s) were set to auto-launch at say PROGRAM14 thru PROGRAM20 that/those application(s) will not launch until you close Wavelink.

Hello Erick, What is the behavior of the device without simscript? Do both packages operate the same way? Mike

Mike, I made an OSUpdate to reset all the parameters on the MC9090 to made the tests. The script was not enabled at that moment to show the difference between the two enable30 version. Test has been done with the same ABup30_ddd, just deleting the enable30 to start the test with a different enable30 for each test.

Hi Erick,

If you are using Symscript only to auto start Telnet, then try the REG setting copied below.   It is the preferred method to auto launch.   Simply copy & paste the registry key that I have provided below into a text editor (like Windows Notepad) and then save it with a “.REG” extension( for example:  autostartTelnet.reg) .  

Copy the registry file into the “\APPLICATION” folder of your unit. You can tweak the “Continue” and “ColdBootOnly” settings accordingly.  

[HKEY_CURRENT_USER\Software\Symbol\Startup\Programs\Prog13]
"Name"= "\Application\Wavelink\TelnetCE\TelnetCE.exe"
"Command"="Command Line Parameter"         (Fully qualified file paths)
"Delay"=dword:00060
"Continue"=dword:0     (0: Do not continue until program complete; 1: Do not wait for program to complete)
"ColdBootOnly"=dword:0 (0: Execute program on every boot; 1: Execute program on cold boot only)

Hello Erick, I think you have another problem.The blob from the enable30 Apf was untouched from MSP 3.2.1. The name of the APF package was changed between the two versions but the contents remain the same. What happens if you make your own Agent30 setting with 3.2.1 and then use it on your 3.3 system? Mike

Mike, I do not have anymore 3.2.1 to make the test you are requesting but the diffrences I can see between those 2 versions are :

enable30_2_0_131 (from the MSP3.3) :

is not doing a warm boot after installation.
After Warm Boot, take about 20 seconds to be available
After Cold Boot, take about 1min40 sec to be available

enable30_1_1_10 (from MSP3.2.1)  :

is doing a warm boot after installation
After Warm Boot, take about 20 seconds to be available
After Cold Boot, take about 40 seconds to be available

This is prpbably the cause of my problem after Cold Boot creating a conflict with a script trying to start a program in the same time the Agent is not already started. But for sure there some differences between those two packages. I made the test on the same MC9090 running Abup30_ddd