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

I don't know why this would be. A Mogul is a QVGA device and runs WM 6.0, so I don't know why this would be the case. Unfortunately, it is difficult for me to test on every device, since I only own a Tilt.

At what point does it not automate? Does it automate anything? If you are able to take screen shots of the various steps during a manual install I can examine them and maybe figure out why it isn't working. You may want to compare the process to the SASHIMI videos (listed on first post). The first video shows an Automate Storage Card install during the walkthrough. You might want to compare your screen and to the video and see if it looks different. I would of course like SASHIMI to be as compatible as possible with other devices, but I need people to work with me who have those devices to get everthing right.

Interesting idea. I will think about this. Maybe I will allow for the loading of multiple settings.ini files. In the meantime...you can simply create another settings.ini file with the other settings and you can switch back and forth by renaming the one you want to use to settings.ini.

[/quote]

Sure, you can do whatever you like in the script. I would set it as a bundeled .MSCR with the CAB. This way it will run right after the CAB is installed. Then you can copy over any files needed in the Root phase.

I will tell you however that the Show/HideWaitCursor command doesn't work well in many scripts, so you may not actually see the wait cursor.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MN-Joe:
SC Automation on Mogul

All of the ROMs I'm playing with today would be WM6.1

Automation is fine up to and beyond programs on SC - For those under SC it automatically launches each CAB, it just waits until I make the selection before continuing to the next CAB. Once it finishes the CABs in SC it continues on just fine running through the remaining features.

One other mention of thanks - I've used Dot Fred Task Mgr for quite some time and never knew the value of how it will Provision an XML until you introduced it to me in your docs.

I played some with the Windowtext settings and based on what I'd seen you write in another forum tried using Paint to get the x,y, but using 12,122 results in selecting the Extended_ROM, I tried many combinations after that without luck so I've uploaded the screencapture in hopes you have an answer. At least I was able to see firsthand how the automation occurs - just don't need it to my Extended_ROM.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Ah ok...great. I didn't realize the Mogul had an extended ROM too.

I believe the issue is that the option for storage card is lower on the screen because of this extra option.

Can you try to rename a cab file to something very short, like "A.CAB" and then install that via the SC method. What I am looking to do is at the top of your screen cap where it says:

"Choose a location to install...."

I want that to all be on one line of text instead of spanning 2 lines like in your example. So, if you rename the CAB to A.CAB it should all be on one line. If you could do that and send another shot that would be nice.

Then, what I would expect to happen is you will see some automation...it still might not work perfectly, in fact it might try to select the extended ROM. But, at least we will be on the right track and I will know what to fix.

Some other questions about the Extended_ROM:

1) Is it something that all Mogul's have?

2) Does it always appear or does it only appear if you "unlock" it?

Also, after a manual CAB installation an screen pops up telling you that it was successfully installed. Normally you would have to click "OK" on this screen, but SASHIMI during automation does this for you. Is that working on your Mogul? Or do you also need to manually advance that screen too?

thx.

One last thing...if you have the time. A full registry export (in .reg format) from your device would also help me in coding around the Extended_ROM. You can use the Full Export option in SASHIMI to do so. ZIP it up and also post it here.

thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MN-Joe:
SC Automation on Mogul

I can rename a cab file, but that doesn't change its internal name which is what shows. Can you create me a couple of test files a.cab and b.cab properly setup as your test file is?

Using the windowtext argument of 12,122 I was able to get automated installation to my Extended ROM, so I hid that ROM and retried and I do get installation to the Storage Card fine, what I was not able to do was discover the secret of how the pixels actually worked in reference to what I'd expected should happen. I tried numerous combinations from 12,122 to 12,150 and could never get anything outside of between 12,122 - 12,128 would install to the second selection, but I couldn't figure out why it wouldn't get to the 3rd selection. As to the Extended_ROM question. Most of the "custom ROMs" have the Extended ROM showing on the Mogul, but it is a simple registry setting to hide or show the ROM.

Attached are the basic Full Registry after your test install and 2 cab files that do nothing more than hide or show the Extended_ROM on the Mogul.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Great MN...this is what I am needing. Sounds like you understand enough to be a good help with this.

I am attaching a ZIP with 3 CAB files that should display on 1, 2, and 3 lines respectively on the install screen.

If you could take a screen shot of the installation screen of all 3 of these with the Extended ROM hidden and then also exposed that would be a big help.

Thanks Again!

edit: 1 other question:

Does the device need to be reset after running those CAB files to lock/unlock the extended ROM?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Okay Joe,

I'd still like you to run the tests from the last post, but I am attaching a beta version that may resolve the issues.

It does a registry check for the existence of an Extended_ROM drive and checks to see if it is hidden or not. Based on what it finds it changes the number of key down presses. Normally, without an extended ROM it only needs to move down one choice to choose the storage card. With an extended ROM it needs to move down 2 spaces to get to the storage card.

I believe this should work.

Just unzip and copy the SASHIMI.MSCR over the current one and let me know how it goes.

Thanks again!

[edit: file removed due to newer release]
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MN-Joe:
SC Automation on Mogul

Here are the 6 screen captures 3 with Extended shown and 3 without.

You do need to restart after applying the registry entry (run the cab file) to hide or un-hide the Extended ROM.

I'll reset my device here in just a few minutes and report back on your beta - thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MN-Joe:
SC Automation on Mogul

I still had to change the windowtext settings as shown below:

-----------

If(((WindowText(54,84) eq "\" \ storageCard)) OR \

((WindowText(54,96) eq "\" \ storageCard)) OR \

((WindowText(12,122) eq "\" \ storageCard)) OR \ (I know from earlier tests that 54,122 would work here as well - I'm just aiming at the button vs. the line)

((WindowText(54,110) eq "\" \ storageCard)))

-----------

Once I did that the only touch I had to do was to hit Accept on the Citrix Installation for a license agreement. I've included my log to give you a sense of what this is all doing - all I can say is fantastic!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Great, looks like we got it figured out. I have attached another version here which has a few more windowtext options (6 in total) that should deal with just about every situation.

I will most likely make this an official release soon. Until then you can just copy the SASHIMI.mscr over top.

For anyone else interested, all this does is fix the problem with Extended_ROMs as MN-Joe and I were discussing. It also adds the IdleTimerReset to the installation phase to prevent the device from going to sleep during lengthy auto-installs (as discussed a few threads back).

Let me know how it works out Joe.

p.s. As far as the Citrix license agreement, not much I can do for that one as I can't account for every single type of manual intervention that would appear during a cab install. You might want to move that CAB to the manual phase if you don't want it to interfere with the rest of the Auto process.

[edit: file removed due to newer release]
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
I've had an issue where after re-installing SASHIMI, it is still able to detect cab files that I have deleted from the Auto\SC and Manual\Cab folders as it goes through the installation process. It displays the free memory and then the size of the deleted cab file as well and sometimes (not always) stops execution with a "Windows..." something error. I'll get the exact error message if it happens again...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I need more information regarding "detect" and "display". Might also want to attach a log file.

However, my guess is that if you delete the settings.ini file and allow SASHIMI to recreated it then everything should be fine.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
Not sure if this is the log file where that error occurred but here it is...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Well it doesn't do much good if it's not the log file where the error is :)

I also need more specifics on the problem that is occuring (CAB names, exact errors, any messages, etc.).

Delete the settings.ini file, try again and if still having problems provide all the requested info.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] souljah777:
Thanks for the work

Hey, thanks for this great app. It certainly saves pain and effort on hard reset.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Carlo626:
Network Folders on SC

trying to AUTO Install some CAB files on a SC will fail if Network Folders are present - see screen shoot for clear understanding.

thanks for a great tool anyway - fantastic job with the documentation too
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Try the beta posted in post #276 and let me know if that helps.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MN-Joe:
Thanks for your help with the Mogul - Titan

Your last update appears to have fixed the issues I had with the Storage Card installs on the Mogul. I've spread the word around a bit in some of the Titan groups so hopefully you'll see an increase in interest as this is a great solution. I'll keep watching for an update that allows for some choices in customization so as I play between a few different styles of ROMs I can use a base with some variations. Once again - thanks for your help and for letting us share your talent.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Carlo626:
Network Folders on SC

thanks for your quick reply bengalih but the new beta version still chooses the second line (network folders) and stops after that asking for a user choice

I understand that you are using a very clever way to achieve an autoinstall of the cabs to the SC and probably the best way to go about it would be to move (if it's at all possible) the position of the network folders from line 2 to line 3 - basically swapping them over and have a consistent positioning for the SC

bye
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I have no control over how that screen is displayed. That screen is presented by the wceload.exe that is part of Windows Mobile. I can't choose what gets diplayed where.

The beta probably does not work because it will only move down 2 lines if it detects the Extended_ROM, not some other installation location like network folders.

Since SASHIMI was designed to setup a device after a clean flash, I see these as minor problems. With the exception of the Extended_ROM which is present on some devices (and may be automatically unlocked in a ROM), there are very few if any ROMs which on a clean flash have both Network Folders and/or Bluetooth Explorer present.

The solution is to use SASHIMI to setup your device

prior

to installing any additional applications (like Network Folders).

I may fix this in a future release, but since some of this will depend on other people testing for me on separate devices, it may not be quickly forthcoming.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] asango:
Hi Bengalih,

Quick question regarding V 6.1: Besides my suggestion regarding the idletimer issue on battery (great you integrated this!) you did not mention my second one you wanted to integrate: That customlinks.ini can handle wildcards like *sashimi*.

Is this also aready included or will it be in 6.1?

Thank you!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
If it wasn't mentioned, it's not in there :)

As you can see 6.1.1b means beta....not an official release.

I am still considering the wild card idea and will try to put it in the next official release. No planned date yet.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Carlo626:
thanks again bengalih for your exhaustive answer and I do agree with you that at first boot the network folders will most probably not be there and can be installed last if needed

the more I use SASHIMI the more I like-it :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Dogpack:
Just started to use the program and love it so far. This is much more flexible than simply using UC, as I can organize and easily change what is installed between flashes.

Due to the Extended ROM being shown, I'm using 6.1.1b. I'm trying to fully automate the SASHIMI install by loading the UC cab through a UC supported ROM.

I think I found a couple issues:

*SASHIMI.lnk loaded from the cab to startup, attempts to load mortscript.mscr instead of SASHIMI.mscr. Copying SHASHIMI.mscr to mortscript.mscr resolved this issue...likewise, changing the lnk shortcut in the cab to reference SASHIMI.mscr would work as well.

*The install to Storage Card fix with an Extended ROM visible does not work when running the UCINIT load method. You must manually select the location for install when prompted. UPDATE: Never mind on this one. At some point I accidently copied the pre beta script over the beta script. :D

*SASHIMI shortcuts are not automatically created through the UCINIT method. (This may have been intentional)

A couple enhancement requests (not sure if asked for already).

*Auto press the left soft key, if the word 'Accept' is displayed. This will allow license agreements to be automated (I'm not sure if this is a standard or not).

*Auto press the right soft key, if the word 'Done' is displayed.

(Installing Skyfire Beta).

If the above two requests are not standard, is it possible to have user configured soft key values to be pressed automatically. Maybe a list of values for left and right soft keys in an INI file; when a value is found, the key is pressed. This will help automate installing some applications that require user intervention.

Thanks again for your great work! I don't mind the above issues existing, but if one of the goals is to fully automate an install, these enhancements would be a great plus.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nikagl:
If I have two cabs that need to auto install in a specific order, how would you recommend to do that? For instance add the first to the root of the Auto folder, and the next to a subfolder? Or name them by adding a number or letter in front?

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
just rename them - it should be alphabetical.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pgmvveld:
Hi,

Maybe I have overlooked it, but how can you make Sashimi re-install all your email account settings?

Thanks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] psychotik:
Screenshots from VGA

Hi bengalih,

i also would like SC install on my Diamond very much!

I made some screenshots from the installation process for you.

Please let me know if you need anything else.

Thanks

Psychotik
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nikagl:
You'll need to make a Provisioning XML that includes your mail-settings.

For creating a cab-file that contains your certificate see the following thread:

http://xdaforums.com/showthread.php?p=2416856

Regards,

Nika.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
I will look at this next time I do some development, as I don't remember off-hand. However I do believe that the link file calls Mortscript WITH SASHIMI.mscr as a parameter, so I am not sure why it doesn't work. I did change some shortcut stuff with the last release, but I thought I tested the UCINIT cab file. I'll look into it...

Yeah...UCINIT should be no different when it comes to the Storage Card install routine.

Yes, this is intentional. UCINIT and AUTORUN should be fully automated, allowing for 0 user interaction (cab allowing). This is why shortcuts are not installed. However, if you run SASHIMI manually again it will prompt for the creation of shortcuts as if it was a first run scenario.

SASHIMI currently handles a very limited amount of automated interaction during the automated SC install. There are too many cabs out there and too many ways that they present user interaction boxes. There are multiple types of text, in multiple locations, opened up with different kinds of window controls. It is simply not feasible to code for all of these possibilities and allow SASHIMI to automatically choose what the proper one would be. In addition there are problems with window control both inside mortscript, and with how a CAB might present a user interaction window.

Chances are if you tried to automate this process you might get 3 or 4 CABS to respond properly, but the remaining 6 or 7 would hang up, possibly causing a problem with the whole SC routine.

As such, CABS which require Manual interaction should be installed during the Manual phase. As far as I am concerned, if you are going to sit there watching the install to deal with CABS that can't be responded to, you might as well manually install those CABS to prevent installation issues.

If someone wants to identify 2 or 3 HIGHLY common prompts that are presented during an install then maybe I will look into automating this further. For this I would require:

1) At least 3 CAB file which present the same type of installation dialog.

2) The presented dialog must have similar verbage, text placement, button choices, and window handling.

Because it is probably difficult to find CABS that follow the above my original view will probably stand.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Yes, as studentjunk wrote, it is alphabetical.

More specifically the way it should work is that all files in the main folder are processed alphabetically. Then each sub-folder is processed in alphabetical order and the CABS within each folder are processed alphabetically.

So a structure like so:

\CAB\F.CAB

\CAB\D.CAB

\CAB\A\M.CAB

\CAB\A\B.CAB

\CAB\B\test.CAB

\CAB\B\alpha.CAB

Will install the CABs in the following order:

D.CAB

F.CAB

B.CAB

M.CAB

alpha.CAB

test.CAB
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Thanks.

If you could please download the test cabs from post #272 and take a screen shot of each CAB on the screen to choose location.

Also, please do a full registry export (you can use SASHIMI registry tools) and zip all those up and send them. I will look into it.

Also, if possible if you could send a couple of screenshots of how SASHIMI looks on the Diamond I would be interested as well.

thanks.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] nikagl:
Did I already mention this:

SASHIMI Rulezzzzz!! :)

I actually love it, in every respect. Initially I was reluctant as it seemed to be a more difficult process that UC, but when I started using it, it turned out to be sooooo much easier! I do still use the UC features because it has one advantage: you can specify the cabs to install from a text file and leave them in the original location. I have all my cabs in a specific folder, also the ones I do not use for most ROMs (only for some when for instance HTC Home turns out not to be available).

Regards,

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

Please find below.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
Thanks for the praise!

Of course you can still keep you CABS in a single location with SASHIMI and then change the Manual/Auto CAB path to a location of your choice.

Since, SASHIMI will work with subfolders as well you can group your CABS according to type if you want (i.e. Apps, Games, Tools,etc..).

If there are some CABS you don't want to install everytime, you can put those in the Manual Path. You can also use the one-off choice from within the manual install if you need to choose another location.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bengalih:
thanks... I might be able to work on it this weekend.

Diamond's only have Internal storage correct? You can't put in an SD card?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Moe5508:
Yep, that's correct. No SD slot...just ~ 4GB + of internal storage...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] psychotik:
Thanks, that would be great! :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] studentjunk:
You can find your important registriest with ceregeditor. It runs on the pc, but reads the pda registry. Just backup your registry, make changes to the functions of interest, and then compare the current registry to the backed up registry. It will show you all the changes, including the changes on your registry settings. You can then copy and paste the registry keys to sashimi.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] JMaxMan:
What I'm trying to understand is if you have lots of cabs files that you are installing. But some of them needs to be installed to the device and others to the sd card. How can you automate this process ? Automattically
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] juju-35:
Thanks so much, this sounds like a good solution! Not as good as a UI based thing that would abstract the main useful areas, but definitely better than reading the reg directly. I will definitely try it.

Juju
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MN-Joe:
At least take a look at the YouTube Videos... Once you install Shashimi you'll find an Auto Directory, in there you'll have a CAB directory and inside of there an SC directory.

Put Device cabs into the Cab directory and Storage Card cabs into the SC directory and then run Shashimi in an Auto mode. Make sure you are running the beta version of Shashimi.mscr on top of 6.1.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Quick Silver:
after the install the program asked me is I wanted to create a shorcut but it didnt create one :(

Is there a way to do this manually?

Thanks :)