yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] juju-35:
Benghali,

that would be so great if you can implement a solution for this!

I am sure you will know best, but given you cannot affect the cab behavior, what about something like this.

1- At a first clean run, before instlaling any cabs, Sashimi asks if you want to export the ROM Start Menu. IF selected yes, then all Start Menu will be saved in the Sashimi directory structure somewhere.

2- At any time and after the user has re-ordered all the shortcuts to his liking in stat menu, you provide a way to export start menu, storing the whole directory structure, but removing automatically the shortcuts that belong to the base ROM.

3- At the next clean install, you have the option to re-install all shortcuts which should delete the whole Start Menu Directory, copy first the ROM only shortcuts and then your Cabs shortucts. An advanced user could play with the ROM shortcuts structure to reorganize them as well prior to cab installs but aftert ROM Start Menu export..

I am sure there are better ways, but that would seem to work at least for my usage...

Looking forward to your solution!

Juju

PS: I guess I was caught not reading docs! I will do better next time.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
tailoring shortcuts

Thank you all for the lively discussion. I think most of the points were covered but I wanted to add a couple of points.

Changing the start menue items is very easy with mortscript in both sashimi and UC. You can write a simple script for this. I assume that most people don't want to change their start menu every 2 weeks, and as a result I don't think automating the script writing process is necessary. Here is my script:

# delete battery icon in S2U2
Delete("\Program Files\S2U2\gfx\battery*.*")

# set up start menu
Rename("\Windows\Start Menu\ALC.2008 Strong.lnk", "\Windows\Start Menu\Programs\ALC.2008 Strong.lnk")
Rename("\Windows\Start Menu\RealOne Player.lnk", "\Windows\Start Menu\Programs\RealOne Player.lnk")
MkDir( "\Windows\Start Menu\Programs\Office Mobile")
move( "\Windows\Start Menu\Office Mobile\*.lnk", "\Windows\Start Menu\Programs\Office Mobile")
RmDir( "\Windows\Start Menu\Office Mobile")
Rename("\Windows\Start Menu\Programs\psShutXP.lnk", "\Windows\Start Menu\psShutXP.lnk")
Rename("\Windows\Start Menu\Programs\notes.lnk", "\Windows\Start Menu\notes.lnk")
Sleepmessage(3,"end of script")
exit

I am sure there is a more elegant way to do it, but it works. The other point I wanted to mention is that I've seen on the UC thread people having trouble running long scripts. I don't know what the timeout is, but if your sashimi install is as long as mine (I have my ppcpimbackup restore all my files and download and install epocrates), then UC won't work without putting several pause scripts in the sdconfig file.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Well that certainly works, but isn't exactly "automated" as it only control pre-defined entries. I have come up with a solution that appears to work along the lines of juju's concept.

I am using an INI file that allows you to define custom locations for shortcuts. It works using a file compare of the Programs Menu both before and after a CAB install and performing operations on newly added files. It won't work in every situation, but I think it should handle the majority of cases. Look for it in the next release, due out by this weekend.

I'm not really sure why you bring this up unless people are using UC to automatically run SASHIMI(?) As I have stated previously (and the documentation shows) this technically can be done by having UC create a shortcut to SASHIMI in the Start Up folder. However, this really isn't recommended. Therefore, I don't know what UC timeouts have to do with SASHIMI. If you enable the UC option within SASHIMI then SASHIMI passes control off to UC at the end of the Auto Install Phase. So, again, I can't see how the length, or complexity of the SASHIMI install affects UC?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
SASHIMI Video Tutorials are here!

A new series of tutorials covering all the aspects of the latest SASHIMI, including a sneak peak at the new features coming with the next version.

If you are new to SASHIMI, you should check out Videos 1 & 2 to get a good idea of what SASHIMI can do.

If you are interested in the newer features, take a look at Videos 3 & 7.

See them now on YouTube

Release 6.0 with the new features shown should be out within 48 hours!​
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] juju-35:
Studentjunk,

I understand one coudl programm all the shrotcuts in mortscript or in XML with UC, but the whole point of Sashimi for me (and I think for many) is that it makes it a ton easier to flash and re-flash and install 99% of your ROM automatically with very little programing skills and pain. If you do not change your start menu then I guess you do not add cabs, in which case you can do a UC script once and for all.

In my case and many cases I think peopel keep chanigng to the newest version fo the cabs, add or try new apps....which makes it cmbersome to reprogram and debug your script each time.

Benghali, cannot wait to test your new development, let me know if you need some tests, I may be able to squeeze some betwen 2 and 3am...! :D:D

Juju
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
don't forget to link to these on the first page when you post the upgrade. thanks for all the hard work!!!!

I just took a look at the shortcut creation tools. Is there a way of putting shortcuts in the '\windows\start menu' folder instead of putting them in the 'programs' folder?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I can do that...easy change.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
I would actually leave the shortcuts exactly where they are...they are perfect there in the Programs\ folder. Start Menu\ folder tends to work very well for apps/progs that you use frequently. I normally run SASHIMI only once after a ROM flash and really don't need to have it in Start Menu... the current option where you choose where to put the shortcuts is perfect for me Bengalih, but it's up to you...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
We aren't talking about the Sashimi shortcut. We are talking about customizing installer shortcuts in the next version. He has a demonstration of it in on of his videos. They were set to only be able to be placed in the Programs folder, but I figured I wasn't the only one who installs some programs to the start menu.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
Am itching for the v6.0 release...I watched the demo videos - they're awesome!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] fcreeves:
WOW. I have been using SASHAMI and just now watched all of your tutorials.

What can I say besides, "What's next?" May be a drag n drop system on the PC where you drag your cabs and regs, in installable order, from a one central folder (which lies on SD or will lie on SD) to a SASHIMI window on the PC that builds an editable config file that you place into SASHIMI for auto installation.

Just a thought. While watching your tutorials it made me think of how LastXP v20 gets updated to v20.1 with a drag n drop system.

Thank you for this phenominal app. I will be busy utilizing it as all the new ROMs can run Igo now. I have to install a majority of apps to SD now since Igo uses up so much memory and crashes w/ MSVC (thanks for that too) or a phone call. I'm going to read your documentation to see if I can get .cab installation to install to SD using sub directories within SASHIMI's directory structure.

Thanks again.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
SASHIMI 6.0 is up.

Had some issues yesterday with the thread getting corrupted in the database. It appears all is back in order now and

this will continue to be the official SASHIMI thread.

Also, the version that was up yesterday had an old documentation file included. Download this latest version to ensure everything is up-to-date.

Sorry for the inconvenience!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
Fantastic! Thanks Bengalih!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Correct. The 6.0 release is updated to create them in the \Windows\Start Menu location by default.

A couple of extra notes on the new customlinks.ini process. Because the method works by doing a file/folder compare before and after a CAB install, the following limitations are in effect:

1) Even though SASHIMI can place shortcuts in the root of \Windows\Start Menu, it will only scan for changes in the \Windows\Start Menu\Programs directory.

2) It will only scan for changes at the

root

level of \Windows\Start Menu\Programs

So, if you have:

CAB1 - Which puts its shortcut in \Windows\Start Menu

CAB2 - Which puts its shortcut in \Windows\Start Menu\Programs

CAB3 - Which puts its shortcut in \Windows\Start Menu\Programs\Games

CAB2 is the only one that SASHIMI will see, since it installs its shortcut in the root of \Windows\Start Menu\Programs. The exception to this is if CAB3

creates

the \Games folder. As such, SASHIMI will pick it up because \Games is created in the root of \Windows\Start Menu\Programs.

I have found that 90%+ of CABs will create their shortcuts in \Windows\Start Menu\Programs or will create a new subfolder there for the application. Therefore, SASHIMI's method should work in 90%+ of the scenarios out there.

So, based on the above, an example customlinks.ini might be:

[LNK Files]
cab1=NONE
cab2=\
cab3=\Programs\My Games

As discussed, CAB1's shortcuts won't be detected, so there really isn't a reason to include it here. I am just putting it here to make the point again that shortcuts created in \Windows\Start Menu aren't scanned.

CAB2's shortcut will get created in \Windows\Start Menu (the root, "\"). So normally CAB2.lnk would probably be placed in \Windows\Start Menu\Programs (again, like 90%+ of the CABs out there). This entry will move it over to:

\Windows\Start Menu\CAB2.lnk.

CAB3's shortcut will get created under \Windows\Start Menu\Programs\My Games. In addition, as I mentioned above CAB3 normally creates it's own directory called GAMES. Since the entire structure is copied, the final location will actually be:

Windows\Start Menu\Programs\My Games\Games\CAB3.lnk

So, the process won't work perfectly in every scenario. Ideally you want the CAB to create its shortcuts in \Windows\Start Menu\Programs directly. If it creates a subfolder that is ok, but remember the entire created folder will be moved to the new location. There really isn't a better way to be able to deal with all the different ways a CAB file might setup shortcuts, and I find this method is the most flexible and will meet 90%+ of the scenarios out there.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] asango:
Wow, this shortcut handling is very handy indeed! Thanks a lot!:):)

One question and one suggestion came up during working with it:

- In the scenario you described above: If Cab3 would normally create his own "Start Menu\Programs\Games" folder and Sashimi would detect this.

But if the folder is already there because another game that was installed before also had this folder hard coded: Will it work also if the folder is already existing and the installed cab therefore is trying to create it but will not because it is already there or does the detection process only work if the folder is really created during the cab install?

- Would it be possible to extend the script in order to use wildcards in the "customlinks.ini"?

Many times new versions of cab files are simply changing their names by incrementing the version number.

For example your own

"bengalih SASHIMI AutoInstaller RAW 5.0.cab"

to

"bengalih SASHIMI AutoInstaller RAW 6.0.cab"

So is it possible to put "bengalih SASHIMI AutoInstaller RAW*" or something into the ini so that the ini does not have to be changed with every new version of the cab?

This would by the way also have the much bigger side effect that all apps with "GPS" in their names would be installable in the "Start Menu\Programs\GPS" folder by simply using the following entry:

"*GPS*=\Programs\GPS"

What do you think about this suggestion?

- And one last thing I would like to report that nearly drove me to insanity until I found the reason:

Some reg entries were auto installed even though I removed every reg file in the "reg" dir and at last I even removed the whole "auto" folder, but still with every auto install these reg entries were imported!?

Then I text searched these entries in all remaining files in the sashimi folder but still found nothing.

Finally I found that in the "bin" directory there was a reg file containing exactly these settings. And the reason I have not found it during the text search was that it was a unicode reg file:mad:

Somehow somewhen I accidentally must have exported or copied this reg file into the "Bin" dir of Sashimi, and the strange thing is that Sashimi is obviously not only importing reg files that are located in the default "Reg" dir, but also in its "Bin" dir.

At least with V5.0 this was the case.

->Is this intentional?

And is this also true for cabs/xml/exe/scripts that anything in the bin dir will be processed as if it would be in the real respective dir?

If yes, is it processed after or before the real intentioned directory is processed?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
I think it's a great idea. Not sure how easy to implement, but my mortscript knowledge is pretty limited.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Correct. If I install CAB1 and it creates \Start Menu\Programs\Cab1.lnk and then I reinstall it with a customlinks.ini file, it will not work since the Cab1.lnk file was already there prior to install. Remember, this works on a file compare/differential. So if the file/folder is already there it doesn't see a change. Since SASHIMI is mostly being used for installs after a clean flash, I don't see this as a major issue. I also don't see any easy way around this. As it is, I think the file compare approach was a pretty novel way to approach this (if I do say so myself :)).... but it has its limitations.

That should be possible. I will consider it in future versions.

This is not intentional, nor is it normal behavior. I re-installed version 5.0 and tested this. I removed all files from the Manual and Auto directories and then placed a CAB, REG, and MSCR in the \bin directory and ran Auto install. As expected, nothing was installed.

The only thing I can think of is that you have an incorrect/corrupt settings.ini file.

If any of your settings.ini entries are set to the SASHIMI directory itself it is possible that the \bin directory is being seen as just a normal subdirectory and getting processed that way.

I would review your settings.ini file, and reset it if necessary. Checking the log file in the future will also save you time in the future. Even if the files are being imported from an unexpected location, they will still log an entry since logging is coupled closely with the operation.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] shonan70:
hi just want to know does it support HTC diamond.Great work
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
read the FAQ in the first post.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] asango:
Great. This will automate the whole process even further and prevent some repetitions every time one has again forgotten to adapt the new file name in case of a new cab version.

Mea Culpa! The file was named "owner.reg". I must have exported this a I tested all the options and was not aware of this.

When I found that it only happened if the file was exactly called "owner.reg" a look in the manual cleared up everything...:o

I never did this so far, but indeed this logging is also a good feature in case of problems. I'll use it from now on...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] dimanto:
4 bengalih

First of all congrats for this excellent application.

I have tried version 6 in my Diamond and as you have already said its working perfectly. So I beleive that you may remove those display warnings.

Now, what about the SD automated installation process? We cannot implement that in Diamond because we do not have an SD but Internal Storage instead?

And, can you tell me if its possible and how to automatically fill in the owner id and password fields after installing each cab?

Best regards!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
If you would be able to send some screen captures to show how it looks on a VGA resolution, I would appreciate it. You can use a program like:

http://xdaforums.com/showthread.php?t=375573 to get the captures if you don't know how.

The Automated Storage Card installtion doesn't work on the Diamond (or any non-QVGA screen) because of the automated screen taps...they would be at a different pixel location with the VGA screen. Also, I do not know about the Diamond's extra memory... you say that it does not have a storage card? If you could send some screen shots of what it looks like when you are installing a CAB that might also help.

As far as filling in the info after a CAB install... you have to find where that info is in the registry and then use a tandem/bundled file. Read the documentation on what the tandem files are. If you need help finding registry differences you can use CERegEditor
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] asango:
Preventing device sleep timeout during autoinstall

@Bengalih:

If one's doing a sashimi auto install without being connected to the power supply, most ROMs do have a sleep timeout that is freezing the install process after some minutes and one has got to switch the device back on to continue the install.

On an automated run including flashing of the ROM there's no means of changing this timeout which is mostly between 1 and 4 minutes.

MortScript has got a function called "IdleTimerReset" which is resetting the timeout counter.

If you would implemet this function in your script and periodically trigger this reset function in SASHIMI.mscr, this should ensure that the whole install process will not be interrupted, and best of all without leaving any traces after the install.

Of course everyone could do this by himself, but with every new version one would have to add it, so could you implement this or any other means of solving this in SASHIMI.mscr?

Thanks a lot!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
I think that's a good idea. I didn't think about it cause I always just uncheck the timeout settings manually.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Easy enough to do. I'm aware of the IdleTimerReset command, but I never think its an issue because I am usually plugged in when re-flashing. I will reset the counter with each CAB install, as it is not intensive on the process. I'll put it in with next release.

thx for the input.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] asango:
Thank you very much, it's always a pleasure, looking forward to the next release!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] zard:
bengalih,

Been happily using v5.0 and then now v6.0, forgotten to send you my thanks and also suggestion.

What I like about the improvement?

In manual mode, you added the option to choose what the next cab to install. That is fantastic.

Something for your consideration?

1. In manual mode, is it possible to increase the font size so that it is easier to read. I don't use all the features, so is not sure if this should apply to the rest.

2. What about adding a coloured background (like green would be great) to manual mode screen? Even better, with option to change the background colour. This will make the screen nicer.

Thanks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
The font size is as large as it can be while allowing the needed text to be viewed. If I made it larget, things may get cut off, or scroll too far off the screen.

This is not possible with Mortscript, sorry.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] licht77:
I had a short glimpse on that tool and think it has a lot of potential! Great work!

Unfortunately its a little bit annoying and time-intensive to find out where all my regged software puts its serials and so on... - so i am afraid that searching and testing for all that information will cost more time than doing the install manually by hand :(

But as soon as your great tool supports some kind of real "automatic" installation (where filesystem and registry is compared before and after the install - like in Thinstall for example) then it will be a real killer application!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MN-Joe:
SC Installs never go automatically

1st I need to say Thank you very much for this contribution to the PPC community. This is a great program and your time and efforts in documenting this and your work to perfect it put most retail products to shame.

I have gotten this setup to the point where I can now reload my phone in a matter of minutes vs. hours. Not so much in time as in just automating the replication so I know things are done in the same order each and every time.

I'm on a Mogul using SASHIMI 6.0 and I've never seen any automation of the SC installs. I still use the Auto feature, but the SC installs I have to walk each one along.

Feature for you to consider - I play with 2 types of ROMs frequently. One from the PPCKitchen where I put in 90% of my needs and another from a stripped down ROM where I have to load everything. I've created 2 full sets of SHASHIMI directories and renamed them as needed, but it would be nice if you had something like Auto1 and Auto2 so you could choose between sets.

I also have 1 annoying issue with certain programs which load themselves into the today screen and get loaded so I'm not able to copy over files I need to setup my configuration (mostly HTC Home). I load 3 Today screen programs in my configuration - HTC Home, Today Agenda, and UltimateLaunch. With each I have a registry entry that should clear the today screen, but these 3 once they install load and create issues. I'm thinking I need a script to run to forcibly kill them so my file copies can occur without errors. So the sequence would look like 1 - Install program, 2 - Run script to kill (unload) and 3 - Copy files, hope this makes sense - and thanks!

I'm thinking what I have below might work:

ShowWaitCursor

If (ProgramXAlreadyRunning = FALSE)

If (ProcExists( ProgramXexe ))

#Kill (ProgramXexe)

EndIf

EndIf

HideWaitCursor
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Sorry you find it annoying and not up to par with enterprise clase products like VMWare's ThInstall. You appear to not have any real clue as to either the functionality of Mortscript nor other products that are out there. Trying to compare this application to a virtualized application packager for windows systems is like trying to compare apples to elephants.

In addition, yes it does take a few minutes to build the necessary files to do an automated install. However, this application is meant for users who most likely flash their ROMS frequently. So, 30 minutes spent preparing SASHIMI can save hours and hours of reinstallation work later on.

So I apologize for taking up your time with an "annoying and time-intensive" application. Perhaps you can write VMWare and ask them when they plan on coming out with ThInstall for mobile devices.

Until then, please don't use this software, as you apparently have no idea how it is really meant to be used.