Originally posted by: nan0bug
Originally posted by: Trygve
You mean *added* bugs, driver and software incompatibilities, and a deliberate effort to make any basic operation that you'd want to do take a few extra mouse clicks than it used to? The annoying "visual styles" I can shut off; I haven't figured out how to fix the rest of the added annoyances.
Oh, yeah, and new "fixes" and "service packs" coming out all the time that disable whatever software I need to use.
I get things done just as fast or faster on an XP machine than I do on a 2K machine. A little effort in customizing things to your liking goes a long way. Only newbies use mice for most tasks anyway. Keyboard shortcuts are so much better.
I've also never had any software incompatibilities from 2K to XP. I'd be interested in hearing what software is giving you problems.
Well, I bought XP Pro because the current version of Avid Xpress Pro (why is *everything* "pro" these days?) only supports XP Pro. ...but it's not compatible with all of Microsoft's "bug fixes," some of which will totally screw up Avid software (fortunately, Avid's technical support section has information on this).
However, installing XP disabled some rather important functions of Adobe Premiere, notably the ability to capture and output video on my system. So you have to upgrade to Adobe Premiere Pro 1.0 (there's that "pro" thing again) which fixes that problem. Adobe has no plans to release a patch for Premiere 6.5, the last "non-pro" version.
But XP SP1 screws up Adobe Premiere Pro 1.0. Fortunately, there's a fix for that. It's called "Premiere Pro 1.5"...but you have to pay for that upgrade, too. (I needed to upgrade After Effects Pro (there's that word again) anyway and some of the other Adobe software I use, so I would have gotten the upgrade regardless, but, still....)
Now, I still haven't gotten the audio working correctly on my SDI card (Osprey 2000 Pro DV--and since it's "pro" too, it ought to be supported, right?) and, though it's less of a big deal, XP keeps "losing" my MOTU 828 firewire audio interface and even when it does recognize it, I haven't been able to get all of its functions working properly yet--but I should probably upgrade it to something more modern anyway.
I didn't have nearly as much trouble going from NT 4.0 to 2K (apart from the drop in stability). The biggest annoyance I ran into there was that Win2K totally screwed up most of my fibre channel HBAs. Of the ones I was using, only the Qlogic models would work with 2K. But, then, the ones that 2K couldn't handle were still supported under Solaris, so that problem could be fixed with a little bit of hardware swapping. Unfortunately, I don't have a supply of spare video and sound hardware lying around to start swapping until I can find out what XP is comfortable with.
Facebook
Twitter