Jump to content

Need help with results of first dual-layer burn


bloomcounty

Recommended Posts

Hi,

 

I just did my first dual-layer burn and I have a couple questions:

 

1. I noticed that both the Buffer and Device Buffer were at 100% the whole time the burn was happening. Is this normal? Or is there some setting I need to adjust?

 

Here is the log:

 

I 18:24:42 ImgBurn Version 2.2.0.0 started!
I 18:24:42 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)
I 18:24:42 Total Physical Memory: 522,416 KB  -  Available: 228,848 KB
W 18:24:42 Drive D:\ (FAT32) does not support single files > 4 GB in size.
I 18:24:42 Initialising SPTI...
I 18:24:42 Searching for SCSI / ATAPI devices...
I 18:24:42 Found 1 DVD?RW/RAM!
I 18:29:00 Operation Started!
I 18:29:00 Building Image Tree...
I 18:29:00 Checking Directory Depth...
I 18:29:00 Calculating Totals...
I 18:29:01 Preparing Image...
I 18:30:29 Using Layer Break LBA: 1688124 -> 1688128 (VTS_06, PGC: 1, Chapter: 11, Cell: 23, Vob/Cell ID: 2/1, Time: 00:53:10, SPLIP: No)
I 18:30:29 Checking Path Length...
I 18:30:29 Image Size: 6,706,790,400 bytes
I 18:30:29 Image Sectors: 3,274,800
I 18:30:29 Operation Successfully Completed! - Duration: 00:01:28
I 18:30:36 Operation Started!
I 18:30:36 Building Image Tree...
I 18:30:36 Checking Directory Depth...
I 18:30:36 Calculating Totals...
I 18:30:36 Preparing Image...
I 18:30:47 Using Layer Break LBA: 1688124 -> 1688128 (VTS_06, PGC: 1, Chapter: 11, Cell: 23, Vob/Cell ID: 2/1, Time: 00:53:10, SPLIP: No)
I 18:30:47 Checking Path Length...
I 18:30:47 Image Size: 6,706,790,400 bytes
I 18:30:47 Image Sectors: 3,274,800
I 18:30:47 Operation Successfully Completed! - Duration: 00:00:11
I 18:33:49 Operation Started!
I 18:33:49 Building Image Tree...
I 18:33:49 Checking Directory Depth...
I 18:33:49 Calculating Totals...
I 18:33:49 Preparing Image...
I 18:34:21 Using Layer Break LBA: 1688124 -> 1688128 (VTS_06, PGC: 1, Chapter: 11, Cell: 23, Vob/Cell ID: 2/1, Time: 00:53:10, SPLIP: No)
I 18:34:21 Checking Path Length...
I 18:34:21 Image Size: 6,706,790,400 bytes
I 18:34:21 Image Sectors: 3,274,800
I 18:35:06 Operation Successfully Completed! - Duration: 00:01:16
I 18:35:06 Operation Started!
I 18:35:06 Source File: -==/\/[bUILD IMAGE]\/\==-
I 18:35:06 Source File Sectors: 3,274,800 (MODE1/2048)
I 18:35:06 Source File Size: 6,706,790,400 bytes
I 18:35:06 Source File Volume Identifier: X3
I 18:35:06 Source File Application Identifier: IMGBURN V2.2.0.0 - THE ULTIMATE IMAGE BURNER!
I 18:35:06 Source File Implementation Identifier: ImgBurn
I 18:35:06 Source File File System(s): ISO9660, UDF (1.02)
I 18:35:06 Destination Device: [1:0:0] HL-DT-ST DVDRAM GSA-4084N KQ09 (E:) (ATA)
I 18:35:06 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x)
I 18:35:06 Destination Media Sectors: 4,173,824
I 18:35:06 Write Mode: DVD
I 18:35:06 Write Type: DAO
I 18:35:06 Write Speed: 2.4x
I 18:35:06 Link Size: Auto
I 18:35:06 Test Mode: No
I 18:35:06 BURN-Proof: Enabled
W 18:35:06 DeviceIoControl(FSCTL_LOCK_VOLUME) Not Supported! - Update your motherboard / IDE drivers!!!
I 18:35:06 Optimal L0 Data Zone Capacity: 1,688,128
I 18:35:06 Optimal L0 Data Zone Method: IFO Cell Boundary, 'SPLIP' Flag Not Set
I 18:36:06 Filling Buffer... (20 MB)
I 18:36:07 Writing LeadIn...
I 18:36:12 Writing Image...
I 18:36:12 Writing Layer 0... (LBA: 0 - 1688127)
I 18:53:43 Writing Layer 1... (LBA: 1688128 - 3274799)
I 19:10:14 Synchronising Cache...
I 19:10:15 Closing Track...
I 19:10:21 Finalising Disc...
I 19:12:39 Image MD5: db7a5d4093e2109411d2c29613b93dc6
I 19:12:39 Operation Successfully Completed! - Duration: 00:37:33
I 19:12:39 Average Write Rate: 3,209 KB/s (2.3x) - Maximum Write Rate: 3,387 KB/s (2.4x)
I 19:12:39 Cycling Tray before Verify...
W 19:12:45 Waiting for device to become ready...

 

2. What does this warning mean?

W 18:24:42 Drive D:\ (FAT32) does not support single files > 4 GB in size.

 

3. What does this warning mean?

W 18:35:06 DeviceIoControl(FSCTL_LOCK_VOLUME) Not Supported! - Update your motherboard / IDE drivers!!!

 

4. And should my burn have turned out okay despite these warnings and/or my question in #1?

 

Thanks!

Link to comment
Share on other sites

#1 buffers being around 100% is a great thing ,means that the data is being constantly fed to your burner

 

 

#2 thats the file size limit when using FAT32 file system ,you dont have the limit when using NTFS (default winXP) ,if you want to convert to NTFS you can do so without losing any data ,you can Google convert fat 32 to ntfs for specifics

 

#3 thats self explanatory update the drivers ,go to the MB manufacturers website and download the latest ones for your MBoard ,when the drive is not locked then the possibility of some other program accessing the drive and ruining the burn

 

#4 from looking at your log yes the burn turned out fine ,it will play on any standalone that supports playback of Dual Layer media ,for more compatibility you can booktype the DL+R's to dvd rom if your burner supports it .Imgburn main window click on the little book icon in the lower right corner , select the LG tab and "change for DL media" and new setting "DVD Rom "

Link to comment
Share on other sites

#2 thats the file size limit when using FAT32 file system ,you dont have the limit when using NTFS (default winXP) ,if you want to convert to NTFS you can do so without losing any data ,you can Google convert fat 32 to ntfs for specifics

 

I'm using Windows XP, so why wouldn't my default be this NTFS?

 

Is there any reason that the FAT32 file system (if that is, indeed, what I've got) isn't good enough to back-up discs? Are there generally any single files on a movie dvd that are larger than 4GB?

 

#3 thats self explanatory update the drivers ,go to the MB manufacturers website and download the latest ones for your MBoard ,when the drive is not locked then the possibility of some other program accessing the drive and ruining the burn

 

How can I tell what MB my laptop has? And how do I ensure I download the correct update/driver? Will doing so mess up any other programs or potentially cause any other problems?

 

#4 from looking at your log yes the burn turned out fine ,it will play on any standalone that supports playback of Dual Layer media ,for more compatibility you can booktype the DL+R's to dvd rom if your burner supports it .Imgburn main window click on the little book icon in the lower right corner , select the LG tab and "change for DL media" and new setting "DVD Rom "

 

Do I need to have a blank in the drive to do this? And what does doing this change exactly? Will it have any effect on how my drive operates when not using ImgBurn (like watching dvds, or burnig data, etc.). Or is it only specific to ImgBurn. Do I want to set it for both SL and DL?

 

Thanks for the help!

Link to comment
Share on other sites

I'm using Windows XP, so why wouldn't my default be this NTFS?

Ask Microsoft. :)

 

Is there any reason that the FAT32 file system (if that is, indeed, what I've got) isn't good enough to back-up discs? Are there generally any single files on a movie dvd that are larger than 4GB?
The files themselves won't be but the dual-layer ISO you create will be.

 

There's really no reason to use FAT32 these days....... unless you're paranoid about losing data and don't keep backups.

 

To convert your drive - open a command prompt (not Start/Run) and type this then hit enter:

 

convert d: /fs:ntfs

 

How can I tell what MB my laptop has? And how do I ensure I download the correct update/driver? Will doing so mess up any other programs or potentially cause any other problems?

 

Head to Google and type in the model number of your laptop.

 

Do I need to have a blank in the drive to do this? And what does doing this change exactly? Will it have any effect on how my drive operates when not using ImgBurn (like watching dvds, or burnig data, etc.). Or is it only specific to ImgBurn. Do I want to set it for both SL and DL?

 

No.

 

Makes the disk compatible with DVD players.

 

No.

 

Other programs also need to set the booktype correctly otherwise nothing would work. With ImgBurn it's just more obvious.

 

Only for +R media.

Link to comment
Share on other sites

The files themselves won't be but the dual-layer ISO you create will be.

 

There's really no reason to use FAT32 these days....... unless you're paranoid about losing data and don't keep backups.

 

I'm paranoid in general! :) Since the process is irreversible, and I don't plant on burning ISOs for dual-layer or single-layer (I'm burning the files directly, as my research has shown me there's not reason not to nowadays), and I'm not really a "computer person" per se (meaning I don't have a bunch of crazy stuff going on with my computer -- i.e. I just mainly rip/burn dvds, use MS Word/Excel, convert music to mp3s, burn cds/dvds, and use Photoshop and Dreamweaver, it doesn't sound like I even need to consider this until it actually pops up for some reason. Does that seem a logical plan?

 

I tried looking up the motherboard, but couldn't find anything... My laptop says it's a Presario V5000, but it's supposed to be a V5310us (something I need to verify with HP).

 

The DVD-ROM thing: It won't let me change anything, but under the device tab, it says DVD-ROM in ImgBurn, so is that all set already?

 

Thanks for the help!

Edited by bloomcounty
Link to comment
Share on other sites

it doesn't sound like I even need to consider this until it actually pops up for some reason. Does that seem a logical plan?

 

Sounds logical to me. :)

 

I tried looking up the motherboard, but couldn't find anything... My laptop says it's a Presario V5000, but it's supposed to be a V5310us (something I need to verify with HP).
Belarc Advisor might be able to help you here as it should list the model number for your motherboard as well as stats on various other bits. Download it from http://www.belarc.com/free_download.html

 

The DVD-ROM thing: It won't let me change anything, but under the device tab, it says DVD-ROM in ImgBurn, so is that all set already?

 

I assume so. You didn't post the entire log which makes it impossible to tell.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.