<< XP may in fact have attempted to replace Windows 2000 Professional, but IMHO and thousands of other IT managers, at this point there is no sense in replacing rock solid 2000 Pro workstations with XP.
Now, in comparison to 2000 Pro's relationship to the 2000 Server products, and XP Pro's relationship, 2000 Pro obviously has closer ties. With that in mind, desktop OSes are usually not associated with server components, e.g. SCSI interfaces. Therefore, I am not too surprised that Microsoft's SCSI support on a desktop OS, specfically XP, is lacking. Although, this does not mean it is OK, but just ain't a surprise considering the above. >>
Your opinion has no bearing really on what Microsoft intends for Windows XP The fact remains that Windows XP is STILL Windows 2000 Professional with more feaures and more user oriented conveniences to help out the consumer. More driver support, better integration, etc.
Home is the desktop oriented version (hence it's lack of features). Pro is the full-fledged mack-daddy workhorse operating system like Windows 2000 Professional. Why else would it support DUAL PROCESSORS??? I'm sure that Besty Buy and CompUSA are selling dual systems on the shelves...yeah right I wonder why Windows XP has built in SCSI drivers and support for every major vendor out there (yeah, they don't care about SCSI in Windows XP...suuuuuuuuuuuuuuuure). I don't care WHAT you THINK of Windows XP as an operating system, the fact remains that it is simply NT 5.1 and is NOT far removed from Windows 2000 in performance or capabilities. So please, get over that fact and get to the underlying mechanics of the operating system. Windows XP is meant to replace Windows 2000. It makes NO SENSE on Microsoft's part to neuter SCSI performance or "leave" something out on purpose. If you see some justification for that, I'd really like to know what b/c it doesn't make any sense. It'd be like saying that Microsoft purposely leaves security breaches in IE and Windows so they can have all the negative publicity when they are discovered. It doesn't make sense.
<< Well, good luck and I am always interested in the resolutions. But, my stance can be re-read just a few lines above -- Desktop OS and common desktop motherboards (non-server boards), and especially "colorful" XP does not bring SCSI to mind when thinking of storage interfaces. >>
Again, what gives you the idea that XP doesn't bring SCSI to mind? Do you have any proof? Any papers? Or are you just looking for a SIMPLE explanation to what is a more complex question/problem? Windows XP is NT 5.1 Windows 2000 is NT 5.0. They are the same basic building block.
SCSI reads are equal if not better than Windows 2000.
SCSI writes are seriously subpar than Windows 2000.
It is more than likely a bug. You make it seem as though Microsoft is purposely neutering Windows XP SCSI performance so that more people will stick with an almost 3 year old Windows 2000. Where's the logic in that? There IS no logic in it. Microsoft is moving EVERYONE over to the NT 5.1 kernel along with 64-bit Windows XP and Windows.NET server. Do you think that Microsoft actually WANTS to give people a reason to stick with an older OS and miss out on some $$$? Come on, you gotta do better than that