ProI 3.3 on 64 Bit XP - Possible?

[ptc-671095]

All,

Our location is stuck on Intralink 3.3 due to a server situation that is
another story. All of our computers are running standard XP except that
we just were issued a new workstation that has 64 bit XP pro by
corporate for a new user.

Has anyone been able to run Intralink 3.3 on a 64 bit platform? I have
tried and the start up batch file just runs and does not fire up
Intralink. Is there a setting that might allow Intralink to run such as
a legacy mode for 32 bit applications?

Thanks for any input that might help our situation.

Dwayne Quatier
GE Healthcare

[JimAugeri]

Dwayne,

I have been away from this for some time now, but I do have a 64-bit Dell T5500 running ILINK 3.3, M022. The problem is getting it to work reliably with Pro/E - and I have NEVER been able to get it to work with 64-Bit Pro/E (WF2) only the 32-bit version. In addition, it took a good bit of hacking through the startup batch file and modifying variables and settings to get it to work at all. So, believe me, I feel your pain!

Jim Augeri

Albuquerque, NM

[scott_rockwell]

Dwayne and Jim,

I'm in the boat!

New 64 bit high end T7500 and stuck with 3.3 m22 until the 9.1 upgrade
is complete. IT has put their qualification requirements in full gear.
They would rather be three builds out of the support window than in the
game with real time production testing. It's not like we would jump to
the bleeding edge. Reckless I know.

So much for the rant ...

I have also had trouble getting 32 bit 3.3 to link with 64 bit 2.0.
Even 32 bit 2.0 has been unsuccessful. I would love to post the receipt
for running Intralink 3.3 M22 and Wildfire 2.0 32 bit (or 3.0, 4.0, 64
bit or any other) and I promises I will if I get there. I have seen the
posts directing the edit of the command bat file "AMD64" to i486_nt ENV
variable. There must be something more.

Is there anyone successfully running 3.3 on XP Pro 64 bit? Maybe with a
virtual machine?

Couldn't be more frustrating - with a Ferrari on a go-cart track.



Scott R

[rrich]

I hear a lot of blame being put on IT departments and who ever. Bottom line is, if you are using ILINK 3.3 and WF2.0 and XP then you are half of the problem. It is time to upgrade on all fronts. PTC cannot be expected to maintain this old stuff and produce and support new stuff. If memory serves PTC did make concessions and supported ILINK 3.4 up to WF4 and maybe WF5. This support was originally going to stop at WF3 and ILINK 3.4 and this was 3+ years ago. The problems and frustrations will still be there with new software too, however they will be different and solvable as new software is being supported. At that point , bandaids, duct tape, and hacked up scripts will not be needed to run your installation.

Keep in mind I am fighting this same battle here too, however we have made the strides to move to the latest software. Currently on WF4 moving to WF5 soon and on PDMLink (windchill). Now our engineering team is lobbying for 64bit win7 and 8gig or more of ram. It is hard trying to convince our IT group of why we need this horse power, but we are collecting ammunition. With only 30 pro/e users out of a company of over 600+ computer users we do not get tons of attention and IT wants a cookie cutter solution.


Ron Rich
Senior Design Engineer
Wet Extractors
TTI Floor Care North America
7005 Cochran Road
Glenwillow, Ohio 44139-4303
Tel (440)996-2477
Cell (440)591-9538

[TerryMcFall]

Yes, but keep in mind it wasn't until this year that IL 9.1 was released with EQUIVALENT functionality to 3.4. The original intention of moving at the WF4 deadline would have put us all on a production version of IL8... a move that only the insane or gifted (both?) admins attempted.

-Ter

[RandyJones]

On 09/30/10 15:53, Terry McFall wrote:
> Yes, but keep in mind it wasn’t until this year that IL 9.1 was released with
> EQUIVALENT functionality to 3.4. The original intention of moving at the WF4
> deadline would have put us all on a production version of IL8… a move that only
> the insane or gifted (both?) admins attempted.
>
> -Ter
>

And to add to this. It wasn't until later builds (M020 ??) of 9.1 until
you could run multiple sessions of Pro/Engineer. Which is functionality
we have been using since Intralink 1.2. My users would have lynched me
if we had migrated to PDMLink before that became available.

Other missing Intralink 3.x functionality:
- exporting objects from one workspace to another
- Delete functionality in 9.1 is horrible when compared to Intralink 3.x.



--
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
1525 E North St
PO Box 5060
Salina, KS USA 67401
email: -
Phone: 785-823-3276
Fax: 785-667-2695
------------------------------------------------------------------------