Titan Kitchen CE OS 5.2.19209 (Build 19209.1.0.2) aka 5060

[hetaldp]

Attached is the

SPB Mobile Shell 2.0 OEM Package I searched the Hell in this World but could not find it so i finally made this OEM

TierMan OEMiser will not work as Registry setting in SPBMobileShell.cab is hidden in SPBMobileShell.rgs which is a Registration Script File so you have to First Install the Software and then Export the Registry using RegEditor and manually make Short Cuts to \Windows

The Registration Keys is Hidden in following Registry Key

[HKEY_CLASSES_ROOT\CLSID\{783AC566-6E9F-41A4-8B5C-C5728C204E51}]
"SIPFlag2"="xxxxxxxxxxxx"



I request some user to use this OEM and if it work Properly then We could replace or this OEM into PPCGeeks_OEM Package

[colonel]

Originally Posted by hetaldp

Sorry its working fine I was using a Extract from Old version with Vista Skin which dont have Entries in .rgu file

I am Extreamly sorry for Wrong Reporting by mistake !!!

Nah, I just wanted to make sure we weren't missing something. It appears that your OEM has many more reg entries. So, we will use it and test. I was just curious as to where they came from.

[mbartels]

Originally Posted by hetaldp

Package from PPC OEM dont run well unless u place

Attached is the Version from DCD Kitchen and it works Well

colonol no2chem Tierman please Take a note (Remeber this OEM look for SDConfig.txt into Root of SDCard and exe is Well placed in OEM)

[b](Placing the SDAutoRun.exe in OEM is more Safer Option o fight against Viruses)[b]

 
REGEDIT4

[HKEY_LOCAL_MACHINE\Security\AppInstall\AutoRun\ExecutableFiles]
"\\Windows\\CheckAutoRun.exe"=hex:

;<<<<<----- Your Additional Entries ----->>>>>
[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Extended_ROM\\autorun.exe"
"AutoRunCFG"="\\Extended_ROM\\config.txt"
"AutoRunType"=dword:00000000
"TurnRadioFlag"=dword:00000000

Above is the Entries from AutoRun.exe in TitanKitchen

Here also its Poiting to Extended ROm but AutoRun.exe is there its self in \Windows So Joining above OEM with SDAutoRun will create Problem also

Thanks a lot for taking time time to post the attachment and explain yourself. For some reason even using your attachment as a kitchen OEM instead of the one from the kitchen team still didn't work. Nothing I do seems to have the 6800 trigger this automatically.

[jeffrc]

fianlly got teh $ to donate, just sent it over, thankd for everything guys, switched to 5060 this morning(had 0 problems with 5059, but i thought what the hell why not?!) and i love it!!

[colonel]

Originally Posted by mbartels

Thanks a lot for taking time time to post the attachment and explain yourself. For some reason even using your attachment as a kitchen OEM instead of the one from the kitchen team still didn't work. Nothing I do seems to have the 6800 trigger this automatically.

Did you include Autorun in the build? Also, check \windows for Autorun.exe and CheckAutorun.

[hetaldp]

I just have to Checked my SDAutoRun and Unchecked OEM Auto run and OEM SDAutoRun

Format the SDCard with FAT32 and place SDConfig.txt in Root of SDCard which Point to each and every cab in right Destination and Hello

If you don't Disable the Security then Major Extended ROM cab which is not a Signed cab will not run ever. So I have made these Security Disabled using 4 Registry Edits and Placed it into Some OEM Package then only unsigned Extended Rom Cab is Automatically getting installed !!! Will Post Security Reg Edit Tomorrow

MAJOR EXTENDED ROM CAB IS UNSIGNED SO IF YOUR KITCHEN IS NOT HAVE REG SETTING TO DISABLE SECURITY CAB WILL NOT GET INSTALLED

@no2Chem

We can add this Reg Setting into SDAutoRUn It self

@mBartels

I will again add those Security Registry Hacks into SDAutoRun OEM i have Uploaded so this Issue will get solved

[tiermann]

Originally Posted by hetaldp

I will again add those Security Registry Hacks into SDAutoRun OEM i have Uploaded so this Issue will get solved

The security entries are already part of 5060. I don't think we put out one without them.

SDAutorun fixed for next update. The only problems were 1) There was no config.txt being added which is supposed to call SDAutorun at the end, and 2) the AutoRun reg entry was set to SDAutorun and not Autorun.

Choose Autorun and SDAutorun after next update is released and it should work fine.

[hetaldp]

Well I guesss Carrier_NoCarrier should also Included for the Users out side USA who dont want any Sprint or Alltel Connection which is Protected by CMGaurdian etc.

I have a Sprint Touch which i am using on TATA and it dont let Sprint Connection to delete it and make new Connection

so Carrier_NoCarrier is a essential Package for all Non USA Users They will manage to Port Extended ROM cab to SDCard and use SDAutoRun to Customise their PPC

[mbartels]

Originally Posted by tiermann

The security entries are already part of 5060. I don't think we put out one without them.

SDAutorun fixed for next update. The only problems were 1) There was no config.txt being added which is supposed to call SDAutorun at the end, and 2) the AutoRun reg entry was set to SDAutorun and not Autorun.

Check Autorun and SDAutorun after next update is released and it should work fine.

Fantastic! Thanks everyone!

[tiermann]

Originally Posted by hetaldp

Well I guesss Carrier_NoCarrier should also Included for the Users out side USA who dont want any Sprint or Alltel Connection which is Protected by CMGaurdian etc.

I have a Sprint Touch which i am using on TATA and it dont let Sprint Connection to delete it and make new Connection

so Carrier_NoCarrier is a essential Package for all Non USA Users They will manage to Port Extended ROM cab to SDCard and use SDAutoRun to Customise their PPC

Even easier would be if we had stock ROM dumps from these carriers. Then we could add Reliance India, or NZ carriers as well.
The only carrier I know of that currently uses Guardian in 5060 is US Cellular, btw.