[Sept 24, 2008] DK's Kitchen v1 WM6.1, CE OS 5.2.20748 and 5.2.20755

[akadonny]

I think _Alex_ was the last to offer a kitchen and I think it's about time we had a new one. Everyone has their own needs and I know no ROM is perfect so here's my attempt to satisfy everyone. :D

I don't know if I'm going to have the time to answer everyone's questions and to help resolve all issues so I have to ask the community to please help out when you guys can.

Next, on with the thanks and I know I'm going to leave some people out so I apologize in advance. So thanks to these users for the tools and support we use to customize our phones:

-- kyphur, bepe, jerplea, jscepi, cmonex, alltheway, p1tater...

And to these people for helping me test and support my roms:

-- hang.tuah, dani31, -888-, idj1975, ecltech, kmfm$, rkrasny...

Here's what's included in the link:
OEM-3.29: my cleaned up OEM folder based off of 3.29 Dopod ROM
OEM-Packages: my packages created with help from XDA (see attachment for list)
ROM-20748: ported XIP from jerplea, OS.NB edited to show 20748
SYS-20748: ported SYS from jerplea, has 20212 components
SYS-Extras: entertainment (solitaire, bubble breaker), office, onenote, windowslive

And without further ado here's what you need to do:
1. Extract Kitchen.rar to the root of your drive (i.e. c:\ or d:\)
2. Extract OEM-3.29, ROM-20755, SYS-20755 to where you extracted Kitchen.rar
3. Copy packages you want from OEM-Packages to OEM folder
4. Copy packages you want from SYS-Extras to SYS folder
5. Cook and flash, see attached DK's Instructions doc if you need more help

NOTE: The contents of "OEM\OEMXIPKernel" are REQUIRED for cooking if you want your rom to boot

To get 2DManila working you will want to include from OEM-Packages the following:
-- 2DManila, Album, AudioBooster, AudioManager, CommManager, ConcurrenceMgr, VerionInfo, YouTube, Camera, Dshow, (me thinks that's everything)...You also need GoogleMaps.cab and OperaMobile (not included, search Dev&Hack for current version)

My Supa-Clean ROM always have the following:
-- ConcurrenceMgr, OutlookEnhancement, PictureEnhancement, RingtonePlugin, VersionInfo, StartupAnimationEngine, SymbolPad, DShow and mHub

click me if wanna give me a little somethin' (https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=akadonny%40msn%2ecom&item_name=Donate%20to%20DK&no_shipping=0&no_note=1&tax=0&currency_code=USD&lc=US&bn=PP%2dDonationsBF&charset=UTF%2d8)

http://rapidshare.com/files/146363122/DK_s_Kitchen_v1.zip <-- 99MB
http://rapidshare.com/files/146441384/OEMandPackages.zip <-- OEM and Packages Only
http://rapidshare.com/files/146425292/ROM_SYS-20748.zip <-- CE OS 5.2.20748, ROM and SYS only
http://rapidshare.com/files/148174032/ROM_SYS-20755.rar <-- CE OS 5.2.20755, ROM and SYS only

http://www.4shared.com/file/65703329/83b15f7c/SYS_XIP_20755_FIXED.html <-- SYS fixed by KMFM$

[akadonny]

TODO:
- Find and Squash bugs
- Get new Jade PhoneCanvas: Sakajati and uDK seem to have this working, but I'm stumped (HELP!!)
- Jade_VolumeControl: didn't include this because when installed you can't change the in call volume with the scroll wheel
- I got the Jade Camera working, but it doesn't seem to have autofocus so I didn't include it. Anyone have a the files for the camera floating around?

OEM Version Numbers:
RandomAccess - 4_0_18174127_0
OutlookEnhancement - 1_0_33540_4
Album - 2_5_18191330_0
BootLauncher - 1_0_34322_2
AdvancedPowerManagement - 1_5_18162126_1
RingtonePlugin - 1_00_080416_1
CommManager - 2_7_1_8
2DManila - 1_00_18183719_00
TaskManager - 2_1_34563_3
AudioBooster - 2_1_18181827_1
LargeTitleBar - 4_40_0_0
PictureEnhancement - 1_50_18141822_c2
YouTube - 1_5_1818_3522
AdobePDF - 2_5_103401_01R1
ArcsoftMMS - 5_0_31_45
HTCGesture - 1_0_30346_1
mHub - 6_54_080529_E0
SymbolPad - 1_0_29364_0
AudioManager - 2_0_18191228_0
VersionInfo - 1_0_18182525_0
ConcurrenceMgr - 1_1_18143521_0000
StartupAnimationEngine - 1_0_626715_0
DShow - 2_00_080730_0
CAMERA - 4_08_30665_00
EnlargeStartMenu - 1_2_34828_4

[akadonny]

reserved for me again!!

[daigoro64]

Great. Really appreciate your gift.

Thank you very much indeed.

[-888-]

yay! Beautiful gift to our community :D

http://img385.imageshack.us/img385/2814/8882thumbsup2000smallpd9.png

I will add it to my public share in few minutes...

[akadonny]

I aim to please! :p

[ecltech]

akadonny,

Thanks for sharing. Haven't done this in a very long time so maybe I'll give it go. :)

[NotATreoFan]

I downloaded your full 99mb Kitchen, and everything extracts fine. I've cooked up several ROMs so far, so I have a decent understanding of the process.

I apologize if this question has a simple answer, but I am having no luck, so here goes:

I want to use your 20748 build (you mentioned that 20753 has issues with SMS Threading) to update my NATF ROM series. Due to extensive customization I have done to my OEM folder, I would like to keep it as it, and so I extracted your ROM and SYS archives into my existing Kitchen folder. Now this is where it gets complicated...

I have tried using you Kitchen and Alex's Kitchen, both produce different results, and neither seem to work.

Using your Kitchen, the ROM appears to build fine, but OS.nb is nowhere to be found when HTC ROM Tool launches.

If I use Alex's Kitchen with BuildOS 2.7, then I get an error that it cannot find the ROM folder, but after clicking OK, everything builds as normal. However, after flashing the new ROM, my Tilt sits at the initial splash with R G D and will not go any further.

If I update the BuildOS in Alex's Kitchen to 4.3, everything builds correct and the ROM flashes OK, but UC does not run, File Explorer has an AT&T icon for some reason, and Manilla does not work.

--Ultimately, here is my question--

I want to keep the customizations that I have made to both AT&T Official 6.1 ROM (3.57) and HTC's Official WWE (3.28), but I want to use a newer OS build.

Is there a very special/exact combination of things I need to do in order to achieve this?

Thank you for absolutely any insight you can provide.

[Knumb]

@NATF- have you tried mbarvian's Kitchen? I have been using his for awhile now trying to get a decent fully stripped rom....It's pretty decent.

@akadonny- sorry for me to tell him it. I will try yours out too...thanks again for your kitchen. Great if added to Wiki...

[NotATreoFan]

@NATF- have you tried mbarvian's Kitchen? I have been using his for awhile now trying to get a decent fully stripped rom....It's pretty decent.

@akadonny- sorry for me to tell him it. I will try yours out too...thanks again for your kitchen. Great if added to Wiki...

I tried this one also...

I must be doing something wrong since these kitchen's can't all be incompatible with the 20xxx builds (can they?), but I can't seem to figure it out.

[akadonny]

notatreofan,

You should be able to combine your OEM with any ROM and/or SYS. If you run through the kitchen I provided you will need to look for os-new.nb as that is the file that is created. I may be wrong, but I think you need Windows Script 5.6 or something like that. Also, the kitchen needs to be run from the root of a drive so the folder structure looks something like:

C:\Kitchen\OEM
C:\Kitchen\ROM
C:\Kitchen\SYS

After you run !COOK.cmd and it finishes you will have a os-new.nb in your C:\Kitchen folder. Sorry if I'm not understanding correctly. I hope this solves your issue.

All - I removed the 20753 ROM and SYS and added 20755 ROM and SYS

[NotATreoFan]

notatreofan,

You should be able to combine your OEM with any ROM and/or SYS. If you run through the kitchen I provided you will need to look for os-new.nb as that is the file that is created. I may be wrong, but I think you need Windows Script 5.6 or something like that. Also, the kitchen needs to be run from the root of a drive so the folder structure looks something like:

C:\Kitchen\OEM
C:\Kitchen\ROM
C:\Kitchen\SYS

After you run !COOK.cmd and it finishes you will have a os-new.nb in your C:\Kitchen folder. Sorry if I'm not understanding correctly. I hope this solves your issue.

All - I removed the 20753 ROM and SYS and added 20755 ROM and SYS

Thank you for your answer. I could swear this is what I was doing, but I've tried so many things that I cannot remember... I'm going to try this method (again?) now, and I'll report back.

[b16b]

i have the same problem
i put your kitchen d:\Kitchen
after inside there the FOLDER sys and rom from 20755 and oem from 3.29
i push the cook
flash the new rom
and after splash screen with R,G,D no respond :confused:

[NotATreoFan]

My problem continues also.

I can cook successfully if I use the included OEM folders, but mine still causes a freeze at boot.

Plus my packages don't cook in properly using your Kitchen either. I put all of my packages in the OEM folder like your instructions say, and I can see BuildOS processing them, but I know that they're not being integrated because the resulting RUU_signed.nbh file is 28MB too small.

[b16b]

I try now the older 20748
and all working grate
in ABOUT screen have the new number of OS and Build

ACADONY you must test the 20755 again
something going wrong with it

also i can inclunding package with you rom
and your package don't working with alex kitchen

[Knumb]

My problem continues also.

I can cook successfully if I use the included OEM folders, but mine still causes a freeze at boot.

Plus my packages don't cook in properly using your Kitchen either. I put all of my packages in the OEM folder like your instructions say, and I can see BuildOS processing them, but I know that they're not being integrated because the resulting RUU_signed.nbh file is 28MB too small.

I am having the same problem at NATF....any ideas????:confused:

[Black-Rose]

No preblems at all with 20748... about cooking...

The one big problem at this moment is that I don't get connection trough my provider/operator.
Through ActiveSync and wifi, programs like PIE and RSS Hub works but not via G, E, 3G or H.
It has connection, I mean G, E, 3G or H are visible (depends area wich one) and there is coming an another smaller icon of the four icons but no connection with an error... ;(

[b16b]

No preblems at all with 20748... about cooking...

The one big problem at this moment is that I don't get connection trough my provider/operator.
Through ActiveSync and wifi, programs like PIE and RSS Hub works but not via G, E, 3G or H.
It has connection, I mean G, E, 3G or H are visible (depends area wich one) and there is coming an another smaller icon of the four icons but no connection with an error... ;(

the 20748 is only one who working.. but activesync running on backround

20755 stack on splash screen
20753 when flash it start the boot loader screen and say something for error in core try again
:(

[KMFM$]

For those getting stuck at the bootloader with 20755. Check to make sure that wince.nls is either in the ROM\XIP folder or as a package in SYS. This is a known problem with ROM's that hang at the splash screen. This may not be the case here, but it wouldn't hurt to check. I'm downloading 20755 now. I'll see what I can do.

[b16b]

For those getting stuck at the bootloader with 20755. Check to make sure that wince.nls is either in the ROM\XIP folder or as a package in SYS. This is a known problem with ROM's that hang at the splash screen. This may not be the case here, but it wouldn't hurt to check. I'm downloading 20755 now. I'll see what I can do.

you found any solution?
i try to night your tip!!
tell us if you found something

-EDIT-
this tip not working :(

[Knumb]

For those getting stuck at the bootloader with 20755. Check to make sure that wince.nls is either in the ROM\XIP folder or as a package in SYS. This is a known problem with ROM's that hang at the splash screen. This may not be the case here, but it wouldn't hurt to check. I'm downloading 20755 now. I'll see what I can do.

It's in the SYS folder. I tried cooking again and it still gets stuck at the main screen...I haven't done anything with the folders either... any suggestions will be grateful....:confused:

I will try 20748 and let you know...

I cooked 20748 but no packages went in but it flashed with no problems...doesn't give me a choice to coose what I would like in my rom...is there any way you could integrate this into your kitchen like the others?

[KMFM$]

Yeah. The download for the 20755 SYS and ROM folders hadn't finished when I posted that. I just remember coming across that tidbit of information. Mainly that was a problem people were having when attempting to port SYS and OS's to other devices. The wince.nls was missing and as soon as they added it the phone would pass the splash screen. I have the full kitchen now and am still digging around to find the cause of the hang.

Update: It's definitely the SYS folder that has the hiccup. Successfully created a test build with 20755 CE OS and 20748 SYS. I'm going to keep digging for the wrench in the cogs.

[NotATreoFan]

Is there a command for BuildOS to automatically skip duplicate files? The version included with this kitchen stops with an error at every duplicate file.

[kareeem]

Is there a command for BuildOS to automatically skip duplicate files? The version included with this kitchen stops with an error at every duplicate file.
It's the most annoying thing ever, however (afaik) there is no way to stop this. You would have to search the extension and then delete the duplicate. It took me the longest time to get one of my kitchens working because of this.

@ akadonny, great work man. I'll definitely test this out. Could you possible post screenshots of start>settings>sytem memory or tell us how much memory (RAM and ROM) is allocated?

[NotATreoFan]

Update:

I was able to sub BuildOS + PackageTools 2.7 into the kitchen. That version will skip duplicate files.

Also, I tried cooking one more time with the 20755 ROM folder, but this time I used my OEM and SYS folders. The ROM flashed correctly, and made it all the way through customization, but the (C) of the ROM didn't change. Now I see:

Windows Mobile 6.1 Professional
CE OS 5.2.20755 (Build 19214.1.0.4)

Is this still considered a port? Or did using my SYS folder counteract everything?

[b16b]

Update:

I was able to sub BuildOS + PackageTools 2.7 into the kitchen. That version will skip duplicate files.

Also, I tried cooking one more time with the 20755 ROM folder, but this time I used my OEM and SYS folders. The ROM flashed correctly, and made it all the way through customization, but the (C) of the ROM didn't change. Now I see:

Windows Mobile 6.1 Professional
CE OS 5.2.20755 (Build 19214.1.0.4)

Is this still considered a port? Or did using my SYS folder counteract everything?

Yes we all have do this part is the easy way :D
but what can do with Sys?
i try many combo from my SYS and sys20755 but nothing good
This OS is real or FAKE? because if is fake we don't make something deferent only the number :p

[KMFM$]

Update:

I was able to sub BuildOS + PackageTools 2.7 into the kitchen. That version will skip duplicate files.

Also, I tried cooking one more time with the 20755 ROM folder, but this time I used my OEM and SYS folders. The ROM flashed correctly, and made it all the way through customization, but the (C) of the ROM didn't change. Now I see:

Windows Mobile 6.1 Professional
CE OS 5.2.20755 (Build 19214.1.0.4)

Is this still considered a port? Or did using my SYS folder counteract everything?

It's still considered a port because you're using the ported 20755 CE OS. However, since you're using the 19214.1.0.4 SYS and OEM folders I would consider this build a hybrid. An Opal/Jade, Kaiser hybrid; I believe.

[NotATreoFan]

It's still considered a port because you're using the ported 20755 CE OS. However, since you're using the 19214.1.0.4 SYS and OEM folders I would consider this build a hybrid. An Opal/Jade, Kaiser hybrid; I believe.

That's what I figured. Thank you for the confirmation.

[b16b]

Can anyone tell me if this OS 20755 is real or fake (edit the number)

[KMFM$]

Can anyone tell me if this OS 20755 is real or fake (edit the number)

From what I can tell, the OS is real. DK gets his XIP and SYS from jerplea over in the nike forums. He just ports them from there over to the Kaiser.

[gufoluca]

Thank you for the package

Just firt question , there is any Emulator to test the cocked rom before flash on device?

Luca

[b16b]

From what I can tell, the OS is real. DK gets his XIP and SYS from jerplea over in the nike forums. He just ports them from there over to the Kaiser.
also the 20748 is from japarela but is fake :(

[KMFM$]

also the 20748 is from japarela but is fake :(

How do you know it's fake???

[b16b]

How do you know it's fake???
i have read it somewhere in the forum...

-Edit-
ROM-20748: ported XIP from jerplea, OS.NB edited to show 20748
this is from the post #1 from acadony ;)

[NotATreoFan]

i have read it somewhere in the forum...

-Edit-
ROM-20748: ported XIP from jerplea, OS.NB edited to show 20748
this is from the post #1 from acadony ;)

Since it's fake, where did it actually come from?

[Knumb]

i have read it somewhere in the forum...

-Edit-
ROM-20748: ported XIP from jerplea, OS.NB edited to show 20748
this is from the post #1 from acadony ;)

So what version is it since it's not 20748?

[KMFM$]

So what version is it since it's not 20748?

Well, I think the OS.nb is 3.29 (which akadonny specifies that he uses as a base). Though the XIP is 20755, I believe that the OS.nb overwrites the CE OS version with the version that is in the os.nb. That's why I think he edited the number to reflect the XIP. I'm not 100% on this, but I'm fairly certain that is what is going on.
Notice that he doesn't mention editing the 20755 os.nb. Maybe he was able to find an os.nb with ce os 20755, instead of needing to use another os.nb. Either way, it's great that he shared his kitchen.

[Knumb]

Well, I think the OS.nb is 3.29 (which akadonny specifies that he uses as a base). Though the XIP is 20755, I believe that the OS.nb overwrites the CE OS version with the version that is in the os.nb. That's why I think he edited the number to reflect the XIP. I'm not 100% on this, but I'm fairly certain that is what is going on.
Notice that he doesn't mention editing the 20755 os.nb. Maybe he was able to find an os.nb with ce os 20755, instead of needing to use another os.nb. Either way, it's great that he shared his kitchen.

thanks for the info. Did you happen to find where the bug or glitch is with 20755? Another note, it doesn't let me choose the packages I want to cook like mbarvian's or Alex's. Any info is greatly appreciated.

[b16b]

Well, I think the OS.nb is 3.29 (which akadonny specifies that he uses as a base). Though the XIP is 20755, I believe that the OS.nb overwrites the CE OS version with the version that is in the os.nb. That's why I think he edited the number to reflect the XIP. I'm not 100% on this, but I'm fairly certain that is what is going on.
Notice that he doesn't mention editing the 20755 os.nb. Maybe he was able to find an os.nb with ce os 20755, instead of needing to use another os.nb. Either way, it's great that he shared his kitchen.

maybe this is original i don't know maybe is from raphael or diamond.. we have newer tha kaiser os from diamond like 19900 or something like that..

you found solution about sys from 20755
or fix for activesync on 20748?

[akadonny]

The OS.NB that is in the kitchen and that I use in my SUPA-CLEAN rom is from the 3.29 Dopod ROM with 20212 OS. It controls the CE OS version that shows up in "About" so I edit it before cooking. During the cooking process:

1. a temporary dump directory is created during Build OS creating the necessary new components.
2. the OS.NB, in my case it is edited to show the new OS version, gets taken apart into it's components.
3. a new OS.NB is created by combining the necessary Kaiser components and the new OEM, SYS and ROM that you just prepared.

Please correct me if I'm wrong, but this is cooking. You can't just use the OS.NB from other devices and expect your Kaiser to boot up. I am very open and I think I've made clear my source and components used in my rom. So if this is too "fake" for ya, just don't use it. :eek:

Hope that didn't come off as being too harsh. Just wanted to defend my fakeness. :p

[NotATreoFan]

The OS.NB that is in the kitchen and that I use in my SUPA-CLEAN rom is from the 3.29 Dopod ROM with 20212 OS. It controls the CE OS version that shows up in "About" so I edit it before cooking. During the cooking process:

1. a temporary dump directory is created during Build OS creating the necessary new components.
2. the OS.NB, in my case it is edited to show the new OS version, gets taken apart into it's components.
3. a new OS.NB is created by combining the necessary Kaiser components and the new OEM, SYS and ROM that you just prepared.

Please correct me if I'm wrong, but this is cooking. You can't just use the OS.NB from other devices and expect your Kaiser to boot up. I am very open and I think I've made clear my source and components used in my rom. So if this is too "fake" for ya, just don't use it. :eek:

Hope that didn't come off as being too harsh. Just wanted to defend my fakeness. :p

I'm perfectly fine with any combination. I'm just wondering where the different pieces originated from...

[Knumb]

The OS.NB that is in the kitchen and that I use in my SUPA-CLEAN rom is from the 3.29 Dopod ROM with 20212 OS. It controls the CE OS version that shows up in "About" so I edit it before cooking. During the cooking process:

1. a temporary dump directory is created during Build OS creating the necessary new components.
2. the OS.NB, in my case it is edited to show the new OS version, gets taken apart into it's components.
3. a new OS.NB is created by combining the necessary Kaiser components and the new OEM, SYS and ROM that you just prepared.

Please correct me if I'm wrong, but this is cooking. You can't just use the OS.NB from other devices and expect your Kaiser to boot up. I am very open and I think I've made clear my source and components used in my rom. So if this is too "fake" for ya, just don't use it. :eek:

Hope that didn't come off as being too harsh. Just wanted to defend my fakeness. :p


I have no problems with the way you did it. I would like to "fix" why 20755 won't work. I cook it np and then flash np, but it just sticks at the rom, radio version....great job anyways akadonny...;)

[b16b]

The OS.NB that is in the kitchen and that I use in my SUPA-CLEAN rom is from the 3.29 Dopod ROM with 20212 OS. It controls the CE OS version that shows up in "About" so I edit it before cooking. During the cooking process:

1. a temporary dump directory is created during Build OS creating the necessary new components.
2. the OS.NB, in my case it is edited to show the new OS version, gets taken apart into it's components.
3. a new OS.NB is created by combining the necessary Kaiser components and the new OEM, SYS and ROM that you just prepared.

Please correct me if I'm wrong, but this is cooking. You can't just use the OS.NB from other devices and expect your Kaiser to boot up. I am very open and I think I've made clear my source and components used in my rom. So if this is too "fake" for ya, just don't use it. :eek:

Hope that didn't come off as being too harsh. Just wanted to defend my fakeness. :p
thanks for the info..
i don't want to say something for you but i want to now all this 3 info now i'm OK (sorry for my english)
can you check the rom and sys from 20755 if cooked stock to splash screen

[KMFM$]

The OS.NB that is in the kitchen and that I use in my SUPA-CLEAN rom is from the 3.29 Dopod ROM with 20212 OS. It controls the CE OS version that shows up in "About" so I edit it before cooking. During the cooking process:

1. a temporary dump directory is created during Build OS creating the necessary new components.
2. the OS.NB, in my case it is edited to show the new OS version, gets taken apart into it's components.
3. a new OS.NB is created by combining the necessary Kaiser components and the new OEM, SYS and ROM that you just prepared.

Please correct me if I'm wrong, but this is cooking. You can't just use the OS.NB from other devices and expect your Kaiser to boot up. I am very open and I think I've made clear my source and components used in my rom. So if this is too "fake" for ya, just don't use it. :eek:

Hope that didn't come off as being too harsh. Just wanted to defend my fakeness. :p

Thanks for the clarification, DK. I thought that was what was going on. I had tried ROM porting previously and kept running into that issue as well. That something in the OS.nb was changing the CE OS number, because I knew for a fact that I had a working XIP (different CE OS number, of course) but all of my builds kept saying the CE OS of the base ROM opposed to the CE OS version of the XIP. I was just never 100% on that and couldn't specifically find info on it either.
Also, I don't believe anyone was attempting to call you a fake or charlaton or anything like that. I think it is just new cooks to the kitchen trying to figure out where and how the ingredients came/come from. I'm still using your kitchen and ROMs regardless. :D :D

[someyungguy]

Anyone fiqure out why the 20755 gets stuck on splash screen?

[akadonny]

I think I may know why many of you are having boot issues. Different Chef's put their core ROM files in different locations. I actually put some required files in my OEM. When you guys cook with my rom make sure you use everything in:

OEM\OEMXIPKernel

Or make sure you include your versions of ALL the files in OEMXIPKernel. Hope this helps.

[b16b]

I think I may know why many of you are having boot issues. Different Chef's put their core ROM files in different locations. I actually put some required files in my OEM. When you guys cook with my rom make sure you use everything in:

OEM\OEMXIPKernel

Or make sure you include your versions of ALL the files in OEMXIPKernel. Hope this helps.
i think the problem is in FILE SYS because already we have test or your folder
OEM 3.29 + ROM 20755 + SYS 20755 Freeze in splash screen but
OEM 3.29(or my) + ROM 20755 + SYS 20748 starting without problem also with SYS 19214

[KMFM$]

I think I may know why many of you are having boot issues. Different Chef's put their core ROM files in different locations. I actually put some required files in my OEM. When you guys cook with my rom make sure you use everything in:

OEM\OEMXIPKernel

Or make sure you include your versions of ALL the files in OEMXIPKernel. Hope this helps.

Thanks, akadonny. I'll give that a try. I know that personally, when I saw that folder in OEM I said to myself, "That shouldn't be there" (Per porting tut's). So I set that folder aside. I'll go back and give that method a try and see where I get.

[b16b]

Thanks, akadonny. I'll give that a try. I know that personally, when I saw that folder in OEM I said to myself, "That shouldn't be there" (Per porting tut's). So I set that folder aside. I'll go back and give that method a try and see where I get.
you have any result? i don't understand what must change to work?

[KMFM$]

Well, I'm testing a few builds now and I'll post back results. However, by the same deductive reasoning as above I would assume the problem is in the SYS folder. Only because, I have also created builds using CE OS 20755 and different SYS (20748) without problems. I will try to re port the SYS and test that; however, it will not have the same files and tweaks as akadonny's SYS folders.

STATUS

XIP: 20748 SYS: 20748 | WORKS
XIP: 20748 SYS: 20755 | DOES NOT WORK
XIP: 20755 SYS: 20748 | WORKS
XIP: 20755 SYS: 20755 | DOES NOT WORK
XIP: 20755 SYS: 20755_RE-PORTED | DOES WORK



@akadonny - I also want you to know that we are not criticizing you or your kitchen. Please, do not take anything that we say in any form of ill will. Unfortunately, most of us are experiencing problems with using the combination of the 20755 XIP and 20755 SYS.We understand that you are busy and may not have time to delve into this as quickly as we may want you to, if you even wish to do so at all. We are simply trying to find a solution to a problem that many are having. We all sincerely appreciate the time and support for the many ROM's that you have released and that fact that you were kind enough to release your kitchen. I appreciate all the cooks and members who have been kind enough to share the fruits of their hard work. Unfortunately, too many ungrateful people have been forcing wonderful members from our community. I just want to assure those people that do spend their free-time, talents, and skills developing for XDA that there are still respectable members out there that appreciate everything provided to this community.

UPDATE ! ! ! : Hold on tight, boys and girls! I believe I have just fixed the problem with the SYS folder!!!! I need to start with a fresh kitchen to verify the solution (my kitchen is currently FILTHY from all the edits ;) ). If it is in fact the solution, I will zip it up and post it ASAP.

[KMFM$]

OK, guys and gals. I have retested my findings and, indeed, I have corrected the 20755 SYS folder issue. Below you will find the working SYS along with the 20755 ROM folder (if you do not already have it). I have tested the SYS folder twice, and each time the handset boots up properly.

SYS_XIP_20755_FIXED.zip (http://www.4shared.com/file/65703329/83b15f7c/SYS_XIP_20755_FIXED.html)

Please post back your results. :D

[b16b]

OK, guys and gals. I have retested my findings and, indeed, I have corrected the 20755 SYS folder issue. Below you will find the working SYS along with the 20755 ROM folder (if you do not already have it). I have tested the SYS folder twice, and each time the handset boots up properly.

SYS_XIP_20755_FIXED.zip (http://www.4shared.com/file/65703329/83b15f7c/SYS_XIP_20755_FIXED.html)

Please post back your results. :D

Great job my friends also from Acadony i try tonight
but can you tell us where is the problem? how fix it?

[KMFM$]

The solution is fairly simple. Just figuring it out was the chore. If you have the files supplied by akadonny, you really do not need to redownload my fix. Simply download g'reloc here (http://forum.xda-developers.com/showpost.php?p=1524413&postcount=1). Place it in the base of the kitchen; the same place as "!Cook.cmd" and "!Flash.bat". Next, run G'reloc and enter the following values:


Slot 0: 01F90000
Slot 1: 03DD0000
Size of Rom: 83400000
Unknown: 00000000

Then press "Doit!". That's it. When G'reloc has finished you can start using the 20755 SYS folder without issues. :D
NOTE: Sometimes G'reloc may appear to stop running / freeze. IGNORE IT. Simply wait it out. It is still working. Just be patient. :D

[littlemumford]

Hey,

Thanks a lot for you kitchen its great to have one with a D3D compatible rom.

Just one quick n00b question! Is there a way to cook into the rom some registry changes, like the TYTN 2 KB fix??

Thanks

[KMFM$]

Hey,

Thanks a lot for you kitchen its great to have one with a D3D compatible rom.

Just one quick n00b question! Is there a way to cook into the rom some registry changes, like the TYTN 2 KB fix??

Thanks

Sure. You can either edit an existing .provxml, or make a package out of it with Ervius' Package_tool+buildOS (see here (http://wiki.xda-developers.com/index.php?pagename=OEM%20Package%20Tutorial)).
I recommend the second method; since it's a package you can enable/disable it during cooking if you ever need/want to (using Ervius' Package_tools+buildOS 2.7 or higher).
If you go the route of editing an existing .provxml file, read up on this (http://msdn.microsoft.com/en-us/library/ms889522.aspx) and this (http://forum.xda-developers.com/showthread.php?p=2729985#post2729985) first. Make sure that you know the order that the .provxml files will run (mxipcold vs. mxipudate) so that you don't make changes in one .provxml file that will be overwritten by another .provxml file processed later.

[b16b]

Sure. You can either edit an existing .provxml, or make a package out of it with Ervius' Package_tool+buildOS (see here (http://wiki.xda-developers.com/index.php?pagename=OEM%20Package%20Tutorial)).
I recommend the second method; since it's a package you can enable/disable it during cooking if you ever need/want to (using Ervius' Package_tools+buildOS 2.7 or higher).
If you go the route of editing an existing .provxml file, read up on this (http://msdn.microsoft.com/en-us/library/ms889522.aspx) and this (http://forum.xda-developers.com/showthread.php?p=2729985#post2729985) first. Make sure that you know the order that the .provxml files will run (mxipcold vs. mxipudate) so that you don't make changes in one .provxml file that will be overwritten by another .provxml file processed later.

1. can you tell me how cook the .provxml from advance config 3.2?
i have export one .provxml with my settings and i want to cook this

2. can tell me if the build 20.755 have the issue with Activesync who running in background.. can we fix this?

[KMFM$]

1. can you tell me how cook the .provxml from advance config 3.2?
i have export one .provxml with my settings and i want to cook this

2. can tell me if the build 20.755 have the issue with Activesync who running in background.. can we fix this?

1. Well, just try renaming your advanced config provxml to "mxipupdate_zzAdvanced_Config.provxml". Placing the "zz" or will make it run last (or close to last; so that it is not overwritten), I believe (I'm quite sure that the provxml's get processed in alphabetical order with "mxipcold_" processed first then "mxipupdate_" second).

2. Unfortunately, yes. Though I manually implemented the server trick that has worked since WM5 (maybe earlier). Open Activesync on the device then select "Menu > Add Server Source". In the following fields just add random / false information to continue on until you reach the end (make sure you clear the box on the first screen that asks to auto detect the server settings). Click "Finish" and you'll be back at the ActiveSync screen. From here click "Menu > Schedule". Then in new window, select "Manually" (you'll have to scroll up) in the drop down boxes for "Peak times:" and "Off-peak times:". Now you can click "OK". Back in the ActiveSync screen click "Menu > Options", highlight the bogus (fake) server that you just made and then hit "Delete". Exit ActiveSync, and then kill ActiveSync.exe in your task manager. So from now on, the ActiveSync service should not start until you actively (or "Manually") sync. Your "manual" setting will stay, even with the server deleted. :D
I'm not too sure how other cooks handle this situation, but that's how I'm handling it for now. I may do a before and after registry comparison to figure out what keys control this and try and make a package for the kitchen.

[anryl]

attached active sync schedule enabled OEM from HERMES

i did not try it yet as did not received the kaiser yet :cool:

[b16b]

1. Well, just try renaming your advanced config provxml to "mxipupdate_zzAdvanced_Config.provxml". Placing the "zz" or will make it run last (or close to last; so that it is not overwritten), I believe (I'm quite sure that the provxml's get processed in alphabetical order with "mxipcold_" processed first then "mxipupdate_" second).

2. Unfortunately, yes. Though I manually implemented the server trick that has worked since WM5 (maybe earlier). Open Activesync on the device then select "Menu > Add Server Source". In the following fields just add random / false information to continue on until you reach the end (make sure you clear the box on the first screen that asks to auto detect the server settings). Click "Finish" and you'll be back at the ActiveSync screen. From here click "Menu > Schedule". Then in new window, select "Manually" (you'll have to scroll up) in the drop down boxes for "Peak times:" and "Off-peak times:". Now you can click "OK". Back in the ActiveSync screen click "Menu > Options", highlight the bogus (fake) server that you just made and then hit "Delete". Exit ActiveSync, and then kill ActiveSync.exe in your task manager. So from now on, the ActiveSync service should not start until you actively (or "Manually") sync. Your "manual" setting will stay, even with the server deleted. :D
I'm not too sure how other cooks handle this situation, but that's how I'm handling it for now. I may do a before and after registry comparison to figure out what keys control this and try and make a package for the kitchen.

thanks you are great..
1. can tell me the folder for the "mxipupdate_zzAdvanced_Config.provxml"
2. i now this way i have post it to ROMeOS section i try the zip from ANRYL
3. can tell me how cook folder icons i have one .dll with icon inside.. like blackset.dll how cook the icons?

[KMFM$]

thanks you are great..
1. can tell me the folder for the "mxipupdate_zzAdvanced_Config.provxml"
2. i now this way i have post it to ROMeOS section i try the zip from ANRYL
3. can tell me how cook folder icons i have one .dll with icon inside.. like blackset.dll how cook the icons?

1. You can place the .provxml just about anywhere. OEM_APPS would be a good place; however, you could place it in any OEM folder and quite possibly any SYS folder. (Though I would recommend an OEM folder for ease of use)

2. Place the .dll in the SYS\OS folder and edit the initflashfiles.dat file correctly. Use the entries already in the initflashfiles.dat file as an example. This will allow you to have custom folder icons for which ever folders that you specify in the initflashfiles.dat file. Look here (http://forum.xda-developers.com/showpost.php?p=2230497&postcount=14) for a useful tool to help with editing. Your entry should look roughly like this:
Directory("\Windows\Start Menu\Programs"):-File("icon.lnk","\Windows\blackset.dll")Now, you will need to place a shortcut called "icon.lnk" into the "Programs" folder as stated above. This shortcut should target the blackset.dll like so:
29, \Windows\blackset.dll,-0(I'll have to double check this for you, I'm doing it all from memory right now :P)

For the "-0" you would place the number of the icon you wish to show. In the .dll the first icon would be "0", the second icon would be "1", and so on and so forth.

For acutal program icons, you will most likely have to reshack the .exe or .dll that contains the icons you wish to replace. You can also create an .mui so that you are not hacking required system files. Hope this helps.:D

[b16b]

1. You can place the .provxml just about anywhere. OEM_APPS would be a good place; however, you could place it in any OEM folder and quite possibly any SYS folder. (Though I would recommend an OEM folder for ease of use)

2. Place the .dll in the SYS\OS folder and edit the initflashfiles.dat file correctly. Use the entries already in the initflashfiles.dat file as an example. This will allow you to have custom folder icons for which ever folders that you specify in the initflashfiles.dat file. Look here (http://forum.xda-developers.com/showpost.php?p=2230497&postcount=14) for a useful tool to help with editing. Your entry should look roughly like this:
Directory("\Windows\Start Menu\Programs"):-File("icon.lnk","\Windows\blackset.dll")Now, you will need to place a shortcut called "icon.lnk" into the "Programs" folder as stated above. This shortcut should target the blackset.dll like so:
29, \Windows\blackset.dll,-0(I'll have to double check this for you, I'm doing it all from memory right now :P)

For the "-0" you would place the number of the icon you wish to show. In the .dll the first icon would be "0", the second icon would be "1", and so on and so forth.

For acutal program icons, you will most likely have to reshack the .exe or .dll that contains the icons you wish to replace. You can also create an .mui so that you are not hacking required system files. Hope this helps.:D

so if want to use -3 icon from dll for games folder
go to initflashfiles.dat and do edit
write somewhere :
Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\blackset.dll")and down from this
29, \Windows\blackset.dll,-31. what this 29?

ok until here?

2. why must create a .mui and how?

3. if i want to cook xml not provxml from advance config how cook xml?

4. i have problem with smartdialing when install Greek smatdialing lose smartdialing :(

thanks a lot you are great

sorry for all this question but you are only one who shared so easy the knowledge

[KMFM$]

so if want to use -3 icon from dll for games folder
go to initflashfiles.dat and do edit
write somewhere :
Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\blackset.dll")and down from this
29, \Windows\blackset.dll,-31. what this 29?

ok until here?

2. why must create a .mui and how?

3. if i want to cook xml not provxml from advance config how cook xml?

4. i have problem with smartdialing when install Greek smatdialing lose smartdialing :(

thanks a lot you are great

sorry for all this question but you are only one who shared so easy the knowledge

1. Don't worry about the "29", I don't think you need it. Just create the shortcut pointing back to the .dll
\Windows\blackset.dll,-32. Don't worry about creating a ".mui". That is only a "safe" way of editing/replacing system files. I can describe that later in a separate post.

3. This ones easy. Simply rename the advanced config .xml to "mxipupdate_zzAdvancedConfig.provxml". It should work no problem as long there is a <wap-provision> tag in the .xml (which I believe it does).

4. Unfortunately, I'm not too sure about this one. I don't use smartdialing so I don't believe I'd be able to help that much. Sorry. :(

[b16b]

1. Don't worry about the "29", I don't think you need it. Just create the shortcut pointing back to the .dll
\Windows\blackset.dll,-32. Don't worry about creating a ".mui". That is only a "safe" way of editing/replacing system files. I can describe that later in a separate post.

3. This ones easy. Simply rename the advanced config .xml to "mxipupdate_zzAdvancedConfig.provxml". It should work no problem as long there is a <wap-provision> tag in the .xml (which I believe it does).

4. Unfortunately, I'm not too sure about this one. I don't use smartdialing so I don't believe I'd be able to help that much. Sorry. :(

i will waiting to explain #2 ;)

[b16b]

so if want to use -3 icon from dll for games folder
go to initflashfiles.dat and do edit
write somewhere :
Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\blackset.dll")and down from this
29, \Windows\blackset.dll,-3

i think something missing from here..
i think must put the ,-3 and the first line
Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\blackset.dll,-3")right?
and after i wright this simple line?
\Windows\blackset.dll,-3are you sure? and without " "

[KMFM$]

I'll have to double check on that, b16b. I'm doing most of this from memory, so I may be off on a few things. I'll look into it and then I'll repost with explicit instructions. :D

[anryl]

i think something missing from here..
i think must put the ,-3 and the first line
Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\blackset.dll,-3")right?
and after i wright this simple line?
\Windows\blackset.dll,-3are you sure? and without " "

i think it should be a litle different
Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\icongames.lnk")

and you create icongames.lnk with the code of the actual dll file
29#"\Windows\blackset.dll,-3 "

[KMFM$]

i think it should be a litle different
Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\icongames.lnk")and you create icongames.lnk with the code of the actual dll file
29#"\Windows\blackset.dll,-3 "

Yes! That is correct, anryl. Thanks for the post. I knew it was something like that, I just couldn't remember completely off the top of my head. :D

[Strepsils]

Please, help me. How can i port Russian language in my rom. I replace all 409.mui on 419.mui(Russian), i edit boot.rgu and replace OEM_lang folder then run G'Reloc, but see only splash screen on boot... What i do wrong?


P.S. Sorry for my English. I really need your help

[anryl]

Please, help me. How can i port Russian language in my rom. I replace all 409.mui on 419.mui(Russian), i edit boot.rgu and replace OEM_lang folder then run G'Reloc, but see only splash screen on boot... What i do wrong?


P.S. Sorry for my English. I really need your help

it is really hard m8 u have to have the whole OEM russian i did CZECH on HERMES it was really difficult get u self the OFFICIAL russian OEM if there is some then just dump IT on HERMES was OEM wm6.0 working on wm6.1 here u might get wm6.1 official . THE SYS rgu files have to be all checked as well. The best is the reDO initflashfiles.dat :cool: HAVE FUN

[b16b]

i think it should be a litle different
Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\icongames.lnk")and you create icongames.lnk with the code of the actual dll file
29#"\Windows\blackset.dll,-3 "

what this 29#
and if i want to create for folder system tools or position or internet or something else where found the number :confused:
thanks for your help

[KMFM$]

what this 29#
and if i want to create for folder system tools or position or internet or something else where found the number :confused:
thanks for your help

Honestly, I don't remember what that number means. Though I don't recall it having any effect on the use of my folder icons. I'll see what I can look up for you, b16b.

[Knumb]

OK, guys and gals. I have retested my findings and, indeed, I have corrected the 20755 SYS folder issue. Below you will find the working SYS along with the 20755 ROM folder (if you do not already have it). I have tested the SYS folder twice, and each time the handset boots up properly.

SYS_XIP_20755_FIXED.zip (http://www.4shared.com/file/65703329/83b15f7c/SYS_XIP_20755_FIXED.html)

Please post back your results. :D

thanks alot for the fix! Nice to see something new when you return from a trip...;)

[b16b]

Honestly, I don't remember what that number means. Though I don't recall it having any effect on the use of my folder icons. I'll see what I can look up for you, b16b.
Directory("\Windows\Start Menu\Programs"):-Directory("Games")

Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\blackset.dll,-8")
\Window\blackset.dll,-8
Directory("\Windows\Start Menu\Programs\Agenda"):-File("icon.lnk","\Windows\blackset.dll,-7")
\Window\blackset.dll,-7
Directory("\Windows\Start Menu\Programs\Multimedia"):-File("icon.lnk","\Windows\blackset.dll,-10")
"\Window\blackset.dll,-10"
Directory("\Windows\Start Menu\Programs\Position"):-File("icon.lnk","\Windows\blackset.dll,-15")
"\Window\blackset.dll,-15"
Directory("\Windows\Start Menu\Programs\System Tools"):-File("icon.lnk","\Windows\blackset.dll,-3")
29#"\Window\blackset.dll,-3"no one of this combo working :confused:

[At0mAng]

OK, guys and gals. I have retested my findings and, indeed, I have corrected the 20755 SYS folder issue. Below you will find the working SYS along with the 20755 ROM folder (if you do not already have it). I have tested the SYS folder twice, and each time the handset boots up properly.

SYS_XIP_20755_FIXED.zip (http://www.4shared.com/file/65703329/83b15f7c/SYS_XIP_20755_FIXED.html)

Please post back your results. :D

Is there another link for this? I cant download it from 4share.

[akadonny]

OK, guys and gals. I have retested my findings and, indeed, I have corrected the 20755 SYS folder issue. Below you will find the working SYS along with the 20755 ROM folder (if you do not already have it). I have tested the SYS folder twice, and each time the handset boots up properly.

SYS_XIP_20755_FIXED.zip (http://www.4shared.com/file/65703329/83b15f7c/SYS_XIP_20755_FIXED.html)

Please post back your results. :D

Added link to first port. Thank you!!

Sorry I haven't been more active in this thread. I've been working some crazy hours preparing for an audit. Such a pain.

[At0mAng]

Added link to first port. Thank you!!

Sorry I haven't been more active in this thread. I've been working some crazy hours preparing for an audit. Such a pain.

Good luck with your audit.

I am using your package to try to cook my first ROM. Does the AudioBooster work if cooked in?

[anryl]

Directory("\Windows\Start Menu\Programs"):-Directory("Games")

Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\blackset.dll,-8")
\...................
29#"\Window\blackset.dll,-3"no one of this combo working :confused:

wrong :cool:

file icongames.lnk u have to create the file
its like txt file just create icongames.txt and then rename it to icongames.lnk
inside the file just 1 lane
29#"\Windows\blackset.dll,-3 "

this file put into rom somewhere
and then initflashfiles.dat

Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\icongames.lnk")

will create in games file icon.lnk from file icongames.lnk

but thats basic programming m8

just type in command prompt

echo 29#"\Windows\blackset.dll,-3 " > icongames.lnk

this will create the file for you then put the file in you rom :cool:


-- the number 29 i dont know what is it for might be some priority thread number but really dont bother

[KMFM$]

Is there another link for this? I cant download it from 4share.

Where can you download from? Let me know and I'll put up another mirror.
(or you could just check this (http://forum.xda-developers.com/showpost.php?p=2735007&postcount=53) post and do it yourself. G'reloc is a smaller download than the package. :D)

@anryl - Thanks for helping out. Sometimes things don't come across as clearly as we think. I believe your instructions are a little less convoluted than mine. :D

[Mobilez6600]

Many Thanks for you contribute! I like Kaiser and I'll try now your kitchen!

[At0mAng]

Where can you download from? Let me know and I'll put up another mirror.
(or you could just check this (http://forum.xda-developers.com/showpost.php?p=2735007&postcount=53) post and do it yourself. G'reloc is a smaller download than the package. :D)

@anryl - Thanks for helping out. Sometimes things don't come across as clearly as we think. I believe your instructions are a little less convoluted than mine. :D

Thanks. I did the G'reloc trick.

Is anyone else having problems with the task manager? It runs but the drop down for it does not show up in the top right hand corner. Other versions work as they should.

AudioBooster does not work even if it is cooked in.

[freewind29]

Thanks for sharing your kitchen!

I tried to use your kitchen to creat my first own rom, there was no problem at all in the building process, when all were done, and flashed into my kaiser, I couldn't get pass through the first splash screen, any idea what I did wrong?

[Branen]

Does anyone have the silence incoming calls softkey working on this build? I know the Helmi WM6.1 i used before had that option.

[dalingrin]

Really appreciate you posting your kitchen and keeping it updated!

[Black-Rose]

Hi Akadonny,

I want to say I like your kitchen very much. Especially the Splashscreen with the rising sun. ;)

Unfortunately I don't get the camera to work; I don't know why I'll try find out...

I've done the G'reloc trick of KMFM$, I can cook with 20755 too!
Through this post many thanx to KMFM$ too!

Another thing: I've compared the 20748 SYS folder with the 20755 SYS folder and saw the the 20755 folder hasn't some files while the 20748 has. Is this problematical?

- Files included in build 20755, NOT in build 20748:
SYS\.Rom\.Rom
SYS\ipsecvpn\ipsecvpnui.cpl\ipsecvpnui.cpl
SYS\OS\gsm610.acm\gsm610.acm
SYS\Redist\cplmain.cpl\cplmain.cpl
- Files included in build 20748, NOT in build 20755:

SYS\OS\dw.exe\dw.exe
SYS\OS\dwui.dll\dwui.dll
SYS\OS\dwxfer.dll\dwxfer.dll

Edit: I mean, what functions have these files?

[utopykzebulon]

someone can explain me why i have this error when i cook!!!

Microsoft (R) RGUComp Version 1.0.000
Registry file processor and hive builder.
Copyright (C) 2004 Microsoft Corporation All Rights Reserved.
built: Nov 19 2004 15:17:13
importing registry file ".\boot.rgu"...
wmain: (RGUComp) !ERROR failed building DEFAULT hives
Creating registry Error...

i don't understand and i've tryed a lot of things!!!

[KMFM$]

someone can explain me why i have this error when i cook!!!

Microsoft (R) RGUComp Version 1.0.000
Registry file processor and hive builder.
Copyright (C) 2004 Microsoft Corporation All Rights Reserved.
built: Nov 19 2004 15:17:13
importing registry file ".\boot.rgu"...
wmain: (RGUComp) !ERROR failed building DEFAULT hives
Creating registry Error...

i don't understand and i've tryed a lot of things!!!

Did you manually edit the file "boot.rgu"?

[utopykzebulon]

Did you manually edit the file "boot.rgu"?

no, i've dumped it from a zip looklike this share but i'va tryed a lot of boot.rgu

[KMFM$]

Which files did you download? Also, what packages are you trying to cook in?

[utopykzebulon]

Which files did you download? Also, what packages are you trying to cook in?

Thank for help but i've solved my pb!!!it come from windows..... :confused:

[KMFM$]

Thank for help but i've solved my pb!!!it come from windows..... :confused:

Well, we're glad you got it figured out. :D

[b16b]

wrong :cool:

file icongames.lnk u have to create the file
its like txt file just create icongames.txt and then rename it to icongames.lnk
inside the file just 1 lane
29#"\Windows\blackset.dll,-3 "

this file put into rom somewhere
and then initflashfiles.dat

Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\icongames.lnk") will create in games file icon.lnk from file icongames.lnk

but thats basic programming m8

just type in command prompt

echo 29#"\Windows\blackset.dll,-3 " > icongames.lnkthis will create the file for you then put the file in you rom :cool:


-- the number 29 i dont know what is it for might be some priority thread number but really dont bother

i try this settings but nothing happen all try again one mote time.. :(

[KMFM$]

b16b, how are you editing the initflashfiles.dat file? If you are using a basic text editor (i.e.-notepad), you will need to use a hex editor to remove the FE FF at the beginning of the file. (If you need a hex editor, google XVI32)
In the initflashfiles.dat file add the line:
Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\icongames.lnk")Save initflashfiles.dat and then hex edit the file as I stated above.
Now, on your desktop computer open a command line and type in the following:
echo 1#blackset.dll,-3 > icongames.lnkNow, look in the directory that is the command line home (i.e.-"C:\Documents and Settings\<Username>") and then copy the "icongames.lnk" file from that directory to a directory in your ROM Kitchen (I normally place the files in SYS\OS). Now cook your ROM. After you flash go to Start > Programs and look at the Games folder. It should show the icon that you specified in the blackset.dll.
Hopefully, this is a little more specific. :D

[b16b]

b16b, how are you editing the initflashfiles.dat file? If you are using a basic text editor (i.e.-notepad), you will need to use a hex editor to remove the FE FF at the beginning of the file. (If you need a hex editor, google XVI32)
In the initflashfiles.dat file add the line:
Directory("\Windows\Start Menu\Programs\Games"):-File("icon.lnk","\Windows\icongames.lnk")Save initflashfiles.dat and then hex edit the file as I stated above.
Now, on your desktop computer open a command line and type in the following:
echo 1#blackset.dll,-3 > icongames.lnkNow, look in the directory that is the command line home (i.e.-"C:\Documents and Settings\<Username>") and then copy the "icongames.lnk" file from that directory to a directory in your ROM Kitchen (I normally place the files in SYS\OS). Now cook your ROM. After you flash go to Start > Programs and look at the Games folder. It should show the icon that you specified in the blackset.dll.
Hopefully, this is a little more specific. :D


with this way
echo 1#blackset.dll,-3 > icongames.lnk
i can create .lnk say i don't have access

[aruppenthal]

First Thanks for your contribution to the community.

OK ive been looking at your kitchen. My question is can any OEM folder be subbed provided I keep the OEMxipkernel in the OEM folder? I have a OEM folder that is completely customized already from my previous rom series that I would like to use.