Shipped Rom FULL QWERTY CAB File?

[DbLoCk3NiNe]

Originally Posted by rstoyguy

You might try incorporating this into your rom and delete the duplicate DLL's from the OEM instead of deleting the duplicates out of the rom....

OEM_HTC_Diamond_QWERTY..........................HTC Diamond QWERTY Keyboard

Personally, I have deleted the files from the ROM with no issues.

This gives me that white keyboard, same one you get from the cab thats on the net. Do you or anyone else have that HTC Qwerty Keyboard either cab or OEM, not the Diamond one. Thx

[rstoyguy]

Originally Posted by PPC_N00B

Not sure how to use/what i would put in there? Thanks for the tip though

From what I've heard, it's perfect for this OEM.. What it does is overwrites duplicates that are in the rom without prompting. Buildos processes the Rom archive(sys) files first, then user selection oem's, and then it processes the Patches folder. Anything in the patches folder will overwrite anything else already processed in the rom. Great for no2chem's 1% battery.dll, an updated audiopara.csv file, or a keyboard oem that replaces many standard rom graphics and dll's like this one...

A great undocumented feature!

[mrgeoff]

Originally Posted by rstoyguy

From what I've heard, it's perfect for this OEM.. What it does is overwrites duplicates that are in the rom without prompting. Buildos processes the Rom archive(sys) files first, then user selection oem's, and then it processes the Patches folder. Anything in the patches folder will overwrite anything else already processed in the rom. Great for no2chem's 1% battery.dll, an updated audiopara.csv file, or a keyboard oem that replaces many standard rom graphics and dll's like this one...

A great undocumented feature!

Exactly! I have the rilphone, battery, and the phcanOverbmp DLLs in there.

I haven't tried moving an entire OEM package in there. It would feel a little cluttered to me. Especially if it was the keyboard oem... that has a ton of files lol

[imneveral0ne]

does anyone have the cab he was originally asking for though? im interested in it too ^_^

[rstoyguy]

Originally Posted by imneveral0ne

does anyone have the cab he was originally asking for though? im interested in it too ^_^

Oh yeah.... I believe this is the one I originally made the OEM out of... Just rename it, and remove the .zip extension...

[imneveral0ne]

awesome. now i already have the diamond one on here though. thats gonna be confusing telling the 2 apart lol

[imneveral0ne]

this appears to be the white one as well. i was searching for the black version

[puff]

Originally Posted by rstoyguy

From what I've heard, it's perfect for this OEM.. What it does is overwrites duplicates that are in the rom without prompting. Buildos processes the Rom archive(sys) files first, then user selection oem's, and then it processes the Patches folder. Anything in the patches folder will overwrite anything else already processed in the rom. Great for no2chem's 1% battery.dll, an updated audiopara.csv file, or a keyboard oem that replaces many standard rom graphics and dll's like this one...

A great undocumented feature!

sooo, u got a copy of that 1% battery.dll handy? Thanks for the clarification

Originally Posted by mrgeoff

Exactly! I have the rilphone, battery, and the phcanOverbmp DLLs in there.

I haven't tried moving an entire OEM package in there. It would feel a little cluttered to me. Especially if it was the keyboard oem... that has a ton of files lol

still searchin for the best keyboard for the touch... touchpal?
takes some gettin used to... but very handy...
any other suggestions?

[mrgeoff]

I'm sporting the vogue keyboard. It works just fine for me lol

[rstoyguy]

Originally Posted by PPC_N00B

sooo, u got a copy of that 1% battery.dll handy? Thanks for the clarification

On the ftp under Vogue/Users/rstoyguy/requests/ as no2chembattery.dll.rar or something close... I'd post a link, but I'm having ftp issues...

Originally Posted by PPC_N00B

still searchin for the best keyboard for the touch... touchpal?
takes some gettin used to... but very handy...
any other suggestions?

I use the Diamond keyboard we're discussing, and also use TouchPal v3.5 when texting (follow custom OEM link in sig), but I still find myself using that tiny keyboard and stylus.