File Size incorrect

abrite

I'm evaling your product. Have been liking it until I wasted a couple of hours trying to find out why one of my hard drives was reporting more space being used than what was registering in your file finder.

Some files show N/A and they are larger than 8Gb. Some files had invalid values. In file finder one was listed with 970.6 Mb, when in reality it was 20.9 Gb. Another in File Finder was 1.2Gb, but in reality was 37.2 Gb. There were a few others.

I can handle a few megabytes discrepancy, but 63.6 Gb discrepancy had me worried. I assumed the sizes that were reported by file finder were fairly accurate and that's why I lost all that time. :(

I did find there was an update and am now using v 1.5.2.342. But that just doesn't report any sizes at all now. I either get N/A's or a blank column entry.

tullik

I suppose you specified *.* as the "Files to Find" and a whole volume (C:\ for example) in the Search in tab ...

Also try this:

1. In the File Finder tool Options tab, make sure the 2nd and 3rd boxes are not checked.

2. When the File Finder results window shows, click on the columns menu and make sure Size is checked.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

I have never seen results like you describe in any PT version going back to 1.4.1... -- I don't believe PT does anything fancy, just uses a windows API to ask how big is the file ...

I cross-checked some of the sizes -- asked FF to show all flies on K:\ larger than 100 MB -- it showed 28 -- I picked one ...

1. File Finder showed 349.8 MB

2. Win explorer showed 358,162 KB

3. Properties showed 349 MB (366,757,888 bytes)

... arithmetic time ...

1. 349.8 * 1024 = 358,195.2 KB

2. 358,162 * 1 = 358,162 KB

3. 366,757,888 / 1024 = 358,162 KB

33.2 / 358,162 = 0.0000926, or 0.009% -- not real significant.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

On the other hand, if you really have files of 20 GB to 40 GB in size, you may have exceeded the capacities of the arithmetic routines implemented in PT -- the developer would know ...

abrite

First I used *.tib - Acronis TrueImage Backup files. Since these are image backups they are very large. Here's a list of the files and their sizes on the hard drive in question:

Phase_3_22.tib 213,643 KB

Phase_3_15.tib 274,227 KB

Phase_3_21.tib 324,490 KB

Phase_3_20.tib 688,037 KB

Phase_3_3.tib 810,997 KB

Phase_3_24.tib 837,157 KB

Phase_3_12.tib 871,199 KB

Phase_3_11.tib 978,764 KB

Phase_3_7.tib 1,107,340 KB

Phase_3_8.tib 1,127,824 KB

Phase_3_16.tib 1,166,651 KB

Phase_3_18.tib 1,193,062 KB

Phase_3_17.tib 1,688,272 KB

Phase_3_10.tib 1,803,458 KB

Phase_3_9.tib 3,004,857 KB

Phase_3_2.tib 3,879,504 KB

Phase_3_5.tib 8,692,316 KB

Phase_3_4.tib 15,490,901 KB

Phase_3_13.tib 19,769,850 KB

Phase_3_6.tib 21,965,366 KB

Phase_3_23.tib 23,523,444 KB

Phase_3_.tib 32,526,311 KB

Phase_3_19.tib 39,021,659 KB

DriveH_Home_2006-06-16.tib 40,686,449 KB

Nothing else in your response applies. Here's a section of the window of what I get when using file finder:

Oh well - too much work to paste an image!

tullik

I think PT only supports windows files. I'm surprised using it against an imaging technology even partially worked. PT probably doesn't apply at all for what you are attempting, but should work fine against a restored volume.

What does windows explorer do with the image drive? The developer said in a post somewhere here that if win explorer can do a thing, then PT should probably be able do it.

tullik

I found this on an Acronis page:

"You can view your images directly from Windows Explorer by assigning a virtual drive letter to one of them — the "drive" is read-only too, so the original archive is always protected. Finally, the program includes the Acronis Migrate Easy tool, which can clone one drive's contents to another and even prepare a disk for that purpose."

Have you tried the underlined part?

abrite

Thanks for the follow-up and checking the Acronis site. However, there seems to be some miscommunication here.

I'm trying to view the files as Windows files. I don't need to know the contents of the files for what I'm doing. My problem is that I have a lot of these large image files that I need to reorganize. I wanted to know how much room they're taking up on my drives and I wanted to know how free room I have on all my drives so I can:

1) Determine which image files I can keep and which ones I need to delete.

2) Relocate the image files in such a way to make maximum use of my NTFS formatted drives (all 4 of them)

3) Determine how long I can make incremental image backups before I have to delete and start over.

I have a lot of math to do based on file and drive sizes. But I can't do it with bad size info.

All other tools I use to get file and drive info (which is limited), works just fine. That's how I found the problem with PowerTools. I was hoping PowerTools would make this task easier for me.

tullik

abrite wrote
Thanks for the follow-up and checking the Acronis site. However, there seems to be some miscommunication here.

I'm trying to view the files as Windows files. I don't need to know the contents of the files for what I'm doing. My problem is that I have a lot of these large image files that I need to reorganize. I wanted to know how much room they're taking up on my drives and I wanted to know how free room I have on all my drives so I can:

1) Determine which image files I can keep and which ones I need to delete.

2) Relocate the image files in such a way to make maximum use of my NTFS formatted drives (all 4 of them)

3) Determine how long I can make incremental image backups before I have to delete and start over.

I have a lot of math to do based on file and drive sizes. But I can't do it with bad size info.

All other tools I use to get file and drive info (which is limited), works just fine. That's how I found the problem with PowerTools. I was hoping PowerTools would make this task easier for me.

Thanks for explaining your objectives. PT File Finder would indeed make that task easier, and if windows explorer (or search) can see the files, then PT should also.

Maybe the problem is as simple as a bug in a calculation or format conversion for large numbers.

Please document the exact differences so the developer will have a place to start -- something like the screenshots below for your *.tib files.