[UC]XDA_UC V2.RC1, Automated & Silent User & Cook, Configuration Service[14/05/10]

My Preferred Method is

  • 1 Full XDA_UC Method, Full XDA_UC without RunCC or SDAutorun

    Votes: 17 51.5%
  • 2 Semi XDA_UC Method, XDA_UC at second boot after RunCC has run at first boot.

    Votes: 7 21.2%
  • 3 Method 3 Legacy Out Of The Box

    Votes: 9 27.3%

  • Total voters
    33
  • Poll closed .
Search This thread

Noonski

Inactive Recognized Developer / Moderator Emeritus
Apr 18, 2005
5,326
149
Amsterdam
noonski.nl
[UC]XDA_UC V2.RC1, Automated & Silent User & Cook, Configuration Service[14/05/10]


Another (The?) new way to implement User Customization and Cooking.

This Thread is meant for Rom Cooks.
Users should take a look at the User To User Tips, Tricks ideas and issues thread.

What the XDA UC service does, is silently install (or not so silently if needed by User), .cab, .xdas, .xml, .reg, .mscr, copy over user manila files, install files from SDconfig.txt if wanted and then a few extra's for the freaks like copying folders or creating shortcuts from specific registries. This happens either at first or second boot depending on the existence of either RunCC.exe or Autorun.exe in rom.


It's all Mortcsript so it's very easy to get a grasp of it and change the behaviour and or Chip in adjustments/improvements.
But no knowledge of mortscript is needed to implement
It Uses DotFred's Taskmanager to parse and implement the .reg and .xml files. But it can also be used to disable or enable services or register DLL files.

More Information about the XDA Type Files at:

http://wiki.xda-developers.com/index...ename=XDA_file

My Shout out for this Two Year Long Evolving Collaborating Endeavour go to:
Bengalih (that has a very similar UC variant called Sashimi and helped with some of the early scripts I was trying to do with mort while cooking, I wish I could have collaborated more with him, it would have saved time re-inventing the wheel), RoryB for bouncing back ideas, supplying new scripts and perfecting older ones, serfer222 For making the script compacter, jmckeejr, Ameet & the whole Digital XDA SPC Cooking Crew, bbobeckyj, CLHatch, Scinor, Mort, Sleuth255, McCune, DotFred, MrVanx, danny_and_2, Cmonex, utak3r, Laurentius26, Radimus, and the Whole Original SPC Crew for accepting my obsessions.
For Knowingly helping me get the information, unknowingly helping me get the information or motivated me in keep going on in my Quest resulting in this.

If I Forgot you, Forgive me.
If you feel that certain information that has been used originated by you give me a holler and I will credit you if this is so.

Before you consider buying me a beer. Please consider Donating to XDA to help out with the maintenance of the forum and get cool stars next to your Nickname showing your appreciation. Then there are always the people that without their apps this wouldn't have been possible at all that you can consider showing some love. Mort, DotFred & Sleuth255 All of whom made Apps Seemingly simple But oh so useful for the whole XDA and PocketPC community.

Download and Info in next Post
 
Last edited:
  • Like
Reactions: ai6908 and aaurnab

Noonski

Inactive Recognized Developer / Moderator Emeritus
Apr 18, 2005
5,326
149
Amsterdam
noonski.nl
What this version of the XDA UC service does, is silently install and execute (listed in the order the items get installed)
  1. Run the Users customisations of course.
    User side information here...
  2. Run Cook.mscr in Windows folder(For Cooks Only)
  3. More Cook info coming.

  • Add native support for .mscr, .mortrun, .xda, xdai, xdas & .xdaz files
(Where in "\Storage Card\" is read from HKLM\System\StorageManager\Profiles\SDMemory For MultiLanguage Support)


Requirements

  • The Rom should have the security relaxed in HKLM\Security\Policies\Polices by setting the value 0000101a to a 1.
    So unsigned installations and Mortscript do not give a security error.
  • If you have a different language then English, don't forget to change the path in the initflashfiles.txt/app.dat file (if your using legacy kitchen ;))
    The rest of the script should dynamcliy get the correct variable for the storage location.
In the end the process it comes down to the device starting after flashing and not needing any reboot while silently installing Cook and User configurations.

On the User end and cook end no SDConfig.txt ort config.txt file is needed.

Attached the OEM Package and a Sample Package for SD.
(Klaxon.Cab, GoogleMaps.xdas, two .reg files, two xml files, my.tsk, and a test mortscript)

The Control factors of the Sample SD Package is that is should install
HKLM\Software\XDA\Test\Reg 1 Parsed=1
HKLM\Software\XDA\Test\Reg 2 Parsed=1
HKLM\Software\XDA\Test\xml1parsed=1
HKLM\Software\XDA\Test\xml2parsed=1

These are the tweaks present in those files.

In addition everything installed will be found under
HKLM\Software\XDA\UC\

And the Morscript in the sample SD Card Package should give a message to confirm it was executed "Mort UC From SD Working"

Cab Files and XDAS files should eventually just be in the startMenu Programs.
G-Alarm is there because it needs User interaction and that will pop up when it needs your attention.

At the end of it all you get a message Installations have finished.

When using SDConfig.txt be sure to add a blank line at the end of it.

Disclaimer:
Please be aware that the XDA_UC script contains a disclaimer, not to post errors with it to the Mortscript forums, and the usual this **** cloud be dangerous to your phones health.

For Standalone version, place XDA_UC folder from "User_Storage Card" on Storage Card.
Then run "\Storage Card\XDA_UC\Install\XDA_UC.exe"
 

Attachments

  • PACKAGE_XDA_UC_1_0_0_5.zip
    393.6 KB · Views: 2,036
  • PACKAGE_XDA_UC_1_1_0.zip
    394.6 KB · Views: 4,521
Last edited:

Noonski

Inactive Recognized Developer / Moderator Emeritus
Apr 18, 2005
5,326
149
Amsterdam
noonski.nl
Changelog:

V 1.0.01

  • Changed Sleep to start UC to 50 seconds for full device Boot before UC starts.
  • Changed "XDA UC Service Start" title to "customization" to match the old one.
  • Changed sleep before completion message to ten second in case the last cab needs user input and the Completion message pops up to early.
  • Changed Sleep at while for Theme installation to 2 seconds.
V 1.0.02:

  • Added Copy1 to Copy2 by reading from registry settings
    [HKLM\Software\XDA\DirCopy]
    "\\Storage Card\\Some Folder"="\\My Documents\\Some Folder"
  • Added Disabling Manila from Homescreen then Copying files from "\Storage Card\XDA_UC\manila" to Windows, The checking for existence of wallpaper_TF3D.png or wallpaper_TF3D.jpg and adding that to
    [HKCU\Software\HTC\Manila]
    "HomeBackgroundPath"="\\Windows\\wallpaper_TF3 D.jp g"
    Import registry files from "\Storage Card\XDA_UC\manila\manila.reg"
    Re-enable Manila on Homescreen and redraw it.
    If not present do nothing.
  • Added RoryB's Complete SDAutorun.exe replacement/SDConfig.txt parser script.
  • Check for existence of Autorun.exe or RunCC.exe to automatic determine which method/bootcount to use.
    There is no longer the need for two separate XDA_UC versions let alone a third.
  • .reg and .xml files will no be sent to renamed taskmanager "FS_TaskMgr.exe"
  • Added checking for cab files in "\Storage Card\XDA_UC\SD\", for those that don't have the luxury of changing the install paths in a cab file to hardcode these to Storage Card. So you get full user input to choose on these cabs.
V 1.0.03:
Todo's
Add Support For Diamond Internal Storage Need Someone with a Diamond to Test.
V 1.0.04:
Added Support for PimPackup files *.pib & .cer files.
Moved Disclaimer to the beginning and added an option to reset ad the end.

V 1.1.00:
Added extra Runs for Diamond and Samsung Internal Storage.

V 1.1.1B2:
Applied script improvements to reduce code used and make script a bit faster.
Removed Manila folder copy and replaced it with more general Copy2Root function/folder.
Added recognition of "REG: " command in SDConfig.txt parsing.
Added recognition of "CER: " command in SDConfig.txt parsing.
Testing:
Code:
If( FileExists( "\" & SDF & "\Cabs\pim.vol" ))
        Kill("cprog.exe")
      EndIf
During SDConfig.txt just before cpy1, cpy2 function.

V 1.1.1B3:

  1. Mayor overhaul by new script from Serfer222
  2. And then I started adding more crap and messing the new clean code up.
  3. XCP1 & XCP2 commands for SDConfig.txt (Folder Copy with SDConfig.txt)
  4. MCAB command for SDConfig.txt (Cabs that you want manual input for during SDConfig.txt)
  5. SCAB command for SDConfig.txt (Cabs that you want installed to SD SemiAutomaticly during SDConfig.txt)
  6. SC1 & SC2 commands for SDConfig.txt (Shortcut creation with SDConfig.txt)
  7. KILL command for SDConfig.txt (Kill a running .exe/process)
  8. EXEC: command for SDConfig.txt (Was already present but i removed the checking if the file is a .exe so anything can be executed and)
  9. Del: Command for SDConfig.txt
  10. .PROVXML now also get parsed in XDA_UC folder
  11. Changed Serfer222's fix to parse mail xml files before PimBackup to "*mail*.*xml" so now if there's a file containing mail anywhere or is a .provxml get's parsed before PimBackUp.
  12. RESET command for SDConfig.txt
  13. WR1: & WR2: commands to write files using SDConfig.txt
  14. Parse File containing "WiFi in it's name" Early like MyHomeWiFi.xml or MyHomeWiFi.provxml
  15. Add a script to run and add XDA_UC to rom's without it.
  16. "Manual" Folder in XDA_UC folder for Full Manual .cab Installs
  17. "Storage Folder in XDA_UC folder for Semi Silent .cab installs to Storage
  18. Early "*wifi*.*xml" parsing from XDA_UC for quick Wifi connecting.
  19. Eauh maybe i forgot some stuff....
Bug Tracker for last Beta.
Wrong code for the WR1: & WR2: commands (Updated Beta Download with Fixed Script)
WR1: command needs a delete or else the next time it is run it will add text to the file instead of write a new one. Working on Fix. Fix Updated in original Download.
Changed XCP1: XCP2: commands into MOV1: & MOV2: to avoid confusion with CPY1: & CPY2: (TNX RoryB good one) Updated in original Beta Download.

Other Updates I'm looking into All Beta:

  1. Changed Manila/Sense Script so it now Checks for manila.reg @ "\Storage Location\XDA_UC\Copy2Root\Windows\manila.reg" and runs the reg from there.
  2. Test everything again ;)
  3. More optimisation of the code suggested by Serfer222
  4. Call for Sashimi & PresetInstaller, so having Making an XDA UC Rom doesn't force users switching their preferred UC Setup.
  5. Add DELT: command
  6. Config.txt for Cooks (May not be included as it is partly redundant)
 
Last edited:

RoryB

Inactive Recognized Developer
Sep 4, 2008
2,920
764
Lexington
SDAutorun replacement without SDAutorun.exe

Information will be added about this in the future.

Some more changes to my method I thought I would share.


Run the items in SDConfig.txt without using SDAutorun. I do not have any tsk to run, but it would work the same. I put copy first since some EXECs like xcopy need to be copied before execution.

Code:
###############################
# SDConfig without SDAutoRun
###############################
; Wait 10 seconds to start to be sure SDCard can be accessed
Sleep( 10000 )
If( FileExists( "\Storage Card\SDConfig.txt" ))
  xcount = ReadLine( "\Storage Card\SDConfig.txt" )
  While( IsEmpty( xcount ) = FALSE )
    If( SubStr( xcount, 1, 5 ) eq "CPY1:" )
        xcopy1 = SubStr( xcount, 6 )
        xcount = ReadLine( "\Storage Card\SDConfig.txt" )
        If( SubStr( xcount, 1, 5 ) eq "CPY2:" )
          xcopy2 = SubStr( xcount, 6 )
          Copy( xcopy1, xcopy2, TRUE )
        EndIf
    ElseIf( SubStr( xcount, 1, 5 ) eq "CAB: " )
        RunWait( "\windows\wceload.exe", "/nodelete /silent " & [COLOR=blue]"""" & [/COLOR]SubStr( xcount, 6 ) [COLOR=blue]& """" [/COLOR])
        While( ProcExists ( "wceload.exe" ))
          sleep( 3000 )
        endwhile
    Else[COLOR=red]if[/COLOR]( SubStr( xcount, 1, 5 ) eq "EXEC:" )
        If( SubStr( xcount, -[COLOR=red]3[/COLOR] ) [COLOR=red]eq[/COLOR] [COLOR=black]"[/COLOR][COLOR=red]exe[/COLOR][COLOR=black]"[/COLOR] )
          Run( SubStr( xcount, 6 ))
        EndIf
[COLOR=red]  ElseIf( SubStr( xcount, 1, 5 ) eq "XML: " )[/COLOR]
[COLOR=red]      RunWait( "\windows\TaskMgr.exe", "/provxml " & SubStr( xcount, 6 ))[/COLOR]
[COLOR=red]      While( ProcExists ( "TaskMgr.exe" ))[/COLOR]
[COLOR=red]        sleep( 3000 )[/COLOR]
[COLOR=red]      endwhile[/COLOR]
[COLOR=red]  ElseIf( SubStr( xcount, 1, 5 ) eq "TSK: " )[/COLOR]
[COLOR=red]      RunWait( "\windows\cusTSK.exe", SubStr( xcount, 6 ))[/COLOR]
[COLOR=red]      While( ProcExists ( "cusTSK.exe" ))[/COLOR]
[COLOR=red]        sleep( 3000 )[/COLOR]
[COLOR=red]      endwhile[/COLOR]
    [COLOR=red]Else[/COLOR]
    EndIf
    xcount = ReadLine( "\Storage Card\SDConfig.txt" )
  EndWhile
EndIf
I have a mortscript I call user_C.mscr for some customizations that I used EXEC to run, but thought this way people could have multiple scripts.
Code:
If( DirExists( "\Storage Card\SDAUTO" ))
 ForEach xscriptfile in Files( "\Storage Card\SDAUTO\*.mscr" )
    CallScript( xscriptfile )
    sleep( 3000 )
 EndForEach
EndIf
Lastly, I have this final folder to hold cab files I want to install with user input. It also has a script to cleanup a few things from the cab install.
Code:
If( DirExists( "\Storage Card\SDAUTO\Final Files" ))
 ForEach xcabfile in Files( "\Storage Card\SDAUTO\Final Files\*.cab" )
    Runwait( "\Windows\wceload.exe", "/nodelete " & [COLOR=blue]"""" & [/COLOR]xcabfile [COLOR=blue]& """"[/COLOR] )
    While( ProcExists ( "wceload.exe" ))
       sleep( 3000 )
    endwhile
 EndForEach
 ForEach xscriptfile in Files( "\Storage Card\SDAUTO\Final Files\*.mscr" )
    CallScript( xscriptfile )
    sleep( 3000 )
 EndForEach
EndIf
I had to set config.txt to hide the overlay image and not lock the screen to allow seeing the messages and responding to them. Eventually I see this changing to have the first script copied to start up folder by an initflashfile and not even need AutoRun. Currently config.txt starts the mortscript and does nothing else.
 
Last edited by a moderator:

Noonski

Inactive Recognized Developer / Moderator Emeritus
Apr 18, 2005
5,326
149
Amsterdam
noonski.nl
Cook.mscr

If your cooking and want your own mortscript to also be run at first boot just name it cook.mscr and put it into Windows folder.

Update: From Version 1.2.0 Cook.mscr will be executed at the same moment as the rest of XDA_UC, so this is depended on if RunCC or Autorun is used.
 
Last edited:

trinode

Senior Member
Jul 13, 2007
356
2
Suggestion:
install the cabs in a known order, perhaps alphabetically, so that we can name the files in the order to install like so

10_MSVC.CAB

20_PIMBackup.Cab
etc means we can control the install order.

:D
 
Last edited by a moderator:

Noonski

Inactive Recognized Developer / Moderator Emeritus
Apr 18, 2005
5,326
149
Amsterdam
noonski.nl
Reason I chose not to use the known "Cabs" folder is not to screw with that configuration.
(XDA_UC is backwards compatible with SDAutorun v2 SDConfig.txt)

Cabs will be automatically be parsed alphabetically that's a default when more cab's are being processed.


At least I think so
;)
It's using MortScripts ForEach File command.

Almost Everything processed will be written to registry under.


HKLM\Software\XDA\UC


And no more hassle with cabs that need user interaction.


You just interact when they come up.


If it's a good idea I could also make it check for a present Welcomehead.png or the Existence of a TF3D folder to copy over personal TF3D files.


Uploaded the OEM and a Sample SD Test Package.
 
Last edited:

Noonski

Inactive Recognized Developer / Moderator Emeritus
Apr 18, 2005
5,326
149
Amsterdam
noonski.nl
Yes there is.
There's a few different solutions.
I have added your request to the first Posts.

It runs at second boot and skips a few things that RunCC takes care of like installing cabs present in the windows folder.


This way you can keep everything is with RunCC and the welcome.lnk in initflashfiles.dat


Personally I prefer the First method with no reboots at all but it does require some extra meddling in the Rom.
 
Last edited:

Noonski

Inactive Recognized Developer / Moderator Emeritus
Apr 18, 2005
5,326
149
Amsterdam
noonski.nl
I have yet to get a hold of the version l3v5y's using.


Yes RunCC can but it needs configuration. Now for a cook that isn't any problem. But for Simple users all they need to do is drop some cabs and tweaks they have collected throughout the forum into a folder not be annoyed by.
 
Last edited:

chavonbravo

Senior Member
Jul 15, 2006
408
3
I posted a rom already that has runcc installing from sdcard's config.txt. Not too difficult at all, wonder why more cooks don't figure it out.
 
Last edited by a moderator:

Noonski

Inactive Recognized Developer / Moderator Emeritus
Apr 18, 2005
5,326
149
Amsterdam
noonski.nl
Because Earlier releases of RunCC from leaked roms did not except these commands.

I have just extracted a version of it from an official Rom and it's got the same version i was using before 1_0_9_0


So weird that it is now accepting it.


But looking back i did not use the addrun("RunExtra"


I did try the Run customer, and default tho.

(Slaps in his forehead)

But it's still not the same as i'm trying to offer here.
 
Last edited:

l3v5y

Retired Senior Moderator
Sep 13, 2007
7,485
44
29
Bristol
Because Earlier release of RunCC from leaked roms did not except these commands.

I have just extracted a version of it from an official Rom and it's got the same version i was using before 1_0_9_0


So weird that it is now accepting it.


But looking back i did not use the addrun("RunExtra"


I did try the Run customer, and default tho.

(Slaps in his forehead)

But it's still not the same as i'm trying to offer here.


What you're trying to offer here is IMHO a far better solution!
:)

Sorry for not getting you my tweaked package, though you seem to have managed without...


I think having a complete solution, with automated install of all cabs in a folder would be great.
:)
 
Last edited by a moderator:

Noonski

Inactive Recognized Developer / Moderator Emeritus
Apr 18, 2005
5,326
149
Amsterdam
noonski.nl
Well i also needed to Scour the new Roms for some updated OEMS and i needed to know for sure that welcomehead.192.png was named that way to add it to the process.

And maybe even a Copy User Preferred Manilla files from SD to device if present. There must be some other good ideas from people that like flashing, but are tired of installing their preferred skins, settings and Apps.


Unfortunately i found that the newer package of Connectionsetup asks for a reset where my previous VGA reskinned package did not.

All the Regs are te same (Except for two new unrelated ones).
I like the old non rebooting version better.
I know that a reboot isn't needed but i can see users unkowingly agree to that reboot. (But that's another subject)

I think i will change the package this weekend So it is only one method.

By default it is set to run at second boot, but it can easily be changed by the cook to run at first boot if that is the setup that one would prefer.

Also i'm still tinkering out the exact form of the XDA files.


But nice to hear i'm not on an island, l3v5y.
 
Last edited:

l3v5y

Retired Senior Moderator
Sep 13, 2007
7,485
44
29
Bristol
Well i also needed to Scour the new Roms for some updated OEMS and i needed to know for sure that welcomehead.192.png was named that way to add it to the process.

And maybe even a Copy User Preferred Manilla files from SD to device if present. There must be some other good ideas from people that like flashing, but are tired of installing their preferred skins, settings and Apps.


Unfortunately i found that the newer package of Connectionsetup asks for a reset where my previous VGA reskinned package did not.

All the Regs are te same (Except for two new unrelated ones).
I like the old non rebooting version better.
I know that a reboot isn't needed but i can see users unkowingly agree to that reboot. (But that's another subject)

I think i will change the package this weekend So it is only one method.

By default it is set to run at second boot, but it can easily be changed by the cook to run at first boot if that is the setup that one would prefer.

Also i'm still tinkering out the exact form of the XDA files.


But nice to hear i'm not on an island, l3v5y.

I think the "EXEC:" command waits for the process to close? If yes, then an application that runs some mortscripts could wait till all the mortscripts are run before continuing, so it can be run at first boot within RunCC. That saves the issue of an extra reboot...

Welcomehead.192.png is the file for VGA/WVGA devices, welcomehead.96.png is for QVGA devices, though it's actually set in the registry, so that could be checked at load time? (I'll find the registry key at some point...)


Something I've just thought of:

If there were a way for ROM cooks to block things that are known not to function or are included already, that would be quite useful. E.G. I include PIMBackup in ROMs, so why would anyone install an extra cab to do the same?
 
Last edited by a moderator:

Noonski

Inactive Recognized Developer / Moderator Emeritus
Apr 18, 2005
5,326
149
Amsterdam
noonski.nl
You could add a check for a specific .Cab name.
And if present change the extension.
Repeat and Rinse a few times.

Then at the end rename all .cabxx back to .cab


I think in general, not a lot of people change their cab names.

Unless like that previous post, someone likes to add numbers to them to control the order.

But in this Silent install method i can see that having one app being installed first could be useful as there's small pauses build into the script so the device isn't slow as hell the first minutes it boots.


I think it might get more error prone if it gets executed through RunCC.

With all the processes that get proccesed through the script.

It's using and starting, cusTSK.exe, TaskMgr.exe, wceload.exe and mortscript. But when Mortscript exitst it should be finished.


I would need to test this style to feel confident it doesn't reboot while there's still work in progress.


I Agree that getting it into the No Reboot style might be some extra work for cooks. And maybe i'm seeing this to much from my own perspective where i always remove and convert OEM configurations to straight forward packages.
 
Last edited:

l3v5y

Retired Senior Moderator
Sep 13, 2007
7,485
44
29
Bristol
You could add a check for a specific .Cab name.
And if present change the extension.
Repeat and Rinse a few times.

Then at the end rename all .cabxx back to .cab


I think in general, not a lot of people change their cab names.

Unless like that previous post, someone likes to add numbers to them to control the order.

But in this Silent install method i can see that having one app being installed first could be useful as there's small pauses build into the script so the device isn't slow as hell the first minutes it boots.


I think it might get more error prone if it gets executed through RunCC.

With all the processes that get proccesed through the script.

It's using and starting, cusTSK.exe, TaskMgr.exe, wceload.exe and mortscript. But when Mortscript exitst it should be finished.


I would need to test this style to feel confident it doesn't reboot while there's still work in progress.


I Agree that getting it into the No Reboot style might be some extra work for cooks. And maybe i'm seeing this to much from my own perspective where i always remove and convert OEM configurations to straight forward packages.


I personally hate having cabs installed, so in theory my ROMs should be good to go without the reset.


Based on what you said, it might be best if the number of complications are minimal, and device compatibility as great as possible. RunCC probably would make things more complex and error prone, so yes, I agree not having it as a dependency makes sense.


A mortscript could always recognise *cabname.cab, so even using an order flag at the front should work.


Silent install sounds like it could be great, although some of the cabs need user intervention... Also, having a flag settable somewhere that makes (or stops) a message box with "auto install is complete" would be useful...
 
Last edited by a moderator:

Noonski

Inactive Recognized Developer / Moderator Emeritus
Apr 18, 2005
5,326
149
Amsterdam
noonski.nl
At the moment i have G-Alarm in my SD folder for that User intervention.

It just pops up at the moment after it's install i know at first i waited for it, no i grab a beer and tap it when i arive but the script continues with the rest of the files present so it's not waiting on that user interaction.


The possible Pop up message would in theory come up at the moment the last cab is just starting to install but it should be possible to add a check if wceload is still active before it pops up.


Which reminds me i still need to contact some of the people that actually helped out a lot without knowing.


"Installation has Finished, if your in a good mood and were planning to get beer from the fridge choose yes to reset the device, If your not in the mood and need to actually use your phone right now, press no to reset whenever you feel like it"


Do you think that would fit in the screen
:D
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    [UC]XDA_UC V2.RC1, Automated & Silent User & Cook, Configuration Service[14/05/10]


    Another (The?) new way to implement User Customization and Cooking.

    This Thread is meant for Rom Cooks.
    Users should take a look at the User To User Tips, Tricks ideas and issues thread.

    What the XDA UC service does, is silently install (or not so silently if needed by User), .cab, .xdas, .xml, .reg, .mscr, copy over user manila files, install files from SDconfig.txt if wanted and then a few extra's for the freaks like copying folders or creating shortcuts from specific registries. This happens either at first or second boot depending on the existence of either RunCC.exe or Autorun.exe in rom.


    It's all Mortcsript so it's very easy to get a grasp of it and change the behaviour and or Chip in adjustments/improvements.
    But no knowledge of mortscript is needed to implement
    It Uses DotFred's Taskmanager to parse and implement the .reg and .xml files. But it can also be used to disable or enable services or register DLL files.

    More Information about the XDA Type Files at:

    http://wiki.xda-developers.com/index...ename=XDA_file

    My Shout out for this Two Year Long Evolving Collaborating Endeavour go to:
    Bengalih (that has a very similar UC variant called Sashimi and helped with some of the early scripts I was trying to do with mort while cooking, I wish I could have collaborated more with him, it would have saved time re-inventing the wheel), RoryB for bouncing back ideas, supplying new scripts and perfecting older ones, serfer222 For making the script compacter, jmckeejr, Ameet & the whole Digital XDA SPC Cooking Crew, bbobeckyj, CLHatch, Scinor, Mort, Sleuth255, McCune, DotFred, MrVanx, danny_and_2, Cmonex, utak3r, Laurentius26, Radimus, and the Whole Original SPC Crew for accepting my obsessions.
    For Knowingly helping me get the information, unknowingly helping me get the information or motivated me in keep going on in my Quest resulting in this.

    If I Forgot you, Forgive me.
    If you feel that certain information that has been used originated by you give me a holler and I will credit you if this is so.

    Before you consider buying me a beer. Please consider Donating to XDA to help out with the maintenance of the forum and get cool stars next to your Nickname showing your appreciation. Then there are always the people that without their apps this wouldn't have been possible at all that you can consider showing some love. Mort, DotFred & Sleuth255 All of whom made Apps Seemingly simple But oh so useful for the whole XDA and PocketPC community.

    Download and Info in next Post
    1
    I tried removing the extra _skip

    And i get:

    attachment.php


    As i said i'm not familiar with the New Ervius Visual kitchen and have no problem using BuildOS.


    Working now, after manually removing the Original WM Taskmanager from the SYS packages. (Which was a module as opposed to DotFred's Taskmanager)


    So the next test was turning Dot Fred's Taskmanager into a module and putting back the WM Tasmkanager as a module to.


    Now it goes through without the error and replaces the WM Taskmgr.exe correctly.

    I learned something new today thanks.

    I'l be uploading the final package for Visual Kitchen later on after actually checking the DotFred Taskmanager performance as a module.
    1
    Hi Noonski,

    I need to keep dotFred Task Manager named as follows:


    FS_TaskMgr.exe



    ... so as to not conflict with other apps I need running. Is this going to be an issue?


    If so, which file(s) do I need to change to have it recognize "FS_TaskMgr.exe"



    Cheers,


    Well the thing is that the scripts are also aligned to parse the XML files to Taskmgr.exe


    So the XDAUC.mscr should be modified to:

    RunWait("\Windows\TaskMgr.exe", REGfile & " /silent")

    &


    RunWait("\Windows\TaskMgr.exe", "/provxml " & XMLfile)


    I chose to keep using that taskmanager name scheme as QuickMenu also calls for it.


    So your hitting a good point here.


    I was thrilled when i could finally get rid of the Windows Taskmanager when MS separated it from Storage Space Control panel Applet. And replace it by default with this powerhouse.

    (and i could always use TaskManagerLite.exe for the same experience as the WM taskmanager)

    And never run into a situation where it was an issue.


    So if it is important to specific Setup's it's good to look into.


    I don't want to go force everyone to replace the WM taskmanager, so i can still go back, but i would also need to adjust the .xda installation script standards to this format.
    1
    What's the proper way to make XDA UC NOT run at 1st boot?

    What I've done is to make a shortcut to XDAUC.mscr. I placed that .lnk in my Start Menu\System Tools folder. The problem I'm having is that sometimes it works and sometimes it doesn't work. It seems to be about 50/50. Whenever it doesn't work, even if I go to \Windows and try to run the XDAUC.mscr directly, nothing happens.

    Which brings me back to thinking that I must not be going about this in the right way. Can someone tell me how I can make a .lnk to XDAUC in my start menu that will always work??

    Thanks in advance for any help! :)
    1
    How can i use this?
    Yes, it is a very simple question but i never find any documentation for this.

    please tell me whitch files should i cook in the ROM.
    And, whitch or what to put on the SDCARD?

    Really, i got lost because i'm new to this.

    There are no separate files...you can just put everything in SD card, under XDA_UC folder, and run it from there. You dont really have to cook them in.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone