It wasn't a bad install. He replaced the motherboard which had a different chipset than the original. When that is the case, it's normal that you would need to reinstall the OS.
Printable View
It wasn't a bad install. He replaced the motherboard which had a different chipset than the original. When that is the case, it's normal that you would need to reinstall the OS.
it couldn't have been a bad install cos he had the same install for a number of months...i think somebody1234 is right thoughQuote:
Originally posted by _John_Lennon_@19 September 2003 - 20:42
meh, guess it was just a bad XP install.
*shrugs.
happens.
Actually, there are often ways of getting round this problem, as long as old and new boards have fully compliant acpi support, but by the time I saw the thread you said he had reformatted his pc, so there's not much point in going through it.
it couldn't have been a bad install cos he had the same install for a number of months...i think somebody1234 is right though [/b][/quote]Quote:
Originally posted by 3rd gen noob+19 September 2003 - 16:53--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (3rd gen noob @ 19 September 2003 - 16:53)</td></tr><tr><td id='QUOTE'> <!--QuoteBegin-_John_Lennon_@19 September 2003 - 20:42
meh, guess it was just a bad XP install.
*shrugs.
happens.
OH!
Ahh, i see now, it wasnt a fresh install.
Well then, no worries, I made that same assumtpion about not having to reinstall windows, when I upgrade my comp for the first time. Bought a new motherboard, new processor, new Ram, and yup, didnt work for same reason.