Updates To SQLServer 2000 DLL's When 2005 Client Tools Installed

Hi,

I have many sql 2000 DTS packages that I support from my development workstation  running v2000 sp4. Packages are altered on the development machine and then go through a normal release mechanisms to production via testing servers etc.

I have recently installed the client tools for SQL Server 2005 on my desktop to evaluate the product.  The 2005 DB instance is running on a seperate server.

So, I have dev edition of sql 2000 and 2005 client tools (including BI Dev studio etc) on my workstation.

I have recently had to make changes to a 2000 DTS package and used my 2000 enterprise manager to do so. No Problem- saved and tested fine on my workstation. 

But when I try and release it to another server, or open the package using enterprise manager from another machine that does not have sql 2005 installed - I get an error message 'Unspecified error'.  This I've seen before when trying to open packages created in v2000 , using v7 or where the service packs are different between machines.

Digging around my workstation and comparing some of the DLLs I know to be required to distribute DTS  packages (from RDIST.txt) it seems that some of the SQL 2000 dll files have been updated by my 2005 installation. 

E.g

DTSFFILE.DLL on my machine is 2000.85.1054.0 whilst on any 'clean' 2000 machine is at version v2000.80.760.0

Surely it cant be right that SQL 2005 has newer versions of components for SQL 2000 than is available with the latest SP for the actual product! Especially considering that the installation of 2005 does not even allow you to edit 2000 DTS packages through the management studio without a 'special' download' of the feature pack,(whihc by the way does not work very well either)

So am I to conclude that you can not run side by side installations of SQL 2000 and 2005 on a single machine and expect 2000 to run as it did previously !!!