...so RAW you need to cook it!
[UPDATE APR-25-2009] - Updated SASHIMI Compliance to 2.1 to work with 8.0. It is recommended that all users who use SASHIMI upgrade to version 8.0.
Hello all,
Since SASHIMI has been getting more and more established within the Windows Mobile community, I thought I would share this method for you cooks or aspiring cooks who would like SASHIMI cooked into their ROMS much like UC.
Cooking SASHIMI into a ROM will allow SASHIMI to be launched automatically after a clean ROM flash. In addition, it allows for customized INI files to be launched alongside a particular ROM version to allow for further customization through the SASHIMI install.
So, onto the details...
First, let me say that we aren't actually cooking in SASHIMI itself. The reason for this is that SASHIMI is best run from external storage (like a Storage Card) so it is always around even after a flash. Also, as SASHIMI users will know, I update SASHIMI fairly regularly, so I don't want to cook in a version that will be quickly outdated. Instead, the way SASHIMI Compliance (SC) works is by cooking in a script which calls SASHIMI if it exists.
SC works as follows:
- A shortcut to SC script is placed in \Windows\StartUp
- SC script checks for SASHIMI's AutoRun registry key
- If AutoRun has been run, then exit
- If AutoRun hasn't been run, check to see if SASHIMI exists in the Storage Location defined by the ROM chef.
- If SASHIMI exists, then launch SASHIMI with the AUTORUN parameter (fully unattended AUTO mode) and optionally with a settings.ini file specified by the SASHIMI Compliance Code (SCC)!
In order to get SASHIMI Compliance cooked into a ROM, you will need to download the two files below and follow these steps:
- OperatorPKG.zip - Copy the SASHIMIAR.mscr, SASHIMIAR.lnk, and SASHIMIAR.xml files into your OEM\OperatorPKG directory.
- Edit the SASHIMIAR.mscr to:
- Define the customStorageLocation variable that your ROM users will be using. Since ROMs are usually tailored to a particular device and language, this variable should be known by the chef. This variable can be left empty for some older devices (Kaiser/Diamond) but should probably be manually entered.
- Optionally, include your own unique Sashimi Compliance Code (SCC) (iniNameSCC). This code can be used by users to launch a specific settings.ini fle during SASHIMI installation. To specify a SCC edit the following line:
Try to make you SCC unique so as not to conflict with other ROMs. Keep the SCC relatively short and do not use spaces. A good example would be "BRR-HTC-1.1"
- Code: Select all
####################################################
# Change the following value to a unique ROM string:
iniNameSCC = "BRR-HTC-1.1"
# Change the following to manually specify the root Storage Location that SASHIMI is installed in.
# If empty, script will attempt to automatically detect SASHIMI location. (e.g. "Internal Storage")
customStorageLocation = ""
####################################################
- OEM_PACKAGE_MortScript4.2.zip - Add this as an OEM package when cooking. It adds in the bare minimal files for MortScript which is required for SASHIMI and SC.
- Add the following line to the config_operator.txt:
- Code: Select all
XML: \WINDOWS\SASHIMIAR.xml
This runs the XML file during initial customization and creates the shortcut in \Windows\StartUp.
FOR USERS:
- As a user of a SASHIMI Compliant ROM, I recommend you are using SASHIMI 8.0 or above. Also, you should install SASHIMI to it's default location on your storage device (e.g.: \Storage Card\SASHIMI, \Internal Storage\SASHIMI).
- Optionally, create a settings file for a specific ROM. The setting file should be named SCC.ini, with SCC being equal to the unique SASHIMI Compliance Code provided by the ROM developer. For example, create a setting file named BRR-HTC-1.1.ini and place it in SASHIMI's \INI folder alongside the other INI files.
That's it! For more info, refer to the SASHIMI documentation.
Hope that some of you find this useful, happy flashing!
v.2.0 download 100 times
