View Single Post
  #303 (permalink)  
Old 08-19-2009, 08:37 PM
askwhy's Avatar
askwhy
Regular 'Geeker
Offline
Location: Fort Collins, CO
 
Join Date: Jan 2009
Posts: 284
Reputation: 1338
askwhy is halfway to VIP status based on repaskwhy is halfway to VIP status based on repaskwhy is halfway to VIP status based on repaskwhy is halfway to VIP status based on repaskwhy is halfway to VIP status based on repaskwhy is halfway to VIP status based on repaskwhy is halfway to VIP status based on repaskwhy is halfway to VIP status based on repaskwhy is halfway to VIP status based on repaskwhy is halfway to VIP status based on rep
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: dcd's hermann ROM & kitchen 2.06

Well, it seems that took care of it. Removing the nueBattery in EXT and adding a different OEM of nueBattery (I used the Fast Charge Battery OEM from Calkulin's kitchen) seems to be what fixed the battery icon being stuck at 100% for me. I have now tried cooking with two different versions of phcanOverbmp.dll including the one I wanted all along and they both work fine now. Hot stuff!

Thanks for the help and feedback!

Quote:
Originally Posted by Rourke Swift
Have you tried without the battery OEMs at all? Not only is the ROM already cert patched, but it's already using the appropriate battery drivers as well (has 1% increments and fast charge by default), so I imagine adding the OEMs in would only unnecessarily complicate things.

Simply put, all you need to get a custom taskbar working is the taskbar itself. SDKCerts and nueBattery are superfluous in this ROM/Kitchen.
Thanks for the response. I did try that first -- just adding a phcanOverbmp.dll and the corresponding registry to enable it (under HKEY_LOCAL_MACHINE\security\ResOver\Bitmaps) and that's when I first saw it stuck at 100%. The taskbar dlls were fine for me, only phcanOverbmp.dll for the battery graphics was giving me trouble, and I tried a bunch of them before even looking at the battery driver. As it turned out (see above) replacing the built in battery driver may indeed have been what fixed it, even though the built in one is nueBattery which supports 1% increments and the version I put in was also nueBattery. I can't explain it -- I can only report what finally worked.
__________________
ROM Taste Good!

Last edited by askwhy; 08-19-2009 at 08:47 PM.
Reply With Quote