1 post • joined 8 Apr 2008
@jason - There's an update out that claims to fix the fabled 80073712 error -- http://support.microsoft.com/kb/947821/en-us has the details.
The Register - Independent news and views for the tech community. Part of Situation Publishing
Biting the hand that feeds IT © 1998–2021