Jump to content

Yet more coasters


Groundrush

Recommended Posts

Can you confirm my suspicions that the media I'm attempting to burn is no good for my drive. Verbatim +R are my current choice and my driver is up to date firmware wise yet i still produce coasters...LoL. This was my first attempt using ImgBurn which in it's self seem quite straight forward, but the results were identical over 4 runs. I've tried samples of all brands (excluding Taiyo Youden) and the mass of coaster speak for themselves.

This is the last log and thanks in advance.

 

I 22:31:40 ImgBurn Version 1.2.0.0 started!

I 22:31:40 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

I 22:31:40 Initialising SPTI...

I 22:31:40 Searching for SCSI / ATAPI devices...

I 22:31:40 Found 2 DVD-ROMs and 1 DVD+RW!

I 22:34:38 Operation Started!

I 22:34:38 Source File: C:\GARFIELD_THE_MOVIE_D1.ISO

I 22:34:38 Source File Sectors: 2,285,870 (MODE1/2048)

I 22:34:38 Source File Size: 4,681,461,760 bytes

I 22:34:38 Source File Implementation Identifier: DVD Shrink

I 22:34:38 Destination Device: [1:0:0] DVD+RW RW8160 1.08 (D:) (ATA)

I 22:34:38 Destination Media Type: DVD+R (Disc ID: MCC-003-00) (Speeds: 2.4x)

I 22:34:38 Destination Media Sectors: 2,295,104

I 22:34:38 Write Mode: DVD

I 22:34:38 Write Type: DAO

I 22:34:38 Write Speed: 2.4x

I 22:34:38 Link Size: Auto

I 22:34:38 Test Mode: No

I 22:34:38 BURN-Proof: Enabled

I 22:34:38 Filling Buffer...

I 22:34:40 Writing LeadIn...

W 22:35:17 Failed to Write Sectors 0 - 31 - Unknown (0x91, 0xC1)

W 22:35:17 Retrying (1 of 20)...

W 22:35:38 Retry Failed - Unknown (0x91, 0xC1)

W 22:35:38 Retrying (2 of 20)...

W 22:36:00 Retry Failed - Unknown (0x91, 0xC1)

W 22:36:00 Retrying (3 of 20)...

W 22:36:21 Retry Failed - Unknown (0x91, 0xC1)

W 22:36:21 Retrying (4 of 20)...

W 22:36:42 Retry Failed - Unknown (0x91, 0xC1)

W 22:36:42 Retrying (5 of 20)...

W 22:37:04 Retry Failed - Unknown (0x91, 0xC1)

W 22:37:04 Retrying (6 of 20)...

W 22:37:24 Retry Failed - Unknown (0x91, 0xC1)

W 22:37:24 Retrying (7 of 20)...

W 22:37:45 Retry Failed - Unknown (0x91, 0xC1)

W 22:37:45 Retrying (8 of 20)...

W 22:38:05 Retry Failed - Unknown (0x91, 0xC1)

W 22:38:05 Retrying (9 of 20)...

W 22:38:26 Retry Failed - Unknown (0x91, 0xC1)

W 22:38:26 Retrying (10 of 20)...

W 22:38:48 Retry Failed - Unknown (0x91, 0xC1)

W 22:38:48 Retrying (11 of 20)...

W 22:39:08 Retry Failed - Unknown (0x91, 0xC1)

W 22:39:09 Retrying (12 of 20)...

W 22:39:31 Retry Failed - Unknown (0x91, 0xC1)

W 22:39:31 Retrying (13 of 20)...

W 22:39:50 Retry Failed - Unknown (0x91, 0xC1)

W 22:39:50 Retrying (14 of 20)...

W 22:40:10 Retry Failed - Unknown (0x91, 0xC1)

W 22:40:10 Retrying (15 of 20)...

W 22:40:29 Retry Failed - Unknown (0x91, 0xC1)

W 22:40:29 Retrying (16 of 20)...

W 22:40:49 Retry Failed - Unknown (0x91, 0xC1)

W 22:40:49 Retrying (17 of 20)...

W 22:41:07 Retry Failed - Unknown (0x91, 0xC1)

W 22:41:07 Retrying (18 of 20)...

W 22:41:25 Retry Failed - Unknown (0x91, 0xC1)

W 22:41:25 Retrying (19 of 20)...

W 22:41:44 Retry Failed - Unknown (0x91, 0xC1)

W 22:41:44 Retrying (20 of 20)...

W 22:42:02 Retry Failed - Unknown (0x91, 0xC1)

E 22:43:25 Failed to Write Sectors 0 - 31 - Unknown (0x91, 0xC1)

I 22:43:25 Synchronising Cache...

I 22:43:26 Closing Track...

I 22:43:27 Finalising Disc...

E 22:43:28 Failed to Write Image!

E 22:43:28 Operation Failed! - Duration: 00:08:50

I 22:43:28 Average Write Rate: N/A - Maximum Write Rate: N/A

Link to comment
Share on other sites

That media is rated at 8x and yet your drive only sees it as 2.4x.

 

That immediately tells me your drive isn't able to support it fully (or at all).

 

Now might be a good time to upgrade your drive rather than trying to find media that it DOES work with. TY and MCC are both excellent media brands/dyes normally.

Link to comment
Share on other sites

Groundrush, not that there's any room for doubt, but I agree with LUK!

 

I recently had a similar experience where I received similar error messages (and not just with ImgBurn, but with other software applications claiming it was bad media that was causing the problem). Although DELL support (and I purposely use their name, so that others may learn from my mistakes) kept telling me it was the type of media I was using (mind you, I was using Yuden and MCC [Verbatim branded] media), I finally convinced them to replace my drive and now I am "back in business" (figuratively speaking, of course).

Edited by Flawless115
Link to comment
Share on other sites

Thanks guys, i think the problem is with my drive...!!!. I currently have my brothers external re-writer plugged in and it's humming like a humming thing. You are probably correct LUK, in that it's time to upgrade my drive so it ooks like it's time to hammer the plastic.......cheers

Link to comment
Share on other sites

Off topic slightly, I'm trying to increase my knowledge of how this all works and understand all things technical. I've posted the snapshot of DVDinfo and read the notes but could someone please take a couple of minutes and give me an idiots guide to deciphering the information below.....Thanks

dvdinfo6lf.png

Link to comment
Share on other sites

Erm... it got to 8x and then died.

 

Lots of weird ups and down until the 2gb marker, then it continued at 6x before messing up again.

 

Update to the YS0X firmware and try again.

 

You can see my scan of the same media type with that drive in the 'Drives and Media' forum.

 

Oh and it being on USB might be a factor - seeing as how CPU intensive USB is compared to methods of connectivity.

It's either CPU or other I/O that's killing the speed, or it's the disc quality and WOPC. It shouldn't be the disc though because MCC are normally pretty damn good! Let's hope the firmware update fixes the issue ;)

Link to comment
Share on other sites

Erm... it got to 8x and then died.

 

Thanks LUK...

 

Now that is what i call a simple idiot proof answer......LoL, call me nieve but you mention I/O and WOPC, could you please explain the definition of these abbreviations.

Link to comment
Share on other sites

I/O = Input Output - i.e. disc (hdd / cd / dvd) activity.

 

WOPC = Walking Optimal Power Calibration. This is where the drive constantly (frequently) checks the quality of the burn as it goes. If it finds the burn going a bit downhill, it'll slow it down and/or change the power of the laser to compensate.

Link to comment
Share on other sites

Again Thanks LUK, i got the YSOX firmware d/load but there is no install notes/file. Is there a definitive guide to flashing as I flashed my laptop a many months back and the process seemed rather complicated, but what I've read over the past couple of days seems even more so, with talk of "BOOT discs and DOS mode". I know this is ImgBurn forum but I would be most grateful for a " nudge" in the right direction. After browsing RPC 1's site and it's affiliates I'm none the wiser as to the whole process without the install notes/file.

Again in advance, any help is gratefully appreciated. :worthy:

Link to comment
Share on other sites

lol it's EASY now! Just run the file, ensure the correct drive is selected (easy if you only have 1 in the first place!) and then click 'start'.

 

 

A humble Thank You :blush:, i'm on it this very moment. I'll burn a test piece and check to see whether the Graphs differ a great deal, if not then it must be the " Stuff " you mentioned....Cheers

Link to comment
Share on other sites

dvdinfo20yv.png

 

 

 

This is the test burn results.....as you can see with the YSOX firmware, to me there seems less drop offs, or are there an equal amount but more evenly spaced....? it dropped off at 28% around the same as the previous burn so as LUK suggested it must be something other. I'm not complaining as I'm more than happy for a disc to be burnt in 10/12 minutes but I thought it only courteous to show you the results. :thumbup:

Link to comment
Share on other sites

If you have another disc to spare, use discovery mode.

 

As it doesn't burn a file, it will take one potential problem out of the equation.

 

The Buffers should be full 100% of the time. The only time the Device one drops off is when the WOPC stuff does it's little check. That should only last a second or two.

 

You've got about 400mb worth of slow burning in that graph, so you should be able to see if the buffers are going mad at any point.

Link to comment
Share on other sites

If you have another disc to spare, use discovery mode.

 

THANKS LUK.......

If it means i'll use a whole spindle to speed things up then i'm prepared to do just that :)

and you mention " discovery mode ", again forgive my ignorance, is this within ImgBurn....?

Link to comment
Share on other sites

Ok here we go......

 

This is the first burn done on Write, incidentally all non essential applications/processes running in the background were shut down....

 

welcometothejungle9op.png

 

 

This was the second burn done in Discovery mode (which blitzed it) in comparison...

 

http://img313.imageshack.us/img313/3230/we...ejungle28fn.png

 

 

The question is can each burn be done in " Discovery " mode, or is this just for trouble shooting purposes. If so how do you locate the ISO file to burn as on the second run when opening Discovery mode there was no means to navigate to the relevant folder, it just burned the disc without any input from me, except hit start.

 

 

Thanks to ALL for your time and patience in this matter...... :thumbup:

Link to comment
Share on other sites

Ah ok, my guess here then is that you're suffering from the windows caching problem. You machine can cope for a while and then it runs out of ram. That's when things slow down.

 

Discovery mode is identical (in what it does) to the normal write mode, except Write mode reads from a file and Discovery mode just uses fictitious data that I make up on the fly from within the program - as such, no file is ever read.

Link to comment
Share on other sites

Thanks LUK.

I'm running from my Laptop (512mb) ram and what with all the background stuff going on that makes sense. I'll just have to start using the Queue system and burn everything when i can afford to close all non essential apps/processes..... :D

Link to comment
Share on other sites

These are the results of todays foray. Although all burns have been successful since i snagged my brothers External drive. I'm confussed with what DVDinfo is showing me, in that i mean the 3 burns made today were carried out under the same conditions. Info from previous topics suggests a caching problem so I've shut down all non essential programs and background applications so very little is being used to slow down my Laptop. The only difference is that each burn was a different ISO file. What I'm asking is why do the 3 graphs not all look the same when basically the test bed was no different....?

 

 

burn14cs.png

 

 

burn28pe.png

 

 

burn34ry.png

Link to comment
Share on other sites

Ah ok, my guess here then is that you're suffering from the windows caching problem. You machine can cope for a while and then it runs out of ram. That's when things slow down.

LUK!,

 

Out of curiosity, is there any amount of RAM that will make this problem go away? I just bought an extra 512 MB of RAM the other day (now I have 1 GB total RAM), doubled the size of the paging file, and I am still experiencing the buffer underruns, just not as often and not as severe as before. My discs still come out fine (I'm assuming that's due to BURN-Proof), but it would be nice to go through an entire burn with full buffers. The writing speed slows down when my buffers are empty and my PC is trying to refill them.

Link to comment
Share on other sites

Ah ok, my guess here then is that you're suffering from the Windows caching problem. You machine can cope for a while and then it runs out of ram. That's when things slow down.

LUK!,

 

Out of curiosity, is there any amount of RAM that will make this problem go away? I just bought an extra 512 MB of RAM the other day (now I have 1 GB total RAM), doubled the size of the paging file, and I am still experiencing the buffer underruns, just not as often and not as severe as before. My discs still come out fine (I'm assuming that's due to BURN-Proof), but it would be nice to go through an entire burn with full buffers. The writing speed slows down when my buffers are empty and my PC is trying to refill them.

When I used to burn discs, the Buffer level would drop down to 0% 2-3 times per disc. Up to this point, I've assumed this was due to the Windows caching problem that preys on ImgBurn 1.2.0.0. To, hopefully, resolve it, I bought another 512MB of RAM. At first, I thought the problem was still there. I just ran a few "test" burns, and now I'm not quite sure I have a problem anymore.

 

I was advised to post a couple of Write speed Graphs to the forum to get feedback regarding my issue.

 

Here's the process I went through:

 

I created two images. I burned one image using 1.1.0.0. Here are the log and write speed graph.

 

I 21:06:13 ImgBurn Version 1.1.0.0 started!

I 21:06:13 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

I 21:06:13 Initialising SPTI...

I 21:06:13 Searching for SCSI / ATAPI devices...

I 21:06:13 Found 7 DVD-ROMs and 1 DVD?RW!

I 21:07:41 Operation Started!

I 21:07:41 Source File: C:\ImgBurn 1.1.0.0\IMAGE_1.ISO

I 21:07:41 Source File Sectors: 2,260,248 (MODE1/2048)

I 21:07:41 Source File Size: 4,628,987,904 bytes

I 21:07:41 Source File Implementation Identifier: DVD Shrink

I 21:07:41 Destination Device: [1:1:0] BENQ DVD DD DW1640 BSOB (E:) (ATA)

I 21:07:41 Destination Media Type: DVD+R (Disc ID: YUDEN000-T02-00) (Speeds: 2.4x, 4x, 8x)

I 21:07:41 Destination Media Sectors: 2,295,104

I 21:07:41 Write Mode: DVD

I 21:07:41 Write Type: DAO

I 21:07:41 Write Speed: 8x

I 21:07:41 Link Size: Auto

I 21:07:41 Test Mode: No

I 21:07:41 BURN-Proof: Enabled

I 21:07:42 Filling Buffer...

I 21:07:43 Writing LeadIn...

I 21:07:58 Writing Image...

I 21:15:29 Synchronising Cache...

I 21:15:30 Closing Track...

I 21:15:34 Finalising Disc...

I 21:15:54 Exporting Graph Data...

I 21:15:54 Graph Data File: C:\ImgBurn 1.1.0.0\ImgBurn 1.1.0.0.ibg

I 21:15:54 Export Successfully Completed!

I 21:15:54 Operation Successfully Completed! - Duration: 00:08:06

I 21:15:54 Average Write Rate: 10,023 KB/s (7.2x) - Maximum Write Rate: 11,134 KB/s (8.0x)

 

post-2746-1144116868_thumb.jpg

 

In looking at this graph I think it looks pretty close to the write speed graph that is in the Drives & Media section using the same burner and media.

 

Moving along, I, then, burned the second image using 1.2.0.0. Here are the log and write speed graph.

 

I 20:52:22 ImgBurn Version 1.2.0.0 started!

I 20:52:22 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

I 20:52:22 Initialising SPTI...

I 20:52:22 Searching for SCSI / ATAPI devices...

I 20:52:22 Found 7 DVD-ROMs and 1 DVD?RW!

I 20:55:25 Operation Started!

I 20:55:25 Source File: C:\ImgBurn 1.2.0.0\IMAGE_2.ISO

I 20:55:25 Source File Sectors: 2,260,256 (MODE1/2048)

I 20:55:25 Source File Size: 4,629,004,288 bytes

I 20:55:25 Source File Implementation Identifier: DVD Shrink

I 20:55:25 Destination Device: [1:1:0] BENQ DVD DD DW1640 BSOB (E:) (ATA)

I 20:55:25 Destination Media Type: DVD+R (Disc ID: YUDEN000-T02-00) (Speeds: 2.4x, 4x, 8x)

I 20:55:25 Destination Media Sectors: 2,295,104

I 20:55:25 Write Mode: DVD

I 20:55:25 Write Type: DAO

I 20:55:25 Write Speed: 8x

I 20:55:25 Link Size: Auto

I 20:55:25 Test Mode: No

I 20:55:25 BURN-Proof: Enabled

I 20:55:25 Filling Buffer...

I 20:55:29 Writing LeadIn...

I 20:55:44 Writing Image...

I 21:03:15 Synchronising Cache...

I 21:03:16 Closing Track...

I 21:03:20 Finalising Disc...

I 21:03:40 Exporting Graph Data...

I 21:03:40 Graph Data File: C:\ImgBurn 1.2.0.0\ImgBurn 1.2.0.0.ibg

I 21:03:40 Export Successfully Completed!

I 21:03:40 Operation Successfully Completed! - Duration: 00:08:08

I 21:03:40 Average Write Rate: 10,023 KB/s (7.2x) - Maximum Write Rate: 11,137 KB/s (8.0x)

 

post-2746-1144116881_thumb.jpg

 

For some reason, during the first 55 seconds of the burn, my Buffer level dropped to 0% (resulting in the low write speed shown on the graph at the beginning). To isolate the problem, I reburned the second image using 1.1.0.0 and the same thing happened. Therefore, I am deducing that it isn't 1.2.0.0 that caused the Buffer to empty the first minute of burning, rather I think it was the image itself. Nonetheless, the image burned successfully (I managed to play it back without any problems).

 

With all that said, my question is this, are these results typical? In other words, are they OK? Or are they evident of the Windows caching problem? My guess is "not," but I'd like some "expert" advice.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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