Mark wrote:
> You still don't make sense, but then again, you don't have to. The MVP
> status automatically makes you right.
I don't make sense because I disagree with you? Your response is just to
insult someone, eh? Doesn't make you look good. Not that I care, you're
going in my killfile anyway.
I'm not going to argue with you, but I will take the time to put this in
very simple terms you will understand:
When you are troubleshooting, you don't just plunge in and try things in a
scattershot fashion. Successful troubleshooting needs to be systematic and
careful. Here is a typical troubleshooting triage:
1. Ask client (or in this case OP) for the recent history of the machine. Do
this with the full understanding that they may not know or they may lie
because they're embarrassed. If you can find out anything, it will help
narrow down the troubleshooting path.
2. Ask client (or in this case OP) if the data is backed up and if it needs
to be. Always make sure the data is secured before starting major repairs.
Oh, and this would include a Repair Install.
3. Based on #1, #2, and examination of machine (hands-on examination is
obviously not possible in a newsgroup), take/make logical troubleshooting
steps.
You can look up any words you didn't understand at
www.dictionary.com.
*plonk*
Malke
--
MS-MVP
Elephant Boy Computers
www.elephantboycomputers.com
Don't Panic!