File size question

[northcat_8]

I use IC7 to create PDI files. My file sizes are always much smaller than being reported, for example, I have backed up several DVDs and after using PDI2ISO windows reports the files size in details mode as being 4,128,680 KB but in my status bar at the bottom it reports teh size as 3.93 GB. I have already burnt this DVD to disc and checked it and it shows in the properties as being 3.93 GB.

So my question:

Is there a definitive way to accurately predict the difference?

I have used ICsettings in accordance with Mister X's webpage, I also enable my "OK" button no matter what the file size. Last night I backed up another DVD and windows reports the file size to be 4,459,840 KB but the properties window reports the size as 4.25 GB and this leads me to my quandry as one of these sizes is great and the other is a coaster.

The difference seems to be about .2 GB consistently. Is that a reliable number across the board?

[Karate Media]

The inconsistancy is probably due to the fact that a gig ain't always a gig -- that's why DVDs both do and don't hold 4.7 GBs of information. They DO hold 4,700,000,000 bytes (is that enough zeros?), but in terms of semantics, it is only considered 4.38 GBs.

A KB is really 1024 bytes, a MB is really 1024 KBs and a GB is really 1024 MBs -- hence the discrepency.

[northcat_8]

I understand a 1 KB = 1024 bytes but I was wondering why if I open the folder containing the ISO file and I use detail viewing mode to list my files, their size, modification date, etc. it gives the larger size but in the status bar at the bottom of the window it gives the smaller size or if I right click and go to properties it will report the smaller size.

And am I wrong to assume that if the smaller size will fit on a DVD-R disc that it's ok to go ahead and burn it? Because that is the correct size?

[Karate Media]

From what I can tell from your information, the numbers are equal -- it's just semantics:

"windows reports the file size to be 4,459,840 KB but the properties window reports the size as 4.25 GB" (from your orig. post)

4,459,840 divided by 1024 divided by 1024 = 4.253234

It's just that one window is reporting it in terms of KBs and one window is reporting it in GBs. It's the same size regardless -- its sorta like 4 cups = 1 quart; two different units of measurement, but it's the same size.

As long as the file is 4.38 GB (using our "1024" measurement) or 4,700,000 KBs (roughly -- I don't feel like doing the math again), then you are good to go.

[northcat_8]

I'm retarded.

That makes sense...Thanks.

[northcat_8]

Karate Media,

Thanks again, since I started adding up the KB myself and using Instant copy tools to enable the "OK" button, I typically make sure that my IC7 reports a size around 4.4-4.5 GB before I start it.

The way you explained it was much easier than anything else I read.

[Karate Media]

Glad I could help, 'cat. All in a day's work...uh...of not working at work but instead working on math problems in a message board...


But wait...when you say 4.5 GB, do you mean the "computer" definition of GB or do you mean 4,500,000 KB? Because the first one shouldn't fit on a DVD but the second one will.

4,600,000 KB is (roughly) the max KB size that will typically fit on a DVD, and 4.38 GB is (roughly) the max GB size that will fit.

So, whatcha mean when you say "4.5 GB" -- and if we're talking "computer-definition" GB, then are you succesfully burning them to DVD?

If that made any sense (it's early in the day for me!), please answer...

[Karate Media]

Sorry for the bump post, but another question came to mind (Again, I'm going on five hours of sleep, so bear with me):

Did you say that you are now checking the math by hand? That status bar you mentioned in your first post had the the correct size in GB, so as long as you keep your disc size under 4.38 GB, you'll be fine.

Or am I just totally missing what you said?

KM
"Interrupting my train of thought/Lines of longitiude and latitude"

[ember]

I had problems whereby IC7 converted to 4.31GB (in the green zone) then told me it was 4.40GB when I tried to burn!

The update sorted out the problem.