[Disc Burn Quality]

here is another screenshot using my burner to test, just wondering how well the burner is burning since it is a year old....

[Disc Burn Quality]

the spike at around 1.5gb doesn't look too good.

its a shame you couldn't measure jitter, it would give a more accurate result

 

 

so does that indicate a bad burn? or possibilty the disc will not work at a future date?

[Disc Burn Quality]

Not sure how to read this, nor if this is the write place to post this, sorry if it isn't, but is this a good or bad burn? thanks

[Sony DVD-R's]

well I burned a disc using the Sony -R's and it burned fine with no errors or anything different then when I burned using +R's....

[Sony DVD-R's]

I just bought a 50 pack of Sony DVD-R's at Best Buy because they are on sale, and noticed they have this thin white line going around the center of them, is this normal?

 

If it is normal, what is it used for? why don't +R's have them. Thanks.

 

None of my DVD+R's have them, which is what I normally buy.

 

Here is an example picture of what I am talking about.

 

[hard disk activity to reach threshold level]

well looks as though it was the Intel Matrix storage driver; I installed the latest version (6.1) and have burned 2 dvd's with no problems...

 

thanks for everyones help

[hard disk activity to reach threshold level]

doesn't look to be all the time, only under high load...0.002 right now...

[hard disk activity to reach threshold level]

Ok so it's easy to see some glitches in that file around the 1.3 GB mark but it's not exactly all over the place the entire time - which is what I was kinda expecting.

 

I think this issue is just something you're going to have to fix yourself via some problem solving and a lot of trial and error.

 

Something is happening that's preventing the program from reading enough data from the hdd to sustain a pretty measly 4x write speed. You just need to find out what that is

 

Maybe take a look in perfmon.msc and see what your typical 'average disk queue length' is. You should be able to just watch the graph! At the moment mine is on 0.002.

 

 

thanks for your help, do you think the files themselves are messed up? or the files are fine, and something is just interfering with the burn?

 

the average is at 1.216 at the current moment of this posting..

[hard disk activity to reach threshold level]

file removed.

[hard disk activity to reach threshold level]

Did you actually search? LUK! has answered this question in detail a number of times.

 

Regards

 

 

yes I did search, and only thing they say is because of bad media, I have used Sony, RiData, Verbatim, and same thing.

 

It has never done this before, until the last few days it just started...

[hard disk activity to reach threshold level]

The whole threshold level thing isn't really the problem here.

 

You need to find out why your internal program buffer and device buffer is falling right down low so that it triggers the buffer recovery - which is where the threshold level comes into play.

 

What's happening on your PC that's so stressful it can't read from the HDD and burn at 4x?! Or did you change the buffer size to 1MB or something?

 

Do you have any free RAM or are you always working in the swapfile virtual memory?

 

 

What's happening on your PC that's so stressful it can't read from the HDD and burn at 4x?! Or did you change the buffer size to 1MB or something?

 

I am not sure, when I burn, I don't do anything else while burning....my HD light on the PC is usually solid whenever burning something....

 

Do you have any free RAM or are you always working in the swapfile virtual memory?

 

I got over 700mb free when burning...

[hard disk activity to reach threshold level]

theres a number of things you can do and rather than make a list go to the SEARCH function at the top of the page and type threshold level and do some reading ,bad media, old hardware ,multitasking,theres a number of things that cause that error

 

 

well I am using SONY media, which is not bad...I have burned over 50 of them and have had no problems...no multitasking, I am not doing anything on the computer, and everything is close except imgburn. And the computer is little over a year old, and dvd burner is less then 3 months old...anything other suggestions?

[hard disk activity to reach threshold level]

What does this mean? how can I fix this?

 

DMA is enabled, and haven't made any changes to the system...

 

 

When burning a DVD+R, I am getting this...

; //****************************************\\

; ImgBurn Version 2.1.0.0 - Log

; Saturday, 28 October 2006, 20:44:39

; \\****************************************//

;

;

I 20:32:56 ImgBurn Version 2.1.0.0 started!

I 20:32:56 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 20:32:56 Initialising SPTI...

I 20:32:56 Searching for SCSI / ATAPI devices...

I 20:32:57 Found 1 DVD-ROM and 1 DVD?RW!

I 20:33:29 Operation Started!

I 20:33:29 Source File: D:\TOS_S3D3B.ISO

I 20:33:29 Source File Sectors: 1,971,723 (MODE1/2048)

I 20:33:29 Source File Size: 4,038,088,704 bytes

I 20:33:29 Source File Volume Identifier: x

I 20:33:29 Source File Implementation Identifier: x

I 20:33:29 Source File File System(s): ISO9660, UDF (1.02)

I 20:33:29 Destination Device: [0:0:0] _NEC DVD_RW ND-3550A 1.06 (E:) (ATA)

I 20:33:29 Destination Media Type: DVD+R (Disc ID: SONY-D21-00) (Speeds: 4x, 6x, 8x, 12x, 16x)

I 20:33:29 Destination Media Sectors: 2,295,104

I 20:33:29 Write Mode: DVD

I 20:33:29 Write Type: DAO

I 20:33:29 Write Speed: 4x

I 20:33:29 Link Size: Auto

I 20:33:29 Test Mode: No

I 20:33:29 BURN-Proof: Enabled

I 20:33:29 Filling Buffer...

I 20:33:30 Writing LeadIn...

I 20:33:56 Writing Image...

W 20:36:04 Waiting for buffers to recover...

W 20:36:18 Waiting for hard disk activity to reach threshold level...

I 20:36:22 Writing Image...

W 20:36:33 Waiting for buffers to recover...

W 20:36:47 Waiting for hard disk activity to reach threshold level...

I 20:36:51 Writing Image...

W 20:37:04 Waiting for buffers to recover...

W 20:37:14 Waiting for hard disk activity to reach threshold level...

I 20:37:16 Writing Image...

W 20:37:44 Waiting for buffers to recover...

W 20:37:54 Waiting for hard disk activity to reach threshold level...

I 20:37:56 Writing Image...

W 20:38:07 Waiting for buffers to recover...

W 20:38:20 Waiting for hard disk activity to reach threshold level...

I 20:38:22 Writing Image...

W 20:38:33 Waiting for buffers to recover...

W 20:38:47 Waiting for hard disk activity to reach threshold level...

I 20:38:49 Writing Image...

W 20:39:08 Waiting for buffers to recover...

W 20:39:17 Waiting for hard disk activity to reach threshold level...

I 20:39:18 Writing Image...

W 20:39:32 Waiting for buffers to recover...

W 20:39:43 Waiting for hard disk activity to reach threshold level...

I 20:39:47 Writing Image...

W 20:40:00 Waiting for buffers to recover...

W 20:40:09 Waiting for hard disk activity to reach threshold level...

I 20:40:13 Writing Image...

W 20:40:27 Waiting for buffers to recover...

W 20:40:40 Waiting for hard disk activity to reach threshold level...

I 20:40:43 Writing Image...

W 20:40:54 Waiting for buffers to recover...

W 20:41:05 Waiting for hard disk activity to reach threshold level...

I 20:41:09 Writing Image...

W 20:41:21 Waiting for buffers to recover...

W 20:41:30 Waiting for hard disk activity to reach threshold level...

I 20:41:34 Writing Image...

W 20:41:47 Waiting for buffers to recover...

W 20:41:57 Waiting for hard disk activity to reach threshold level...

I 20:42:01 Writing Image...

W 20:42:13 Waiting for buffers to recover...

W 20:42:24 Waiting for hard disk activity to reach threshold level...

I 20:42:32 Writing Image...

W 20:42:46 Waiting for buffers to recover...

W 20:42:57 Waiting for hard disk activity to reach threshold level...

I 20:43:00 Writing Image...

W 20:43:13 Waiting for buffers to recover...

W 20:43:24 Waiting for hard disk activity to reach threshold level...

I 20:43:25 Writing Image...

I 20:43:57 Abort Request Acknowledged

I 20:43:58 Synchronising Cache...

I 20:43:59 Closing Track...

I 20:44:11 Finalising Disc...

E 20:44:27 Failed to Write Image!

E 20:44:27 Operation Aborted! - Duration: 00:10:57

I 20:44:27 Average Write Rate: 2,780 KB/s (2.0x) - Maximum Write Rate: 5,750 KB/s (4.2x)

I 20:44:39 Close Request Acknowledged

I 20:44:39 Closing Down...

I 20:44:39 Shutting down SPTI...

I 20:44:39 ImgBurn closed!

[Verify Against Image File - Broken in 2.1.0.0?]

when will an update come out to fix this? just wondering, not trying to rush you Lighting Uk...