Custom VGA OEM Requests ....Get them here! Updated 6/13/2009

[madcook]

i dont know what im doing wrong but i cant seem to make a phm editor or pocket rar oem well i was tring to to make two oems one of each .i have made an opera but no luck on this two what do you differant to make this work btw i did find them in oem from but i still want know

[rstoyguy]

Originally Posted by salisburyl

i dont know what im doing wrong but i cant seem to make a phm editor or pocket rar oem well i was tring to to make two oems one of each .i have made an opera but no luck on this two what do you differant to make this work btw i did find them in oem from but i still want know

Say you have two OEM's, utils1 and utils2...
Take the utils2 OEM and copy the files from it into the utils1, EXCEPT the following files:
*.DSM
*.RGU
initflashfiles.txt
options.xml

Then you take the contents of the utils2 RGU and cut and paste the contents into the utils1 RGU keeping the original content. Then do the same with the initflashfiles.txt file, copy the contents from utils2 OEM and paste it into utils1 OEM keeping the original contents in both. Now edit the description inside the utils1 OEM and delete the utils2 OEM. You've made your first mega-pack! Your gathering a good set of skills senior! Keep it up!

And in the RGU, be sure to keep the two blanks lines at the bottom to keep buildos happy!

[Trident]

Can we get an OEM for this KB?

[jtvgeo]

Originally Posted by Trident

Can we get an OEM for this KB?

here u go

[Trident]

Originally Posted by rstoyguy

Convience is good! And here is my version. I started using the provxml for this particular one when the RGU contents wouldn't override a registry edit in the phone canvas OEM in some kitchens. May require a soft reset as I think the battery icons are loaded before the provxml is run. And a new set...I've already switched back to 6.1...grrrr.

When I just used this in the new grooveKitchen it threw up an error about there being a duplicate of BTDiscoverable.bmp-- any idea where this is also hiding so I can delete it instead of this taskbar?

I found where I messed up. But now, with the ROM flashed, I get no custom icons at all. Something ain't right here.

I can't seem to get the OEM to work and I don't really understand inda's instructions regarding replacing the OEM & SYS files or deleting them after dropping them in OEMDrivers. HOw do I find all of them to delete/replace them?

I think it's time for bed...
I got pretty far, but am stuck on this error. notify.dll.0409.mui is a directory and not a file or some such thing. (see capture)
I found the file/folder in the taskbar OEM and in a SYS folder as well, but don't know if I should delete one of them or do something else.

[rstoyguy]

Originally Posted by Trident

I think it's time for bed...
I got pretty far, but am stuck on this error. notify.dll.0409.mui is a directory and not a file or some such thing. (see capture)
I found the file/folder in the taskbar OEM and in a SYS folder as well, but don't know if I should delete one of them or do something else.

The file is located in ..\SYS\Base_Lang_0409, and you'll want to navigate to that directory and delete the "directory-looking" file and it's contents. Then you can drop that in whereever you want, I've got a seperate OEM for the taskbar.

[pixelwix]

anyone have the latest tf3d oem with altel brown skin that i can use on a 6.5 rom? all the once i've tried don't start tf3d or make the rom crash!!!, please help me out i'm using juiceys kitchen and i don't really care for tf3d2...

[indagroove]

Originally Posted by Trident

When I just used this in the new grooveKitchen it threw up an error about there being a duplicate of BTDiscoverable.bmp-- any idea where this is also hiding so I can delete it instead of this taskbar?

I found where I messed up. But now, with the ROM flashed, I get no custom icons at all. Something ain't right here.

I can't seem to get the OEM to work and I don't really understand inda's instructions regarding replacing the OEM & SYS files or deleting them after dropping them in OEMDrivers. HOw do I find all of them to delete/replace them?

I think it's time for bed...
I got pretty far, but am stuck on this error. notify.dll.0409.mui is a directory and not a file or some such thing. (see capture)
I found the file/folder in the taskbar OEM and in a SYS folder as well, but don't know if I should delete one of them or do something else.

When you add oems, and get errors during BuildOS, that usually means that you have duplicate files. You can't have more than one of any given specific file name. Therefore, you just need to use your PC's simple search tool to search you kitchen and/or sys/oem folders.

In this case of directory and not a file, that usually means that you have duplicates, and one is a dll file, and one is a dll module (looks like a folder with a few files inside of it).

Some taskbar dlls are in oem, and some in sys by default, so you gotta check both locations.

[Trident]

Originally Posted by indagroove

When you add oems, and get errors during BuildOS, that usually means that you have duplicate files. You can't have more than one of any given specific file name. Therefore, you just need to use your PC's simple search tool to search you kitchen and/or sys/oem folders.

In this case of directory and not a file, that usually means that you have duplicates, and one is a dll file, and one is a dll module (looks like a folder with a few files inside of it).

Some taskbar dlls are in oem, and some in sys by default, so you gotta check both locations.

I was trying this way too late/early. I figured out exactly what you said to do and it worked perfectly the next day.

The way I understand it, I could have used the rar you posted and done the same thing manually, correct? Just search for each file and replace it with the new ones?

[indagroove]

Originally Posted by Trident

I was trying this way too late/early. I figured out exactly what you said to do and it worked perfectly the next day.

The way I understand it, I could have used the rar you posted and done the same thing manually, correct? Just search for each file and replace it with the new ones?

Exactly. That's what I do when I use custom taskbar icons. Why waste time and space with .dsm, .rgu, option.xml, when you have to delete the duplicates anyway? The only good reason that I can think of, is so that they stay with your oem base, and when you upgrade your sys you will already have them in your kitchen, and judt have to delete the sys dlls. Either way, it works fine. BTW, I've never needed to include sdkcerts when cooking in taskbar dlls.