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?

F
FilipeDuarte1-Visitor
1-Visitor
August 11, 2011

David,

The problem was that I was using a SMS installation package for 32-bit Windows!

I have reinstalled INTRALINK with the original media and applied the changes you suggested to javaw.exe and the start /B ... and now Pro/E and Intralink work in a linked mode.

Thanks a lot for your reply -- it made me review the proilink.bat file and then I realized that there was something wrong with the installation.

Filipe

Terms & ConditionsCookie settingsAccessibility statement