Colonel's Custom 3.5 (New 3/19)

[TheRocoLoco]

Originally Posted by colonel

New nk.nbf going up. Fixed the VC feedback problem, but the gateway still stays open. At least she talks now. Also fixed the speed dial button in the phone app...

What did you do for these 2 fixes? I need to make them both to my own ROM.

Thanks a ton in advance
-TRL

[jamesus]

Originally Posted by colonel

BTW, noone likes MemMaid or PIEPlus?

Love having MemMaid included...saves me time installing!

[colonel]

Originally Posted by Jmckinney1976

I am having two issues so far:

1. PIEPlus says it's expired as soon as I boot up for some reason, even though I am entering the correct date.
2. My ppc is freezing for no apparent reason. Last night it froze at 5:00AM while charging

In regards to PIEplus, what do you mean by the correct date? Don't know about the freezing. Were you running any apps or have anything running from the SD? Also, your question about the .dll, when did this error occur? Were you trying to run something when it appeared?

[colonel]

Originally Posted by TheRocoLoco

What did you do for these 2 fixes? I need to make them both to my own ROM.

Thanks a ton in advance
-TRL

These are all the entries for both. There are only about 5 for speed dial button at the top. Compare or use the rest for VC

[colonel]

Originally Posted by naigaboy

Just woke up to the same problem. also i just tried to map voice command to button 5 and i realised that HKLM\software\OEM\voicecommand doesnt exist. I had to create the registry key, then create the string value=Path, data=Windows\rundll32.exe to get it to map to button 5, for anybody else that wants that back. (thanks Luv2chill)

Put this in for the next nk.nbf.

[luv2chill]

Actually I read a post over at pdaphonehome from a guy who said that a blank value for path works too. I've just tested it and indeed it does (can't believe I never tried that). Anyway, I suggest that as a better alternative... really no harm in running rundll32.exe but why do it if you don't have to? So just make the string value called Path and leave the data blank.

I will update my original post and the cab file attachment with that change.

[colonel]

Got it. Makes perfect sense.

Still dealing with the IDTransfer issue. The error code seems to point to this entry.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETCompactFramework\Installer\Assemblies\Global]
"Microsoft.WindowsMobile.Status, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"=hex(7):5c,\
  00,77,00,69,00,6e,00,64,00,6f,00,77,00,73,00,5c,00,47,00,41,00,43,00,5f,00,4d,\
  00,69,00,63,00,72,00,6f,00,73,00,6f,00,66,00,74,00,2e,00,57,00,69,00,6e,00,64,\
  00,6f,00,77,00,73,00,4d,00,6f,00,62,00,69,00,6c,00,65,00,2e,00,53,00,74,00,61,\
  00,74,00,75,00,73,00,5f,00,76,00,31,00,5f,00,30,00,5f,00,30,00,5f,00,30,00,5f,\
  00,63,00,6e,00,65,00,75,00,74,00,72,00,61,00,6c,00,5f,00,31,00,2e,00,64,00,6c,\
  00,6c,00,00,00,4d,00,69,00,63,00,72,00,6f,00,73,00,6f,00,66,00,74,00,2e,00,57,\
  00,69,00,6e,00,64,00,6f,00,77,00,73,00,4d,00,6f,00,62,00,69,00,6c,00,65,00,2e,\
  00,53,00,74,00,61,00,74,00,75,00,73,00,2e,00,64,00,6c,00,6c,00,00,00,00,00

One strange thing is that the registry entry for the OEM for both CF1 and CF2 has this entry.

"Microsoft.WindowsMobile.Status, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"=multi_sz:"\\Windows\\GAC_Microsoft.WindowsMobile.Status_v1_0_0_0_cneutral_1.dll",
  "Microsoft.WindowsMobile.Status.dll"

EDIT: Nevermind, That is just the hex coding of the same string. I should have know that right away.

[muscle1]

Hey guys, what's wrong with the MMS Composer??? It's not in the options of messaging!
colonel?

[colonel]

Its in mine.

[muscle1]

Hmmmmmmmmmm that's odd, it's not in mine!