|Tell us the make and model of your brand name system, or if you have a generic desktop system, the make and model of the mboard. |
The model, sometimes the make, of a mboard in a generic desktop system is usually printed on the mboard's surface in obvious larger characters, often between the slots.
The specific model of a brand name system is often shown on a label on the outside of the case somewhere, or it can often be determined by going to the brand name's web site and loading a program they have available, if Windows is still working, on the subject computer.
If it's a Dell computer...
Go here for how to find the Service tag "number":
Tell us what it is.
If it's a HP or Compaq computer.....
Scroll down a bit.
Look for the similar label on the outside of your computer.
Quote the specific model number - that's at the end of the first line.
Quote the Product number - that's on the third line.
If it's a Lenovo computer
Find your specific Product number and tell us what it is:
Finding my product number
If it's an Acer laptop or netbook
Where is the model number located on my notebook or netbook?
Where is the serial number located on my notebook or netbook? (part two)
If it's an Acer desktop computer
Where is the model number located on my desktop?
Where is the serial number located on my desktop? (part two)
"my computer can't see my cd/dvd drives"
" i need pci simple communicationc controller for motherboard "
Your operating system not having built in drivers for a "pci simple communications controller " has NOTHING TO DO with it not being able to "SEE" your CD / DVD drives !
Windows detects CD / DVD drives automatically and installs built in generic drivers for them if their power connectors from the power supply / data cables are correctly connected and if there's no problem with the data cables.
If the drive is desktop IDE, the jumper setting for Master, Slave, or Cable Select must be correct on the back of the drive.
If there are two drives on the same IDE data cable, either one must be set to Master, the other to Slave, or both drives must be set to Cable Select. If two IDE drives - two optical (CD or DVD) drives. or two hard drives, or a hard drive and an optical drive - connected to the same data cable are both jumpered Mster or Slave, BOTH drives will NOT be detected by the mboard / the operating system.
E.g.. Labelling for CD / DVD drives - Master - MA, Slave - SL, Cable Select - CS. Install the jumper on two pins vertically with respect to the back of the drive. If the 3 pairs of pins on the back of the drive are not obviously labeled with printed letters, use good lighting - the letters are often etched into the plastic above the pins, or they're stamped into the metal on the top of the drive at the back of the drive above the pins.
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 intermittent, 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.
Try another data cable if in doubt.
80 wire data cables must have the proper end connector connected to the mboard IDE header - usually that's blue, but in any case it's the one farther from the middle connector on a 3 connector data cable.
Check your SATA data cables. The connector on each end should "latch" into the socket on the drive and on the mboard, or on the drive controller card - it should not move when you merely brush your hand against it near the socket - if it does, mere vibration can cause a poor connection of it - use another SATA data cable that does "latch", or tape the connector in place.
(There is a slight projection or bump on one side of the outside of the connector that "latches" it into the socket - it's easily broken off or damaged)
The same thing applies for the SATA power connection.
XP doesn't have the drivers built in for most things that first came out after XP was first released, circa 2001, and it doesn't have some of the drivers built in for things made before that.
Whenever you load Windows from a regular Windows CD (or DVD) from scratch, after Setup is finished you must load the drivers for the mboard, particularly the main chipset drivers, in order for Windows to have the proper drivers for and information about your mboard hardware, including it's AGP or PCI-E, ACPI, USB 2.0 if it has it, and hard drive controller support. If you have a generic system and have the CD that came with the mboard, all the necessary drivers are on it. 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 have brand name system computer, the drivers you need for all the devices the computer came with, including the "pci simple communications controller" if it came with it, are in the downloads for your specific model on the brand name's web site. You often must go to the web site for the region the computer was bought in.
If you have a generic desktop system, the drivers you need for everything built into the moboard are in the downloads for your specific mboard model. If whatever the "pci simple communications controller" is, is built into the mboard, they will have the drivers for it.
You MAY need to go to the web site for the region the computer / mboard was bought in.
If whatever the "pci simple communications controller" is, did NOT originally come with the brand name system, and/or if it's on a physical card installed in a slot on generic system's desktop mboard and it did not come with the system....
You could use what Nick Ritchie suggested to identify what it is, and with that info search for drivers for it
- or - if it's a it's on a physical card installed in a slot on desktop mboard, remove the AC power to the computer, remove the card, and see if you can see an obvious model number printed on it's surface that you can use to search for drivers for it,
- or - go in Device Manager, double click on the unknown "pci simple communications controller" listing, then click on the Details tab.
Tell us what the Plug-n-Play ID string you see there is. e.g. PCI/VEN_8086&DEV_27D8&SUBSYS...
(e.g. RIGHT click on My Computer - Properties - Hardware - Device Manager)