COSMOSFloWorks 2008 conflict with AutoCAD Mechanical 2009?

Hello, I apologize if this is in the wrong section.

I am a computer technician at an educational institution and wehave SolidWorks 2008 SP4.0 installed in student labs. We also havemany other pieces of software including AutoCAD Mechanical 2009.

A professor reported COSMOSFloWorks would crash when trying to usethe wizard (near the top left of the UI). Upon furtherinvestigation we narrowed it down to a software conflict withMechanical; if it is installed on the system, COSMOSFloWorks wouldcrash when trying to run the wizard. We've eliminated other piecesof software, and we've tried with multiple files. The crash ONLYoccurs if Mechanical is installed. The Event Viewer offers littlehelp (it just says it crashes, which we already know).

We have also tried installing SolidWorks 2008 SP5.0 but the resultis the same.

The student labs are running Windows XP SP3 with the most recentpatches/updates. The computers vary in hardware specs from lab tolab, but are all running at least dual cores at 2.0GHz, and allhave at least 1GB of RAM (most have 2). The file itself is tiny(135KB), and is a .SLDPRT file. It's not a complicated file in anyway. And as already mentioned, we have tried with more than onefile, all with the same result.

Online searches have turned up nothing, and reading any releasenotes on SolidWorks hasn't mentioned any conflicts with otherpieces of software (investigation into Mechanical hasn't turned upanything, either). I am in the process of comparing registrychanges to see if there are any conflicts. The installation orderbetween the two does not matter either; we've tried with SolidWorksfirst and with Mechanical first and both tests resulted in the samebehaviour. Any lab that does not have Mechanical installed can runthe COSMOSFloWorks wizard without error and operates like normal.

Is anyone aware of a conflict between these two pieces of software?Do you have any suggestions on how to remedy the issue or perhaps awork-around? Any insight would be greatly appreciated, thank youfor your time.

- ChrisSolidworksGeneral