Free Republic
Browse · Search
News/Activism
Topics · Post Article

To: VeniVidiVici
Do you have a link for this? I have a link that says this was a fault with Harris' implementation of the software that uses GetTickCount, and that the 49.7 day limitation of it in the API is due to it being 32-bits.

We have the same information. Microsoft's implementation rolled over at 49.7 days (2^32/(1000*60*60*24)). Microsoft's RPC uses GetTickCount(). Pre-fix implementations (Update Rollup 1 for Windows 2000 SP4 last year fixed it) would grow to use 60% of processor resources after the GetTickCount() rollover, killing system and network performance.

Because of this, the machine would become unusable if the FAA didn't reboot often. Harris put in a reset routine when the OS hit 49.7 days of uptime as a safeguard against the slowdown. So you get shutdown instead of slowdown.

It still amazes me though. Microsoft didn't think anyone would want to have their server up for 50 days at a time?

80 posted on 04/28/2006 5:45:58 AM PDT by antiRepublicrat
[ Post Reply | Private Reply | To 77 | View Replies ]


To: antiRepublicrat
Microsoft didn't think anyone would want to have their server up for 50 days at a time?

That sounds like the wisdom of experience.

92 posted on 04/28/2006 8:12:58 AM PDT by Petronski (I love Cyborg!)
[ Post Reply | Private Reply | To 80 | View Replies ]

Free Republic
Browse · Search
News/Activism
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson