yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze ROM Development] powinmo:
Thanks for allowing me to provide some of the updates to your auto installer scripts...

*edit* Has S4X been advertised outside the Fuze specific device forums? Can we/I post a message to the general software/app forum and just link to this thread? I seem to remember I found S4X just by some off thread search because it was not in the TouchPro2 or the main app forums.

You know I wondered about why there were no pre-checks around some of the tskKills calls while others had them. However, the tskKill sub already handles the procexists check. With the refactoring I did to the sub, I think we may no longer need the pre checks prior to calling a tskKill now and having multiple dialer cabs install should work without the changes you listed... your thoughts?

For kicks... I may dump in extra dialer cabs on my test tp2 unit and see how the dialerCAB sub works during my next flash. If it works, I'll remove some of the duplicate procexists checks prior to tskKill calls.
[Touch Pro, Fuze ROM Development] powinmo:
Looks like you are on a decent track. I do not have the time to dig down to help you further right now. One other route to review to see how those Position values are used is:

Sub SCInstall

You'd be able to see where it is trying to grab and look for certain WindowText information... good luck.
[Touch Pro, Fuze ROM Development] blast0id:
in the beginning I posted links in all the energy threads and all the xda_uc related threads... but haven't done that since probably aug or sept, maybe even earlier... feel free to link wherever so long as no one else complains, I won't.

sent from a dubstep powered subsonic G2 bass cannon via XDA_app
[Touch Pro, Fuze ROM Development] scockman:
What mscr file did you place this code into? Or did you create new file? I am new to this, so pardon my confusion.
[Touch Pro, Fuze ROM Development] blast0id:
You can just create new file and save as unicode when done, if using with my mod place it in the filesMSCR folder, if using standalone with energy xdauc place in root of xdauc... hope that helps you =)

a G2 subsonic bass cannon blast0id via andr0id
[Touch Pro, Fuze ROM Development] Snake28:
Is there a possibility to get the complete Package (include the changes)?

Because I can't make it to work...

Thank's

Snake28
[Touch Pro, Fuze ROM Development] scockman:
That is what I was thinking when I was setting up my XDA_UC folder, I saw there was a folder for mscr scripts. Except now when it runs I get an error:

Comma or closing paranttheses expected

Line 21 (\Storage Card\XDA_UC\_Mod_\filesMSCR\Move_lnk_files.mscr): If ( FileExists( "\Windows\Start Menu\Programs\" & fileNM & .lnk" )=TRUE )

But then I just noticed as I was typing this out there was a " missing above between the last & and .lnk, which was a cut & paste from your previous post. Added it and now it is working. Next steps are to troubleshoot why only a portion of my links moved.

Anyway, thanks go out to you for setting this up and to powinmo for continuing the work. This has definitely been a time saver when it comes to flashing new ROMs.
[Touch Pro, Fuze ROM Development] blast0id:
No problem, I'm just happy it was as useful to others as it was for myself... as far as the links go you might try using mortscript to strip any read only attributes from them... sometimes that helps...

a G2 subsonic bass cannon blast0id via andr0id
[Touch Pro, Fuze ROM Development] scockman:
Got it figured out. I needed to add a simple MkDir at the top of my script to create a "Applications" folder in order to move items into it.

Now I am going through and getting some more tweaks, such as the double flip, time format (24hr), etc. This will definitely come in handy, especially when I go through and upgrade the wife's phone. I don't mind going the extra steps on mine, but I want her's to go smoothly. Again thanks. :D
[Touch Pro, Fuze ROM Development] blast0id:
hey, thanks, that's the first donation I've ever gotten... lol... never actually thought I'd get one hehe... thanks for poppin' the cherry... haha...
[Touch Pro, Fuze ROM Development] scockman:
Thank you. I believe in giving kudo's to those that help out in saving us ROM addicts time in flashing and setups. :D
[Touch Pro, Fuze ROM Development] Marquis63:
all I need to know is how to install the XDA_UC folder to my SDCard:confused:
[Touch Pro, Fuze ROM Development] blast0id:
You should have total commander installed, it makes transferring files and creating folders... etc... much easier. Open TC and goto storage card -- press "file" choose "mkdir" type "xda_uc" hit enter, you should now have xda_uc folder on storage card. Now unzip the package to xda_uc, then download powinmo's update a few posts up. Place extracted update file in sc/xda_uc/_Mod_/_bin folder. If your rom doesn't support xda_uc natively you can manually run the "s4xauto.exe" in the _bin folder to start the process...

Hope this helps!

a G2 subsonic bass cannon blast0id via andr0id
[Touch Pro, Fuze ROM Development] powinmo:
I did a fresh test flash with multiple dialer cabs on the 1.6.1 script in my attachments... worked great :) No changes required. Also stripped out the extra procexists checks in a test version of the script, and repeated by doing a hard reset. So far multiple dialer cabs install fine based on my current tests either way.

Based on your sig... looks like you moved on to Android eh?
[Touch Pro, Fuze ROM Development] powinmo:
Glad you are able to support some of these contributors to the community!

Hopefully we can continue to keep S4X usable and updated...
[Touch Pro, Fuze ROM Development] powinmo:
First I would recommend not spamming with the same request otherwise I'd report your subsequent posts. That's just common courtesy and not flaming you directly.

Second all you need to do is unzip my patch to your

\Storage Card\XDA_UC\_Mod_\_bin

directory or which ever your localized SD path is to override the v1.6 S4X_Auto.mscr file.
[Touch Pro, Fuze ROM Development] powinmo:
Looks like a few folks have downloaded the 1.61 update. I have seen no posts regarding if it helped or not. I'm assuming it is helping some people out I hope.

I am planning a minor 1.62 update some time in the next few weeks:

1. that basically cleans up the extra procexists checks prior to a taskKill call that are no longer needed now that the sub works as intended.

2. validating/adjusting the tandem .cab + .reg mentioned in posts 241 + 242 - as I am having some issues with it as well, once I determine a possible resolution if needed.

3. update the s4x_autolauncher.mscr with the new version numbering as well.

4. any other tweaks I find in the course of the cleanup from #1, etc.

5. if the user that is working on the sdauto updates for non wvga screens has his code working, I can incorporate that as well.

If anyone has any other major hiccups they'd like to see addressed, please let me know. If it is something I can simulate/test I will try, but no promises.

I will also try to create an updated full package with this release. Note, I am not promising any kind of schedule for this next update. This post is simply to notify current users of a potential upcoming update and hope that others looking at S4X consider it as a great adjunct to XDA_UC.
[Touch Pro, Fuze ROM Development] blast0id:
you may just want to post a link to this thread, and also to your update post, in each of the energy rom threads, or any rom that incorporates a form of xda_uc, that's what I did for the first few versions to get people to try it out and start using it... I don't think there's a flashaholic out there that this wouldn't be helpful to. =)

when you update to 1.62 email me and I will attach it properly to the first post, along with your changelog and notes. I am currently working on a way to modularize the script and make it more dynamic... similar to how I have it write the tsk menu dynamically... happy trails!
[Touch Pro, Fuze ROM Development] Snake28:
Hi powinmo,

it's great that you make the script work!

When I use the Script with XDA_UC included in EnergyRom (21.12.2010) there are Errors.

No CAB's are manually installed form: XDA_UC\_Mod_\filesCAB\Manual.

Error ist "insuffizient Space". But there's enough Space at all.

Import from Cookie's *.cht File didn't work correct. Not all Settings are importet. When I make it manually it works.

Grretings

Snake28
[Touch Pro, Fuze ROM Development] powinmo:
I probably should be more thankful of the handful of folks using the updates :) Shows there is still interest... I'll post some info in the various other threads over the next few weeks that this project is still alive.

I'll keep you posted on the 1.62 progress. Let me know if I can help you with the refactoring/modularization. I can provide coding review/assistance, etc ... or if you just need someone to bounce ideas off of. Also, I assume you still have a winmo device of some sort? Your current sig indicates a droid device ;)

Thanks again for keeping up to speed in the thread.
[Touch Pro, Fuze ROM Development] powinmo:
Appreciate you trying out the scripts/updates.

1. your failure of installing from ...filesCAB\Manual + the space error is due to the aggressive safety checking of S4X. It requires 4x the filesize of the cab of free space on the target device.

My guess is you have an older device with not a lot of native RAM, combined with installing a bunch of CABs prior to the manual step.

I may make this configurable to allow users with older devices to adjust accordingly.

If these are manual installed CABs, that pretty much NEGATES the whole idea of an automated installer like S4X. Personally, I use S4X to run hands free including a reboot at the end.

I have .auto files to deal with stuff that would otherwise require to be put in the Manual directory. I would recommend learning how to write .auto files. I can attach a sample of one if you need it. That might be helpful, because there are not many good examples for new users for this purpose. See the 2nd post from ben about the description of .auto files as a starter.

2. Cookie import. My guess is you are using Cookie 2.0.0.0. I've seen it fail CHT importing of all settings from either a full blown XDA_UC only setup and from S4X. Personally I've never seen it fully restore from a good known CHT file from an automated method.

IT IS NOT A PROBLEM with XDA_UC or S4X. All these scripts do is call the CHT editor with a command line. Given a scan of the editor thread, this seems to be a known issue... among other glitches I've experienced. Which is why I still use CHT 1.8.5 and CHT restores are always fine.

Good luck.
[Touch Pro, Fuze ROM Development] blast0id:
Yeah I still have the frankenfuzepro (fuze w/touchpro keyboard) but honestly have turned it on since I got my G2... I will send you the beta script when I have completed it, and if I get stuck I'll be sure to PM you... thanks again for keeping this alive...

A note on the 'aggressive' checking... that is actually sashimi code... I had thought about lowering it to double... but figured that could be dangerous so never did... I figured most apps are areound 2mb max (average) and if you don't have 8-10mb free probably shouldn't be installing anyways... so again feel free to change this, but I don't think that's the reason the cabs didn't install... not sure what the cause was there...

a subs0nic G2 bass cann0n blast0id via andr0id
[Touch Pro, Fuze ROM Development] powinmo:
No worries on keeping this project alive. It's worthwhile. I'm sure the G2 is very nice device and learning Android is keeping you busy along with personal life stuff :)

Apologies on the free space checking, I did fail to mention it was inherited code from sashimi. I do see the logic in the 4x free space checking, but I personally think 3x is more than enough. I did find the problem with the other user's issue and was able to replicate it. See my next post about the fix...
[Touch Pro, Fuze ROM Development] powinmo:
So watching the the BCS bowl game kept me (NOT) entertained enough I spent the time flashing the Energy Jan.6 ROMs and working on the update for 1.62...

Here's the status so far:

Version 1.62

1. Eliminated extra ProcExists checks around tskKills due to prior sub refactoring in 1.61

2. fixed "sub tandem" so that tandem installs like .cab+.reg work now

* the calls to FileInstallMethods never passed the proper fType and sType values to allow the tandem item to run

** eg, xyz.cab and xyz.reg never installs the xyz.reg file because it continued to pass the "CABfiles" fType/sType vs "REGfiles"

* tested and verified at least a few .cab+.reg tandem installs

3. fixed "Sub cabInteract" for failing on Manual CAB installations

* the free space check during a Manual CABfiles install would fail because the SpaceFree check did not have a valid InstallDestination to use

** as a result CAB files in the filesCAB\Manual would sometimes fail due to insufficient free space on the target (would read 0 bytes free on bogus target)

4. modified "Sub autoPhase" to add in second install pass on:

a. registry

* \Storage Card\XDA_UC\_Mod_\files2REG (localized as needed)

Runs after filesCHT is processed

* Allows for a final set of .reg imports prior to exiting S4X

b. mscr

* Location \Storage Card\XDA_UC\_Mod_\files2MSCR (localized as needed)

* Runs after filesCHT and files2REG is processed

* Allows for a final set of mscr scripts to run prior to exiting S4X

eg, allows for something like after a CHT Import, you can import a direct registry tweak to override some CHT settings from a file in files2REGfrom a .reg file in files2REG

5. Expose free space check multipler to target location during CAB file installations

* Sashimi (and S4X inherited) defaulted to a value of 4

** if your target destination does not have 4 x the size of your CAB file free, the CAB will not install

* exposed in autosettings.ini:

! section: [AutoSettings]

! key name: "freeSpaceMultipler"

! value: 1 to 99

* default to 3 x CABsize if not defined in autosettings.ini

5. Expose WaitFor text window during SDAuto CAB installations

* Sashimi (and S4X inherited) defaulted to a value of 10 to 20

** if your target CAB did not load wceload within the timeout period it may cause the script to hang or skip

* exposed in autosettings.ini:

! section: [AutoSettings]

! key name: "txtWindowWaitFor"

! value: 1 to 99

* default to 25 seconds to wait for the wceload text window to become active

* may need longer depending on how slow your device is and how large the CAB installations are

9. tweaked pretty tabbing/spacing for a few lines here and there

Other:

a. CHTEditor 2.0.0.0 importing is still busted, and does not load the full import file. This seems to be a known issue in the editor thread (eg, lockscreen layout will fail importing).

b. CHTEditor 1851 importing works just fine.

If anyone else has any other items they'd like to see addressed, please let me know. Otherwise I expect to release this update maybe sometime this weekend or sooner... (no promises yet)
[Touch Pro, Fuze ROM Development] puff601:
hey powinmo here is a script and reg file needed to fully import cht 2.0, lockscreen and all. i cant remember where i found the files but it took lots and lots of searching! ive tested it using energyrom's xda uc. the reg file included is what solves the issue with cht not fully importing. it wouldnt fully import before because .cht file associations are not added to the registry until cht editor is opened for the first time. that is what the included reg file does, it adds .cht file associations to the registry :) glad i could step in and help you out since youve helped me out so much with your scripts! thanks and keep up the great work!
[Touch Pro, Fuze ROM Development] vinceweis:
Thanks

Just wanted to say thanks for you guys still working on these scripts. I have ORD and need all the help I can get with tons of stuff to reinstall on every flash. I might be able to do some of this stuff but just don't have the time so I really appreciate the time you spend.
[Touch Pro, Fuze ROM Development] Snake28:
Didn't work @ my HD2 with EnergyRom from 6.1.2011 (German). I matched the mscr at my path.

First it seems to work, but not all was importet. Not all rows were importet also not a fourth Site with my Contacts.

Greetings

Snake28
[Touch Pro, Fuze ROM Development] powinmo:
I do appreciate puff's effort to help with the CHT2 import issues. The REG file basically just adds the ability to run the .cht file directly without specifically running the chteditor.exe binary during the command line execution.

I've tested the REG entries on 3 different TP2s with Jan.6 and Jan.16 CHT2 ROMs from NRGZ. No go. Same issues many others are reporting in the CHT2 thread right now.

Just have to wait for the CHTE team to get around to fixing things. Otherwise stick with CHT185/CHTE1851 for something solid.
[Touch Pro, Fuze ROM Development] powinmo:
Glad you and others are still finding these scripts useful. Please continue to provide any suggestions and comments to help make it more flexible for you and the community.
[Touch Pro, Fuze ROM Development] powinmo:
Version 1.62 update zip file has been posted:

http://xdaforums.com/showpost.php?p=10118521&postcount=287

Version 1.62 changelog:

http://xdaforums.com/showpost.php?p=10118557&postcount=288

I've tested this on 4 TP2 units with various flavors of Energy ROMs from Dec.27.2010, Jan.6 and Jan.16 2011. For my setup, everything appears to work as I need it.

Please let me know if there are any issues, concerns, etc. If no one has any major issues in a week or two I may provide a full package update directly to benjamminzIS to post.
[Touch Pro, Fuze ROM Development] vinceweis:
I just used the code to flash the latest Energy ROM. I used the Full Minus backup first. Most things worked really well. It even seemed to import a lot of the cookie settings. One thing I noticed is that I was suprised to see that the Compact start menu was already loaded. It is what I normally use to save memory. What I found however was that it seemed to be operating on top of the standard start menu; ie no memory was gained. I still had to select the compact menu to get the memory I was expecting. Is there something in this code that tried to load the Compact menu but did not disable the Standard menu?
[Touch Pro, Fuze ROM Development] blast0id:
have you done any editing of the regexport.ini??? or did you just leave it as it is in the package? if you haven't edited it at all, then you may need to add the lines necessary to backup the compact start menu reg settings... I personally don't know where they are, and I don't have my winmo phone with me right now so I can't really look... but since you did a full minus file backup, and (probably) used just the default regexport.ini then quick menu is one of the things already in the default regexport.ini as I used it myself... but the compact start menu entries are not... sorry I can't be of more help right now, but either ask around in the energy threads if anyone knows what the reg entries are for CSM or do some digging in the registry and I'm sure you'll find it... you could also always do a hard reset, then do a full regexport, then change the compact start menu settings from the app, then do another full regexport and then compare the two regexports with winDiff or similar program (Notepad++ comes with a nice compare plugin too)
[Touch Pro, Fuze ROM Development] vinceweis:
I did not do any editing. I used default on everything. Thanks, this gives me a start of where to look. It was not a big problem, just thought I would comment on it as it was about the only thing I saw as an issue for me.
[Touch Pro, Fuze ROM Development] powinmo:
Glad ben was able to maybe point you in the right direction.

Note that this is likely not a direct problem with the S4X_Auto.mscr scripts I have been helping to update. I can only surmise that the script is now restoring some settings that probably were ignored (bypassed) with the older versions.

But do let us know what you find in case there is some kind of collision happening we might need to address.
[Touch Pro, Fuze ROM Development] blast0id:
well he said he did a full minus file backup with everything at default, and mentioned that he used compact start menu before doing the backup. it's definitely not the scripts fault, all he needs to do is put the reg entries for compact start menu into the regexport.ini before doing his next backup and it will then properly export those keys to be restored...

I'm wondering if I should leave the regexport.ini example up, and just empty the one that's actually in the package, and maybe throw a check into the backup script that throws an error "you need to edit the regexport.ini to fit your personal needs before running this backup!" if it hasn't been edited yet (is still empty). Otherwise, if people are using the default file, and they don't use at least all the programs I did, then they're going to have a lot of empty reg keys being restored, which potentially could cause some strange issues (hopefully not, but it's windows, so you never know)
[Touch Pro, Fuze ROM Development] powinmo:
I knew he posted about using the backup portion of the script, but the way he worded things it was as if the restore script updates I posted were the cause of this. I just wanted folks to realize that.

I would go with your recommendation for updating the regexport.ini. There are just too many dangerous/odd things that can happen with winmo if any funky registry items are missed or imported that do not need to be. I do not use the backup scripts yet (I currently use UCMe2) so I have not had a chance to do any code review on it.

Again, appreciate you checking on the thread when time permits...
[Touch Pro, Fuze ROM Development] GLO:
Hi,

Anyone still using this?

I'd love to see it up and running again.

Im particularly trying to find out what reg keys i need to back up so that all my apps are registered via these keys.

How do i find out what keys have changed when an app is registered.
[Touch Pro, Fuze ROM Development] powinmo:
I still use S4X quite often, but primarily for restoring after flashing a ROM. I have my own backup routines.

Search for "Kheb" here on XDA for a tool to do a diff check before and after you install an app to see the file and registry differences. I use it every so often to check this kind of stuff.
[Touch Pro, Fuze ROM Development] ForgetfulGuru:
Still using it

Been using it for the last 3 or 4 ROM update.

seems todo it's job just ad described.

can't ask for more than that, was a bit of a learning curve to start with, that maybe puts off a lot of users.

As for installed apps registration code, how many you got? use a reg explorer, search for the name of the app and back up the whole key to the correct file in _mod_ (filesreg).

Happy hunting

edited due to XT9 having a laugh. ;)
[Touch Pro, Fuze ROM Development] powinmo:
If you've used XDA_UC itself, dropping in S4X is not too bad. It is just a matter of rearranging your files to the proper locations at that point. Otherwise, yes there can be a learning curve, but that seems well worth it if you flash a lot and/or support friends/family with WinMo devices.

As for finding where apps register themselves, you can use the Khebs tool to run before, then after you install/reg your app to see what you need to backup... The S4X backup script should then allow you to add in those entries.

Good luck!
[Touch Pro, Fuze ROM Development] motisu:
Hi Powinmo,

Long ago, I had a request to benjamminzIS about adding a change to the main script which would restore both the PIM.VOL file and also the PIMBACKUP file. The reason that I would like this is because I have a scheduled run of PIMBACKUP nightly at 3:00 AM to backup files and directories that contain info that I want to carry over from HR to HR. Whenever I do an HR, I first restore my PIM to get all my contacts, schedule and phone logs and then I run PIMBACKUP restore to restore the files. ATM S4X will only restore 1 of the 2 and not both. Is it possible to add this option?

http://xdaforums.com/member.php?u=2554890