1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Date changes after connecting w/dialup

Discussion in 'Windows XP' started by compdude, 2003/05/21.

Thread Status:
Not open for further replies.
  1. 2003/05/21
    compdude

    compdude Well-Known Member Thread Starter

    Joined:
    2002/01/10
    Messages:
    62
    Likes Received:
    1
    I have recently experience something truly bizarre with my daughter's PC. It is a Compaq 667 MHz, 256 Mb RAM, running XP Pro. I recently upgraded to XP Pro from Win 98. I didn't notice any problems until I went to update Norton A/V. I was told that my subscription had expired on 5/18/2004. I looked at the system date and it was February 7, 2036.

    I changed the time and date back to current, rebooted and the date was the same. Rebooted and changed the BIOS date and everything was fine. Long story short, whenever I connect via dialup, as soon as the connection is established, the hard drive gets hit, and about 10 seconds later, the date changes.

    Now, I understand the significance of this date as it relates to the internet clock, but I can't make the connection between it and what is happening on my machine. I have run a complete virus scan (after getting the latest updates) and run SpyBot S&D. Both did not find anything. Is it possible that my ISP is pushing this date down to my machine? I contacted them and they said the problem has nothing to do with them.

    Anyone have any idea on this one?

    Thanks
     
  2. 2003/05/21
    unixfan

    unixfan Inactive

    Joined:
    2002/01/26
    Messages:
    282
    Likes Received:
    0
    Have you tried disabling Internet Time Synchronization under Date and Time in Control Panel?
     

  3. to hide this advert.

  4. 2003/05/21
    compdude

    compdude Well-Known Member Thread Starter

    Joined:
    2002/01/10
    Messages:
    62
    Likes Received:
    1
    Yes, I forgot to mention that. I renamed timedate.cpl to timedate.old so the O/S couldn't find it to use it. XP did warn me when I renamed it that "critical system files had been altered" and wanted to restore but I ignored and continued. Still got the same results.
     
  5. 2003/05/27
    compdude

    compdude Well-Known Member Thread Starter

    Joined:
    2002/01/10
    Messages:
    62
    Likes Received:
    1
    I finally was able to resolve this. The problem was caused by a Compaq-specific application called SyncClk.exe. I was able to track it down to an ini file called cpqcld.ini. There were entries for several applications to launch when a network/internet connection is established. I commented out these entries and the problem went away. I am assuming that the return from whatever server was called by SyncClk must return a 0 or null. This is then interpreted as February 7, 2036 (date the internet clock rolls over to 0). Just one more reason to not get a Compaq, or if you already have one, remove all their proprietary software. It usually causes more problems than it helps.
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.