[Touch Pro, Fuze ROM Development] powinmo:
Changelog for updates by powinmo:

110117

Version 1.62

1. Eliminated extra ProcExists checks around tskKills due to prior sub refactoring in 1.61

2. fixed "sub tandem" so that tandem installs like .cab+.reg work now

* the calls to FileInstallMethods never passed the proper fType and sType values to allow the tandem item to run

** eg, xyz.cab and xyz.reg never installs the xyz.reg file because it continued to pass the "CABfiles" fType/sType vs "REGfiles"

* tested and verified at least a few .cab+.reg tandem installs

3. fixed "Sub cabInteract" for failing on Manual CAB installations

* the free space check during a Manual CABfiles install would fail because the SpaceFree check did not have a valid InstallDestination to use

** as a result CAB files in the filesCAB\Manual would sometimes fail due to insufficient free space on the target (would read 0 bytes free on bogus target)

4. modified "Sub autoPhase" to add in second install pass on:

a. registry

* \Storage Card\XDA_UC\_Mod_\files2REG (localized as needed)

Runs after filesCHT is processed

* Allows for a final set of .reg imports prior to exiting S4X

b. mscr

* Location \Storage Card\XDA_UC\_Mod_\files2MSCR (localized as needed)

* Runs after filesCHT and files2REG is processed

* Allows for a final set of mscr scripts to run prior to exiting S4X

eg, allows for something like after a CHT Import, you can import a direct registry tweak to override some CHT settings from a file in files2REGfrom a .reg file in files2REG

5. Expose free space check multipler to target location during CAB file installations

* Sashimi (and S4X inherited) defaulted to a value of 4

** if your target destination does not have 4 x the size of your CAB file free, the CAB will not install

* exposed in autosettings.ini:

! section: [AutoSettings]

! key name: "freeSpaceMultipler"

! value: 1 to 99

* default to 3 x CABsize if not defined in autosettings.ini

5. Expose WaitFor text window during SDAuto CAB installations

* Sashimi (and S4X inherited) defaulted to a value of 10 to 20

** if your target CAB did not load wceload within the timeout period it may cause the script to hang or skip

* exposed in autosettings.ini:

! section: [AutoSettings]

! key name: "txtWindowWaitFor"

! value: 1 to 99

* default to 25 seconds to wait for the wceload text window to become active

* may need longer depending on how slow your device is and how large the CAB installations are

9. tweaked pretty tabbing/spacing for a few lines here and there

Other:

a. CHTE2.0.0.0 importing still has issues with loading all settings. Known issue based on what I've seen in the CHTE2.0.0.0 threads.

b. CHTE1.8.5.1 importing works fine.

c. Running subsquent S4X sessions may "lockup" when trying to install SDAuto CABs. Basically any Text Window operation (WaitFor or WndExists) may crash after the first execution of S4X. This leads to the script just hanging there and will require you to manually kill the mortscript process. This looks like an issue with Mortscript b11 that S4X has packaged in, and not any fault of a custom ROM or S4X itself.

101227:

0. bumped version to 1.61 temporary so my updates can be differentiated from original author until they merge changes

1. fixed/modified pimRestore sub

* corrected: "sourcPIM" to "sourcePIM"

* corrected: sType for PIMRestore registry write was missing - subsequent S4X executions would apply or miss PIB/PIM restores

* added ability to execute an auto type script for PIB automation

- auto-type scripts must be in the filesPIM directory

- if "pimbackup.restore.mscr" was found, this script is run each time a PIB file is restored

- if <filename>.mscr is found for a specific <filename>.PIB file, this script is run only for that PIB and overrides running the "pimbackup.restore.mscr" file

2. refactored sub taskKill

* exitSub(0) in MortScript 4.3.0.11 is broken and the taskKill sub terminates prematurely

* eliminated the need to use exitSub

* this caused items like dialerCAB to fail when it could not kill cprog.exe (for CDMA ROMs) properly

! If you have seen very odd behavior with items that required a taskkill, this MAY fix your problems...

3. modifed sub chtRestore

* fails if your filename is not exactly "chtbackup.cht" (default)

* if default filename is not found, the sub will check for the most recent .cht file in the "filesCHT" directory and use that

* no longer relies on the default filename

* tested against CHT Editor 2.0.0.0 final and 1.8.5.1 - both work fine

4. added MortScriptVersion output string to Init messages so we can debug what versions of MortScript is in use

5. modified checking of xdauc.mscr so that the script works with Energy ROMs from Nov 2010 onwards

6. tweaked pretty tabbing/spacing for a few lines here and there