Rom Cooking Related Question: Bugs and Problems

[kin0kin]

I'm facing a rather tricky problem.

Adobe Flash LE has a file called searchtext.bmp, same goes for the taskmanager that i'm using....BuildOS says there is redundant files (already exists)...what can I do to avoid this conflict?

Same thing happened to audio manager and audio booster. I first installed audio manager, then I installed audio booster. They happen to be using the same file name for some apps, and as a result, audio manager's skin was messed up because audio booster's skin file overwritten it :(

[allan1]

cook one in and use a cab for the other!

[kazuni]

one thing you can do, is that you cook the bitmap file as a different name, say, package A has a file called myfile.bmp, and package B as well. what you need to do is cook the file in B as myfile_.bmp and an initflashfiles.txt with the entry such as:

Directory("\Program Files\ProgramB"):-File("myfile.bmp","\windows\myfile_.bmp")

that should work.

** this means that, program A and B would be in \program files\ instead of \windows\.

[kin0kin]

cook one in and use a cab for the other!

Allan, that will not work as I mentioned in my thread that it will overwrite the file with the same name.

@kazuni
That sounds like a plan, seperating them into different folders. I'm gonna try and see if it works :D

[kin0kin]

Another questions I have is about same DLL. For example, Comm manager uses a dll called phcanOverbmp.dll. I noticed that the "White battery Icon" fix also uses the same DLL, but they are of different size with Comm manager's version @ 500+kb, while the battery fix version @ at smaller size.

Which DLL should I keep?

Can I keep the one that is larger and apply the registry settings found in the battery fix?

[kazuni]

Another questions I have is about same DLL. For example, Comm manager uses a dll called phcanOverbmp.dll. I noticed that the "White battery Icon" fix also uses the same DLL, but they are of different size with Comm manager's version @ 500+kb, while the battery fix version @ at smaller size.

Which DLL should I keep?

Can I keep the one that is larger and apply the registry settings found in the battery fix?

as long as your program isnt hard coded to use \windows\phcanOverbmp.dll then you can make the OEM package for Comm Manager to reside in another folder and use its own phcnaOverbmp.dll

if not, then you will have to try and see if you do not apply the battery fix at rom cooking, then manually copy the file over into your pda after bootup, and see. that way, you are trying both original commanager and batteryfix's phcanOverbmp.dll and see if they can coexist.

remember, you cannot use file explorer to copy over a file that already existed in rom from another location. you would have to copy it as a different name, and then put it inside \windows\ and then rename the file as the original file name.

see if that helps?

[kin0kin]

actually, I don't think I even need to replace the phcanOverbmp.dll :p
the "fix" pretty much just sets the parameter "BatteryIconIdStart" to integer: 1001

Looking at the fix in Schap's thread, the Integer was set to 1000....does anybody know what difference does it make? :confused:

[mattk_r]

The .bmp in the taskmanager isn't needed.

The phcanoverbmp in the comm manager is a stock version. Remove it from the package if your going to install a custom one from somewhere else. The larger one probably has Schaps battery indicator.

Typically, duplicate files are caused from re-introducting a file that isn't needed - typically from to packages that were compiled and one inadvertently getting an unnecessary file.

You're on the right track with asking what the difference is, but sometimes I'll grab a cab for the package I'm trying to install and compare the files. In many cases, that's solved the mystery. :)

Another suggestion is if you're customizing your own kitchen, you might put everything into the OEMApps folder. Thay way you're not adding additional .dsm/.rgu files into your rom unnecessarily. Just copy the files over and paste the .rgu contents (following the guildelines for doing so) to the OEMApps folder .rgu.

[kin0kin]

Matt,

Actually most of the time I'd take the cab, decommission it, and compare it to some of the premade packages to see what the differences are, then i'd use my own discretion to recreate my own package.

Another suggestion is if you're customizing your own kitchen, you might put everything into the OEMApps folder. Thay way you're not adding additional .dsm/.rgu files into your rom unnecessarily. Just copy the files over and paste the .rgu contents
You mean I could just go into the packages, take out all the content and copy them into OEMApps, along with the respective .rgu?

What happens to the initflashfiles.txt then? Do I combine all the initflashfiles into one big initflashfiles for all the apps and put it in there as well?

And the benefit of doing this is saving some spaces from the all the .dsm files?

[kazuni]

yeah, you would also need to put in the appropriate entries for the initflashfiles.txt

one little advice, i have had a lot of problem with his is that,
option.xml is in UTF format;
initflashfiles.txt is in UTF format;
anything.rgu is in UTF format as well;

but shortcuts are all in ANSI stardard format.

have fun :D

[kin0kin]

lol, yeah most of them are in unicode. When I just started getting into cooking, I wasn't even sure if .dsm is suppose to be in unicode or ansi since most of the guides only say to create rgu in unicode, none said anything about whether dsm should also be in unicode or ansi. But anyway, for those who are looking for the answer, .dsm is in ansi

Problem #1
I've still got a few tiny bugs I need to fix for my rom. When I create the "accessories" and "system tools" folder with the line:


Directory("\Windows\Start Menu\Programs"):-Directory("Accessories")
Directory("\Windows\Start Menu\Programs\Accessories"):-File("W5torage.lnk","\Windows\W5torage.lnk")


The first line should create the folder for accessories. However, the folder that it created is just the generic folder.

How can I get windows to create the accessories folder like the one in the picture below?
http://i13.photobucket.com/albums/a288/kin0kin3/icon.gif

Should I be be using the code:
Directory("\Windows\Start Menu\Programs"):-PermDir("Accessories")

?? :confused:

Same goes for the system folder.


Problem #2
Another thing I'm having problem with is getting autoconfig to run. I've created the following:

Folder name: Preconfig

With the following content:
-preautorun.exe
-preautorun.lnk
-HTC_Default.tsk
-Preconfig.txt

LOCK:Enabled
EXEC:\Windows\SetHSDPA.exe /Enable
EXEC:\Windows\cusTSK.exe \Windows\HTC_Default.tsk
LOCK:Disabled
RST: Reset

I then created a dsm file and populated it with buildDSM. I toss it into the OEM folder and ran buildOS....it didn't work :( Am I missing something?

BTW, kazuni & matt, thanks for helping me out, you guys have been really helpful :D

Edit: Problem two solution
I'm an idiot, it's missing the provxml

Question
What is the App_Service.dll for? I was examining the pandora kitchen's OEM package for Pre-settings and in both ATT preconfig were the App_Service.dll, but it wasnt there in the Orange_UK's presettings..

[kazuni]

lol, yeah most of them are in unicode. When I just started getting into cooking, I wasn't even sure if .dsm is suppose to be in unicode or ansi since most of the guides only say to create rgu in unicode, none said anything about whether dsm should also be in unicode or ansi. But anyway, for those who are looking for the answer, .dsm is in ansi

Problem #1
I've still got a few tiny bugs I need to fix for my rom. When I create the "accessories" and "system tools" folder with the line:


Directory("\Windows\Start Menu\Programs"):-Directory("Accessories")
Directory("\Windows\Start Menu\Programs\Accessories"):-File("W5torage.lnk","\Windows\W5torage.lnk")


The first line should create the folder for accessories. However, the folder that it created is just the generic folder.

How can I get windows to create the accessories folder like the one in the picture below?
http://i13.photobucket.com/albums/a288/kin0kin3/icon.gif

Should I be be using the code:
Directory("\Windows\Start Menu\Programs"):-PermDir("Accessories")

?? :confused:

Same goes for the system folder.


Problem #2
Another thing I'm having problem with is getting autoconfig to run. I've created the following:

Folder name: Preconfig

With the following content:
-preautorun.exe
-preautorun.lnk
-HTC_Default.tsk
-Preconfig.txt

LOCK:Enabled
EXEC:\Windows\SetHSDPA.exe /Enable
EXEC:\Windows\cusTSK.exe \Windows\HTC_Default.tsk
LOCK:Disabled
RST: Reset

I then created a dsm file and populated it with buildDSM. I toss it into the OEM folder and ran buildOS....it didn't work :( Am I missing something?

BTW, kazuni & matt, thanks for helping me out, you guys have been really helpful :D

Edit: Problem two solution
I'm an idiot, it's missing the provxml

Question
What is the App_Service.dll for? I was examining the pandora kitchen's OEM package for Pre-settings and in both ATT preconfig were the App_Service.dll, but it wasnt there in the Orange_UK's presettings..

The only way you can make them is specifying an icon file. if you take a look and unhide the folder there, there is an icon.ico or a dll there.

[kin0kin]

Actually, I found the solution after looking at the initflashfiles.dat from another rom which has the folders and here's what I found:

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

Directory("\Windows\Start Menu\Programs"):-Directory("System Tools")
Directory("\Windows\Start Menu\Programs\System Tools"):-File("icon.lnk","\Windows\systemtoolsico.lnk")
That's one less problem! :D

New Problem
One other odd problem I'm having is with the theme. For some reasons windows wont apply the theme properly for the first time with my rom, the theme is only partially applied with some "leftovers" from the windows default theme...like some parts being blue and etc. Sometimes I need to reapply the theme several times to get it applied properly. Does anybody know what's causing the problem. I've had the same problem last time and somehow it just disappeared in one of my test roms but it is now back. :mad: