If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#196
|
|||
|
|||
Build 10031
On Mon, 16 Mar 2015 13:24:56 -0700, "Gene E. Bloch"
wrote: On Sun, 15 Mar 2015 19:06:38 -0500, Char Jackson wrote: On Sun, 15 Mar 2015 14:09:42 -0700, "Gene E. Bloch" wrote: On Sun, 15 Mar 2015 10:56:58 -0500, Char Jackson wrote: On Sat, 14 Mar 2015 18:04:54 -0700, "Gene E. Bloch" wrote: On Sat, 14 Mar 2015 19:53:20 -0500, Char Jackson wrote: On Sat, 14 Mar 2015 12:19:13 -0600, GreyCloud wrote: Char Jackson wrote: On Fri, 13 Mar 2015 13:03:48 -0600, GreyCloud wrote: Char Jackson wrote: I don't use Restore Points, and in fact that's one of the very first features I disable on each of my personal systems, but I didn't know that rolling back to a previous RP would also clean up the filesystem. I'm very surprised to hear that, and if it's true, it makes me extremely happy to know that this feature is disabled. At the time I was busy cleaning up the remnants off my hard drive that was eating up a lot of space. Unfortuanely, one particular remnant directory was also tied to VS. VS wouldn't load any projects. So I resorted to the restore point. Problem solved. All you have to do is make a restore point once a week and you won't have any problems. Regarding that last sentence, I'm sorry but I don't believe that for a second. Then you apparently just don't do much system cleaning then. No, that's not the problem with that statement. The problem is that you're saying that if everyone made a restore point once a week then no one would have any problems. Restore points don't prevent problems, as you surely must know. In the best case, they might fix an issue, but you never know what else they might 'fix' at the same time. Restore points aren't able to read your mind. Instead, they just change everything they think they should change, all at once. In anything less than the best case, they make one or more changes to your system without fixing the issue you're currently interested in, so you're left wondering what got changed while knowing that the thing that was surely broken is still broken. It's sort of a lose-lose. I'd say "In anything less than the best case, they make one or more changes to your system without fixing the issue you're currently interested in" is quite an exaggeration... How about "in some of the worst cases" as a more moderate - and IMO *much* more accurate - qualifier? I've never experienced the extreme of which you write. I re-read my text and compared it to yours, and I think I have to stay with mine. Aren't there really only two possible outcomes when you roll back to a previous restore point? Either your issue is resolved, or it isn't. Either way, the user has no idea what else was changed in the process. I don't see a gray area in between "my issue was resolved" and "my issue wasn't resolved", and in both of those cases there can be other things that got changed that you may not even see until later because you're focused on the thing you were trying to resolve. Am I looking at it wrong? You have ignored a range of grey shades (way more than 50, IME). Give me some hints, please. What am I overlooking? (I'm not intentionally ignoring anything, so I translated 'ignored' into 'overlooking'.) I'm going to try to wrap up by doing one last post, then I'll follow your lead, at least until the topic comes up again next time. :-) For one thing, many people have already posted about having their butts saved by restoring to an earlier restore point, me among them. I fully acknowledge that it works (sometimes or even most of the time). My only concern is, and has always been, that the process isn't transparent. If it fixes the issue that you're trying to fix, then you know it made changes related to that issue. However, whether restoring fixed the issue or not, there's no way to tell what *other* system-level changes it made at the same time. That's pretty black/white to me, and it makes me too uncomfortable to consider using it. I certainly can't use it on someone else's system, for example. I have absolutely no problem with other people using it, of course. I assume they've weighed the pros and cons and then decided the benefits outweigh the risks. I'm fine with that. I will say no more on this topic. Thanks for trying to enlighten me. |
Ads |
#197
|
|||
|
|||
Build 10031
On Mon, 16 Mar 2015 13:24:56 -0700, "Gene E. Bloch"
wrote: For one thing, many people have already posted about having their butts saved by restoring to an earlier restore point, me among them. Me too. |
#198
|
|||
|
|||
Build 10031
Ken Blake, MVP wrote:
On Mon, 16 Mar 2015 13:24:56 -0700, "Gene E. Bloch" wrote: For one thing, many people have already posted about having their butts saved by restoring to an earlier restore point, me among them. Me too. Out of curiosity, but do you have any info on what David Cutler is working on now at MS? |
Thread Tools | |
Display Modes | Rate This Thread |
|
|