Preview | SOLIDWORKS USER FORUM
Use your SOLIDWORKS ID or 3DEXPERIENCE ID to log in.
cschris shaw01/04/2009
Hello, I apologize if this is in the wrong section.
I am a computer technician at an educational institution and we have SolidWorks 2008 SP4.0 installed in student labs. We also have many other pieces of software including AutoCAD Mechanical 2009.
A professor reported COSMOSFloWorks would crash when trying to use the wizard (near the top left of the UI). Upon further investigation we narrowed it down to a software conflict with Mechanical; if it is installed on the system, COSMOSFloWorks would crash when trying to run the wizard. We've eliminated other pieces of software, and we've tried with multiple files. The crash ONLY occurs if Mechanical is installed. The Event Viewer offers little help (it just says it crashes, which we already know).
We have also tried installing SolidWorks 2008 SP5.0 but the result is the same.
The student labs are running Windows XP SP3 with the most recent patches/updates. The computers vary in hardware specs from lab to lab, but are all running at least dual cores at 2.0GHz, and all have 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 any way. And as already mentioned, we have tried with more than one file, all with the same result.
Online searches have turned up nothing, and reading any release notes on SolidWorks hasn't mentioned any conflicts with other pieces of software (investigation into Mechanical hasn't turned up anything, either). I am in the process of comparing registry changes to see if there are any conflicts. The installation order between the two does not matter either; we've tried with SolidWorks first and with Mechanical first and both tests resulted in the same behaviour. Any lab that does not have Mechanical installed can run the 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 a work-around? Any insight would be greatly appreciated, thank you for your time.
- Chris
I am a computer technician at an educational institution and we have SolidWorks 2008 SP4.0 installed in student labs. We also have many other pieces of software including AutoCAD Mechanical 2009.
A professor reported COSMOSFloWorks would crash when trying to use the wizard (near the top left of the UI). Upon further investigation we narrowed it down to a software conflict with Mechanical; if it is installed on the system, COSMOSFloWorks would crash when trying to run the wizard. We've eliminated other pieces of software, and we've tried with multiple files. The crash ONLY occurs if Mechanical is installed. The Event Viewer offers little help (it just says it crashes, which we already know).
We have also tried installing SolidWorks 2008 SP5.0 but the result is the same.
The student labs are running Windows XP SP3 with the most recent patches/updates. The computers vary in hardware specs from lab to lab, but are all running at least dual cores at 2.0GHz, and all have 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 any way. And as already mentioned, we have tried with more than one file, all with the same result.
Online searches have turned up nothing, and reading any release notes on SolidWorks hasn't mentioned any conflicts with other pieces of software (investigation into Mechanical hasn't turned up anything, either). I am in the process of comparing registry changes to see if there are any conflicts. The installation order between the two does not matter either; we've tried with SolidWorks first and with Mechanical first and both tests resulted in the same behaviour. Any lab that does not have Mechanical installed can run the 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 a work-around? Any insight would be greatly appreciated, thank you for your time.
- Chris