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

Please feel free to make suggestions/bug reports/feature enhancements.

I couldn't think of anything else it needed at the time, but I'm sure it's not perfect.

On my list so far is:

Add support to use XML provisioning files (in addition to REG). - Not sure if I will put this in both Manual AND Auto modes...thinking maybe just Auto.

Writeup instructions, and maybe a little update that shows/updates the program to run in UC/Autorun mode. - This will allow it to run in auto mode as soon as the SD card is placed in the device (or a new device is started for the first time with the SD in the slot).

Integrate a config.txt / sdconfig.txt file so those of you who run UC can easily move/switch between both apps. Basically the idea is SASHIMI will process the config.txt file in addition to what it already does. It is kind of repetitive, since then you would be able to either import an XML through my methods, or just put your XML/CPY/EXEC commands in the config.txt file. Obviously if you ONLY use config/sdconfig.txt then there really isn't a need to use SASHIMI too, but if you want the extra options while still maintaining any work you did with UC then it's a go!

I would like to try to keep the app aroung it's central purpose, which is as an installer automater/helper app...so try to keep suggestions/recommendations around that.

thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] overhaulengines:
better than uc, imho

thanks for you help bengalih, from your other thread, got my emails set up,

i used tiermanns Personal OEMizer to create my provisioning XML.

i then used the task manager you provided and bam, it worked:D:D.

this is why i believe SASHIMI is the best choice. i flash many roms, not all roms have the same programs installed, when i use uc i have to change my config.txt or i might install something that is already in the rom or i might miss something that is not in the rom. yea yea i know, cry me a river:)

heres what i like, i put my stuff in auto file, like my spb mobile, spb weather and a few others that no one installs because they must be purchased, then all my others in the "manual file" stuff like pcm keyboard, rss hub, htc end key, etc and google search which makes you stop and accept user agreement, if i have something in the manual file thats already installed in the rom you just flashed, just click no when it gets to it and on to the next cab.

i believe with sleuths uc if a cab requires a reboot it cant be used, for example i can put spb phone suite in manual and once completed it ask if i want to reboot, i select no and now it goes to the next cab, once im done with the cabs i want to install then i reboot:p very very nice

thanks

Lupe
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Thanks Lupe...glad you got it worked out.

I am finishing up the next version, which will incorporate UC as well, so if users have an sdconfig.txt file they want to use it can also be used by SASHIMI (in reality I am calling UC's SDAutorun.exe to do it). So, it will be like a combined installer.

There still isn't a substitute for UC in terms of cooking it into a ROM to run automatically on first boot, but with my next version you will be able to use the sdconfig.txt and you will also be able to initiaze SASHIMI when the storage card is inserted. This makes it ideal if you need to provision alot of phones and each one is slightly different.

It sounds like you are taking advantage of the manual+auto install...great. FYI if a .CAB is already unstalled, then the following will happen:

1) If in Manual mode, it will ask you to remove the old CAB first and then it will ask you the location to install the new one. Of course you can always skip the CAB in manual mode if you don't want to reinstall.

2) If in Auto mode it will automatically remove the CAB and install it again.

Ah, one last thing...the Task Manager is DotFred's task manager, I can't take the credit for that application, and I will be sure to credit him in the next release notes.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Version 3.0 coming soon.

I'm finishing up version 3.0 to be release by end of week.

Here are the following updates:

v.3.0

- XML integration added! Use XMLs with/instead of .REG files to provision your device.

- UC integration and the ability to use sdconfig.txt files.

- Option to auto-launch when Storage Card is inserted.

- Better Log handling and INTEGRATED log viewer.

- Additional menus for less clutter and more choices!

- More status dialogs to let you know what's happening when.

- Ability to create/restore Program Menu shortcuts to any location.

- \Scripts and \Root directories available in both Auto and Manual modes for more control!

- Moved tandem/bundled .REG processing before .CAB installation for the ability to import registry entries prior to application install. .MSCR and .XML tandem files process after .CAB installation.

- Optimized code formatting

Let me know if there are additional options you would like to see.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aadadams:
Does the SDConfig.txt file use eliminate the ability to use the programs default folder based way of separating and installing? The program is excellent as is. But if I were shooting for the moon I would suggest adding ability to export personal information to .XML or .REG from current device for use after flash...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] thehighlandway:
I completely agree with this. If you were able to have the tool create the .xml and/or .reg files from your currently installed ROM, it would make an excellent tool a killer app.

Thanks for the work!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
No, the SDConfig.txt file is an ADDITIONAL step in the Auto phase.

So, after running either the Auto, or Manual+Auto modes the last step will be to process an SDConfig.txt file if it exists AND the option to use UC is enabled within SASHIMI.

I think that answers your question.

I did also add the option to do a backup of the entire registry to a file. But, your suggestion gives me an idea....

I can't really provide an interface with MortScript to do a selective backup of the registry, but what I may be able to do is read another configuration file. So, the user would create a file with the following format:

Whatever keys are listed in the entries will be written out to a .REG file in the Manual\Reg directory and can then be imported if desired or moved to Auto\Reg.

Would that suffice for what you are asking?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aadadams:
That, my friend, would be EXCELLENT! This is an awesome application! Keep up the good work!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aadadams:
Thanks for everything, sir. I cannot wait to try this out.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Ok, I have implemented all the above features.

I just need to do a bit more testing and then repackage the .CAB and update the documentation.

Unless i get anymore feature requests/bug reports I will be upping this probably by Friday.

If any new feature requests are too complex (but worth doing) they may wait until next version.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
You can set the reg owner tag as a manual registry backup, and the dependent programs as auto. The manual systems run prior to the auto.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] zard:
bengalih,

Great job with version 4.6. Almost everything went well, especially your new feature of automating cabs to be installed on Storage Card (maybe already in previous version but I didn't realise it).

2 things to feedback:

1. When using Auto routine, the files under SC, went on well but I'm not sure how many cabs had been installed before it stopped at one of my cab where the screen request you to select to device or SC. I had to manually click on SC and it continued without any problem after that. No big deal.

2. I use Sashimi in this way, doing Auto, end it and running again, Manual. At the end of each installation, I received some prompt error, but sorry buddy, I didn't write down what the error message was, something like link not there or something, can't remember. I promise I will write it down the next time I use it. With this error popping up, Sashimi will not gracefully shutdown by prompting with countdown.

Very well, thank you for a great app. It's so powerful now but I still have not used all the features.

Thanks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] carphead:
I've just started using this in place of UC. I love it but I'm stuck on one thing (apart from being able to automate the registration codes for me apps but that's by the by). How can I automate entering the wifi/wireless keys?

There doesn't seem to be anything in the registry except the domain and dhcp information. I'd love to be able to take a snap shot of the various wireless networks I connect to and not have to remember or write down the keys.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] asango:
No, I have already tried this before.

Apparently any subfolder gets processed after the main folder, so it is possible to get some control by putting things that must be carried out late into a sub folder, but the different sub folders are again processed based on something else than alphabetical orders.

Yes, if an alphabetical order would be used everything would be perfect.

This is for example also done in BartPE Win auto installations and is THE standard method of having control over the installation process.

This would definitively solve all of these problems, thank you very much and looking forward to the implementation of this alpha order!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] zard:
How do you automate the registration codes for your apps? This would be very useful.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
The way the SC install works is by using automated screen taps. It is as if a ghost is using your device. This is the only way to really get Storage Card installs to work because of the new security on WM 6+ devices. In essence you can only do it manually...so what I did was let SASHIMI take control and "manually" do it for you. SASHIMI is the only installer I know of capable of installing to the Sotrage Card in any type of automated fashion. SASHIMI can deal with several issues that come up when doing an auto install to SC it knows how to automatically respoind to several prompts (like where to install or if it prompts you to remove a previous version, etc..). However some cabs may present dialogs during installation that SASHIMI can't handle. Because I need to manually code every interaction, I can't possibly account for every CAB out there.

As to why SASHIMI would stop responding with screen taps to the SC install routine I can only think of 2 reasons:

1) Something is on the screen that SASHIMI isn't expecting: As mentioned this could be a dialog from the CAB install, or if the screen is switched manually or automatically to a different window.

2) Some other program is interfering: This shouldn't be likely because SASHIMI is usually functioning before much else is installed on your device. However I found this to be an issue with other programs that access the display. Like when I was trying to take screenshots of the process, the application that does that was somehow interfering with the screen.

As stated in the docs, don't touch the device screen when SASHIMI is doing the SC install phase, or you may interfere with it's automated taps.

If you find this to be a continuing issue, or notice any pattern, let me know.

So it sounds like you are saying SASHIMI gives you an error after everytime you run it??

I don't think I've heard that one before. Please write down what the error message is so I can have a better idea.

thx.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Everything is in the registry. The trick is figuring out which location to export.

In some cases it might be easier to write a provisioning XML file to set up all the network connections.

Because this information is not really specific to SASHIMI, but rather to device provisioning in general, I don't have all the answers readily available.

I guarantee the answers have been posted previously elsewhere in the forums, or maybe another user here who does those can help.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
You can use a tandem/bundled REG file which puts the registration code into the registry.

read the documentation for info on bundling.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
ok. I will put this on the list for next version.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] carphead:
Thank you Bengalih. I got so focused on it being in the registry that I hadn't even thought about going via provisioning XML stupid of me really. A quick search lead me to this.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jdmba:
Almost There

Wow --- OK we now have:

1) CAB to reset to AT&T Connectivity Defaults

2) CAB to restore WiFi settings

Anyone know how to make a CAB to restore a POP3 email account set up in messaging?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] carphead:
I've not yet managed to build a CAB that works with wifi settings. But I've ended up using just the XML and I'll create one for each network I use and have a template one that I can just edit using Notepad.

Email can be done by XML as well see here. I've not tried POP3 but I know it works with IMAP as I've setup my fastmail account with it as well as my Exchange account.

I would assume that you can merge all the XML files into one and then create CAB for it but I think I'd prefer to keep them just as XML and run them automatically so if anything changes I can just edit the XML on the device directly.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] zard:
I left those cabs that gives additional prompts to the manual folder. The cabs under SC are straight forward cabs. Maybe too many cabs to handle....
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Well, I have tested only with about 15-20 CABS at a time with no issues. There is no reason that it couldn't handle as many. I would be interested if this was a repeatable event, and if so, if there was a particulare CAB file that it stopped on each time...or after a particular number.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] zard:
I tested twice with 2 different roms yesterday. It stopped at the same rom, which is a yahoogo version 3 cab. I need to help it out by selecting SC and then it continued. For the first rom, I can't remember how many cabs I need to help out by clicking SC but for 2nd rom, I remembered clearly that I needed to help another cab, spbtime2 and after that, everything went on smoothly.

As for the error message, I didn't get it anymore.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Ok, I downloaded and tried out the Yahoo cab and I see what the issue is. The cab names are so short that it throws the screen tap off. I had accounted for 2 and 3 line cab files, but not a single line. I will fix this in next update.

As far as the error messages, I will assume that there was something else going on at your end since no one else has reported them, and you can't recreate it. If they come back, please take note.

thx.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] herczyn:
true, but not what i meant.

my solution has to be implemented:

sashimi needs to ommit the first folder. i think it would be quite easy for you to implement and very helpful for all of us.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Actually, it's not a very logical method of copying entire files and folder structures.

And, since no one else has resonded to your original post, I'm betting that the functionality is not really something most people are interested in.

However, since it is so easy to implement, you can always write your own script to run from the \scripts directory to do what you like. :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
The new version of SASHIMI should be out shortly. The following are the enhancements to expect:

NEW! - Alphabetized processing of all files and folders for better control of installations.

NEW! - EXE paths and processing added to Install phases.

NEW! - Owner settings back-up option and automatic restore before install phase.

UPDATED! - Fixed issue with install to Storage Card routine for CAB files with very short names.

UPDATED! - File order processing. Registry files now get processed after CAB file installs.

UPDATED! - INI file processing to better deal with missing values for critical path variables.

UPDATED! - CAB installer updated to deal with non-standard Storage Card naming.

UPDATED! - Startup executable (VipMSCRexe) updated to 3.0

UPDATED! - Optimized code structure with reduced sub-routines for less code complexity

Please report back any additional bugs found in previous versions that are not addressed in the above change log asap.

thx
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
This is so exciting! I dare not even ask, what's the ETA? :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sdlopez83:
This program has simplified my life so. I can now flash or hard reset my phone while driving... It Is an essential utility that blows UC out of the water. Again benghali man for making my life easier.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
Please stop flashing and hard reseting while driving. You don't live in the DC area do you? If so what route do you take to work. I want to avoid it!!!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
5.0 is now available. Check first post.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
Fantastic!!!!!!! I just don't know what to say anymore but really when you follow the history of this app, see how active the developer is, the support he gives to users, and man oh man all I can say is great job Bengalih and thanks for this app and the frequent updates!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] :
wow, never seen this before :O

gonna test this thingy..
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
Oh oh, seems the auto process for SC install is checking device Main Memory again in this version instead of SD memory...I got an error message similar to the one I'd posted in post # 151...

Edit: might be an issue with my update process from v4.6 to v5.0. Let me do a clean install of SASHIMI and report back...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
should be ok...the code looks right.

let me know.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
Yeah, its working great! Thanks. You can't create staging sub-folders in the SC folder, can you? coz then its 2 folders deep? This is only possible currently under Manual process with the Manual\Cabs\Stage1\ syntax?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Yeah, currently sub folders fro CABs can only be created under \Manual\CAB and \Auto\CAB, since SC is a subfolder under \Auto, it is already one level deep, so you can't create any more folders underneath it.

however, all folders support alphabetizing now, so if you want to control their order, you can control it that way.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
4X Constraint under SCInstall Sub-Routine Error?

I'm getting an error about install location size being insufficient under the SC\ process and it refers to the Storage Device memory...I've checked the SASHIMI.mscr code and it seems to be the 4X STORAGE:CAB ratio constraint that's causing this error. The cab file I'm trying to install is about 60MB (free device memory at this stage is about 74MB) and even though it's supposed to install to SC the process fails here because the 4X constraint checks both device memory and SC...I'll try and change this constraint to 1X under the SCInstall subrountine and see if that goes through...do you think?

Edit: I used this amended script and SC install ran without a problem...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
You're right. Looking back at my code I check for free space in device memory before I check whether or not it is going to SC... so even if it is going to SC it is still constrained. This must have happened when I did some reorganizing of the code structure.

Changing it to just 1x will work...but only if what you are trying to install is no bigger than device memory. So...if you are trying to install something 80MB to the SC and device memory is only 70MB free it will fail.

Good catch, and something I will fix in the next release. I was planning on something quite different for the next release, but I think I will release an quicker update in the next few days which fixes this as well as a few other things.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jdmba:
Bengalih,

I have finally flashed to a different ROM and have, as such, tested Sashimi 5. I have noted the following:

1) SPB products always ask if you want to install as trial or registered. Sashimi defaults to trial. Does this mean that they must be added to manual instead? Is there a way to not automatically answer "install as trial" vs "install registered copy" in auto?

2) I thought registry entries were supposed to process first for some reason (e.g., to set the owner information BEFORE installation for programs; as this can have an effect on their registration). Registry entries were processed after CAB install. Perhaps we need two levels of registry entry processing - first, and then "whenever"?

Thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I can take a look at one of the SPB products to see how the install routine goes. However, if it asks anything during install then chances are you need to set it for Manual...since it requires user interaction. I'm pretty sure that I have installed SPB products before and have not been prompted. If you want to link me to one or two directly I can try them out.

As far as registry processing, in versions before 5, REG entries were processed FIRST. This meant that the .REG directory was processed before CABS and also tandem REG files were processed before installing the CAB. This was changed in version 5 because of feedback that if the REG is installed FIRST, then the CAB may overwrite the REG with default entires. This made more sense to me, so I changed REG processing to happen AFTER CAB install. This was in the change log AND in the documentation.

The only exception to this is that the OWNER information is alway set as the first step. This assumes you used the "Backup Owner" option in tools to create the owner.reg file. If that file exists it will always be the first thing during an install phase. That will set your Owner info so that any programs that require owner info will have it.

I really can't see the point now of having a REG install phase both before and after cab install. As long as the owner info is there the CABs should install no problem. If there is a REG key needed, there should be no problem with that being set AFTER install in the registry.

As always, if you can give me some good solid examples of why this doesn't work, and why both would be needed, I will consider it.

thx.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] carphead:
From what I understand when you install a registered install of a SPB product it puts a encrypted serial number into the registry of your device. When the CAB file finishes it then removes that encrypted serial number. I've tried to find the registry key without any luck.