.AUTO File Tips and Tricks

[Every11s2RuleDWorld]

how bout 1-calc by omegaone
http://www.omegaone.com/calc/ppc/default.htm

thank you.

This one works for me, it may work for you too ... try it

Note: Under Settings->Advanced Settings->11) Alternate Storage Location, I configured ASL as Storage Card.

[AutoFile]
InstallLocation=2
WindowTitle="License Agreement"

[ScriptCommands]
01 = Sleep(250)
02 = SendTab
03 = Sleep(250)
04 = SendTab
05 = Sleep(250)
06 = SendCR
07 = Sleep(250)
08 = SendOK

[scoob2009]

Hi,

I'm not sure if it's possible to automate the installation of Pocket Informant. It first of all presents you with a EULA and you must tap accept in the bottom left before it then asks you where to install it (again tap left soft key). I presume this constitutes multiple windows and therefore won't work unless someone can suggest a way around it.

BTW one of the problems I often have is finding out the name of the window to put into the .auto file. How does everyone else determine the actual window name as it isn't usually displayed on the screen.

Cheers,
David

Are you using PI9? For me, it just askes for the license agreement which I input as

[Autofile]
InstallLocation=0
WindowTitle="Pocket Informant Setup"

[ScriptCommands]
1=SendLeftSoft
2=
3=
4=



Hope that helps.

Now, anyone have an auto file for the latest SPB Wallter : http://www.spbsoftwarehouse.com/products/wallet/

It asks for a language selection but since English is the first choice, I just need the window name to send a left soft key tap.
Thanks

edit- here is the screenshot.

[dpeart]

HI all,

I'm trying to create a .auto file for a cab file that asks me if I want to soft reset after it completes. When running by hand I hit "no" and continue, but when I run it with an auto file Sashimi gets stuck at the installation location screen. Without the auto file it runs fine, but I have to hit the confirmation.

Here is my auto file.

[AutoFile]
InstallLocation=0
WindowTitle="Reset"

[KeyStrokes]
01=Sleep(250)
02=MouseClick("Reset",293,312)
03=Sleep(250)


Any ideas?

thanks,
dave

[SteveJames]

OK, after spending hours investigating why certain cab installs won't respond to any type of .auto influence I have come to thefollowing conclusions:

1) There seems to be a problem with Mortscript's Show( WindowTitle ) and certain applications. Specifically for me these are SPB Wireless Monitor and SPB Radio. The Show( WindowTitle ) just will not activate the window. DotFredsTaskMgr will highlight the window so it could be a Mort issue but Isuspect it's a combination of badly coded apps.

2) It appears that some applications halt the SASHIMI script once they install. One example of this is AEButton Plus. Once you save and exit from the settings screen the script starts running again. However, by this time the settings window you're trying to control has disappeared. I don't know wether Mort has a command for starting a detatched script in the background which would WaitFor a particular window to become active?

Anyway, the long and short of it is that probably the only way round these issues at the moment for a full auto install is to use WinCECab Manager to remove the Setup.dll from the cab. Take a snapshot after a hard reset with SKTracker and install the version of the cab with Setup.dll included. Take another snapshot and generate a comparison file and save it as a .txt file. Hard reset again and repeat the process with the version of the cab with Setup.dll removed. Then use Excel to do a side by side comparison of the two files after each has been sorted. With this information, it's possible to generate a Tandem .reg file to create / modify the relevant registry entries and also a .mscr to handle file deletion / renaming etc.

Anyway, I hope this information helps and prevents others from spending hours trying to automate cab installs that are not currently automatable.

A quick Mort script to determine if your app falls into the first category is:

Sleep( 10000 )
WindowTitle = ActiveWindow()
Message ( "." & WindowTitle & "." )

Effectively, after running the script from File Explorer you have 10 seconds to switch to the screen from the cab install. This will output a message with the window title (ignore the leading and trailing periods - these are just to make sure there's no leading or trailing white space in the window title.

Then run another small script:

Sleep( 10000)
Show( WindowTitle )

where WindowTitle is the title of the window (in quotes) displayed in the message box from the first script.

If the window won't come to the foreground then don't bother wasting time with an auto file!

[SteveJames]

Some more observations after spending a few more hours with .auto files and poring over the SASHIMI.mscr code:

Even though SPB Radio appears not to respond well to the Show command I think it probably is the same as AEButton Plus in the fact that the SASHIMI script hangs until the screen exits.

With SPB Wireless Monitor, I think the problem is that the SPB pop up window is sluggish to start. Therefore, the installer window closes before Wireless Monitor opens. Unfortunately the SASHIMI script does not handle this. Fortunately, it's just a simple matter on locating the SASHIMI.mscr script in SASHIMI\Program\Bin and adding a Sleep(2000) in Sub AutoInteract i.e.

EndIf
Sleep(2000)
ElseIf(WndExists(windowTitle))

This will give it two seconds to activate. If performance matters, you could use a WaitFor(windowTitle) command but you'll need to add a flag to stop it waiting for the window again after CallScript(tmpAutoMSCR).

Anyway, this simple change may resolve some issues with cab control if the problem with them is slow window activation.

Now, multi window handling!!!

I sucessfully use the following .auto file to control installation of Developer One's CodeWallet Pro 6:

[AutoFile]
InstallLocation=1
WindowTitle="Developer One Software"

[ScriptCommands]
01 = Sleep(250)
02 = SendOK
03 = WaitFor("Dialog",10)
04 = Show("Dialog")
05 = SendCR
06 = Sleep(250)
07 = SendUp
08 = Sleep(250)
09 = SendCR
10 = Sleep(250)
11 = SendOK

So, the first dialog box that pops up is 'Developer One Software' which needs a simple 'OK' to install. The next dialog is called 'Dialog' which the script WaitFor for 10 seconds. I've shown the window just in case. Anyway, it seems to work fine. Unfortunately (or fortunately) it's the only cab I've got with a multi window input but the above script may be of use to those trying to automate problem installs.