Drive Utility

[azmanar]

Hi,

I built a small utility that lists All My PC Drives including HDD, CD-Rom, Removable and Network Drive. On Select, it gives info on the Drive. On Double Click, opens an Explorer Window of that Drive.

Uses Drive.Enumerate, Drive.GetType, Drive.GetSize and Drive.GetFreeSpace to generate info on Drives. Pass em to a ListBox.

The problem is I can't get FULL SIZE using Drive.GetSize of a CD loaded on the drive. Instead it outputs the USED SPACE of the CD. Despite this anomaly, the utility is working without fail. (attached)

How do I get the Full Size of a CD?

[azmanar]

Anyone .......?

[Gabis]

well, if im not mistaken, unless they are CD-RW's once they have data on them the size only shows as how much data was written to them. I havent messed with a CD-RW in a very long time though, so im not sure how the relevant size data works if that is indeed what you are dealing with.

[azmanar]

well, if im not mistaken, unless they are CD-RW's once they have data on them the size only shows as how much data was written to them. I havent messed with a CD-RW in a very long time though, so im not sure how the relevant size data works if that is indeed what you are dealing with.

Generally, CD-R size can be between 700 to 800 Mb, depending on the make and quality. So I just need to know the size used against the full capacity of the CD-R. I need to apply the same to CD-RW ( now has Overburning option ) and DVD too.

Then I can calculate the Free Space and the Percent used, to be displayed on the APP for the user.

[rhosk]

The problem is I can't get FULL SIZE using Drive.GetSize of a CD loaded on the drive.

How do I get the Full Size of a CD?
This is normal OS behaviour. Do a properties check on any CD in explorer (file manager). It will only give you what was burned to the CD and it will always be 0 bytes remaning.

[azmanar]

This is normal OS behaviour. Do a properties check on any CD in explorer (file manager). It will only give you what was burned to the CD and it will always be 0 bytes remaning.

Ron,

Thanks so much for the info. Helps me stop wasting my time from pursuing this any further.


PS: For NLEs, we've decided to go for 64bit dual processor AMD machines. We're skipping Intel totally.

[Gabis]

heh yeah thats what i was trying to say rhosk, you just worded it a helluva lot better :)

and yes, AMD Dual-Core 64's are sweeeeeeeet. IMO Intel has missed the boat on the super-premium CPU market, at least for now.

[azmanar]

and yes, AMD Dual-Core 64's are sweeeeeeeet. IMO Intel has missed the boat on the super-premium CPU market, at least for now.

AMD won because of T.S.C. :
1. Lower Temperature
2. Higher Speed
3. Lower Cost