# Is this a new motherboard Catch-22 or is Windows XP being too clever?

**URL:** <https://boards.straightdope.com/t/is-this-a-new-motherboard-catch-22-or-is-windows-xp-being-too-clever/141396>\
**Category:** Factual Questions\
**Created:** [December 9, 2002, 12:57am UTC](https://boards.straightdope.com/t/is-this-a-new-motherboard-catch-22-or-is-windows-xp-being-too-clever/141396 "2002-12-09T00:57:45Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![glilly](https://avatars.discourse-cdn.com/v4/letter/g/48db29/32.png) [@glilly](https://boards.straightdope.com/u/glilly)\
**Post date:** [December 10, 2002, 5:25pm UTC](https://boards.straightdope.com/t/is-this-a-new-motherboard-catch-22-or-is-windows-xp-being-too-clever/141396/21 "2002-12-10T17:25:05Z")

</div>

> [@](#):
>
> \*Originally posted by cstamets \*  
> **Not to be a stickler, but I said to change the IDE to the generic Standard IDE controller. I’m only pointing this out in case someone else needs to try it sometime. I guess I should have mentioned that just deleting the driver doesn’t work. I’m sorry I wasn’t more specific…**

Actually, you were specific enough. When I went to the profile, there were Standard IDE controllers for IDE 1 and 2, and another more specific-looking one that didn’t seem to have the option of changing. Since I couldn’t change it, I thought if I’d delete that, I’d be left with the generics. When that didn’t work, I tried deleting the lot of them, which I’ve been moderately sucessful with in other types of drivers. Not this time.

So, either I 1) didn’t know what I was doing, or B) had an odd configuration (more likely B). So, future upgraders, try what **cstamets** suggested first, if, for no other reason, repairing Win takes at least half an hour.

[Previous page](https://boards.straightdope.com/t/is-this-a-new-motherboard-catch-22-or-is-windows-xp-being-too-clever/141396.md?page=1)