yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I'm sure SPB can't do anything that abnormal with a registry key.

Simply export the registry, install the software, register it, and then export the registry again. Compare the two and you will find any changes, one of which must be the key.

Other than that, perhaps it places a file on the device somehwere. Which you should also be able to find with a file compare.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] rush242:
Autoback up

Bengalih,

I had an idea I wanted to throw at you... tell me what you think. Is it possible that SASHIMI could also be used to pull registry settings from the phone?

For example, there are probably 15-20 or so things that people set according to their preferences.

Would it be possible to go through Settings > Personal, and >System and >Connections and make a check box screen for each of the items contained there? That way the user could install a ROM, go through each of those and set them as he desired, and then go through SASHIMI, checking the boxes of the ones he desired, and SASHIMI would export and keep them on the Storage Card with itself. Then, when the user installed a different ROM, he could run through that checkbox list again and have SASHIMI restore them along with whatever else SASHIMI was restoring/installing??

I'm sure that between us, we could come up with all the registry keys that would need to be backed up, and the user could remain responsible for the keys for the programs he installs.

Everything in Settings is, for the most part, pretty standard between ROMs and I think we could make short work of it.

Thoughts, ideas?

Regardless, I can't thank you enough for SASHIMI, you've done a wonderful thing, even as it stands.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
This is pretty much what the customexport.ini file does. It allows you to define any registry entries you want to back up. It backs them up, either to manual or auto, and allows you to restore them during a flash. Read the documentation if you aren't familiar with this option.

So, all the functionality is there, it sounds like you are just asking for a different kind of interface to work with.

I am playing around with a new interface for the Manual phase. One that will allow you to see a list of everything in the manual directories and choose to restore them. I don't really like how currently you need to skip..skip...skip through manual entries to get to the one you want.

So, with the customexport.ini you can export all your registry settings to individual reg files...you can do this now. When I get this new GUI down that will allow you to see each registry file (which you can name as you want, e.g. BlueTooth, Ringers, Etc...) and restore them one at a time. OR,

alternatively just back them up to Auto and restore them all at once.

It might be a few weeks before you see this new interface. I think I have all the code, but I need to break out a separate subroutine for Manual vs. Auto. I condensed them in version 5.0 for code efficiency, but now they appear to be so different I think I need to break them out again.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] carphead:
You were of course correct. I used CeRegEditor to do a remote compare with a registry backup when the only change was entering the registration key.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] dimanto:
SASHIMI AND htc Diamond

I have tried to install your life saving application in my Diamond and I got the following message:

"Screen size should me 240(w)x320(h) to properly display SASHIMI. SASHIMI may not perform optimally."

And then an error about a comma expected in line ...

Is this application compatible with Diamond.

Anyhow congratulations to the programmer of this great app.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laubscherc:
I am speechless!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
SASHIMI should work on non-QVGA devices, however I don't know how nicely the display and formatting will be. I designed this on the Kaiser, and don't have a VGA device like the diamond to test with.

However the Auto Storage Card install routine won't work because it depends on screen taps to specific pixels which will be different on VGA devices like the diamond.

That being said, there was also apparently an error with my code (missing comma) that crashes when trying to log a non-QVGA resolution.

I will be posting a new version of SASHIMI by this weekend (maybe even tomorrow) that will fix that issue. So, when the new version is there you should be able to use it on your Diamond (again, without the Auto Storage Card install ability). I'll be interested to know how it looks on your Diamond or if the formatting is too off.

BTW...the Auto Install to Storage Card I speak about is the "SC" directory option which is discussed in the documentation. So the only functionality you will miss is that.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I installed some SPB software and didn't see these options. I think the problem here may be if you are installing them using the Windows PC-based installer?

Just get the CAB from the PC installer (it usually puts it in the \program files directory on your PC) and just use the CAB in your SASHIMI directory. None of the CABS gave me any problems with a fully automated install.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
New version of SASHIMI should be out within the next few days. Below is the current change log. I believe i have addressed everything in the thread (and more!). Please get any other bug reports in asap.

NEW! - Brand new GUI menu system for Manual Install phase. Makes individual file selection easier!

NEW! - One-off file selection dialog now supported during every step of Manual Install phase.

NEW! -

Infinite

subdirectory processing. No longer are subdirectories for nesting files only limited to one level deep.

[*]UPDATED! - Reorganization of some menu options for more intuitive access.

[*]UPDATED! - ROM language support has been expanded. Auto Storage Card screen taps now supports 8 ROM languages.

UPDATED! - Free space check during Auto Storage Card routine fixed to not check main memory when installing to Storage Card.

UPDATED! - Error checking routines and logging for non-standard ROM languages and non-QVGA resolutions.

UPDATED! - Removed AutoRegExport and FileBackupPath paths and setting. Defaulting back to \REG and \Root respectively. This is due to the new Manual Phase GUI system, these options are no longer necessary.

UPDATED! - VipMSCRexe no longer used for startup executable due to problems processing Unicode characters for multi-language support. Has been replaced with MortScript's Autorun.exe

Just doing some final testing and updating documentation. Trying to make a quick video which walks through some of the newer features as well.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] juju-35:
What a FANTASTIC PROGRAM!

Hello,

I can't say enough about this!!!

I have dreamt of Sashimi, and here it is. I always have found that changing ROM is very tempting, but re-configuring and re-insalling all your programs a royal pain.

I jsut started using 5.0 and it seems to work well.

I do have some questions/suggestions (sorry if some answers are obvious):

1- I do not speak "reg" fluenrly yet, so is there a good list somewhere of the reg to save for some of the most obvious things one would want to restore, like: All system settings, such as Today plug-in configuration, time format, date format, HTC home shortcuts...? Can (has) somoene share(d) thsoe examples?

2- I am assuming you can copy files into the Auto/Root to storage card by using the "/Storage Card" path?

3- THe only thing I could not find how to restore are the shortcut in the menu programm. if you install many cabs (like I do), it becomes very important to install the hortcuts for those programms in folders that make sense for you (TOOLS, GAMES,...), which usually do not install in the directory you woudl like them to by default. One option would be to edit each cab and change the default install directory, but wouldn't it be nice if the subdirectories in the Root directory would also automatically install the shortcut in the same sub-directory in the programm menu? Like all cabs in Auto/Cab/TOOLS would then have a shortcut created in Programs/TOOLS directory.

4- Sashmi crashed every time I had the HTCWaitAnimation cab in my auto list. The new ROM I installed alrady had HTC Wait Animation installed.

5- UC was a pain to programm but has a mode to enable cabs to install that require extra intervention (like put in serial number, or input some settings during installation. Would this be enabled in manual mode?

Thanks again,

Juju
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Some examples have been posted in this thread. Others are prevalent all over the forums. Because it is not SASHIMI specific, I don't take the time to cover all the registry locations available that you may want to back up. You should be able to find most of what you need in 10 or 15 minutes by searching the forums.

Yes, that will work... but I don't know why you would want to copy files from SASHIMI's root directory to the Storage Card? If you need files on your Storage Card...just put them where you need them. SASHIMI's \Root option is really there so you can restore from your Storage Card (permanent storage) to your device storage (which will be erased on a new flash. But, yes...it will work if you create \Root\Storage Card\SomeDir\file.txt, etc...

Everything is controlled by the file structure or the registry. In the case of shortcuts, most of them are stored in \Windows\Start Menu\Programs. So, simply copy this location underneath one of the \Root directories, so it looks like:

\Root\Windows\Start Menu\Programs\ with all your program groups and shortcuts set up how you want. Now, when you run SASHIMI and copy that Root directory (either manually or automatically) it will copy those folders back and your shortcuts will be there.

Now you will still have whatever shortcuts the CABS installed themselves, and there is really no way to prevent this other than edit the CABs directly. If this doesn't meet your needs you can always add a custom .MSCR script into the SASHIMI process which can do almost anything.

I downloaded and took a look at the HTCWaitAnimation cab. The problem is that whoever authored that CAB used the MortScript setup.dll to automatically run an embedded mortscript file. For reasons that I cannot ascertain, this somehow interrupts any other running Mortscripts. This seems to be a built-in behavior of the setup.dll and there isn't really anything I can do to prevent this. Even installing this file during the manual phase will interrupt SASHIMI. The only solution I can give you is to install this file separate from SASHIMI or to add it to an SDCONFIG.txt file and execute it during the UC phase from within SASHIMI. Because SASHIMI passes control to UC at this point, it can't be interrupted.

This is a newly discovered "bug" and at present I don't believe there is anyway to get around this through coding. Luckily, not too many CABs out there use a MortScript-based setup.dll.

Yes, any CAB that requires user interaction to install is best installed in Manual Mode. If it doesn't require input, but you want to add some settings (e.g. registration code to the registry), you can also use a tandem/bundled file.

Hopefully that answers your questions, you should read the full documentation for specifics on the above.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] juju-35:
Sounds good, I will.

Well, tested and now works. Some programms that I want to install to the Storage Card have config files that are copied over my version when re-isntalled, therefore the need to copy over the correct file on the card.

Well, this does not really work for the reason you quote but also that will not work accross different ROMs because it will have different pre-isntalled programms. I would think this need is quite general and was suggesting it would be really cool if you could use the sub-directories in the Cab directory as directory for the shortcuts. I know you cna also edit each cab to change this, it is just another royal pain your magic could avoid...

Yes, I have a bunch of other cabs that do not work. For instance Livingsoft Dictionaries have a dialog box before install that asks to not run explorer or any other program, and that seems to not work even in Manual install mode.

Same with BBconnect, which asks a bunch of inputs and then reboots at the end of the process...it does not start either in Manual mode when answered yes to install.

I guess I may sitll have to manually install a bunch of those....

Thanks again, despite these limitations Sashimi still promises to solve 95% of my new ROM installs.

Juju
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] juju-35:
One more remark...

Sorry for all my postings, but I found also that after flashing a new ROM I coudl not find a way to properly install automatically and run the auto install with Sashimi.

1- I tried the 2577 directory thing but it does not give me the dialog to chose to install on the Card as a result it instlals in main memory.

2- I use a UC ROM,so I tried to link the cab to SDConfig.txt and use the HIDE mode, but it reboots before it gave me the chocie of the shortcut and so it did not work either.

So far, when flashing a new ROM I have found no other way that to manually install Sashimi. Not a huge deal, but not perfect.

A suggestion if I may:

Could you change the cab to install by default only to Storage card to avoid this, and also remove the final dialog to reboot and to create the shortcut and create a shortcut in a default location?

That would make IMO automatic initial install easier...

Juju
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] antjmon:
I've been using this since earlier days and it has developed quite nicely into a work of art. Thank you immensely bengalih. This is one the best addons for any of my pdas since settings savior and hardspl. I'm curious if you built upon settings savior at all, or started from scratch.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] antjmon:
I have no issues with using sashimi after each flash. I simply use the default windows file explorer and then go to the 2577 folder and open the second autorun there. Then I plug my tilt in so the screen wont turn off and in about 5-8 minutes its done. Honestly regarding your sdconfig...in my experiences sashimi is just as fast if not faster and certainly more versatile than uc (no offense to sleuth) so I have completely abandonded the uc method. The only added step is having to wait until the phone reboots and manually selecting the autorun which I actually prefer because I can on the fly adjust which programs are installed where without having to edit a sdconfig file. (VERY useful considering most cooks prefer including different apps)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] juju-35:
Oh I completely agree with you that Sashimi is MUCH BETTER AND EASIER than UC. In fact, it makes ROM flashing a much more smooth experience altogether, as such I would vote for it being the best applciation ever hadns down, and I tried a looot of things!!

I was trying to find if there is a good way to automatically launch it after flashing, but agree it is not a big dfeal to use file explorer and launch manually the Sashimi cab or autorun.

My only suggestion to the author was to automatically create programm menu shortcuts into the same sub directory names you have the cabs in the cab folder, but no luck with pushin this idea so far...:rolleyes: Still very happy about the whole thing and do not look forward to going back to xml programming and magic codes and missing spaces with UC!

Juju
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
This topic has been addressed both in previous threads and the documentation. But, I will cover it one more time and then close the book on it. I DO suggest you read through the documentation fully, since some of your questions are easily answered there.

First off, in regards to #1, if you want CABS to install to the Storage Card during an Auto Install Phase, you need to place them in the SC directory: \Auto\CABS\SC. This gives you the option to install cabs automatically to either the main memory or Storage Card during an Auto phase. Again, this is stated clearly in the documentation.

I don't really know what exactly you are doing in #2. Having a UC compatible ROM is irrelevant for SASHIMI. Even if you want to use the UC option you do not have to have a UC compatible ROM. SASHIMI uses it's own copy of Sleuth's UC to perform processing of the SDCONFIG.TXT file.

When starting SASHIMI after a clean flash you basically have two options.

1) Run SASHIMI.EXE from the SASHIMI\bin directory. This in effect is like running SASHIMI for the first time. It will prompt you to re-create shortcuts. Then you can run SASHIMI from the shortcuts. This is what I suggest you do.

2) Run SASHIMI using the \2577\Autorun.exe option (either manually or by inserting the Storage Card with the \2577 in root). This will run SASHIMI in autorun mode. It will default to Auto Phase and will also default to "YES" and automatically reboot the device.

Let me state that again: IF YOU USE THE \2577 METHOD, NO FURTHER INPUT IS REQUIRED AFTER CLICKING TO RUN AUTORUN.EXE (or inserting the storage card).

If you use option #2, SASHIMI still will run in "setup" mode if you execute it from the \bin directory the first time after a clean-flash.

Again, this is addressed above. Use the SC directory. If I made the program auto default to Storage Card, then I would have people posting saying they want to install to main memory! That's why you can DO BOTH, if you read the documentation to understand how the program works.

There is no reason to remove the final reboot dialog, as it will default to "YES" in autorun mode, and thus does not require any user interaction.

Although it might be one click less to automatically set up the shortcuts, I believe that most of SASHIMI's users prefer the option to setup the shortcuts in the location of their choice. Again, since it doesn't prompt for shortcuts (or anything else) if you use the Autorun mode, I don't see this as a problem.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] juju-35:
Benghali, thanks but do not bash one of your biggest fan :). Also have been flashing for a while so I think I understand the basics more than you seem to imply.

I have read the documentation and all threads

I have no issue using the SC directory to install OTHER cabs that Sashimi itself in the Storage Card

My experience when I use the 2577 method is that Sashimi installs to main memory, not to the SD card!

This is why I tried to use UC to load the Sashimi cab with the dialog mode open. THis did not work either and rebooted before Sashimi would instlall everything

This is what I am doing now and I do not find this ideal and it requires one extra step that is not automatic. Still much better than installing everything by hand of course!!

Again my experience there is that installs Sashimi in the main memory, and created no shortcuts.

I understnad how Sashimi works at a high level and know to use it to instlall my programms where I want, I was saying that if the default install was on Storage card with a default location for the shortcut, that would leave people to do a manual cab install to install it where they want and chose the shortcut location while giviing "automatic install" option do the recomended install (Storage card witha default lcoation for shortcut).

Thanks and peace... :)

Just trying to understand better the options, which hopefully are useful to others, and suggest a few improvements that some others may like.

Juju

PS: I would be happy if you coudl give consideration to my previous shortcut of installed cabs (other than SAHIMI) suggestion, as I woudl think it would be useful to many. Having shortcuts created automatically inside the Program menu according to the subdirectory you chose to put them in the cab directoriy isnide the Sashimi directory would be great. You could always have a shortcut.ini file to specify whether you wanted to go with the default location of the shortcut, no shortcut at all, or subdirectory name location...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Glad we are on the same page now! :) The documentation does state the following:

So, I'm not sure that I could be clearer on the topic! You are correct in that many CABS install things to the registry that would be wiped out after a ROM flash. However I have coded SASHIMI to automatically check and add anything needed back to the registry, so you don't need to worry!.

You're desire is a good one. I agree that many users would find this functionality useful. Unfortunately it is not possible for several reasons:

1) SASHIMI has no control over what is installed from the CAB files. Therefore SASHIMI could not control how or where to place a shortcut. SASHIMI can't even control to tell the CAB NOT to create a shortcut. CABS are self contained, and especially with the enhanced security of WM6+, it is all but impossible to interfere with the installation procedure of a CAB file. So if a CAB file is coded to create a shortcut...it will create a shortcut. The only way to prevent it is to edit the CAB file first on your PC and remove the shortcut pieces.

2) SASHIMI has no way of knowing what is INSIDE a CAB file. This is similar to point #1 however what I am getting at here is that if you have a CAB file called "ABC Application Explorer.CAB" if may have within it several files including one called "AppExp.EXE." SASHIMI does not know the name of the CAB's executable contents, nor does SASHIMI know where this CAB and it's files will be installed (other than Main Memory vs. Storage Card...it does not know directories). Because of this it would be impossible to create a shortcut to any files installed by a CAB.

The above limitations are not limitations of SASHIMI per se. They are limitations of the ability to tap into the wceload.exe program which installs the CABs on a device. This is one reason why applications like UC can't force an install to Storage Card. The programmatic interfaces just aren't available, or are locked down.

So although that type of functionality would be nice (and probably take me quite a bit of code to implement!), it just isn't possible.

True. Again, if a CAB is configured to install a shortcut, there is nothing anyone can do to stop it. Either edit the cab, or delete the shortcut after it is created (which cannot be automated since there is no way to read the CAB to see what was created).

That would be one way to approach it. I think you can also write a provisioning XML file that may be able to copy/delete shortcuts. But again I stress, you can't control what a CAB does.

At this point I think I can confidently say that I know pretty much everything (99% of what) MortScript is capable of. MortScript, nor really any other application out there has the ability to tap into the CAB install process to do what you describe. Again, this is mostly due to security changes in WM6+.

I do think it would be beneficial...just not possible. But, as I write this I have an idea that might work. I just don't know how processor-intensive it will be. I am going to try something out and may have some other type of solution that could work.