Hey, who turned down the thermostat? I thought it was supposed to stay above 0F last night and it was -8F when I got up. Drove the Voyager anyways although it (the Voyager) was unhappy about starting. Heater output temp got up to approx 80F although I don't think the interior of the van got over 40F. Definitely the next project is the heater.
Spent a lot of time yesterday working on the CEO's Treo 700 from Verizon. It wouldn't AutoSync. It would connect for about 15 - 30 seconds then disconnect. Remove it from the cradle, return it to the cradle, briefly connect then disconnect, repeat. Learned that the new AutoSync 4.1 (required for the Treo 700) uses the TCP/IP stack for connectivity, the USB connection shows up in Device Manager as a Network card. The PC thinks it is a 10 Meg network device!
Coincidently, since the Treo was installed the PC has been taking a very long time to start. It was because the PC was looking at this network device and trying to connect to it (which it can't do until ActiveSync is loaded after login!). If the Treo is not connected to the PC until you want to AutoSync then boot times are back to normal.
Rebuilt the TCP/IP and winsock stacks using netsh, uninstalled and reinstalled ActiveSync, cleaned up the Startup sequence, do a soft reset of the Treo. Same thing: connect briefly then disconnect. So I performed a Hard Reset of the Treo and now it works great.
Of course, you don't want to perform a hard reset unless absolutely needed because it resets the Treo to factory defaults, but sometimes that is the cure. Why the heck Palm is using M$ ActiveSync I don't know because I have never had a problem with HotSync and I have never had a good experience with ActiveSync.
'Til later,
E
No comments:
Post a Comment