- Messages
- 36,134
- Location
- ABQ NM
C'mon Sean, we all you you just came here to pick a fight.I wasn't trying to cause a stir on this one. Really, I wasnt'.
I guess my perspective comes from, trying for a long(er) term fix (to keep the customer from calling back next week with the same problem).
If you have the software and drive space to make an entire image of your drive, it will certainly be much faster.
The definate down side of what I orginally suggested is the time it takes. I forgot to mention how long this process can take. My apologies here.
I do agree with you about the risk of restoring an image of a corrupted system, but that's why I have incremental images at various milestones. To over-simplify, if my system goes south this week, I'll restore last week's (or maybe last month's) image.
I also agree about a lot of folks not knowing how to maintain or fix a system. I've done telephone tech support for our company, so I know how clueless some people can be.
Thinking of Blue Screens, back in the first year or two of Windows NT, we sold a product that replaced several important NT system files with our own version. (Files like NTOSKRNL.EXE, and several others at that level. We were MS source code licensees at the time, so this was done with MIcrosoft's blessing.) Things would work fine until someone installed a Service Pack, then re-installed our software, which would put the old kernel file back in place. At that point the customer had a very dead, very blue system. I got to walk a number of guys through complete WinNT re-installations over the phone. By the time Windows 2000 was released, we and MS had built our hooks into an API, so we no longer had to swap out the kernel for our product.