View Single Post
Old 06-30-2013, 01:25 PM   #896
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by ixtab View Post
I assume that the problem arises because of the developer certificate, which has a "begin" date probably some time in 2011 or 2012.
Sounds likely to me also.
After all, what computer doesn't have the date-time set correctly in the 21st century?

If you can get KUAL installed and running, there is a ntpdate button to set the hardware / software date-time from the public ntp networks.
Without 3G available, the DX would have to get its network connectivity over the USBnetwork cable.

Set the date-time more recent than the certificate start date-time:
(MMDDhhmmCCyy)
Code:
date -u -s 063012002012
hwclock --systohc

Last edited by knc1; 06-30-2013 at 01:56 PM.
knc1 is offline   Reply With Quote