Is anyone else using this particular NOVERSION technique with Intralink 3.4? It's broken now wi
For some years now, we have used the technique documented in TPI 112366 to help us to manage change with non-ProE files. It's another variation on using the NOVERSION.EXE command. I just confirmed that it doesn't work with M060.
You can read the text of the TPI below.
I suspect that this is broken because of the known SPR which was reported in the past two weeks by Dave Engel and Andrew Mansfield (i.e. that M060 can no longer interpret Windows environment variables in using the NOVERSION command.