[Kitchen] WVGA Touch Pro 2 Collaboration

[Sharkie405]

Damn, them boys over at MUI are having a rough time of late!

[1sae]

So I'm trying to cook Opera Mini as the default browser, and I've found the right keys in the registry to add them. But when I cook them the don't get added in a way that works.

This is what I have in my app.reg:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shell\Rai\:DEFBROWSER]
"0"="Opera Mobile 10"
"1"="\\Program Files\\Opera Mobile 10\\Opera10-armv4i.exe"

When I cook it, the registry key shows without the quotes. Without quotes in the registry makes the manila links not work.

\Program Files\Opera Mobile 10\Opera10-armv4i.exe

If I try

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shell\Rai\:DEFBROWSER]
"0"="Opera Mobile 10" 
"1"=""\\Program Files\\Opera Mobile 10\\Opera10-armv4i.exe""

the kitchen shows an error and the registry key is blank.

How do I go about cooking this?

EDIT: For anyone interested I figured it out. It shoud look like this:

REGEDIT4

[HKEY_CLASSES_ROOT\http\Shell\Open\Command]
"Default"="\"\\Program Files\\Opera Mobile 10\\Opera10-armv4i.exe\" %1" 

[HKEY_CLASSES_ROOT\https\Shell\Open\Command]
"Default"="\"\\Program Files\\Opera Mobile 10\\Opera10-armv4i.exe\" %1" 

[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Rai\:DEFBROWSER]
"0"="Opera Mini 5.1"
"1"="\"\\Program Files\\Opera Mobile 10\\Opera10-armv4i.exe\""

[corey1138]

Here is CHT2 Final and CHT Editor Final EXTs converted from OEMs if you wanna play with them. I made the OEMs with cab2oem. My OEMs work fine in OSBuilder but the EXTs are un-tested. Actually i do get an error when exiting CHT Editor but the settings still apply.

[Sharkie405]

Originally Posted by 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!

Bump.

Ok, well how about this... Can someone, anyone please post their XDA UC OEM or EXT package that's set up to NOT run at 1st boot?

Pretty please

[corey1138]

Originally Posted by Sharkie405

Bump.

Ok, well how about this... Can someone, anyone please post their XDA UC OEM or EXT package that's set up to NOT run at 1st boot?

Pretty please

Are you sure its not putting a shortcut in the startup folder? Maybe make your shortcut go under My Documents somewhere or the AppData folder. Did you try the XDA_US thread in XDA?

[Sharkie405]

Originally Posted by corey1138

Are you sure its not putting a shortcut in the startup folder? Maybe make your shortcut go under My Documents somewhere or the AppData folder. Did you try the XDA_US thread in XDA?

Yes, I've changed it so it doesn't put a shortcut in the startup folder. I have the link going in my System Tools folder. I did try the XDA UC thread a couple of days ago, but there's not been a post in that thread since. The problem is not that it's starting at start up, the problem is that my link to it doesn't always work.

On a separate note,

I'm going to be taking down all the build links I've posted of late to make room to upload ROMs. So, if you might want them, go ahead and get 'em. They won't be around for much longer.

[macsrgr84me]

Originally Posted by corey1138

Here is CHT2 Final and CHT Editor Final EXTs converted from OEMs if you wanna play with them. I made the OEMs with cab2oem. My OEMs work fine in OSBuilder but the EXTs are un-tested. Actually i do get an error when exiting CHT Editor but the settings still apply.

Did you have to make any changes to the files after dragging the two files onto cab2oem for your OSBuilder kitchen?

Thanks.

[corey1138]

Originally Posted by macsrgr84me

Did you have to make any changes to the files after dragging the two files onto cab2oem for your OSBuilder kitchen?

Thanks.

The only thing i did was save the initflashes and thr rgu as unicode so Brian's OS Builder wouldn't gag on them. Also the rgu's usually hve some paths that need to be fixed "\\" insted of a single "\". I check this with the registry preview in OS Builder. I caint remember if I recmoded the dlls... Probably no need for it...

[1sae]

Hey guys, I'm having a scrolling problem with my manila messaging. I'm using the 2019 package Sharkie posted here.

WHat happens is I cant scroll all the way to the top. I drag it down, but then it just bounces back to the bottom. I've searched but can't find any info on this. I've also tried using the 2018 and even the stock 2012 messaging package which did the same thing.

Anyone else have this problem? Maybe point me in the right direction?

[mwalt2]

Originally Posted by 1sae

Hey guys, I'm having a scrolling problem with my manila messaging. I'm using the 2019 package Sharkie posted here.

WHat happens is I cant scroll all the way to the top. I drag it down, but then it just bounces back to the bottom. I've searched but can't find any info on this. I've also tried using the 2018 and even the stock 2012 messaging package which did the same thing.

Anyone else have this problem? Maybe point me in the right direction?

You need to use HTCMessagingClient or use manila.exe and mode9.dll from a Leo ROM. There's something hardcoded in the Oboe manila.exe that makes it dependent on HTCMesagingClient for proper scrolling in messaging and twitter. Alternatively, you can just use the entire Manila_Core from a Leo ROM instead of only manila.exe and mode9.dll. If you don't feel like re-cooking to fix the issue, you can recmod mode9.dll and copy mode9.dll and manila.exe to \windows (overwriting the Oboe ones).