Browse Prior Art Database

Multi-System Files Environment Builder

IP.com Disclosure Number: IPCOM000106574D
Original Publication Date: 1993-Nov-01
Included in the Prior Art Database: 2005-Mar-21
Document File: 2 page(s) / 112K

Publishing Venue

IBM

Related People

Jacobs Jr, RL: AUTHOR [+3]

Abstract

When installing software files, it is necessary to coordinate the changes to the configuration of the workstation to accommodate the software files installed. This invention identifies and modifies the correct system environment files associated with a workstation in which software is being installed regardless of the current operating system of the workstation at the time.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 48% of the total text.

Multi-System Files Environment Builder

      When installing software files, it is necessary to coordinate
the changes to the configuration of the workstation to accommodate
the software files installed.  This invention identifies and modifies
the correct system environment files associated with a workstation in
which software is being installed regardless of the current operating
system of the workstation at the time.

      A software application can be designed to execute on a machine
with an OS/2* environment, DOS environment, or both.  The ability to
execute a program under any environment requires certain
environmental commands to be issued so as to allow access to the
application's files and libraries.  These commands are issued within
the systems configuration files and are executed when the environment
is first accessed.  To prevent a contrast of commands when accessing
different environments, certain files are used for a particular
environment.  The CONFIG.SYS file will hold the statements that are
executed for the machine regardless of the environment.  The
AUTOEXEC.BAT file retains the commands for the DOS environment only,
and the STARTUP.CMD file keeps OS/2 related statements.  To
manipulate certain programs for certain environments, statements are
placed within the different system files as needed.  A software
application which will execute only in DOS environments needs only to
modify, at the least, the AUTOEXEC.BAT file.  Likewise, if an
application needs to be started each time an OS/2 environment is
started, the STARTUP.CMD can be modified.

      A dual bootable machine, one in which the OS/2 and DOS
operating systems are both installed on one machine, will have five
system files.  Each one of these files will need to be modified
accordingly depending on the package to be executed (figure).

      It is possible that with the changes of the system files,
errors could occur which would cause the environment of the
workstation to be incorrect and non-functional.  An archive of system
files needs to be generated so as to recover from any errors that may
occur.

      This program will determine the environment of the workstation
in which the software is being installed.  It evaluates if the
workstation is running on a dual bootable machine, then determines
what environment it is under.  The correct system configuration files
will be accessed based on this information.

      Three specialized files are used by this program to rebuild the
system configuration files.  The base environment file is
automatically generated and contains the original statements from a
user's system configuration file.  The user environment file is used
to allow users the capability to modify their system configuration
files instead of directly modifying their system files, which would
eventually be overwritten.  The package environment file contains the
statements that are to be added to the system configurat...