"Ok, yes all of the drivers are installed. This is on a fresh load of WinXp Pro Sp2 original operation system not recovery disk." If you use a Recovery disk for a brand name system software installation, all the necessary drivers are already present for the hardware the system originally came with when the Recovery procedure has been completed. As I pointed out.... "If you load drivers from the web, brand name system builders and mboard makers often DO NOT have the main chipset drivers listed in the downloads for your model - in that case you must go to the maker of the main chipset's web site, get the drivers, and load them." If you're not 100% sure the main chipset drivers were loaded, it does no harm to go to the the maker of the main chipset's web site, get the drivers, and load them. "Checked setting on cable select. Yes" You can either use cable select jumpering on the drives, or master/slave jumpering, but don't mix the two types of jumpering for drives on the same 3 connector data cable. If you do, you will likely have problems with one drive. If you use master/slave jumpering, if there are two drives on a data cable, one must be jumpered master, the other slave. If one drive is attached to a cable, it should be jumpered master - on older mboards it will not be detected at all if it is jumpered slave - on newer mboards it may still be detected if it is jumpered slave, but in some situations, with some software, it may not be detected properly. The info on the label on some drives can be confusing - e.g. sometimes the jumpers are shown upside down with respect to the back of the drive. If the position of the power connector is shown relative to the jumper positions, go by that, or if there are markings near the jumpers on the back of the drive (they may be stamped into the plastic or metal but not highlighted and be difficult to make out), go by that. The correct end connector on a 3 connector 80 wire data cable MUST be installed on the mboard IDE header in either case - usually that's blue, or in any case it's the end connector farther from the middle connector on a 3 connector data cable. If either data cable has ever been removed.... It is common to un-intentionally damage IDE data cables, especially while removing them - the 80 wire ones are more likely to be damaged. What usually happens is the cable is ripped at either edge and the wires there are either damaged or severed, often right at a connector or under it's cable clamp there, where it's hard to see - if a wire is severed but it's ends are touching, the connection is intermittant, rather than being reliable. Another common thing is for the data cable to be separated from the connector contacts a bit after you have removed a cable - there should be no gap between the data cable and the connector - if there is press the cable against the connector to eliminate the gap. 80 wire data cables are also easily damaged at either edge if the cable is sharply creased at a fold in the cable.

0

When you look at the IDE ATA/ATAPI controllers in Device manager are there listings for Primary channel, Secondary channel and dual channel? If you are using both to copy disks you should connect one to each channel (separate cables). You can connect the DVDrom as the slave to your boot drive and make the DVD burner the Master on the secondary channel. Using Master/slave setting for each channel allows you to connect either drive to either connector on the cable. This makes it easier to route cables. If the cables are still an issue you might look into round cables. I just got an email from an online vendor this morning for cheap round cables. the link is below. I have bought from this vendor with good results. http://www.cableclub.com/advanced_s...

0

Are you positive that you have 'correctly' jumpered 'cable select' on both devices. Those jumpers can be tricky on some drives. Maybe try Master/Slave.

0

Ok, I switched from cable select to master and slave. This did not cure the problem. I am officially out of ideas now. To Tubesandwires: By the way the computer is a IBM Netvista 8307. No I did not use a Recovery disk. Use Original WinXP Sp2. "If you load drivers from the web," The drivers were from Lenova/IBM site. "Checked setting on cable select. Yes" The setting are clearly labeled and are correct depending if I used Cable select or Master and Slave. "common to un-intentionally damage IDE data cables" I do not think this is the case, reason for thinking this is if the cable was bad I would think the dvdrom would not work if placed in a different postilion on the cable. But it has not, it will work no matter where it is placed and not matter what setting CS or MS. So this is why I think I can rule out the cable. Last of all yes the correct end of the cable is being use. The single connector end is in the MB and the 2 connectors are being used on the drives. To OtheHill, "IDE ATA/ATAPI controllers in Device manager " Yes the Device Manager was check and there 2 ide controller there, Primary and Secondary and addition Intel controller,8280 Ultra ATA Storage Controller. There are no yellow exclamation marks. Reported as installed and working properly. Any more comments? Never say Never Romeo Void Firefox 2.0.0.16 A Safer Browser Thunderbird 2.0.0.16

0

It's possible for a (defective?) drive on a cable to cause problems with the other drive. Try swapping the CDROM drive with the slave drive on the first channel. Actually the best place for the CDROM drive is probably as slave on channel one.

0

Yes cables are correct. Never say Never Romeo Void Firefox 2.0.0.16 A Safer Browser Thunderbird 2.0.0.16

0

I suggested recabling to split the two optical drive apart. I have experienced issues with older systems when using two optical drives on one channel. What other drives are installed in the system?

0

"IBM Netvista 8307" "The drivers were from Lenova/IBM site." Did you download and run this from there? These are the main chipset drivers: INF Update utility http://www-307.ibm.com/pc/support/s... Main chipset "drivers" may have few or no actual driver files - they always have one or more *.inf files that inform Windows about what features it already has built into it that it should use for the mboard main chipset. If you DID, then... Found in the downloads on that site, in "Flash BIOS update - bootable diskette version"....... "Installation README" ftp://ftp.software.ibm.com/pc/pccbbs/thinkcentre_bios/24jt54a.txt Check your bios version. You may need to update the bios. - If it's older than 24KT34A/24JT34A (a lower number after KT or JT), there is a fix in that version and newer. "Fix for secondary IDE drive sometimes not being detected" - If it's older than 24KT32A/24JT31A there is the fix in that version and newer: "Correct setting of IDE slave device UDMA mode under ACPI"

0

Good find tubes.

0

If you can't get both optical drives working on the same data cable, it makes very little difference or no difference whether they on the same data cable as a hard drive. The cpu always accesses the drives one at a time, and the max speed of one drive on the data cable is not affected by the max speed of the other drive on the same cable.

0

Finally I got it to work. What pain. Primary ide master 80 GB Slave Lite-on DVD writer. Secondary 200 Gb hdd dvd-rom. Luckly I am in full tower, I had to get rails to mount the 80GB hdd in a 5.25 space. Then shift everything around in the chassic. So now if you look at the case. 1st bay 80Gb Primary Master 2nd bay DVD writer Primary Slave 3rd bay DVD-rom Secondary Slave. 4th bay 200 Gb hdd Secondary Master 1.4 Mb floppy I have never had so much trouble get a computer to work properly. Oh well, it works and that's the way it will stay for a while. I feel like I have cheated some how going back to the old master and slave but it seem to be the only way to get it to accept the dvd writer. Thanks for all the great replies. PS. I did flash the bios and it did not help. Never say Never Romeo Void Firefox 2.0.0.16 A Safer Browser Thunderbird 2.0.0.16

0

That is the correct way. CS is cheating. The OEMs do that so when someone adds a drive they don't have to change jumpers on previously installed drives.

0

It's good to hear you found a solution. "PS. I did flash the bios and it did not help." You should always load bios defaults, or clear the cmos by moving a jumper on the mboard then moving it back, after you flash the bios. The flash procedure usually does not do that automatically, and you should do that to make sure the data contents of the cmos match the new bios version, otherwise your bios may not work properly because the contents of the cmos are that for the previous bios version.

0