Dvd slow burning

[Psco2007]

I have been using Nero and Imgburn at 8x and have been burning a 4.45gb in about 8 minutes.
It now is taking 30 minutes or more.

The IDE controllers are set to DMA and nothing else has changed.
The dvd drive is new (LOGITECH - GH22NP20)
The dvds are Memorex - which is what I have always used in the past.

Could the drive be the problem, or has a setting changed?

Thanks for any help.

Paul

[Lawbringer]

Try using a Verbatim DVD-+R, as Memorex discs don't have the best reputation out there. If the problem persists with the Verbatim disc, you might have to look at the drive.

[hech54]

The dvds are Memorex - Could the drive be the problem

Future note....you CANNOT put these two phrases in the same post EVER again....

[Psco2007]

The dvds are Memorex - Could the drive be the problem

Future note....you CANNOT put these two phrases in the same post EVER again....

What the heck are you talking about??
When I read some of the questions in this forum and I try to decipher the grammar and spelling, it gives me a headache and SO DO YOU.

[lordsmurf]

The dvds are Memorex - which is what I have always used in the past.

Then you've been making a mistake for a long time.
Read about the best DVD you should be using here: http://www.digitalFAQ.com/reviews/dvd-media.htm

Try better discs, and I bet your problems go away.

[hech54]

The dvds are Memorex - Could the drive be the problem

Future note....you CANNOT put these two phrases in the same post EVER again....

What the heck are you talking about??

It means the problem is most likely your Memorsux discs.

[Psco2007]

Try using a Verbatim DVD-+R, as Memorex discs don't have the best reputation out there. If the problem persists with the Verbatim disc, you might have to look at the drive.

Thanks for your reply.
I took your advice and bought Verbatim dvds, but the problem persists.
I don't mind the extended burning time but wonder if there is a problem with the drive.
I went to device mgr and set the drive to maximum- any other settings that I might be missing?

Thanks again.

[hech54]

That is an LG drive right....not Logitech?

[Psco2007]

That is an LG drive right....not Logitech?

Yes, LG GH22NP20

[jman98]

The IDE controllers are set to DMA and nothing else has changed.

What exactly are you seeing that makes you say this? I don't remember the exact language of the phrase, but Windows has a setting that says something like "use DMA if possible" and that doesn't necessarily mean that DMA is being used. Your probably sounds suspiciously like a Windows XP PIO mode issue.

[d1spyky]

Double check your IDE controllers, Primary (and secondary if available...), advanced setting tab, transfer mode is DMA and NOT PIO.
If PIO mode, you need to delete and reset setting.

Run -> regedit
Find the following KEY:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\000x
The last four digits will be 0000, 0001, 0002, 0003, and so on.
Under each key, delete all occurences of the following values:
MasterIdDataChecksum
SlaveIdDataChecksum
Reboot the computer.
Windows will now redetect DMA settings.

Good Luck...

[Psco2007]

The IDE controllers are set to DMA and nothing else has changed.

What exactly are you seeing that makes you say this? I don't remember the exact language of the phrase, but Windows has a setting that says something like "use DMA if possible" and that doesn't necessarily mean that DMA is being used. Your probably sounds suspiciously like a Windows XP PIO mode issue.

When I go to device mgr and ide controllers and advanced, it shows all are in dma mode.

[Psco2007]

Double check your IDE controllers, Primary (and secondary if available...), advanced setting tab, transfer mode is DMA and NOT PIO.
If PIO mode, you need to delete and reset setting.

Run -> regedit
Find the following KEY:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\000x
The last four digits will be 0000, 0001, 0002, 0003, and so on.
Under each key, delete all occurences of the following values:
MasterIdDataChecksum
SlaveIdDataChecksum
Reboot the computer.
Windows will now redetect DMA settings.

Good Luck...

I followed your directions, but do not see the settings you referenced.

[d1spyky]

Assuming Windows XP...
Regedit
HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet (not ControlSet001) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Control
Class
{4D36E96A-E325-11CE-BFC1-08002BE10318}\000x
The last four digits will be 0000, 0001, 0002, 0003, and so on.
Under each key, delete all occurences of the following values:
MasterIdDataChecksum
SlaveIdDataChecksum
Reboot the computer. Windows will now redetect DMA settings.

[davexnet]

If you use Imgburn to burn the dvd, it creates a very interesting log in a window that contains a lot of info about the burn.
Either review it carefully or post it in here if in need of assistance - it may help diagnose the problem.

I've noticed in situations I've encountered with cheap media. With some drives, you can set the burn to 12x or 16x,
and indeed it starts out that way, but after a while the drive itself detects an issue and slows it down.
You can see it in the Imgburn stats. Starts at 12x and ends at 4x.

[Psco2007]

Assuming Windows XP...
Regedit
HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet (not ControlSet001) <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Control
Class
{4D36E96A-E325-11CE-BFC1-08002BE10318}\000x
The last four digits will be 0000, 0001, 0002, 0003, and so on.
Under each key, delete all occurences of the following values:
MasterIdDataChecksum
SlaveIdDataChecksum
Reboot the computer. Windows will now redetect DMA settings.

I followed your directions and it still is the same.
I think it is the drive.
I am going to burn with IMGburn and post the log.
Thanks very much for your help.

[Psco2007]

If you use Imgburn to burn the dvd, it creates a very interesting log in a window that contains a lot of info about the burn.
Either review it carefully or post it in here if in need of assistance - it may help diagnose the problem.

I've noticed in situations I've encountered with cheap media. With some drives, you can set the burn to 12x or 16x,
and indeed it starts out that way, but after a while the drive itself detects an issue and slows it down.
You can see it in the Imgburn stats. Starts at 12x and ends at 4x.

Hi Dave,
As you can see, IMGBURN took even longer - Verbatim dvd - 49 minutes.
Please look at log.
I have a feeling it is just a bad drive - only 3 weeks old.

Thanks
Paul

[Psco2007]

I used the "build" feature - thought that is what you are supposed to do to burn to dvd.
I haven't used this program too often - it saved it to my computer.
Sorry - hope that isn't a problem.

[Psco2007]

Here is the burn log.
It took 14 minutes and burned between 2 and 5.

[Psco2007]

I keep trying to send the burn log - seems to be a problem.
Hope this works.

[fritzi93]

Entries like the following would seem to have little or nothing to do with the burner itself or the media used:

Waiting for hard disk activity to reach threshold level...

Waiting for buffers to recover...

Is your hard drive "thrashing"? Is it severely fragmented?

[LIGHTNING UK!]

Try clicking Tools -> Reset DMA in ImgBurn.

That does what d1spyky mentioned earlier - only it leaves no room for user error.

Once you've rebooted, go into device manager and take a look at what it says for DMA again.

You could take it one step further and actually uninstall the IDE/ATAPI controller entries (not the channels, they'll go anyway), reboot and let Windows find them again.

After that, try burning a DVD-R in ImgBurn's 'Discovery' mode. That'll rule out HDD transfer speed issues as the data comes purely from memory.
If that's still slow, try repeating that process again but enable 'Test Mode' before you start it burning.

[Psco2007]

Hi,
I had Imgburn reset the dma's and reboot.
It is showing some IDE channels not showing dma in current transfer.

[LIGHTNING UK!]

The N/A's are just there because there's no drive attached.

Did you actually test the speed using Discovery mode or have you not got that far yet?

[Psco2007]

Haven't gotten that far yet - have to leave now and will have to do it tomorrow.
You also said there is no drive attached, but I have two dvd drives.

[LIGHTNING UK!]

Yeah and I expect they're the two covered by the 1st 'Secondary IDE Channel Properties' picture - the one showing 2 drives using 'Ultra DMA Mode 2'.

[nic2k4]

Fritzi93 is probably right, it looks like a HDD is the problem. Get CrystalDiscInfo and check the status of your HDDs. If any are not green, start by replacing the cable. If your burner issue improves, all is well, don't worry about the SMART info. Over time the drive will go back to green.

[Bjs]

Just looked at the log ... appears more than 1 optical drive is installed.

If the drive which is burning slower is sharing the same data connection with another drive of the same type ... remove the other from the cable before continuing any and all tests for accurate results.

Sometimes secondary drives which develop even the smallest of faults can be the cause ... these faults do no harm but can contribute to slower burning speeds later.

[VegasBud]

Since it hasn't been mentioned...

The first burn log posted (which took 49 minutes 48 seconds for the task to complete) says ImgBurn was only creating an iso, not actually doing any burning. Since iso creation (typically) just involves reading from a hard drive and writing to a hard drive, the inordinate amount of time spent creating the iso had nothing to do with the burner or the media which was in the drive at the time...and everything to do with the throughput of the hard drive(s) used for the source and destination.

Personally, I would figure out why it takes ~50 minutes to create a single layer iso before worrying about the burner and the media.

[Psco2007]

My thanks to all who replied.

I replaced the LG drive and the problem of slow burning is now gone.

Thanks again!!