yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aadadams:
Me too. Still salivating... I am going to flash one of the new HTC stripped down versions to play with this. I hope to be able to export my personal info and etc. to get up to speed quickly. I anticipate this is going to be the best app of 2008...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Thanks for your support... I'll give you a heads up to get the customization file ready so you will be able to use it when it comes out.

SASHIMI 3.0 will use a file called regexport.ini in the \bin directory.

Create this file as a normal text file of the following format:

[MySettings]
RegExportDirMode = Manual
key1 = HKCU\

The first field (the section header) "MySettings" can be called whatever you want. It must be enclosed in brackets like in my example. This is the name of the .reg file that will get created.

The second field "RegExportDirMode" should be set to either "Manual" or "Auto". This controls where the file gets created. If Manual, it goes into the \manual\reg\export directory, if Auto it goes \auto\reg\export.

The next field is the regkey you want to export. In my example I used HKCU\ so it will export the entire HKCU subtree. You can add additional lines after this in the format name = key. The name can actually be anything you want, it doesn't matter, but to keep it simple you should probably just keep on like key1, key2,...key23, etc. and the key is the location you want to export.

Here is another example

[MySettings]
RegExportDirMode = Manual
key1 = HKCU\

[MySoftware]
RegExportDirMode = Auto
key1 = HKLM\Software\
gobbledegook = HKLM\Apps\

This example will create two files, MySettings.REG in the manual directory and MySoftware.REG in the auto directory. Each file will contain the keys listed in it's section. Then, when you run SASHIMI to install it will prompt you for the manual .REG keys and automatically install the autos...just like previously.

I hope this meets the needs expressed in previous posts. It takes a few minutes to build the file, but it is easy and modular. Of course SASHIMI will allow you to also do a full reg export, backup, and restore too but you need to be careful when restoring backups between ROMS (nothing new there)!.

It should be up by tomorrow, but maybe I'll get it up later tonight.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aadadams:
Sounds great... Can't wait...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
3.0 is available. Check the first post :)

enjoy!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] aadadams:
Finally back from being MIA. Work was a PITA today. I will download and try it soon... but I think I need a nap first.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] myv6mustang:
Hey bro, Im a frequent flasher and been looking for a program like this. It works good but my auto install folder doesnt work. Im sure thats something on my end so i will keep trying.

what i really wanted to ask and whats been a problem for me is registration. is there a way to install a program and then have your program copy the registration files needed to get the program started so that when i install a program its ready to use without entering registration codes? sry if this is a stupid question just trying to find a way to shorten the time it takes to get up and running
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
hey. Well, I haven't heard about a problem with the auto install folder before. However, some .CABs may now work in silent mode. If an app needs manual interaction to install then it may not work in auto mode. This is true for any type of automatic installer, Tiered, UC, and so on.

As far as copying registration info...there are a few ways to do this. If it's files, then you want to place these in an appropriate subfolder of \root and it will be copied to the proper location. If it is a registry entry you can use the .REG or .XML options, or write a mortscript to populate the info.

I would really suggest going through the sample install and tutorial I posted. It will only take about 10 minutes and will get you familiar with almost all the features of the program.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] myv6mustang:
Ill give it a shot...with the update. Just wonder but will mess around with it a bit more and see what i can find thanks for the response.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
If you still have a problem afterwards please give me a specific description of your problem and post or PM me the log file.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] a2k:
Tandem Custom Installs...

Bengalih, great work on Sashimi, thank you!

I do have a question...

I would like the option of installing say what I would like to have listed as XYZ Suite.

The XYZ Suite script will in essence install two applications then run any associated .registry files. Currently it I have these apps in the manual directory and it asks me to install app1 with associated app1.reg, then app2 with associated app2.reg then I would need to manually install a third .reg file to customize both apps.

Could you please show me how to write a small script which does the following...

1. Installs app1.

2. Installs app1.reg upon completion app1 installation.

3. Installs app2.

4. Installs app2.reg upon completion app2 installation.

5. Executes customization.reg upon completion of all of the above.

Many Thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
If I understand you correctly, I think the easiest thing to do is this:

\Manual\CAB\App1.cab

\Manual\CAB\App1.reg

\Manual\CAB\App2.cab

\Manual\CAB\App2.reg

\Manual\REG\App1and2.reg

This way you will be prompted to install App1 and then App2, each one will install the tandem .reg file in the the CAB directory. Then in the next part of the manual phase it will ask you to install the App1and2.reg from the REG directory.

If you don't want to be prompted, you can change all those Manual directories to Auto and it should do the same thing....I'm not sure what else you are looking for...?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] a2k:
This is exactly what I would like to do, but be able to launch it from a script file please :-)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I saw your post over in the Mortscript forum...probably best to keep it there as you aren't asking about SASHIMI functionality, but rather how to write your own installation script.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Version 3.5 input...

I am working on the next version (3.5 unless the feature set gets dramtically expanded...then maybe 4.0 ;) ).

Currently the two major additions are:

1)

Auto Storage Card install

- this any cabs placed in \Auto\CABS\SC will be auto installed to the Storage Card instead of main memory. I have had pretty good success getting this to work, although most CABS that normally would require interaction will still need to be done in the Manual Phase.

2)

File/Directory Backup

- based on v3patel's suggestion. This will use a file similar to v3's regexport.ini, but this file will define file's and folders (and optionally subfolders) that you can choose to backup from main memory to either \Manual\Root or \Auto\Root for restoration during a future installation.

If there are any specifics that you would like to see implemented in the above features, or additional feature requests, please let me know.

We're probably looking at about 7-10 days until next release depending on additional requests.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] overhaulengines:
pim back up

hello bengilih,

is there a way to get pim back up to load using your program? i know it has many steps,

thanks

Lupe
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
SASHIMI 6.5beta is Here!

​

6.5b uses the latest (beta) version of Mortscript. I recommend that you perform a full upgrade to your previous versions.

For the full change log and to download check out the first post.

If you want a quick peek, take a look at the videos on the first post. Video #9 shows new features.

Please provide feedback. I haven't done full regression testing, so you might find some new bugs, but it should be pretty darn stable.

I am most interested in feedback from Diamond (or other VGA) users. I would like to know if it properly detects Internal Storage and if the AutoInstall to Storage Card properly works to install to Internal storage.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] TheChampJT:
Great work! I just hard reset, so I will be trying the new beta on my Touch here shortly.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
Fantastic work - thanks for the update!!!

One of the biggest challenges that I have not yet mastered using SASHIMI is probably the custom reg export that allows me to export my "registered" apps and then import the reg keys after a new flash so that I do not have to re-enter all my registration details again! e.g. I have all of SPB's apps (SPB Finance, Mobile Shell, Phone Suite, Backup, Wallet etc). I've created a regexport.ini file, done the export/import and was rather disappointed that all my apps were not registered at all after a cold reset. Any ideas on how to do this successfully? What am I missing out in the process?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I would guess that you aren't properly locating the registry keys that need to be backed up. Applications don't always store their registration info in the same location that the other application settings are.

For instance, I installed SPB Weather, exported the registry, registered it, and then exported the registry again. I then compared the two registries and found the following key had changed:

The XXXXXXXX was my entered registration key (not shown for security reasons). When I deleted that entry the application was no longer registered. When I added it back with SASHIMI the program was registered again.

So, make sure you know where a program holds its registration info. This is usually in the registry, but can also be in key files or sometimes it's built into the .EXE itself and the whole file needs to be restored.

Usually, the quickest way to do this is to just do a registry search for the entered Registration code. If you don't find it this way, you may need to do full before/after exports and compare as in my example.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
Cool, thanks for that quick response and detailed explanation!!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KukurikU:
one of the "must have" software for the flash addicts!

i am impressed. i watched yr videos....man, when you do something, you are going all the way :) the full 9 yards

thank you, thank you and ...R E S P E C T! !

going to start preparing my next restore!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
In addition, not all programs store registration information in the registry. The example that comes to mind is Opera 8.65, which stores the information in the windows directory. I found it after registering the program and then checking for newly changed files by sorting by date.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] racerx_:
Love the new beta! and I can confirm its working on the Diamond, with installation to internal storage.

the only thing i can see that's not perfect (but its really not a big deal) is when cabs, etc, with long filenames are installing the filename doesn't word wrap, but goes off the screen.

There's 2 things i'm wondering about..

1) is there any way to have it setup where the device doesn't automatically turn off while doing an install to storage card/internal storage... for other things sashimi seems to keep the device awake, but for storage card install looks like sashimi is not in charge..

2) I tried to put my pim.vol file in the root directory so it would restore (also contains our photo contact favorites for TouchFlo3D which is a pain to restore manually) but it doesn't seem to restore. Am i doing something wrong, or maybe SASHIMI doesn't have permission to touch that file?

thanks for the AWESOME app!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Great... thanks for that confirmation. It's hard to test for sure when I don't own a Diamond!

Yeah...that is annoying. It does wrap, but only if there is a space. So if it is really long it will get cut off, but if the path or file name has a space, it will break there. This is a Mortscript problem, and nothing I can really do to fix it. I might try to post in the Mort forums and see if its something he can fix. The old dialog system used standard "Message" commands to show the status... but I can be a little more accurate with the new Status Dialog screens...I also think it is more professional looking.

I could of course only show the file name...and not the whole path. That would fit more on the screen, but I thought people would want to know the full path. Maybe I can put an option to choose which way...full path..or just file name...

Hmm...you might be right here...I need to look at the code. I put in the IdleTimerReset for the CAB installs, but I think there is a separate code piece for the SC installs. If so I will add it in there too.

Well, I don't think it is SASHIMI specific.. but I do think that file is either locked down or possibly set to read-only/system. I don't really know the specifics, but I would gather that a program like PIM backup would be more capable of handling the specifics of PIM backup (obviously ;)) than SASHIMI.

Maybe you can do some tests to see if the problem is read-only? I am pretty sure that if MortScript tries to xcopy over a file and the destination is read-only then it doesn't copy. Because xcopy works on a whole directory, I can't really enumerate the destination files and remove the read-only attributes. Maybe I can find another way. Worst case scenario, another script can be written and executed to copy over any pain files, while removing any attribute settings.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
Maybe I missed this in the documentation guys, please pardon me, but can I use wild cards in the regexport.ini file similar to the new functionality that the customlnk.ini file has now, based on new Mortscript features?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] racerx_:
thanks for the replies.. yeah the thing is PIM backup restores certain data, but not the entire contents of the PIM file (cause the program hasn't been updated) which now contains photo contact favorites for TF3D (not the end of the world, but a real pain to restore manually after each flash)

It'd be interesting to see if SASHIMI could overwrite this file.. currently the program that i know is capable of it is Total Commander, so it is possible.. just something about how it treats that file i guess..
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Do you know if there is a manual procedure for backing up/restoring the file?

If so, can you link me to it?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
No...and based on the limitations of the 3rd party application that actually performs the export...it probably never will.

EDIT:

However, realize the the regexport.ini exports the entire subkey specified. So:

HKLM\Software\Programs

Will export everything under programs.... this is in effect a "full" wildcard. What it does not support is "partial" wildcards like:

HKLM\Software\Programs\SPB*

:)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nikagl:
I've installed and tested the new beta. Other than an error that it wasn't able to overwrite the original icon file when creating the new shortcuts, it runs SUPERBLY! Much faster (guess also thanks to newer version of Mortscript) and I love the new progress indication/onscreen-logging!!

Thanks Bengalih!!

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
OK, thanks. I was more thinking along the lines of a partial wildcard indeed like:

HKCR\CLSID\{A*
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Heh...yeah that's an issue that has been around for a few versions... ocassionally those files get set to read-only somehow and they dont' like it when you try to overwrite them. I never really bothered to fix it... but I actually finally did after I released this beta. So, the official release won't have that issue!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] racerx_:
yeah the only manual way i've found to do it is with total commander. other file explorers aren't allowed to overwrite that file. Not sure what total commander's secret is ha.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I messed around with this for a couple of minutes. What I found is this:

PIM.VOL can apparently be

copied

without a problem using most any method.

Overwriting/Deleting the file cannot be done...even with Total Commander. I tried right after a clean reboot as well on a fresh stock ROM, to minimize what can be locking it down.

By reading some other threads the solution I found was to rename the file. So, if I rename PIM.VOL to PIM.OLD I can then copy back the original PIM.VOL. After the device is reset it seems to be using the copied file and then the original (now PIM.OLD) can be deleted.

So, backup shouldn't be an issue...and should be able to be accomplished just using filebackup.ini. Restore seems to require a reboot, so I'm not sure that SASHIMI is the best tool to try and automate this.

From my understanding, the reason application like PIM backup can work is that they use APIs that can access the contents of the file while it is locked down. So they can open a stream to read/write into the file by the API, but they themselves do not actually backup and restore the file at the file-system level.

I suppose I can add in a tool to "restore" the PIM.VOL by automating the rename/copy and then prompting for a reboot.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
pim.vol

Has anyone tried copying this file with UC? I remember successffully doing this on UC many moons ago, but am getting an error when I test it now:

It's not an issue for me, I was just wondering if I could get the PIM.VOL file to copy using UC:

Lock:enabled
cpy1:\Storage Card\pim.vol
cpy2:\pim.vol
Lock:disabled

I use DCD ROM, but I disabled UC cause I no longer use it. So if it hasn't been tried, it may work.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ich.net:
little Bug in SASHIMI 6

Found in "Registry Tools">"Custom Export":

If you choose to skip a registry-export it's skips more than this registry-export, at least if there are entries in regexport.ini which haven't been exported yet.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Nice catch. Thanks. I was forgetting to reset the "skip" flag after each section. Fixed for official release.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] CLHatch:
I have Owner Info routines if you want to use them...

I just got this working in my own script yesterday, no need for XML files or anything... Should also handle any Unicode characters. I have not used SASHIMI, but thought it might come in handy for it also.

Main routines are GetOwnerInfo, SaveOwnerInfo, GetOwnerNotes, and SaveOwnerNotes. They handle the maximum lengths of each field, and truncate the strings as needed. Also allows the option of setting the "Show info on boot", and "Show notes on boot", which is actually a flag at the end of the binary registry entry.

They can be used as follows:

#Below at the start of your script
Include( "Owner_Info_Subs.mscr" )
Call( "InitOwnerInfo" )

#Below anywhere else
CallFunction( "GetOwnerInfo", OwnerInfo )
OwnerInfo["Name"] = "The Wizard"
OwnerInfo["Address"] = "123 Yellow Brick Road^NL^Wonderland, OZ 0000-0000"
OwnerInfo["Show"] = OWNER_INFO_SHOW
CallFunction( "SaveOwnerInfo", OwnerInfo, OwnerInfo )

OwnerNotes = Map( \
"Notes", "Follow the yellow brick road!", \
"Show", OWNER_INFO_NOSHOW \
)
CallFunction( "SaveOwnerNotes", OwnerNotes, OwnerNotes )

InitOwnerInfo defines some needed variables, including two constants, OWNER_INFO_SHOW, and OWNER_INFO_NOSHOW... in the above example, the owner info would be shown on booting, the owner notes would not.

Of course, it doesn't care how you make the array... second example I used Map. Occurs to me these could actually be read from a text file also, but you would have to be sure you don't get extra linesfeeds at the end, as they would be stored in the registry also.

Any part of the information that is not defined will be cleared in the registry, so if you only want to change some of the information, fill an array with GetOwnerInfo first, then make your changes to the array, and do a SaveOwnerInfo with the same array. SaveOwnerInfo calls GetOwnerInfo at the end, and returns the string array back so you'll see exactly what was stored (say, if the strings passed were too long and were truncated).

The array elements are:

OwnerInfo["Name"]
OwnerInfo["Company"]
OwnerInfo["Address"]
OwnerInfo["Telephone"]
OwnerInfo["Email"]
OwnerInfo["Show"]

OwnerNotes["Notes"]
OwnerNotes["Show"]
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bilbobrian:
Excellent work, thanks for the hard work.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Thanks Hatch... that is some nice code.

However, SASHIMI currently uses SKtools via command-line options to export and import registry settings.

There is already an option in SASHIMI that will export the

HKEY_CURRENT_USER\ControlPanel\Owner\

key to a file called owner.reg

This backs up all the owner settings (Name, notes, etc..) and restores them flawlessly.

In addition, through the use of the regexport.ini file, users can define any key(s) to get exported into a Unicode .reg file for re-importation during a SASHIMI install phase.

Quickly looking at your code, I'm not sure it really does anything additional to what the current export/import option provides.

Since you don't use SASHIMI, you probably weren't aware of how it was functioning. But, since it calls a 3rd party app that can natively process the registry it works quickly and generally more accurately as it can be a pain to code around Mortscript to ensure 100% accurate registry import/export (what with all the nulls, unicode and such your coding reflects).

While code like yours shows it is possible to use Mortscript to handle a complicated registry function, it can be time consuming. Since there are thousands of registry keys and many may need complex coding to handle properly, I decided to leave most of the processing of it to SKTools. Especially since I never know which keys the user may want to export/import. I probably won't ever have SASHIMI handling the majority of registry operation natively for the above reasons.

Thanks for your contribution though, you should post it to the mortscript thread so that others can see a good example of how to handle this sort of operation.