Win 7

[rollinsn]

Hi folks,

Any hints or special knowledge to run WF2,4 and 5 on Win7?

Does the XP "emulator" need to be installed / running?

Thanks,

-Nate

This email may contain material that is confidential, privileged and/or attorney work product for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[lococnc]

Running WF5 on Win7 x64 just fine for the last 3 months.

[lsrutkowski]

I have had several computers up and running Wildfire 4.0 m130 on Windows 7 (64-bit) for the past month. Pro/E has worked just fine. Intralink (we are on 3.4 m062) has required a bit of tweaking.

[ptc-83293]

Lawrence,

In your reply you mentioned having to "tweak" something to get iLink 3.4 M062 to install on Win7. What was it? I've been trying but can't get it to install on Win7x64.

[lsrutkowski]

Below is a copy of my notes. In addition to what is below, make sure there are no spaces to the loadpoints of either Intralink or Pro/Engineer or you will not be able to use the Import/Export function of Intralink. Intralink runs the Pro/E import and export function and cannot find the Pro/E laucher if there is a space.

There were 3 major items that needed to be fixed with Intralink 3.4 m062.

1. The “...\i486_nt\jre\bin\javaw.exe” needs to be set to run in Windows Vista compatibility

(this is necessary for Win7 to launch Intralink 3.4. Be sure to use Vista and NOT Vista Service Pack 1 or 2)

2. The “proilinkrelease_3.4.bat“ file will need to be changed to include “-Dsun.java2d.noddraw=true” in the application launch line (3rd or 4th line from the end of the file, my line looks like: “start /B %prodir%\%mc%\jre\bin\javaw -Xmx256m -Xss8m -Dsun.java2d.noddraw=true -jar %PRO_DIRECTORY%\java\lib\Intralink.jar -l %luknfeel% %intralinkparams% >> "%logfile%"”)

(This is not necessary for the application to run, but it does allow the use of the Aero theme set while using Intralink. I have found the document flip function (Windows + Tab) to be invaluable while working, but it only operates with Aero. Without the change above, the system will automatically switch to the default, non-Aero theme when you launch Intralink)

3. Once again in the “proilinkrelease_3.4.bat“ file, the machine type needs to be specified after the check in order to find the loadinpro.exe file. This section is a little harder to find, but it looks like this:
“
set proe_mc=%mc%
if EXIST %PROE_DIR%\%proe_mc%\obj\loadinpro.exe goto fbskp
set proe_mc=x86e_win64
if EXIST %PROE_DIR%\%proe_mc%\obj\loadinpro.exe goto fbskp
set proe_mc=i486_nt
:fbskp

set PDM_LOADINPRO_PATH=%PROE_DIR%\%mc%\obj\loadinpro.exe
“

I changed the “%mc%” to “x86e_win4” in the last line so it now appears as:

“set PDM_LOADINPRO_PATH=%PROE_DIR%\x86e_win64\obj\loadinpro.exe”

This just sets the file to ALWAYS look in the x86e_win64 directory (which is the proper directory for a 64-bit OS) and keeps Intralink synched up with Pro/E.

-Lawrence Srutkowski

In Reply to Christopher Welcher:

Lawrence,

In your reply you mentioned having to "tweak" something to get iLink 3.4 M062 to install on Win7. What was it? I've been trying but can't get it to install on Win7x64.

[DamianCastillo]

I sure hope the new CREO Kernel was created for Windows. I am tired of the Unix baggage Pro/E currently has. Oh, sorry.... CREO elements/pro


"Too many people walk around like Clark Kent, because they don't realize they can Fly like Superman"

[ptc-158344]

They can fly like Superman around PlanetCreo. (hehehe)

[ptc-83293]

Thanks, Lawrence!



Our problem is just getting M062 or M070 to INSTALL! Currently it crashes
during the initial launching of the installer, whether it is launched from
the CD or shared network drive.



If we can get it to install, then we'll try this.



Thanks again,



. Chris

[ptc-83293]

Thanks to all that replied. We got it!




FYI - as expected, PTC support (both on the phone and online) politely told
me to eat $&%! because 3.4 was EOL. (understandable)



Here's what we did, given consistently named <proe_loadpoint> and
<proi_loadpoint> folders/locations and executables for ProE and ProI:



[1] Installed ProE (WF4/M150) in the Win7x64 machine.

[2] Since we had issues installing Intralink 3.4 M062, we left our current
M040 install (or installed M040) on the Win7x64 machine (maintains registry
entries, etc.).

[3] Renamed M040 <proi_loadpoint> folder.

[4] Since the M062 installer (and ptcsetup.bat) crashes (even when launched
"As Administrator"), we installed it on an XPx64 machine and configured the
Intralink batch file to correctly work with our ProE (WF4/M150)
installation.

[5] Copied the entire <proi_loadpoint> folder from the XPx64 machine to the
Win7x64 machine.

[6] Set java to run in Windows Vista compatibility (this is necessary for
Win7 to launch Intralink 3.4). Find the "javaw.exe" executable in the
<proi_loadpoint>\i486_nt\jre\bin folder, right-click and select Properties.
Click the Compatibility tab and set "Run this program in compatibility mode
for:" then select "Windows Vista". Be sure to use Vista and NOT Vista
Service Pack 1 or 2.

[7] Edit the javaw line in the Intralink executable (.bat file) to include
"-Dsun.java2d.noddraw=true" in the application launch line (3rd or 4th line
from the end of the file). My line looks like (yours may differ):



start /B %prodir%\%mc%\jre\bin\javaw -Dswing.useSystemFontSettings=false
-Xmx256m -Xss8m -Dsun.java2d.noddraw=true -jar
%PRO_DIRECTORY%\java\lib\Intralink.jar -l %luknfeel% %intralinkparams% >>
"%logfile%"



Thanks to all of you who offered suggestions!!! Since it is increasingly
difficult to purchase new hardware with XP, I'm sure this will come up more
often.



. Chris



Christopher J. Welcher
Director of Engineering Services



Valley Engineering Group, Inc. | 1729 Rutan Drive | Livermore, CA 94551

925.371.5015 (Phone) | 925.371.5013 (Fax) | 925.525.4095 (Mobile)

<">mailto:chris.welcher@vegonline.com> chris.welcher@vegonline.com |

[bmozley]

ProE users,



Has anyone had any problems with running Wildfire 3 on a windows 7 - 64
bit machine?

I'm getting some errors, like my config files do not recognize directory
paths, my ProE icon does not recognize the bat file, the error message
is : "the item ' proeconfig.bat' that this shortcut refers to

Has been changed or moved, so this shortcut will no longer work
properly." I have tried creating a new icon, same problem. I even did a
complete uninstall and install of Pro Wildfire 3, and when you launch
the bat file <ptcsetup.bat> it should run, it doesn't. Any advice?



Brad

WF3 / W7-64

[PAULKORENKIEWIC]

maybe WHERE the program files are? With 64bit systems there is a
C:\program files and a c:\program files(x86). IF you "let" the install
program have it's way, I think it would dump things in the later which
might screw things up.

An old adage that I've always stuck to was to NEVER let the install have
it's own way. I've always forced the install to do it's thing in
C:\PTC\<wildfire4 or=" whatever=">... That way, when we have to do
multiple installs, I do the install on my machine, and then just copy
those files to the rest...

just a thought...

Thanks...

Paul Korenkiewicz
FEV, Inc.
4554 Glenmeade
Auburn Hills, MI., 48326

[dgschaefer]

We installed WF3 x32 on my Win7 x64 box and used the default settings (I
think, I didn't' do the install but that's our practice) and it put it
in the standard Program Files folder. It runs fine and we have an older
build that technically isn't Win7 verified.



Now, we don't use the PTC batch files, we have our own which calls
proe.exe directly.



Doug Schaefer