Re: Motherboard Upgrade=Reload XP?

No you cannot update the chipset drivers. Whenever you change the
motherboard that a harddrive containing the OS has used, then you MUST
reformat the harddrive and do a fresh install of the OS. Otherwise you face
ongoing Registry errors and data corruption.

--
DaveW



"Dave I." <daveri1@xxxxxxxxxxx> wrote in message
news:Xns96B5C18EED3A4hammer@xxxxxxxxxxxxxxxxx
> I'm looking at upgrading my P4PE to a P4S800D-E motherboard. All other
> hardware the same. Will I need to reload Windows XP (Pro, SP2) from
> scratch (yuck) or will it allow me to update the chipset drivers (SiS vs.
> Intel) during the first boot? Thanks.
>
> Dave


.

Relevant Pages

  • Re: Motherboard Upgrade=Reload XP?
    ... > No you cannot update the chipset drivers. ... > motherboard that a harddrive containing the OS has used, ... > reformat the harddrive and do a fresh install of the OS. ... everytime some hardware is changed? ...
    (alt.comp.periphs.mainboard.asus)
  • Re: Halo graphical problems
    ... Did you reinstall XP when you upgraded your motherboard? ... and then repair Windows: ... Download the Sasser patch to reinstall it after you repair Windows! ... |>How to update your Chipset Drivers: ...
    (microsoft.public.games)
  • Re: Motherboard Upgrade=Reload XP?
    ... >>> No you cannot update the chipset drivers. ... >>> motherboard that a harddrive containing the OS has used, ... Don't forget to backup just in case. ... worst that can happen is I'll have to reformat and reinstall anyway. ...
    (alt.comp.periphs.mainboard.asus)
  • Re: Fatal XP hardware install
    ... Check the BIOS settings ... >>for the presence of a LAN device and try disabling it. ... >>motherboard chipset drivers first to be SP2 compliant and then procede. ...
    (microsoft.public.windowsxp.general)
  • Re: usb connection slow error
    ... Your USB ports are controlled by Chipset drivers for the ... Motherboard - which you should of installed first thing after Windows XP ... chipset drivers from Toshiba for Win2000 in order to fix the problem. ...
    (microsoft.public.windowsxp.general)