yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] overhaulengines:
same problem is had with email settings, i had to remane .provxml to .xml, then worked perfect, you are going to love this app.

lupe
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] smuook:
Looks like great work bengalih... can't wait to try on my next flash. My hats off to you...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Ok thanks...will try to add support for provxml file extension in next release.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] v3patel:
Look like we need to backup all ini's before installing new version

I am not sure i installed new version 4.1 and I lost my regexport.ini gor replaced by new ini. Is it me or has any one faced the same issue?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
This is probably true. I did include the following disclaimer in the Installation/Readme included:

Since you are a contributor and longtime user, you probably didn't read the instructions :)

I will try to make those warnings more prevalent on future updates. I may also offer two cab files. One for new users, and one for upgraders...without all the sample files.

Part of the problem is that there are often new/changed directory structures and ini files, so I would normally recommend a full installation.

I can also try to set in the cab installer not to overwrite the exisiting files, or maybe I will offer it with a ".sample" extension so it won't overwrite.

Sorry...hope you can recover easily!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] v3patel:
not a problem to recover

it is not a problem for me to recover. May in your script you just like you are creating setting file you want to create rest of ini files

like add code below and then remove ini from cab

# Check if filebackup.ini file exists and read contents.
If (FileExists(filebackupINI) = 0)
INIWrite(filebackupINI,"FileSet1","FileBackupDirMode","Mannual")
INIWrite(filebackupINI,"FileSet1","file1","\My Documnets\My Pictures")
Endif
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] v3patel:
my working filebackup.ini sample

[FileSet1]
FileBackupDirMode=Auto
fold01=\AppToDate\*
fold02=\Windows\Start Menu\*
fold03=\Windows\StartUp\*
fold04=\Program Files\Chartcross\*
fold05=\Program Files\HButton\*
fold06=\Program Files\phoneAlarm\*
fold07=\Program Files\QuickMenu\*
fold08=\Program Files\rlToday\*
fold09=\Program Files\UltimateLaunch\*
file01=\Windows\animated.gif
file02=\Windows\cLaunch.dat
file03=\Windows\filedlgchg.cpl
file04=\Windows\gsgetfile.dll
file05=\Windows\Vip*.tsk
file06=\Windows\vip_main.lnk
file07=\Windows\WM5NewMenu.cpl
file08=\Windows\WM5NewMenu.exe
file09=\Windows\Fonts\arial.ttf
file10=\Windows\Fonts\arialbd.ttf
file11=\Windows\Fonts\arialbi.ttf
file12=\Windows\Fonts\ariali.ttf
file13=\Windows\Fonts\ariblk.ttf
file14=\Windows\Rings\hd-*.mp3
file15=\Windows\Rings\vip-*.mp3
file16=\pim.vol

Basically if you need to back up multiple files based on some search caiteria it is also possible. Look at the line "file15=\Windows\Rings\vip-*.mp3" this will back up all of my mp3 files in rings directory which start with "vip-"

One thing that must be kept in mind is key name must be unique eg fileo1, file01 must be unique if you have two line like

"file01=\Windows\Rings\vip-*.mp3

file01=\pim.vol" then it will only backup last file listed with same key in this case pim.vol
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I didn't test if wildcards like *.mp3 would work, so I'm glad it does.

However your example of \Window\Start Menu\ should not back up ALL subfolders. If that's the case, then all your folders up to Fold09 should be backing up subfolders too.

The proper syntax for backing up subfolders would be \Windows\Start Menu\* are you saying that this isn't working properly?

The methods I tested were 3 types:

Single file:

\Windows\Start Menu\file1.lnk

Single directory:

\Windows\Start Menu\

Directory including subdirectories:

\Windows\Start Menu\*

Are you saying this syntax is not working as intended?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] v3patel:
YES * needed to backup entire including sub folder

YES * needed to backup entire including sub folder. Some how it work on first try but may I was doing somthing wrong. I re-test and you are correct * needed to backup directory with sub folders.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Are you also sure that *.mp3 or another file extension works? I looked at my code and it doesn't appear that it would. So I am curious if it is actually working...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] v3patel:
yes *.mp3 worked

yes *.mp3 worked and is working for me
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Ok, one last thing to verify. Are you sure it is working to copy ONLY *.mp3 files? Meaning if you have both .mp3 and .txt files in the directory, only .MP3 files are being copied and not everything.

Briefly reviewing my code, I'm not seeing how it would work, as anything other than "" or "*" gets interpreted to *.* and would thus copy everything

thx.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JaxPilot:
Methodology Question

Here is my question. I have flashed several of Dutty's ROMS, and am comfortable with that process. I dabbled in UC, and got some fairly basic success with installing CABs that were required for me. The problem I have is that I am pretty unfamiliar with working with the registry.

Where I am getting confused, with SASHIMI (which is a great tool), is how to get specific stuff out of the registry. I am just really confused on the methodology to use for getting the relevant registry entries exported to package with the CABS. Can any one provide a step by step example for locating a program, locating the relevant registry files, getting them out and packaged with the cab files? For example - PocketBible, Expressmail, or something like that.

I don't know if I should just flash the new basic ROM, install each cab manually, do the registry compare, export the changes, and then just repeat it for all the stuff I need to install.

While this will be painful the first time, it should set me up well for future flashing.

Thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] laakness:
It's best to use a registry viewer on your phone to find the keys that you want to backup. For instance I have it exporting a few of the programs settings that I use.

Here is my regexport.ini file so far.

[SPBWeather]

RegExportDirMode = Manual

key1 = HKCU\Software\Spb Software House\Spb Weather

[PocketCMKeyboard]

RegExportDirMode = Manual

key1 = HKCU\Software\PocketCM

[RescoExplorer8]

RegExportDirMode = Manual

key1 = HKLM\Software\Resco\Explorer\Options

[Bandswitch]

RegExportDirMode = Manual

key1 = HKLM\Software\Daniel Herrero\Bandswitch

[OwnerInfo]

RegExportDirMode = Manual

key1 = HKCU\ControlPanel\Owner
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Right, what Laakness says is correct. There isn't a magic way to just get what you want out of the registry, it is a manual process.

Luckily the WM registry is no where near as cumbersome as the Windows registry, there are far fewer entries.

Generally almost all of your settings for a particular application will be under:

HKCU\software\program name

or

HKLM\software\program name

It is generally safe to export that location, reinstal your cab and then reimport that reg file (like with a tandem/bundled reg file).

Now of course applications can install things in other locations (like CLSIDs and file associations, etc), but these will generally get set back up when the cab is installed on the fresh device. Importing your old reg info over it will usually be safe and restore your settings.

Some applications (like SASHIMI :)) don't store all there info in the registry, but rather in configuration files. These files are generally in the application's directory, but may also be in \Windows. This is usually not the best practice, the only reason SASHIMI does it is that your registry get's removed after a clean flash...so SASHIMI can't look there!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] laakness:
bengalih,

I just started using this last night and it is working flawlessly for backing up. I have yet to restore but will try it this weekend. Going to take a Sprite image first and then clear the storage to give it a shot.

Thanks again on such a well thought out piece of restoration software.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Thanks... it was written to do the "install" part...the ""backup" was added later...so I don't suspect you'll have an issue with its bread and butter!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Yeah I just confirmed that this does not work as I initially thought (and documented)

*.mp3 will indeed backup all .mp3 files, but it

will also

backup all other files in the folder as well.

I will work at implementing the ability to backup just a certain file type as well...although I think this will involve a slight tweak of the filebackup.ini syntax to allow for all the available options.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
4.3(?) Currently in the works

Thanks to all using SASHIMI. The latest version had more than twice as many downloads in less than half the time of previous versions!

The next version of SASHIMI is being developed. Current improvement include:

- NEW! - Command-line arguments supported to allow direct run of file and registry backups and direct access of SASHIMI's sub-menus.

This can allows automated scheduling of backups via system notifications.

- UPDATED! – Dynamically read Storage Card name for use on localized ROMs or other devices which don’t reference name as "Storage Card."This should allow easy usage on WM devices other than Kaiser/Tilt (from 4.2

beta).

- UPDATED! – New icons, and shortcut creation subroutine with more dynamic code. Shortcuts for command-line quicklinks are also included!

- UPDATED! – Filebackup.ini syntax and subroutines to allow backup of wildcard file groups (e.g. *.mp3, *.jpg, etc...)

- UPDATED! – Updated error checking in code to deal with various program or system exceptions.

- UPDATED! – Installation routine. Now even easier to get SASHIMI up and running on a fresh install or new ROM.

For any bug reports/fixes or additional request please post here.

At this point I am looking at early next week unless significant requests come in.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] zard:
Using version 4.1 now. Really love it.

After facing on and off problems with WM 6.1 roms, when SIP cannot stick, I came upon this routine.

1. After rom flashed and SR, first I install Resco Explorer and registry add-on.

2. Install PCMKeyboard.

3. Install DefaultIM.

4. Select PCMKeyboard insdie DefaultIM.

5. SR.

6. Confirm PCMKeyboard sticks.

7. Install Sashimi v4.1.

8. Run Sashimi, Auto.

9. SR.

10. Run Sashimi, Manual.

11. PCMKeyboard is still working as default SIP.

One thing I suggest that could be implemented in the next version, for additional cab installation routine, could the 2nd time default back to last cab install location instead of going to default root directory? I tend to keep test cabs at a fixed location so it will make it even faster.

Thanks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
I doubt SASHIMI has anything to do with SIP sticking...the SIP routine up to and excluding SASHIMI installation works just fine in any case. There's something about cooked WM6.1 builds that just stuffs up SIPs not cooked in...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Yeah, SASHIMI should have nothing to do (good or bad) with anything else working properly. I assume you are just assuming the SIP stuff first to ensure that it is done manually to limit any possible problems?

When you ask about defaulting back to the additional CAB location do you mean for each cab chosen or on future SASHIMI runs?

It should go back to the same location if you were say...installing 5 cabs in a row with the additional cabs option. However that location would not be saved next time SASHIMI is run. Is this what you mean?

I should be able to implement in an extra ini setting to save this info.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] asango:
Starting Sashimi only after a cold boot or a newly flashed ROM?

Hi,

works perfectly, great tool, thanks a lot!

I only got one thing I did with UC and could not cover with Sashimi:

- Is it possible to somehow autostart Sashimi only after a *cold* reset or a newly flashed ROM?

Of course I could copy an lnk file during the sdconfig.txt UC stage to the Win startup folder which is calling Sashimi in autostart mode, but the problem ist that this would call Sashimi on every boot, which is of course not desired.

Then I tried to use the EXEC: command in sdconfig.txt but no luck:

EXEC:\Storage Card\SASHIMI\Bin\MortScript.exe \Storage Card\SASHIMI\SASHIMI.mscr

or anything like this (also without the script file as command line parameter)

always results in an error message during execution of the exec command which is stating that the file "storage " can not be found.

Must have something to do with a problem that sdautorun.exe is not capable of long filenames containing blanks (But only regarding the EXEC command. The CAB command is doing well with blanks in the directory name...).

I have tried all variations of putting it into " " or using short names, nothing is working. Seems to be a bug in at least the sdautorun.exe I'm having in my ROM (Mobile Vista 1.3 by Confused Stu).

So this is also not an option.

Is there any other way of starting Sashimi only once after a cold boot?

If this would be possible then a fully automated install after a cold boot or flashing the ROM would be possible the way I always did it with UC, with the difference that Sashimi is MUCH more comfortable...

(I saw some posts earlier that in V 4.3 you are intending to implement something related to this issue, maybe this will solve this problem?)

Thank you for any suggestions!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] axeman:
looks neat! its on my list of must haves now!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JeckyllHavok:
Boy you're genius.

It's one of the most usefull apps i ever got.

I flashe my rom very often because i like to try new ones and i ever spend a lot of time with customizing my device after(I think my girlfriend likes the app, too) :rolleyes:

But with Sashimi it's a dream..
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] m.zielinski:
Several things

Hi,

I just tried your beta 4.2 because my SD-Card is named different although i use an english rom.

Some Observations:

* The Exported REG-Files have an extra Backslash where the Path from the settings ends

e.g. \HKCU\Software\Resco\\something

I defined \HKCU\Software\Resco for the export

* i couldnt start the programm because i always get errors that show("desktop") doesnt work - after commenting out all those commands it worked fine.

* No way for Manual install going to SD-Card - maybe also in the Manual installation should be a SD-Folder

* Maybe an second "Root"-Folder would be fine because i also copied some files manually to there and to differ that from the backup-files-feature it would be nice to have a different folder for that ?

But still your Script is really great! its exactly what i needed for fast flashing and setting up again - GREAT JOB!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Thanks for the feedback! My comments are under your below:

Out of curiosity, why is your SD card named differently if you are running a TyTn II with english ROM? Did you change it yourself and if so why?

Registry imports/exports are done by a 3rd party tool. I only pass it the parameters from the regexport.ini file in the proper syntax. It puts in these extra slashes even when run manually. So, this is not something I can fix. However it works...anything you export it will import, so this isn't really an issue.

This is very interesting, especially since you use an English ROM. Basically this command is used to "minimize" everything else by showing the Today Screen/Desktop and is for cosmetic purposes only. Again, if you are using an English rom especially I don't know why it wouldn't be able to find this window. Can you tell me what ROM exactly you are using?

This I honestly don't think is necessary. If you are doing a manual install you are sitting there clicking on the CABS anyway, so it is easy enough to just install it to the SC yourself. I understand that you may want this because you still want to install some to SC and it may be easier to organize them to remember what goes where. However, because the auto SC install uses screen taps, it could be problematic with the user constantly hitting the screen (during Manual Phase). For now I don't think this is something I will change. If you want to organize the CABS, you could always just add "SC-" in front of them so you remember which ones you want to install to the SC.

SASHIMI wasn't designed to be a complete backup tool (although it has evolved to have those features!). I'm working under the assumption that everything people are backing up with SASHIMI is in order to restore it on a new flash. You can always backup/copy the files to the Manual location and then you are able to choose what to restore during the Manual Phase. However, I'll think about this and maybe provide some more directory options...

Thanks again for the input!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] asango:
Found a very simple solution

Hi bengalih,

thank you for taking my thoughts in consideration!

The reason I need a fully automated installation is simple and I think many people have the same "problem":

I'm testing a lot of different ROMs and also sometimes I need to flash several devices paralelly.

The problem is not the 5 seconds it takes to start the script, the problem is that after starting flashing -which is taking some minutes- I often forget to start the script which is also running another 15 Minutes or so after flashing has ended, because I'm doing other things inbetween.

And then when I get back to the devices to start working with them I find that I again forgot to start the scripts after flashing ended.

And this is more than tedious also for a lot of other people I would bet :D

But the good news is that I've already found a very simple solution meanwhile:

I wrote about the problem that the sdconfig command EXEC did not work with "Storage Card" or other names with blanks, so I simply did it this way:

LOCK:Enabled
HIDE:Disabled

CAB: \Storage Card\_install\cabs\MortScript-4.1-PPC.cab

CPY1:\Storage Card\shortcuts\sashimi.lnk
CPY2:\Windows\sashimi.lnk

LOCK:Disabled
HIDE:Enabled

EXEC:\Windows\sashimi.lnk

and the lnk file is simply calling your autorun.exe:

77#"Storage Card\SASHIMI\2577\autorun.exe"

If copying only the script to the "non blank named" win folder and calling this script instead of the lnk file in the EXEC command, this way one would not even have to create a lnk file, have not tried this, but it should also work.

This way I could do exactly what I needed and the whole process after kicking off the flashing procedure a fully restored and operational device is generated without one single click or any other manual interaction.

Exactly what I had with UC, but now much more convenient regarding flexibility with your Sashimi.

Yust because I'm curious:

Will the cab you're about to implement in the next version go beyond this functionality?

I would still need a sdconfig.txt for this as you wrote, right?

So what further advantages would your new solution provide?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Well I don't think there are that many people out there flashing multiple devices in parallel constantly and rebuilding ROMs at such a rate as this. Unless you are in some sort of production line system that I can't even fathom outside the factory, and then I'm sure you have better tools than SASHIMI.

That seems like a good solution, I don't see any major issues with it.

This won't work as the SASHIMI.mscr needs to be where it is with all the other folder underneath it. This is why shortcuts exist...you can't go moving around different parts of an application and still expect it to work! :)

Basically my solution will do the same. My UC Init cab adds the necessary MortScript entries, so you wouldn't need to also install the MortScript CAB (or rather you would use my cab instead). I also set up a link in the \Windows folder with a reg key check, so if you ever wanted to re-run SASHIMI at bootup you could delete the key and it would trigger again.

There really isn't any other "functionality" to "go beyond" with this as it is a simple task of just getting SASHIMI to run after a clean boot. You

will

still need an sdconfig.txt (unless you are going to cook it in). There is no other way to go about this, either the code to autorun needs to be cooked into the ROM's auto config procedures or else it needs to be triggered by something else that runs automatically. Since UC, as it's name implies, is the only customizable method that is also cooked into many ROMs, this would be the only way to setup additional configurations.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] asango:
Not really, seems that your Sashimi is more flexible than you think :) :

Since the 2577 directory and its contents can be moved to the SD root and still AutoRun.mscr in it is working I could not imagine that copying it to the Win folder and calling it from sdconfig.txt would not work.

But since you said it would not work I could not believe this and I tried it.

And as I expected it *does* work.

(Please note: I have not talked about ripping the SASHIMI.mscr out of the SASHIMI directory which of course would not work. The simple solution I wrote of is copying and calling the AutoRun.mscr from the Win directory)

Even if it's only one device I'm flashing several times to try out something or test some ROMs it's tedious to get back after flashing or cold booting and see that I'll have to wait another 10 or 15 minutes until I can go on simply because I've again forgotten to start the script manually.

Therefore I think I think this is reason enough and it's a very good idea that you'll take care of this issue in the next version, so thanks a lot for this and also Sashimi as a whole. Great work and looking forward to the next version(s)!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
That's right...the 2577 script can be moved and called from somewhere else, as it will always reference back to the SASHIMI directory. I misunderstood what you were moving.

I suppose this is an issue for the extremely impatient or forgetful...but since we came up with a few solutions I guess you're all set :)

thanks again for the feedback
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] v3patel:
New issues :

I just re-flshed with Dutty;s new rom.

Before I flashed I move 2577 one folder up

After flshign trying to run autorun.exe gets into error as it can not find Mortscript.exe in same directory

SO I went to SASHIMI folder and trying to execute sashami.mscr that also did not work as mortscript (.mscr) are not yet link to mortscripts

Solution I have to go to bin directory then run Mortscripts ones and then run any mscr.

May be for future release you want to move sashimi.mscr into to bin directory and then create shortcut to mscr in to main SASHIMI directory.