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

[madcook]

hey rstoyguy thanx to your tutorial i made my first oem it was opera 15613 just a test but still thanx

[mwalt2]

I have a problem with duplicate files when I create my OEM. The OEM made by packagecreator creates a setupdll.dll file. There is also a file of that name in another OEM that I am trying to use. They have different file sizes, but give duplicate errors in buildOS. I have the option checked to prefix files for duplicates, but it does not prefix the setupdll.dll file. How can I get around this problem? Thanks.

[rstoyguy]

Originally Posted by mwalt2

I have a problem with duplicate files when I create my OEM. The OEM made by packagecreator creates a setupdll.dll file. There is also a file of that name in another OEM that I am trying to use. They have different file sizes, but give duplicate errors in buildOS. I have the option checked to prefix files for duplicates, but it does not prefix the setupdll.dll file. How can I get around this problem? Thanks.

Those are usually safe to delete. They are usually run when the .cab is installed, you just gotta figure out what they do...

[Trident]

I read the first few pages of posts... skimmed actually.
You mention that these OEMs are designed for the PPCG OEM.rar files in the kitchen that's in the stickys.
Will they also work in kitchens like Calkulin's?

[rstoyguy]

Originally Posted by Trident

I read the first few pages of posts... skimmed actually.
You mention that these OEMs are designed for the PPCG OEM.rar files in the kitchen that's in the stickys.
Will they also work in kitchens like Calkulin's?

Yep, and unless otherwise noted diamond/touchpro as well. This all got started back when chef's didn't release kitchens, and ppckitchen was born. Now there are a ton of kitchens and should work for most. As long as the programs work on the device/wmversion it's good. And I've used calkulins kitchen tools since I jumped to a vga device, so....and tested.

Those kitchen guys can only provide so many OEM's...

[Trident]

Is it possible to get an OEM for the newest tsowen taskbar that will work on a WM6.5 ROM (using the Sprint signal strength settings and including sdkcerts)?

Attached for your convenience.

[indagroove]

Originally Posted by Trident

Is it possible to get an OEM for the newest tsowen taskbar that will work on a WM6.5 ROM (using the Sprint signal strength settings and including sdkcerts)?

Attached for your convenience.

You don't need an oem for that. I've extracted the files for you (attached) and you can do one of two things with it:

1. Drop all the files into OEMDrivers (or pretty much any OEM package for that matter, and then delete all duplicate files from OEM and SYS.
2. Just replace all the files in OEM and SYS with the once in the attachment.

If you really need an oem for this, just run the folder through package creator to create rgu, dsm, and option.xml.

[rstoyguy]

Originally Posted by Trident

Is it possible to get an OEM for the newest tsowen taskbar that will work on a WM6.5 ROM (using the Sprint signal strength settings and including sdkcerts)?

Attached for your convenience.

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.

[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.

Does SDKcerts need to be run before this or is it included and/or not needed?

Originally Posted by indagroove

You don't need an oem for that. I've extracted the files for you (attached) and you can do one of two things with it:

1. Drop all the files into OEMDrivers (or pretty much any OEM package for that matter, and then delete all duplicate files from OEM and SYS.
2. Just replace all the files in OEM and SYS with the once in the attachment.

If you really need an oem for this, just run the folder through package creator to create rgu, dsm, and option.xml.

This seems like a great option. This way this will be the default, correct?
Will it still show up as an installed "program"?
Are the duplicates in a particular folder anywhere? Browsing through the OEM and SYS folders in the kitchen, I couldn't find any of them. #2 therefore has the same issue.

You guys are so good.
Really.

[rstoyguy]

Originally Posted by Trident

Does SDKcerts need to be run before this or is it included and/or not needed?

You guys are so good.
Really.

SDKcerts is included in both the RGU and provxml. It is basically a security certificate in a registry entry form...