Kbase 1790: BTOS Installation Errors and Things to Look Out For
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
BTOS Installation Errors and Things to Look Out For
911022-ptg01There are several bugs that have been discovered in the installation of
BTOS/CTOS v6.2G04. Specifically, the scripts refer to error codes of
which there is no known reference and which do not display any
identifying text which can be used in identifying the problem, such as
invalid control code, serial number, etc.
The following is a list I compiled of these errors and what I did to
create them:
1. Enter past version number and receive -
Install Error (14):
2. Enter Past serial number and receive -
Install Error (9):
Install Error (10): unable to open build file
3. Enter Past control number and receive
Install Error(10): unable to open output build file
Install Error(11): unable to open output build file
4. Enter control codes out of sequence and receive -
Install Error(6):
5. Enter past company name and receive -
Install Error (13):
6. Enter invalid SN/Control Num for product being installed and
receive -
Install Error (5) :
Note : At this point installation abnormally terminates.
7. Entering serial number in incorrect format and receive -
Install Error(6) :
A second bug should also be noted. On the BTOS/CTOS platform, command
references are kept in command files, which describe command name,
command template, and run file to execute when this command is
executed. Login accounts are assigned to a specific command files with
the default being [sys]<sys>sys.cmds. During the BTOS/CTOS
installation, the user is prompted for the command file that should be
used to store commands Progress installs. If that command file does not
already exist, then the installation will terminate abnormally,
the command file is not created, and the commands will not be installed.
There is also a third quirk about the BTOS/CTOS installation. If you
are installing from tape, Progress does not complete the installation
for you. This is the default action. Progress will execute through the
installation prompting for installation information and then state that
installation is complete. It is not complete. The customer must use the
SUBMIT command to submit from processing the file InstallProgress.sub
from his current volume and directory. This step is not necessary when
installing from disk.
Progress Software Technical Support Note # 1790