Skip to main content
N
nhanratty1-Visitor
1-Visitor
June 28, 2010
Question

Pro/ENGINEER Installation Directory

  • June 28, 2010
  • 11 replies
  • 2464 views

Hi everybody

Many years ago as an applcation engineer for PTC I was advised that youshould not install Pro/ENGINEER into the Program Fles folder on a PC - the reason being Pro/ENGINEER did not like the space between Program and Files in the folder title. Consequently every Pro/ENGINEER installation I have ever carried out has always been into a folder like

C:\PTC\proewildfire3

I'm just curious to know ifis this still relevant advice. Does Pro/ENGINEER still get upset by the space? Did it ever get upset by the space?

Regards,

Neal

11 replies

B
BobFrindt1-Visitor
1-Visitor
June 28, 2010
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
Sr. Designer
Parker Hannifin Corporation
Parker Aerospace
Gas Turbine Fuel Systems Division
8940 Tyler Boulevard
Mentor, OH 44060 USA
direct (440) 266-2359
cell: (216) 990-8711
fax: (440) 266-2311
-
www.parker.com



Neal Hanratty <->
06/28/2010 07:13 PM
Please respond to
Neal Hanratty <->


To
-
cc

Subject
[proecad] - Pro/ENGINEER Installation Directory






Hi everybody
Many years ago as an applcation engineer for PTC I was advised that you
should not install Pro/ENGINEER into the Program Fles folder on a PC - the
reason being Pro/ENGINEER did not like the space between Program and Files
in the folder title. Consequently every Pro/ENGINEER installation I have
ever carried out has always been into a folder like
C:\PTC\proewildfire3
I'm just curious to know if is this still relevant advice. Does
Pro/ENGINEER still get upset by the space? Did it ever get upset by the
space?
Regards,
Neal


Site Links: View post online View mailing list online Send new post
via email Unsubscribe from this mailling list Manage your subscription


Use of this email content is governed by the terms of service at:

privileged. It only should be used or disseminated for the purpose
of conducting business with Parker. If you are not an intended
recipient, please notify the sender by replying to this message and
then delete the information from your system. Thank you for your
cooperation."
A
Anonymous
June 29, 2010

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

L
lsrutkowski1-Visitor
1-Visitor
June 29, 2010


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.

In Reply to Neal Hanratty:

Hi everybody

Many years ago as an applcation engineer for PTC I was advised that youshould not install Pro/ENGINEER into the Program Fles folder on a PC - the reason being Pro/ENGINEER did not like the space between Program and Files in the folder title. Consequently every Pro/ENGINEER installation I have ever carried out has always been into a folder like

C:\PTC\proewildfire3

I'm just curious to know ifis this still relevant advice. Does Pro/ENGINEER still get upset by the space? Did it ever get upset by the space?

Regards,

Neal

D
dgschaefer21-Topaz II
21-Topaz II
June 29, 2010
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
D
DamianCastillo1-Visitor
1-Visitor
June 30, 2010
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. 🙂
N
nhanratty1-VisitorAuthor
1-Visitor
July 16, 2010
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


P
patharris1-Visitor
1-Visitor
July 16, 2010
Hello All,
A related issue that was touched on by some responders was the location of
the Pro/E model files and their paths.

Length of path may become an issue with backups of the various model files
if you choose to put them in Documents and Settings\My Documents\Guy with
very long name\etc\etc\etc folder. The issue is that a hard disk drive can
manage a longer path than many removable medias such as tape, CD ROM, maybe
DVD, etc. The models will work fine on your computer and you think you have
a good backup, however when you need to restore a backup you find that the
long paths have resulting in the backup software truncating names and
created a referencing issue making it very hard to get the files back into
the correct location. For this reason our project setup method locates
Pro/E project directories on shorter paths (not using interlink, etc.), not
in "Documents and Settings".

Everybody claims that they back up onto removable media, even if they don't.
If you have a contractor or collaborator who claims to be backing up, one
way to confirm is to look at the length of their paths. If any paths are
over 128 characters you may want to check further and confirm that the
backups can actually restore correctly.

Regards,

Pat Harris
Principal Engineer
Product Design, Inc.
5133 Washington St., Suite 9
Downers Grove, IL 60515
L
lwh1-Visitor
1-Visitor
July 17, 2010

Even if it seems to work most of the time, using spaces or special characters may have unexpected side effects.

Using ä (a-umlaut) in a workspace name f.i. kept ProE from loading drawing formats...

P
puetzc1-Visitor
1-Visitor
July 19, 2010
I read in an online blog (JoelonSoftware

The proper question is "How often do you perform a trial restore?"
D
dperry1-Visitor
1-Visitor
July 21, 2010

Just got through with an install of WF4.0 with Intralink 3.4 (M062). Space in the folder name for the install of WF4.0 ... By PTC install CD default caused me grief!! Linked session of Pro-E and Ilink kept giving "loadinpro" error and loss of viewed data in the workspace window. The initial setup install for WF4.0 created a folder named "proeWildfire 4.0" the fix was to have it install to "proeWildfire_4.0" or rename theexisting folder and re-run setup. That fixed the problem.

Dave

In Reply to Neal Hanratty:

Hi everybody

Many years ago as an applcation engineer for PTC I was advised that youshould not install Pro/ENGINEER into the Program Fles folder on a PC - the reason being Pro/ENGINEER did not like the space between Program and Files in the folder title. Consequently every Pro/ENGINEER installation I have ever carried out has always been into a folder like

C:\PTC\proewildfire3

I'm just curious to know ifis this still relevant advice. Does Pro/ENGINEER still get upset by the space? Did it ever get upset by the space?

Regards,

Neal

Show more replies
Terms & ConditionsAccessibility statement