DVD Writer IDE Transfer Mode Problem

"Zach" wrote in message
oups.com...
Thanks to everyone for all of the help. I apologize for the delay in my
response. Here's where I'm at:

-I checked the BIOS settings and could not find any problems. The
primary IDE slave is enabled. One interesting thing is that the primary
IDE slave device is listed as unknown in the BIOS while windows can
detect it as a Pioneer DVR-111. I guess this goes along with the error
message I'm getting before windows starts.

-The jumper settings on both DVD drives are correct. I originally had
the DVD-ROM set to master and the DVD-RW set to slave. I also tried
setting both drives to cable select and am getting the same problem. I
tried switching the jumpers from each drive to test if possibly the
jumper was bad and am still getting the same problem.

-I tried using a new IDE cable and am still getting the same problem.

-My computer only has one IDE cable, which is listed as the Primary IDE
cable in the BIOS. My hard drives use those new fangled serial cables.
The master (DVD-ROM) is using the IDE connection on the end of the
cable and the slave (DVD-RW) is using the IDE connection in the middle
of the cable.

-I'm using Windows XP Service Pack 2 and all of the critical updates
are installed.

-My computer is a Dell Dimension 9100. From what I can see on the
motherboard, it is made by Dell. One of the stickers on it has the
following numbers:
CN-0X8582-70821-55K-G076
Rev. A00
Let me know if you need any more information about the motherboard.

-One thing I haven't tried is to connect my DVD-RW as the master and my
DVD-ROM as the slave. I'll try this today and let you know what I find
out.



Thanks again,
Zach
---------------------------------------
With Dell BIOS, any unpopulated IDE positions (as shipped) will be disabled
in BIOS menu. After adding another IDE device, you need to go into the BIOS
menu, then set the new IDE position as "AUTO", then save and exit BIOS.
Reboot, then re-enter the BIOS menu another time, then save and exit again.
I know this is an extra step, but in the past when servicing other Dell
machines, the BIOS menu had to be accessed twice before the new device is
recognized and labeled correctly in BIOS. See if this helps in your case;
just a Dell idiosyncratic BIOS thing.

--
-Russell
http://tastycomputers.com

I just switched the DVD-ROM to slave and the DVD-RW to master. This
seems to have fixed the problem. The BIOS now recognizes both devices
and they are both now set to Ultra DMA Mode 2. I'm not really sure what
was going on, but I'm glad it's working now. Thanks for the help!

THANK YOU THANK YOU THANK YOU

I was ready to bash my head against a wall.

I have a Pioneer DVR-111D (BK) with 1.29 firmware. It is SATA.

For some strange reason...my burner started burning at only about 3.8X
max. Reading and writing.

After reading this article I discovered that the transfer mode was set
to PIO and I couldn't change it to the other way. After reading the
article, I was able to resolve the problem.

Any idea what could have caused this problem in the first place? It
just happened all of a sudden....

I use Nero 7 (not the buggy 6 I have been reading about) for most of
my burning (via DVD Shrink). It was happening with ANY software I was
using though.

I really appreciate the help guys.

..


"DigitalBear" wrote in message
...
THANK YOU THANK YOU THANK YOU

I was ready to bash my head against a wall.

I have a Pioneer DVR-111D (BK) with 1.29 firmware. It is SATA.

For some strange reason...my burner started burning at only about 3.8X
max. Reading and writing.

After reading this article I discovered that the transfer mode was set
to PIO and I couldn't change it to the other way. After reading the
article, I was able to resolve the problem.

Any idea what could have caused this problem in the first place? It
just happened all of a sudden....

I use Nero 7 (not the buggy 6 I have been reading about) for most of
my burning (via DVD Shrink). It was happening with ANY software I was
using though.

I really appreciate the help guys.



We have hit upon this many times here. Most revertions happen when there are data
collisions over the bus. Bad ribbons possibly