Change to MSINSTALL for XENIX Pascal

Product Version(s):
Operating System:   XENIX
Flags: enduser |
Last Modified: 24-FEB-1988    ArticleIdent: Q10280

PRODUCT:  PASCAL/3.30

DESCRIPTION:
Filenames in Pascal, Fortran, and C are the same in the same directory.
The libraries have the same names as the C libraries but different content.
This means to us that you cannot have Pascal, C, and Fortran installed at
the same time !

MICROSOFT RESPONSE:

We named these files with the same names because they are exactly the same
files.  The FORTRAN and Pascal runtimes needed portions of the C runtimes,
so we included them as is.  There should be no problem copying these all on
1 directory as long as the user copies the latest ones over the older ones.

Because of possible confusion, we have rewritten the install program
(msinstall) to do checking for the file creation dates.  What the compiler
does now is warn the user that if there are old versions of the libraries,
it WILL NOT write over these libraries.  It writes these libraries (if they
are present) out to temporary files.  Then it checks to see if there are
temporary files (i.e. there were libraries present before msinstall was
invoked) and if they are present, it copies these original libraries back
to the filenames that the compiler looks for.

If the user later wants to use the new libraries, the install program can
be run again, after the original libraries are renamed to different
filenames. Please note that these C libraries ARE necessary for Pascal and
FORTRAN now. You can indeed have C, Pascal, and FORTRAN on one system.
Indeed, you can have different versions of each of these products on the
same machine also.

If you want to have different versions of the same product on the same
machine, you may do one of the following:

(1) Alter the msinstall program.  The msinstall program first checks to see
if there are current C libraries.  If there are C libraries already
existing on the system, msinstall will rename all of these copies of the
libraries.  It then checks to see if there are these old library files. If
there are old library files, it copies these files back into the original
names, which are the filenames that the compiler searches for.  What you
can do is delete the section of the msinstall program that copies the old
library files back to the original filenames.  This would mean that then
the msinstall program will backup your library files, and then install the
new versions of these files.  This would be very simple to do.

(2) Alter the cl driver.  Create a driver that would look for the filenames
of the old library files instead of the new files.  Then you could use
multiple versions on your machine, invoking the newest version with the cl
driver and the older version with your altered driver.  This would be more
complicated and would require a programmer with more skill, but it is
possible.

If any users have additional questions about the installation procedure, we
would suggest that they first read the msinstall program to see what it
does, and then contact Microsoft OEM customer support with specific
questions.
