I would suggest working with Academic Support on the startup failure. (3) Should I worry that Creo 3.0 won't run at all on these machines? (2) I see no difference in performance, but I only opened simple parts and assemblies. (1) Could this be a difference in the Creo builds? Can anyone suggest any other reason that the two systems would behave differently - other drivers, registry keys, etc?
Once it's running, I can set the graphics to opengl (using file->options->configuration editor), and it continues to run, and I can restore the last session and it will set the graphics to opengl and run OK, but I can't start it without the config.pro file that sets it to win32_gdi. We had seen this before on other machines, so I created a config.pro file with the line "graphics win32_gdi". Today I installed Creo 2.0 on the other one, and it wouldn't start up (gives a fatal error message). We installed Creo 2.0 (M070) on one of them during build season (late January/early Feb) and the install went smoothly and everything ran fine (and continues to run well). I have verified that the graphics driver version is the same on both machines and that both installed Windows updates recently. I have two nominally identical machines - Dell Optiplex 9020 with Intel graphics, running Windows 7 64 bit, purchased at the same time, identical hardware and nominally identical update history, similar software installed. I am a mentor for FRC Team 2877 - The Ligerbots, and one of my tasks is to build our Creo skill base over the summer to put us in a better position for the next build season.
0 kommentar(er)
