BuildOS Puking on my .rgu - Upgrading, Modifying and Unlocking

Hey everyone - hopefully someone here can help me fix my problem. I am trying to create an OEM package that will install a shortcut for "new sms" and then I am trying to map it to the left softkey of my Kaiser.
I have the shortcut, the dsm, the .rgu, initflashes, and option.xml in the package folder. Everything works fine except for my .rgu file.
REGEDIT4
[HKEY_CURRENT_USER\Software\Microsoft\Today\Keys\112]
"Default"="New SMS"
"Open"="\windows\newsms.lnk"
Click to expand...
Click to collapse
BuildOS really doesn't like that last line where I change the "Open" key, but I can't for the life of me figure out why. When I delete that line, build the ROM, and enter the line manually after flashing it works just fine.
Any ideas?

Replace with...
Code:
REGEDIT4
[HKEY_CURRENT_USER\Software\Microsoft\Today\Keys\112]
"Default"="New SMS"
"Open"="\\windows\\newsms.lnk"
You should escape the slashs...

holy crap! Thank you so much!!
I've been banging my head against the wall for like three days on that one!
Worked perfectly!

Related

Applying registry changes in a .cab-file?

Hi!
Is it possible to create a .cab-file which does not install anything, but only applies a number of registry changes? This way you would be able to "install" changes to the registry along with the other .cab-files running from the extended ROM after a hard-reset. How do I do that?
Any other ideas as to how to auto-apply registry changes are also very welcome Thanks..
/Joe72
No problem, just use WINCE Cab Manager. For learning purposes you should open some of the CAb-Files that came with the original ExtROM. Most providers split the registry settings to different files so that I reduced the size of my ExtROM by merging them (take those files, that just have 46kb, they only contain registry entries).
Open them with the above mentioned CAB Manager and look for a file named "platformxx", extract it, edit it, perform the desired changes (or mergers) and import to CAB Manager. Make sure that you remove the old "platformxx" and change the settings of the imported file so that it matches the settings of the deleted one (most times you have to make sure that the installation paths "hard coded" to the windows folder (edit the properties of the old file before and write them down).
unfortunately not all the flags for modifying the registry are supported by the wince cabloader.
full cab spec: http://msdn.microsoft.com/library/en-us/install/hh/install/inf-format_2v02.asp
wince cab spec:
http://msdn.microsoft.com/library/en-us/wcepb40/html/pbrefaddreg.asp
this is an example minimal cab.inf file:
Code:
[Version]
Signature = "$Windows NT$"
Provider = "testprovider1"
CESignature = "$Windows CE$"
[CEStrings]
AppName = "testappname1"
InstallDir = "%CE1%\installdir"
[Strings]
reg_path= "Software\testregpath"
[CEDevice]
ProcessorType = 2577 ; arm
UnsupportedPlatforms = "HPC","HPC Pro","Pocket PC"
VersionMin = 3.00
VersionMax = 4.99
[DefaultInstall]
Copyfiles=CopyToInstallDir
AddReg=RegSettings
[RegSettings]
HKCU,%reg_path%, "testdword",0x00010001,1
HKCU,%reg_path%, "teststring",0,"teststringvalue"
HKCU,%reg_path%, "testmultistring",0x00010000,"teststringvalue","second string", "third string"
HKCU,%reg_path%, "testbinary",1,44,45,46,47,48,49,4a
[SourceDisksNames]
1 = ,"All Files",,
[SourceDisksFiles]
"mktst.bat"= 1
[DestinationDirs]
CopyToInstallDir= 0, "%InstallDir%"
create the cab with:
Code:
Windows CE Tools\wce420\Pocket PC 2003\tools\cabwiz cab.inf /cpu arm /err caberrors.log
HTC has provided a more extensive install tool, with the CESetup.dll that is in all the cabs, this tool will import a 'platformxxx.reg' file if present in the .cab.
Hi
Thanks for the replies.
It seems like more work than I thought it would be..
In WinCE Cabmanager, there is a "Registry" fold-out in the left side menu similar to the one seen in Regedit.exe on Windows desktop or Remote registry from the Embedded C++ package. My initial plan was to import the registry into a cab-file and use this tool to change the things I want changed. This way, the cab-file would contain no files for installation, but a complete registry, modified to my needs. When running this cab-file on the WinCE device, I was expecting this registry to take the place of the old one.. Or would something else happen?
Thanks,
Joe72
I did it the easy way. I installed all my apps and stuff that I need and then made a backup of the registry, which I then flash installed into the extended ROM section of the phone.
So on a hard reset all my stuff gets installed, including of course a regedit program and hack to view extended rom. All I then do is open the regedit program and restore the registry in one go from the extended rom.
Used PHM Regedit for it.
where can i find the information that it is not visibly in the "remove programs"?
I want generate a programm that is not removable.
Thx for Your help
Snappy
What encoding should I use in platformxxx.reg to make parameters which contain non-latin characters displayed correctly? I tried Windows-1251, UTF-8, Unicode. In all cases russian text is not imported correcty. It is displayed in Western encoding.
P.S. When I use Registry branch in WinCE CAB Manager everything is ok, but if I import large enough .reg file the resulting cab becomes not working.
http://forum.xda-developers.com/viewtopic.php?t=31209
mobify registry
Element said:
http://forum.xda-developers.com/viewtopic.php?t=31209
mobify registry
Click to expand...
Click to collapse
Was it an answer?
My CABs are installed successfully.
Aftef hard reset the following is installed from ExtROM:
1. CAB which changes default codepage to russian (419)
2. CAB which translates some items into russian
So all I see instead of russian items is abracadabra.
But if I install only the first CAB from ExtROM and the second one is installed only from soft reset everething is displayed correctly.
So how to make it without soft reset?
Element said:
http://forum.xda-developers.com/viewtopic.php?t=31209
mobify registry
Click to expand...
Click to collapse
or Restorator
There IS an easy solution: Create .reg files by exporting from TRE, and u can re-apply them later by double clicking the reg file. See this post for doing it on the jasJar (will work on any XDA tho).
http://forum.xda-developers.com/viewtopic.php?t=30460
craigiecraigie4 said:
There IS an easy solution: Create .reg files by exporting from TRE, and u can re-apply them later by double clicking the reg file. See this post for doing it on the jasJar (will work on any XDA tho).
http://forum.xda-developers.com/viewtopic.php?t=30460
Click to expand...
Click to collapse
I do not need "clicking". The aim is to make it installing automaticly from ExtROM after hardreset.
priezz said:
I do not need "clicking". The aim is to make it installing automaticly from ExtROM after hardreset.
Click to expand...
Click to collapse
FYI, although this thread is quite outdated, I use regedit to import registry files from the command line...

[Updated 10/9/07 v1.0]Pandora's Kitchen Utility - Works on any BuildOS based kitchen

Pandora's Kitchen Option Utility
This utility will allow you to quickly save or recover your settings when customizing the options to your taste.
You will no longer have to go through BuildOS and check all your favorite programs every time you rebuild your image or install a new kitchen set.
Simply define your settings once, and from then on it's but a few clicks away
Troubleshooting:
If you receive an error when clicking "Load Kitchen":
1. The error message will display the path to the file. Check that it is formatted properly. See further down troubleshooting for more info.
2. Under the menu option File is the selection Log File. Click this to open the current log file for the kitchen you attempted to use. The last few lines should point to the option.xml file that caused the error.
3. Try running BuildOS. If it won't open, don't expect this to work. Try to isolate the trouble package and compare to other working ones.
Option.xml file formatting issues:
The file must be saved as Unicode
The file must follow the following format - noting that the entry for Tip is optional and the indention spacing is not displaying properly:
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="Time Sync Tab" group="Registry Tweaks" checked="false">
<Tip>Add time sync Tab to Phone Settings</Tip>
<Guid type="p">2f1ae013-04e8-11dc-8314-0800200c9a66</Guid>
</Item>
</Items>
Can't load Saved Configuration:
Your configuration file may have corrupted. Retrieve a backup or recreate it.
Known MAJOR Issues:
No known
Known Deficiencies:
List sorted by in alphabetical order
Future build will integrate BuildOS functionality - single user interface for both
once updated, option.xml files no longer use <cr> for readability. No effect on performance or function.
v1.0 Beta 1 does not read / edit the SYS folder option.xml file(s).
Downloads:
Installer:
Public Beta coming soon... target release of 10/10/07
.NET Framework 2.0 Redistributable (required if you don't already have it on your PC)
RapidShare Link
Revision History:
v1.00 Beta 1: Initial limited beta release
How-to video:
RapidShare Link (updated 10/9/07)
Suggestions:
Word to the wise - BACK UP YOUR KITCHEN!! It will save you much headache should something go wrong.
I can only rub my hands in glee - really look forward to using this as it allows for formal comparative testing between builds for me ;-)
Looks great Matt,
one question, how east is it to update the OEM packages. Same as before,just put them into the kitchen folder?
allan1 said:
Looks great Matt,
one question, how east is it to update the OEM packages. Same as before,just put them into the kitchen folder?
Click to expand...
Click to collapse
Very, then run this utility to set your options to true/false as you desire, then backup the settings so you can easily re-set them if you download a whole new setup.
Super easy and super quick. Just have a few XML formatting issues to resolve before I can get this out
News?
It sounds so good....
i'm getting excited
You're a good egg, you!
are we any closer to a beta yet?

Rom Cooking Related Question: Bugs and Problems

I'm facing a rather tricky problem.
Adobe Flash LE has a file called searchtext.bmp, same goes for the taskmanager that i'm using....BuildOS says there is redundant files (already exists)...what can I do to avoid this conflict?
Same thing happened to audio manager and audio booster. I first installed audio manager, then I installed audio booster. They happen to be using the same file name for some apps, and as a result, audio manager's skin was messed up because audio booster's skin file overwritten it
cook one in and use a cab for the other!
one thing you can do, is that you cook the bitmap file as a different name, say, package A has a file called myfile.bmp, and package B as well. what you need to do is cook the file in B as myfile_.bmp and an initflashfiles.txt with the entry such as:
Directory("\Program Files\ProgramB"):-File("myfile.bmp","\windows\myfile_.bmp")
that should work.
** this means that, program A and B would be in \program files\ instead of \windows\.
allan1 said:
cook one in and use a cab for the other!
Click to expand...
Click to collapse
Allan, that will not work as I mentioned in my thread that it will overwrite the file with the same name.
@kazuni
That sounds like a plan, seperating them into different folders. I'm gonna try and see if it works
What about same DLL?
Another questions I have is about same DLL. For example, Comm manager uses a dll called phcanOverbmp.dll. I noticed that the "White battery Icon" fix also uses the same DLL, but they are of different size with Comm manager's version @ 500+kb, while the battery fix version @ at smaller size.
Which DLL should I keep?
Can I keep the one that is larger and apply the registry settings found in the battery fix?
kin0kin said:
Another questions I have is about same DLL. For example, Comm manager uses a dll called phcanOverbmp.dll. I noticed that the "White battery Icon" fix also uses the same DLL, but they are of different size with Comm manager's version @ 500+kb, while the battery fix version @ at smaller size.
Which DLL should I keep?
Can I keep the one that is larger and apply the registry settings found in the battery fix?
Click to expand...
Click to collapse
as long as your program isnt hard coded to use \windows\phcanOverbmp.dll then you can make the OEM package for Comm Manager to reside in another folder and use its own phcnaOverbmp.dll
if not, then you will have to try and see if you do not apply the battery fix at rom cooking, then manually copy the file over into your pda after bootup, and see. that way, you are trying both original commanager and batteryfix's phcanOverbmp.dll and see if they can coexist.
remember, you cannot use file explorer to copy over a file that already existed in rom from another location. you would have to copy it as a different name, and then put it inside \windows\ and then rename the file as the original file name.
see if that helps?
actually, I don't think I even need to replace the phcanOverbmp.dll
the "fix" pretty much just sets the parameter "BatteryIconIdStart" to integer: 1001
Looking at the fix in Schap's thread, the Integer was set to 1000....does anybody know what difference does it make?
The .bmp in the taskmanager isn't needed.
The phcanoverbmp in the comm manager is a stock version. Remove it from the package if your going to install a custom one from somewhere else. The larger one probably has Schaps battery indicator.
Typically, duplicate files are caused from re-introducting a file that isn't needed - typically from to packages that were compiled and one inadvertently getting an unnecessary file.
You're on the right track with asking what the difference is, but sometimes I'll grab a cab for the package I'm trying to install and compare the files. In many cases, that's solved the mystery.
Another suggestion is if you're customizing your own kitchen, you might put everything into the OEMApps folder. Thay way you're not adding additional .dsm/.rgu files into your rom unnecessarily. Just copy the files over and paste the .rgu contents (following the guildelines for doing so) to the OEMApps folder .rgu.
Matt,
Actually most of the time I'd take the cab, decommission it, and compare it to some of the premade packages to see what the differences are, then i'd use my own discretion to recreate my own package.
Another suggestion is if you're customizing your own kitchen, you might put everything into the OEMApps folder. Thay way you're not adding additional .dsm/.rgu files into your rom unnecessarily. Just copy the files over and paste the .rgu contents
Click to expand...
Click to collapse
You mean I could just go into the packages, take out all the content and copy them into OEMApps, along with the respective .rgu?
What happens to the initflashfiles.txt then? Do I combine all the initflashfiles into one big initflashfiles for all the apps and put it in there as well?
And the benefit of doing this is saving some spaces from the all the .dsm files?
yeah, you would also need to put in the appropriate entries for the initflashfiles.txt
one little advice, i have had a lot of problem with his is that,
option.xml is in UTF format;
initflashfiles.txt is in UTF format;
anything.rgu is in UTF format as well;
but shortcuts are all in ANSI stardard format.
have fun
lol, yeah most of them are in unicode. When I just started getting into cooking, I wasn't even sure if .dsm is suppose to be in unicode or ansi since most of the guides only say to create rgu in unicode, none said anything about whether dsm should also be in unicode or ansi. But anyway, for those who are looking for the answer, .dsm is in ansi
Problem #1
I've still got a few tiny bugs I need to fix for my rom. When I create the "accessories" and "system tools" folder with the line:
Code:
Directory("\Windows\Start Menu\Programs"):-Directory("Accessories")
Directory("\Windows\Start Menu\Programs\Accessories"):-File("W5torage.lnk","\Windows\W5torage.lnk")
The first line should create the folder for accessories. However, the folder that it created is just the generic folder.
How can I get windows to create the accessories folder like the one in the picture below?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Should I be be using the code:
Code:
Directory("\Windows\Start Menu\Programs"):-[B][COLOR="Red"]PermDir[/COLOR][/B]("Accessories")
??
Same goes for the system folder.
Problem #2
Another thing I'm having problem with is getting autoconfig to run. I've created the following:
Folder name: Preconfig
With the following content:
-preautorun.exe
-preautorun.lnk
-HTC_Default.tsk
-Preconfig.txt
Code:
LOCK:Enabled
EXEC:\Windows\SetHSDPA.exe /Enable
EXEC:\Windows\cusTSK.exe \Windows\HTC_Default.tsk
LOCK:Disabled
RST: Reset
I then created a dsm file and populated it with buildDSM. I toss it into the OEM folder and ran buildOS....it didn't work Am I missing something?
BTW, kazuni & matt, thanks for helping me out, you guys have been really helpful
Edit: Problem two solution
I'm an idiot, it's missing the provxml
Question
What is the App_Service.dll for? I was examining the pandora kitchen's OEM package for Pre-settings and in both ATT preconfig were the App_Service.dll, but it wasnt there in the Orange_UK's presettings..
kin0kin said:
lol, yeah most of them are in unicode. When I just started getting into cooking, I wasn't even sure if .dsm is suppose to be in unicode or ansi since most of the guides only say to create rgu in unicode, none said anything about whether dsm should also be in unicode or ansi. But anyway, for those who are looking for the answer, .dsm is in ansi
Problem #1
I've still got a few tiny bugs I need to fix for my rom. When I create the "accessories" and "system tools" folder with the line:
Code:
Directory("\Windows\Start Menu\Programs"):-Directory("Accessories")
Directory("\Windows\Start Menu\Programs\Accessories"):-File("W5torage.lnk","\Windows\W5torage.lnk")
The first line should create the folder for accessories. However, the folder that it created is just the generic folder.
How can I get windows to create the accessories folder like the one in the picture below?
Should I be be using the code:
Code:
Directory("\Windows\Start Menu\Programs"):-[B][COLOR="Red"]PermDir[/COLOR][/B]("Accessories")
??
Same goes for the system folder.
Problem #2
Another thing I'm having problem with is getting autoconfig to run. I've created the following:
Folder name: Preconfig
With the following content:
-preautorun.exe
-preautorun.lnk
-HTC_Default.tsk
-Preconfig.txt
Code:
LOCK:Enabled
EXEC:\Windows\SetHSDPA.exe /Enable
EXEC:\Windows\cusTSK.exe \Windows\HTC_Default.tsk
LOCK:Disabled
RST: Reset
I then created a dsm file and populated it with buildDSM. I toss it into the OEM folder and ran buildOS....it didn't work Am I missing something?
BTW, kazuni & matt, thanks for helping me out, you guys have been really helpful
Edit: Problem two solution
I'm an idiot, it's missing the provxml
Question
What is the App_Service.dll for? I was examining the pandora kitchen's OEM package for Pre-settings and in both ATT preconfig were the App_Service.dll, but it wasnt there in the Orange_UK's presettings..
Click to expand...
Click to collapse
The only way you can make them is specifying an icon file. if you take a look and unhide the folder there, there is an icon.ico or a dll there.
Actually, I found the solution after looking at the initflashfiles.dat from another rom which has the folders and here's what I found:
Code:
Directory("\Windows\Start Menu\Programs"):-Directory("Accessories")
Directory("\Windows\Start Menu\Programs\Accessories"):-File("icon.lnk","\Windows\accessoriesico.lnk")
Directory("\Windows\Start Menu\Programs"):-Directory("System Tools")
Directory("\Windows\Start Menu\Programs\System Tools"):-File("icon.lnk","\Windows\systemtoolsico.lnk")
That's one less problem!
New Problem
One other odd problem I'm having is with the theme. For some reasons windows wont apply the theme properly for the first time with my rom, the theme is only partially applied with some "leftovers" from the windows default theme...like some parts being blue and etc. Sometimes I need to reapply the theme several times to get it applied properly. Does anybody know what's causing the problem. I've had the same problem last time and somehow it just disappeared in one of my test roms but it is now back.

Inserting .reg files

Hello,
I have my connection-information exported with PHM Regedit, into a reg-file which looks like this:
Code:
[HKEY_CURRENT_USER\Comm]
[HKEY_CURRENT_USER\Comm\EAPOL]
[HKEY_CURRENT_USER\Comm\EAPOL\Config]
[HKEY_CURRENT_USER\Comm\EAPOL\Config\Heerlenerweg_Wifi]
"Enable8021x"=dword:00000000
[HKEY_CURRENT_USER\Comm\EAPOL\Config\Rielity]
"EapTypeId"=dword:0000000d
"Enable8021x"=dword:00000001
[HKEY_CURRENT_USER\Comm\RasBook]
[HKEY_CURRENT_USER\Comm\RasBook\Technific]
"Entry"=hex:\
18,02,4C,00,00,00,00,00,00,00,00,00,00,00,00,00,F8,07,F5,03,00,00,00,00,70,\
3A,E8,03,00,10,00,00,A0,32,74,00,65,00,63,00,68,00,6E,00,69,00,66,00,69,00B,2C,D0,\
30,CA,00,00,00,00
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\MESSAGING]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\MESSAGING\Certificates]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\trust]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\trust\Certificates]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\disallowed]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\disallowed\Certificates]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\ca]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\ca\Certificates]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\MY]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\MY\Certificates]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\Root]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\Root\Certificates]
(removed a lot of .hex since it was personal connection info for VPN etc).
How can I ever import it back into my hard-resetted pocket-pc?
Where can I find email-account register settings?
I really can't find anything that works. Would like to change it in .cab but no tools for that. It is a .reg file.
The best way to do it would be to convert your reg to a (prov)xml and import it with FDCsoft's Task Manager or Advanced Config.
you can use CeReg editor http://ceregeditor.mdsoft.pl/ceregedit_setup.exe
It is not converting my .reg right ... like other converters dit?
Good program, I try it more. Want to export some regsettings in to a UC cab.
Hmm, PHM Regedit does not have REGEDIT 4 as file start.
I just added that with notepad, now it sees the .reg file ok.
CdRegistryeditor is good ...
.reg file imported in TRE
This is my first post on xda-dev
... and i'm not sure that it's the right place to put my information but ...
I've managed to import a .reg file directly on my HTC TyTN under WM6.1 (schaps ROM) with TRE v090 (Tascal Registry Editor):
http://www2r.biglobe.ne.jp/~tascal/download/pocketpc/tre_e.htm
(you can register *.reg files under menu options)
The goal was to insert Environment vars list for www.rainer-keuchel.de ported GNU tools after a new ROM flash.
I've got some error about "syntax error" apparently about some HCR keys,
(certainly some error in my .reg formating)
but all HLM keys were inserted correctly.
I tried PHMregEdit 070 but the import function isn't (yet?) implemented
i'm not a WinCE/Mobile5/6 Systems specialist but hope that this info could help someone.
Riel said:
Hello,
I have my connection-information exported with PHM Regedit, into a reg-file which looks like this:
Code:
[HKEY_CURRENT_USER\Comm]
[HKEY_CURRENT_USER\Comm\EAPOL]
[HKEY_CURRENT_USER\Comm\EAPOL\Config]
[HKEY_CURRENT_USER\Comm\EAPOL\Config\Heerlenerweg_Wifi]
"Enable8021x"=dword:00000000
[HKEY_CURRENT_USER\Comm\EAPOL\Config\Rielity]
"EapTypeId"=dword:0000000d
"Enable8021x"=dword:00000001
[HKEY_CURRENT_USER\Comm\RasBook]
[HKEY_CURRENT_USER\Comm\RasBook\Technific]
"Entry"=hex:\
18,02,4C,00,00,00,00,00,00,00,00,00,00,00,00,00,F8,07,F5,03,00,00,00,00,70,\
3A,E8,03,00,10,00,00,A0,32,74,00,65,00,63,00,68,00,6E,00,69,00,66,00,69,00B,2C,D0,\
30,CA,00,00,00,00
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\MESSAGING]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\MESSAGING\Certificates]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\trust]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\trust\Certificates]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\disallowed]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\disallowed\Certificates]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\ca]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\ca\Certificates]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\MY]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\MY\Certificates]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\Root]
[HKEY_CURRENT_USER\Comm\Security\SystemCertificates\Root\Certificates]
(removed a lot of .hex since it was personal connection info for VPN etc).
How can I ever import it back into my hard-resetted pocket-pc?
Where can I find email-account register settings?
I really can't find anything that works. Would like to change it in .cab but no tools for that. It is a .reg file.
Click to expand...
Click to collapse
..you can use mortskript!
For Email use: http://www.winmo-experts.com/viewtopic.php?f=8&t=3

[APP] Ervius Kitchen package Updater 1.31 16/01/10 - now with .cab file importer

hi all..
there is a new version - 1.31 dated 16/01/10. If you are not using this version you should. there are probably bugfixes and other features you want.
i've made a tool which can be used to update packages in an Ervius kitchen. i made it as Sparkienl updates his kitchens every so often, but sometimes the new version of the kitchen has old versions of the packages.. it can also convert .cab's to EXT kitchen packages
changes -
1.31 - added handling for HKCR registry settings.
- fix for null reference exception (caused by HKCR registry entries).
1.3a - added a default value for app.reg. if keyname = "" then it will write @ into the app.reg
1.3 - added tabs in app rather than stuffing everythign under one form. the .cab file import is now on the options tab. So is the folder mappings button.
- added a preload for the foldermappings.xml file. first time the datagrid is loaded it wont be blank now.
- added a {build} and {device} style combo box rather than assuming build and device numbers.
important. the build number is used when searching for packages in your kitchen. if you use the build number - eg 28014 rather than "common" you might then get duplicate packages inside your kitchen - eg one in c:\kitchen\ext\blackstone\common\package_1_0 and c:\kitchen\ext\blackstone\28014\package_1_0. This can lead to funny issues when you are cooking.
- added an image comparer. take a folder with a few images and then compare it to your kitchen. It will show any image which is different from your kitchen in a grid. you can select images that you want to update your kitchen with. THIS WILL OVERWRITE THE DESTINATION IMAGE WITH NO WARNING.
- added more UI disables when background threads are working. closing the app while the searcher is running will still crash the app though. i know about this one, but it's a 1% thing.
-
1.12a - .cab file import completely fails under win7. fixed.
1.12 - fixed app.dat entries (no really, it should be fixed this time). all files goes into \windows it seems and get copied from there to their proper destination. kinda stupid tbh.
- fixed app.dat shortcuts that were still not fixed in 1.11.
- added a foldermappings.xml file so that each of the variables can be changed for localisation - eg %CE2 -> \windows or it's local equivalent. you dont need to generate this file, if it doesnt exist it will be created with the english (0409) settings. you can then either hand edit the .xml or use the inbuilt editor. i'll add something later on so that you can have multiple locales in a combobox and use different ones.
1.11 - shortcut creation not working 100%.
- multiple registry keys under one branch not being exported properly. fixed.
- binary registry keys not being exported correctly. fixed. notification bar packages (eg dusk taskbar icons) now working properly.
- problem where multiple directories matching a source package name - eg power-* showing up as old version (red), not unknown version (blue). fixed.
1.10 - added import cab function. this can convert a .cab into a kitchen package using the _setup.xm in a wince cab. it will process the registry entries, files, shortcuts and app data and create the app.dat and app.reg files. i have only tested this on a few .cab's (the dusk 2.5 manila theme and the taskbar icons and a few other ones) so tbh i don't know how reliable it its but it seems ok. need feedback on this one please
- added new status icon - grey. when you refresh the package if the package exists in the source but not the kitchen you see a grey icon.
- new packages are now correctly added to kitchen rather than just being passed over.
- added some filters - show missing (packages exist in package source but not in kitchen), show different (versions are different), show same.
- other bugs fixed.. i think the packages.txt was being added to even if the package already existed. maybe some others.
1.02 - added combobox for users to select htc model. blackstone and topaz built in, but if you type in your model into the combobox this app will try and match the folder %kitchenroot%\EXT\%htcmodel%\common\packages.txt. If it finds packages.txt in that folder you can then choose to update packages.txt. It also uses this folder as the root of the packages folder in your kitchen.
- added .erv file updater. if you choose a .erv file from your kitchen this app will try and update it with your updated packages. you'll notice in the kitchen the new version of the package is not grey anymore (ie you dont need to enable it). But, you can only update one .erv file per package update.
1.00 - original version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
images comparer
before you do anything - backup your kitchen. THIS APP WILL MAKE CHANGES
TO YOUR KITCHEN AND IF SOMETHING GOES WRONG IT CAN OVERWRITE/DELETE STUFF.
1. open up the app.
2. point the source folder at your directory that contains kitchen packages
3. point the destination directory at the root of your ervius kitchen (other kitchens won't work (eg PRB), because their directory structures are different to ervius - i might make an update to try and more kitchens to the compatibility list since i know ervius isnt the fastest to cook.). the app will then try and fill in the device model and build numbers. If they are blank the folder structure in your kitchen is wrong.
4. click the refresh 'packages list' button.
the status led colours mean the following -
grey. new package. the package exists in the source, but not in the kitchen. you can choose to add it here.
red. the version in the kitchen is older than the version in your source package folder.
blue. something went wrong getting the destination package version. most likely this util could only find the directory name. also, if that package doesnt exist in your kitchen this will happen also.
yellow. the version of the package in your kitchen is newer than the version in your source folder. you can update it with this old version, but i don't recommend it of course.
green. the two versions are the same.
5. Select the packages you want to update (i advise only one or two each time) and then click copy packages.
6. browse to your .erv file you want to update with the new package versions. if you do this my updater will add the lines to the end of the .erv file and you won't have to enable the new version of the package when it has been updated.
7. click copy packages. packages that turn green have been updated.
8. open up Ervius visual Kitchen and then open up your .erv file. go ahead and cook your rom!.
Image comparer.
In 1.3 i have added an image comparer. It will take a folder of images and try and find images of the same name in your kitchen. hopefully this can help you update your kitchen images. Or atleast have a visual inspection of where images come from. The filter will limit the datagrid to only those images where the filename matches the filter (the filter isnt on the directory).
updated exe due to bug running on win7. if you are using any other version grab this one.
Excellent tool!!! I used to compare the kitchen packages manually but I'm sure your tool will help a whole lot and save time!!!
Did you upload the correct file? I tried to run it but I could never get to the similar screenshot as you showed. The app's title is only "50chickens Kitchen Uploader" and not "50chickens Ervius Kitchen Uploader", and worse it is not functioning.
ah.. you're right!
i uploaded an old build.. sorry about that!.. it's been fixed.
although the people who downloaded the source got the current one
SWEET thanks
So nice, thanks man
new version.
1.10 - added import cab function. this can convert a .cab into a kitchen package using the _setup.xm in a wince cab. it will proces the registry entries, files, shortcuts and app data and create the app.dat and app.reg files. i have only tested this on a few .cab's (the dusk 2.5 manila theme and the taskbar icons and a few other ones) so tbh i don't know how reliable it its but it seems ok. need feedback on this one please
Hey,
This tool works really great!! But I have just one suggestion:
When importing the cab, it presumes that it's going to be used in a WWE or english version of WM. So it uses Program Files, Start Menu etc. instead of the how it's written in the language of the ROM. To make it easy for yourself, maybe it can be defined in an .INI file?
akito said:
Hey,
This tool works really great!! But I have just one suggestion:
When importing the cab, it presumes that it's going to be used in a WWE or english version of WM. So it uses Program Files, Start Menu etc. instead of the how it's written in the language of the ROM. To make it easy for yourself, maybe it can be defined in an .INI file?
Click to expand...
Click to collapse
doesnt sound too hard. check back in a few days.
Looks great,
Can you point me in the right direction to make this compatible with other devices.
Rataplan said:
Looks great,
Can you point me in the right direction to make this compatible with other devices.
Click to expand...
Click to collapse
im not sure what you mean by other devices but you mean other HTC devices all you need to do is edit the combobox where it says blackstone to whatever youre device codename is eg leo, kaiser, hermes etc.
akito said:
Hey,
This tool works really great!! But I have just one suggestion:
When importing the cab, it presumes that it's going to be used in a WWE or english version of WM. So it uses Program Files, Start Menu etc. instead of the how it's written in the language of the ROM. To make it easy for yourself, maybe it can be defined in an .INI file?
Click to expand...
Click to collapse
i know i said a few days.. im almost done
couple of other bugfixes coming too.. you always find more bugs when you try and actually use software rather than just 'testing' it
Don't worry, I'll wait just a bit longer ;-)
akito said:
Don't worry, I'll wait just a bit longer ;-)
Click to expand...
Click to collapse
new version. localising the variables is a bit simple atm.. which i'll expand on so you can keep and use multiple locales in another version soon.
Hey, using Windows XP it works perfectly fine. However, using Windows 7, which I'm using to build the ROM, I can't import any cabs anymore. It crashes immediatly with a error-popup that's coming from .Net. I could get you a screenshot if you wish, however the text that appears will be in dutch as is my Windows 7. Would it be of any help?
akito said:
Hey, using Windows XP it works perfectly fine. However, using Windows 7, which I'm using to build the ROM, I can't import any cabs anymore. It crashes immediatly with a error-popup that's coming from .Net. I could get you a screenshot if you wish, however the text that appears will be in dutch as is my Windows 7. Would it be of any help?
Click to expand...
Click to collapse
try and right click -> run as administrator. but yeah, a screeny will help.
Tried that already, but doesn't solve it unfortunately. I'll get you the screenshot by tomorrow
akito said:
Tried that already, but doesn't solve it unfortunately. I'll get you the screenshot by tomorrow
Click to expand...
Click to collapse
ok.. i get the same prob on my win7 box. so i think it's a prob with building on xp. let me rebuild it on win7 later (going to work now). i've reposted 1.11 in the mean time.. sorry about that!!!
akito said:
Tried that already, but doesn't solve it unfortunately. I'll get you the screenshot by tomorrow
Click to expand...
Click to collapse
yeah for some reason when i build it under xp it has problem loading cablib.dll under win7. probably some oddball win7 .net permissions thing i can't cater for on xp. looks like i can only make release builds at home
50chickens said:
im not sure what you mean by other devices but you mean other HTC devices all you need to do is edit the combobox where it says blackstone to whatever youre device codename is eg leo, kaiser, hermes etc.
Click to expand...
Click to collapse
Sorry for my stupid question, didn't even try, great apps works perfect.
Older Mobile
Will it suppor older mobule phones, like HTC Trinity or Elf?

Categories

Resources