DVD takes 90 min to burn. Help?
 

After upgrading from Nero 6.0.0.0 to Nero 6.6.0.0, a 4GB DVD ISO takes 90 minutes to burn, where with 6.0.0.0 it took 14 minutes to burn. I'm going to try Alcohol 120% to see if I get the same problem. Anyone seen anything like this? I have loaded Nero 6.3.0.0 and it does the same thing.

Thanx in advance.

I Don't think it's a incompatible/unsupported media problem.......your dvd would still be burned within an hour when burning at lowest speed....Check your device manager -->ide ata/atapi controller settings....it's possible that your drive reverted to PIO mode after updating Nero....set it to use UDMA2...

The Second IDE channel, which has the DVD-R, has reverted to PIO mode, I set it back to DMA and I'll reboot it. Thanks

Yeap that should do it.

It didn't change the setting, "Transfer Mode = DMA if available" and "Current Transfer Mode = PIO". Is there a setting in Nero to fix this? It all happened after I installed Nero 6.6.0.0. Re-installing 6.3 didn't help.

What master/slave ide configuration you have on both IDE channels,which drives are attached and what mobo/chipset you use??

Primary IDE Channel - Master=Maxtor 60GB - Slave=IBM 60GB
Sec IDE Channel - Master=BTC DVD-R - Slave=BTC CD-R
M/B Asus w/VIA chipset (Celeron/P3 900MHz)

Primary IDE Channel - both drives set to UDMA

Sec IDE Channel - Master set to PIO(set to use DMA if available)
- Slave set to UDMA
***Master was set to UDMA until I installed Nero 6.6.0.0***

Using WinXP SP1

A few things you can try:
.disconnect your cdwriter from the ide cord and try to enable dma aain for your dvdwriter when it's alone on the channel....
.if that doesn't work,change your ide cable to another format.....40 pin to 80 pin or vice versa...

And install sp2 while your at it. ;)

I had the same problem one time and this is the info from the net and here that resolved the issue.

Quote:

From Microsoft In Windows 2000 only, read requests to ATA disks are sometimes issued with a time-out value of 4 seconds. This occurs when your computer resumes from standby. This might cause a disk time-out because drives typically take more than 4 seconds to spin up. This time-out value was changed to 10 seconds. In Windows XP and Windows Server 2003, this time-out value is always 10 seconds. An alternate, less-aggressive policy is implemented to reduce the transfer mode (from faster to slower DMA modes, and then eventually to PIO mode) on time-out and CRC errors. The existing behavior is that the IDE/ATAPI Port driver (Atapi.sys) reduces the transfer mode after any 6 cumulative time-out or CRC errors. When the new policy is implemented by this fix, Atapi.sys reduces the transfer mode only after 6 consecutive time-out or CRC errors. This new policy is implemented only if the registry value that is described later in this article is present. To implement the alternate behavior (reducing the transfer mode after six consecutive time-out or CRC errors instead of after six cumulative time-out or CRC errors), you must modify the registry as described below after you install the hotfix. WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. Follow these steps, and then quit Registry Editor: 1. Click Start, click Run, type regedit, and then click OK. 2. Locate and then click the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0001 3. On the Edit menu, point to New, and then click DWORD Value. 4. Type ResetErrorCountersOnSuccess, and then press ENTER. 5. On the Edit menu, click Modify. 6. Type 1, and then click OK. Follow these steps, and then quit Registry Editor: 1. Click Start, click Run, type regedit, and then click OK. 2. Locate and then click the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002 3. On the Edit menu, point to New, and then click DWORD Value. 4. Type ResetErrorCountersOnSuccess, and then press ENTER. 5. On the Edit menu, click Modify. 6. Type 1, and then click OK. Note The numbered subkeys that are listed earlier correspond to the primary and secondary IDE channels on a computer that contains a single IDE controller. If your computer contains two IDE controllers, the numbered subkeys for the primary and secondary IDE channels for each of the two controllers may be: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0003 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0004 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0005 To verify that you have located the correct subkey, verify that the DriverDesc value for the subkey contains the string value "Primary IDE Channel" or the string value "Secondary IDE Channel." From FOX reg. key : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0001 or 0002 (depending on beeing primary[0001] or secondary[0002] ide channel) there you modify the DWORD value of : if the drive is on master: "MasterDeviceTimingModeAllowed" or if the drive is on slave: "SlaveDeviceTimingModeAllowed" to ffffffff then go back to your device manager set your drive in IDE channel properties first back to pio and then, after confirming, again to dma ...that should do the trick From McoreD CD-ROM and DVD-ROM drives can revert to using PIO mode, despite being set to use "DMA if Available." Here's how to make Windows XP redetect the DMA capabilities of the drives. This behaviour occurs with the following conditions: Windows XP is the operating system A CD-ROM or DVD-ROM drive, which is known to support DMA mode now works only in PIO mode. The drive controller is set to use "DMA if available" but reports to be only in PIO mode. Following is the mechanism that has worked for me, please try it at your own risk, it involves hacking the registry: Open RegEdit Find the following KEY: CODE 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: CODE MasterIdDataChecksum SlaveIdDataChecksum Reboot the computer. Windows will now redetect DMA settings.

Wow! That's why I love BetaOne! Everyone is so helpful. I'll try these fixes and let ya all know if it works. Thanx again all!

Well, that worked perfectly! Were back to burning DVDs in 14 minutes. Thanks again for everyone's help.:D

Thanks Vinnie
My Favorite program burn DVD is "Super DVD Copy" and "Ashampoo Burning Studio 5" and NOW "CloneCD 5.0.4.2"
Yes , CloneCD 5.0.4.2

Thanks for asking this question, I was wondering why my dvd @ 1x took 90 minutes to burn. I'm at work now, so I will have to wait till I get home to check the PIO and DMA settings.

Thanks,
PCTech:p

Actualy 90 mins at 1X sounds about right , I usually take just over 20 with my 4X burners.

With DMA on and @ 1X speed,it should be between 55-60 minutes maximum...

@Vinnie - Nice record keeping, I'm impressed. :cool:

I bet your HD is so nice & neat. :thumbsup:

Edit - This is a very good thread and I feel it should also be under Hardware Support so I've moved it but left a redirect in the Software Support section.

Roadworker has it right.
According to my calculations a DVD will burn 1360 kb/s at 1x. At that rate a full DVD, 4.7 Gb will take 60.39 minutes.

Thanks, I had enough trouble trying to get mine working right that I made it a point to keep the info at hand.
:D

Or even less,since a dvd can only hold 4.37 gb.......;) .......that 4.7 gb is a marketing trick,the manufacturers use another counting system than the binary one to count their bits...:)

@ Roadworker
Forgot about that, the same old trick that hard drives use.
:rolleyes:

It did it again, 68 minutes to burn a DVD. I deleted the:

MasterIdDataChecksum
SlaveIdDataChecksum

values from the reg again, now it's about 15 min to burn a DVD, which is normal. Any idea what causes it to revert to PIO mode? I didn't install any new software or hardware this time to cause it. Just a minor annoyance.

Did you read about the recent problem found caused from SP2 that slows down burns? Not sure if this might apply to your problem.

I think this explains it, third paragraph down.

In Windows 2000 only, read requests to ATA disks are sometimes issued with a time-out value of 4 seconds. This occurs when your computer resumes from standby. This might cause a disk time-out because drives typically take more than 4 seconds to spin up. This time-out value was changed to 10 seconds.

In Windows XP and Windows Server 2003, this time-out value is always 10 seconds.

An alternate, less-aggressive policy is implemented to reduce the transfer mode (from faster to slower DMA modes, and then eventually to PIO mode) on time-out and CRC errors. The existing behavior is that the IDE/ATAPI Port driver (Atapi.sys) reduces the transfer mode after any 6 cumulative time-out or CRC errors. When the new policy is implemented by this fix, Atapi.sys reduces the transfer mode only after 6 consecutive time-out or CRC errors. This new policy is implemented only if the registry value that is described later in this article is present.

To implement the alternate behavior (reducing the transfer mode after six consecutive time-out or CRC errors instead of after six cumulative time-out or CRC errors), you must modify the registry as described below after you install the hotfix.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Follow these steps, and then quit Registry Editor:

1. Click Start, click Run, type regedit, and then click OK.

2. Locate and then click the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0001

3. On the Edit menu, point to New, and then click DWORD Value.

4. Type ResetErrorCountersOnSuccess, and then press ENTER.

5. On the Edit menu, click Modify.

6. Type 1, and then click OK.

Follow these steps, and then quit Registry Editor:

1. Click Start, click Run, type regedit, and then click OK.

2. Locate and then click the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\
Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002

3. On the Edit menu, point to New, and then click DWORD Value.

4. Type ResetErrorCountersOnSuccess, and then press ENTER.

5. On the Edit menu, click Modify.

6. Type 1, and then click OK.

Note The numbered subkeys that are listed earlier correspond to the primary and secondary IDE channels on a computer that contains a single IDE controller. If your computer contains two IDE controllers, the numbered subkeys for the primary and secondary IDE channels for each of the two controllers may be:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\
Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0002

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\
Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0003

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\
Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0004

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\
Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0005

To verify that you have located the correct subkey, verify that the DriverDesc value for the subkey contains the string value "Primary IDE Channel" or the string value "Secondary IDE Channel."

I had changed these settings back in late December, I think you will find all that info earlier in this thread too. As long as I can fix it, no big deal, just curious what causes the changes to be made in the Registry.

That's the reason I posted that part again, it explains why it changes:

That's why you have to add the new DWORD value, i.e. ResetErrorCountersOnSuccess
After doing this it takes 6 consecutive errors instead of 6 cumulative time-out or CRC errors to drop down the speed.

I've not had anymore problems after doing everything in the post. Of course you might be having so many errors that it's dropping down the speed anyway. You might try lowering your burn speed and see if that helps any.