The process of determining the fault would have probably also included the following steps in this order:
1. The tech would have asked to have the rifle reloaded (reinstall) and again miss the mark completely.
2. The tech would have blamed the whole incident on whomever drove him to the range. (Bad or corrupted driver
) After leaving the range and returning in a cab the whole incident would be repeated, but it's likely that the tech would actually miss so badly he would hit the next target. That would not be a bug, but rather an intended feature.
3. In a feat of brain-power rarely observed in the typical M$ tech, the whole incident would be blamed on a bent cleaning ramrod. (Bad ram
) The tech would insist the rifle be cleaned with a new ramrod, but unfortunately the problem would still persist.
4. Firmly convinced M$ could not be at fault, the tech would examine the gun's serial number and check it against the blacklisted serial number list. Finding this was, in fact, a genuine copy, and surprising enough just like every other M16 in the world, the problem would still be unresolved.
5. The tech would blame the whole incident on a 3rd party.
Of course, the real problem from the beginning is that the typical Microsoft tech isn't qualified to fire an assault rifle. (On a similar note, some apparantly barely possess the minimum intellegence level necessary to work on a computer...)
