Hey all, Well I just saw this post and first off wanted to let everyone know there is a new version of SASHIMI over at
winmo-experts.com. Version 8 includes mostly better support for newer devices (more resolutions and storage card options). If you are a SASHIMI user I recommend you upgrade and please post any feedback over in the forums there.
I also wanted to thank all of the SASHIMI users here and hopefully clear up some misconceptions about how SASHIMI works. I personally believe that SASHIMI is the most powerful installer out there. SASHIMI at its most basic functional level does pretty much everything UC does and with just a little extra work much much more.
Some of the things that only SASHIMI does:
- Allows installation of CABS to Device Memory, Storage Card, Internal Storage, etc.
- Allows the use of .AUTO files to automate CAB installs which require user input.
- Easy drag-and-drop allows simply placing files in the directories instead of writing any code.
- Processes REG files in addition to XML - Many users find writing a REG file is much easier than XML.
- Runs custom Mortscripts to do anything else you can code. Runs EXE and LNK files and installs Certificate Files.
- Can automatically continue after a restart from a CAB during installation.
Although I always enjoy getting new SASHIMI users, I don't feel I have a
competition going with UC or any of the other installation methods. I have always tried to design SASHIMI to be user friendly and powerful. Whenever I hear of a lack of what other installers can't do, I have tried to put that into SASHIMI. I also believe the documentation of SASHIMI (including the videos) make it the easiest to use.
I don't intend to (and have never before) badmouthed any of the other installers out there because I believe that the development is good for the community. I also acknowledge that for certain users they may prefer lesser functionality for an interface that they are already comfortable with or simply are happy enough with their installer that they don't feel the need to explore. For those of you who use SASHIMI know that I even integrated UC into it for those who wish to use both.
For whatever reason there are still alot of misconceptions about what SASHIMI is, what it can do, and how it works. Personally I believe these are mostly from people who didn't want to take the 10 minutes to watch a video or read the documenation. It appears most of the posters in this thread have actually worked with it to some degree and I always encourage feedback since I always want to make the program something people want to use.
In closing, I just to reply to a few of the comments posted here to maybe clear up a few things --
@chazybaz13's comment of "if it was so great it could do the cab installs and backup restores on its own" and zikronix's reply of "it could if a chef would actually build the compliance support in to the rom":
Yes, this is exactly right. UC only runs automatically after a flash if a chef has added in the UC compliance. SASHIMI can run the same way if a chef uses SASHIMI Compliance (SC). Since UC came about before SASHIMI, and had a larger initial following (not sure what the ratio is now) more chef's integrated it. However the instructions for cooking in SC are available over at
winmo-experts.
Another point on this is that SASHIMI can run automatically after inserting the Storage Card if using the \2577 directory which is detailed in the documentation. Of course every person is entitled to their opinion, but I find it a little silly that even if this were an issue, that taking the 5 seconds to click to run SASHIMI (or UC if the case was reversed) should make a difference as to which one is used. I think the core functionality would be the more preferable factor to debate.
@parkjam's comment of "I like UC because it allows me to tweak on a per ROM basis":
SASHIMI does have the capability through using multiple .INI files to load up a different set of CABS (based on their directory) for use with different ROMs. In addition, the latest version (8.0) includes a "Skip" directory which allows you to quickly drag and drop those CABs you don't want to install into a subdirectory for easy retrieval later.
Again, personal preference here, but dragging and dropping a file is about as easy as opening a files and commenting/uncommenting a line.
@conflipper's comment of "RUNCC is going to be the new winner, I can tell you that right now. HTC program that will search for configure files, and then run them in a certain order, but it lets you customize what order, and what to look for, very nice.":
I must admit that I don't know too much about RunCC yet as I am still using 6.0/6.1 ROMS. However the most info I could find on it was a
post Noonski has over at XDA where he is integrating it with AutoRun. In fact, as he states RunCC is really nothing more than a new way that HTC is implementing the Autorun Config file and there is no information I can find that states it does anything like searching for and/or configuring files anymore than the old autorun procedure has done. It is simply a new loader with increased performance.
Noonski however has been utilizing the same method he mentions in that RunCC post for a while now, which is basically cooking in Mortscript to a ROM to allow for more options (namely being able to use MortScript to do installation tasks). While his method certainly has merits and possibly some advantages, it is really more of a method to allow cooks easier ways to customize their ROMs by being able to use MortScript to do tasks instead of messing around with all the ROM XML files.
One of the things this method
does allow you to do is to run MortScript files from your UC SDconfig.txt files. While this is certainly better functionality, it still means coding MortScript files yourself, which may be great for some advanced users, although SASHIMI has been able to run custom MortScript files since day one.
In short, I don't think RunCC is a replacement for SASHIMI, or even UC at this point, nor do i think it was ever designed to be one, but just rather a newer loader mechanism for provisioning the same old XML files as before. More info on RunCC may prove that belief wrong, but I will tell you that if it does have some enhanced functionality I will certainly attempt to integrate it with SASHIMI as I have done with UC.
Anyway, thanks for the support and I am always welcome to hearing more about what you like and don't like about SASHIMI. I have been unable to devote as much time to development recently (8.0 took longer than expected to be released) but still plan on keeping it up with the recent devices and technologies. Please post anything directed for me specifically over at
winmo-experts as I check there most often.
Happy Flashing!