how to dump the newest 19839 ROM？
i found i can't dump it。can anybody tell me？
thanks
search my friend and it will do you wonders....
http://forum.xda-developers.com/showthread.php?t=379559
in this thread it should show you what you need...
no,this is not the way which can dump the 19839 rom your friend UDk made,and besides they just keep it as a secret and ignore every PM which were sent by the person who would be happy to know the truth.and someone just criticize that the other cookers who just start a "Cooker War" and on the other hand he just make some undumpable Rom as the prove of his selfishness.What a ridiculous phenomena....
You can use this http://forum.xda-developers.com/showthread.php?t=384251 tools to dump all polaris ROM's there is only one thing and that is that the cooker removes DSM/RGU files and packages.sof from his ROM and this makes it not possible to use it.
NikMel said:
You can use this http://forum.xda-developers.com/showthread.php?t=384251 tools to dump all polaris ROM's there is only one thing and that is that the cooker removes DSM/RGU files and packages.sof from his ROM and this makes it not possible to use it.
Click to expand...
Click to collapse
thanks,but the rom is only removes dsm and rgu.if u dump it ,u will find the rom is do something by the owner.
so i want to know it.
All roms can be dumped.
Using kitchen tools or Htc Rom Image Editor
http://forum.xda-developers.com/showpost.php?p=2028331&postcount=1
Use dsms & rgus from an older build into your dump directory ....
swtos said:
All roms can be dumped.
Click to expand...
Click to collapse
really do you think what wrote???
ervius said:
really do you think what wrote???
Click to expand...
Click to collapse
what do you mean ?
would it be unreasonable to ask for the dsm and rgu's of matching build to be provided, even in a separate archive? i have no problem with placing them into my dump before packaging, just dont like the idea of dsm/rgu from a different build. i prefer clean, true SYS..
edit: im speaking in general, not specifically for 19839. i just think that alot of authors are spending time reconstructing dumps that would be better spent developing with a known good, easily accessible source.
swtos said:
what do you mean ?
Click to expand...
Click to collapse
nothing.... dump it and rebuild.
dcd1182 said:
would it be unreasonable to ask for the dsm and rgu's of matching build to be provided, even in a separate archive? i have no problem with placing them into my dump before packaging, just dont like the idea of dsm/rgu from a different build. i prefer clean, true SYS..
edit: im speaking in general, not specifically for 19839. i just think that alot of authors are spending time reconstructing dumps that would be better spent developing with a known good, easily accessible source.
Click to expand...
Click to collapse
rgus and sdms are allways the same from build 19716, same!!!
ervius said:
rgus and sdms are allways the same from build 19716, same!!!
Click to expand...
Click to collapse
no, they are not. some SYS rgu's have changed between 19716 and 19199/19202/19209. as the dsm contains the build number info, it goes without saying they are different too.
i really mean no disrespect and i appreciate everything you guys do. ervius, your buildos and other tools are appreciated as well as your ROMs. but my point is that we are putting people to unnecessary trouble. what benefit does anyone gain from this?
dcd1182 said:
no, they are not. some SYS rgu's have changed between 19716 and 19199/19202/19209. as the dsm contains the build number info, it goes without saying they are different too.
i really mean no disrespect and i appreciate everything you guys do. ervius, your buildos and other tools are appreciated as well as your ROMs. but my point is that we are putting people to unnecessary trouble. what benefit does anyone gain from this?
Click to expand...
Click to collapse
yes, dsm contains version, but you solve with my dsm patcher...
and rgu, maybe only 19716 are differents, for me no differences from 19199 and last posted...
I think that microsoft provides us with TRUE SYS 19202 (Mar 24 - April 5 - 2008)....
So, there's no reason to patch dsms... to match a non existing version .....
swtos said:
All roms can be dumped.
Using kitchen tools or Htc Rom Image Editor
http://forum.xda-developers.com/showpost.php?p=2028331&postcount=1
Use dsms & rgus from an older build into your dump directory ....
Click to expand...
Click to collapse
oh,no
swtos,if u dump it?
you should to do it!and if u try ,u will find the rom is different .
does anybody find this?
the dsm youcan use the 19202 or 19209 or 19199,it will ok.
we know the dsm has the information of the ROM,but it's not important.
the important is if u can get the all file from the rom?!
GPRS said:
the dsm youcan use the 19202 or 19209 or 19199,it will ok.
we know the dsm has the information of the ROM,but it's not important.
the important is if u can get the all file from the rom?!
Click to expand...
Click to collapse
no, he cannot, only who protects roms can.....
@ervius
please can you post dsm's & rgu's that worked with your build ??
thanks.
how protected?and how dump?
anbody tell me?help!
yes, I agree with u. swtos's ROM can be dump but can't be rebuilt. I want to know what's the problem of the ROM.
GPRS said:
oh,no
swtos,if u dump it?
you should to do it!and if u try ,u will find the rom is different .
does anybody find this?
Click to expand...
Click to collapse
Related
Hi all, I post this little apps that maybe can help you if you want dump a protected rom (not all, obviously.....) but in some cases it can help.....
how it works:
put a .payload or a .nb file in the same folder of the app, open a command prompt and write:
rom_deprotector os.nb
or
rom_deprotector os.nb.payload
where os.nb / os.nb.payload is the name of your target file.....
wait and finger cross that the target file was protected in a way known by my apps, if my apps "deprotect" the target file, you can dump it then
good lock.....
version 2 a bug on output string solved!
There are a couple different ways to protect a rom. Which method does this one unprotect? imgfs signature mod? file/module header swap?
chavonbravo said:
There are a couple different ways to protect a rom. Which method does this one unprotect? imgfs signature mod? file/module header swap?
Click to expand...
Click to collapse
there are other ways to protect roms, not only theese 2, bwt... it deprotects the 1st one that you told......
so, maybe an old wise will be able to build another "new???" rom.....
haha very nice tool, i am yet to test this out, but it looks very nice. I am going to go out an guess that you and UDK are about 4 steps ahead, and have already been using new ways to protect your roms.
very nice work though once again. you never stop amzing everyone with the work you do.
conflipper said:
haha very nice tool, i am yet to test this out, but it looks very nice. I am going to go out an guess that you and UDK are about 4 steps ahead, and have already been using new ways to protect your roms.
very nice work though once again. you never stop amzing everyone with the work you do.
Click to expand...
Click to collapse
what about???
did it work well???
Maybe I'm doing something wrong, but it doesn't seem to work for me.
I have extracted the nb file out of a nbh file (using NBHextract). Now I try to execute "ROM_Deprotector.exe os.nb" (whereas "os.nb" is the name of my nb file).
But nothing is happening, the command is executed (that means I can type in a new command), but the file stays untouched, and the computer isn't working at all.
What am I doing wrong?
@ervius
Amazing achievement,,,
How can I tell the type of protection added on the rom? Is there a way to find out which rom is capable to be deprotected by your method?
And if you don't mind, I think your tool can be useful as relatively handy to my thread here
johnpatcher said:
Maybe I'm doing something wrong, but it doesn't seem to work for me.
I have extracted the nb file out of a nbh file (using NBHextract). Now I try to execute "ROM_Deprotector.exe os.nb" (whereas "os.nb" is the name of my nb file).
But nothing is happening, the command is executed (that means I can type in a new command), but the file stays untouched, and the computer isn't working at all.
What am I doing wrong?
Click to expand...
Click to collapse
I tested couple of roms and same results keep happening to me.
@ervius,,, would you mind share the details of handling one sample rom as a tutorial to understand this method better?
if my apps "deprotect" the target file, you can dump it then
Click to expand...
Click to collapse
How can i tell if the file got deprotected successfully, and can you explain how you dump it after all?
NOBELOVE said:
I tested couple of roms and same results keep happening to me.
@ervius,,, would you mind share the details of handling one sample rom as a tutorial to understand this method better?
How can i tell if the file got deprotected successfully, and can you explain how you dump it after all?
Click to expand...
Click to collapse
try version 2 attacked to the 1st post!!!!!
to see if it works, try to dump, for example a DIB rom (os.nb), then use deprotector and try to redump it..... to see if rom_deprotector works...
bye!
ervius said:
try version 2 attacked to the 1st post!!!!!
to see if it works, try to dump, for example a DIB rom (os.nb), then use deprotector and try to redump it..... to see if rom_deprotector works...
bye!
Click to expand...
Click to collapse
This rom deprotector doesnt work on my ROMs My ROMs are cooked in your visual kitchen Any ideas ervius?
So am I. The initiative is so great. I had tested with most ROMs out there but didn't have luck at all. Does not matter you use nb or payload.
Hope you find a real way to break it!
hugs
Ameet said:
This rom deprotector doesnt work on my ROMs My ROMs are cooked in your visual kitchen Any ideas ervius?
Click to expand...
Click to collapse
If i rememember right Bepe new kitchen, what ervius is based off, it takes the apps.reg and inserts that into the hives, and so you can not decompile it.
also i think this tool just reconstructs the imgfs start address if a chef decided to mess up the imfgs address.
conflipper said:
If i rememember right Bepe new kitchen, what ervius is based off, it takes the apps.reg and inserts that into the hives, and so you can not decompile it.
also i think this tool just reconstructs the imgfs start address if a chef decided to mess up the imfgs address.
Click to expand...
Click to collapse
yes, you are right!
bepe kitchen produces a dumpable rom, but unusuable to rebuild new roms!
bye!
ervius said:
yes, you are right!
bepe kitchen produces a dumpable rom, but unusuable to rebuild new roms!
bye!
Click to expand...
Click to collapse
Oh ok. Now I get it. So the tool only reverses the protection which is done on the ROM IMGFS header to make it really undumpable. Right? You right about Bepe's kitchen producing dumpable ROMs but due to lack of dumped DSMs & RGUs the ROM is not re-packagable Cool.. Now I get the drift
Mind sharing how to protect the ROM so can be documented in the tutorials?
Used your deprotect tool, it said deprotection done successfully.
But after dumping bepe's rom, all file names, sizes are correct.
Some files, e.g. .lnk files are correct too.
But all .dll and .sys files are all zero padded, and unusable.
if
we provide you with updated ways roms get protected are you up for updateing this sweet little tool?
joshkoss said:
we provide you with updated ways roms get protected are you up for updateing this sweet little tool?
Click to expand...
Click to collapse
sorry for late.....
no, becouse there are a lot of protection, and I don't know all of them... maybe.....
bye!
Dear Ervius
amd NOOB
will this tool will work with ur kitchen build roms. casue when I try to dump ur kitchen's build rom (which is CRACING's wm 6.5 23034 rom) through visual kitchen's build 1.8.1 .. its just build ur kitchen's structure but did nothing with sys, oem and ext folder.. its just resume language as 0000 and dpi as 00
please help me.. I tried ever rom in it. but didnt get result yet
Ladies and gents, would one of you mind sharing a working erv file from your kitchen? I've attempted to build my first Leo ROM and it won't get past the customization. I would like a reference to compare my build to. I don't need a full kitchen, unless you want to share, just the erv to build it.
Thanks guys
silentP
there's already a kitchen thread for this. do a search!
zenkinz said:
there's already a kitchen thread for this. do a search!
Click to expand...
Click to collapse
-nevermind, it's pointless
the erv may vary due to differ packages u may have. so it also pointless.
what problem u hv?
monx® said:
the erv may vary due to differ packages u may have. so it also pointless.
what problem u hv?
Click to expand...
Click to collapse
monx, thanks. The ROM boots and shows the splash screen. It goes to the RunCC and stops. It never finishes or reboots. If I soft-reset, it begins the customization process and hangs. I just wanted to compare what someone else had. I don't want the whole kitchen. I'm using the kitchen here: http://forum.xda-developers.com/showthread.php?t=624672
u need to recmod NTConfig.dll from Notification enhancement. use the NTConfig.dll file. delete the modules.
monx® said:
u need to recmod NTConfig.dll from Notification enhancement. use the NTConfig.dll file. delete the modules.
Click to expand...
Click to collapse
Thank you for taking the time to help. I'll try it.
Respectfully
hi all..
we all have suffered from one common things while making a rom..
after all your hard work and spending so much time and reading on and on for improvements u encounter this
stuck at smart mobility
so i request all people who faced such problems and have solved them,,plz write here about it..
what u have done..??
what is the cause??
this will easier for lots of people to understand why they have non booting rom..
so afterall i got this solution..
1.Make sure the following packages are cooked:
. NetCF or NetCF 3.5
. Dummy FWUPDATE
. Dummy SQM
. WinCENLS_WWE
byDOTCOMPT
2.if your rom gets stuck on radio screen and the screen doesnt dim after a lil bit then you have problem with xip...if the screen does dim it usually means a problem with system.
byTWOPUMPCHUMP
3.recmod ALL modules in your EXT folder
recmod these three folder in sys...browsing, browsingcore, and browsingie
BYTWOPUMPCHUMP
4.ALSO SEE THE ATCHED TXT FILES BY KOKOTAS FOR WHICH FILE TO RECMOD ON PAGE 3
This could be caused by many things.
I suggest you check all last changes you did, which packages/edits etc...
Before I edit my kitchen I always make sure I have a backup incase stuff like this happens so I can refert back.
I recommend editing step by step and not edit to many things at once.
Grtz Leo
Totally agree with Laurentius.
Just some points to look:
1.wince.nls
2.XIP
3.boot.rgu
4.UPXed files
Best Regards!
ps:A Hard Reset would be nice after flashing
kokotas said:
Totally agree with Laurentius.
Just some points to look:
1.wince.nls
2.XIP
3.boot.rgu
4.UPXed files
Best Regards!
ps:A Hard Reset would be nice after flashing
Click to expand...
Click to collapse
almost done..
ok i made a rom 23544..works like a charmm..
but i just upgrade new build like 23548,49,52
all have non booting issue..
no changes have been made from 23544 build not even new application added..
but no luckk.
checked wince..found xip is ok..
also done recmod but no luck..
so now???
i tell u what i just change build 23544,,i got bootable rom..then just chang build ..48..49
non bootable rom
Try XIP 23544, SYS 23548,49,52.
Maybe a bad XIP source?!
If you change to a new MS build you only need MSXipkernel plus SYS.
No recmod is needed, I never use recmod.
Try playing with wincenls, move it from SYS to XIP or maybe viceversa.
Laurentius26 said:
If you change to a new MS build you only need MSXipkernel plus SYS.
No recmod is needed, I never use recmod.
Try playing with wincenls, move it from SYS to XIP or maybe viceversa.
Click to expand...
Click to collapse
but without recmod the kitchen even not building a rom
That's weird, the kitchen should run without recmodding modules.
Maybe you have a conflict in your kitchen where a file is overwriting a module?
saurabh88 said:
but without recmod the kitchen even not building a rom
Click to expand...
Click to collapse
so your rom gets stuck at first screen, with radio info ect on bottom of screen? what modules are you recmodding? do you have hidden and system files visable on your pc? what kitchen are you using? there are alot of things that could cause your rom not to boot, the more info you give the easier it is to help
twopumpchump said:
so your rom gets stuck at first screen, with radio info ect on bottom of screen? what modules are you recmodding? do you have hidden and system files visable on your pc? what kitchen are you using? there are alot of things that could cause your rom not to boot, the more info you give the easier it is to help
Click to expand...
Click to collapse
i use evk..
other things i have already stated before that with same kitchen i can make rom of 23544;but what the fkkkk..i just change build to23548;4951 non bootibg rom...
strange but true.
i just use extra button in evk to recmod as someone already made a post to use extra button via batch file..
saurabh88 said:
i use evk..
other things i have already stated before that with same kitchen i can make rom of 23544;but what the fkkkk..i just change build to23548;4951 non bootibg rom...
strange but true.
i just use extra button in evk to recmod as someone already made a post to use extra button via batch file..
Click to expand...
Click to collapse
Make sure the following packages are cooked:
. NetCF or NetCF 3.5
. Dummy FWUPDATE
. Dummy SQM
. WinCENLS_WWE
Could you post your Build_log.txt here.
-
saurabh88 said:
i use evk..
other things i have already stated before that with same kitchen i can make rom of 23544;but what the fkkkk..i just change build to23548;4951 non bootibg rom...
strange but true.
i just use extra button in evk to recmod as someone already made a post to use extra button via batch file..
Click to expand...
Click to collapse
then obviously something different has been done with the newer builds you are trying to use that wasnt done with 23544. did you recmod 23544 the exact same way as you did the newer ones that didnt work? if your rom gets stuck on radio screen and the screen doesnt dim after a lil bit then you have problem with xip...if the screen does dim it usually means a problem with system. you can use beyond compare to compare the working build to the non-working one, if there is something different you will be able to tell.
twopumpchump said:
then obviously something different has been done with the newer builds you are trying to use that wasnt done with 23544. did you recmod 23544 the exact same way as you did the newer ones that didnt work? if your rom gets stuck on radio screen and the screen doesnt dim after a lil bit then you have problem with xip...if the screen does dim it usually means a problem with system. you can use beyond compare to compare the working build to the non-working one, if there is something different you will be able to tell.
Click to expand...
Click to collapse
yes screen does not dim..
so what is your suggestion??
Then XIP(MSXIPKernel) is probably the cause.
Did you try a different XIP or a combination of XIP(MSXIPKernel) 23544 and SYS 23548 as I told you before?
From where did you get the 23548-49-52 builds?
Maybe you should download them again?
Best Regards!
saurabh88 said:
yes screen does not dim..
so what is your suggestion??
Click to expand...
Click to collapse
thats why i asked if you have hidden and system files showing on your pc...maybe you left some files/dsm/rgu out of msxipkernel.
kokotas said:
Then XIP(MSXIPKernel) is probably the cause.
Did you try a different XIP or a combination of XIP(MSXIPKernel) 23544 and SYS 23548 as I told you before?
From where did you get the 23548-49-52 builds?
Maybe you should download them again?
Best Regards!
Click to expand...
Click to collapse
yes did it but no luck.....
i download them from da_g thread..
if u can plz give me the link of them to dwnld again
twopumpchump said:
thats why i asked if you have hidden and system files showing on your pc...maybe you left some files/dsm/rgu out of msxipkernel.
Click to expand...
Click to collapse
ok i will compare them and see.l
saurabh88 said:
yes did it but no luck.....
i download them from da_g thread..
if u can plz give me the link of them to dwnld again
Click to expand...
Click to collapse
Have you tried the 23554 that I posted (It is in my Rollups folder, link can be found in NRGZ sticky in this forum)
build log of 23554
still stuck at smart mobility,,,here i attached file plz someone look at it and help me...
i have just sorted them through dump sorter..
Saurabh: see also this post by twopumpchump: http://forum.xda-developers.com/showpost.php?p=6032341&postcount=14
AndrewSh said:
23668 AKU 5307 Windows CE: 5.2 Build 4585 (June 17 2010. 16:05:08)
23668_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409.7z (38.98 MB)
http://www.multiupload.com/BRBSUQU4QD
http://multi-up.com/299136
Re-uploaded by Alexx~
Click to expand...
Click to collapse
Wow! Tried it and seems sooooo faster respect to 23667. My I8000 has increased performances as never before. Now SPB MS carousel is really responsive!
I noticed a lot of changes between 23667 and 23668. Any idea?
And, what about Metadata folder. Up to now I never found it inside a package, but now I did.
fubo73 said:
And, what about Metadata folder. Up to now I never found it inside a package, but now I did.
Click to expand...
Click to collapse
Metadata package is the all the registry entries, gathered together into one place.
utak3r said:
Metadata package is the all the registry entries, gathered together into one place.
Click to expand...
Click to collapse
Are you saying it is built during cooking? If not, why I did not find it in packages so often?
utak3r said:
Metadata package is the all the registry entries, gathered together into one place.
Click to expand...
Click to collapse
user and default.hv in metadata are useless because registry should be created from rgu and provxml while cooking.
The important part of metadata are packages.cif and .sof - they define the order and amount of packages cooked into the rom.
That's why I created my own Metadata with necessary packages list and always use it.
AndrewSh said:
user and default.hv in metadata are useless because registry should be created from rgu and provxml while cooking.
The important part of metadata are packages.cif and .sof - they define the order and amount of packages cooked into the rom.
That's why I created my own Metadata with necessary packages list and always use it.
Click to expand...
Click to collapse
can you please tell us how to edit/adjust packages.cif/packages.sof?
HD2Owner, I already posted that some time ago but no-one cares....
Utility by Barin (asusmobile.ru)
AndrewSh said:
HD2Owner, I already posted that some time ago but no-one cares....
Utility by Barin (asusmobile.ru)
Click to expand...
Click to collapse
thanks alot. is there a english version of this tool available?
HD2Owner, English version is a part of Barin's OSBuilder (which I use as a rom kitchen)
The English discussion and public downloadable release is here
Mmmm interesting I heard itbefore an effectively from you Andrew lets make it important here cause neither me use it... Thanks a lot
Just to make it more understandable - screenshots from packages cif and sof editor from OSBuilder tool
Barin is now on vacation and I have no contact with it, but I hope he will forgive me.
I translated pSofCifBuilder to English.
But IMHO, it's a naughtiness, the best choice would be to use OSBuilder.
Good luck
Alexx~ said:
But IMHO, it's a naughtiness, the best choice would be to use OSBuilder.
Good luck
Click to expand...
Click to collapse
Yea I am starting to like that OSBuilder now...
AndrewSh said:
user and default.hv in metadata are useless because registry should be created from rgu and provxml while cooking.
The important part of metadata are packages.cif and .sof - they define the order and amount of packages cooked into the rom.
That's why I created my own Metadata with necessary packages list and always use it.
Click to expand...
Click to collapse
what if we don't modify packages.sof and cif? i've never ever modified them and i dont think that ever caused a problem to me.
!Aman! said:
what if we don't modify packages.sof and cif? i've never ever modified them and i dont think that ever caused a problem to me.
Click to expand...
Click to collapse
I don't think that anyone has until now, and it doesn't seem to have mattered much, has it? Does the operating system even read either of those files? It seems like they're there for book-keeping, but I could certainly be wrong. There's not much point in modifying them with EVK since most EXT's don't have dsm's, and they get thrown out during cooking, anyway.
!Aman! said:
what if we don't modify packages.sof and cif? i've never ever modified them and i dont think that ever caused a problem to me.
Click to expand...
Click to collapse
Farmer Ted said:
I don't think that anyone has until now, and it doesn't seem to have mattered much, has it? Does the operating system even read either of those files? It seems like they're there for book-keeping, but I could certainly be wrong. There's not much point in modifying them with EVK since most EXT's don't have dsm's, and they get thrown out during cooking, anyway.
Click to expand...
Click to collapse
If you use PRB-based kitchen then it doesn't matter. When you use OSBuilder it DOES matter. Don't know whether even older kitchen like Build OS cares or not.
cnzqy1 said:
If you use PRB-based kitchen then it doesn't matter. When you use OSBuilder it DOES matter. Don't know whether even older kitchen like Build OS cares or not.
Click to expand...
Click to collapse
as i said i never ever modified them, that means it doesnt even matter with Build OS. moreover, using "all packages to one" technique strips most of the info from these files without even affecting the ROM.
In this order, which is specified in packages.sof will be building registry. It is not related to PRB, or OSB, or any other kitchen.
Building registry does rgucomp (default.hv, user.hv and boot.hv) on the list of packages (dsm) from packages.sof
It has always been, regardless of whether old or new kitchen. So no other way.
Further deletion of files dsm ("all packages to one", etc.), nothing to do with the building registry.
P.S. There is a myth that OSB is important packages.sof, and at for other kitchens, it is not needed. This is nonsense. In OSB can view and edit packages.sof and packages.cif. That's all the difference.
well, my point is just that registry is added into the hives even if package has not been mentioned in packages.sof, so why bother editing it?
It is important that packets from the SYS and from OEM (which can be attributed to the group OEMDrivers) were formed in the order of packages.sof. The rest you can adjust with the names (dsm or package, depending on the kitchen).
If you think that the roster of SYS formed not so - you are mistaken.
As an example, you might see messages about the problem of "blank page" in IE.
trust me, i've never modified that file. i always use it without editing, from whichever source i get it. i'm not saying it is useless, but in most cases we don't need to edit this file
Hi there, I am a newb chef, I have recently released my custom ROM into the world and people asked for other languages...
I have a kinda quick way to build all the languages but i have to be at the PC all the time to do it. I was wondering if there is a script or automation tool anyone has to get this done? I've tried searching but not sure exactly what to look for here-any pointers? I could probably live with switching kitchens if anyone knows it can be done easily in another as there are 5 languages now!
e.g. So I can press, say "create ROM", and it'll make ruu_signed-0409.nbh, ruu_signed-0410 etc...
Thanks for any wisdom you care to impart!
arealityfarbetween said:
I could probably live with switching kitchens if anyone knows it can be done easily in another as there are 5 languages now!
Click to expand...
Click to collapse
Oskitchen builds all the selected languages in the same pass and also picks all the right SYS packages (EA/NonEA/AH/CS/etc) while building to avoid having to keep different project files for each language.
airxtreme said:
Oskitchen builds all the selected languages in the same pass and also picks all the right SYS packages (EA/NonEA/AH/CS/etc) while building to avoid having to keep different project files for each language.
Click to expand...
Click to collapse
Wow! I'd read a bit about it but was already setup with EVK, guess i should have made the switch when I had to copy and paste sys packages into the right directories.
Cheers!
airxtreme said:
Oskitchen builds all the selected languages in the same pass and also picks all the right SYS packages (EA/NonEA/AH/CS/etc) while building to avoid having to keep different project files for each language.
Click to expand...
Click to collapse
Does OSkitchen also respect the _skip and _only tags that prb uses ?
NRGZ28 said:
Does OSkitchen also respect the _skip and _only tags that prb uses ?
Click to expand...
Click to collapse
I've always wondered what _skip files are for, i've not seen _only but wasn't looking for them What's the advantages of recognising them/What do they do?
Slightly OT i know...
NRGZ28 said:
Does OSkitchen also respect the _skip and _only tags that prb uses ?
Click to expand...
Click to collapse
The "_skip" file is not copied but anything else is, including _skip_* files
airxtreme said:
The "_skip" file is not copied but anything else is, including _skip_* files
Click to expand...
Click to collapse
Hmm okay. Well I was wondering if your kitchen touches these files or not. I have a huge.. 13 device kitchen.. that works soley on the ability to skip_ or _only include/exclude certain packages in the build chain. Say _skip_Diamond or _only_Leo for certain packages. I have a GUI kitchen for PRB made by myself, but I wouldnt mind trying another kitchen one of these days and yours seems very nice (but I gotta be able to keep the folder/package structure I have now, unfortunately).
NRGZ28 said:
Hmm okay. Well I was wondering if your kitchen touches these files or not. I have a huge.. 13 device kitchen.. that works soley on the ability to skip_ or _only include/exclude certain packages in the build chain. Say _skip_Diamond or _only_Leo for certain packages. I have a GUI kitchen for PRB made by myself, but I wouldnt mind trying another kitchen one of these days and yours seems very nice (but I gotta be able to keep the folder/package structure I have now, unfortunately).
Click to expand...
Click to collapse
The kitchen was designed to leave the source folders completely intact so it shouldn't change anything inside the package folders once the ROM has been imported