yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Software Development] agibby5:
I'm cooking a rom for a Palm Treo Pro. I'm trying to integrate XDA_UC. I'm using XDA_UC V 1.1.00 from post 2 of this thread. I extracted the .zip file to my OEM Packages folder, refreshed the Oem Packages tab of the kitchen. I'm using (osKitchen), and the package showed up. I selected it, cooked the rom, and flashed. I know it's trying to run properly, as expected, because I get an error about XDA_UC.mscr below.

Whenever the device boots, it tries to run XDA_UC.mscr from \Windows\Startup, the file does exist. However, I get the following error:

I've spent hours on this and wouldn't be posting if I hadn't struggled thoroughly. I'm not sure what I'm doing wrong. Any help is greatly appreciated. Thanks
[Windows Mobile Software Development] saurabh88:
i have tried all the way but no luck..i cany figure out whats wrong.
[Windows Mobile Software Development] serfer222:
if you use Autorun or RunCC you should use XDA_UC on second boot.

I just released new version of my .NET version of XDA_UC - you can configure it to run on any boot you like. Try it.
[Windows Mobile Software Development] saurabh88:
ok thanx but which packages should be included ??all three in v2.1legacy?should i have to use them seperate or that singke folder..

in oem or ext?
[Windows Mobile Software Development] serfer222:
it depends on your kitchen - what kitchen do you use?
[Windows Mobile Software Development] saurabh88:
oskitchen ......so should i convert packag
[Windows Mobile Software Development] serfer222:
sorry, I don't know about oskitchen.

I used EVK and OsBuilder only.

In my ROM with XDA_UC I used only RunCC and XDA_UC

RunCC replaces AutoRun
[Windows Mobile Software Development] xxlagunaxx:
Nevermind.
[Windows Mobile Software Development] NotATreoFan:
*NOTE* This is for my Fuze ROM, not the Touch Pro2.

Using v2.1RC, I'm having an issue with my theme being applied.

I modified the XDA_UC.mscr from Cook.tsk to match my theme name, and if I check Today settings after the reboot, it shows my theme as active, although Microsoft's Classic Blue is really active.

If I change the theme to anything else, and then back to my theme, it applies as expected. I have also tried changing 'DisableTheme' to '1'. When I do that, Classic Blue will show as the current theme, and I can manually set my theme file.

Also, is there a way to delay the start of XDA_UC? I'm not using AutoRun or RunCC, but I would like to be able to complete the screen alignment before XDA_UC starts.
[Windows Mobile Software Development] serfer222:
maybe you have SDConfig.txt on your card? XDA_UC reads TSK: parameter from this file.

there is

Timing = 30000

in the beginning of XDA_UC.mscr

it means - script will sleep 30 000 ms (30 sec) before it shows first window.
[Windows Mobile Software Development] NotATreoFan:
The SD card only contains the RAPHIMG.nbh used to flash the ROM. I tried changing the name of the TSK file, and also editing XDA_UC.mscr to the original TSK filename. Neither works.

I've tried playing with the timing string, but I still feel the vibrate as soon as screen alignment begins, and by the time I'm done with that, the install is already 3 or 4 CABs in.
[Windows Mobile Software Development] serfer222:
XDA_UC v2.RC1 installs all cab files from Windows folder before it shows the message to user. If you want to change this - cut these lines

# Install .cab files silently present in Windows folder unless Run in Manual Mode
#################################################################################
If ((RegRead( "HKLM", "Software\XDA", "Manual" ) eq 1) OR (FileExists( "\Windows\RunCC.exe" )) OR (FileExists( "\Windows\Autorun.exe" )))
# Do Nothing ;)
Else
@InstallCABs ("\Windows\*.cab", TRUE, FALSE)
EndIf

and paste them after

Message("XDA_UC will start customizing your device. Share issues at at the official XDA_UC user2user Thread.", "XDA_UC Customization")

also you can cut

Vibrate(100)

and paste it on the line before

Message("XDA_UC will start ...

this will fix vibration issue
[Windows Mobile Software Development] NotATreoFan:
I was able to add a 25 second countdown by editing the already modified XDA_UC.mscr attached a few posts up, and that is an acceptable fix for the issue with CAB installs happening before the screen alignment is done.

The only issue remaining is why the theme is not applying during the first step of XDA_UC. Like I said before, when that part is enabled, it shows as the active theme in Start -> Settings -> Home, but the default Microsoft Blue is still active. If I switch the selection to Microsoft Blue and then back to PureBlack3 (or any theme I have tested), it activates correctly.
[Windows Mobile Software Development] edsub:
Does anybody know how to install a .pfx certificate via XDA_UC.

I know installing .cer certificates is supported, but how about .pfx?
[Windows Mobile Software Development] serfer222:
I think I can add this feature to my XDA_UC_NET version of XDA_UC.

http://support.microsoft.com/kb/950090

Looks like it's very easy to do.

What do you think?
[Windows Mobile Software Development] edsub:
XDA_UC is cooked in my (Energy) ROM so I prefer to use that.

But certainly this is a good option!!
[Windows Mobile Software Development] serfer222:
I will try to create small commandline application to do this task.

Am I right there will be two parameters - pfx file and password?
[Windows Mobile Software Development] Mastiff:
Having a problem copying files with XDA_UC

XDA_UC runs all my XML's, CAB's and REG's perfectly. But I simply can't grasp the copy files thing! I have created a directory called Copy2Root under the XDA_UC directory on the SD card, but the files does not get copied anywhere. So I tried with a SDConfig.txt file, both in the XDA_UC directory and in the root directory of the SD card, with this in it:

*********************************************

LOCK:Enabled

CPY1:\Storage Card\XDA_UC\Copy2Root\test.txt

CPY2:\Program Files\test.txt

LOCK: Disabled #Added a space her for this message alone to avoid it being interpreted as a smiley

RST: Reset

*********************************************

Empty line after the last line and all. But nothing is copied. Any idea what I'm doing wrong here?
[Windows Mobile Software Development] maesus:
kurniawan77,

I have the same question and similar problem as you. I took the entire RunCC EXT off the ROM but keep htcOOBE in, and use XDA_UC to customize the ROM. However, even after XDA_UC completed, reset, OOBE did not occupy the fullscreen and only the "setup wizard' at taskbar but no gui. Same issue as you had. I must run RunCC, and let it completed, then the next startup will have ConnectionSetupAuto and OOBE running.

I also tried to run RunCC, and modify the XDAUC.mscr to KILL runcc.exe to "take over' the customization process. However, on the next startup, it restart the whole installation process like fresh install ROM! :confused:

Have you found a good solution yet?
[Windows Mobile Software Development] madnish30:
Hi,

Thanks for the great work.

Just a little question.

I'm cooking Visual Package using EVK, but i don't use UC for any customizations.

I'm cooking it so that the ROM is UC compatible for the users.

Can someone tell me what all i files do i delete in order to remove the theme which is cooked in by default.

I'm guessing that cook.tsk has to be deleted and cusTSk.app has to be deleted..

But i want to confirm i hope those are not dependencies.

Also cookinf the visual package make my ROM UC compatible right ?

Thanks alot.
[Windows Mobile Software Development] MaXyM:
[edited - sorry, wrong thread]
[Windows Mobile Software Development] dhncali420:
Enable Connection Setup on first boot with XDA_UC

For weeks I was searching for a solution but no luck, so I tried this:

added this to XDA_UC.mscr

# Run Connection Setup @ 1st Boot
##########################
If (RegRead( "HKLM", "Software\XDA", "Manual" ) eq 1)
Else
If (FileExists( "\Windows\ConnectionSetupAuto.exe" ))
Run("\Windows\ConnectionSetupAuto.exe")
EndIf
EndIf

add the above After:

# Check if Script should continue
#################################
If ((runCustomization) OR (RegRead( "HKLM", "Software\XDA", "Manual" ) eq 1))
Else
Exit
EndIf

and it worked like a charm, connection setup runs at first boot if XDA_UC runs at first boot or it runs at second boot If other UC services used

hope this helps
[Windows Mobile Software Development] Noonski:
First of,

Thanks to Serfer for going ahead and evolving on the XDA_UC idea and popping his head in this thread helping users.

And off course all the other users that have been helping others here, and not the least RoryB.

Second.

I'm back, but will not actively be working Rom's, Script or frontpage articles.

It would take to much time that i don't have at the moment.
[Windows Mobile Software Development] :
hi..

y have a strange problem...all my cab in my "Storage" folder not instaled on my storage but directly on my phone...:eek:

I'm with a french rom and my storage card name is "Carte MicroSD"

the only cab on my storage are ok if xda_uc send me were can you install this cab...if i choose Storage card it's ok....

for help me you can se my XDA_UC.mscr
[Windows Mobile Software Development] Noonski:
It's all in this part:

# Sub RunAnySD
##############
Sub 2SD
WaitFor( Installation ,3 )
SendDown( Installation )
SendSPACE( Installation )
SendLeftSoft
While( WndExists( "Installing" ) )
Sleep(500)
EndWhile
SendOK( Installation )
EndSub

You need to find the French Window Name for the installation Window.

And then you can put it in the Variable at the top

Installation = "Installation"
[Windows Mobile Software Development] :
ok thanks..i test it with

# Sub RunAnySD

##############

Sub 2SD

WaitFor( Installation ,3 )

SendDown( Installation )

SendSPACE( Installation )

SendLeftSoft

While( WndExists( "Installation" ) )

Sleep(500)

EndWhile

SendOK( Installation )

EndSub

the Variable at the top is ok

the French Window Name for the installation Window is "Installation"
[Windows Mobile Software Development] :
with this modification it's not good...all cab are ok in phone memory (all included cab in XDA_UC folder) but i have now an error cab in "Storage" folder ok my XDA_UC folder..:cool:

screen of this error
[Windows Mobile Software Development] RoryB:
Tweaked the previous post to fix a problem if the ROM does not have a config_operator.txt file
[Windows Mobile Software Development] :
hi

i have look and take this

# Sub RunAnySD

##############

Sub 2SD

WaitFor( Installation ,3 )

SendDown( Installation )

SendSPACE( Installation )

SendLeftSoft

While( WndExists( "Installing" ) )

Sleep(500)

EndWhile

SendOK( Installation )

EndSub

now no error mesage but the cab in "Storage" folder of my xda_uc no send in program files of my storage card but in program files of my phone.

the cab in this "storage" folder with notification for install on sd or phone are ok if y choose "sd card" on screen

i think this line not change the default selection for the auto install (silence) the cab "Storage" folder

# Start installation of To Storage .cab files in Storage Card\XDA_UC\Storage folder

###################################################################################

@InstallCABs (XDAUC_FOLDER & "\Storage\*.cab", FALSE, TRUE)

on the screnn i don't see this modification and the firts section (phone) is actived..?

i can change this for take by default the second option by default to "storage" folder of xda_uc?..

[edit]

when i test this

# Start installation of To Storage .cab files in Storage Card\XDA_UC\Storage folder

###################################################################################

@InstallCABs (XDAUC_FOLDER & "\Storage\*.cab", FALSE)

all is ok but in manual mode for storage folder / if i chose manualy the "storage card" all my cab are in program files of my storage...i don't undertand why the automatic selection is not good with me.....
[Windows Mobile Software Development] :
hi i have edit my post

have you an idea for auto select the Storage option?
[Windows Mobile Software Development] edsub:
item deleted
[Windows Mobile Software Development] Rouz.:
Unknown command '@clearattributesysandro'

Can anyone help me with this issue?

Previously it was working fine, but now I'm getting this error, and i can't find any solution.

Any help is much appreciated
[Windows Mobile Software Development] RoryB:
I would say your XDA_UC.mscr is missing the clearattributesysandro subroutine. Look near the end of the script (where subroutines must be placed).
[Windows Mobile Software Development] imbunned:
thanks a lot:)
[Windows Mobile Software Development] nsourm:
cooking xda_uc

Hello to all .I'm a newbie i cooking and i'm using airxtreme's kitchen.I'm wondering if someone can help me to cook xda_uc in my rom.

Thanks a lot for your help
[Windows Mobile Software Development] Grumps:
Use this file and Just Cook it last. it should work fine
[Windows Mobile Software Development] nsourm:
Thanks a lot Grumps.

But as a newbie this file have to be putted in ext packages.Is that correct?Do i have to do something else?

Thanks for your help
[Windows Mobile Software Development] Grumps:
Create a new group Called 99 Cook last or something. Then unzip this file and drop it in there and you can select it so it will include it in the build
[Windows Mobile Software Development] vasujahagirdar:
hi all,

im also a new one trying to cook my own rom on my elfin using os kitchen,importing newer builds and mega packages,and wants to customise by one of the method like autorun,runcc or xda-uc but want to where to put my cabs,xml, .exes and other files in the kitchen,and where to write these in the xda-uc ??searched many threads but not able to understand the technical jargon ,so plz help.

thanks
[Windows Mobile Software Development] hectorhts:
Hi I have a T-Mobile HD2 with HSPL 3/ EnergyROM Energy.Leo.21916.Sense2.5.Cookie.GTX.Oct.13 on it and in the start menu/tools i got an icon XDA UC and I want to know whats the utilily for that thank you
[Windows Mobile Software Development] af974:
Sorry Rory,i dont understand,are you saying that we need to compile these lines:

must put the filename to have clear attribute?

Though i've never had this kind of error with Kaiser, this are happening only with Leo.

# Sub ClearAttributeSysAndRO
############################
Sub ClearAttributeSysAndRO (fileName)
SetFileAttribute( fileName , "readonly", FALSE)
SetFileAttribute( fileName , "hidden", FALSE)
SetFileAttribute( fileName , "system", FALSE)
SetFileAttribute( fileName , "archive", FALSE)
EndSub

EDIT: problem solved,XDA_UC must be the last package to be cooked,had some regs that went in conflict lol
[Windows Mobile Software Development] RoryB:
From the error message in your previous post line 60 of \windows\startup\XDA_UC.mscr probably has in it @clearattributesysandro(CARRIERSPLASHSCREEN)

The code above looks to be correct for that to work, but I think it will only work as a part of a string of code.

If @clearattributesysandro(CARRIERSPLASHSCREEN) is on the line by itself, try changing that line to

Call(clearattributesysandro, CARRIERSPLASHSCREEN)
[Windows Mobile Software Development] af974:
Thanks for reply Rory but ,well i realy dunno why, i had XDA uc before my reg tweaks and always got the error, now i moved xda_uc after them and it works fine.
[Windows Mobile Software Development] RoryB:
I'm glad it is working for you now. No matter how it works.

Maybe the way things are set up now the reg settings do something required for mortscript to work properly. Not sure what since I do not use XDA_UC
[Windows Mobile Software Development] sharkie405:
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! :)
[Windows Mobile Software Development] robekia1:
Very Bad Question

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.
[Windows Mobile Software Development] ai6908:
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.
[Windows Mobile Software Development] robekia1:
Thanks a ton.

What about scripting? please guide me for the best thing to do regarding the selfregister DLLs.

To Make it clear:

I'm trying to cook "MOBiDIV_PrayerTimes_Diamond2_B15_TSD_Jun1.Cab" but the problem with the included "fileosp.dll" which requires self registration that is been automatic done while installing the .CAB:rolleyes:

So, is there any kind of solution to do it while COOKING the ROM?
[Windows Mobile Software Development] robekia1:
Registering DLL

How i can use it for registering DLLs?
[Windows Mobile Software Development] robekia1:
No Reply !!!

No Reply !!!:eek::eek::eek::eek::eek:
[Windows Mobile Software Development] Noonski:
I tried removing the extra _skip

And i get:

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.
[Windows Mobile Software Development] ai6908:
Thanks, I am glad I am not the only one! Should have tried with TPC kitchen as they still use the old style and would have known! But thanks for the fix!
[Windows Mobile Software Development] hilaireg:
dotFred Filename

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,
[Windows Mobile Software Development] twopumpchump:
i have never gotten dotfred task mgr to work with bepes platformrebuilder in exe file form, have to change to module ;) is weird because i know others who use it all the time with no errors :confused: oh well, looks like noonski fixed it up, im gonna give it a try in my kitchen and see what happens :D
[Windows Mobile Software Development] hilaireg:
As it's a self-contained EXE, I simply renamed the EXE as I noted above. This gave me the flexibility to run it along side other Task Managers.

I'm hoping this isn't going to be a problem for implementing XDA_UC.

:(
[Windows Mobile Software Development] Noonski:
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.
[Windows Mobile Software Development] hilaireg:
How about renaming the DotFred Task Manager to something like fdcTaskMgr.exe and add in a credits ReadMe file to avoid possible complaints.

I would rather not have to modify your files if at all possible so as to avoid confusing folks and/or making it difficult for them to update XDA_UC going forward.

Cheers,
[Windows Mobile Software Development] B4PJS:
Just a quick bit of information about the file vs module thing, this is due to a windows issue where you cannot overwrite a folder with a file (try naming a folder "blob.exe" and then pasting a file called "blob.exe" in the same base folder). As you have noted there are 3 ways around this:

Delete the original module

modularise the file

recmod the original module

IIRC I had the same problem when I first converted the Sashimi/mortscript package from a cab due to the fact that it contained a taskmanager in file format.

B
[Windows Mobile Software Development] Noonski:
Would the Tweak:

[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Rai\:MSTASKMGR]
"0"="MSTASKMGR"
"1"="\\Windows\\TaskManagerLite.exe"
"2"=dword:1
"3"=dword:0

Change any of this?

I know that the default WM taskmanager can be set up to close applications If memory drains to much, but i haven't seen that happen to much.

What else relies on the default MS Tasmgr.exe?

I'm really trying to think this over, and trying to outweigh my personal preferences against issues that might arise.

(Personal Preference Being WM Taskmgr.exe Weak, Dot Fred Smash:D)
[Windows Mobile Software Development] hilaireg:
I feel your delima.

I much prefer fdcSoft (dotFred) Task Manager as well but I didn't want to impose my preference on the kitchen and it's users - so I created a specific package for it and renamed the EXE to FS_TaskManager ... figured no one would use a name like that.

If you look at the package in the kitchens, you will notice that the .REG/.RGU file does not hook into that key. It simply sets the .REG association to point to FS_TaskManager. Unless there's a hard dependency that requires registration in the key, I would be inclined to avoid it or leave it as optional.

I also decoupled MortScript 4.2 (DLL & EXE) so that i may also be updated in the future. At the moment, I the following "commented" packages:

FDC Soft Task Manager

SDAutoRun 2.0

MortScript 4.2 (Comment indicating that it requires SDAutoRun 2.x)

XDA_UC (Comment indicating that it requires MortScript & FDC Task Manager)

Remove CustSat/SQM (Comment indicating that it requires XDA_UC)

My reasoning for this is that FDC Soft & SDAutoRun are the foundation, MortScript & XDA_UC a framework, and the CustSat/SQM package (and others) the finishing touches over top of the framework.

BTW; thanks for taking the time to revisit this on the 23rd hour ... I'm delaying PACK3 release for the moment.

Cheers,
[Windows Mobile Software Development] Noonski:
Updating to this name scheme should not interfere or urge to update.

Both previous and the next version will do the same without conflict.

It's a good thing i have put, setting up the Defaults for XDA files off, for after getting the UC part up. (there's only so much variables one person can think up without the input of others)

If you have already thought about it more and about the interference of Cook choice, you actually saved me some time.

I will have another bourbon and dinner then dive into adding a few User Customisation for Manilla Functions and change the naming Scheme.

Bit i'll take the whole weekend for this ;)