I posted this over at Sleuth's thread in Hack & Dev, so I thought maybe I should also post it here so that if other cooks would like to incorporate auto installation feature, you can take a look at how it is done.
I have been using auto installation feature in my Roms for the past 3 months and there is no need to introduce another app as everything can be done with just autorun.exe. However, pardon me if I missed something that this app offers but autorun.exe/preautorun.exe doesn't.
Let me share what I know about auto cab installation.
With just autorun.exe, it is possible to:
1) Auto Install cabs from Extended Rom, then
2) Continue Auto Installation from Storage Card
3) It is also possible to Auto install the cabs into Storage Card by editing the cabs Path with some sort of cab creator/editing program. I used WinCECabManager.
4) With the Hide command, you can auto install virtually everything with just autorun.exe
Auto installation is not new and we've seen it used in Extended Rom. We also know that it is possible to Auto Install from storage card. We know that for autorun to work, it has to point to the config.txt file's path:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"TurnRadioFlag"=dword:0
"AutoRunType"=dword:0
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
In this case, when autorun fires up, it searches for the config.txt in Extended Rom and start executing the parameters in the file. At the end of the config file, it usually ends with the reset command. For example:
Code:
LOCK:Enabled
CAB: \Extended_ROM\AdobeFlashLite_2_1.cab
CAB: \Extended_ROM\HTCTaskManager.cab
Hide:Enabled
LOCK:Disabled
RST: Reset
To have auto run install from storage card, we simply change the path to:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunType"=dword:0
"AutoRunCFG"="\\Storage Card\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
Of course, for phones without extended rom, I believe it's look for autorun in windows. In either case, it doesn't matter since all it needs is to launch autorun from somewhere and points to the config file.
The Tricky part for phones with Extended Rom is, how the heck can we auto install from Storage Card after auto installation is done in Extended Rom. We want it to auto install from extended rom, then continue to the storage card, not just either one of them.
To auto install from Storage Card, after auto installation is done with Extended Rom, we simply have to patch the config file path with a command in Extended Rom, then EXECute autorun again. I made a cab called Set_Auto_Run which simply contains:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRunType"=dword:0
"AutoRunCFG"="\\Storage Card\\config.txt"
"AutoRun"="\\Extended_ROM\\autorun.exe"
*there's also another line that sets the autorun flag to 0.
and my Extended Rom config file looks like this:
Code:
LOCK:Enabled
CAB: \Extended_ROM\AdobeFlashLite_2_1.cab
CAB: \Extended_ROM\HTCTaskManager.cab
CAB: \Extended_ROM\Set_Auto_run.cab
Hide:Enabled
EXEC:\Extended_ROM\AutoRun.exe
LOCK:Disabled
RST: Reset
The config file in the storage card would be something like this:
Code:
LOCK:Enabled
CAB: \Storage Card\Cabs\Call_Firewall.cab
CAB: \Storage Card\Cabs\TCPMP.cab
CAB: \Storage Card\Cabs\FlashVideoBundle.CAB
CAB: \Storage Card\Cabs\Threaded_SMS.cab
LOCK:Disabled
RST: Reset
At the end of the autorun from storage card, it resets the phone. However, if one doesn't use the auto installation feature, autorun will execute the reset command in the config.txt within Extended Rom and completes the Rom Installation.
To auto Install from Storage Card to Storage Card/Windows, simply change the Cab's Path. Instruction can be found in my Rom's link.
Click to expand...
Click to collapse
To make your life easier, all you need to do is put the following lines in your config.txt in extended rom:
Code:
CAB: \Extended_ROM\Set_Auto_run.cab
Hide:Enabled
EXEC:\Extended_ROM\AutoRun.exe
LOCK:Disabled
RST: Reset
And toss in the Set_Auto_Run.cab into your extended Rom, then prepare the config.txt in storage card and you are done. If there's no config.txt in storage card, this feature is bypassed automatically.
Thank you... this feature should be in all ROMs, especially LITE ROMs, that usually take so much more time to customize
Great info mate. Worth adding a note, or link to this thread, into Matt_kr's 'Extended_ROM Consolidation' thread. I think even more people could benefit from your research that way. (Don't look it up by name, he spelled 'consolidation incorrectly in its title - it's here: http://forum.xda-developers.com/showthread.php?t=335871).
Qudos to you fella.
Related
Hi,
I upgraded my XDA 2s last week to the 1.40 Type I ROM along with the Type I Radio 1.13 and customised my Extended ROM in the 1.40 kitchen. I have been experiencing some weird problems though and wondered if anyone else had had the same things and if there is a workaround.
1) I had trouble with GPRS reconnecting but then foudn the post about changing Caller ID version so that one is sorted.
2) My bluetooth headest has gone weird on me a couple of times during calls, it suddenly adds a question mark to the headset icon in the top bar and switches the call to the phone which is quite annoying (and dangerous when driving!)
3) It seems that my settings for sounds and notifications keep going back to default, particularly my SMS tone, which is just a WAV file in the Windows directory.
4) Sometimes when i switch it on a white light comes on the screen for a second then it switches off again and has to be pressed again. A soft reset cures this normally.
I really like 1.40 apart from these irritations as I really want to keep WMP10. If anyone has any insight, I have posted the contents of my config.txt file to see if anything could be causing issues.
Thanks for any help,
Fin
EXEC:\Extended_ROM\TPDisable.exe
CAB: \Extended_ROM\BA_Version_140.CAB
CAB: \Extended_ROM\Album_BlueAngelAKU26_Generic_WWE_RC20.CAB
CAB: \Extended_ROM\IA_CallerID_1.20_WWE.CAB
CAB: \Extended_ROM\MIDI561.sa.CAB
CAB: \Extended_ROM\ClearVue2.4.381WWE_withoutBP_OzUp.sa.CAB
CAB: \Extended_ROM\Java_V10.1.2.49_BA_WWE_0901_unremovable.CAB
CAB: \Extended_ROM\CAB-MMS-2.0.0.21-BlueAngel-Generic-ENU-27Dec04.sa.CAB
CAB: \Extended_ROM\BA_OEM_PA_Remove_WiFi_Logo.sa.CAB
CAB: \Extended_ROM\BA_Camera_Driver_Patch.sa.CAB
EXEC:\Extended_ROM\TPEnable.exe
CAB: \Extended_ROM\BA_cm_rm_map_o2_v3.CAB
CAB: \Extended_ROM\O2UK_AP_09212004_BA_1.sa.CAB
CAB: \Extended_ROM\O2UK_Button9_WWE.sa.CAB
CAB: \Extended_ROM\O2UK_Connection_Setting.sa.CAB
CAB: \Extended_ROM\O2UK_Hide_WLan_message.sa.CAB
CAB: \Extended_ROM\O2UK_PIE_homepage.sa.CAB
CAB: \Extended_ROM\O2UK_Regional_TimeZone.sa.CAB
CAB: \Extended_ROM\VideoMMSB12_BA.sa.CAB
CAB: \Extended_ROM\TrayLaunch.CAB
CAB: \Extended_ROM\FINIIW.CAB
CAB: \Extended_ROM\RESCOEXPLORER.CAB
CAB: \Extended_ROM\rescoreg.CAB
CAB: \Extended_ROM\FTP.CAB
CAB: \Extended_ROM\SoftReset.arm.CAB
CAB: \Extended_ROM\RAR.CAB
CAB: \Extended_ROM\PocketMSN2K3SE.CAB
CAB: \Extended_ROM\BA ExtROM Unlock WORKING.CAB
CAB: \Extended_ROM\battery_OU_081304.sa.CAB
CAB: \Extended_ROM\install.ARM.CAB
RST: Reset
I am being tortured by the fail in re-connect gprs, could you tell me how to solve me by the 'Caller ID version' that you suggest on your post.
Best regards
Patrick Choy
xda 2s GPRS Connection Issues
mfchoy wrote:I am being tortured by the fail in re-connect gprs, could you tell me how to solve me by the 'Caller ID version' that you suggest on your post.
Hi Patrick
You have to unhide and unlock your extended ROM and replace the Caller ID cab file with older version of the same file that is available on the wiki site in the Blue Angel ROM kitchen. From memory, I believe the older version of the file you need is the one with the 14 suffix. are you familiar with unhiding ans unlocking the extended ROM?
Best Regards
Chris
Thanks Chris but I am not familiar with playing around with the ext rom, do you think there is patches out there that I can apply, otherwise, you walk me through step by step how to do it.. if it's not too troublesome.
Best regards
Patrick Choy
Instead of unlocking the ROM, can't you just copy the photo contact cab file to the phone, rename the IA*.DLL's and then execute the cab file to load the program? Obivously this will be removed after a hard reset.
1.40 Extended ROM GPRS Problems
HennyB wrote:
Instead of unlocking the ROM, can't you just copy the photo contact cab file to the phone, rename the IA*.DLL's and then execute the cab file to load the program? Obivously this will be removed after a hard reset.
Click to expand...
Click to collapse
Mmmm... that might work, although since the existing version of the program is also running, there may be some conflicts, unless you could stop it before starting the replacement... Not sure on that... "The Last One" or "Happy Goat" could probably advise if you if you PM one of them.
mfchoy wrote:
Thanks Chris but I am not familiar with playing around with the ext rom, do you think there is patches out there that I can apply, otherwise, you walk me through step by step how to do it.. if it's not too troublesome.
Click to expand...
Click to collapse
As far as I know there are no patches available at this time. We are still waiting for O2 to release their version of the 1.40 software, which will also include the Blackberry client software. Its only a 50:50 chance that their update will also contain some GPRS, Bluetooth and WiFi improvements, but I would not hold my breath....
The wiki site (wiki.xda-developers.com) is really the place where all the knowledge resides, plus the various ROMs and CABs. It explains explains all in great detail and I would encourage you to read the sections on Blue Angel. In the meatime, here are some specific links to help you step by step through the ROM unhide and unlock process.
http://wiki.xda-developers.com/index.php?pagename=BA_ERK_X_Zip
Once you have unhidden and unlocked the Ext ROM, you will be able to replace the Caller ID file with the older version (1.17), which can be fould here:
http://wiki.xda-developers.com/index.php?pagename=BA_ERK_Applications
The 1.40.147 extended ROM seems to differ from other extended ROMS in that you do not have to update a Config.txt file. You just copy in the new CAB files using the same file naming scheme as the other files in the Ext ROM. I cheated a bit here, by just renaming the older version of the file after I downloaded it (not really good CM practice but it worked for me ). So after unhiding and unlocking the ROM:
1. Download the 1.17 version of the file from the link above to a folder on your device
2. Look at the file name of the Caller ID CAB currently in the extended ROM and rename the file you downloaded to the exact same name.
3. Delete the current Caller ID CAB from your extended ROM.
4. Copy the Caller ID file you just renamed into the extended ROM.
5. Re-Lock and Re-Hide the extended ROM per the instructions at the link above.
6. Then perform a Hard Reset and the modified extended ROM file will reload. WARNING! Remember that a hard reset will ERASE all the date and 3rd party apps you currently have on your device. You will have to resynch with outlook and reload any apps you want again after the hard reset, so make sure all is backed up before you do any of this.
So that's what I did. You could try the trick that HennyB suggested first of course and see if that works. The other option is to wait for the new ROM from O2. And if you do not want to mess with the Extended ROM, but can't wait for the new O2 update, try going back to the current 1.31 ROM from O2 and installing in 'corporate mode' when prompted. The 1.31 ROM always had a very stable GPRS connection for me.
Hope that helps
Regards
Chris
Caller ID
I have done this previously. All you need to do is copy the Cab file over to you device. Typically to temp folder. Use file explorer to navigate to the Temp folder and double tap on the CallerID cab file. A window will open staing that it cannot copy IACIDSync.dll. Select cancel, and find this file in the windows directory and rename it. Go back to temp folder and double tap the callerID cab file. It then states their is a problem with another IA*.dll file (cannot recall the name). Go to windows and change the file name. this has to be done on 2-3 files. Then the cab file will finally load.
Caller ID
I have done this previously. All you need to do is copy the Cab file over to you device. Typically to temp folder. Use file explorer to navigate to the Temp folder and double tap on the CallerID cab file. A window will open staing that it cannot copy IACIDSync.dll. Select cancel, and find this file in the windows directory and rename it. Go back to temp folder and double tap the callerID cab file. It then states their is a problem with another IA*.dll file (cannot recall the name). Go to windows and change the file name. this has to be done on 2-3 files. Then the cab file will finally load.
HennyB wrote
I have done this previously. All you need to do is copy the Cab file over to you device. Typically to temp folder. Use file explorer to navigate to the Temp folder and double tap on the CallerID cab file. A window will open staing that it cannot copy IACIDSync.dll. Select cancel, and find this file in the windows directory and rename it. Go back to temp folder and double tap the callerID cab file. It then states their is a problem with another IA*.dll file (cannot recall the name). Go to windows and change the file name. this has to be done on 2-3 files. Then the cab file will finally load.
Click to expand...
Click to collapse
Sounds like this is the workaround then. Certainly seems easier than the ROM "surgery' and if you ever have to do a hard reset, you could modify the ROM then..
Regards
Chris
I have done this previously. All you need to do is copy the Cab file over to you device. Typically to temp folder. Use file explorer to navigate to the Temp folder and double tap on the CallerID cab file. A window will open staing that it cannot copy IACIDSync.dll. Select cancel, and find this file in the windows directory and rename it. Go back to temp folder and double tap the callerID cab file. It then states their is a problem with another IA*.dll file (cannot recall the name). Go to windows and change the file name. this has to be done on 2-3 files. Then the cab file will finally load.
Click to expand...
Click to collapse
Hi Henny, the rename that you say mean just change the name to something else, correct me if I am wrong about what you say. And crbrow51, you mean if I perform a hard reset, everything that I do according to Henny will be gone, isn't it.
Best regards,
Patrick Choy
I just renamed the IA* files to IA*.dlb from .dll and then executed the cab.
I am definitely running version 1.17 of the Photo Contact program but still have GPRS program. Photo contacts seems to work more reliably though.
Now I dont believe that changing the version of photo contacts will solve the radio problem.
Hennyb wroteI just renamed the IA* files to IA*.dlb from .dll and then executed the cab.
I am definitely running version 1.17 of the Photo Contact program but still have GPRS program. Photo contacts seems to work more reliably though.
Well that fix worked for me, although I did it via the extended Rom update and hard reset. Is it conceivable that a hard reset is needed to completely flush the effects of the existing Caller ID version...? Anyhow, here is a link to a thread that has some more pointers to possible GPRS connection fixes
http://forum.xda-developers.com/viewtopic.php?t=21972&highlight=
mfchoy wrote: Hi Henny, the rename that you say mean just change the name to something else, correct me if I am wrong about what you say. And crbrow51, you mean if I perform a hard reset, everything that I do according to Henny will be gone, isn't it.
Yes, if you do the workaround to bring this file in without updatinf the extended ROM, then the change is lost on a hard reset.
Regards
Chris
Removed phonealarm program (which I thought was great) and now GPRS is working flawlessly.
Not sure if changing to photo contacts helped the situation or not.
What is phonealarm?
What Is Phone Alarm?
Its a great profile and repeating audible alerts program for PPC PE devices.
You can download the trial at
www.pocketmax.net
try AlarmToday by the same developer. Great products, first class support.
Also, as an aside, i have both working on my device with no GPRS problems. My bet is that the caller id cab file downgrade fixed the problem as it di for me ;-)
Regards
chris
Also, as an aside, I have both working on my device with no GPRS problems. My bet is that the caller id cab file downgrade fixed the problem as it di for me
Click to expand...
Click to collapse
GPRS on my phone even with the caller ID downgrade did not work properly until Phonealarm was uninstalled.
I believe the compatibility problem is with the new O2 Asia 1.40 ROM. Users have reported the same problem on the Pocketmax.net forum for phonealarm.
http://www.pocketmax.net/phpbb2/viewtopic.php?t=565
Mmm.. interesting... Which version of PhoneAlarm are/were you using? I had trouble with 1.20 and went back to 1.13... I was thinking of moving to the O2 Asia ROM, to see if there were any improvements to bluetooth connectivity. Guess I could do that and use O2 Plus instead of PhoneAlarm... Thoughts..?
Regards
Chris
Re: What Is Phone Alarm?
cbrow51 said:
Its a great profile and repeating audible alerts program for PPC PE devices.
You can download the trial at
www.pocketmax.net
try AlarmToday by the same developer. Great products, first class support.
Also, as an aside, i have both working on my device with no GPRS problems. My bet is that the caller id cab file downgrade fixed the problem as it di for me ;-)
Regards
chris
Click to expand...
Click to collapse
Thanks
Mmm.. interesting... Which version of PhoneAlarm are/were you using? I had trouble with 1.20 and went back to 1.13... I was thinking of moving to the O2 Asia ROM, to see if there were any improvements to bluetooth connectivity. Guess I could do that and use O2 Plus instead of PhoneAlarm... Thoughts..?
Click to expand...
Click to collapse
I was using 1.22 and the new Asia ROM.
I do not use bluetooth but one of my friends does and said that the older ROM with the bluetooth patch is better than the new 1.40 Asia ROM.
I had a same issue with GpRS not being able to reconnect. Drove me nuts as we use mobile mail to our devices.
Installed the older called id cab (1.17) (just renamed one file) and now its all good.
Also my XDA2s now does not freeze when gprs is reconnecting.
Thanks!
Hi All,
I have unlocked my MDA Pro extended ROM. I am currently on T-mobile and copied all my files to my storage card and then PC.
I have decided what files I want to keep.
Do I simply modify the config file ie delete the files I have deleted? and re save it.
Do I still require the auto executable file??
I thought I read somewhere that the pocket PC will try to run all files in extended ROM??
I copied my required files, modified config file and auto file to extended ROM and hard resetted - I think I got an error and I had to 'run' each file in turn??
Did I miss something??
Cheers
John
The error I get when I run AutoRun.exe is
\Extended_ROM\Default_Backg does not exist!
Any ideas why I get this error????
The Files I have in my extended ROM are:
AutoRun.exe
config.txt - see below
WiFiTempON.exe
WiFiTempOFF.exe
Shorcut-MMS1-JAVA6XX-CV-VOICE-EmailWiz-TMO-03Nov05.CAB
Signed_UNI_TMO_Connection_112100.CAB
Signed_UNI_TMO_Setting_111100.CAB
Signed_UNI_TMO_WiFi_SSID.sa.CAB
TMO_pIE_HardKey_0810_Signed.CAB
UNI_BrowserPerformance.sa.CAB
config.txt file is as follows:
LOCK:Enabled
EXEC:\Extended_ROM\WifiTempON.exe
CAB: \Extended_ROM\Signed_UNI_TMO_WiFi_SSID.sa.CAB
EXEC:\Extended_ROM\WifiTempOFF.exe
CAB: \Extended_ROM\Signed_UNI_TMO_Connection_112100.CAB
CAB: \Extended_ROM\UNI_BrowserPerformance.sa.CAB
CAB: \Extended_ROM\Signed_UNI_TMO_Setting_111100.CAB
CAB: \Extended_ROM\CAB-Customization-TMUK-Universal-01-05-16NOV05XML.CAB
CAB: \Extended_ROM\Shorcut-MMS1-JAVA6XX-CV-VOICE-EmailWiz-TMO-03Nov05.CAB
CAB: \Extended_ROM\TMO_pIE_HardKey_0810_Signed.CAB
LOCKisabled
RST: Reset
I am running the LVSW 3.30.2.1 version of WM6. The hack for WM5 in the wiki (http://wiki.xda-developers.com/index...ermes_Registry) does not work in this version. Does anyone know how to relocate the IE cache to a storage card in WM6?
Thanks!
try sktools or pocketmechenic. it works for universal running wm6
This hack from http://wiki.xda-developers.com/index.php?pagename=Hermes_Registry (1/2 way down the page) does work for Hermes variants on WM5/WM6 such as Cingular/The New AT&T/AT&T 8525 (my backup phone) and Softbank X01HT (my primary phone) (I made a registry entry for it but of course, I use my login name such as \Storage Card\LoginName\Profiles\Temporary Internet Files, etc).:
PocketIE Cache in storage card
Create these folders:
\Storage Card\Pocket IE\Temporary Internet Files
\Storage Card\Pocket IE\Cookies
\Storage Card\Pocket IE\History
Add the following registry keys, string data type:
[HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"Cache"="\Storage Card\Pocket IE\Temporary Internet Files"
"Cookies"="\Storage Card\Pocket IE\Cookies"
"History"="\Storage Card\Pocket IE\History"
You then would need to do soft-reset to get the new folders to work.
CES1951 said:
I am running the LVSW 3.30.2.1 version of WM6. The hack for WM5 in the wiki (http://wiki.xda-developers.com/index...ermes_Registry) does not work in this version. Does anyone know how to relocate the IE cache to a storage card in WM6?
Thanks!
Click to expand...
Click to collapse
PIE on Storage Card
Custel's WM6 has HTCustom (and other's like Pimp My Black) have options to change the location of PIE cache to the MicroSD card.
Just run HTCustom
Select the Pocket IE tab
and choose SD Card (or Main Memory)
Save will SoftReset your device
Be careful with the D-Pad option on the same screen. Some people don't like the way that changes the behavior of PIE as well as message reading.
Mark
crazyut said:
. . . I made a registry entry for it but of course, I use my login name such as \Storage Card\LoginName\Profiles\Temporary Internet Files, etc. . . .
Click to expand...
Click to collapse
Thanks, crazynut. The trick is in the registry string. This ROM includes reg strings as in the wiki and your reply, with the default path "\windows\Profiles\guest\*" I verified that that is the location where the cache files were stored and then tried changing that to "storage card\Profiles\guest\*" and modifying folder names on the storage card to match followed with a soft reboot. It didn't work, either. Could you spell out what you did in more detail?
CES1951 said:
Thanks, crazynut. The trick is in the registry string. This ROM includes reg strings as in the wiki and your reply, with the default path "\windows\Profiles\guest\*" I verified that that is the location where the cache files were stored and then tried changing that to "storage card\Profiles\guest\*" and modifying folder names on the storage card to match followed with a soft reboot. It didn't work, either. Could you spell out what you did in more detail?
Click to expand...
Click to collapse
N00b download one of the tweak tools either pimp my black V2.0 or Htcusom 1.4 and it will set the reg for you and your done.... no reg hacks no nothing just some clicking on the screen...
It works as in the wiki. I am not sure what Registry Editor you are using. You should be able to use Total Commander or a similiar product. I think a lot of people like PHM Registry Editor. I use Kilmist Registry Editor since I got my company to pay for it.
That being said, AustinSync said in another post that you can use one of the tweaking tools to click the location to the storage card (my experiencde with doing that tells me that they just do not let you choose which folder on the storage card).
Good luck.
Cheers
CES1951 said:
Thanks, crazynut. The trick is in the registry string. This ROM includes reg strings as in the wiki and your reply, with the default path "\windows\Profiles\guest\*" I verified that that is the location where the cache files were stored and then tried changing that to "storage card\Profiles\guest\*" and modifying folder names on the storage card to match followed with a soft reboot. It didn't work, either. Could you spell out what you did in more detail?
Click to expand...
Click to collapse
So here's the scoop. You got this killer rom, but it loads a whole bunch of stuff that you don't want. You get around this by resetting before the configuration starts after aligning the screen.
You might have a host of cabs that you always load, and after you flash you need to run each one. Every rom you use it's the same thing - flash the rom, then load all your cabs.
Or, you may have a program you want to execute, such as enabling SetHSDPA.
Here's a way to "automate" it so you can use the power and flexibility of the PreConfig funtion as an "after the flash" customization tool, and make subsequent installations much faster.
You'll need a folder on your storage card called CABS, and in that folder put the attached file called CFG.txt as well as the cabs / exe's etc (unless they're already in the ROM, then just point the config file to the correct path) that you want to run. The CFT.txt is the file that will tell it what to install, and is exactly like the PreConfig.txt file - see my extended rom thread for ideas on what you can do with it.
Basically, here's the contents of the CFG.txt file I attached:
LOCK:Enabled
CAB: \Storage Card\CABS\A2DPFix.CAB
CAB: \Storage Card\CABS\ATIFix.cab
CAB: \Storage Card\CABS\Cingular_WAP_MediaNet_MMS_Settingsv2_No_ICON_Change.cab
CAB: \Storage Card\CABS\Google Maps Cell.CAB
CAB: \Storage Card\CABS\Monopoly.cab
CAB: \Storage Card\CABS\NETCFv2.wm.armv4i.cab
CAB: \Storage Card\CABS\S2U2-0.72-WM5.cab
CAB: \Storage Card\CABS\Solitare.cab
CAB: \Storage Card\CABS\StartClean.cab
LOCKisabled
RST: Reset
Just list out your cabs or actions in this file - and be sure the files you are referring to are in the destination path.
To use this setup:
Edit the CFG.txt file and place in \Storage Card\CABS (if the folder isn't there, create it)
Copy your cabs/exes into this folder, being sure they are set to READ ONLY.
Install the attached cab, and after you reset it'll start the installation!
Once the installation is complete and the phone resets - you can remove the program from Settings-Remove Programs.
Important Notes:
Don't forget to make your CABs READ ONLY - or they'll delete after installing. YOU HAVE BEEN WARNED!!!
Ensure that the cabs you're installing does not require any user input. If it does, it will hang the installation process, you'll need to reset the phone, and not all of your stuff will get installed.
Known list of NOT COMPATIBLE files:
MS Reader
Sweet bro!!! I am all over it, will give it a go and let you know my results!!! Very cool stuff!
You Rock!
Downloading Now!
Can I put this on My Treo?
berdinkerdickle said:
You Rock!
Downloading Now!
Can I put this on My Treo?
Click to expand...
Click to collapse
sure, if it's WM5/6.
mattk_r said:
sure, if it's WM5/6.
Click to expand...
Click to collapse
Jokes on Me.
Seriously Though,
This is Great!
mattk_r said:
...clip...
Ensure that the cabs you're installing does not require any user input. If it does, it will hang the installation process, you'll need to reset the phone, and not all of your stuff will get installed.
Click to expand...
Click to collapse
We do want to be sure not to use apps that require a reset.
great! That's what I was looking for recently
Is there a way to get cab files to default to installing on a Storage Card? I'm trying to prevent it from asking me where I want to install it and thus causing this tool from hanging up.
Nevermind, I made a bad assumption (yes, I know what they say about assuming things) that the PreConfig Launcher would hang up waiting for input for where to install something. I just tested it out on a cab that allows a user to override the installation directory and everything worked fine.
Sorry.
kc_hubbard said:
Is there a way to get cab files to default to installing on a Storage Card? I'm trying to prevent it from asking me where I want to install it and thus causing this tool from hanging up.
Nevermind, I made a bad assumption (yes, I know what they say about assuming things) that the PreConfig Launcher would hang up waiting for input for where to install something. I just tested it out on a cab that allows a user to override the installation directory and everything worked fine.
Sorry.
Click to expand...
Click to collapse
You could edit your cabs and have them install to the storage card by default - or at least I think you could. I'm thinking something like %storage card%. If I get a chance I'll poke around WinCE Cab Manager and see if it's possible.
I just tested it by building a cab to install to the folder /Storage Card, and it worked fine.
mattk_r said:
I just tested it by building a cab to install to the folder /Storage Card, and it worked fine.
Click to expand...
Click to collapse
Matt,
While I'm not quite the noob the number of posts would indicate I am, I admit that I haven't done much w/ building cab's. In an attempt to build one to install directly to the storage card, I've used WinCE to alter the default directory and have altered _setup.xml file, both to no avail.
While my pride says not to ask you to tell me how you set the cab up to install to storage, I'm not above asking you to post the example you created to test this so that I can look it over and try to figure this out for myself.
Would you mind attaching a cab file that installs directly to storage for me? Please?
kc_hubbard said:
Matt,
While I'm not quite the noob the number of posts would indicate I am, I admit that I haven't done much w/ building cab's. In an attempt to build one to install directly to the storage card, I've used WinCE to alter the default directory and have altered _setup.xml file, both to no avail.
While my pride says not to ask you to tell me how you set the cab up to install to storage, I'm not above asking you to post the example you created to test this so that I can look it over and try to figure this out for myself.
Would you mind attaching a cab file that installs directly to storage for me? Please?
Click to expand...
Click to collapse
I could - but this is super easy. When you add a file, you get a window with three tabs, one being location. In that tab, you'll have the folder view. Click on the root '/' folder and press 'new folder'. Call it Storage Card.
That's it!
mattk_r said:
I could - but this is super easy. When you add a file, you get a window with three tabs, one being location. In that tab, you'll have the folder view. Click on the root '/' folder and press 'new folder'. Call it Storage Card.
That's it!
Click to expand...
Click to collapse
I must be an idiot to not have been able to figure that out (and my day job is computer programming, albeit on IBM Mainframes). Will work on this again once I'm back home. I'm sure big brother is already not too happy w/ all the time I spend on the forums anyway.
Thanks Matt!
so, if i were flashing a ROM i would flash, install the cab and then, assuming i already have my cabs and config files on my card, i hard reset and this should launch ok?
thanks,
mark
AximMarkSD said:
so, if i were flashing a ROM i would flash, install the cab and then, assuming i already have my cabs and config files on my card, i hard reset and this should launch ok?
thanks,
mark
Click to expand...
Click to collapse
From what I've done/learned no hard reset is required. You install the Pandora PreConfig Launcher and let your phone Restart. When it restarts, your cabs in the CFG.TXT file will be installed.
so after a flash or a hard reset (for whatever reason) you just install the cab and then soft reset and it will install your cabs?
AximMarkSD said:
so after a flash or a hard reset (for whatever reason) you just install the cab and then soft reset and it will install your cabs?
Click to expand...
Click to collapse
correct - as long as your cabs and the configuration file reside in the CABS folder on your storage card
mattk_r said:
correct - as long as your cabs and the configuration file reside in the CABS folder on your storage card
Click to expand...
Click to collapse
right.
thanks. that's a great tool.
pardon the ignorance but i've never played w/ the WinCE cab manager. can i change the default install location on commercial cabs that i've purchased (assuming they require no interaction during install)?
AximMarkSD said:
right.
thanks. that's a great tool.
pardon the ignorance but i've never played w/ the WinCE cab manager. can i change the default install location on commercial cabs that i've purchased (assuming they require no interaction during install)?
Click to expand...
Click to collapse
Yes you can change the default install directory.
Matt,
Thanks for this great program. It makes changing roms SOOO much easier!! When combined with WinCE cab manager, you can autoinstall just about any program. This thread should be stickied.
Quick guide on how to get programs to install to storage card used WinCE Cab Manager. This guide was modified from K's FlexiRom instructions:
Preparing the cabs
---------------------------
- To set the cabs to a static path, install WinCECab Manager.
- Open a cab with WinCE Cab Manager and click on "CAB Information".
- Double click on "Default Install Dir" then select "Installation Directory"
- Change the default install directory to what every use desire. Do this by creating new directories under "/". For most users wanting to install on storage card, change path to "/Storage Card/Program Files/cabname". Before moving on to the next step, make sure that once you make the folders, click the desired installation path and click "APPLY".
- After applying the new default installation path, choose "Do not allow user to select installation directory"
- Check if there "Setup dll" is present under Cab Information. If setup dll is present, delete it off. [this step is from K's instructions, not sure if it is necessary or not. I've been doing it.]
- Save the cab then right click on the can and select "Read Only" and click apply/OK.
- Check and prepare all the cabs you want to auto install and place them into the CABS Folder of your storage card.
PS Using WinCE Cab manager, you can also modify the shortcuts of the program.
this is last sdconfig (to start at first reset, after rom flashing) and its tools packaged for rom cokkoer.
if you use my kitchens only have to add it into \sys or \packages folder, if use other kitchen:
edit config.txt into "\OEM\OEMOPERATORS" folder, adding this value just before
LOCK: Disabled
RST: Reset
the string:
CFG: \windows\sdconfig.txt
so you have
xxxxxxxx
xxxxxxxx
CFG: \windows\sdconfig.txt
LOCK: Disabled
RST: Reset
in your config.txt file
while the tool is stored into "personal" tab on settings, and under windows mobile you can access it every times you want.
sdconfig (not tool) at 1st startup, and before config.txt will be execute, search for all: cabs provxml and tsk files into:
\storage card\Cabs\ folder, if found populate in \windows\ the file called "sdconfig.txt", and install at costumization, all it found inside...
if not,(if doesn't found the \storage card\cabs\ folder) create a blanch \windows\sdconfig.txt"
the programs is able to automatic recognize of "storage card or scheda di memoria etc.. and esecuzione automatico or startup folders, no more need it sdconfig.ini!!!
bye!
new version, same but changed icons, so maybe someone can be happy seeing icon present and doesn't change the icon or delete my sign inside my appz!!!
what is sdconfigtool ? lol
simkard said:
what is sdconfigtool ? lol
Click to expand...
Click to collapse
sdconfig:
is used to install all cabs you want at 1st reeboting when you ppc goes to costumizing (you need: sd card inserted and a directory into sd called "\cabs" and into \cabs folder some cabs present!)
sdconfig tool:
if you want install more cabs in one step, the tools search for all cabs, provxml and tsk present into sd card and its subfolder, list all them to you, and you can choice al them you need and want install, the tools install all them for you, one step one, you can also choice for each cab where istall it, into system or into storage card!