Database Info

[Release] EasyPortOven V2 [Updated May 07, 2008] Now with XIP porting!!

This is a release for my ROM porting kitchen. It ports both XIP's and SYS folders [currently for the herald/atlas/wing only].
http://www.darthnet40.com/xda/ivanmmj/Kitchens/
Place bepe's kitchen in the Working_Folder (so that OEM/SYS/ROM and other folders are right within Working_Folder.) Alternatively, you can place also place all the files into EasyBakeOven's folder. Allow the Working_Folder to override EasyBakeOven's Working_Folder. You will not loose any data.
Place the SYS file you wish to port into Working_Folder (and delete your old SYS folder.) Place your xip.bin that you wish to port into the Prepare folder.
Obligatory Warning Label:
Use this at your own RISK. I cannot be held liable for any damage caused to your device by your own mistakes or by my mistakes in the instructions.
If you wish to know how to do this manually, head over to my HowTo thread.

thanks ivan

Could you please post a basic tutorial how to use this? I'm a bit confused. TY

Well, for now, since it's not a final release, just put the SYS folder from a ROM you want to port over into the Working_Folder and then run the batch file. Then take your favorite ROM (like JustClean) and delete the SYS folder that it came with. Then add the SYS you just ported over. Then just use my kitchen the way you would normally use it.
I'll try to write something more useful, or maybe automated the whole process more later, but for now, I don't have the time to. I hope my "tutorial" is useful, though!

Sry for being a bit stupid, but what is this supposed to port into what? It updates ROMs from ypur old EasyBakeOven?

CommZ said:
Sry for being a bit stupid, but what is this supposed to port into what? It updates ROMs from ypur old EasyBakeOven?
Click to expand...
Click to collapse
it is for porting for example a Kaiser SYS to a hreald SYS for cooking!!
to get a newer build.... the kaiser ones are allways earlier than all other devices...

Aah, so it is not much useful for me as I am barely able to use ivan's easy kitchen. Thanks

not working for me.... get an error... I/O error
g´reloc stop working
sorry...

papamopps said:
not working for me.... get an error... I/O error
g´reloc stop working
sorry...
Click to expand...
Click to collapse
That's strange.... Make sure that your SYS folder does not have a XIP folder in it or anything similar. If that doesn't work, try to run it WITHOUT the OEM.

ivanmmj said:
That's strange.... Make sure that your SYS folder does not have a XIP folder in it or anything similar. If that doesn't work, try to run it WITHOUT the OEM.
Click to expand...
Click to collapse
i run both with and without oem... and sys only has sys files. no xip!

papamopps said:
i run both with and without oem... and sys only has sys files. no xip!
Click to expand...
Click to collapse
One of the SYS folders that I found had a XIP something folder. (It wasn't called XIP, but it had files that the XIP had and it had XIP in its name.) This caused it to crash.

ivanmmj said:
One of the SYS folders that I found had a XIP something folder. (It wasn't called XIP, but it had files that the XIP had and it had XIP in its name.) This caused it to crash.
Click to expand...
Click to collapse
sorry. but my sys is completely similar to the one i use for herald. BUT i have to change some files to get it working fro herald.
i did manually with the wince_
and the shellres.dll and the other
the ones you have in your portkitchen. then treid to cook... all good BUT stuck at blackscreen after 2nd bootscreen!

papamopps said:
sorry. but my sys is completely similar to the one i use for herald. BUT i have to change some files to get it working fro herald.
i did manually with the wince_
and the shellres.dll and the other
the ones you have in your portkitchen. then treid to cook... all good BUT stuck at blackscreen after 2nd bootscreen!
Click to expand...
Click to collapse
so i should replace the shellres.dll and WinCENLS?

hmm... I thought I did that on the kitchen. It's very possible that I didn't upload the proper files, though...

Update. I updated it, now it even has XIP porting! Look for the walkthrough link for those who want to know how to do it by hand.

ivanmmj said:
Update. I updated it, now it even has XIP porting! Look for the walkthrough link for those who want to know how to do it by hand.
Click to expand...
Click to collapse
thanks!
ill use the nice and very easy walkthrough

Can you added support for htc wizard?

This is ancient. I haven't worked on this for ages. You no longer need this to port. There are much easier methods out there. Remind me again and I'll research it later.

By any chance, are you putting up .07 SJK with 28005/8 tonight. I kinda would like to reference what I did with your kitchen with what you are gonna do with yours.

Yes, I am. I'm actually in the mist of uploading it right now.

Can anyone help me to debug my first rom

Hey guys,
I am working on my first rom. After going through many readings from other sub-forum (hermes and kaiser) as well as Ivan's cooking class, I made my first rom using the Wing stock rom. After deleting un-used packages and files, I can sucessfully build the os.nb and converted it to .nbh file. But when I tried to flash it back to the wing, I got a error saying my RUU cannot used to flash the device, but I have been using this same RUU for many roms. I attached the screenshot, please take a look and help me debug it. It's my first rom Many thanks

go and try when you buld .nbh to set device "herald" but in section "version" write "test" not the numbers that are there by default.....
hope that helps.

Yep, looks like you didn't set it to Herald when you built it.

Thanks. You guys are right. I can flash my rom now. However, it stuck in the primary splash and does not response to the stylus. Any idea how to fix? Again, really appriciate any help.

live4nothing said:
Thanks. You guys are right. I can flash my rom now. However, it stuck in the primary splash and does not response to the stylus. Any idea how to fix? Again, really appriciate any help.
Click to expand...
Click to collapse
This is part of the fun of being a cook, figuring out what mistakes we made.
There could have been 1 million different things you could have done that made it not boot up. It could have been something you removed or something you added. What kitchen are you cooking with? (It could also be that you didn't relocate all the modules if you're using something like hypercore.)

ivanmmj said:
This is part of the fun of being a cook, figuring out what mistakes we made.
There could have been 1 million different things you could have done that made it not boot up. It could have been something you removed or something you added. What kitchen are you cooking with? (It could also be that you didn't relocate all the modules if you're using something like hypercore.)
Click to expand...
Click to collapse
I am using hypercore. Can you point me to a reference to use hypercore or maybe an better kitchen for new cooks?

Either use G'Reloc for hypercore, or use Bepe's Extended Kitchen for the Herald. The latter option would be the best.

After re-doing the delete packages part, I got the rom flashed into my wing, booted, but nothing working. I mean windows started, top and bottom bars also loaded, but radio not working, nothing reponses. One thing, the screen seem to flicker a little bit. I notice the boot speed is super fast (really really fast) as in none of the hardware drivers is initialized at all. I am clueless as of this point. Any more help?
@Ivan:
Thanks man. Since I started with hypercore and kind of familiar with it already, I would like to stick with it. Can you show me how to use G'Reloc? Thanks

Just drop the file into your build folder and run it. (Assuming you're using a SYS folder that belongs to your phone.) Bepe's kitchen is great because it does a lot of fixing up for you automatically. It's not a competitor's kitchen, it's a MUCH newer kitchen. I use both. I use Hypercore to take Herald ROMs appart and for different tools in it and Bepe's kitchen to put my ROMs together (and a kaiser kitchen to take appart kaiser, diamond and other ROMs) and I also use my own kitchens which are mostly based out of Bepe's kitchens.
The whole boot speed and nothing working means that you deleted things packages you shouldn't have.

I run G'Reloc, but it ask for slot 1, slot 2, ... Do you mind explain them to me? I tried to just click "do it" with the default values, and it showed that it relocated 265 out of 368. I built the rom and flashed it to my wing, but it stuck in the boot splash now. Thank for the help

Those are taken from a folder in your SYS folder. It sounds to me like you deleted a lot of packages that are essential to WM6/6.1. You can't delete everything that SOUNDS like you don't use. Also, the SYS folder HAS to be from a Herald UNLESS you ported it. If you didn't port it, then the values on slot 1 and slot 2 will be wrong.

I followed your guide to take the SYS from the Kaiser's rom. Here's what I did. I run buildOS.exe, then I run G'reloc, then I run createROM.bat. Did I do it right?

live4nothing said:
I followed your guide to take the SYS from the Kaiser's rom. Here's what I did. I run buildOS.exe, then I run G'reloc, then I run createROM.bat. Did I do it right?
Click to expand...
Click to collapse
Which guide? My guide? You run G'Reloc first and THEN buildOS, or else you're building the OS BEFORE fixing the files that you need to BUILD the OS.

The sequence part, I guess on my own. I meant I follow your guide on porting the SYS and XIP on lesson 4 and 5. I did not even try G'Reloc in the first place because I did not know I have to do it. Btw, thank again man, you're such a big help to me.

The reason why the guide was failing and I hadn't mentioned G'Reloc in the walkthrough is because the walkthrough was made for Bepe's Extended Kitchen. No problem with the help. I remember when I was learning, no one answered, so I figured I'd give something back.

working with OEM
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.

live4nothing said:
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
Click to expand...
Click to collapse
This is great news, we have a new herald cook on the way.
I'm very glad to see this since I will be not be cooking any more after my current release is done.
Keep it up bro,

live4nothing said:
Hey Ivan,
thank to your help, I was be able to cook some roms with the newer SYS and XIP build. During the process, just to learn how to port SYS and XIP, I borrowed your OEM folder (I copied the whole OEM folder form your JustMine kitchen). Now I learned how to port SYS and XIP and get them working, I want to play with my own OEM. Otherwise, I would not be cooking if I copied your OEM. Here what I did:
1) Since I can't find any base OEM folder for herald or wing here, I used hypercore to extract the OEM from the official stock Wing stock rom.
2) I copied the whole OEM without deleting junks (because it failed when I deleted stuffs before. So I want to ensure that I got the OEm working before start deleting stuffs) to bepe kitchen
3) build the rom
Here's what happen:
When i used the stock OEM, my wing can boot into WM, but it skip the screen align, setting timezone and setting password section. AFter that, it say my pout.exe (or something like that) and repllog.exe is currupted. The green light indicating the radio is blinking, but the radio doesn't pick up anytihing, said no service.
If I replace your OEM, everything works fine. So I test my OEM by building it with the stock SYS and XIP, it also works fine. Did I missed anything? Thanks for all your help, man.
Click to expand...
Click to collapse
Your missing the SQM package (or at the very least the patched file that you use to bypass it.) http://forum.xda-developers.com/showthread.php?t=393997

ivanmmj said:
Your missing the SQM package (or at the very least the patched file that you use to bypass it.) http://forum.xda-developers.com/showthread.php?t=393997
Click to expand...
Click to collapse
Dude Ivan, you are awsome. I sucessfully created a ROM using my ported SYS, XIP and my own OEM. Again, thank you very much for guiding me through the whole process. I am thinking release it as a lite rom so everyone here can enjoy the newest build if they wish to. Before I can do it, I want to do some tweaks to it. So can you so me how to cook registry entries into the ROM? Thanks

live4nothing said:
Dude Ivan, you are awsome. I sucessfully created a ROM using my ported SYS, XIP and my own OEM. Again, thank you very much for guiding me through the whole process. I am thinking release it as a lite rom so everyone here can enjoy the newest build if they wish to. Before I can do it, I want to do some tweaks to it. So can you so me how to cook registry entries into the ROM? Thanks
Click to expand...
Click to collapse
You've got two options. RGU's and PROVXML's. You're better off setting up a package with an RGU that has all your registry keys. RGU's are nothing more than reg files. ^_^ And I'm glad it worked.

Porting the newest XIP

Hi folks,
After messing around for a while, I finally created my own ROM and sucessfully flashed to my wing. It all works, but it has out dated build. I am using Ivan's guide and Hypercore to cook my room. Here my question. In hypercore, when I extracted the XIP, all the files in the XIP folder are binary. However, from the Hermes forum, they posted the base SYS and XIP for the newest build, but they are in package format. Can I use this new SYS and XIP in Hypercore? If so, how? Thanks

As long as you port the XIP and SYS as per my XIP porting guide, then yes. But you can't port the XIP using Hypercore alone. You'd have to use Bepe's extended kitchen. This kitchen will automatically fix the memory addressing for you. The memory addressing of the the SYS you can easily fix by running G'Reloc after following my walkthrough for XIP porting.

Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.

live4nothing said:
Hi,
Here's what I did:
port xip and sys using ivan's guide
replace sys and xip into bepe's kitchen
replace my oem folder (mine is from the stock rom, not sure if it works with 6.1, so I borrow ivan's justclean oem)
build the rom
After the flash, it stuck in the second splash screen, the blinking light for radio is blinking. There is also a "beep" sound right after it passed the first splash and entering the second splash. Then it stopped here. What's wrong with my procedure? Is this symptom indicate the xip or the sys part gone wrong? Any help is appriciated.
Click to expand...
Click to collapse
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)

ivanmmj said:
That's because the SYS and the OEM folders were G'Reloc'ed sperately. In other words, place both Bepe's kitchen. Or just drop and run G'Reloc into your Build folder in Hypercore and run it before you start cooking. (You have modules coming from different places. You have to adjust the memory addresses to not conflict with each other.)
Click to expand...
Click to collapse
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.

live4nothing said:
Sorry, I did not type it correctly. I actually ran g'reloc after I put both both SYS and XIP in bepe's kitchen. One thing is that in the status bar of g'reloc, it show total of 488 modules and relocated 288 modules. Is this bad? If so how do I fix it? Here what I did to port the XIP and SYS:
1) use masterrom from hypercore to extract xip.bin from the newest pdaviet rom (the 20753 build)
2) use bepe's xipport to dump and create packages as your guide showed
3) copy and replace the folders inside MSXIPKernel and MSXIPKernelLTK from Files and Modules into Bepe's kitchen's old XIP
4) get the new SYS from hermes' forum, replace with my old .vm, wincenls_wwe, shell/shell32 shell/shellres
5) replace the old SYS folder with my new ported SYS folder
6) borrow OEM folder from your justclean kitchen
7) run g'reloc
8) run buildOS and try to delete duplicate files (I kept the ones from SYS, deleted the ones in OEM)
9) build new new nbh from nb and flash
what did I do wrong? my goal is to have the most update build and software. I tried pdaviet's 20753 build, it is incredibly fast. Thanks for your help
Another question, would is be bad or could anything bad happen to my wing if I flashed it too much? I flashed to test my rom more than 20 times this week.
Click to expand...
Click to collapse
I tired that build as well and it had issues, thats why I went with 20748 instead.
Also, if you compare the size of the sys folder for build 20753 and another version, you will know why it's faster.
Just and FYI,

Good tips. Also, you have to build the ROM from within Bepe's kitchen. That way, it runs G'reloc on the XIP as well. Or, run the G'reloc with the following AFTER running BuildOS but before actually building the ROM. "G'Reloc.exe -doit -dump"

Ivan and Tony, Thanks. One will try the 20748 build later this week if I have time. However, I have one more question. I look around the forum, I saw there are two type of xip like this:
XIP: (bigstorage)
20753_XIP 09/19/2008
20755-XIP 09/23/2008
To Make XIP/ROM Non-BigStorage or Real BigStorage:
Copy this over existing rom folder
What the different between bigstorage and non-bigstorage or real bigstorage? Which one should I use for our wing/herald? Again thanks for your your help.

Those bigstorage do not apply to our ROM's. Our devices do not store data in the same way as BigStorage compatible ROMs. Our BigStorage comes from stripping the extra crap out of our ROMs.

Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.

live4nothing said:
Could this be the reason I could never got my rom working. I first used there sys and xip. Can I use their SYS? Since we cann't recook already cooked rom and I can't find any new base rom in our forum.
Click to expand...
Click to collapse
You can use any SYS and XIP that isn't a ROM that has been made with certain kitchens... The issue is that you have to G'reloc the OEM, SYS and XIP within the same kitchen while they're in the same directory. G'reloc will only relocate the modules it sees and if it relocates them seperately, it might set the modules to the same memory address as the other G'reloc did with the OEM package.

A question for the cookers

Say I downloaded "frauhottelmann"'s GUI kitchen and I grabbed the original, unmodified S740 SYS and OEM folders from a thread here.
What would I need to replace in order to build a ROM that will bootup on an Excalibur ? I have the "dump" of the original 6.1 ROM from the Excalibur. Some drivers maybe ? Any help ? Thanks

Oh, so you got it already. You should start with the OEM folder of the Excalibur. Then you might have to add some of the *.cpl.xml from OEMMISC to get all settings to work. The new packages are a bit trickier to use. You need more files from the new OEM. And don't use the new Connection Setup, it doesn't work. You should be able to use the whole SYS folder though.

This is going to be difficult then. The only kitchen that exists for the Excalibur, dumps the contents of the ROM in one folder and doesn't seperate the foldes out to OEM, SYS, etc...
So is the SYS folder where all the drivers are then ?

No. There are two main folder. SYS is for the general Windows Mobile OS part. OEM is what the manufacturer or you add. The folder for drivers is on OEM and is called OEMDrivers. If you have a dump, you can make "packages" with PKGTools. There is no official 6.1 ROM right? So I guess this will be a problem, because then it doesn't sort the packages right. You'll have to try. Maybe send me a screen shot of the files or the result!

Well the original 6.1 ROM for the Excalibur (the ONLY one) was made by this guy Kavana. I'm pretty sure it was based on the files from the MS emulator and drivers from the OEM WM6. IS PkgTools included in your kitchen ? Should I try to dissassemble the ROM with your kitchen ?

yes pkgtools included.
give it a try and post if it worked!
good luck mate... i saw your prog for the weather! really nice!!
htc sliding plugin also rocks! anyway keep it up!

Well I managed to make an excalibur ROM that works (partially) with the VOX GUI kitchen, and replacing the OEMDrivers with the drivers from my official WM6 ROM. Problem is, the center button on the keypad doesn't work. Everything else is fine... although WI-FI and BT don't turn on. Any ideas what I'm doing wrong ? Oh and the startup screen is all skewed and in 4 pieces, right after the splash screen, bu before the usual winmo 6.1 splash screen.

Well I'm over that road bump now, and I'm trying to port the S740 XIP and SYS over to take advantage of the new CHOME
So far, so good...

Thanks guys for the support. I was able to make a new ROM based on the 20279 core from the S740 ALL by myself. Reading these forums for a few days is what did the trick... heh. THe ROM runs great and I have to say that BuildOS+package tools is my best ROM cooking friend right now...

NRGZ28 said:
Well the original 6.1 ROM for the Excalibur (the ONLY one) was made by this guy Kavana. I'm pretty sure it was based on the files from the MS emulator and drivers from the OEM WM6. IS PkgTools included in your kitchen ? Should I try to dissassemble the ROM with your kitchen ?
Click to expand...
Click to collapse
There is no rgu file in the rom you dumped.
and the one is not official 6.1.
You can dump the
moto q8 WM6.1 rom
s740 official rom
C810 official rom for your resource.

I know.. that was my original problem. No worries though, as I used the SYS folder from the S740 and all is well now

Porting SYS section (from 6.1 to 6.1)

Hello.
I have a problem with SYS porting. I have ported XIP and it work (tested with ather 6.1). And now I want to port SYS. Every tutorials says me to copy .VM from old SYS into NEW, then reloc and then build rom. So I did that and phone does not boot. I searched a lot of forums, topics and boards, and I didnt find any solution to my problem.
My phone is Himalaya.
What I do after flashing : I press camera+recors+reset buttons (hard reset) and choose no yes yes (disable kitl, format registry and storage), then I click D-PAD, and wait. After few seconds phone turns on backlight, and after next few seconds (longer) phone disables backlight. Nothing more.
With normal boot it should enable backlight and afther 2-3 seconds it should display welcome screen from rom (welcomehead.96).
What should I do to make my SYS work?

It depends on the kitchen, but I normally copy .VM, .ROM and Metadata over to a new SYS.

I moved .ROM, .VM, and after your suggestion I also moved metadata, and nothing changed.
What should I do now?

Do you get the Ani_on.gif to show? If not, it's probably a XIP issue then. Build builds are you porting from/to? Does your old XIP work with the new ported sys? Are you using 0409 lang, or some other lang?

I got full working rom with my new xip and old sys and oem.
At my sys, I can't see welcomehead.96, it is just white screen.
My device is himalaya, I don't remember old build but new is 21054.
I also tried this :
I got working SYS and OEM (from ather's rom) and copied OS and OSFiles to this, now rom hangs at welcomehead.96.
Also i tried this:
Got not working SYS and OEM (from 21054) and copied OS, OSFiles and Shell into this, and rom hangs at white screen.
I also tried to relocate rom whit address from ather's rom, nothing changed.
I ported xip by method : MSXIPKernel from new build, and other files from old.
Also i tried to moving WINCENLS (blabbla) to SYS, without it phone does not turn on backlight!!
Also i have enough space to place wince.nls into xip, i tried it and nothing changes (as in sys).
I use 409 (wwe) only. (no space in rom for other langs)
It is really weird...
What should I do now?