Anonymous

USA

Guess

Your report is very misleading, and pretty vague, and almost assuredly untrue. For example, you stated:

". . . a Microsoft-based replacement for an older Unix system needed to be reset every thirty days 'to prevent data overload', as a result of problems found when the system was first rolled out."

Assuming that the Windows server in question was fully updated with the latest Service Packs and Critical Updates, then the ONLY reason this would occur is if there was an application running on it that had a memory leak! A "memory leak" would indicate that the program WAS NOT CODED PROPERLY!

Furthermore, you said, " . . . However, a technician failed to perform the reset at the right time and an internal clock within the system subsequently shut it down. A back-up system also failed."

My, I wonder what OS that "Backup System" was running . . .

So--let me get this straight:

1.) A Microsoft Windows server replaced a UNIX machine, and presumably there was SOME application running on it that was necessary for the Radio system to work properly.

2.) Since the only reason that a Windows server needs to be rebooted is because of a memory leak, which can only be caused by an improperly-coded application, and it would appear that the application in this case is none other than the one that is necessary for the radio system to work properly.

That would indicate that the fault and blame lies DIRECTLY in the lap of whomever CREATED that application!!

Oh, but then it's SO EASY to shift the blame to SOMEONE ELSE, ESPECIALLY if you HATE Microsoft, and of course, Microsoft makes a HANDY "Whipping Boy", doesn't it?

Maybe you should be a little more responsible in your reporting, and gather all the FACTS before you start "reporting" things like this.

Also, MAYBE whomever coded that application should take responsiblity for their poor code writing--don't you think?