Don't manually install all your applications and settings after every new ROM flash!  Use bengalih's...

Specialized Automation Script for HTC Installations, MortScript Initiated 

or simply...

 

SASHIMI Auto Installer RAW Edition v.7.0

SASHIMI FAQ

CHANGE LOG AND FIXES

KNOWN ISSUES

INSTALLATION

            Upgrading SASHIMI

            Installing SASHIMI

            Re-Installing SASHIMI

BASIC STRUCTURE AND FEATURES

ADVANCED SETTINGS AND FEATURES

            Menus

            Auto Install to Storage Card

            Tandem Files and Bundling

            .AUTO Files

            EXE Parameters

            Custom Links (Shortcuts)

            Custom Export

            File Backup

            Custom Tools

            UC Settings

            Autorun and UC Initiated Options

            Command Line Options and Quick-Links

SAMPLE INSTALL RUN

ADDITIONAL INFO

            File Processing Order

            SASHIMI Folders

            SASHIMI Files

            SASHIMI Registry Entries

            Makisu

CREDITS

LICENSE AND DISTRIBUTION

 

SASHIMI FAQ


What is SASHIMI?
SASHIMI is first and foremost an installer. Its main function is to install CAB, .REG., .XML, .EXE, and .MSCR  files that can be used when setting up your device.  It can be run in Manual Mode, Automated Mode, or in Manual+Auto mode.  SASHIMI can also perform backups of your important files and registry entries and allow for easy restore during installation.   It would be impossible to describe all the additional things that SASHIMI can do....well actually, not impossible, just lengthy...so read the documentation or check out the series of video tutorials!

 

Why SASHIMI?

You don't really think I came up with that unwieldy name first do you?  SASHIMI, like all great things, is RAW!  RAW, like sushi, sashimi means "uncooked". A RAW installer is most suitable for use on uncooked, stock, or lite ROMs.  It helps users who would prefer to install all of their own apps an easy semi-automated way to do it.  Of course it can be be used on cooked ROMs too, we sushi chefs like to share!  Arigato!  SASHIMI builds on the feature set of it's predecessors and the VIP+bengalih RAW Auto Installer, but with more wasabi-infused features!


What devices will SASHIMI work on and is tied to a specific region/language?
SASHIMI was built for the HTC Kaiser and its variants. However it should work on any device running Windows Mobile 6\6.1 with a QVGA or VGA resolution.  SASHIMI should work on all WM6\6.1 ROMS regardless of language.  For more detailed information see SUPPORTED LANGUAGES.  SASHIMI's basic functionality should work on non-QVGA/VGA devices however formatting of the menus may not be ideal.  In addition, some special features (like the Auto Install to Storage Card) will not function on non-QVGA/VGA devices because they depend on screen taps that are hard-coded to QVGA/VGA resolutions.

Can SASHIMI do this, that, and the other thing?
Yes. But seriously, read the documentation and go through the tutorial...you will be an expert afterwards. If there are features that SASHIMI doesn't have please post requests in the thread. If the requests sound good and I have the time to implement them, I will!  Also, be sure to take a look at the available video tutorials for extra insight!

SASHIMI r0x0rz d00d, you r0x0rz, what can I do 4 U?
Gee thanks. I'm just happy people are using it. Just spread the word and leave feedback on what you like or what you don't.  If you really want to make a contribution, there are people who need it more than I.

You didn't answer my question here. This FAQ sucks.
Technically I shouldn't even put this in the FAQ, it's a statement, not a question. More accurately it's an insult. Why are you insulting me?  If you read the documentation and still have questions, post in this thread and they will be answered.

 

CHANGE LOG AND FIXES

 

v.7.0 - 8/09/08

v.6.5beta - 8/02/08

v.6.0 - 6/29/08

v.5.0 - 6/20/08

v.4.6 - 6/13/08

v.4.5 - 6/12/08

v.4.1 - 5/31/08

v.4.0 - 5/31/08

v.3.0 - 5/22/08

 v.2.0 - 5/16/08

v.1.0 (under VIP+bengalih RAW Auto Installer name) - 5/15/08

KNOWN ISSUES

INSTALLATION

 

UPGRADING SASHIMI

 

If updating from a previous version of SASHIMI it is recommended to backup all INI files and uninstall the previous version.

Uninstalling the previous version should only remove SASHIMI installed program files, not any files that were manually copied into SASHIMI's directories.

Alternatively you can install directly on top of the old version.  INI files will be preserved and updated with any new entries.

It is strongly recommended to run through the entire tutorial again to learn about any major changes of SASHIMI's core features.

Please also re-read the sections for all the customized INI files to check if there have been any syntax updates or changes.

 

INSTALLING SASHIMI

 

The SASHIMI Auto Installer is designed to be as easy and intuitive as possible!

 

Let's start by looking at how to install:

  1. Copy the bengalih SASHIMI Auto Installer RAW cab file over to the device.

  2. Run the cab on the device and INSTALL TO STORAGE CARD (or Internal Storage).

  3. During  installation, SASHIMI will prompt to setup shortcuts for the application.  Depending on the security configuration of the device, it may also ask to setup security for unsigned applications and then, optionally, reboot.

Congratulations, installation is complete!

 

RE-INSTALLING SASHIMI

 

It is NOT necessary to re-install SASHIMI after flashing a new ROM.

Simply run SASHIMI.exe from the \bin directory and SASHIMI will detect a clean install and prompt to setup shortcuts and security.

Alternatively, running Autorun.exe from the \Bin\2577 directory will run SASHIMI in one-off Auto mode without any user interaction!

 

BASIC STRUCTURE AND FEATURES

 

Learning how to use SASHIMI is as simple as understanding its directory structure.

Review the following directory structure:

That's it...it's really simple.

Let's take a look at some advanced features and then walk through a sample run...

 

ADVANCED SETTINGS AND FEATURES

 

Let's take a look at some of the advanced settings and features of SASHIMI to take full advantage of its power!

Most of the additional features of SASHIMI can be accessed from the Tools or Settings menu:

 

MENUS

TOOLS MENU

 SETTINGS MENU

AUTO INSTALL TO STORAGE CARD

 

To have CAB files install to the Storage Card in Auto mode, place them in \SASHIMI\Auto\CAB\SC (or a directory called \SC under your CAB location).

Any cabs in the SC directory (and subdirectories) will get auto-installed to the Storage Card.

NOTE:  This process is the same for devices with Internal Storage instead of a Storage Card (like the DIAMOND).  The SC directory is still used.

 

This process depends upon SASHIMI  being able to properly interpret the onscreen text in order to send automated screen taps.  Storage Card installs will be skipped if either of the following is true:

  1. An unsupported language is detected.  For more information see SUPPORTED LANGUAGES.

  2. A resolution other than QVGA/VGA is detected.

SASHIMI will issue a warning at run-time if either of these scenarios are detected.  An event will also be logged to the system log when Auto Install to Storage Card is skipped.

 

NOTE:  It is recommended not to touch the screen or use other applications while SASHIMI is installing and this is especially important during this phase.

NOTE  Not all applications will work with automated installs (either to main memory or storage card).  If a CAB file requires additional user interaction, it is generally better suited to install during the Manual Phase.  In addition, some 3rd party applications which take control of the device's display may interfere with the Auto Install to Storage Card process (e.g. screen shot or other capture software).

 

TANDEM FILES AND BUNDLING

 

In addition to placing .EXE, .REG, .XML, and .MSCR files in their respective directories, they can also be placed in the same directory as  the .CAB files.  They should be named identically to the .CAB's (but with their own extension).  This will automatically Import/Provision/Execute these files when the .CAB file is installed.

These are called tandem files and the process is called bundling.

For example:

If a .CAB file called HelloWorld.CAB is placed in either the \Manual\CAB or \Auto\CAB directories,

then placing a file called HelloWorld.reg in the same directory with the .CAB will import the registry file when the .CAB installs.

Likewise, if a HelloWorld.mscr script or HelloWorld.exe executable is added into the same directory, it too will be run alongside installation of the .CAB.

 

.AUTO FILES

 

In addition to the tandem file features listed above, SASHIMI v7.0 introduces a new tandem .AUTO file for use with .CABs.

An .AUTO file can only be used with .CAB file during the Auto Install phase and is only supported when installing to main device memory

(NOT with the \SC, Auto Install to Storage Card feature).

 

The .AUTO file is a specialized script file that can be customized to automate additional interaction needed for a CAB's proper installation.

A tandem .AUTO file should be created in the same directory as the .CAB with the same name.

 

For example, to automate SuperText.CAB create an .auto file named SuperText.auto in the same directory.

 

A sample .auto file is located at \SASHIMI\bin\sample-file.auto

This file should be used as the template for ALL .auto files.

 

To use:

  1. Copy it to the .CAB's location

  2. Rename it to correspond to the associated .CAB

  3. Edit as below:

The contents of this file are in Mortscript, but the only sections that should need modification are highlighted below:

 

The windowTitle parameter should be set to the title dialog (Window name) that the CAB presents during installation.  This field is case sensitive:

########################################################
windowTitle = "Program License Agreement"
########################################################

The keystroke section must contain a list of all keystrokes necessary to automate the .CAB installation.

Format of command is SendKey(windowTitle).  Only the Key should be changed.  Place multiple commands on separate lines.

# Send keystroke to window
########################################################
SendCR (windowTitle)
########################################################

The sample file contains additional syntax on other commands.

For example, if the automation required is to move the cursor to right twice and then hit enter, the syntax would be:

########################################################
SendRight (windowTitle)

SendRight (windowTitle)

SendCR (windowTitle)
########################################################

For additional information on how to send keys and automate screen text, please refer to the MortScript documentation.

 

EXE PARAMETERS

 

Defines command line parameters for .EXE files.  Will match listed .EXE files that are installed during the Manual or Auto Phases (including Tandem files) and run the .EXE with the parameter defined by the exeparams.ini file.  The exeparams.ini file should be located in the \SASHIMI\bin directory.

A sample file called sample-exeparams.ini is included in \bin to show the proper syntax.

exeparams.ini Syntax

 

The exeparams.ini file enables listed .EXE files to be run with a command line parameter during the Auto or Manual phases of SASHIMI.

The syntax is as follows:

[EXE Parameters]
cusTSK=\Windows\Windows Mobile Green.tsk

CUSTOM LINKS (Shortcuts)

 

SASHIMI provides the capability to control how shortcuts are created for CAB files during install.  This capability is defined within the customlinks.ini file.  The customlinks.ini file should be located in the \SASHIMI\bin directory.  A sample file called sample-customlinks.ini is included in \bin to show the proper syntax.

customlinks.ini Syntax

 

The customlinks.ini file enables the moving or deletion of .lnk (shortcut) files after a CAB has completed installation.  The syntax is as follows:

[LNK Files]

Myapp-version*=Programs\MyApps
regedit.Rpr_ARM=Programs\Registry Tools
kevtris=NONE

*=Programs\Other Tools

In the above example, when the regedit.Rpr_ARM cab file is installed it's shortcuts will be moved to the Programs\Registry Tools submenu.  When the kevtris cab file is installed, no shortcuts will be created (or technically, it's shortcuts will be removed).

 

The wildcard (*) is also supported.  In the above example, all CABs that begin with Myapp-version will have shortcuts created in Programs\MyApps, since the wildcard is used.  In addition, the last entry will match ALL undefined CABs and likewise create their shortcuts in Programs\Other Tools.  The most restrictive entry is matched first, so you can use the full/partial wildcard in addition with specific entries.

 

NOTE:  The folder defined for each CAB will be created as a subfolder of \Windows\Start Menu\.

 

TIP: To assist in the creation of a customlinks.ini file, use TOOLS > Additional Tools > Make CUSTOMLINKS.INI.  It provides the ability to define a source directory (and subdirectories) to enumerate all CAB files into a basic customlinks.ini for further customization.

CUSTOM EXPORT

 

Exports selected registry entries for backup/restore purposes defined by the regexport.ini file.  The regexport.ini file should be located in the \SASHIMI\bin directory.

A sample file called sample-regexport.ini is included in \bin to show the proper syntax.

regexport.ini Syntax

 

The regexport.ini file enables specific registry entries to be exported into .REG files for future importation during the Auto or Manual phases of SASHIMI.

The syntax is as follows:

[MySettings]

RegExportDirMode=Manual

key1=HKCU\ 

Here is another example:

           

            [MySettings]

            RegExportDirMode=Manual

            key1=HKCU\

 

            [MySoftware]

            RegExportDirMode=Auto

            key1=HKLM\Software\

            gobbledegook=HKLM\Apps\

 

This example will create two files: MySettings.REG in the manual directory and MySoftware.REG in the auto directory:

Once the formatted regexport.ini file is created, it should be placed in the \SASHIMI\bin directory.

To perform the export go to the Tools > Registry Tools menu and run Custom Export.

This will process the regexport.ini file and create the registry files in the appropriate directories.

 

NOTE:  All exported files are placed in either the Manual or Auto REG Path as defined by RegExportDirMode.

           

FILE BACKUP

 

Backs-up selected files and folders for backup/restore purposes defined by the filebackup.ini file.  The filebackup.ini file should be located in the \SASHIMI\bin directory.

A sample file called sample-filebackup.ini is included in \bin to show the proper syntax.

filebackup.ini Syntax

The filebackup.ini file enables specific files and folders to be backed up for restoration during the Auto or Manual phases of SASHIMI.

The syntax is as follows:

[FileSet1]

FileBackupDirMode=Auto

file1=\My Documents\My Pictures\           

To backup a single folder use:  
                               		\Program Files\MyProgram\*.* This will backup everything in MyProgram.
To backup a folder and all subfolders use:    \Program Files\*.*,* This will backup everything in Program Files including subfolders.
The ",*" denotes subfolders.
To backup a single file use:      \Program Files\MyProgram\config.ini This will backup just the config.ini file.
 
To backup all files of a single type:  \My Files\*.mp3 This will backup just the .mp3 files in My Files

 

Once the formatted filebackup.ini file is created, it should be placed in the \SASHIMI\bin directory.

To perform the backup go to the Tools > File Tools menu and run File Backup.

This will process the filebackup.ini file and copy the defined files and folders to the appropriate directories.

 

NOTE:  All backed up files are placed in either the Manual or Auto Root Path as defined by FileBackupDirMode.

 

CUSTOM TOOLS

 

SASHIMI allows for the addition of user defined custom applications and scripts into the Menu System. 

The customtools.ini file should be located in the \SASHIMI\bin directory.  A sample file called sample-customtools.ini is included in \bin to show the proper syntax.

customtools.ini Syntax

The customtools.ini file allows for the specification of the layout of the Custom Tools menu within SASHIMI including its name and applications.

The syntax is as follows:

[Custom Tools]

CustomToolsMenuTitle=Custom Tools

Clear Storage=\Windows\ClearStorage.exe 

Command line parameters for .EXEs are supported.  For example, to run the program MyApp with the parameter -backup add the following line to customtools.ini:

           

            My App=\Program Files\MyApp.exe,-backup

Once the formatted customtools.ini file is created, it should be placed in the \SASHIMI\bin directory.

Access the Custom Tools menu from the Tools menu. 

 

UC SETTINGS

 

User Customization (UC) allows the use of an SDConfig.txt file to automate the install of .CAB and .XML files.  It also allows copying of files and some other custom commands.

In reality there isn't much UC can do that SASHIMI can't, but the feature is included for those that want to continue to use their SDConfig.txt files from previous UC setups.

The current ROM does not have to be UC compatible in order for this capability to work.  SASHIMI includes the necessary UC file to process the sdconfig.txt file.

 

To use UC with SASHIMI first place an SDConfig.txt file in the root of the Storage Card.  Then, go to Settings > UC Settings and choose Enable UC.

When UC is enabled it will execute the SDConfig.txt file during the final  part of the Auto phase.

 

To learn more about UC and the syntax of SDConfig.txt files, go here.

 

AUTORUN and UC INITIATED OPTIONS

 

Although starting SASHIMI in Auto Install mode takes only a few quick seconds, there have been questions on how to further automated SASHIMI following a clean install.

Due to these requests to automate SASHIMI to run without additional  manual intervention, the following methods were developed:

Autorun - Autorun allows SASHIMI to run automatically when a Storage Card containing SASHIMI is placed into a device.  This option is best suited for a brand new device or when provisioning many devices (such as in a corporate usage).  To use Autorun, simple move/copy the \2577 directory to the root of the Storage Card.  When the Storage Card is next inserted into a device, SASHIMI will automatically execute in Auto Install Phase. 

 

TIP:  Autorun.exe can be run manually from \SASHIMI\2577 to do a quick launch in AutoRun mode following a clean flash!

 

NOTE:  Some other applications may also use a \2577 directory for Autorun functionality (e.g. TomTom).  If this is the case then you must remove or rename the other application's \2577 directory to use SASHIMI's \2577 directory.  Only one \2577 directory with its corresponding Autorun.exe file can be active on a device at any time.

 

UC Initiated - UCInitiated functionality is provided by a set of files in the \SASHIMI\UCINIT directory.  Simply copy the SDCONFIG.TXT file from this directory to the root of your Storage Card.  When UC runs it will read this SDCONFIG.TXT file and automatically configure SASHIMI to perform an Autorun following UC's reboot. 

 

NOTE:  You will need to manually edit the provided SDCONFIG.TXT file if you are using something other than "Storage Card"

 

TIP:  A registry key will be set to prevent multiple Autoruns of SASHIMI in both of the above scenarios.  See the SASHIMI REGISTRY ENTRIES for more information.

COMMAND LINE OPTIONS AND QUICK-LINKS

 

SASHIMI now allows for several command line parameters to help automate the use of certain menus and tools.

 

SASHIMI must be called with these parameters set to the runmode variable (e.g. runmode=REGEXPORT)

For more information on how to use parameters with MortScript files, view the MortScript documentation.

 

The available command line parameters for runmode are:

TIP:  For ease of use Quick Links for the six main parameters are automatically created when using Create Shortcuts from the Additional Tools menu.

The quick links can be run manually, or assigned to buttons.  In addition, using these quick links it is possible to schedule automated backups using system notifications or any 3rd party scheduling tool. 

 

SASHIMI also supports a settingsFile command line parameter to load a specific settings file at runtime.

 

For example:

settingsFile=MySettings.ini

 

This will copy the defined settings file to settings.ini and initiate SASHIMI with those settings.

 

SAMPLE INSTALL RUN 

 

Now that you have seen all the features of SASHIMI, let's walk through a sample Install which includes some included sample files:

  1. Install the application using the procedures in the Installation section above.

  2. Run SASHIMI from the created shortcut.

  3. SASHIMI will perform a systems check for any problems.  If prompted, resolve the problems as described and  run SASHIMI again.

  4. After a few seconds, the Main Menu will appear asking which Installer Mode to run.  Let's go with the full Manual+Auto.

  5. The Manual Install Phase will start, displaying the main menu for Manual Operations.  Click on the CAB option to enter the CAB menu.

  6. The Manual CAB Path location display, allowing you to choose a CAB file.  Double-click to install "SASHIMI MANUAL INSTALL CAB TEST" and then follow the prompts to install the CAB to the Storage Card.

  7. The status dialog will show a tandem .REG file associated with the .CAB being installed.

  8. The status dialog (and pop-up script) will show a tandem .mscr bundled with the .CAB file being installed.

  9. You now have the opportunity to choose any additional .CAB files to install.  We don't need to install additional .CABs, so click CANCEL to return to the Manual Phase Menu.

  10. Click to open the REG menu.

  11. Browse to \REG\Sub1 and double-click to import the MANUALINSTALLRECURSIVETEST sample .REG file.

  12. You now have the opportunity to choose any additional .REG files to import.  We don't need to import additional .REGs, so click CANCEL to return to the Manual Phase Menu.

  13. We will skip the XML menu since we don't need to provision any XMLs now.  Click to open the Root menu.

  14. The Manual Root Path location display, allowing you to choose a folder to copy.  Double-click to copy over \PROGRAM FILES and its contents.

  15. Choose YES if asked for a normal copy.

  16. You now have the opportunity to choose any additional folder to copy.  We don't need to copy additional folders, so click CANCEL to return to the Manual Phase Menu.

  17. We will skip the EXE menu since we don't need to provision any EXEs now.  Click to open the MSCR menu.

  18. This last step in Manual Install is to present the scripts from the Manual Scripts path be run.  Scripts are run last to allow for customization of anything previously done.  Double-click to run the MANUALSAMPLESCRIPT sample .MSCR file.

  19. You now have the opportunity to choose any additional .MSCR files to run.  We don't need to run additional .MSCRs, so click CANCEL to return to the Manual Phase Menu.

  20. Click > End Manual Phase

  21. Now the Automated Install Phase will start, a status window will pop-up to display the process.  The process may occur quickly, but the log file can be consulted if necessary.

  22. First a sample .CAB is automatically installed.

  23. Now an example of an Auto Install to Storage Card will execute.  The cab file will begin installation and it will automatically select the proper destination.  Prompts will appear on the screen, but do not touch them, SASHIMI will automatically navigate them for you.  (applies only to SUPPORTED LANGUAGES).

  24. After all the .CABs are installed a .REG and .XML file will get processed automatically.

  25. The contents of \Auto\Root are then automatically copied to the device's main memory.

  26. Now a sample .MSCR file is automatically run.

  27. Finally, a prompt to reboot the device appears.  You can click NO since a reboot isn't required.

 The sample Install is now complete.  The following should exist if you properly followed the instructions in the Sample Install Run: 

Once you've double checked everything is where it should be you can uninstall the sample CABS, delete all of the above entries, and remove any sample files and folders from within the \Storage Card\SASHIMI directory structure.

 

ADDITIONAL INFO 

 

RESET RO (READ-ONLY) and DESTRUCTIVE OVERWRITE

 

When performing Root copy procedures with SASHIMI, there are two additional features available:

 

Reset RO (read-only) - Standard xcopy procedures will not overwrite read-only files in the destination.  SASHIMI however provides and enables this ability by default.  To disable this feature (no overwrite read-only files) go to SETTINGS > Copy Operations > Enable/Disable Reset RO.

 

Destructive Overwrite - Standard xcopy procedures merge the source and destination files, replacing destination files when they exist.  However, in some cases the need may be to remove the destination directly entirely, replacing it with the Root source.  When performing Root copy in Manual mode, SASHIMI will determine if the target directory already exists.  If the directory exists, SASHIMI will prompt for a standard copy (merge) or a Destructive overwrite, which will delete the contents of the destination directory prior to copy.  Auto mode Root copy operations always perform a standard copy (merge).

 

FILE PROCESSING ORDER

 

The order in which SASHIMI process the various steps within the installation phases is as described below

(assuming a full Manual+Auto Install is run):

* All file and directory processing is done alphabetically by file, folder, and then subfolder for each file type.

 

SASHIMI FOLDERS

 

SASHIMI

│
├───2577 - Used for Autorun options.  Can be removed if not needed                                 
├───Auto - Root directory for Auto Install Phase processing                     
│ ├───CAB - Default directory for CAB and tandem/bundled files for auto install
│ │ └───SC - Default directory for CAB and tandem/bundled files for auto install to Storage Card

│ ├───EXE -  Default directory for EXE  files for auto install
│ ├───REG - Default directory for REG files for auto install.  Also used for output of a Custom Export.
│ ├───Root - Default directory for Auto File Backup mode and additional files/folders for copy during auto install
│ │ └───Program Files - Sample directory.  Can be removed.
│ │     └───bengalih
│ │         └───SASHIMI
│ │             └───Copy Test
│ ├───Scripts - Default directory for .MSCR files for auto install.
│ │ └───Sub1 - Sample directory.  Can be removed
│ └───XML - Default directory for .XML file for auto install.
├───Backups - Default location of full registry exports and backups.  Location of Owner.reg backup file.
├───Bin - Location of all application executables and .ini files
├───Log - Location of log files

├───Makisu - Location of Makisu plug-in application.  See Makisu documentation for more info.
└───Manual - Root directory for Manual Install Phase processing
   ├───CAB- Default directory for CAB and tandem/bundled files for manual install

   ├───EXE - Default directory for EXE  files for manual  install
   ├───REG- Default directory for REG files for manual install.  Also used for output of a Custom Export.
   │└────Sub1 - Sample directory.  Can be removed.
   ├───Root - Default directory for Manual File Backup mode and additional files/folders for copy during manual install
   ├───Program Files - Sample directory.  Can be removed.
   │   └───bengalih
   │     └────SASHIMI
   │           └────Copy Test
   ├───Scripts - Default directory for .MSCR files for manual  install.
   └───XML - Default directory for .XML  files for manual install.

 

SASHIMI FILES

 

The main files necessary for SASHIMI's proper operation are those located in the \SASHIMI\Bin folder.  The following is the list of files and their function:

SASHIMI REGISTRY ENTRIES

 

The following registry entries are used by SASHIMI:

SUPPORTED LANGUAGES

 

SASHIMI should work with all ROM languages for basic operation.  Language specific variables, like the name of the Storage Card will be auto-detected by SASHIMI.

The Auto Install to Storage Card feature will only work with languages that have key words pre-programmed into SASHIMI.  Currently SASHIMI supports the following languages (and codepages):

Makisu

 

SASHIMI comes bundled with a customized version of Makisu XML Maker.  Makisu allow for the creation of provisioning XML files for e-mail and wireless account settings.  SASHIMI will automatically add an entry to the customtools.ini file so that Makisu appears within the Custom Tools menu.  Access Makisu from the Tools > Custom Tools menu.  For more information, see the accompanying Makisu documentation.

 

Now all that's left is to put your own .CAB, .EXE, .REG , .XML, and .MSCR scripts into the proper directories and run it for yourself!

Now go and flash some ROMS....enjoy!

 

CREDITS

 

Thanks go to:

 

Mirko Schenk - Author of MortScript, without which none of this would have been possible.

 

v3patel(VIP) - for his original VIP installer script which was a good portion of the inspiration for the original SASHIMI.

While it still bears some similarity to the VIP installer, it's grown well beyond and filled with tons of new features.

v3patel is also active in suggesting new ideas to help make SASHIMI even better.

 

SKKV Software - For their SKTOOLS.  The trial version is included in this package to assist with the custom registry

exports and full backups/restores.  While the trial functions adequately for purposes of SASHIMI, you may want to check out full

verisons of their software at http://www.s-k-tools.com

 

DotFred - For his Task Manager application.  This is what gives SASHIMI the power to import .REG and .XML files. 

The Task Manager program of course is so much more, and I urge you to try it out for all of its features.

 

Sleuth - for his contributions to the XDA community and his work on UC which is integrated and included.

To be honest, I was going to just use the built-in Autorun.exe and config.txt files for processing

(which also would have been compatible with the UC sdconfig.txt format).  Unfortunately, the built in Autorun.exe

automatically deletes .CAB files after installation!  Sleuth's SDAutorun.exe doesn't exhibit this behavior,

which made it a more user friendly choice.

 

SASHIMI Users - To all of you who use the program and provide feedback and inspiration in the forums.  Thanks!

 

LICENSE AND DISTRIBUTION

 

This script and associated applications are free for personal use.  Personal modification is allowed.

Any published modifications to the script should be credited to its author.

For corporate use please contact the author, bengalih, on xda-developers.

To modify SASHIMI for use and distribution on devices other than that which it was originally intended,

contact the author, bengalih on the xda-developers.com forums.

 

For more info, support, bug reports, or feature requests visit the xda-developer forum or see the SASHIMI video tutorial series!