Ron Martell said:
This means that OEM versions do not necessarily have the ability to
perform certain repair and recovery operations such as doing a repair
install, booting to the recovery console, or replacing damaged system
files by using SFC /SCANNOW. Some OEMs do provide at least some of
these capabilities or equivalent functionality, but doing so is not
mandated by Microsoft.
Tell me about it. I've just installed a couple of business computers for
which I had to spend 3-4 extra very frustrating hours trying to find a way to
get a clean copy of XP onto them. Preinstalled copy loaded with foistware, No
SATA driver, no media, no website entry for the model at all. The HD had an
i386 folder but even that reported missing files when an install was done
from it . Worst of all, it bluescreened well-into the setup, meaning a lot of
time and several repeats spent trying to figure-out why. I was on the point
of giving up and returning the computers as unusable when I found a reference
to someone in a similar situation having success with the SATA driver from
another model. It worked. But honestly, I shouldn't have had to do _ANY_ of
that!
What really takes the biscuit is that we paid extra for a 'business' model
with XP Pro, thinking that would mean a computer ready for domain use.
Instead we got a computer set-up to _advertise_ the products of Symantec et.
al. to us. We need that about as much as we need a free copy of the Blaster
Worm. Or a hole in the head.
This is the 'other side' of software piracy. If the customer has paid for
Windows, is he/she entitled to a copy of _Windows_ .. Or not?
Or should they be faced with a bill for engineer's time, and supply of
proper Windows CD, to sort out the mess left by the OEM?
Or should the engineer treat it as a 'loss leader' and not charge the
customer for the wasted time?
Unfortunately the latter is becoming all-too-common a scenario with new PCs,
and I have to cover my time-costs somehow. The customers find this hard to
understand, though, and I sympathise with them.