|
Yesterday I was cutting code in Visual Studio 2015,
Today I was cutting meadow grass with a scythe.
Ireland is a very strange place.
|
|
|
|
|
Duncan Edwards Jones wrote: I was cutting meadow grass with a scythe
You Luddite, with your hand tools!! Afraid of advanced technology are ye?
Duncan Edwards Jones wrote: I was cutting code in Visual Studio 2015
|
|
|
|
|
Recently I noticed that my new(er) computer (i7, 8Gb Ram, 1TB drive) reports that I've used something like 392GB of my availalbe 921GB.
It looks like this:
http://newtonsaber.com/images/codeproj/drivestats1.png[^]
I thought that sounded like a lot, because I have basically nothing on the machine.
I examined c:\windows\ thinking maybe 8.1 was large: About 20GB in there.
Next I examined all Program Files (x86), Program Files (64), and ProgramData dirs and they equaled about 20Gb.
I was really stumped so I selected all folders on my drive and examined them and it said I had 127GB used. What?
You can see it at:
http://newtonsaber.com/images/codeproj/drivestats2.png[^]
Okay, so there are hidden files on Windows Systems and maybe other explanations for this?!? Anyone got any explanations?
I'm talking about 260GB of space or something. What would that be? That's a lot of data space.
Plus, that's double what I'm supposedly using when examining via File Explorer.
I just don't get it. Is this acceptable and expected?
|
|
|
|
|
No idea?? How much space is taken up by your System Restore files? Just another reason I am grateful I dumped 8.1 and went back to Windows 7! When Win 10 settles down, I'll jump straight to 10.
How do we preserve the wisdom men will need,
when their violent passions are spent?
- The Lost Horizon
|
|
|
|
|
Thanks for replying. And your question is a good one.
I checked it out in Computer Management => Disk Management though and the other space for recovery partitions seem to be taken into account. But again, Disk Management also reports that 57% of my 921GB is taken up.
You can see it in this snapshot of disk management.
http://newtonsaber.com/images/codeproj/drivestats3.png[^]
I greatly appreciate any input on this. It's quite crazy.
|
|
|
|
|
Did you go to Control Panel -> System -> System Protection -> Click on System Drive -> Configure ..... to check the disk space consumed by Restore Points?
How do we preserve the wisdom men will need,
when their violent passions are spent?
- The Lost Horizon
|
|
|
|
|
Cornelius Henning wrote: check the disk space consumed by Restore Points?
Thanks, that is a great one. Didn't know about it.
I t is only at 3.32 GB at the moment though.
Thanks for the input and ideas on this.
|
|
|
|
|
newton.saber wrote: I was really stumped so I selected all folders on my drive and examined them and it said I had 127GB used. What?
Does it include page file and hibernate file? Guess they are around 32GB in total for your system.
<edit>
Are you logged in with administrator account? Are you sure that your account has permission to all directories?
Also: http://blogs.msdn.com/b/ntdebugging/archive/2008/07/03/ntfs-misreports-free-space.aspx[^]
</edit>
modified 1-Aug-15 19:03pm.
|
|
|
|
|
Mladen Janković wrote: page file and hibernate file?
I was wondering about the page file and wasn't sure.
I do have a hibernate file -- meaning I do use hibernate and i love it --, but that is crazy if it takes like a 100GB or something.
So, let's say that the Hibernate file and the page file are 100GB together, then I'm still missing another 160GB. And if those two files really take up 260GB that is just sick. Sick!
|
|
|
|
|
Volume shadow copies?
Try vssadmin at an elevated prompt.
|
|
|
|
|
dandy72 wrote: vssadmin at an elevated prompt.
Wow, I tried that out. I've been using Windows since version 3.0 and I've never heard of that tool.
I'm sure it wasn't in Windows 3.0 though.
Anyways, I ran the tool but don't know exactly what it even means.
I guess what I'm learning is :
Windows eats up your hard drive and that is all there is to say about that.j
"All in the name of safety and protection, we've destroyed your life. But, at least the bad guys didn't compromise you." ~The "Good" Guys
|
|
|
|
|
And did you check your privileges? (hehe) I mean for real, file ACLs and stuff.
|
|
|
|
|
I think it was introduced with Vista.
To make a long story short, try:
vssadmin.exe delete shadows /all
...and see if you regain any space.
And as others have written - try windirstat
|
|
|
|
|
Personally I show all files including the hidden and system files on every system I work on.
You could start at the root and work your way from there narrowing down the largest folders off of the root and keep working your way down untill you find the hog.
It is possible that it could be the (Hidden) System restore/ Volume shadow copy folder.
|
|
|
|
|
Try WinDirStat[^]
It's free, and it should tell you what is hogging your drive.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
|
|
As I noted in my message right above yours. 
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Oopsie! 
|
|
|
|
|
It occurs to me that every algorithm is O(n) for some value n, which may be 2m, m!, m^2, or pretty much anything else, so if I have an algorithm that is O(m!^z), I can simply say that n = m!^z and voila! I have reduced my algorithm to O(n). 
Maybe this will bring Luc back in for a look.
|
|
|
|
|
As long as you're cheating like that, you can also add an arbitrary nesting of logarithms.
|
|
|
|
|
Nesting algorithms are for the birds.
|
|
|
|
|
|
I have the feeling that you are confusing simplifying a problem and solving it...
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Nah, not really, though I admit that I still don't truly understand Big-O notation.
What got me thinking about this today was the comment:
"If you have figured out the O(n) solution, try coding another solution using the divide and conquer approach, which is more subtle"
Now, I'm pretty sure that the first algorithm to come to mind (and the one I implemented) is not O(n) -- I think it's closer to O(n!) (edit: It isn't; it's O(n^2)) -- so I wonder whether they actually know an O(n) algorithm or maybe they don't understand O(n) notation even as well as I.
From there, it was a simple matter to state that every algorithm is O(n).
modified 2-Aug-15 14:31pm.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
