Problem Creating Disc Image

[hypoxic]

I'm trying to create a disc copy to save as a backup of a disc that contains my home movies. I use the "create disc copy" command under the file menu and everything seems to go ok but when I check the created iso file there is a file called xxxx.iso which is somewhere around 3.6 gigs and another file called xxxx.oo1 that contains around 500 megs. The combined size of these two files equals the total size of the disc I'm imaging. I've tried this with several different disc and roxio always seems to split the image file at the 3.6 gig size. The .001 file varies in size depending on the size of the disc I'm trying to image. Is there a size limit to the iso file that roxio can create? Is there a way to produce a single iso file with all the disc data in one iso file?

[Brendon]

Hello,

 

It looks like the destination disk that you're creating the .ISO on must be formatted using the FAT32 file system.

The largest file which can be saved in FAT32 is just under 4 GiB - it's a file system limitation - so the software splits it into an .ISO as big as it can save, and a .001 file which holds the rest.

 

e.g. I have a DVD which Windows shows as having 4,408,016,896 bytes of user data, and I'm copying it with Disc Copier 6.

On a FAT32 disk it saves the ISO at 4,193,280 KB [4,293,918,720 bytes or 3.99 GB] and the .001 file 11,424 KB [108 MB or 114,098,176 bytes]

On an NTFS disk there's only one file, the ISO at 4,304,704 KB [4,408,016,896 bytes or 4.10 GB]

 

I hope that explains what's happening. I've quoted the various figures because they are what Windows told me, and they show how confusing things get when you use different units for the same thing.

 

 

 

 

.

[hypoxic]

Thanks for the reply Brendon. I checked the disc properties for my hard drive and it is definitely an NTSF drive. I have other files on the drive larger that 4 gigs so I don't think that's the problem. Incedentally, it's always splitting the file at 3,652,200 KB. Any other thoughts or ideas?

[gi7omy]

I've a strange feeling (I haven't used ECD6 for that long) but a spanned backup does have a high overhead (it needs to have the progrem to restore - which implies a boot sector, a bootable app to actually start the working - that may account for the 'loss' of space

 

I could be wrong - I'm open to correction on tat

[Larry]

As I recall, v6 did some odd things at times when creating image files and truncating it into the extra .001 file. I remember running into it myself on occasion back in the day. Not too surprising I think since it was the first version with video abilities.

 

What you could try is the free Imgburn ( here - link ) utility to see if it can create an image file that's not truncated. That would help narrow it down to either your system or the software.

[Brendon]

Thanks for the reply Brendon. I checked the disc properties for my hard drive and it is definitely an NTSF drive. I have other files on the drive larger that 4 gigs so I don't think that's the problem. Incedentally, it's always splitting the file at 3,652,200 KB. Any other thoughts or ideas?

That's 3,739,852,800 bytes. I don't know anything that's significant about that number.

 

It isn't a 'spanned backup' it's just a disc copy, so the concern about restore program overhead doesn't apply.

 

My Disc Copier 6 doesn't split the ISO at all on an NTFS drive under XP, although it does split it where I told you on a FAT32 drive. I'd be very interested to know why your system is splitting the output file, although I don't know what is doing it at the moment.

 

However, does it matter? You are copying the disc to ISO to back it up, and the split ISO will behave exactly the same as a single-file ISO when you burn it back to plastic - try it and see. Are you worrying about nothing?

 

 

Brendon