Posted in the BuildOS thread...

Yes, it is just another method of getting the cert installed. I've used the .cab version successfully on every version of Windows Mobile I've had on my phone (including the original Sprint ROM and updated official Sprint ROM) with the exception of the latest (1117) kitchen. I can't personally vouch that it works in that kitchen as I now use the OEM method (I started using that in the 1108 kitchen).

Though I guess if the cert if properly installed as a trusted cert in Windows Mobile, then this may not be the solution. Have you tried accessing your exchange server using Pocket IE? Active Sync and Pocket IE are supposed to use the same APIs for accessing the server so if you can't access it from IE w/out SSL errors, it won't work in Active Sync.

Not a bug but, more like a benefit
 

I noticed that after I cooked this ROM that I am getting EVDO signal. I have NEVER, in 1 1/2 years of owning my PPC 6700, received EVDO signal here at my home. I don't know if this is a result of his build or if a tower was added at the precise time that I uploaded this ROM lol. Just wanted to mention as I thought it was odd. I did upgrade my radio about 2-3 weeks ago to 1.43 but only had 1-2 extra reception bars on 1x.

Please disregard this post. It is apparently an new tower. I don't want to get this forum off topic because I jumped the gun prior to checking on what I was posting. If any of the moderators want to delete this post and any referring to it please feel free to do so.

That's great, but just as an FYI it definitely is not related to this ROM. Your carrier must have turned up a new EV-DO tower.

That is the case apparently. After my wife got home I checked her phone and it is showing EVDO as well. Just really funny that it went live around the very same time.

i am now starting to get EVDO more often in my apartment, however i think its only due to the weather as i am on the fringe of an EVDO coverage area.

installing ROM
 

A little confused here. The instructions say to start the executable "ppc-buildOS.exe" from the BuildOS folder within the root directory "BuildOS". Starting that shortcut produces: "unable to open BuildOS_config.txt.....". I assume then we should use the "Apache Helmi WM6 PPC-BuildOS" link in the root directory. Clicking this I go past the "carrier not found" and then I get "Module PPCGeeks_OEM.rar was not found. I click OK and it states that 5 modules were not found including voice commmander, HTC smartdiling and 3 office applications. The selections window does fill after that. Should I ignore all these flags?

First, yes you should be using the shortcut to launch buildos, not the exe directly.

Second, you are missing the ppcgeeks_oem.rar file, or if you do have it you didn't put it in the right place. First of all, place it in the root of the BuildOS folder (i.e. C:\BuildOS). Second, don't extract it (I know that seems counterintuitive but BuildOS automatically takes care of that). After you have done that, relaunch BuildOS with the shortcut and you should be good to go (aside from the carrier not found error which you should just ignore).

Is anyone having problems getting MS voicecommand 1.6 to announce incoming calls?? Yes I have the box checked.

This happened before and I applied the WM6 service patch 1 and it began working with the previous versions and VG's version.

Thanks

If you are using the OEM for voice command that came with this kitchen then you should not be having any problems with call announcements. If you installed it later via cab then I dunno.

But I made this particular OEM and tested it very thoroughly so I would be surprised if it's not working for people. Please give more details if so (not announcing over the speaker or not announcing over bluetooth?).

One thing is for sure, that service pack thing is not applicable to these kitchen-based ROMs. It could potentially cause other problems so if you applied it you may want to hard reset to get rid of it.