Comments for WinDirStat weblog http://blog.windirstat.info News and discussions around WinDirStat Thu, 03 Jul 2008 22:25:38 +0000 http://wordpress.org/?v=2.3.3 Comment on <Unknown> again … by Oliver http://blog.windirstat.info/20070321/unknown-again/#comment-10296 Oliver Thu, 05 Jun 2008 22:10:10 +0000 http://blog.windirstat.info/20070321/unknown-again/#comment-10296 Alright, for any readers of this post. There is another issue that has surfaced recently. WDS is not aware of some special "virtualized" folders on Windows for x64. This means that at the moment the results will - to some extent - be inaccurate for those platforms. This is being fixed for the next release. // Oliver Alright, for any readers of this post. There is another issue that has surfaced recently. WDS is not aware of some special “virtualized” folders on Windows for x64. This means that at the moment the results will - to some extent - be inaccurate for those platforms. This is being fixed for the next release.

// Oliver

]]> Comment on <Unknown> again … by romeojk http://blog.windirstat.info/20070321/unknown-again/#comment-10293 romeojk Thu, 05 Jun 2008 19:17:01 +0000 http://blog.windirstat.info/20070321/unknown-again/#comment-10293 I had a similar problem: 150 gig hardrive in a T61 Lenovo thinkpad. unknown space was at 115 gig's. My machine was running into trouble. I went to the ThinkVantage>system backup and restore>Advanced, and deleted all but the most recent backup...nothing changed (took a few hours). Then I went in and deleted the most recent backup (it said it was about 7 gigs), and shazam!!...bingo!! the unknown space went away and my machine is back to normal. Thank you so much for this site, I found it doing a search on google. I really think it was just the last backup/restore that was done and something went wrong with it to fill everything up, my machine was running fine until around when this backup occurred about 3 weeks ago. Thanks again so much, I really appreciate the help. I had a similar problem: 150 gig hardrive in a T61 Lenovo thinkpad. unknown space was at 115 gig’s. My machine was running into trouble. I went to the ThinkVantage>system backup and restore>Advanced, and deleted all but the most recent backup…nothing changed (took a few hours). Then I went in and deleted the most recent backup (it said it was about 7 gigs), and shazam!!…bingo!! the unknown space went away and my machine is back to normal.

Thank you so much for this site, I found it doing a search on google.
I really think it was just the last backup/restore that was done and something went wrong with it to fill everything up, my machine was running fine until around when this backup occurred about 3 weeks ago.

Thanks again so much, I really appreciate the help.

]]> Comment on Poll about the future of WinDirStat by fowl http://blog.windirstat.info/20080427/poll-about-the-future-of-windirstat/#comment-10281 fowl Wed, 04 Jun 2008 04:18:27 +0000 http://blog.windirstat.info/20080427/poll-about-the-future-of-windirstat/#comment-10281 Oh if it's faster, I'm all for it! (need an excuse to load a 64-bit on this box anyway... :P) Oh if it’s faster, I’m all for it!

(need an excuse to load a 64-bit on this box anyway… :P)

]]> Comment on <Unknown> again … by Oliver http://blog.windirstat.info/20070321/unknown-again/#comment-10277 Oliver Mon, 26 May 2008 09:19:03 +0000 http://blog.windirstat.info/20070321/unknown-again/#comment-10277 Hi, there could be one reason only, that I can imagine here: sparse files. NTFS offers to create totally or partially sparse files where the contents will be filled in over time. This means that not all the space is occupied when this sparse file is created. Depending on the tools you use, it will either show the real size on disk or the one that is reserved. // Oliver PS: Everything else would boil down to corruption of the file system. In this case run CHKDSK. Hi,

there could be one reason only, that I can imagine here: sparse files. NTFS offers to create totally or partially sparse files where the contents will be filled in over time. This means that not all the space is occupied when this sparse file is created. Depending on the tools you use, it will either show the real size on disk or the one that is reserved.

// Oliver

PS: Everything else would boil down to corruption of the file system. In this case run CHKDSK.

]]> Comment on <Unknown> again … by feeblemind_99 http://blog.windirstat.info/20070321/unknown-again/#comment-10276 feeblemind_99 Mon, 26 May 2008 02:44:07 +0000 http://blog.windirstat.info/20070321/unknown-again/#comment-10276 hi oliver, i have an HP dv2730tx laptop run in vista home OS with 250gb hard drive. i have my drives partition plus it has another 12GB recovery. So all in all i have 3 partitions, my C: and D: drives have equal spaces. my problem is, when i look in the windows explorer and see the bar of how much space is still free, it says 63.0gb of 112gb. but i know it could not be because only few programs are installed in my laptop, when i go inside my C: and selected all the folders then right click --> properties, only 20GB are used. I even used windirstat and it also produces the same result 20GB used, i wonder where does the remaining 30++Gb go? thanks hi oliver,

i have an HP dv2730tx laptop run in vista home OS with 250gb hard drive.
i have my drives partition plus it has another 12GB recovery. So all in all i have 3 partitions, my C: and D: drives have equal spaces.
my problem is, when i look in the windows explorer and see the bar of how much space is still free, it says 63.0gb of 112gb. but i know it could not be because only few programs are installed in my laptop, when i go inside my C: and selected all the folders then right click –> properties, only 20GB are used. I even used windirstat and it also produces the same result 20GB used, i wonder where does the remaining 30++Gb go?

thanks

]]> Comment on Poll about the future of WinDirStat by Oliver http://blog.windirstat.info/20080427/poll-about-the-future-of-windirstat/#comment-10275 Oliver Wed, 21 May 2008 00:24:15 +0000 http://blog.windirstat.info/20080427/poll-about-the-future-of-windirstat/#comment-10275 Good point, it might be additional hassle indeed. But I'll decide after actually checking the performance differences. I can imagine that particular operations would be faster natively. Good point, it might be additional hassle indeed. But I’ll decide after actually checking the performance differences. I can imagine that particular operations would be faster natively.

]]> Comment on Poll about the future of WinDirStat by fowl http://blog.windirstat.info/20080427/poll-about-the-future-of-windirstat/#comment-10274 fowl Tue, 20 May 2008 10:15:14 +0000 http://blog.windirstat.info/20080427/poll-about-the-future-of-windirstat/#comment-10274 I don't see the point of a x64 release, there are api's to allow 32bit apps to see an unvirtulised view of the filesystem. A 64bit build seems an unnecessary complication for both you and the potential downloader. Oh and awesome app btw! Looking forward to see how you deal with the hardlink problem. I don’t see the point of a x64 release, there are api’s to allow 32bit apps to see an unvirtulised view of the filesystem.

A 64bit build seems an unnecessary complication for both you and the potential downloader.

Oh and awesome app btw!

Looking forward to see how you deal with the hardlink problem.

]]> Comment on Poll about the future of WinDirStat by jimmy http://blog.windirstat.info/20080427/poll-about-the-future-of-windirstat/#comment-10262 jimmy Thu, 08 May 2008 01:28:00 +0000 http://blog.windirstat.info/20080427/poll-about-the-future-of-windirstat/#comment-10262 You could do a fileid lookup, those that are under winsxs with a linkcount > 1 could have other links hidden. If only they'd hardlinked the "real" copy and junctioned the others it would be a bit easier. AV/backup apps would've hit issues tho... Great app - glad to see you're continuing to refine it. Thx much. You could do a fileid lookup, those that are under winsxs with a linkcount > 1 could have other links hidden.
If only they’d hardlinked the “real” copy and junctioned the others it would be a bit easier. AV/backup apps would’ve hit issues tho…

Great app - glad to see you’re continuing to refine it. Thx much.

]]> Comment on Poll about the future of WinDirStat by Oliver http://blog.windirstat.info/20080427/poll-about-the-future-of-windirstat/#comment-10260 Oliver Wed, 07 May 2008 23:39:41 +0000 http://blog.windirstat.info/20080427/poll-about-the-future-of-windirstat/#comment-10260 So you suggest hiding everything outside that place? What about MKLINK and other tools which I like to use to create hardlinks (e.g. DFHL)? Those hardlinks will be hidden as well. I think you certainly have a point here, but they shouldn't be hidden either way. Instead WDS should handle this properly. So I'll work on this. There is another problem on 64bit, btw, which prevents it from seeing the "redirected" files (such as those under system32), causing wrong results on any Win64. So you suggest hiding everything outside that place? What about MKLINK and other tools which I like to use to create hardlinks (e.g. DFHL)? Those hardlinks will be hidden as well.

I think you certainly have a point here, but they shouldn’t be hidden either way. Instead WDS should handle this properly. So I’ll work on this. There is another problem on 64bit, btw, which prevents it from seeing the “redirected” files (such as those under system32), causing wrong results on any Win64.

]]> Comment on Poll about the future of WinDirStat by jimmy http://blog.windirstat.info/20080427/poll-about-the-future-of-windirstat/#comment-10259 jimmy Wed, 07 May 2008 22:00:38 +0000 http://blog.windirstat.info/20080427/poll-about-the-future-of-windirstat/#comment-10259 For the most part tho, the file under \winsxs is the "real" file on Vista. Toggling to hide hardlinks then would hide hardlinks not under that path. For the most part tho, the file under \winsxs is the “real” file on Vista. Toggling to hide hardlinks then would hide hardlinks not under that path.

]]>