Community Tip - Your Friends List is a way to easily have access to the community members that you interact with the most! X
We are setting up CREO 2.0 M020 Schematics.
We have gotten to the place that we want to print out our schematic. When I hit
the OK from the Print screen, all that happens is the Print box closes and I do
not get my windows printer or anything. I cannot even do a print preview. Has
anyone else seen this? Is there a fix for this? My consultant has the same
build and Print works just fine on their computer.
Thank you,
Brian Toussaint
Does your consultant have meeting software so they can run your computer and look at things. That has really helped us.
Without that ability, my next suggestion is to make a word document with ALL your steps and screen captures of every window that you edit. When I am doing this for instructions, I use windows built in capture routine to paste the screen into paint, then circle anything I change in red.
I use a word document with two columns, one for the text and one for screen shots that show the results.
You might have to show them your printer installation. I just click on Win in the printer selection so that it brings up the list of windows printers.
We have schematics installed at G:\engApps\Creo\Schematics1\Creo 2.0\Schematics
We are using 2.0 M020
That is a networked drive that is used for all of our engineering software.
We also have Windchill 10.2 and the Workgroup Manager installed.
Our printers are in all sorts of places with our IS group setting up the installation but Schematics brings up the dialog to go to any of the installed printers.
One thing - a wild chance - Could your printer window be popping up behind Schematics. I had that happen with other software that I had full screen. I had to shrink the program window and move it out of the way before telling it to print.
I finally got a response from tech support. Seems that the
space in my path, D:\ptc\Creo 2.0\Schematics, is what caused the issue.
Once I removed the space, then it was good to go.
Thank you,
Brian