Database Info

Rom cooking help

What is the reg key to disable Error reporting
How the heck do i move the Live Messenger and Windows Live Shortcuts for Start menu without getting a double. Where is the original entry that moves them from the windows directory to the Start Menu\ Programs.
I know how to do the steps just cant find the sections.

nottoosmart said:
What is the reg key to disable Error reporting
How the heck do i move the Live Messenger and Windows Live Shortcuts for Start menu without getting a double. Where is the original entry that moves them from the windows directory to the Start Menu\ Programs.
I know how to do the steps just cant find the sections.
Click to expand...
Click to collapse
Code:
[HKEY_LOCAL_MACHINE\System\ErrorReporting\DumpSettings]
"MaxDiskUsage"=dword:0
"MaxLogFiles"=dword:0
"DumpEnabled"=dword:0
I think this is what you're looking for.
Regarding the Windows Live shortcuts, just act as they are already in start menu\programs and edit the initflashfiles to move them out of there

anichillus said:
Code:
[HKEY_LOCAL_MACHINE\System\ErrorReporting\DumpSettings]
"MaxDiskUsage"=dword:0
"MaxLogFiles"=dword:0
"DumpEnabled"=dword:0
I think this is what you're looking for.
Regarding the Windows Live shortcuts, just act as they are already in start menu\programs and edit the initflashfiles to move them out of there
Click to expand...
Click to collapse
I did that with the shortcuts, but now i got 2 copies of each.

typho5
I have a real simple question....I lost my command instructions for Typho5.exe, and it has totally slipped my mind.
What is the command to to seperate GSM, IPL & SPL, & OS from nk.nbf with out the files being split up?
From what I remember it was - typho5.exe nk.nbf -nosplit?
Is that correct? I'm sure I'm missing something here.

typho5.exe -x nk.nbf

nottoosmart said:
What is the reg key to disable Error reporting
How the heck do i move the Live Messenger and Windows Live Shortcuts for Start menu without getting a double. Where is the original entry that moves them from the windows directory to the Start Menu\ Programs.
I know how to do the steps just cant find the sections.
Click to expand...
Click to collapse
Well, I had already said this once already, but look at the proxml file in the windows live folder, and delete the first two entries, or change the direct that there are to be installed too!

bradsnw said:
I have a real simple question....I lost my command instructions for Typho5.exe, and it has totally slipped my mind.
What is the command to to seperate GSM, IPL & SPL, & OS from nk.nbf with out the files being split up?
From what I remember it was - typho5.exe nk.nbf -nosplit?
Is that correct? I'm sure I'm missing something here.
Click to expand...
Click to collapse
Thats correct!
If you open 'run' and type the address of the folder you can have it run with out opening a command prompt
e.g D:\DEV_WIZcrossbow CLEAN-V2\Dump\typho5.exe -x nk.nbf
Then you just place you nb file in the same folder each time and run it from the run command in start menu. It will keep it there as well for you to use and use!!!

funman i figured an easier way out. just rename the shortcuts and make the changes in the initflashfiles.dat. LOL. Thanks though. I guess your way is correct. Now my only issue is making my ROM have more memory. Im stuck at 23.49 available program memory. Im working off my vanilla rom. Any suggestions?

nottoosmart said:
funman i figured an easier way out. just rename the shortcuts and make the changes in the initflashfiles.dat. LOL. Thanks though. I guess your way is correct. Now my only issue is making my ROM have more memory. Im stuck at 23.49 available program memory. Im working off my vanilla rom. Any suggestions?
Click to expand...
Click to collapse
Well you could do it that way, but i would say that it would help your PPc if there was not redendet reg and other thing sitting in the PPC

ok i fixed it there. thanks
Now that that is done, onto my memory issues. LOL. And i dont mean my brain. Basically im trying to get at least 30 mb available memory. here is the drill down of my startup folder.
CapNotify
custTDYTSK - Cingular Ext Rom thing.
Init_Tray
ScreenRotate
Voice Command
WiFiInit

Ok so i am still working on the memory, I got other simple little thing and i dont want to have to tear apart Xplorer 1.1 to find out how to make an icon for my connectivity folder. LOL. Im being lazy. Ani you here? how did you do it?

nottoosmart said:
Ok so i am still working on the memory, I got other simple little thing and i dont want to have to tear apart Xplorer 1.1 to find out how to make an icon for my connectivity folder. LOL. Im being lazy. Ani you here? how did you do it?
Click to expand...
Click to collapse
I did it by making a resource file, placing it into windows and then making an
ico.lnk or icon.lnk ...don't remember and have no time to check now.
Dirrect that icon to the resource you created, make it invisible and put it into the folder you want to change appearence
phiew

I tried to create a DLL. but reshacker didnt like it. What do you mean a resource and what did you use to create it?

nottoosmart said:
I tried to create a DLL. but reshacker didnt like it. What do you mean a resource and what did you use to create it?
Click to expand...
Click to collapse
I created a dll too and used Restorator 2007

Ok, so ive got the picture that I want to use for my icon. Its in transparent GIF format though. Anyone know of a good software to use to convert that wont water mark or anything thats free or even trial?

http://www.gold-software.com/download5206.html

HTC Camera 3.0/3.3 cab?

I'm currently using Equinoexe's Touchflo rom (VERY slick BTW, kudos to him!), and the only thing I'm having a problem with is the camera that's packaged with it... Does anyone have 3.0 or 3.3 wrapped up in a cab file? I've searched and searched, and nothing comes up.
THANKS!

I believe copying files does the trick. For me it didn't. I am also looking to make it work but I gave up.

yes, any1 have cab file?

I'd be interested in the Camera files as a cab too.

Here's Faria's 3.3 camera files, but they're not in a cab. It includes a readme.txt file instructing where to dump the files.

reg key
does anyone know where abouts in the registry the reg key goes or wot prog ram i could use to import the key

i'd like to add that in the rar file posted for faria's 3.3 camera, there are files to place in windows, and instructions to also import a reg key for the camera. that reg key, however, isn't included with the package.. does anyone know what is needed?

The registration included to the package but it is hidden because the extension is reg which connected to the files system. If you want to see, you must set your windows to appear the files system.

For example Resco explorer has the option to show hidden files, then to apply the reg file, just double click it.

Problems with PROVXML files

I've spent the last 6 hours trying to get PROVXML files working with 1.60 ROM and I just can't... Here is what I've tried:
Created my own PROVXML files in Notepad, Notepad++ and XML Notepad, following existing examples and documentation from http://msdn2.microsoft.com/en-us/library/aa456134.aspx
Modified existing PROVXML files (e.g., 'copy' command to 'move' command for OEMDrivers\mxip_HtcApps_HTC_Ringtone.provxml) and re-touched with proper timestamp and file attributes (+s +r +h +a)
Cut up portions of Menu_Operation.XML and placed into renamed files, such as mxipupdate_package_ver.provxml and mxip_package_ver.provxml
Saved in ANSI & Unicode
Used BuildOS.exe and BuildOS+Package_Tools-2.7.exe
And no matter what I do, the file operations I'm trying to perform within the PROVXML never happen!!!
I would be greatful for any help or insight. Thanks much!

I've had issues adding new provxml files but have always been able to add operations to existing ones w/o problems. This is essentially how I split out MMS from SMS on my latest ROM. Timestamp/file attributes weren't an issue for me. Instead, my biggest issue was the fact that my ROM wasnt running the MASD provxml that was part of the ArcSoft package. I ended up working around the problem my placing the MMS account provisioning into another provxml. Interestingly, looking at these files with WinHex shows a 3 byte sequence that proceeds the non-unicode provxml files themselves. Definately not a checksum since I've been able to change the contents w/o adjusting this info and the provisioning itself still runs. In fact, deleting the sequence entirely seems to have no effect on whether the provisioning doc runs at cold boot or not. Consequently, I've always been interested in understanding the mechanism that controls what provxml files get run.

The hex bits are only found in provxml files contained with the OperatorPKG folder. Other provxml files have no special hex bits, and unfortunately, I've added those hex bits to my files and still have not had any success.
The main reason why I want to use provxml files is to replace initflashfiles.txt in every package and reduce the amount of memory used by having duplicate copies in the windows folder and the copied folder.
Any additional insight would be appreciated...
Thanks again.

_Alex_ said:
The main reason why I want to use provxml files is to replace initflashfiles.txt in every package and reduce the amount of memory used by having duplicate copies in the windows folder and the copied folder.
Any additional insight would be appreciated...
Thanks again.
Click to expand...
Click to collapse
You ever have the option to pack the soft into a CAB and install on first boot trough customizacion OEM... i know is not the same, but you gain control about the space on storage.
Cheers.

..................................

..................................

bengalih said:
Hey all,
I thing UC is great, but I have gotten to prefer the Tiered Autoinstaller that allows me to pick and choose my CABs to install.
I have taken Tiermann's cool app and packaged it for a non-cooked in audience. Add it to your favorite ROMs to quickly pick and choose all your CABs to install.
Find out more about it and grab it here
Click to expand...
Click to collapse
Thank you kindly

bengalih said:
Hey all,
I thing UC is great, but I have gotten to prefer the Tiered Autoinstaller that allows me to pick and choose my CABs to install.
I have taken Tiermann's cool app and packaged it for a non-cooked in audience. Add it to your favorite ROMs to quickly pick and choose all your CABs to install.
Find out more about it and grab it here
Click to expand...
Click to collapse
OK so THIS is a big step forward for the crazy flasher that lies in us.
Time saving, simple, perfect.
Very convenient to use (especially because I already have my CAB collection on my storage card in a folder named CAB...)
Thanks

Choice between Device and SD Card
Hello Bengalih,
is it possible that when i use the TierAutomatic Installer that i have the choise between the Telefon Memory or the Storage Card where the Programm has to be installed ?
I like to install the most of my Programms to the storage card to keep the Memory of the Phone free for the running Programms.
Or doesn´t this make sense ?
Greetings from germany
Jürgen

oooh great!

Awesome THANK YOU!
but 1 question/request
I have my cab directory sorted by different directories, is there a way to checkbox an entire directory? instead of adding each cab in config.sys?
i have directories like
\Storage Card\Games
\Storage Card\Tweaking
\Storage Card\System Tools
\Storage Card\Multimedia
etc. so it would be awesome to just check the entire directory to save overview

Awesome work dude - been looking for an installer like this that runs perfectly on non-UC compliant ROMs! This works flawlessly - thanks!!!!

Is it also possible to install the cabs on the storage card? i dont want my games on my device but on my storage card...

Imperium said:
Is it also possible to install the cabs on the storage card? i dont want my games on my device but on my storage card...
Click to expand...
Click to collapse
I would like to know that too.

Imperium said:
Is it also possible to install the cabs on the storage card? i dont want my games on my device but on my storage card...
Click to expand...
Click to collapse
change the default installation directory to your storage card using WinCE cab manager.

JuWarth said:
Hello Bengalih,
is it possible that when i use the TierAutomatic Installer that i have the choise between the Telefon Memory or the Storage Card where the Programm has to be installed ?
I like to install the most of my Programms to the storage card to keep the Memory of the Phone free for the running Programms.
Or doesn´t this make sense ?
Greetings from germany
Jürgen
Click to expand...
Click to collapse
The Tiered Auto Installer works by using a built-in copy of Autorun. Since Autorun doesn't allow any user interaction, it is not possible to "choose" what location you want to install.
However, you can use a CAB editor tool to open up your .CAB, and change the default installation directory to "\Storage Card".
WinCE CAB Manager can do it with the trial version.

Thx for the answer
Thx for the answer. I will try the WinCE cab manager

Imperium said:
Awesome THANK YOU!
but 1 question/request
I have my cab directory sorted by different directories, is there a way to checkbox an entire directory? instead of adding each cab in config.sys?
i have directories like
\Storage Card\Games
\Storage Card\Tweaking
\Storage Card\System Tools
\Storage Card\Multimedia
etc. so it would be awesome to just check the entire directory to save overview
Click to expand...
Click to collapse
Yes you can do this...with a little elbow grease:
From the TAutoInstall page...
It will find all cab files referenced in the config.txt as well as those found in \Windows, \Storage Card\Boot, \Storage Card, \Extended_ROM, and \Extended_ROM2.
Click to expand...
Click to collapse
Note that the config.txt should be located in the same directory as TAutoInstall, which in my package is \Windows. I have found that if TAutoInstall is installed in another location with a space in the name (e.g. \Storage Card or \Program Files) that it won't function properly).
In addition the following quote:
Note: The default search directories can be overridden by a command line.
TAutoinstall.exe "\SomePath\folder1" "\SomeOtherPath\Folder2"
You can have up to 10 search paths.
Click to expand...
Click to collapse
In fact, this is the magic of how my packager is working. I have created a shortcut to run TAutoInstall with specific search directories, in this case \Storage Card\Cabs.
NOTE: When you specify directories on the command line it no longer checks the default directories listed above, but it will still check the config.txt file.
Unfortunately it doesn't check recursively, but you can have up to 10 paths. So, to do what you ask you will need to edit my .lnk file:
You need to open the .lnk file in a text editor.
You can copy the \Program Files\TAInstall\TAInstall.lnk to your PC via activesync.
Open it in WORDPAD, not NOTEPAD as it doesn't save them properly.
You will see my syntax:
47#"\Windows\TAutoinstall.exe" "Storage Card\Cabs"
Note the format, specifically the quotes and the number at the beginning. The number is the number of characters in the string minus anything before and including the #. So in the above link there are 50 characters minus 3 (47#). You can modify the shortcut for up to 10 paths, like so:
122#"\Windows\TAutoinstall.exe" "Storage Card\Cabs" "Storage Card\Cabs\Sub1" "Storage Card\Cabs\Sub2" "Storage Card\Cabs\Sub3"
Note that I updated the number to reflect the number of characters in the string minus 4 (122#).
I have not tested it with more than one path, but it should work. I also don't know if there are any limitations as to the maximum length of a shortcut, perhaps a developer would know.
Once you've edited it, copy TAInstall.lnk back to \Program Files\TAInstall\ and you should be good to go. If you have a problem, make sure that the shortcut is being save properly by your text editor. Remove everything you added and re-save and see if the .lnk file still works. If not, then you're text editor probably mangled it.
I would then make a backup copy of the lnk so you won't need to do it all over again.

simple 3-row Mortscript
another "solution" without UC could be a simple mortscript in the cab-directory:
It's not "unattended", but it will do the the job...and you can select the install directory....
ForEach CAB in files (Systempath("ScriptPath")&"\*.cab")
RunWait (%CAB%)
EndForEach

petervbeck said:
another "solution" without UC could be a simple mortscript in the cab-directory:
It's not "unattended", but it will do the the job...and you can select the install directory....
ForEach CAB in files (Systempath("ScriptPath")&"\*.cab")
RunWait (%CAB%)
EndForEach
Click to expand...
Click to collapse
Peter, could you be a bit more step by step with that, maybe putting it into a code box?
I get it, I can read it, I don't know what a "mort-script" in the "cab-directory" would look like (text file?) and where exactly it would go.
Thanks for this thread, guys!

rush242 said:
Peter, could you be a bit more step by step with that, maybe putting it into a code box?
I get it, I can read it, I don't know what a "mort-script" in the "cab-directory" would look like (text file?) and where exactly it would go.
Click to expand...
Click to collapse
just create a text file on your desktop computer and save it with the .mscr file-extension.
then copy this file including the mortscript.exe to your "cab" directory on your mobile machine. that's it
the "cab directory" is just the directory where you save these two files and all your cabs....
but as i said - this script will just call all setups, all necessary informations are manually - it's just like you click each
cab file seperately in file explorer...
attached you'll find my installer (sorry, the language is in german (NO, i'm NOT german, i'm from South-Liechtenstein )
and it'll write a registry key how many times you've started this script....the first time there is no message, if you run this
script more than once, there is a counter and it will remind you how many times you've started this script... (yeah, i like such things....)
i like the fact that i absolutely know what this script is doing, i can easily choose between storage and memory and if i want to
cancel a setup it's no problem
edit: english script (including mortscript exe is uploaded...hope that helps)

rush242 said:
Peter, could you be a bit more step by step with that, maybe putting it into a code box?
I get it, I can read it, I don't know what a "mort-script" in the "cab-directory" would look like (text file?) and where exactly it would go.
Thanks for this thread, guys!
Click to expand...
Click to collapse
I have a feature-rich MortScript that I will be uploading shortly...you may like it better than the Tiered Installer....

petervbeck said:
i like the fact that i absolutely know what this script is doing, i can easily choose between storage and memory and if i want to
cancel a setup it's no problem
edit: english script (including mortscript exe is uploaded...hope that helps
Click to expand...
Click to collapse
Thanks Peter!! That should really help.
UC is good, but there are so many differences between ROMs that you're always editing the text file and thus prone to making it error out. Not to mention, the Lock/Unlock BS.

I've been using Tier Autoinstall in my ROMs for awhile. Even have a cab for non-cooked installation that puts a shortcut in the same place you do?!? funny how great minds think alike . I'll update this post to put in the link to the wiki about it (once the wiki is back up).

_Alex_ said:
I've been using Tier Autoinstall in my ROMs for awhile. Even have a cab for non-cooked installation that puts a shortcut in the same place you do?!? funny how great minds think alike . I'll update this post to put in the link to the wiki about it (once the wiki is back up).
Click to expand...
Click to collapse
Hey welcome back _Alex_, I thought you were movin' on.
Yes, I actually discovered the Tiered AutoInstall first in your ROM I believe. I know you have a stand-alone UC (which I link on the front page), but never saw a stand-alone Tiered from you.
Although I like the check-box effect to install cabs, the current version of Tiered AutoInstaller (and thus my stand-alone version) is a little too limited for all but automated installs.
If you guys like, please check out my new VIP+bengalih RAW AutoInstaller. Fully MortScript based with quite a few more features!

..........................

............................................

.....................................

excellent work as always, thanks a lot!

Nice. Make as many options as there can be.

email settings
very nice, just installed so far so good. installed my cabs no problem, instruction to do this are pretty clear.
i have been reading about UC from slueth on how it install my setting for my email, not having much luck understanding, got it to install my cabs no problem. next i am trying to learn how to copy my email settings, i dont know if this can be done with this program? and if you can help me do this, its only 1 email account pop3 so not much info.
thanks
Lupe

Sounds cool, in fact, I liked it the first time, When it was UC. Just kidding I had to say it, just had to. I look forward to giving this a go when I have a moment.

JimmyMcGee said:
Sounds cool, in fact, I liked it the first time, When it was UC. Just kidding I had to say it, just had to. I look forward to giving this a go when I have a moment.
Click to expand...
Click to collapse
Thanks...I think
Let me take this opportunity however to say a couple of things about UC, and specifically how this tool is really for a different purpose.
First off, although UC is a nice standard, even Sleuth acknowledges that there is really nothing new in what he is doing with UC. He took some standard autorun.exe techniques and registry entries and bundled them to make a procedure that used to take 3 or 4 steps now take 2. UC adds nothing new, other than a standardized way to use autorun.
Also, UC mainly is meant for fully automated installs of a storage card. So, you pop your card in the slot, and sdautorun processes the sdconfig.txt automatically. UC can install CABs, provision XML and copy files (with limited success). However you must first set up your sdconfig.txt file and build your XML files manually or by exporting registry keys. You must set all this up beforehand in the sdconfig file.
SASHIMI takes a different approach in that you don't need to set up a config.txt file and it isn't bound to statically install the same things each time. In addition, since it can import reg keys natively (well, technically it calls another included app to do it, but it's all bundled in the installer) you don't need to go through the hassle of exporting reg keys, and then converting them to .XML (and optionally rolling them into a .CAB file).
Other advantages SASHIMI has:
In addition to running fully automated, you can choose to run only Manual, or Manual+Auto which will allow you each time to be prompted with a set of CABs and .REG files which you wish to install.
Customizing .CAB installs by tethering/binding .REG and .MSCR files so you can easily map additional configuration entries to a particular .CAB
Logging, so you can track what has been done
Transfer entire directory structure. If you have several folders with multiple subfolders you want transfered from storage you can do this easily.
Modular - the multiple directory structure allows for nice compartamentalization and organization of applications and configuration settings. Things aren't stored in static config.txt files or difficult XML. Simple .REG files, CABS, and optionally MortScript files if you want to use them.
All of these benefits come with only one drawback, which is inherent in this technique. That is it may not be fully automated. Of course this makes sense because if you want to be prompted about which CABs you want to set up or where you want to install them, you need to invest a little time answering prompts. I think the time to do this is considerably less than creating a config.txt file.
In addition, SASHIMI can be run using only Auto mode, in which case it is fully automated (and logged). In fact, it can even be configured to be run automatically when the SD card is put in if you so choose (I will be writing up instructions for that).
So, it really depends what you want to do. I honestly feel that SASHIMI can do everything autorun (and thus UC) can do and more. The exception is it can't import XML. I may update this by including autorun in the package and build this feature in as well. Personally, I think it's easier to work with .REG than .XML. UC however, has a slightly simpler structure which of course why it isn't as feature rich. I think it lends itself more to it's main purpose...which is to be cooked into ROMs and do a fully automated install at boot.
However, as the name implies, SASHIMI is a RAW installer and is meant more for users who want full control of what is getting installed (generally users who use lighter, uncooked ROMs and want to install more apps, etc.
Although, as I said everyone can use it. I think you really need to download it and run through the tutorial to see the power it has.
thx!

Awesome!!!!!! Been following your dev work on this and I should say this is a really great new level you've taken this package!!!!

Gonanaaa try this!

Thanks for this
Sashimi works great. You did a marvelous job of documenting it. Follow the directions and you have an easy solution for us flashing junkies....Bravo!

parleyp said:
Sashimi works great. You did a marvelous job of documenting it. Follow the directions and you have an easy solution for us flashing junkies....Bravo!
Click to expand...
Click to collapse
Thanks for your support.
Please feel free to make suggestions/bug reports/feature enhancements.
I couldn't think of anything else it needed at the time, but I'm sure it's not perfect.
On my list so far is:
Add support to use XML provisioning files (in addition to REG). - Not sure if I will put this in both Manual AND Auto modes...thinking maybe just Auto.
Writeup instructions, and maybe a little update that shows/updates the program to run in UC/Autorun mode. - This will allow it to run in auto mode as soon as the SD card is placed in the device (or a new device is started for the first time with the SD in the slot).
Integrate a config.txt / sdconfig.txt file so those of you who run UC can easily move/switch between both apps. Basically the idea is SASHIMI will process the config.txt file in addition to what it already does. It is kind of repetitive, since then you would be able to either import an XML through my methods, or just put your XML/CPY/EXEC commands in the config.txt file. Obviously if you ONLY use config/sdconfig.txt then there really isn't a need to use SASHIMI too, but if you want the extra options while still maintaining any work you did with UC then it's a go!
I would like to try to keep the app aroung it's central purpose, which is as an installer automater/helper app...so try to keep suggestions/recommendations around that.
thanks

better than uc, imho
thanks for you help bengalih, from your other thread, got my emails set up,
i used tiermanns Personal OEMizer to create my provisioning XML.
i then used the task manager you provided and bam, it worked.
this is why i believe SASHIMI is the best choice. i flash many roms, not all roms have the same programs installed, when i use uc i have to change my config.txt or i might install something that is already in the rom or i might miss something that is not in the rom. yea yea i know, cry me a river
heres what i like, i put my stuff in auto file, like my spb mobile, spb weather and a few others that no one installs because they must be purchased, then all my others in the "manual file" stuff like pcm keyboard, rss hub, htc end key, etc and google search which makes you stop and accept user agreement, if i have something in the manual file thats already installed in the rom you just flashed, just click no when it gets to it and on to the next cab.
i believe with sleuths uc if a cab requires a reboot it cant be used, for example i can put spb phone suite in manual and once completed it ask if i want to reboot, i select no and now it goes to the next cab, once im done with the cabs i want to install then i reboot very very nice
thanks
Lupe

overhaulengines said:
thanks for you help bengalih, from your other thread, got my emails set up,
i used tiermanns Personal OEMizer to create my provisioning XML.
i then used the task manager you provided and bam, it worked.
this is why i believe SASHIMI is the best choice. ...
Click to expand...
Click to collapse
Thanks Lupe...glad you got it worked out.
I am finishing up the next version, which will incorporate UC as well, so if users have an sdconfig.txt file they want to use it can also be used by SASHIMI (in reality I am calling UC's SDAutorun.exe to do it). So, it will be like a combined installer.
There still isn't a substitute for UC in terms of cooking it into a ROM to run automatically on first boot, but with my next version you will be able to use the sdconfig.txt and you will also be able to initiaze SASHIMI when the storage card is inserted. This makes it ideal if you need to provision alot of phones and each one is slightly different.
It sounds like you are taking advantage of the manual+auto install...great. FYI if a .CAB is already unstalled, then the following will happen:
1) If in Manual mode, it will ask you to remove the old CAB first and then it will ask you the location to install the new one. Of course you can always skip the CAB in manual mode if you don't want to reinstall.
2) If in Auto mode it will automatically remove the CAB and install it again.
Ah, one last thing...the Task Manager is DotFred's task manager, I can't take the credit for that application, and I will be sure to credit him in the next release notes.

Version 3.0 coming soon.
I'm finishing up version 3.0 to be release by end of week.
Here are the following updates:
v.3.0
- XML integration added! Use XMLs with/instead of .REG files to provision your device.
- UC integration and the ability to use sdconfig.txt files.
- Option to auto-launch when Storage Card is inserted.
- Better Log handling and INTEGRATED log viewer.
- Additional menus for less clutter and more choices!
- More status dialogs to let you know what's happening when.
- Ability to create/restore Program Menu shortcuts to any location.
- \Scripts and \Root directories available in both Auto and Manual modes for more control!
- Moved tandem/bundled .REG processing before .CAB installation for the ability to import registry entries prior to application install. .MSCR and .XML tandem files process after .CAB installation.
- Optimized code formatting
Let me know if there are additional options you would like to see.

Does the SDConfig.txt file use eliminate the ability to use the programs default folder based way of separating and installing? The program is excellent as is. But if I were shooting for the moon I would suggest adding ability to export personal information to .XML or .REG from current device for use after flash...

aadadams said:
Does the SDConfig.txt file use eliminate the ability to use the programs default folder based way of separating and installing? The program is excellent as is. But if I were shooting for the moon I would suggest adding ability to export personal information to .XML or .REG from current device for use after flash...
Click to expand...
Click to collapse
I completely agree with this. If you were able to have the tool create the .xml and/or .reg files from your currently installed ROM, it would make an excellent tool a killer app.
Thanks for the work!

aadadams said:
Does the SDConfig.txt file use eliminate the ability to use the programs default folder based way of separating and installing? The program is excellent as is. But if I were shooting for the moon I would suggest adding ability to export personal information to .XML or .REG from current device for use after flash...
Click to expand...
Click to collapse
No, the SDConfig.txt file is an ADDITIONAL step in the Auto phase.
So, after running either the Auto, or Manual+Auto modes the last step will be to process an SDConfig.txt file if it exists AND the option to use UC is enabled within SASHIMI.
I think that answers your question.
I did also add the option to do a backup of the entire registry to a file. But, your suggestion gives me an idea....
I can't really provide an interface with MortScript to do a selective backup of the registry, but what I may be able to do is read another configuration file. So, the user would create a file with the following format:
HKCU\Settings\Phone Settings\
HKLM\Control Panel\Sounds\
HKLM\Software\Application1\
Click to expand...
Click to collapse
Whatever keys are listed in the entries will be written out to a .REG file in the Manual\Reg directory and can then be imported if desired or moved to Auto\Reg.
Would that suffice for what you are asking?

That, my friend, would be EXCELLENT! This is an awesome application! Keep up the good work!

Thanks for everything, sir. I cannot wait to try this out.

Ok, I have implemented all the above features.
I just need to do a bit more testing and then repackage the .CAB and update the documentation.
Unless i get anymore feature requests/bug reports I will be upping this probably by Friday.
If any new feature requests are too complex (but worth doing) they may wait until next version.