N
Neville Lang
Hi all,
This query is on the operation of WM2003 and not .NET CF. Over the weekend,
I finally found time to update my Compaq iPAQ 3970 from the Pocket PC 2002
operating system to Windows Mobile 2003. At the same time, I finally got
around to update the .NET CF to SP1. The improvement in performance is very
good, especially as I am building an app based around Tab Controls.
My question is that with the old operating system, when I booted up my main
computer each morning, the Pocket PC would automatically power on as well in
the cradle and when the bootup completed, the Activesync would begin. What I
have found is that when I boot up my main computer now, the Pocket PC does
not automatically power up - instead I need to manually turn it on and then
Activesync fires up. Does anyone know why this action has changed or is
there a setting that needs to be made?
Apologies in advance for posting on this NG as this is not strictly a .NET
CF query.
Regards,
Neville Lang
This query is on the operation of WM2003 and not .NET CF. Over the weekend,
I finally found time to update my Compaq iPAQ 3970 from the Pocket PC 2002
operating system to Windows Mobile 2003. At the same time, I finally got
around to update the .NET CF to SP1. The improvement in performance is very
good, especially as I am building an app based around Tab Controls.
My question is that with the old operating system, when I booted up my main
computer each morning, the Pocket PC would automatically power on as well in
the cradle and when the bootup completed, the Activesync would begin. What I
have found is that when I boot up my main computer now, the Pocket PC does
not automatically power up - instead I need to manually turn it on and then
Activesync fires up. Does anyone know why this action has changed or is
there a setting that needs to be made?
Apologies in advance for posting on this NG as this is not strictly a .NET
CF query.
Regards,
Neville Lang