Well MS is famous for releasing code that is "not ready for primetime" and certainly there may be a bug or two with some software that wasnt designed to run on XP specifically. Thats kinda expected as I see it. I run several labor intensive software packages on various XP machines at the office. Mainly just games and typical home uses software at the house. No problems. Hey, different strokes. Didnt work out for you. Too bad. Its a pretty significant upgrade IMO and rock solid after I changed all the drivers to XP specific ones that were available. I guess, after some retrospect, I never really had any problems with 2K either though. Still running Webserver, DB, Mail server software on a Win2K server farm and never have to reboot though I do anyway periodically. Win2k Pro workstations that maintain fairly consistent stability as well. So I suppose I could defer and say not such a significant improvement over 2K but unless its a specific problem with a software program or suite, I wouldnt blame the issue on XP on the whole. On the contrary, on the several dozen machines I take care of that have it on there rigs as well as the evergrowing machines I support, very solid. Mileage varies from user to user so it's not particularly hard to imagine someone having issues like yourself.