yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Thanks!

I added the shortcut creator as an afterthought to a request and don't really think there will be much more development on that front. If someone really really wants to change the location of a CAB's shortcuts AND change the name of the shortcut and all this other mess, then it's probably easier to edit the CAB then to spend so much time going through and creating these INI files.

I may however put in an option to automatically scan a directory and create a skeleton customlinks.ini file to be customized for use.

There isn't really the ability to do any of that within the Mortscript code. I guess I could add an option that would just install all the files listed, but I dont' really see that as different then doing the auto-install. If you don't have manual interaction...it goes in auto. If you need manual interaction, well you need manual interaction anyway, so sitting there and clicking to install the cab really isn't an inconvenience.

As I keep saying, this stuff isn't SASHIMI specific. There are hundreds of threads on this forum about registry entries, including and not limited to everything you mention. I don't have the time or the will to go out collecting all of this and compiling it. SASHIMI is meant for power users, and power users should really understand some basic registry stuff.

If someone else wants to write up a guide to common registry settings for use with SASHIMI then I would be glad to include that and credit them. As I mentioned before, it's really as simple as users sharing their regexport.ini files. I don't really see the need for another menu system to do the job of what the file's syntax does really well.

Can't tell you specifics, except what I've said before which is that any CAB which requires manual user intervention (license agreements, reboot prompts, etc), is best done under Manual and not Auto. Some will work under Auto, some not. I can't really control what someone's CAB will or will not do. I can only code towards the vast majority of them and give a couple options on how to install them (manual/auto/SC).

As always, I'll take everything into consideration. The more user feedback I get on a specific feature, the more likely I am to implement it!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
From the "Tools" menu...it is in the documentation.

Are you sure you clicked "Yes" when it asked you to make shortcuts? Are you sure you looked in the location you chose to create them?

I've done dozens and dozens of installs of SASHIMI while I am developing it, and I never have a problem with shortcut creation. Are you running this on a Kaiser/Tilt or some other device?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Quick Silver:
I most likely clicked the wrong spot with my fat fingers :(

Thanks for all your hard work a great program :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Heh, no problem... let me know if it's an actual issue when you try again.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nikagl:
Hi all,

I've had three (minor) issues today:

1. It automatically installed Schap's Advanced Config into Storage Card, but there's nothing in the Auto\CAB\SC folder.... why? The log too says it was installed into Storage Card:

03/21/08,12:17:30,Auto .CAB install to \Storage Card successful. VALUE: \Storage Card\SASHIMI\Auto\CAB\Schaps_AdvancedConfig_v2.1.0.0.CAB

2. For some reason it started the install of all CABs in the Manual folder too - I have definately selected "Auto" only...

03/21/08,19:04:22,Auto .CAB installed. VALUE: \Storage Card\SASHIMI\Manual\CAB\3dtrackingfree.CAB

Related to this it also tried to import provisioning files from this folder which are no provisioning files at all:

03/21/08,19:04:35,Auto Tandem .XML file provisioned. VALUE: \Storage Card\SASHIMI\Manual\CAB\AdvancedConfig\Old\AdvancedConfig_0409-nikagl-20080615-1500.xml

3. To fix this I moved the Manual\CAB folder to the root, when I performed a hardreset and tried the install again, it tried to install the CABs from the Manual folder again, but now they were not in there anymore and it presented an insufficient space error (even though there's enough space, but probably caused by the file missing):

03/21/08,12:25:16,Auto .CAB skipped due to insufficient space in main storage. VALUE: \Storage Card\SASHIMI\Manual\CAB\3dtrackingfree.CAB

Here's my settings file:

[File Paths]
ManualCabPath=\Storage Card\SASHIMI\Manual\CAB
ManualRegPath=\Storage Card\SASHIMI\Manual\REG
ManualXMLPath=\Storage Card\SASHIMI\Manual\XML
ManualRootPath=\Storage Card\SASHIMI\Manual\Root
ManualEXEPath=\Storage Card\SASHIMI\Manual\EXE
ManualMSCRPath=\Storage Card\SASHIMI\Manual\Scripts
AdditionalCabPath=\Storage Card
AdditionalREGPath=\Storage Card
AdditionalXMLPath=\Storage Card
AdditionalEXEPath=\Storage Card
AdditionalMSCRPath=\Storage Card
AdditionalRootPath=\Storage Card
AutoCabPath=\Storage Card\SASHIMI\Auto\CAB
AutoRegPath=\Storage Card\SASHIMI\Auto\REG
AutoXMLPath=\Storage Card\SASHIMI\Auto\XML
AutoRootPath=\Storage Card\SASHIMI\Auto\Root
AutoEXEPath=\Storage Card\SASHIMI\Auto\EXE
AutoMSCRPath=\Storage Card\SASHIMI\Auto\Scripts
[Settings]
UCEnabled=1

Any thoughts?

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Whoa...ok you have alot going on there and I don't think all your tests are quite valid.

On #1 - This may be a problem with SASHIMI since the cab name starts with "sc" it might think it's a storage card install. I will look into that.

The rest of your tests don't seem to be from the same test, as they are dated 7 hours different.

The only possible way i can see #2 taking place is that at some point your Auto settings path was set to the \Storage Card\SASHIMI\Manual\CAB directory. I don't see another explanation for that log entry.

Also, there is obviously a provisioning file in that directory, as the log file shows specifically that it is using "AdvancedConfig_0409-nikagl-20080615-1500.xml'. SASHIMI can't make that stuff up...that XML file was there...so it got provisioned.

The other things you state also seem out of whack...but your setting.ini file seems to look ok.

Did you maybe flash a ROM with a different language? So the storage card is called something different?

I can only suggest you delete the settings.ini file and let SASHIMI recreate it (manually, or restore defaults inside SASHIMI). It looks pretty much like a default file you posted, but I can't be sure that was the way it looked when those installs actually took place, or if those were the proper names of the locations on your device at the time.

I have never seen nor had these issues reported before.

So, in short #1 may be a SASHIMI issue, the rest, I have to say is probably some sort of user/configuration error. I don't know what version you are using... and I don't think anything this major could have broken or there would be more reports.

oh and as far as the out of space issue... it actually calculates to make sure there is at least 4x the size of the CAB to install. So if a CAB is large...let's say 10MB... there would have to be 40MB in the destination, this is because most CABs are compressed 1.5-4.0x times the actual installation size.

If all else fails i would try to do a full SASHIMI re-install, although I can't see how that would help anymore then deleting the settings.ini file.

If you can't find the issue after all that, make sure you report everything...your ROM, etc. Also post the actual settings.ini file and I will flash that ROM and test with that ini file.

I'll eat my hat if it's a bug though (except #1)...I think you're overlooking something.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JMaxMan:
I guess my question is what determines where the cab files gets installed if you put it in the auto folder.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nikagl:
Hi JMaxMan,

Put them in the SC folder under CAB and it will get installed to the Storage Card...

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JMaxMan:
Thanks, Now I feel so stupid... I was wondering what the folder was
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nikagl:
Lol! If you feel stupid - check the manual first (RTFM = Read the Fabulous Manual ;)) before asking :P
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Nikagl,

Let me know how things look after you tried the above advice for the issues you have.

I might try to get another beta out this weekend, and need to know if there are any real issues there (apart from #1).

thx
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kareeem:
bengalih, you have done a PHENOMENAL job with this program. The videos were amazing!! You reminded me of the people that unbox the tilt from some sites for some reason. Just a quick question, i changed my default directory to storage card>cab instead of the sashimi one; if i want program to be on the SC, do i just create an SC folder there?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nikagl:
Lol, start practising your jaws then ;)

You are right about the times. Issues 2 was caused before issue 1 (I numbered 1 first because I had the feeling it was easier than 2 and 3).

Here's the exact order of what happened:

1. Originally I had a CABS and COPY folder on my card in which I saved all my cab and manually copied files for reinstalls - I used UC to install most of it

2. When I started testing SASHIMI I moved all cabs that I want to automatically install to the Auto\CAB folder (including some subfolders) - that worked fine expect for Schap's Configuration Tool, quite sure it's a bug - for the mean time I'll rename the file :)

3. Then I moved all my other CABS (+ readme's, some exe's, etc., etc.) to the Manual\CAB folder - from that moment on I would need the CABS folder anymore :)

4. I also moved some of the manually installed/copied files to the Auto\Root folder, the rest of the COPY folder I moved to the Manual\Root folder

5. Then I did the first test-run - I did a Manual+Auto run, but it took so long for loading the Manual list, I did a soft-reset

6. After restarting the phone + SASHIMI I started the Auto run - it started to also install the CABS in the Manual folder and tried to read the xml-files which are ALSO in the Manual\CAB folder! I did a hard-reset, as I wanted to have a clean machine without the invalid installed cab-files

7. After hard-reset I first moved the Manual\CAB folder to the root of the storage card and renamed it to OldCABS. I then tried another Auto Run. It worked well, just gave me the errors of insufficient space - but again, there's more than enough space on the device - the reason it generated that error is 99.9% because it couldn't find the cab in the Manual\CAB location

The main question is: Where does it "remember" what files it finds in the folders? Somehow it remembered the old location even after a hardreset...

I'll PM you the entire log (with some comments in it) so you can see what happened.

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] licht77:
Hi bengalih! Sorry - i didnt want to offend you in any way... there is a misunderstanding: not your great app is "annoying and time-intesive" but finding out all the registrykeys of my installed applications :)

And for the example with thinstall: of course this has nothing to do with your application - it was just a kindly ment idea/suggestion for you (comparing the registry before and after an installation to make an diff and find out what has changed)...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nikagl:
Two tips:

1. I use SASHIMI to export the registry and compare the two with UltraEdit + UltraCompare Lite and copy/paste the needed keys

2. You can export the settings you created with AdvancedConfig into a file with one program:

http://xdaforums.com/showthread.php?t=371828

Good luck!

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bsw11:
Suggestion

Hi - I abs LOVE this program!!

I have one suggestion that I think would be great to add:

Have a top menu mode called Auto as Manual which runs the AUTO folder just like you normally run the Manual folder.

I find at times certain installs screw up and I normally have to rename the 2 folders to make that work. This way its just a click and its done.

Thanks again! You have made flashing MUCH more fun!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
I think that's a good idea. Especially for people new to sashimi. There were a few programs that required manual input, and I didn't realize it until after some troubleshooting.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I actually see this as adding to the confusion that some would experience.

I will consider it...but am not quite sure.

In the meantime of course you have two options (within SASHIMI):

Change your Manual locations to the same as the Auto locations, this way when running Manual, everything in the Auto location is available.

Use Manual to do the one-off or alternate location. SASHIMI will remember the alternate location directory so installing a bunch of CABS this way should be pretty quick.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Ok, well first off, so we are on the same page I agree that the schaps issue was/is probably a bug. Any CAB that begins with "sc" might exhibit this behavior. I am definitely going to test/fix that.

What you are showing elsewhere is contrary to any test I have run with SASHIMI. In fact, if SASHIMI did this under normal operation then I would expect everyone would be reporting this because SASHIMI would not be working as advertised!

I am not denying that this happened, however it doesn't seem that your testing was very thorough, nor have you followed any additional instructions (or at least not reported the results).

As I suggested you should delete the settings.ini file completely. If that doesn't work you should delete and then re-install SASHIMI (and the directory structure) and see if this is recreated.

Did SASHIMI crash or abnormally exit during any of these installations?

The only other thing I can think of is to look for a file called TempSortFile.ini in the \bin directory. This file is created during the enumeration process, but should be deleted once the CAB files are installed.

Looking quickly at my code it appears that it is possible that a TempSortFile.ini from a previous install might be used in a future install if SASHIMI terminates improperly. From practice I have not seen this happen, and it isn't something that should keep happening as the file should be deleted each run.

I can't recreate this scenario. If you do a reinstall and can't recreate it either, then I would have to write it off to something being corrupt. If you CAN recreate it again, I would like as stated previously to have:

1) ROM used

2) SASHIMI ver used

3) Copy of settings.ini file

4) Detailed explanation of how to recreate.

When I do the next version I will do some more testing to try to get these abnormal results. I may put in another line of code to ensure the temp file is deleted at run time too....if that is what it turns out to be.

thanks for the feedback.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I'm not harboring a grudge here... however if I were to let's say take a snapshot of a device. Then, install a CAB and take an after-shot. Then I compare the differences from before and after. Let's say I find 10 files and 25 registry entries that have changed. So, I decide to somehow package those changes into a file. Guess what I would have? THE ORIGINAL CAB FILE that I installed!

Seriously, that is exactly what a CAB file is. CAB files are very simple in that they are just a collection of files and REG changes. So a CAB file basically is an application snapshot file, moreso then a standard windows application.

If for instance you also wanted to customize an installation by adding a few more registry keys that is exactly what SASHIMI allows you to do with tandem/bundled files (for one example).

From your original comments it seems that you really didn't take the time to fully look at what SASHIMI is capable of. If you do I think you will find it basically can deliver a great deal of what you are talking about through slightly different methods.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nikagl:
Hi Bengalih,

Thanks for your detailed responses! From the KaiserTweak and AdvancedConfig threads I know how much time it takes.

I'll try to recreate the issue soon, I'm struggling with getting the current ROM (a veryvery lite version) going the way I like which takes a little more time than expected. I am quite sure it was caused by the TempSortFile.ini file, because I cancelled the Manual job (see step 5) when it took too long (more than 5 minutes)!! My advice would be to delete the TempSortFile.ini every time the user starts SASHIMI and you'll avoid this happening again...

Did someone also try installing many cabs when not docked? For me it takes almost 30 minutes when it's installed and my phone turns off when doing that (if it's not docked). I have turned off all Power and Backlight options, but it's still turning off. Is there a way to force the phone to stay on (other than docking it or touching it every few minutes)?

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I don't think just cancelling the Manual job will cause the file to remain...but I am going to do more testing and better control the possibility of the file staying around....

Also, the beta version that is posted a couple pages back has the IdleResetTimer command built-in which will prevent the phone from turning off during long, undocked installs.

EDIT:

The more tests I am doing (and reviewing of my code), the less I think this could be a temp file issue. As I can't get the temp file to stay around even if I try to force it. So, until one of us can recreate the issue (and list steps to recreate), I am not going to obsess about it.

The only slightly similar thing I have seen when testing (and this was with older versions, i don't know if it still does it), is that if the directory it is looking for doesn't exist, sometimes it would attempt to scan the entire root structure and install everything... but that doesn't seem like what is going on either. In any event, let me know what any future tests you do yield.

thx.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nikagl:
Hi Bengalih,

First of all my utmost apologies - I had not seen there is a beta in one of the posts! My advice would be to either add a beta to the 1st post, or add a link to the post containing the latest beta (and include a disclaimer for beta users "for your risk only!"). Also, remove older versions of the beta's (for instance 6.1) to avoid people downloading an older version.

I'll try to reproduce with the beta - with the non-beta (6.0) it's simple: while it's loading the manual list (which needs to be long to be able to do it), press the softreset button and do an auto/manual install - it will install the manual cabs too that had already been listed before the softreset.

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
The beta won't matter with those issues, it will have the same results. The beta really only fixes some Storage Card installs in specific scenarios.

Also, I appreciate you putting SASHIMI in your sig, but you may want to fix the link so it links to the main page instead of your post.

thx.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nikagl:
Oops - changed it ! :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mb:
I know I'm dumb...

... but I was under the impression that if you specified to install Sashimi to the Storage Card, it would then automatically presume that all your install files would then be taken from the Storage Card!

I couldn't work out why this software wasn't working for me, then I realised that it was pointing to the install directories in the phone memory. A change of location to the Storage Card, and bingo - it all works fine.

Can a future option prompt you to ask if you would like your default location to be the Storage Card, rather than manually changing all the settings?

Or should it already do this? Great piece of software though, real time saver!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I'm not sure what exactly you are saying the issue is.

If you install SASHIMI to the storage card, then it creates it's directory structure ON the storage card. Meaning you would have:

\Storage Card\SASHIMI\Auto\CAB

\Storage Card\SASHIMI\Auto\REG

...

\Storage Card\SASHIMI\Manual\CAB

\Storage Card\SASHIMI\Manual\REG

and so on....

By default, the settings for the install paths (as far as WHERE to look for the files to install) are those directories listed above, which ARE on the storage card.

As far as the default INSTALL location for CABs, yes they install to the phone device memory by default unless you place them in the \CAB\SC directories.

You shouldn't even have any SASHIMI directories in the phone memory,

unless you installed it to the phone memory at some point.

If what you are saying is that you installed SASHIMI to the storage card and yet it is looking to the phone memory for the CAB, REG, XML directories or so forth then something isn't right.

Either you installed it incorrectly, are confused by something, or you are installing it on a device that may have something our of the ordinary (e.g. something other than a Kaiser/Tilt) which SASHIMI may not have been fully tested on.

The youtube videos show the basic operation after a default install, and no one else has reported this problem (and I have not seen anything close), so I think you might be confused as to the proper/initial setup.

You might want to do a fresh install and/or review the documentation.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Dr. Strangelove:
Hi guys, Bengalih,

I have recently flashed a new ROM (Garmin's DK2) and decided to use Sashimi to reinstall it after seeing the vids on Youtube.

But I can't get Sashimi to work fully. I run everything in Auto mode. CABs that need user interaction are installed first, using UC (not through Sashimi, but with first boot). After a reset I manually initialize Sashimi by running Sashimi from the 2577 folder.

Sashimi than starts with the CABs that are installed to the main memory. All goes well. But when it starts installing the CABs that need to be installed to my Storage Card, things start going wrong. Some CABs install, others don't. But there is no logic.

I have included some log files:

- Log1: run with standard Sashimi v6.0

- Log2: reinstalled Sashimi and only included CABs that neede to be instaled to my SC. Strangely, when isolated, all CABs install well.

- Log3: further testing

- Log4: further testing using Sashimi's v6.1.1 beta. Logs 3 installations, with a hard-reset between every install.

Notice how there sometimes a CAB gets installed, and other times it don't. It also says the REG and XML files are installed, but I can confirm this is NOT true. Same goes for the ROOT files, which are NOT copied.

I have not included my settings.ini, since it's the default one.

When manually seperate the automated installations (run Sashimi multiple times, filling only a folder at a time with the files that need to be installed), all seems to go well (as can be proved by log2).

Some CABs that need to be installed to the SC fail after trying to install, others fail instantly. One CAB doens't install because of a lack of space, but that's normal. Don't mind that CAB.

Hopefully someone can assist me, 'cause I would love to use Sashimi. This would make my life so much easier.

Thanks in advance

(and for the wonderful app)