On Mon, 17 Feb 2003 07:51:50 -0800, "Hugo Hernandez"
hernandez at wnco dot com> wrote:
>Does anybody know if going from Win2K to XP decreases the performance of a
>CAD station?
If so, not enough to notice the difference. And if it does, it's
invariably because the machine is not properly tuned to XP. That means
turning off a lot of the extra "services" that Microsoft put into the
product, that do nothing but slow modern hardware down to the speed of
obsolete hardware.
I will say I like XP better than 2K, but only after I've sufficiently
killed off all of those insipid things.
>Our company is contemplating a systemwide (about 10,000 computers) upgrade
>from Win2K to WinXP because of some compatibility issues on some of their
>applications.
I have a hard time believing that you have apps that will be "more
compatible" under XP than they would be under Win2K. Over NT, sure -
but most apps out there are designed for Win2K and just happen to run
fine under XP. Some, however, do not run so wel or need patched.
>As part of their upgrade project, they have included money to
>upgrade all P-II and older systems to P-III 1.8 Ghz. systems.
That's an upgrade???
P-IIIs are dated, old, decrepit technology. Move to P4s or Athlon XPs,
2000MHz or better.
In general, AutoCAD runs about the same under both 2K and XP. However,
there is one HUGE compatibility problem - printers. Specifically, if
you set up printers with common PC3 and PMP files located on a server,
you must set aside a folder for Win2K machines and XP machines, since
the PC3/PMP files are proprietary to one OS. If you don't, your
machines will get the dreaded "null pointer" error when you go to
print.
If you set up PC3s and PMPs on each individual station (which I do not
recommend) you won't have this issue.
Matt
mstachoni@comcast.net
mstachoni@bhhtait.com