|
Files from 2nd HD take 5x as long to burn
|
|
|
bonjonno
Newbie
|
31. December 2005 @ 08:21 |
Link to this message
|
|
I am using NERO BR 6. I have two identical WD 40GB drives. My C is NTFS and is the master; also has win XP Pro. My E is FAT32 and is the slave. Both on the primary controller. If I make an image from a dvd or burn a dvd from an image, it works at 16X from the C drive and takes a bit over 5 minutes, from the E drive is always about 20 minutes. I have a benq DW1640. Running out of room on the C drive but the E drive takes so long. Any clues as to what is the deal? This is a dell 400SC btw. P4 2.8. Thanks
|
|
Advertisement
|
 |
|
|
AfterDawn Addict
|
31. December 2005 @ 08:26 |
Link to this message
|
|
is DMA enabled?
what is the speed of each drive?
are they on the same cable?
you could try changing to ntsc
Nothing here to see, move along folks.
 |
|
bonjonno
Newbie
|
31. December 2005 @ 08:31 |
Link to this message
|
DMA was the first thing I thought of, but I cannot find it listed anywhere. Both drives are 7200. They are on the same cable. Change what to NTSC? Thanks.
|
AfterDawn Addict
|
31. December 2005 @ 08:36 |
Link to this message
|
go to device manager
----------
change fat32 to NTSC
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/co...
To convert a volume to NTFS from the command prompt
1.
Open Command Prompt. Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
2.
In the command prompt window, type: convert drive_letter: /fs:ntfs
For example, typing convert D: /fs:ntfs would format drive D: with the ntfs format. You can convert FAT or FAT32 volumes to NTFS with this command.
Important Once you convert a drive or partition to NTFS, you cannot simply convert it back to FAT or FAT32. You will need to reformat the drive or partition which will erase all data, including programs and personal files, on the partition.
Nothing here to see, move along folks.
|
|
bonjonno
Newbie
|
31. December 2005 @ 08:51 |
Link to this message
|
OK. Your typo threw me. You meant NTFS not NTSC.
But this got me looking at the controller properties and I discovered this. Primary IDE both device 0 and device 1 are set to DMA if available; Device 0 has current transfer mode Ultra DMA Mode 5, and device 1 has PIO Mode. Both are greyed out. I'm stumped.
|
AfterDawn Addict
|
31. December 2005 @ 08:58 |
Link to this message
|
|
hi
pio is not brill! PIO = slower transfer
uninstall the controller (not channel) and reboot pc!
see if it will go to DMA
are the last 2 the hard drives??? as one is dma5 and other pio?
do you have them on same cable in the pc?
did you set the jumpers correctly?
Nothing here to see, move along folks.
This message has been edited since posting. Last time this message was edited on 31. December 2005 @ 09:00
|
|
bonjonno
Newbie
|
31. December 2005 @ 09:06 |
Link to this message
|
|
I will try that asap. Yes those are the settings on the two hard drives that are on the same cable; both are set to CS as per instructions.
|
|
bonjonno
Newbie
|
31. December 2005 @ 09:34 |
Link to this message
|
|
WOO HOO! Both drives now UDMA5. Thank you Rotary! You pointed me in the right direction. I found this fix elsewhere; it took a change in the registry, but it worked.
Re-enable DMA using the Registry Editor
My thanks go to my fellow MVP Alexander Grigoriev who taught me this method.
Run REGEDIT. Go to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}
It has subkeys like 0000, 0001, 0002, etc. Normally 0001 is the primary IDE channel, 0002 the secondary, but other numbers can occur under certain circumstances. You have to go through these subkeys and check the DriverDesc value until you find the proper IDE channel.
Delete MasterIdDataChecksum or SlaveIdDataChecksum, depending on whether the device in question is attached as master or slave, but it can't actually hurt to delete both. Reboot. The drive DMA capabilities will be redetected.
Open Device Manager again and check whether the device is now actually using DMA mode. If so, congratulations, you've made it (at least until the next time Windows disables DMA).
2005-10-24 – Tomáš Souček wrote, if this doesn't work, check also the dword value MasterDeviceTimingModeAllowed, whose default value is hex 0xFFFFFFFF. If you have a much smaller value, you can try to set it back to its default and reboot for a test.
|
AfterDawn Addict
|
1. January 2006 @ 01:15 |
Link to this message
|
|
hi
you set one as master and the other as slave!
not CS! then the pc would of did it itself..
glad you got it working ;-])
Nothing here to see, move along folks.
|
|
Advertisement
|
|
|
Moderator
|
1. January 2006 @ 03:06 |
Link to this message
|
|
some 'corporate' type PCs like Dell, Compaq or whatever seem to love the pointless and annoying cable select. Any machine i've come across with cable select i've changed to standard MASTER or SLAVE arrangement without issue. Not sure if that works in all cases but i've never had issues yet with Compaq stuff (i stay awy from Dell stuff myself)
Main PC ~ Intel C2Q Q6600 (G0 Stepping)/Gigabyte GA-EP45-DS3/2GB Crucial Ballistix PC2-8500/Zalman CNPS9700/Antec 900/Corsair HX 620W
Network ~ DD-WRT ~ 2node WDS-WPA2/AES ~ Buffalo WHR-G54S. 3node WPA2/AES ~ WRT54GS v6 (inc. WEP BSSID), WRT54G v2, WRT54G2 v1. *** Forum Rules ***This message has been edited since posting. Last time this message was edited on 1. January 2006 @ 03:07
|
