Skip to main content
R
ryang14-Alexandrite
14-Alexandrite
May 20, 2011
Question

Pro/Intralink 3.4 M062 and Windows 7 64-bit

  • May 20, 2011
  • 1 reply
  • 7002 views

I know how to get Pro/Intralink to run on Windows 7 64-bit, but my question is if there is anyone out there that is currently running this environment in production and if so what issues have you experienced. Due to the "unsupported" status by PTC of Pro/Intralink, we hesitate to change our standard workstation configurations to a Windows 7 64-bit platform. However, many of our Pro/Engineer users could benefit from this.

1 reply

T
ToddSwartz10-Marble
10-Marble
May 31, 2011

We have about 20-30 users running on the Win 7-64 bit. No real issues to speak of other than what you have likely found about running the javac in compatibility mode. Other than that, I have not noticed any differences from Win XP.

We see some issues around printer drivers etc and other software, but none from Intralink or Pro/E (both Wildfire 3 & 4)

F
FilipeDuarte1-Visitor
1-Visitor
August 7, 2011

Hi Todd,

I was able to get Pro/Intralink 3.4 M062 to work in 64-bit Windows 7 following tips by DHLewis. I then created a workspace called test. I also managed to install WF 4.0 M170 for 64-bit XP and Vista and it works OK independently or when selecting Workspace menu Intralink "Launch Pro/Engineer - No Workspace. Unfortunately I am unable to get Pro/E to work in linked mode with Intralink. The error message in std.out reads "ERROR: cannot register workspace "test"."

Can you help me to fix this?

D
DHLewis13-Aquamarine
13-Aquamarine
August 11, 2011

Filipe,

Have you looked at the proilink.bat file to verify that the path's for the variables to Pro/E are correct?

the variables that control linking in the bat file are:

PROE_DIR and PROE_START

PROE_DIR is set to the root folder of the Pro/E Install (Location where the bin folder is)

PROE_START is set to the command run to use Pro/E (If you want to choose the configuration use ProE.exe, or else use the .bat file name here)

Also make sure that your .psf files have the correct Intralink Dir and command defined.

That should be everything needed for the link to work correctly.

David

Terms & ConditionsCookie settingsAccessibility statement