Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X
The Windows 7 workaround of having to set Compatibility Mode to Vista on the javaw.exe has caused us heartburn for two reasons:
Well no more! We've discovered that if you add the lineset __COMPAT_LAYER=VISTARTM to your proilink3.4.bat launch batch file, the problem is GONE!!
Apologies if this has been discussed before, but we're excited to have found this! No apparent side effect arise with this setting. Please advise if you find differently.
Good weekend,
G.
Hi George
Thanks for posting: this is a nice little tweak: just added to our startups.
I'd previously devised a registry file for this, but adding to startup is neater.
Cheers
Edwin Muirhead, CAD Manager, Weatherford
ps: FYI the registry entry is something like this:
[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
"C:\\ptc\\ilink\\proiclient34M062\\i486_nt\\jre\\bin\\javaw.exe"="VISTARTM DISABLETHEMES"
In Reply to George Leonard:
The Windows 7 workaround of having to set Compatibility Mode to Vista on the javaw.exe has caused us heartburn for two reasons:
- Compatibility Mode can't be set on programs which exist on mapped network drives (that's how we happily deploy PTC apps here), or at least not permanently.
- For home installations, we had to rely on the user (*shudder*) to make this change to theproiclient3.4\i486_nt\jre\bin\javaw.exeexecutable.
Well no more! We've discovered that if you add the lineset __COMPAT_LAYER=VISTARTM to your proilink3.4.bat launch batch file, the problem is GONE!!
Apologies if this has been discussed before, but we're excited to have found this! No apparent side effect arise with this setting. Please advise if you find differently.
Good weekend,
G.
Jim,
Does your install path for Intralink or Pro|E include a space in it?
The group I am with upgraded to Win7 64-bit (ilink 3.4 and WF4) about a year and a half back and discovered (about 1 month too late) that if you have a space in either install path, Intralink will have some problems working with Pro|E. In our case, because we are installed to ".\PTC\Wildfire 4", the import and export functions kick out an error trying to find "\bin\proe.bat" and we cannot open files direcly from Intralink.
George,
What date code of Intralink 3.4 are you running? This fix was a nice tweak for us and works great with Intralink 3.4 M030 - thanks! However I'm migrating us to 3.4 M062 so we can go to Wildfire 4. Everything has gone smoothly except adding the "set COMPAT_LAYER=VISTARTM" tweak in the intralink startup .bat filesdoesn'twork with M062 - I get a "java.lang.NullPointerException null" in the .pro.log file and the client fails tostart. I have had to revert to setting the compatibility on the javaw.exe to Vista SP2 to get the M062 client to start on Windows 7. Anyone have any idea why this is?
Regards,
Erik
In Reply to George Leonard:
The Windows 7 workaround of having to set Compatibility Mode to Vista on the javaw.exe has caused us heartburn for two reasons:
- Compatibility Mode can't be set on programs which exist on mapped network drives (that's how we happily deploy PTC apps here), or at least not permanently.
- For home installations, we had to rely on the user (*shudder*) to make this change to theproiclient3.4\i486_nt\jre\bin\javaw.exeexecutable.
Well no more! We've discovered that if you add the lineset __COMPAT_LAYER=VISTARTM to your proilink3.4.bat launch batch file, the problem is GONE!!
Apologies if this has been discussed before, but we're excited to have found this! No apparent side effect arise with this setting. Please advise if you find differently.
Good weekend,
G.
Hi Erik
We have it working with M062/M060 here - seems fine, not seen that error. I would check java paths, etc. You never know, someone at PTC Tech support may still help you: I had success the other day with an Ilink 3.4 server issue!! 🙂
Edwin
In Reply to Erik Gifford:
George,
What date code of Intralink 3.4 are you running? This fix was a nice tweak for us and works great with Intralink 3.4 M030 - thanks! However I'm migrating us to 3.4 M062 so we can go to Wildfire 4. Everything has gone smoothly except adding the "set COMPAT_LAYER=VISTARTM" tweak in the intralink startup .bat filesdoesn'twork with M062 - I get a "java.lang.NullPointerException null" in the .pro.log file and the client fails tostart. I have had to revert to setting the compatibility on the javaw.exe to Vista SP2 to get the M062 client to start on Windows 7. Anyone have any idea why this is?
Regards,
Erik
In Reply to George Leonard:The Windows 7 workaround of having to set Compatibility Mode to Vista on the javaw.exe has caused us heartburn for two reasons:
- Compatibility Mode can't be set on programs which exist on mapped network drives (that's how we happily deploy PTC apps here), or at least not permanently.
- For home installations, we had to rely on the user (*shudder*) to make this change to theproiclient3.4\i486_nt\jre\bin\javaw.exeexecutable.
Well no more! We've discovered that if you add the lineset __COMPAT_LAYER=VISTARTM to your proilink3.4.bat launch batch file, the problem is GONE!!
Apologies if this has been discussed before, but we're excited to have found this! No apparent side effect arise with this setting. Please advise if you find differently.
Good weekend,
G.