All
Just a summary of the replies I got regarding my query on installation
folder for Pro/ENGINEER.
Thanks to everyone that responded...some interesting viewpoints.
I think I'll stick to the PTC folder...
Regards
Neal,
We started with Unix before moving to Windows and I too was told spaces
were bad. Now, with several years of installs in the Program Files
directory and no issues I don't believe it really matters anymore
Mike Brattoli
As I recall this was only relevant for the old installations back on the
Sun sparc and Silicon Graphics UNIX based boxes and such. The space and
special characters no longer seem to matter.
Since WF 2.0 (and we are up to WF 4.0 now) we have loaded ours in a
folder that is named like this
C:\Program Files (x86)\proeWildfire 4.0
No issues, no problems
Bob Frindt
Hi Neal,
I'm still doing it on any install that I do. Although, I have my Start
In directory in 'Documents and Settings' pulling my config files with
spaces and such with no issues. I'm pretty sure that retrieving model
files from folders with spaces is still a no-no.
Best Regards,
Matt Larsen
Hi,
Yes, this is a good advice even today, though the implications of not
following it are much less severe today than they were in the past.
If you use Pro/Toolkit, it really dislikes Pro/Engineer installed in a
folder with a space in its name.
If you keep your libraries with ProE and happen to use a search path
file, every line with a space in it will not be searched.
Pointing Config.pro options to a library with a space in its name might
not work either.
It is still the best to define your own installation directory without a
space in its name.
All the best
Uriel Avron
Hi,
We have put 3 and 4 in program files folder without any problems. No
problems with pulse either.
Best regards
Stephen White
From what I have been able to tell for working with 2001, WF3, WF4, and
WF5, the problem with spaces in the folder path is no long an issue for
Pro/ENGINEER. Other PTC products (Intralink, Windchill, etc) still have
problems on occasion and if they link up with Pro/E, then you may see
that some options do not work.
The one example I can think of right now is if you have Pro/E installed
to a directory with a space in it (ie, c:\ptc\wildfire 4.0\), then
Intralink 3.4 will be unable to run the Import/Export command.
Lawrence Srutkowski
Yes, it is still relevant to stay away from spaces and special
characters (such as punctuation.Although PTC claims that they meet
Microsoft requirements for such, it is not 100%. Every few months,
someone posts a problem related to this. We had one less than a month
ago in which it was found that Windchill could not properly deal with
the java path if it contained special characters.
Gerry Champoux
I think, it quit being an issue after WF was released, it might have
been a little after that, because we didn't go to WF immediately but
picked up on it with a later build.
Brian S. Lynn
It's been the default location for Pro|E for many revs, at least back to
WF1, maybe 2001. We've used the default path offered (into the Program
Files folder) since then and have had no issues.
There are areas where Pro|E continues to choke with spaces in the path
or file name, but this doesn't seem to be one of them.
Doug Schaefer
The standard install from the PTC disc will use spaces. Out of habit, I
don't use them because the underlining code in PTC has Unix traits or at
least I have seen enough issues that I believe it does.
I install under \ptc\wf4-m110
I like to indicate the build versions because I run Pro/E installation
on a server and not the users computer. This allows for easy upgrades
and downgrades as needed. 🙂
Damian Castillo
Regards,
Neal Hanratty
