R
Richard
Goal, continue to boot into Xpe and run the shell/application.
I fixed the BIOS now so if the Cmos battery goes dead or the CMOS is
cleared, it will have the proper defaults to continue operation.
Application/Shell will take care of reporting issues to the remote server
via satellite.
Now, if it's a battery or the time and date is lost, XPe comes up and states
that "The System Time is incorrect" and hangs there unless I tell it to
continue. We have seen this a time or two during real bad storms, and it sux
driving out a couple of hundred miles to set the date and time. I can do
that remotely if the system boots on up.
Is there an easy way to avoid that? I do not have message interception at
the moment, is this about the only fix? Any registry keys that allow XPe to
ignore incorrect time settings?
Thanks,
Richard
I fixed the BIOS now so if the Cmos battery goes dead or the CMOS is
cleared, it will have the proper defaults to continue operation.
Application/Shell will take care of reporting issues to the remote server
via satellite.
Now, if it's a battery or the time and date is lost, XPe comes up and states
that "The System Time is incorrect" and hangs there unless I tell it to
continue. We have seen this a time or two during real bad storms, and it sux
driving out a couple of hundred miles to set the date and time. I can do
that remotely if the system boots on up.
Is there an easy way to avoid that? I do not have message interception at
the moment, is this about the only fix? Any registry keys that allow XPe to
ignore incorrect time settings?
Thanks,
Richard