Version: 2008
  • On The Insider: Miley Cyrus in Sex and the City 2
Advanced Search
advertisement
advertisement
mySimon mySimon mySimon Outdoor Gear mySimon Swimwear mySimon Home and Garden

Forum display:

Computer help: Hardware Conflicts in recently built machine

by peteyboy84 - 7/22/06 10:25 AM
Post 1 of 2

Hardware Conflicts in recently built machine

by peteyboy84 - 7/22/06 10:25 AM

Hi,

I recently combined a couple of old machines into one, and loaded WinXP SP2 on it. I took the hard drive, CDR and DVD from my HP Pavillion and put it into my IBM NetVista. I took the IBM NetVista HD out and put that in an external enclosure.

Now sometimes when I boot up the CDR and DVD drives are not recognized as even being in the machine and sometimes they are. I think it is when I have the external drive hooked up. So I assume that I have some sort of conflict in basic settings.

Can someone please point me in the right direction as to how to troubleshoot and resolve these conflict(s)?

Also, I did not make any jumper changes on the external HD - so not sure whether that would cause a problem if it still thinks it's the master???

Thanks for any help.

Post 2 of 2

Sounds like a bad cable

by jnbhoward - 7/22/06 12:20 PM In reply to: Hardware Conflicts in recently built machine by peteyboy84

To me, this sounds more like either a bad IDE cable, or the cable isn't fully connected to one or all the sockets. I'd check to make sure the connections are good, and if they are, getting a new IDE cable.

It's incredibly rare to see a hardware conflict these days, now that the ISA bus is long gone. Two devices fighting over a specific IRQ or DMA address was about the only real source of hardware conflicts there ever was. Nowadays, that's all managed by the computer. You can sometimes have driver conflicts, but that too is pretty rare. It just has yet to leave the collective psyche of computer users. You could have two devices jumpered to master, but that wouldn't cause intermittent functioning, it would result in both devices being inoperative. Possibly even preventing the system from booting, but likely only if the devices in question were on the primary controller.

Forum legend:
Locked Locked thread
Moderator Moderator
CNET staff CNET staff
Samsung staff Samsung staff
Norton Authorized Support team Norton Authorized Support team
AVG staff AVG staff
Windows Outreach team Windows Outreach team
Dell staff Dell staff
Intel staff Intel staff
Powered by Jive Software