Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/6PNLDCXU4J75BPZ2BTKXA7R4I744Y7HJ/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "[email protected]",
    "message_id_hash": "6PNLDCXU4J75BPZ2BTKXA7R4I744Y7HJ",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/P2LUUKGYYBP44ZXB2NLERRW7OHVNISKU/?format=api",
    "sender": {
        "address": "W7IN (a) montana.com",
        "mailman_id": null,
        "emails": null
    },
    "sender_name": "Larry Gerhardstein",
    "subject": "[amsat-bb] Re: PC clock",
    "date": "2010-05-10T03:23:58Z",
    "parent": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/E4VCXV277AWBQQ5NYAZAQSSFDIXO4RY5/?format=api",
    "children": [
        "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/7KRXQK2PWBONELKRZY72F2GBHMCHSN7I/?format=api"
    ],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "Greg,\n\nDuring the process of getting a serial port interface that worked \nproperly with W7-64b, I experienced a myriad of system crashes.  This is \npossibly why my clock got off by about +30 seconds.  I often check my \nPC's clock against the WWV clock on my wall, especially when tracking \nbirds.  It's now on to within a second.  If it got off by more than 2 or \n3, I'd want to corrected it; the problem is not Doppler, it's a near \noverhead pass (that's when I discovered the PC time error).  Plus, I \nwant correction automatic and not have to mess with it for a long time.  \nI believe the once-a-week default in Win7 for syncing PC time with \nInternet server time is too loose.  Once a day or even once an hour \nseems better to me.\n\n73, Larry W7IN\n\nOn 5/9/2010 7:05 PM, Greg D. wrote:\n> Hi Larry,\n>\n> I know PC clocks are not all that accurate, but we're talking seconds \n> per month.  Needing to update a clock more often than that probably \n> isn't due to the PC hardware.  I've never had one be off this much \n> unless the clock battery was dead, and any PC new enough to run Win-7 \n> isn't going to have that issue.  I would suspect that there is a some \n> software you are running that is messing it up.  Back in the DOS days, \n> this was a common occurrence, and I'm surprised to hear about it under \n> something more modern, but my gut feel tells me that is what is happening.\n>\n> Maybe a device driver or something else low-level.  Try booting \n> something else (a \"Live\" CD of Linux, for example) to prove the \n> hardware is good.  Go back to Windows piece by piece.  If you can \n> figure out which it is, then this whole idea of applying bandaids can \n> go away.\n>\n> Just a thought,\n>\n> Greg  KO6TH\n\n<snip>\n\n",
    "attachments": []
}