yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
You should download the MortScript documentation so you can understand all the way to send key strokes. It is important if you want to automate everything with .AUTO files.

If you want to send me the .CAB or a link to the .CAB to download it, I can see what it is doing and try to help with the .AUTO file if I have the time.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] geistteufel:
in fact I make a Big package for a rom (additionnal auto install) for french user

so I have a set of cab installed in auto/cab and auto/cab/sc

I'm currently looking for the cab which make this full screen blocking message appear.

I send you a screen shot when I get it

I don't really know if auto can help in this case, cause if it's after installing bunch of tools ..

everything continue normally but in background ... we don't see the process anymore ...

ok I have found it !!!!

WeatherDatabaseEditor

I join the cab and screen shot
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Well, sorry to get your hopes up! :)

I was going over this again in my head and then looking at my code.

I ALREADY DO execute non-SC installs using the /silent (or /noui) switch.

So, basically SASHIMI

is

using the same load command that UC would use. The difference with UC is that the UC splash screen is on-top so you can't see all the windows that get opened up underneath...but they ARE there.

However I did implement a new line of code that will bring the SASHIMI Status dialog back to the front when screens display.

For instance, with google maps...after it installs it pops up a license agreement and then another "ok" screen. Those screens pop-up regardless if you do an interactive or silent install (SC or non-SC). But now they get hidden by SASHIMI in much the same way UC hides them.

They will be visible after SASHIMI is done, but just like UC if you have SASHIMI reboot, they will be gone after reboot (obviously!).

There ARE some CABs that can't be automated at all with basic SASHIMI and even UC. For example, the Citrix install (icasetup.arm.cab) will pop-up a license dialog that

must

be accepted manually. If you try to install this CAB with UC, UC will just hang because the license screen pops up in the background. Likewise SASHIMI will stop until you manually accept the agreement.

Again, the solution for you hardcore who must automate everything would be to use SASHIMI's .AUTO files.

So, with the next release, it should work closer to UC in that certain screens will still launch, but will get hidden by the SASHIMI status (much like UC splash screen hides everything). Remember this will be with

installs to memory only

! When you install to the Storage Card you still want to either CABS with basically no interaction. Remember UC doesn't even support SC install...at all...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] geistteufel:
ok thanks man

yeah I think just always on top status could solve lot's of problem

but in fact, actually, If I don't answer cancel to this question, SASHIMI don't continue their execution

so I don't know if a always on top is a good idea for that :) we will see
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
if it works the same, i'll just move the files to the auto install and not worry about it. they should work regardless of whether the screen is hidden. I'm not sure I see the benefit of hiding it.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] geistteufel:
the benefit is simple, it's for prevent user (not me :) ) to don't reboot or doing something work before SASHIMI do his task.

If an user don't see that process is running and doing thing, they can break it before the end.

I'm currently make additionnals tools and optimization for french rom, and purpose it to frenchies

so I really want they see good process during install.

I was using UC before (for rom supporting additionnal install over sdconfig), but lot's of rom don't use it. so now, with this FANTASTIC tool, I have a way to make it work forever !
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] stickydonkey:
GREAT tool Bengalih!!

I'm having a problem with the L26 Throttle ROM, probably others, when there is customisation (UC? in ROM, NOT SDCONFIG.TXT) being installed when SASHIMI is supposed to be running on first boot. The Customisation does a Soft Reset before SASHIMI is finished in the background. I know this because i can see SOME apps installed but not all and also when i change the REG for Autorun to 0 and soft reset again and it installs the SASHIMI AUTO perfectly with all my CAB's, REG and XML and Copy... I even tried changing the SASHIMI Autorun to 0 and export as REG, convert to XML and then to CAB, and running from UC, but i think thats running before SASHIMI changes the reg key to 1.

Please can someone give me some advice on this.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I don't really know what to tell you if the ROM, or your configuration is trying to run both SASHIMI and UC. Only one should run at a time. So, either disable UC and use SASHIMI (and/or have SASHIMI kick off UC at the end). OR, don't have SASHIMI autorun and manually run it after the ROM's UC reboots.

You can look at the documentation which explains the various registry keys used for Autorun, perhaps that will help.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] stickydonkey:
I'm not running UC, its part of the "customisations" built into the ROM (L26 Throttle B6) that runs on first boot after which it soft resets automatically, before SASHIMI finishes. My only real alternative is to remove the SD card before flashing and after it finishes the first run customisations, plug the SD back in. But thats a pain in the ass to remove and insert all the time. I flash PLENTY. FlashAHolic! hehe

My name is Sticky and i have not flashed in 1 day and 7 hours.:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
No, your better solution would be to remove the /2577 directory from the Storage Card root...which is the only way that SASHIMI is auto-running when detecting the storage card. Then, manually run SASHIMI after your ROM is done with its customization.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] stickydonkey:
I was afraid so... Thanks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] rkrasny:
Auto Cab ?

Bengalih:

Thank you once again for a fabulous program!

I just did one of my first sashimi restores after a rom upgrade and the auto install failed on a cab that I hadn't anticipated a dialog box or something similar. The auto process stopped and I was left doing a manual install on the remaining auto cabs (or hard reset, remove offending cab and start again, but I have a lot of cabs through sashimi).

Is there any way to know if the auto process will fail besides trial and error? Is there any way to restart it from a certain point and not from the beginning (alphabetical)?

Thanks again.

RK
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] LivinOne:
Any plans to do registry monitoring during the installs so Sashimi can automatically capture the registry locations to save per app?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
The way to know if a CAB has a chance of failing during the auto-phase is if it

requires any manual intervention

. If you don't know how a CAB will behave then you probably need to try it first. SASHIMI isn't meant to make your life easier for ONE install. If you re-flash often then it is worth putting in 30 minutes or so to set everything up and tweak your individual configurations. For CABs that don't work well in Auto, you should use Manual or use the .AUTO tandem files discussed in the documentation.

As far as picking up where things left off... the next version will have an auto-resume to do this. I'm hoping to have this out by the end of the month...there are a few bugs I am working out of several aspects.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Probably not. Please remember that SASHIMI is built using Mortscript and therefore I am constrained mostly by the limits of that language. In order to do what you are asking efficiently I would really need some sort of API to monitor the regsitry.

I could probably implement something that would have to export/read the registry before and after a CAB install and then somehow compare the two. Without aid of a 3rd party FC program this would be highly improbable. And, even with a 3rd part program to do the comparision it would still be very slow.

There have been many questions on this, so if I have time I will at least try to write a guide (or do a video) that shows you how to export and compare registry files to help people in this situation.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] LivinOne:
Sashimi is a large prog with many features but still does not do any of the most difficult part... capturing custom settings of OS and apps. Installing apps not that time consuming in comparison. Not trying to flam the app, it is fine but just like UC... it does only the easy parts.

CeRegEditor can do reg comparisons. I'll use that.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Actually the most difficult part is being able to deal with responses like yours, especially when I state clearly why this isn't possible based on the current scripting language.

Once you write your application to deal with the "difficult part"(s) please provide me the link.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] LivinOne:
I did not intend to offend... the app is nice and does well at the features it handles. I was just pointing out that the reg settings are the most vital. IMO.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] overhaulengines:
root before regs

hello Bengalih, dont know if it possible to get the regs to be installed after the root. here what i am trying to do, i do my manual install, then i go to auto, during auto i install spb mobile shell, then i want to install a spb mod created by greatbal, which involves dropping a dat file in the programs/spbmobile file. i do this with the "root" function, this change my photo contact from only 9 contacts to 3 pages of 16 contacts. the problem is the reg file is installed before the "dat" file is installed and as a result the photo contacts are not installed correctly, just random contacts from my contacts are installed. i figured out what i need to do, i put the spb reg in manual, during auto phase i install spb mobile shell along with all my other cabs, the all regs (less spb mobile shell) then root (date file ). then once this is done i go back to manual and install mobile shell reg. everythings perfect. i love it:), with all this said, is there an easier way? thanks

Lupe
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Protonus:
bengalhi:

Thanks for your wonderful programs.

Quick question: I have a number of programs that I'm copying manually to the device, that do not have installers (just single file .exe programs). I have been manually creating shortcuts for these programs. Is there a way to use customlinks.ini to make shortcuts for them automatically, or another method in Sashimi?

I was thinking of just copying the finished shortcuts to the ROOT directory to copy the shortcut files themselves back to the device. Is this the best way to do it?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] overhaulengines:
shortcuts

hello, check out the youtube link in the first post and then check out video #7, once install your cabs it will also create shortcuts wherever you want them. works really cool, also when you downloaded the sashimi cab, it created a documentation folder on your storage card(inside sashimi), look in there also, its installed on your storage card, copy it back to your computer for easy reading

Lupe

edit. my bad, when you download sashimi and unzip, it creates the documentation folder on your computer, and the cab to transfer to the device
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
well yes and no. You are correct that since the Root processes after the REG it can't do what you want. However scripts (MSCR files) process last. So you could write a simple script file to import the REG file again and/or any other operations you want to perform.

Check out the mortscript thread for help with any scripting questions.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Right...SASHIMI doesn't create shortcuts for just stand-alone EXEs. If you create the shortcuts want and just add them to the Root they can copy each time you run SASHIMI.

It's not to difficult to script shortcut creation for a file...I think there are some scripts out there that already do it. Creating a shortcut is so simple however (basically copy/paste shortcut), that it's often not worth trying to automate it.

But, yet...create them once, put them in root to copy...that's how I would do it.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Protonus:
bengalih, Thank you for your input. Another question along the same lines. Any way to automate moving the shortcuts for programs, that are installed by the ROM? ie. File Explorer, etc? I could put copies in the correct shortcut folders, that the ROOT copy portion of Sashimi, could automate for me, but, the originals would be left behind. Anyway to move them, or delete them automatically?

Actually in general, an automated delete, of files / folders could be handy. Thanks in advance.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] directorfer:
Thank You!

I just want to say thanks for this sweet app. I used it for the first time a few days ago and it made my life happier with how easy it was to install all my appz. Thank you Bengalih!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Protonus:
bengalih:

A suggestion as well. When backing up the owner information, could you also backup the Device Identity (ie the phone's name) which is used by Active Sync among other things. It's located here:

HKEY_LOCAL_MACHINE\Ident

to me that's really part of the owner information if you will. Makes sense to me to have both backed up together. Thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
I have mine in the regexport.ini. I have to agree though that I think about it as the owner information. I think it's a good suggestion.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Set up a folder in Manual\Root (or another location of your choosing) for your Programs subfolder. Then use Manual phase's Root copy to copy this using the destructive overwrite option. This will delete the entire Programs Folder menu from the device (including all shortcuts there) and replace it with your custom one.

This has to be done using the Manual Root copy phase, because you will have the option to do the destructive overwrite. Auto phase will never use destructive overwrite as a safety precaution.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I will take a look, however I think that the regexport.ini solution is best for this. The reason that I include the owner info is that there are some cases where apps will not install properly if no owner information is set.

For all other registry keys, like the identity, I know of no issues that would require this to exist Prior to applicaiton install. One line in the regexport.ini would import this for you during the auto reg phase.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] del4:
So to delete a single file from a directory, I'd have to put a copy of everything but that one file into corresponding directory in the Manual\Root location?

How then to delete an entire directory? Am I correct in assuming that the only way to do that right now would be to write a simple mortscript to do so? Seems like that would be the easier method for deleting individual files too, rather than using the destructive overwrite and Root folder method...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Pretty much. SASHIMI isn't in the business of deleting files.. Destructive overwrite is the only thing that can remove a directory and all it's files in order to replace it with a source directory of your choosing.

Writing a simple mortscript to delete a few files and running it in the scripts phase may be better.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Protonus:
I think this is the route I'll have to go.

I like the idea of backing up the shortcuts to the ROOT folder, and doing destructive overwrite, however, this would erase all the shortcuts made during the AUTO phase. Could get around it I suppose by backing up all the shortcuts made during the AUTO phase too... just an extra step. Hmm.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] juju-35:
Shortcuts not being copied to the right place...

Hello,

I have 100+ cabs being installed in auto-install and I use the "customlinks/ini" to customize the directory where they are installed.

I initially listed all cabs with the new automatic cab enumeration tool, so I guess my cab names are correct.

Most of them works but I have a few misplaced ones that are mystery:

Alll thoses just install to the main "\Programs" directory.

TomeRaider3.3.6.arm=\Programs\Info

MSVC=\Programs\System Tools

iContactBE6.3.1=\Programs\Office Mobile

pTravelAlarm_273_WM2005.STRONGARM=\Programs\Accessories

Quick_GPS_v1.00=\Programs\Positioning

ImageViewer-0.9=\Programs\Multimedia

Another mystery is I have the following in my file:

ThrottleLauncher=\Programs\System Tools

TL_TouchFlo3D=\Programs\System Tools

And Sashimi did the following:

1- Create correct .lnk files for ThrottleConfig and ThrottleLauncher in the System Tools directory

2- Create a "ThrottleLauncher TF3D" Directory in \Programs, with "Comm Manager", "contacts" and "Home" shortcuts in it

3- Create the same directory with the same links inside in \Programs\System Tools!!

Of course I cna use a Mortscript ot delete or move those "delinquents", but I would rather them install in the right place...

Any clue?

Juju
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] CLHatch:
I believe there are some programs that use the device name instead of the owner name for registration... I don't use any of them myself, but I THINK some do (when the registration is per device instead of per user).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
I took a look at the makisu video for the first time, and I was wondering what people thought of the program.

I have email xml set up from months ago. The accounts havne't changed, but my preferences for the number and size of the messages have changed. Does anyone know an easy way of automating the changes. Ideally I'd like to be able to copy the settings like in the regexport.ini file; that is identify which email settings I want to save, and automatically backing them up.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
There is no way to "back-up" the e-mail settings. They are stored within an internal database file. The best thing to do is make the XML file (manually, or with Makisu) and then you can hand-edit it in the future if you want to make changes, or just run Makisu again and choose the new options.

I really hope to have the next version of Makisu out within a week or so, which will support all the options (message size, etc..).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kyakubov:
auto install to SC

Hi everyone.

Yesterday I was trying to install games to my Storage card but it didn't work. I placed about 11 cab files ( all games) to sashimi/auto/sc/ folder and ran the application but for some reason all the cabs got installed under windows directory. None of them were installed to SC.

Any thoughts?

thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] overhaulengines:
hello, i have never had this problem, been using Sashimi from the very beginning. are you running the install right after a new rom flash? or are you just trying it the first time? if its the first time using Sashimi did you already have your games previouly installed on the main memory? are you positive they are in the SC folder?

thanks

Lupe
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
post your log file.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kyakubov:
here is the log file

09/12/08,12:49:08,SASHIMI 7.0 Initialized. Command line parameter: (none)

09/12/08,12:49:08,Storage Card detected. VALUE: \Storage Card

09/12/08,12:49:10,Settings.ini file processed.

09/12/08,12:49:10,System Language Detected. VALUE:English-1033

09/12/08,12:49:11,Supported resolution detected. Value: 240x320

09/12/08,12:49:11,EXTENDED_ROM Exposed. Auto SC KeyRepeat VALUE: 2

09/12/08,12:49:11,No Network Folders Detected. Auto SC KeyRepeat VALUE: 2

09/12/08,12:49:13,Idler script initiated. Idle timeouts will be prevented while SASHIMI is active.

09/12/08,12:49:22,Auto Phase Initiated

09/12/08,12:49:33,Auto .CAB install to \Storage Card successful. VALUE: \Storage Card\SASHIMI\Auto\CAB\SC\SJ AllMobileMines.cab

09/12/08,12:49:43,Auto .CAB install to \Storage Card successful. VALUE: \Storage Card\SASHIMI\Auto\CAB\SC\SJ BubbleBreaker_Solitaire.cab

09/12/08,12:49:50,Auto .CAB install to \Storage Card successful. VALUE: \Storage Card\SASHIMI\Auto\CAB\SC\SJ Chess.cab

09/12/08,12:50:00,Auto .CAB install to \Storage Card successful. VALUE: \Storage Card\SASHIMI\Auto\CAB\SC\SJ DopeWars.cab

09/12/08,12:50:08,Auto .CAB install to \Storage Card successful. VALUE: \Storage Card\SASHIMI\Auto\CAB\SC\SJ Freecell.cab

09/12/08,12:50:16,Auto .CAB install to \Storage Card successful. VALUE: \Storage Card\SASHIMI\Auto\CAB\SC\SJ Hearts.cab

09/12/08,12:50:25,Auto .CAB install to \Storage Card successful. VALUE: \Storage Card\SASHIMI\Auto\CAB\SC\SJ Kevtris.cab

09/12/08,12:50:32,Auto .CAB install to \Storage Card successful. VALUE: \Storage Card\SASHIMI\Auto\CAB\SC\SJ PocketSand.cab

09/12/08,12:50:40,Auto .CAB install to \Storage Card successful. VALUE: \Storage Card\SASHIMI\Auto\CAB\SC\SJ PocketSudoku.cab

09/12/08,12:50:48,Auto .CAB install to \Storage Card successful. VALUE: \Storage Card\SASHIMI\Auto\CAB\SC\SJ Rubik.cab

09/12/08,12:51:00,Auto .CAB install to \Storage Card successful. VALUE: \Storage Card\SASHIMI\Auto\CAB\SC\SJ TripYzee.cab

09/12/08,12:51:03,Auto Root folder copied. VALUE: \Storage Card\SASHIMI\Auto\Root\Program Files

09/12/08,12:51:07,\Storage Card\sdconfig.txt file not found. UC skipped.

09/12/08,12:51:10,Auto Phase Complete

09/12/08,12:51:11,SASHIMI Install Completed.

09/12/08,12:51:25,Idler script terminated. Idle timeouts will resume normally.

09/12/08,12:51:26,SASHIMI Exited

as I said before they all got installed under windows directory.

I also tried to install one of the cabs individually and it didn't ask me where to save it, it automatically installed it under windows, maybe it's the way the cab file is designed?? no idea
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Yes, if you are trying to install the CAB manually (without SASHIMI) and it still installs to \Windows (or doesn't ask you where to install) then the CAB is hard coded to install to \Windows, and SASHIMI can't change that.

The log file will still reflect that it is installing to the Storage Card, because SASHIMI properly detects it as a storage card install since it found it in the \SC directory.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] rkrasny:
CERegedit

I have been using Sashimi for quite some time (and loving it). However, I have been consistently unable to use CERegedit to compare registries before and after changes. CERegedit always hangs reading one or the other registry (I make the registry copies with the Sashimi tools).

I realize this isn't really a Sashimi question, but I was wondering if anyone else is experiencing this. Of late I have been just guessing what registry keys to export in regexport.ini, and that is imperfect at best.

BTW, Sprite backup checks the registry "for corrupt database) every night and reports nothing. This has occurred with several ROMs and multiple registry saves.

Thanks in advance.

RK