Related
Hi could someone post a wm6 link to a pure virgin rom for me to cook, I don't want any extra apps in and if possible would like it to be stripped of useless extras ie games must keep office mobile (not calc)
Many thanks
Gary Hopefully a new cooker if i get the pure rom to startwith
virginity is rare novadays....
I think matt released a "virgin" aka "Naked" version of Pandora1.10... check that thread.
Sign me up for one of those virgins .. oh .. wait.. you mean a different kind of virgin.. lol.
Since you want office (currently not available in a cab) you'll need a rom cooked pretty much specifically to your needs.
I'd suggest reading Faria's and double0fours kitchen guides, then choosing the base you want and building your own with one of the kitchens out there. The learning curve isn't too bad, and that way you can get exactly what you want.
My Problem Is stripping all the S**T out the rom (What dll's go with what EXE's and shortcuts Reg settings to free up as much avail space in rom etc) can add software no problem,
garymeg said:
My Problem Is stripping all the S**T out the rom (What dll's go with what EXE's and shortcuts Reg settings to free up as much avail space in rom etc) can add software no problem,
Click to expand...
Click to collapse
The kitchen uses an application called BuildOS. You check the check boxes for the apps you want, and that's all it installes - in addition to os and sys components. No filtering required.
mattk_r said:
The kitchen uses an application called BuildOS. You check the check boxes for the apps you want, and that's all it installes - in addition to os and sys components. No filtering required.
Click to expand...
Click to collapse
garymeg.....mattk_r is right !
Download, run the kitchen and check or in your case...don't check anything.
Heads up...if you're doing this to save on storage space, you got it wrong. The OS, with or without goodies will be about the same size. The advantage of cooking programs into the ROM is to actually save on storage space. The OS is a region you can not touch once it's built. To install programs afterwards will use up space.
Use the kitchen, do it your way....it's easy.
If you still want to try a pre-cooked rom, the third post in the OS thread in my signature I'm uploading a naked plus camera, office, and media player. I can't strip out media player yet, because there's a file interdependency between Office and Media player that I haven't fixed yet.
A great idea was brought to my attention by DaKender and rather than wait on a poll to fill in, I thought I'd just go ahead and start it.
This thread is only for the request and posting of working packages for kitchens. A great place to learn how to make packages is here.
http://forum.xda-developers.com/showthread.php?t=303195
Kitchen authors, please PM me with posts that can be moved into this thread so you can keep your kitchen threads cleaner and answer tech questions.
If you are posting a package:
1) Packages may only consist of free software or software embedded in a factory ROM.
2) Package(s) must work and have been used by the poster in cooking a ROM. Please state the kitchen you used.
3) Uploads must be named according to contents (i.e. Compressed_Office_2007_for_318_build.zip).
4) You must state the contents of the package in your post. Not every little thing but enough for a person to make an informed decision to use the package or not. Packages do not have to include an option.xml file. However, they must include an initfileflashes.dat as well as .rgu and .dsm files.
5) If your package is too big, please use the uploads/Wizard section of the FTP to post and post the link.
If you are posting a request:
1) Click on the paperclip icon on the main forum page next to this thread to see if a package you are requesting has already been posted. This is the most important rule!
2) Include requests for multiple packages in a single post. No need in cluttering the thread with multiple requests by the same person.
Please keep this thread clean. Useless or off-topic posts will be promptly deleted.
FTP Kitchen Pantry is now open. Please upload packages to there. The address is: ftp://xdaupload:xda:@ftp.xda-developers.com/Uploads/WIZARD/Kitchen_Pantry
Requesting packages for:
Mobireader
SPB Mobile Shell v1.5
Coreplayer v1.04
HTC X-Button-task manager (drop down menu one)
i can provide cab's if necessary. im at college right now so will edit the post later on tonight!
thanx
VoIP Package
Uploaded to the ftp server are the working VoIP packages for WM6. The zip file contains 2 packages which were used to cook my latest ROM in double_ofour's kitchen. No initflashfiles.dat is needed because these are SYS modules.
Link:
ftp://xda:[email protected]/Uploads/WIZARD/Kitchen_Pantry/VoIP.zip
This is a great idea to have an "almighty" thread with all packages around here in one place. I also agree with the idea of requesting packages and fulfilling requests.
I don't understand why people won't cooperate. Unfortunately i don't have any packs on my PC, but i will contribute as soon as possible.
Cheers !
.NET2 SP2
Here's a working package with .NETCF2 SP2. Works in double_ofour's kitchen. .zip file contains one package. There are no modules in this package as in the original.
ftp://xda:[email protected]/Uploads/WIZARD/Kitchen_Pantry/NetCF2_sp2.zip
jwzg said:
FTP Kitchen Pantry is now open. Please upload packages to there. The address is: ftp://xdaupload:xda:@ftp.xda-developers.com/Uploads/WIZARD/Kitchen_Pantry
Click to expand...
Click to collapse
Just wanted to say "THANK YOU" for doing this. I just wish I had the time and knowledge to do it. Will do my best to help contribute, just a busy time at work during the summer season, feel like the one legged man in a butt kicking contest lately....... If I can help out in any way, just let me know, I'll do my best.
DaKender
Does size matter... when it comes to OEM/ROM package, that is?
I'm understanding the 54-ish mb ROM limit, but Can anyone off the top of their heads say how that breaks down system vs. extras? What the OEM folder size limit? How much memory does it actually save to put less stuff in the OEM, all? None? some? How different is the TouchMyCube built in, size-wise. Anyone tried sticking in the cube after flashing?
OK, this went a little too far, but it would be nice to benefit from experience rather than fumble around trying something new (there I go again).
I think it's a stitch that people are flashing using mirrors....
BTW, I'm working on a cab list for the pantry so people can taste before they buy. Feel free to PM me if you know one that probably isn't posted or might be hard to find. (Got the ArcSoft MMS; thx Ingenetics for asking for it.)
(Up to interpretation: )
You can eliminate packages from either side, so the question might possibly be. "What packages can be deleted from the SYS folder to make room for additional OEM folder items?" Many people have removed VoIP, Catalog(ue), Voice Command, Windows Live, Autoupdate and Office Mobile to name most. All but Autoupdate and Catalog(ue) are deleted or have different versions placed in the various official ROM's. It's really a zero-sum game adding and subtracting packages.
\Windows
After cooking a couple roms (nothing special, nor would I want to publish them as they are, but working on it) I'm pretty convinced that the more there is in the Windows directory the slower the OS. I did a bunch of the regedits manually b4 build instead of using rgus and deleted Adobe, replaced it w/ Xpdf (1/3 the size & I like it better, plus the source code is available) and MS Voice Command and got a substantial performance difference, subjectively, even after installing lots and lots of other crap (Cyberon Voice dial & commander, gigantic spb stuff, pocket informant... locally (\Program Files and on card). What softwate do people use for benchmarking?
Any chance we could get one of these threads in the Hermes WM6 forum. There
seems to be a lot of interest in home cooking right now with the release of Core and Pandora kitchens.
I've uploaded four new packages today.
Office 2 k 7 Compressed for Build 318: The exe's only have been compressed. This package integrates the fix needed to make 2 k 7 run on versions of WM6 that do not already have it. It was used to cook my own ROM. It contains no initflashfiles.dat.
ftp://xda:[email protected]tp.xda-developers.com/Uploads/WIZARD/Kitchen_Pantry/Office_2007_Compressed.zip
Windows Live Search: Latest version (I think). Contains initflashfiles.dat and shortcuts.
ftp://xda:[email protected]/Uploads/WIZARD/Kitchen_Pantry/Live Search.zip
Esmertec Java: Version comes from the Herald. I'll edit the post after a while to give numbers. Contains initflashfiles.dat and shortcuts.
ftp://xda:[email protected]/Uploads/WIZARD/Kitchen_Pantry/Esmertec Java.zip
Hey Jwgz!
How's going btw?
I'm almost releasing my own ROM finally! Have been cooking so many ROM's with so many different kitchens and I think I can upload a few functional OEM packages! But It will be directly via upload link at our FTP server.
So, preparing and update news later when I finish!
Good initiative !
Rgs,
Xpdf
Can somebody please upload xpdf package. I am looking for files to cook in a ROM, not the cab file. Thanks in advance.
I'm well guys...I'm just swamped at the moment. New job, new house and that's just the beginning. I'll be keeping in touch. I have the pocketxpdf package, but I'm on a dial-up connection right now. As soon as I can get real internet, I'll do it. If someone can beat me to it though...
Pocketxpdf
Initflashfiles included along with .dsm file and fonts. Used in my personal ROM.
ftp://xda:[email protected]/Uploads/WIZARD/Kitchen_Pantry/PocketXpdf.zip
OEM Pack compilation
No doubt you guys have seen the massive OEM Pack included in mattk_r's Rom Kitchen. Links to ver 3.9 are in the first post here:
http://forum.xda-developers.com/showthread.php?t=311144
I sent in some packages that may make it into ver 4.0, but also want to cross post here in case someone's looking for them. Sorry for the double post:
http://forum.xda-developers.com/showpost.php?p=1436358&postcount=133
Include in my attachment are xnView Pocket, cLaunch today plug-in, Calendar Plus today plug-in, Tascal Reg Editor, a Unit Conversion utility, and a simple countdown timer I use when grilling steaks. Cheers
Maybe you can add to the first post that request and posts of paid for software isn't allowed. Or maybe i'm wrong in understanding this rule.
Also maybe a link to....... Man is the search horrib
http://forum.xda-developers.com/showthread.php?t=303195
Which explains how to make an OEM package?
You said it yourself,
Wholy Wonderbra's Batman, This Looks almost two zebra's!
I have not yet looked if there exists a Shozu package.
XDA Mobile 6 Release 4 Cooking Pack
Build your own flavor of XM6r4
By popular demand, I'm releasing the XDA Mobile 6 Release 4 (XM6r4) Cooking Pack. Basically, this is just a the ROM / SYS / OEM folders that I used to build XM6r4. Those so inclined, can download this and build their own flavor of XM6r4 and customize it to their heart's content.
NOTE: This is NOT a Kitchen, but is "guts" of the kitchen. I personally used anichillus' HyperCore Kitchen to build XM6r4, and recommend this kitchen. But since most all of the Wizard kitchens I've seen are almost all alike, these folders will probably work in the majority with only minor changes.
How to Use the Cooking Pack
First you need to download a kitchen and install it per the instructions for that kitchen. NOTE: This thread is NOT for supporting kitchens, and is NOT for general questions on cooking. It will be for the usage of this Kitchen pack. I'll reserve the next post or two and will add specifics that are posted about how to make this work with other kitchens if there are changes needed.
After you get your kitchen setup, then download the XM6r4 Cooking Pack. Unzip the file and place the ROM, SYS, and OEM folders under the kitchen directory where it belongs (for HyperCore, these folders will go under the Build folder).
At this point you are basically ready to cook.
Where are the options.xml files???
My style of cooking may be a little different than what some are used to. For me, rather than having a BuildOS that is loaded with lots of options, I personally prefer to have an OEM directory which (in most cases) is what is going into the rom, and another directory for things that won't go into the rom (OEM-Hold or somesuch. Call it what you want). Then all I do is take OEM packages I don't want in the ROM from the OEM folder and move them to the OEM-Hold folder. By doing this, they won't be part of the rom (and you don't have to deal with checking and unchecking things in BuildOS). If you don't like this style, then feel free to create options.xml files for each of the OEM packages and you can then check and uncheck to your heart's content. Some of the packages do have options.xml, so you can use those as examples on how to set that if (if thats what you want).
If you want to add things to the rom, you'll need to create the OEM packages and drop those in the OEM folder.
Final Notes
This is an exact copy of the folders I used in building XM6r4. I have not upgraded or changed anything (so the same bugs and features in the built version will be in this cooking pack). A lot of the pieces originated from mattk_r and theloon's kitchen work for the 318 ROM. Then I've made changes to those bases to create the XM6 series. Most OEM folders found in theloon's kitchen work will probably work with this cooking pack (but no guarantees).
Official Download Sites for XM6r4 Cooking Pack
HTTP Download
Happy Cooking!
.
Extras
Splash Screens
Attached are the BMP and PNG files used for the splash screens on XM6r4. While the graphics are not mine originally (I've found them here in the forums but asked permission for their use) some modifications are by me. If you are using HyperCore, there are tools for building splash screens in that kitchen.
NOTE: For me, the first splash screen (the so called HTC Logo, which I used the Cylon image for) tends to be the trickiest one. If the file size and complexity of the graphic isn't just right, the screen will not show up properly. If you are trying to build your own htc logo splash screen and having problems, use a graphic editor to convert it from BMP to GIF. Then close the image completely (important) and then reopen it, and then convert the GIF back to BMP. This will sometimes work. If not, then convert the image to a jpg and increase the compression level to be below 50% (the image will start to get grainy and not look as good so you'll have to play around with this). Then close the image and then reopen the jpg then convert it back to a BMP and try again.
Corrected Arcsoft MMS Folder
You can download the Corrected Arcsoft MMS Folder from HERE. Then just extract the contents of this zip file to your OEM folder and it will replace the existing Arcsoft MMS folder. This will fix the bug that was in the original XM6r4 rom. Note that due to filesizes in this patch, you will NOT be able to rebuild a full XM6r4 with this patch. You will have to remove something else as the patch makes the entire rom too big.
Basically this patch is an example of the dangers of compressing things. I had compressed some of the larger MMS files, and it turns out that this broke parts of the MMS application.
This space is intentionally left blank
Thanks...
downloading the cooking pack right now...
love your work...
and thanks for sharing the pack and the roms...
Do these folders have the mms folder fix that was an addon cab in the R4 thread?
thx mfrazzz,
this is the best "Sinterklaas kado" (it's typical dutch) I could get. I've alway great fan of your rom and customized to my own settings.
one question, your three start up screens, are they included? because there are nice.
I just hope this doesn't mean you're not going to develop for the HTC Wizard anymore ...
I am convinced that this is a great base ... so ...this means you're Santa and you came early this year
Take Care !
anichillus said:
I just hope this doesn't mean you're not going to develop for the HTC Wizard anymore ...
I am convinced that this is a great base ... so ...this means you're Santa and you came early this year
Click to expand...
Click to collapse
Lets just say that "Santa" hasn't come yet (its only 8-Dec after all!!!)
I meant to do this after XM6r3 but just never got around to doing it. Wanted to release this now before I started doing anything else.
famewolf said:
Do these folders have the mms folder fix that was an addon cab in the R4 thread?
Click to expand...
Click to collapse
Nope, they don't. I'll update the second post with the replacement files for the MMS folder. Thanks for reminding me. Watch for this later today / tonight (US Mountain Time).
daheufster said:
this is the best "Sinterklaas kado" (it's typical dutch) I could get. I've alway great fan of your rom and customized to my own settings.
one question, your three start up screens, are they included? because there are nice.
Click to expand...
Click to collapse
Thanks for that! And thanks for the reminders of the splash screens. I'll upload those later too.
The second post has been updated with a file containing the splash screen graphic files, and a download link for the XM6r4 patch (which is just a replacement of the Arcsoft MMS folder in the OEM packages).
Are the splash screens just BMPs with the extensions changed?
I've tried several times to make a flash that JUST changes the splash, and what I get simply won't load - it goes to 90% and freezes....... 320x240, BMP, 24 bit color depth - which should be right.....
Genesis3 said:
Are the splash screens just BMPs with the extensions changed?
I've tried several times to make a flash that JUST changes the splash, and what I get simply won't load - it goes to 90% and freezes....... 320x240, BMP, 24 bit color depth - which should be right.....
Click to expand...
Click to collapse
No, you have to "cook" the splash screens. In HyperCore there is a script to help you do this. Or the old tried and true way that I've used in the past is from this post: http://forum.xda-developers.com/showthread.php?t=284006&highlight=splash
But its not just changing the extensions... You have to build the .nb files that then get built into an .nbf file.
Aha! Grabbed the other package... thanks.
BTW, the Hypercore Kitchen is flagged as having a nasty Trojan embedded in it by my antivirus software..... your R4 kit doesn't work with the 1933 kitchen..... it appears to, but doesn't build the image - it looks like there are some missing pieces......
Oh, it also doesn't work with Faria's kitchen..... hmmm.... are there things missing in general?
Genesis3 said:
Aha! Grabbed the other package... thanks.
BTW, the Hypercore Kitchen is flagged as having a nasty Trojan embedded in it by my antivirus software..... your R4 kit doesn't work with the 1933 kitchen..... it appears to, but doesn't build the image - it looks like there are some missing pieces......
Oh, it also doesn't work with Faria's kitchen..... hmmm.... are there things missing in general?
Click to expand...
Click to collapse
Try the following:
Grab the r4 rom...extract the rom to the kitchen of your choice then replace the folders using the r4 kit provided...then replace the mms folder (fix) then tweak.
Uh, what tool do I use to extract the rom?
That one's a new one for me
your roms is very nice and thanks for sharing the pack !!!
Genesis3 said:
BTW, the Hypercore Kitchen is flagged as having a nasty Trojan embedded in it by my antivirus software..... your R4 kit doesn't work with the 1933 kitchen..... it appears to, but doesn't build the image - it looks like there are some missing pieces......
Oh, it also doesn't work with Faria's kitchen..... hmmm.... are there things missing in general?
Click to expand...
Click to collapse
I haven't downloaded the HyperCore Kitchen lately, but there was no Trojan or Virus in it previously (a few months ago). What antivirus software are you running? I know in the past some kitchens (I believe Faria's did this too) were flagged with virus and stuff when they really didn't have them.
As for the 1933 kitchen, why does it now work? Can you give more specifics? Sometimes some of the kitchens just require the os.nb file to be named differently in the ROM folder.
BuildOS appears to run normally but the CreateROM program fails with an error.
I will see if I can figure out what's up with it....
If its just a naming problem that's easy enough to fix.
Genesis3 said:
BuildOS appears to run normally but the CreateROM program fails with an error.
I will see if I can figure out what's up with it....
If its just a naming problem that's easy enough to fix.
Click to expand...
Click to collapse
Is the error near the end of task? When CreateROM fails with an error normally this is caused because the amount of extra OEM packages exceed the maxium ROM size. When this occures CreateROM gives an error.
No, it was right up front, but it appears that I found the problem - it was a rename on the original OS file that was required.
It builds now..... I need to sort out the size issues (they're still there) and then play with this .vs. my 1933 custom hack job to see what I prefer.
The only "gotcha" I have open on my 1933 build right now (a mix of V1 and V2 which appears to work very well in general) is that the camera won't record video - there are obviously some DLL problems somewhere, and just stuffing the Camera 3 package in there from some of the other kitchens does not fix it - so its in the base OS somewhere.
dang I been trying to figure this out all day.
I copied the oem and sys folders into the hypercore build directory, put in files that I did not want into the package folder, but I dunno how to build the os from there
How does one extract a CAB from a ROM?
For instance if I want to cook my own ROM, but I want to use some of the applications in say Dutty's latest release, how do I get those cab packages to install on my own?
Particularly, i am interested in pulling the latest remote desktop off of the latest test Tilt ROM because it has the ability to map the mobile's local storage.
thanks!
one word: RTFW.
Read The FFing Wiki!!
If I could find it on here I wouldn't have posted asking about it.
This is the first of my posts that have been met with a response like this, but honestly go troll somewhere else. It is 0% productive to make responses like that. You are cluttering up the forum with usesless posts (as much as I would be guilty of if this is indeed described in the wiki). If it's in the wiki, why don't you point me to where?
The wiki isn't a single page as much as you'd like to believe, it' links to hundreds and thousands of posts of information.
I have CIM and SIM unlocked my device, flashed about 5 different ROMS and radios and done numerous other things with info I have gotten from the wiki. I read through the ROM cooking kitchen tutorials, but could not find anything which mentions my task at hand. I found information and links on the cooking tutorials to use OEM cabs that people had already extracted....but what if the one I want isn't there? Where is the info that tells me how to pull one OUT of a ROM (instead of putting one already extracted IN)?
So, either you are misunderstanding what i want to do, or else the way i am phrasing it is misleading, both to you and to myself, which is maybe why i can't find the info I want.
So, please your brilliance, point me to location in the Wiki that would describe a procedure where i would be able to extract a .CAB (like Windows Mobile Desktop) from the latest AT&T test ROM.
Otherwise your contributions to this thread are unwanted.
while maarten might have pointed you in the wrong direction, your thread is still a redundant one. if you tried to search, you will find lots of threads covering this subject. and yea, your search results are probably gonna end up with tons of threads that end up looking like this thread, but if you sift through the results.......and by sift i mean u really really sift, i promise you, you will find something useful.
Simple Answer...
...You can't extract a CAB from a ROM usually.
Explanation: In the ROM itself things like windows live are extracted from the CAB already and are installed, so the CAB itself is not there. If your original question was how do I extract the files needed to MAKE a CAB.. then that's more complex, a different question, and a waste of your time if you don't already know how to do it.
If you really want to learn you will have to search.. if you just want a CAB of the latest windows live messenger get the build number by installing the ROM and looking in the application for it.. then use the google search of xda-developers (e.g. "Windows Live" <build number> )and you can be sure you will find someone has already done the hard work for you.
hope that helps.
You find threads on converting CAB's to OEM packages but not the other way round.
The trouble is when you extract a ROM, you'll probably find in the SYS directory, the OEM folder you want with all the relevent files. BUT you won't know where they all go. And if the files you want are in the OEMApps folder you won't know what files need to go together. What I do is look at a similar OEM package (See Alex's excellent work) and this will show the files you need, where they go plus any registry settings. You can probably copy over the newer files from your extracted ROM to the OEM package, overwriting the older files.
If the OEM package doesn't exist it will be a long, long job!! You need to search through the files on a device with the installed ROM and make a note of the location of the application files - this is required for the install.txt file. The next problem (& the major one) is to find any relevant registry settings - again you can search through the registry of the installed ROM. Now all this take a lot of time and effort...
odyseus said:
The next problem (& the major one) is to find any relevant registry settings - again you can search through the registry of the installed ROM. Now all this take a lot of time and effort...
Click to expand...
Click to collapse
You can cheat a little bit here though, some apps will recreate any missing entries with sensible defaults if you leave them out.. others wont.. for those you can find ANY version of the CAB that you want to use (even an older one say) and use its registry as a guide to where to find the ones for the new version.. the registry locations dont change that much between versions usually.
you'll still get issues.. but in most cases this helps if not works
Thanks for your info sambartle and odyseus. I had feared as much based on what I had found through search already, but thought there might have been a way... I guess _Alex_ and others do quite alot of legwork to extract and make all these things themselves.
I can't quite understand it however.... If I take a windows PC for example (which is similar in it's registry) I couldn't necessarily find all the associated files and registry keys associated with an application. If you are lucky they are all under one folder and one key of the registry... but something like MS Office installs so many shared files, and classes objects into the registry it would be nigh impossible to recreate that (even given the time).
Unfortunately, if the last posts I read are accurate the developers here won't be providing new OEM dumps for a while. Maybe once 6.1 is more widely released microsoft will allow download of the new mobile desktop.
Ah well, thanks for your help.... and to the other posters...it's worthless posts like yours that contribute nothing to the forum that makes extracting useful information through the forum more difficult than it should be.
bengalih said:
Thanks for your info sambartle and odyseus. I had feared as much based on what I had found through search already, but thought there might have been a way... I guess _Alex_ and others do quite alot of legwork to extract and make all these things themselves.
I can't quite understand it however.... If I take a windows PC for example (which is similar in it's registry) I couldn't necessarily find all the associated files and registry keys associated with an application. If you are lucky they are all under one folder and one key of the registry... but something like MS Office installs so many shared files, and classes objects into the registry it would be nigh impossible to recreate that (even given the time).
Click to expand...
Click to collapse
It requires alot of testing and re-installing or re-flashing, sometimes on the same ROM, sometimes on different ones, just to iron out the bugs. It's one of the reasons why I released AT&T and HTC versions in the past, just so that I can have two platforms to test on.
Windows CE is alot simpler than Windows XP by at least 10 fold. Yet there are people who have created portable versions of Microsoft Office through the use of deployment applications like thinstall, so anything *IS* possible, with automation.
Automation that works at the functionality of thinstall for CE doesn't exist because of economies of scale (e.g., it's not worth any developer's time to create a deployment package as robust as Thinstall for the PPC).
bengalih said:
Unfortunately, if the last posts I read are accurate the developers here won't be providing new OEM dumps for a while. Maybe once 6.1 is more widely released microsoft will allow download of the new mobile desktop.
Click to expand...
Click to collapse
Dumping and stripping is relatively easy once you've gotten the hang of it. You just need to keep at it.
Personally, I just don't find it to be challenging any more, since I've done quite a few AT&T/HTC WM6.0s and HTC WM6.1s and I'm now waiting for an official shipped version (no more leaked betas!!!).
bengalih said:
Ah well, thanks for your help.... and to the other posters...it's worthless posts like yours that contribute nothing to the forum that makes extracting useful information through the forum more difficult than it should be.
Click to expand...
Click to collapse
Your initial question / thread starter didn't have many details, so I would have flamed you too, although I would have also provided a link to my OEM Package Tutorial (Creating Packages from ROM files section)
It never hurts to be overly verbose when asking a question. This would make the flamers leave you alone (because they'll just get tired of reading) and should *NOBODY* respond within a couple of days, when you bump it (with flowery encouraging yet challenging words, like 'You guys are so great, but nobody could answer my question?'), nobody will mind that you did, and you will get answers after that bump...
FWIW, I still think this should have been a question asked in the OEM Tutorial thread, which I have subscribed and respond to much more frequently than new threads which I'm not aware of until I actually have the time to READ new threads. It's also because, should anyone have similar questions, it'd be much easier to fiind in the bigger OEM Tutorial thread than in this one...
Hope this helps!
Thanks Alex... as you said you would have provided me the link to your Creating Packages from ROM section which I did gloss over briefly previously but didn't totally see how it helped me (since I was looking for Cabs). But, now that you point me there I again I took another look and got some useful information.
So this is where i am at:
Ok,
So first I extract the ROM using your kitched script, then in the SYS folder I find two folders that seem to be what i want:
RemoteDesktopMobile
RemoteDesktopMobile_Lang_0409
Inside the first folder are subfolders with names like:
MvkLib.dll
and
wpctsc.exe
and inside those are an actual DLL or EXE file, and some other files called imageinfo.bin, imageinfo.txt, and some files S001, S002, s003, etc...
I am going under the assumption that all I need is the .DLL file, and the rest are some sort of uncompiled form of the DLL? (Please let me know if i need to pay attention to those other files.)
So I take all those DLL and EXE files. I also look for and find an INITFLASHFILES.DAT and don't see any references to these files, so i assume they all go in \WINDOWS?
There is also an RGU file inside here that has a few registry keys for this application.
Inside the second folder is just a DSM, and a couple of .txt and .htm files. Since these files aren't in INITFLASHFILES.DAT either, I assume they just go in \WINDOWS?
I also find a provxml file in \OEM\OEM_Lang_0409 called mxipupdate_RemoteDesktopMobile.provxml.
The contents are:
Code:
<wap-provisioningdoc>
<characteristic type="FileOperation">
<characteristic type="%CE11%" translation="install">
<characteristic type="MakeDir" />
<characteristic type="Remote Desktop Mobile.lnk" translation="install">
<characteristic type="Copy">
<parm name="Source" value="%CE2%\wpctsc.lnk" translation="install" />
</characteristic>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
Based on my reading of the links off your page and some further research this file seems to say the following:
Make a directory (if it doesn't exist) called \Windows\Programs (%CE11%)
Make a shortcut in the directory called Remote Desktop Mobile.lnk (the decimal ASCII text) that maps to \Windows\wpctsc.lnk (%CE2%)
So... now I have:
A handful of files...I need to put them in \Windows
I have an RGU file with a couple registry entries I need to import into the registry
I need to make
a shortcut to the exe int the \Programs directory
How then do I now package all this up into a CAB that will automatically perform the above operations?
I know about "makecab" to actually package all these up into a cab. But how to i write the command file that tells it how to do all the provisioning and registry entries?
Please let me know I am on the right track.
Thanks!
Ok...I found a program called WinCE Cab manager that made the process pretty easy. I installed it on my device and it seems to work well.
I have uploaded it here:
http://rapidshare.com/files/104977265/Windows_Mobile_Desktop_6.1.cab.html
Where is the appropriate place to post this to share with others?
yeah like people have said dumping the rom is the way to do it but most roms nowaday dont have the files for you to recook(so no oems)
so the best thing is to do is get the cab yourself and convert it to an oem with ervius's package creator
sorry kidnamedAlbert...I'm not sure where you were getting at there... the whole point of my post was how to get those cabs made from the ROM in the first place. As you can see from the previous posts it seems I have already resolved (or started my way to) getting this done.
Personally, i prefer to have the cab file as I am more interested on just being able to install it on my device then cook it into a ROM. If someone wants to cook it into a ROM that seems to be a well documented procedure if the cab file is already available.
In my case, there was no cab file available for the latest version of Windows Mobile Desktop...so i made my own from the ROM.
Maarten_0031 said:
one word: RTFW.
Read The FFing Wiki!!
Click to expand...
Click to collapse
One word: RELAX and STOP SWEARING, geez.
I am using Alex's kitchen to cook ROMs for my Kaiser(s). I am using the official 5.2.19212 as the base and up until recently it has all worked fine. I keep one Kaiser as my everyday phone and I haven't re-flashed this for about 6-months. The other Kaiser I continually re-flash and test new software on before I let it anywhere near my main phone.
Anyway recently I replaced the Windows Live in my kitchen with the latest official one (I posted on this in another thread). I created the OEM package(s) from the .cab file and also remoduled the .exe, .dll & .mui files using the option 'PkgToolsBuildos-4.3b1.exe'.
Now everything seemed to work - or at least the new Windows Live did. At the same time as this I was testing Microsoft Tag Reader and since I think it will be quite useful I decided to put this in the kitchen. This is where I started to notice problems. MS Tag would start but failed when trying to initialise the camera - the standard camera application worked fine. I also noticed that Office Communicator Mobile 2007 R2 (which I installed from the .cab file) would not run and just hangs the device requiring a soft-reset to get it going again.
After lots of messing aroung I decided to restore a backup of the kitchen and low and behold both MS Tag & Communicator Mobile now work fine. I have since copied most of the newer stuff into the older kitchen (newer LiveSearch, some updated .rgu files etc) and it seems to be working. I haven't updated Windows Live as yet but that is something I will do this morning.
My suspicion is that my use of 'G'Reloc.exe' might be wrong, probably due to my lack of understanding about what it does. I thought that when .exe, .dll & .mui files in packages are remoduled they need to be configured for specific memory locations and this is what G'Reloc.exe does automatically.
I have been making changes to my kitchen - for example when I created the new Windows Live package I remoduled all the files I could and then just ran 'G'Reloc.exe' with the new package in the SYS folder in the kitchen. G'Reloc.exe then searches through the SYS & OEM folders for modules and automatically changes the memory locations the modules will be placed in (relocates them). This seems to be true as when I simply remoduled the Windows Live package and put it in the kitchen it won't run. If I run G'Reloc.exe and then re-flash Windows Live works.
I think G'Reloc.exe has made some irreversible damage to the modules in the kitchen which is resulting in this weird behaviour. I have a backup of the kitchen so I can revert things back quite easily but the main issue is I don't know where I'm going wrong and I think the remoduling & relocating is where it is.
If anyone can please assist or give me any pointers?
Cheers
Andy