Originally posted by: Smilin
If you would like to focus on additional aspects of your system restore conversation we can do that. Honestly I find you a bit tiresome though. Do you really want to go into how much of a drain system restore is on your system when it spins for 2 seconds once every 24 hours? Is that **really** an argument you want to have?
Originally posted by: hooflung
The idea behind Vista is grand. The DRM shows pretty conclusively that trusted computing is misrepresenting the core ideals of what trusted computing actually is. It should be 'mis'trusting computing.
Microsoft cares more for its partners than it does the back of the people who put their products on the map.
Originally posted by: bsobel
Originally posted by: hooflung
The idea behind Vista is grand. The DRM shows pretty conclusively that trusted computing is misrepresenting the core ideals of what trusted computing actually is. It should be 'mis'trusting computing.
Microsoft cares more for its partners than it does the back of the people who put their products on the map.
Perhaps you can explain exactly how DRM has inconveinced you or stopped you from doing anything other than stealing content?
Originally posted by: ielmox
Originally posted by: Smilin
If you would like to focus on additional aspects of your system restore conversation we can do that. Honestly I find you a bit tiresome though. Do you really want to go into how much of a drain system restore is on your system when it spins for 2 seconds once every 24 hours? Is that **really** an argument you want to have?
You add nothing new to the argument, you're simply repeating the same crap you were hand-waving about before when you got in a tiff following an emotional reaction to minor comment pertaining to your dear MS SR. I already explained and clarified my position, and I have backed up all my claims with relevant cites. If you have something new and of substance to add, go right ahead. Otherwise consider my original point not only intact but reinforced: system restore is a resource hog for all the reasons already stated and with the weight of authority already provided.
Originally posted by: lxskllr
Originally posted by: Smilin
You should like call and talk to one of the guys that has supported system restore at Microsoft. I bet those guys have seen every SR case known to man and know the ins-and-outs and limitations. They might know what works, what doesn't and even have access to the SR source code. Heck I bet they've even seen dozens of cases where people claim performance issues but when troubleshot down to root cause it turns out to be something else. (someone here knows where I'm going with this... )
Do you have his number? :Q
Originally posted by: Smilin
Originally posted by: ielmox
Originally posted by: Smilin
If you would like to focus on additional aspects of your system restore conversation we can do that. Honestly I find you a bit tiresome though. Do you really want to go into how much of a drain system restore is on your system when it spins for 2 seconds once every 24 hours? Is that **really** an argument you want to have?
You add nothing new to the argument, you're simply repeating the same crap you were hand-waving about before when you got in a tiff following an emotional reaction to minor comment pertaining to your dear MS SR. I already explained and clarified my position, and I have backed up all my claims with relevant cites. If you have something new and of substance to add, go right ahead. Otherwise consider my original point not only intact but reinforced: system restore is a resource hog for all the reasons already stated and with the weight of authority already provided.
You live in a special, special world where reality bends around and ignorance turns into pure sunshine. Since I'm not "out there" with you why don't you remind me again where you proved system restore is a resource hog? Perhaps you'll explain:
How much cpu does it eat?
How much memory?
How much disk space?
What other "resource" are youreferring to?
The only thing it even remotely consumes is disk space. That argument has been beat to death. Move the slider or stand back while SR automatically reduces it's footprint as needed.
How much CPU and memory does it consume? If you run something resource intensive like say video editing or a game for 24 hours straight (insane!) what percentage of frames do you think will fail to render because of this "hog"?
c'mon don't give up. You're on the threshold of proving your point and stopping my laughter. I can just feel it!!
Originally posted by: ielmox
Originally posted by: Smilin
If you would like to focus on additional aspects of your system restore conversation we can do that. Honestly I find you a bit tiresome though. Do you really want to go into how much of a drain system restore is on your system when it spins for 2 seconds once every 24 hours? Is that **really** an argument you want to have?
You add nothing new to the argument, you're simply repeating the same crap you were hand-waving about before when you got in a tiff following an emotional reaction to minor comment pertaining to your dear MS SR. I already explained and clarified my position, and I have backed up all my claims with relevant cites. If you have something new and of substance to add, go right ahead. Otherwise consider my original point not only intact but reinforced: system restore is a resource hog for all the reasons already stated and with the weight of authority already provided.
Originally posted by: bsobel
Originally posted by: ielmox
Originally posted by: Smilin
If you would like to focus on additional aspects of your system restore conversation we can do that. Honestly I find you a bit tiresome though. Do you really want to go into how much of a drain system restore is on your system when it spins for 2 seconds once every 24 hours? Is that **really** an argument you want to have?
You add nothing new to the argument, you're simply repeating the same crap you were hand-waving about before when you got in a tiff following an emotional reaction to minor comment pertaining to your dear MS SR. I already explained and clarified my position, and I have backed up all my claims with relevant cites. If you have something new and of substance to add, go right ahead. Otherwise consider my original point not only intact but reinforced: system restore is a resource hog for all the reasons already stated and with the weight of authority already provided.
Actually you haven't proven anything, you've made ubsubstantiated claims. At this point your close to simply trolling so advise you to let it drop.
Those benchmarks were taking near the release of Vista, using early drivers. When SP1 comes out and the drivers have matured, I doubt there will be a performance difference. The same was true when Windows XP was release. Most programs ran faster in Windows 98.
Originally posted by: themisfit610
One other thing that drives me absolutely bonkers with Vista is its constant prompting for your admin password if you need to do anything.
Originally posted by: n7
I have SP1 beta on my notebook.
I should really test it on my desktop, but i don't see any point.
I don't understand what you guys think is going to be magically better in SP1...
Yes, there will be some changes under the skin, but thus far, i've noticed nothing really different.
The whole concept of waiting for a Service Pack is silliness these days IMO, since there's not much to change.
Originally posted by: ShawnD1
Originally posted by: themisfit610
One other thing that drives me absolutely bonkers with Vista is its constant prompting for your admin password if you need to do anything.
UAC takes 5 seconds to disable.
Originally posted by: BehindEnemyLines
There are times I wonder why UAC prompt appears when it doesn't really make sense. For example (these are my opinions), the button that opens up Resource Monitor - it only monitor, right? I just want to see what process is accessing which file.
Originally posted by: Smilin
You live in a special, special world where reality bends around and ignorance turns into pure sunshine. Since I'm not "out there" with you why don't you remind me again where you proved system restore is a resource hog? Perhaps you'll explain:
Originally posted by: bsobel
Actually you haven't proven anything, you've made ubsubstantiated claims. At this point your close to simply trolling so advise you to let it drop.
Originally posted by: ielmox
Besides, you're automatically assuming that System Restore works perfectly - not a safe assumption, particularly not when you consider that different components and functions can end up compounding system problems. I refer to cases such as this one, in which a user's System Restore took up massive disk space even after the SR quota was reduced:
http://techrepublic.com.com/52...hreadID=216768&start=0
An admin who answered advised switching off System Restore too - and he cast a lot more doubt than I have on the usefulness of restore. Lack of further replies suggests the problem was happily solved with this simple fix.
Originally posted by: lxskllr
That link is meaningless. He's saying system restore is accounting for 70% of the used space. 70% of what? Without knowing how much space is used in total, 70% means nothing.
I would suggest you carefully read Smilin's signature, then even more carefully read all of his posts in this thread.
System restore is great. It doesn't always work perfectly in fixing a machine, but in the 3 times or so that I've used it, it's worked fine.
Originally posted by: ielmox
percentage of space is a standard indicator in disk applications, including the native Windows display, the System Restore quota manager, as well as Disk Keeper and similar software, all of which provide indications and recommendations based primarily on percentages. Percentage used would thus most definitely appear not to be meaningless.
Also, the guy does comment on the size of the disk, you seem to have missed that. But disk size simply isn't that relevant here, it was an instance showing how System Restore can get it totally wrong - first by seriously exceeding default disk quota (by percentage), then by exceeding the minimum disk quota (by percentage) after the user turned it down to the lowest setting (by percentage).