SATA - Designers need to get Brains into Gear

Just a comment, but this being the second time I've been faced with a two-day
marathon trying to repair/reinstall XP onto an SATA disk/mobo combination,
that perhaps it's time Microsoft and the hardware-designers both got their
brains into gear over this.

The craziest feature is the insistence having drivers on a FLOPPY. Now
perhaps neither camp has noticed, but the introduction of SATA more or less
coincided with the demise of the floppy drive as a standard component.

There is also the issue that in many cases, attempting a repair install -
even with the OEM-specific copy of Windows - will remove the SATA driver,
thereby breaking Windows and making the whole computer unbootable.

IMHO it's time the whole SATA driver question was revisited, and a proper
solution found. One that doesn't (ridiculously) call for an obsolete
component to make the latest hardware work!

WinXp was designed some years ago, before sata I believe.
So you are using Old Tec(winxp) with new Tec(sata)
You may find the floppy obselete, but they can still be useful - not least
for installing drivers.

"Ian" <Ian.DeleteThis@discussions.microsoft.com> wrote in message
news:28508874-AB2A-42EE-90EB-E71836825814@microsoft.com...
> Just a comment, but this being the second time I've been faced with a
two-day
> marathon trying to repair/reinstall XP onto an SATA disk/mobo
combination,
> that perhaps it's time Microsoft and the hardware-designers both got their
> brains into gear over this.
>
> The craziest feature is the insistence having drivers on a FLOPPY. Now
> perhaps neither camp has noticed, but the introduction of SATA more or
less
> coincided with the demise of the floppy drive as a standard component.
>
> There is also the issue that in many cases, attempting a repair install -
> even with the OEM-specific copy of Windows - will remove the SATA driver,
> thereby breaking Windows and making the whole computer unbootable.
>
> IMHO it's time the whole SATA driver question was revisited, and a proper
> solution found. One that doesn't (ridiculously) call for an obsolete
> component to make the latest hardware work!
>
>