用户:随便问我：修订间差异
跳转到导航
跳转到搜索
（→文件文本） |
（→文件文本） |
||
| 第2,705行： | 第2,705行： | ||
</pre> | </pre> | ||
</div></div> | </div></div> | ||
* OS2BETA.ZIP | |||
<div class="toccolours mw-collapsible mw-collapsed"> | <div class="toccolours mw-collapsible mw-collapsed"> | ||
OS2RPRTS.TXT [COMMENTS FROM OS2 BETA TESTERS] | |||
<div class="mw-collapsible-content"> | <div class="mw-collapsible-content"> | ||
<pre width="87"> | <pre width="87"> | ||
| 第3,700行： | 第3,701行： | ||
</pre> | |||
</div></div> | |||
* OS2-2DOC.ZIP [OS2 Beta 6.167 Docs] | |||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
6167DOCS.LST | |||
<div class="mw-collapsible-content"> | |||
<pre width="87"> | |||
This is a listing of the documents that can be found on this diskette. | |||
OVER6167.DOC Overview of the 6.167 version of IBM 32 Bit OS/2 | |||
INST6167.DOC Installation instructions and list of restrictions for | |||
IBM 32 Bit OS/2 internal driver level 6.167 | |||
READ6167.DOC Read me first file for IBM 32 Bit OS/2 driver 6.167 | |||
VMBOOT.DOC Paper discussing the Virtual Machine boot function of | |||
IBM 32 Bit OS/2 | |||
V2-WIN.DOC Information on running Windows applications under IBM 32 | |||
Bit OS/2. | |||
ESLS6167.DOC Installation instructions and list of restrictions when using | |||
Extended Services/2 (version 246) and LAN Services 2.0 (version | |||
281) with IBM 32 Bit OS/2 driver 6.167. | |||
INDBC167.DOC Installation instructions and restrictions for use with IBM | |||
Extended Services/2 Database Manager Client feature. � | |||
</pre> | |||
</div></div> | |||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
ESLS6167.DOC | |||
<div class="mw-collapsible-content"> | |||
<pre width="87"> | |||
Restrictions and Installation Instructions for | |||
IBM Extended Services for OS/2 (Driver Level S1A246) | |||
and | |||
IBM OS/2 LAN Server V2.0 (Driver Level 281) | |||
on | |||
IBM OS/2 Standard Edition V2.0 (Driver Level 6.167) | |||
October 18, 1991 2:16 p.m. | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 & OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver | |||
6.167 | |||
This document contains information of a proprietary nature. ALL INFORMATION CONTAINED | |||
HEREIN SHALL BE KEPT IN CONFIDENCE. None of this information herein shall be divulged to | |||
persons other than IBM employees authorized by the nature of their duties to receive such information, or | |||
individuals or organizations who are authorized in writing in accordance with existing policy regarding release | |||
of company information. This material, if exported from the United States, is shipped under General | |||
License GTDR. | |||
Restrictions and Installation Instructions for | |||
IBM Extended Services for OS/2 (Driver Level S1A246) | |||
and | |||
IBM OS/2 LAN Server V2.0 (Driver Level 281) | |||
on | |||
IBM OS/2 Standard Edition V2.0 (Driver Level 6.167) | |||
October 18, 1991 2:16 p.m. | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 & OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver | |||
6.167 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 ii OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Contents | |||
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 | |||
2.0 System Requirements and Performance ............... . . . . . . . 3 | |||
2.1 Memory and Fixed-Disk.Requirements . . . . . . . ............. 3 | |||
2.2 Extended Services.Performance. ........... . . . . . . . . . . . . . 4 | |||
2.3 LAN Server/Requester.Performance. ........... . . . . . . . . . . 4 | |||
3.0 New and Enhanced.Function ... . . . . . . . . . ......... . . . . . . 6 | |||
3.1 New and Enhanced Function in Communications Manager .. . . . . . . . . 6 | |||
3.2 New and Enhanced Function in Database Manager ............ . . 7 | |||
3.3 New and Enhanced Function in.LAN.Server 2.0 . . ........... . 8 | |||
4.0 Quick Glance - Fixes in this.Driver ....... . . . . . . . . . . . . . . . 10 | |||
4.1 Fixes in Communications.Manager. . . ....... . . . . . . . . . .. . 10 | |||
4.2 Fixes in Database Manager ............. . . . . . . . . . . . . . . 16 | |||
4.3 Fixes in LAN Services. . . . . . ........... . . . . . . . . . . . . . 19 | |||
5.0 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 | |||
5.1 General Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 | |||
5.2 Extended Services Restrictions. . . . . . . ............. . . . . . . 20 | |||
5.3 Communications Manager.Restrictions . ............. . . . . . . 21 | |||
5.4 Database Manager Restrictions. . . . . . . ............. . . . . . 25 | |||
5.5 LAN Server Version 2.0 Hardware.Restrictions ... . . . . . . . . . . . . 28 | |||
5.6 LAN Server Version 2.0 Server.Restrictions ... . . . . . . . . . . . . . . 29 | |||
5.7 LAN Server Version 2.0 Requester Restrictions. . . . . . . . . . . . . . . . 34 | |||
5.8 LAN Server Version 2.0 Publications Restrictions. . . . . . . . . . . . . . 37 | |||
6.0 Extended Services Installation. . . . . . . ............. . . . . . . 38 | |||
6.1 Before You Install Extended.Services ..... . . . . . ......... . . 38 | |||
6.2 Extended Services Installation Concepts. . . . . . . . .......... . . 40 | |||
6.3 Basic Configuration Services (BCS) ............... . . . . . . . . 41 | |||
6.4 Advanced Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 | |||
6.5 Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 | |||
6.6 Applying Patches to the Installed System. . . . . . . . ........ . . . 44 | |||
7.0 Installing Communications Manager ............... . . . . . . . . 47 | |||
7.1 Before You Install Communications Manager ................. 47 | |||
7.2 Installation Instructions for Communications Manager .... . . . . . . . 49 | |||
7.3 Re-installation of Communications Manager ................. 52 | |||
7.4 Communications Manager Installation Notes ................. 52 | |||
7.5 ROP Service and SPA Router Installation.Instructions .... . . . . . . 53 | |||
8.0 Installing Database Manager ............. . . . . . . . . . . . . . . 55 | |||
8.1 Before You Install Database Manager ............... . . . . . . 55 | |||
8.2 Database Manager Installation Examples. . . . . . . . ........ . . . 56 | |||
9.0 Installing OS/2 LAN.Requester. . ......... . . . ... . . . . . . . 65 | |||
9.1 Basic Installation for OS/2 LAN Requester ................. . 65 | |||
Contents ii | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 iii OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
9.2 Advanced Installation for OS/2 LAN Requester .............. . 65 | |||
9.3 Reinstalling, Reconfiguring.or Removing. . ........... . . . . . 65 | |||
10.0 Installing OS/2.LAN.Server . . ....... . . . . . . ... . . . . . . . 66 | |||
10.1 Basic Installation for OS/2 LAN Server. . . . . . . . .......... . . 66 | |||
10.2 Advanced Installation for OS/2.LAN.Server ..... . ....... . . 66 | |||
10.3 LAN Server 1.3 Migration Utility ............... . . . . . . . . 66 | |||
11.0 Installing IBM LAN Support Program and.DOS.LAN.Requester . . 67 | |||
11.1 Installing the IBM LAN Support.Program, V.1.21. ........ . . . 67 | |||
11.2 Installing DOS LAN.Requester. . ......... . . . ... . . . . . . 67 | |||
Appendix A. SNA Advanced Configuration . . . . . . . . ............ . 69 | |||
A.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 | |||
A.2 Advanced Configuration for 5250. ............. . . . . . . . . . . 70 | |||
A.3 Advanced Configuration for 3270.Over Token-Ring. ........ . . . 76 | |||
A.4 Advanced Configuration for 3270.Gateway. . . . ....... . . . . . . 79 | |||
Appendix B. EHLLAPI Virtual Device.Driver (VDD) ... . . . . . . . . . . 83 | |||
B.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 | |||
B.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 | |||
B.3 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 | |||
B.4 Compatability (With Personal Communications 3270.2.0) . . . . . . . . 84 | |||
Appendix C. Communications Manager Stop.API. ........... . . . . 89 | |||
C.1 Overview and Usage ........... . . . . . . . . . . . . . . . . . . . . 89 | |||
Contents iii | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 1 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
1.0 Introduction | |||
This document provides the basic installation instructions for the IBM Extended | |||
Services for OS/2 (Extended Services) and LAN Server (LS) V2.0 driver. For | |||
additional information on installing these products, please refer to the Workstation | |||
Install Guide publication for Extended Services and the LAN 2.0 Network | |||
Administrator Reference Volume 1 publication for LS. | |||
The Extended Services and LAN Server V2.0 driver consists of: ( 3 1/2" format): | |||
- 8 Extended Services diskettes | |||
- 2 patch diskettes | |||
- 2 OS/2 LAN Server V2.0 diskettes | |||
- 3 OS/2 LAN Requester V2.0 diskettes | |||
- 1 OS/2 LAN Network Device Drivers diskette | |||
- 1 OS/2 LAN Migration Utility V1.3 diskette | |||
- 3 DOS LAN Requester diskettes | |||
- 1 PC LAN Support Program diskette | |||
The patch diskettes contain patches for Extended Services. | |||
# Note: | |||
# OS/2 LAN Server driver 281 and Alternate Diskette 1 for Extended Services driver | |||
# S1A246 are required for use with SE 2.0 driver 6.167. The Alternate Diskette 1 for | |||
# Extended Services must be used as a replacement for the Diskette 1 in the original | |||
# Extended Services driver S1A246. This Alternate Diskette 1 must be used during | |||
# initial Extended Services installation. | |||
The entire Extended Services installation procedure starts with Diskette 1 of the | |||
Extended Services diskettes. You will be guided to insert program diskettes 1 | |||
through n, depending on your system requirements. The CONFIG.SYS file is | |||
updated automatically during the Extended Services installation process. | |||
The installation of OS/2 Communications Manager, OS/2 Database Manager and | |||
OS/2 LAN Server assumes that you have already installed the appropriate OS/2 | |||
base operating system, or that you already have EE 1.30.1 installed. | |||
For a 16-bit base, SE V1.3 manufacturing refresh 1.30.1 is required. For a 32-bit | |||
base, SE V2.0 driver level 6.167 is required. | |||
# NOTE | |||
# Although, these drivers will run on either a SE 16-bit base or a 32-bit base, this | |||
# document was primarily written from a 32-bit installation and execution | |||
# perspective. Thus, there may be slight differences when running in a 16-bit | |||
# environment. | |||
# Throughout this document, a revision code of # in the left margin denotes changes | |||
# from the previous Restrictions and Installation document for Extended Services and | |||
# OS/2 LAN Server running on SE 2.0 level 6.605. | |||
Introduction 1 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 2 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Introduction 2 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 3 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
2.0 System Requirements and Performance | |||
The following sections identify performance characteristics of these drivers. | |||
2.1 Memory and Fixed-Disk Requirements | |||
NOTE: THIS INFORMATION ONLY PERTAINS TO THESE DRIVERS, AND | |||
IS SUBJECT TO SIGNIFICANT CHANGE IN THE FUTURE! | |||
For OS/2 Standard Edition V 1.30.1, a base partition of 20MB is needed. This | |||
partition must hold this SE base, swappper.dat file, and the Extended Services and | |||
LAN Server V2.0 files that are installed in the boot partition. | |||
# For OS/2 Standard Edition 2.0, the base partition should be no smaller than 40MB. | |||
# This is to contain both the SE base and the common files used by Extended | |||
# Services and LAN Server (files that are always installed in the boot partition), and | |||
# to give some room for future expansion. | |||
# In addition to the disk space required for the appropriate Standard Edition base, the | |||
# minimum disk space used by Extended Services or LAN Server is 12MB. However, | |||
# depending on the Extended Services and LAN Server features that are actually | |||
# configured and installed, up to 32MB of disk space may be used by Extended | |||
# Services and LS. | |||
The memory requirements of the OS/2 base operating system depend upon which | |||
version of the operating system is used and which features of the OS/2 base system | |||
are concurrently used. The MINIMUM memory requirement for the OS/2 SE | |||
Version 1.30.1 product is 2 MB. The MINIMUM memory requirement for OS/2 | |||
SE Version 2.0 is 4 MB. | |||
For these drivers, the minimum RAM for Extended Services or LAN Server, in | |||
ADDITION to the base operating system requirement, is 1MB. | |||
In addition to the memory required by the base operating system, Extended Services | |||
and LAN Server, the user should allow additional memory to be used by whatever | |||
user applications that are concurrently executed. In general terms, small OS/2 | |||
applications (for example, WordPerfect or Excel) typically require about 1 MB of | |||
memory while large OS/2 applications (for example, DeScribe or Lotus 123/G) need | |||
2-3 MB of memory. | |||
We continue to work to improve the disk and memory usage of the SE, Extended | |||
Services, and LS products. The numbers above may not reflect the actual disk and | |||
memory requirements of the final product. | |||
These drivers are NOT suitable to be used as a benchmarking platform. | |||
Performance improvements continue to be made and the performance of this early | |||
code may not represent the performance of the final product. | |||
System Requirements and Performance 3 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 4 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
More complete information regarding the disk and memory requirements for | |||
Extended Services, LAN Server, and OS/2 SE Version 2.0 will be made available at | |||
general availability. | |||
2.2 Extended Services Performance | |||
Performance evaluation is ongoing; and performance is expected to improve over | |||
time. This level of code, however, may not accurately represent, in your | |||
environment, the performance of the final product. It is therefore | |||
RECOMMENDED that this level of code NOT be used for performance | |||
benchmarking and evaluation. | |||
2.3 LAN Server/Requester Performance | |||
2.3.1 Performance Considerations | |||
When using this driver of LS 2.0, you may notice very significant improvements or | |||
some degradation from LS 1.3 depending on your particular environment and/or | |||
application. Some of these situations are described below. For the environments in | |||
which OS/2 1.3 requesters are upgraded to OS/2 2.0, the descriptions assume | |||
sufficient memory in the requesters to avoid swapping during application execution. | |||
Note: We recommend that you do not use this driver level of code for performance | |||
benchmarking or evaluation. | |||
Environment 1 | |||
Upgrading LS 1.3 servers to LS 2.0 but not upgrading the requester's operating | |||
system from OS/2 1.3 to 2.0. Also includes DLR requesters with or without upgrade | |||
to DLR 2.0. | |||
LS 2.0 Advanced Version | |||
? LS 2.0 Advanced performs up to 2 times faster than LS 1.3 for most HPFS file | |||
I/O operations, including application loading, for both DLR and OS/2 | |||
requesters. The result is both shorter response times seen by the user and greater | |||
throughput capacity of the server. | |||
LS 2.0 Entry Version | |||
? The performance will be about the same as LS 1.3. | |||
Environment 2 | |||
Upgrading OS/2 requesters to OS/2 2.0 but not upgrading the server to LS 2.0 from | |||
LS 1.3. | |||
Application Loading Across LAN: Currently, OS/2 2.0 application load times | |||
across the LAN are slower than when using OS/2 1.3 as the requester operating | |||
system. This is related to OS/2 2.0 loader performance. Application loading from | |||
the DOS session is about the same as OS/2 1.3. | |||
System Requirements and Performance 4 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 5 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
File I/O Performance Across LAN: OS/2 file I/O performance is slightly slower | |||
with OS/2 2.0 than 1.3 but is not perceivable in many environments. This is a | |||
known problem and improvements will be made. DOS session I/O performance of | |||
OS/2 2.0 has noticeably improved performance over 1.3 for many types of I/O | |||
operations. | |||
Environment 3 | |||
Upgrading OS/2 requesters with OS/2 2.0 and also upgrading LS 1.3 servers with LS | |||
2.0. | |||
LS 2.0 Advanced Version | |||
? Performance will be similar to that of the Environment 1 Advanced version but | |||
OS/2 application loading will be somewhat slower. | |||
LS 2.0 Entry Version | |||
? The performance will be about the same as LS 1.3. | |||
System Requirements and Performance 5 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 6 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
3.0 New and Enhanced Function | |||
The following sections identify the function available in this driver. | |||
3.1 New and Enhanced Function in Communications Manager | |||
Following is a list of the new or enhanced functions that will be available in this | |||
driver for Extended Services Communications Manager. This list is NOT intended | |||
to include ALL functions that will be available in the final product. | |||
Note | |||
Please be aware that there may be restrictions/limitations that apply to some of | |||
these functions for this driver. Please BE SURE to refer to 5.3, | |||
﨏ommunications Manager Restrictions?on page 21 for information about | |||
these restrictions. | |||
? | |||
Advanced Peer-to-Peer Networking (APPN) Support | |||
? Modification of the LAN Transport layer to improve performance across | |||
supported LANS | |||
? Enabling support for industry standard NDIS interface | |||
? Programmable Configuration allowing REXX interface to the configuration file | |||
? 3174 Peer Communication enabling | |||
? EHLLAPI extensions including multiple simultaneous application access and | |||
support for structured fields low level verbs | |||
? ACDI extension allowing API to re-direct ACDI output (in addition to | |||
command line) | |||
? 370 Netview Remote Operations allow OS/2 commands from the Netview | |||
operator, REXX, and CLIST | |||
? | |||
New LU pooling algorithm to allocate session when requested, not as | |||
configured | |||
? Persistent Verification: reduced ID exchanges for LU6.2 (W/S to host) | |||
? File Transfer support for long file names | |||
? 3270 Jump key | |||
? Optionally installable Communications Manager Utilities | |||
? Configuration File Manager to simplify the administration of configuration files | |||
? Increased number of workstations for SNA Gateway support | |||
? 5250 in a PM text window as default | |||
? Migration path from EE 1.30.1 | |||
New and Enhanced Function 6 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 7 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
? Auto-reactivate DLC after adapter failure | |||
? REXX EHLLAPI interface (for information, see RXHLLAPI.DOC in | |||
\CMLIB) | |||
? | |||
DOS session interface to EHLLAPI (for information, see Appendix) | |||
? CM Stop API (for information, see Appendix) | |||
? Command line upgrade function for upgrading configuration files | |||
3.2 New and Enhanced Function in Database Manager | |||
Following is a list of the new or enhanced functions for Extended Services for OS/2 | |||
Database Manager that are available in this driver. The list is NOT intended to | |||
include ALL functions that will be available in the final product. | |||
Note | |||
Please be aware that there may be restrictions/limitations that apply to some of | |||
these functions for this driver. Please BE SURE to refer to 5.4, 﨑atabase | |||
Manager Restrictions?on page 25 for information about these restrictions. | |||
? Roll Forward Recovery (except for User Exits) | |||
? | |||
DOS Windows Client Support | |||
? | |||
Database Manageability Tools | |||
?Configuration Tool | |||
?Recovery Tool | |||
?Directory Tool | |||
? Database Manager Command Line Interface | |||
? Protocols for Extended Services | |||
?Database server support for Extended Services clients using NETBIOS, | |||
APPC and APPN protocols | |||
?Database server support for EE 1.2/1.3 OS/2 clients using SQLLOO | |||
? Reliability, Availability, Serviceability and Trace | |||
?Independent Trace Facility (ITF) | |||
?First Failure Support Technology/2 (FFST/2) support | |||
? Translate Function | |||
? SQLSTATE | |||
? User Defined Collate Sequence | |||
? Database Client with Local Databases | |||
? Standards Compliance: SAA and MIA | |||
?SQL Date/Time/Timestamp Arithmetic | |||
New and Enhanced Function 7 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 8 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
?Packages | |||
?Multivendor Integration Architecture (MIA) Version 1 implementation | |||
3.2.1 Design Changes from Previous Database Manager Releases | |||
Please note that the following design changes have been made to Database Manager | |||
in IBM Extended Services for OS/2 | |||
? You cannot create a database on a diskette, except on a Standalone Database | |||
Manager workstation. | |||
? APPC/APPN will NOT issue a STARTDBM (as APPC formerly did with EE | |||
1.3). You must issue a STARTDBM at the database server before any database | |||
clients can connect to a database. | |||
3.3 New and Enhanced Function in LAN Server 2.0 | |||
Following is a list of the new or enhanced functions for OS/2 LAN Server 2.0 that | |||
are available in this driver. The list is NOT intended to include ALL functions that | |||
will be available in the final product. | |||
Note | |||
Please be aware that there may be restrictions/limitations that apply to some of | |||
these functions for this driver. Please BE SURE to refer to 5.6, 﨤AN Server | |||
Version 2.0 Server Restrictions?on page 29 and 5.7, 﨤AN Server Version 2.0 | |||
Requester Restrictions?on page 34 for information about these restrictions. | |||
Reorganized/Improved Publications | |||
PM Hypertext Based OnLine Reference | |||
PM Based Graphical Install | |||
386 High-Performance File System | |||
Local Security for 386 HPFS | |||
Fault Tolerance | |||
? UPS Support | |||
? Disk Mirroring and Duplexing | |||
Support for Multiple LAN Adapters | |||
NDIS Support - (Network Device Interface Specifications) | |||
IBM Token Ring Busmaster/A Support | |||
Remote IPL Enhancements | |||
New and Enhanced Function 8 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 9 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
? Remote IPL of DOS or 1.3 OS/2 Workstations | |||
? Ethernet (DOS and OS/2 1.3 Requesters) | |||
DOS LAN Requester Enhancements | |||
? Enhanced Windows 3.0 Support | |||
? | |||
DBCS Command Line Support | |||
? DBCS Printer Support | |||
? DOS 5.0 Compatibilty | |||
Operator Priveleges | |||
Time Source Service | |||
Logon Enhancements | |||
? | |||
Fault Tolerant Logon Capability | |||
? Backup Logon | |||
? Logon From Multiple Workstations | |||
Generic Alerter Service | |||
First Failure Support Technology/2 (FFST/2) | |||
LAN Over Coax | |||
New and Enhanced Function 9 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 10 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
4.0 Quick Glance - Fixes in this Driver | |||
The following sections identify fixes (to previous driver restrictions) that have been | |||
incorporated into this driver. | |||
4.1 Fixes in Communications Manager | |||
? INSTALLATION AND CONFIGURATION | |||
FIXED | |||
If you are installing IBM Extended Services for OS/2 with the SE 2.0 | |||
operating system, you must take the following step after installing SE 2.0 | |||
and before installing IBM Extended Services for OS/2. You should copy the | |||
file ABIOS.SYS from the \OS2 directory to the root directory of the logical | |||
drive on which OS/2 is installed. | |||
FIXED | |||
If you plan to install Communications Manager through Advanced | |||
Installation with the default configuration file ACSCFG.CFG, you MUST | |||
select BOTH ACSCFG and ACSCFGUS from the Default Configuration | |||
File menu during initial installation. If you select only ACSCFG, | |||
installation will fail. | |||
FIXED | |||
If you have the Networking Services/2 product installed on your workstation | |||
and you are planning to install IBM Extended Services for OS/2 on that | |||
workstation with Standard Edition version 1.3 at the refresh level 1.30.1, you | |||
should reformat your partition during the installation of Standard Edition. | |||
FIXED | |||
Basic Configuration Services should not be used to create a 5250 WSF | |||
configuration file during initial installation. Instead, Advanced Installation | |||
should be used to install a User Defined 5250 configuration file. | |||
FIXED | |||
The Install/Remove function to Remove Communications Manager (CM) | |||
may not remove all the Communications Manager files from the system. | |||
RESTRICTION | |||
An initial IBM Extended Services for OS/2 installation using A:ESINST | |||
cannot be followed by a second A:ESINST without reformatting and | |||
reinstalling the base operating system. If additional features need to be | |||
installed after the initial installation, the REINST command should be used. | |||
Quick Glance - Fixes in this Driver 10 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 11 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
FIXED | |||
After verifying a configuration file, you may see the following message in the | |||
message log even though the configuration file verified without errors. This | |||
message should be ignored. | |||
The Communications Manager configuration does not start the SNA | |||
support. Change and re-verify the Communications Manager configuration. | |||
RESTRICTION | |||
After you complete steps for installation of Communications Manager, you | |||
are instructed to stop active features and press CTRL-ALT-DEL to reboot | |||
the system. Instead of pressing CTRL-ALT-DEL, you should use the | |||
DESKTOP Shutdown to stop the system if you have formatted your | |||
hardfile using the High Performance File System (HPFS). | |||
? INSTALLATION AND OPERATION OF CM WITH LAN SERVER (LS) | |||
RESTRICTION | |||
If you are planning to use both IBM Extended Services for OS/2 and LS, | |||
you should install IBM Extended Services for OS/2 FIRST. When you | |||
install Extended Services, you should select to install the LAN Adapter and | |||
Protocol Support from Additional Features in Communications Manager | |||
Advanced Installation (if it is not already installed based on a configuration | |||
file you have selected). | |||
FIXED | |||
A NET START REQUESTER may fail if a NETBIOS application is | |||
started at the same time. If this occurs, you should restart the requester. | |||
? CUSTOM BUILD AND CUSTOM INSTALLATION | |||
FIXED | |||
Limited testing has been done with the Custom build and custom | |||
installation feature. | |||
FIXED | |||
Custom build and custom installation should not be used for a configuration | |||
file containing ACDI parameters. | |||
FIXED | |||
Custom build and custom installation should not be used for configurations | |||
containing APPC/APPN parameters. | |||
Quick Glance - Fixes in this Driver 11 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 12 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
FIXED | |||
Custom build and custom installation does not function correctly to install | |||
LAN for a configuration file with ACDI redirection. | |||
After a custom build and custom installation, the Basic Configuratio n | |||
Services (ESCFG command) is not accessible. | |||
? PROGRAMMABLE CONFIGURATION | |||
FIXED | |||
The APPN feature of Programmable Configuration is not functioning in this | |||
driver and should not be used. | |||
? CONFIGURATION UPGRADE | |||
FIXED | |||
Limited testing has been done with the Configuration Upgrade and | |||
installation with pre-existing Extended Edition configuration files to be | |||
upgraded. Upgrade of Extended Edition 1.2 or 1.3 configuration files for | |||
3270 or ASYNC should work correctly. You should not attempt to upgrade | |||
a configuration file which contains combinations of other features with 3270 | |||
or ASYNC. | |||
FIXED | |||
Configuration Upgrade should not be used to upgrade EE 1.0 and EE 1.1 | |||
configuration files. For this first driver, advanced configuration should be | |||
used to build the files rather than upgrading from the old EE 1.0 or 1.1 file. | |||
FIXED | |||
Communications Manager configuration files containing Database Remote | |||
Data Services features cannot be upgraded. | |||
FIXED | |||
Communications Manager configuration files containing LAN Requester | |||
cannot be upgraded. | |||
FIXED | |||
An Extended Edition 1.2 or 1.3 level configuration file cannot be upgraded if | |||
it contains 3270 DFT and 3270 non-DFT with more than one session for | |||
DFT or non-DFT. | |||
FIXED | |||
EE 1.2 and 1.3 configuration files containing only NETBIOS parameters | |||
cannot be upgraded in this first driver. | |||
Quick Glance - Fixes in this Driver 12 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 13 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
FIXED | |||
EE 1.2 and 1.3 configuration files with APPC Transaction Program | |||
parameters should not be upgraded in this first driver. | |||
FIXED | |||
Configuration upgrade should not be used to upgrade more than one EE 1.2 | |||
or EE 1.3 configuration file during installation. | |||
FIXED | |||
5250 WSF configuration files do not upgrade correctly. | |||
FIXED | |||
REINST should not be used to install an upgraded configuration file which | |||
is stored in \CMLIB. | |||
? SDLC CONNECTIVITY | |||
FIXED | |||
Intermittent TRAP D errors may occur with the SDLC connectivity. | |||
? 3270 TERMINAL EMULATION | |||
FIXED | |||
The 3270 terminal emulator should not be restarted after selecting to stop | |||
specific emulator sessions or a software error will occur. You should be able | |||
to stop 3270 emulation and restart it without problems if you select to stop | |||
ALL sessions. | |||
? 3270 HOST GRAPHICS | |||
FIXED | |||
When running on the OS/2 2.0 operating system, host graphics files can be | |||
printed or plotted only when using the PR option from the GDDM | |||
directory panel. | |||
RESTRICTION | |||
When running on the OS/2 2.0 operating system, the PF5=SAVE PIF | |||
option under the GDDM output function is not working correctly. | |||
? SNA GATEWAY | |||
Quick Glance - Fixes in this Driver 13 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 14 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
FIXED | |||
If the SNA Gateway has a LAN connection to the host or to its attached | |||
workstations, the gateway may hang when logging off the last workstation. | |||
To avoid this problem, the FREE UNUSED LINKS parameter in the DLC | |||
profile (accessed from CM Advanced Configuration SNA Feature Profiles) | |||
should be set to NO on your SNA Gateway. | |||
? DMA ASYNC | |||
RESTRICTION | |||
The DMA Async support for line speeds up to 64Kbps is not functioning | |||
correctly on the PS/2 Model 90 and Model 95. If you are using a PS/2 | |||
Model 90 or 95 with ASCII emulation or ACDI redirection, you can still | |||
use line speeds up to 19.2 Kbps. You should add a REM statement to your | |||
CONFIG.SYS as follows. In this statement, d is the logical drive on which | |||
Communications Manager is installed. | |||
REM DEVICE=d:\CMLIB\ASYNCDDC.SYS | |||
? | |||
5250 WORKSTATION FEATURE (WSF) | |||
FIXED | |||
Basic Configuration Services (ESCFG command) should not be used to | |||
create a 5250 WSF configuration file. Instead Advanced Configuration | |||
should be used. | |||
FIXED | |||
When configuring 5250 WSF session assignments, red warning panels will be | |||
displayed indicating that the APPC partner LU alias and the APPC mode | |||
name do not exist. You will be asked if you want to continue. Select YES. | |||
If you have configured these parameters, they do exist even though the | |||
warning indicates that they do not. | |||
FIXED | |||
To use 5250 WSF with the auto sign-on feature, the LU name and the LU | |||
alias name should be configured to match. | |||
FIXED | |||
The F4=LIST function from the 5250 Session profiles does not provide a | |||
list of the mode and partner LU profiles. | |||
FIXED | |||
When using the twinax connectivity for 5250 Workstation Feature, only one | |||
twinax attached workstation can access the AS/400 at a time. This occurs | |||
because every twinax workstation connects to the AS/400 with a PU name | |||
of PU00000. | |||
Quick Glance - Fixes in this Driver 14 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 15 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
FIXED | |||
Using the SE 2.0 operating system, 5250 fails to stop when it is selected to | |||
be stopped from Communications Manager main menu. You should not | |||
attempt to stop 5250 WSF if there are other Communications Manager | |||
features running on the system. If you do attempt to stop 5250 WSF, you | |||
should not attempt to restart 5250, or the other features running on the | |||
system will be brought down. Your host line may need to be varied off and | |||
back on after this scenario. | |||
? LAN ADAPTER AND PROTOCOL SUPPORT | |||
RESTRICTION | |||
When using the IBM Token Ring 16/4 Adapter or the IBM Token Ring | |||
16/4 adapter /A, and the adapter is set for 64K paged, a user application | |||
cannot take advantage of the 64K. | |||
FIXED | |||
"Universally administered address reversed" is now a configuration option for | |||
NETBIOS in the NETBEUI section of PROTOCOL.INI. For this first | |||
driver, this option will not be operational. | |||
FIXED | |||
If you are writing NETBIOS applications, you may find that the return code | |||
from NETBIOS in the AX register is not always correct. For this first | |||
driver, you should rely on the NETBIOS return code in the NCB rather | |||
than that in AX. | |||
FIXED | |||
The following statement should be added to the bottom of the CONFIG. | |||
SYS to start the service required for LAN Adapter and Protocol Support | |||
error handling. In this statement, d is the logical drive on which the OS2 | |||
operating system is installed. | |||
RUN=d:\OS2\EPW.EXE | |||
? | |||
APPN | |||
FIXED | |||
The APPN function of routing traffic through an intermediate node is not | |||
functioning correctly. | |||
FIXED | |||
The APPN messages in this driver are in a format such that the message | |||
itself contains both the message and the help text. Therefore, if you choose | |||
to view the help, you will get an indication that the help is not available. All | |||
the information needed is contained in the message text itself. | |||
Quick Glance - Fixes in this Driver 15 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 16 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
? ACDI REDIRECTION API | |||
FIXED | |||
The MASM API data structure for ACDI Redirection API is incorrectly | |||
named as REDIRECT.INT. You should rename this file to | |||
REDIRECT.INC. This file is found in \CMLIB if you have selected to | |||
install the API Data Structures. | |||
? EHLLAPI | |||
FIXED | |||
The 5250 EHLLAPI TWAIT option on Set Session Parameters acts like an | |||
LWAIT. It does not time out after the first minute. | |||
? | |||
REMOTE OPERATIONS (ROP) SERVICE | |||
FIXED | |||
For Remote Operations, an extra unwanted ICON and entry in the Task | |||
List for ROP KERNEL is displayed. Neither the ICON nor the Task List | |||
entry should be accessed. | |||
FIXED | |||
The ROP Service may not always start after initially starting the system or | |||
after CTRL-ALT-DEL to reboot the system. If this problem occurs on | |||
your system, you should select to start ROP Service again. It should start | |||
correctly the second time. | |||
FIXED FOR SE 2.0 ONLY | |||
Occasionally the CTRL-ALT-DEL and Desktop shutdown may fail to | |||
work after running ROP Service for an extended period of time. In this | |||
case, the PC must be powered off. This can cause a significant delay in | |||
startup when the PC is restarted. | |||
? SUBSYSTEM MANAGEMENT | |||
FIXED | |||
The subsystem management functions to display class of service and | |||
topology for the active configuration file are not working correctly. | |||
4.2 Fixes in Database Manager | |||
The following table shows what has been fixed and what has not been fixed since | |||
the previous driver. | |||
Quick Glance - Fixes in this Driver 16 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 17 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Table 1 (Page 1 of 2). Database Manager Fixes Since Previous Driver | |||
Problem SE 1.30.1 or SE Status | |||
2.0 | |||
Install SE 2.0 only Fixed | |||
Musical notes may appear on screen during | |||
the 'Transferring files...' message. No impact | |||
to install. | |||
Install SE 2.0 only Fixed | |||
After Database Manager is installed, during | |||
IPL the system message SYS1195 appears on | |||
the screen. The message reads "The command | |||
"SYSLOG" on line xx of the CONFIG.SYS | |||
file is not recognized. Line xx is ignored." | |||
Install Both Fixed | |||
Database Manager messages are properly | |||
installed, but no entry exists in Group Main. | |||
(This applies to Standalone DBM only) | |||
Create Database Both Fixed | |||
After creating a new database with Extended | |||
Services, change the following database | |||
configuration parameters for that database: | |||
? Log file size (# of 4K pages): change from | |||
32 to 50 | |||
? Auto-restart: change from 'YES' to 'NO' | |||
Backup/Restore SE 2.0 only Fixed | |||
You can backup the 'Entire database' ONLY | |||
(you CANNOT do a 'Changes Only' | |||
backup). | |||
Reinstallation (REINST) SE 2.0 only Fixed | |||
Removal/reinstallation of Database Manager | |||
components is unpredictable. If the user must | |||
remove or reinstall components with this | |||
driver, a disk format and a full install of the | |||
operating system and Extended Services may | |||
be required. | |||
Reinstallation (REINST) Both Fixed | |||
During a reinstallation, the system may | |||
erroneously detect that a previous version of | |||
Database Manager is installed. If you get the | |||
Remove Previous Version of Selected | |||
Component screen, select 'Remove Previous | |||
Version' and the install should complete | |||
normally. | |||
Quick Glance - Fixes in this Driver 17 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 18 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Table 1 (Page 2 of 2). Database Manager Fixes Since Previous Driver | |||
Problem SE 1.30.1 or SE Status | |||
2.0 | |||
Command Line Interface does NOT work SE 2.0 only Fixed | |||
Command Line Interface SE 1.30.1 only Fixed | |||
? Cannot be run from the Desktop | |||
? AUTOCOMMIT (the default) is not | |||
working. The user will need to perform | |||
commits ('dbm commit') manually. | |||
? REORGCHK is not working. | |||
? Message 'DBM.MSG file can't be found' | |||
appears after normal completion | |||
Install is failing to add x:\sqllib to | |||
DPATH= statement of config.sys (where | |||
x is the drive DBM is installed on). | |||
Workaround is to add x:\sqllib to | |||
DPATH= statement of config.sys | |||
manually. | |||
REXX Interfaces to Database Manager SE 2.0 only Fixed | |||
If the user experiences difficulty with a REXX | |||
application, the application should be | |||
re-tokenized. | |||
Independent Trace Facility (ITF) Both Fixed | |||
The mask (-m) option is not working. If the | |||
mask is used, the trace buffer will be empty. | |||
Be aware that the mask option is invoked in | |||
two ways. Neither one of these is working: | |||
1. By starting trace using 'trc on | |||
<options>' where one of the options is | |||
-m (mask). | |||
2. By starting trace with simply 'trc'. | |||
This method of starting trace gives you a | |||
full-screen menu of selectable options. If | |||
you select any of the Products, Events or | |||
Components this will also set a mask, and | |||
the trace buffer will be empty. | |||
Log Full Condition (SQL0964)Both Fixed | |||
SQL0964 (DBM log full condition) received, | |||
even though periodic 'commits' are being | |||
done. | |||
Quick Glance - Fixes in this Driver 18 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 19 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
4.3 Fixes in LAN Services | |||
# NOTE TO OUR CUSTOMERS | |||
# Since this is a new driver for LAN Server, it is highly recommended that you | |||
# upgrade your system from the 274 LS driver to the 281 LS driver. | |||
# Please note that the following are NO longer restrictions in the 281 LS driver: | |||
# | |||
FIXED | |||
# Under Restrictions and Special Considerations for API's: The new 32 bit | |||
# DosFindFirst() /DosFindNext() calls will not work properly on a network drive | |||
# | |||
FIXED | |||
# Under Install/Config for the Server: | |||
? | |||
# If the requester is already installed on a workstation, the server cannot be | |||
# installed. To install a server, remove the requester first. | |||
# ? LAN Services cannot be moved to another drive, if already installed on a | |||
# different fixed disk drive. | |||
# FIXED | |||
# Under Install/Config for the Requester: | |||
# ? LAN Services cannot be moved to another drive, if already installed on a | |||
# different fixed disk drive. | |||
# ? Do not install the Loop Back Driver support. | |||
# | |||
FIXED | |||
# Under Generic Alerter Services for the Server: The problem of the | |||
# SYSLEVEL.SRV file not always being located in the :\IBMLAN subdirectory. | |||
Quick Glance - Fixes in this Driver 19 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 20 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
5.0 Restrictions | |||
The following sections identify inconsistencies, restrictions, and problems that we | |||
are aware of in this driver. Our development groups are currently addressing these. | |||
5.1 General Restrictions | |||
You must install Extended Services before you install any components of LAN | |||
Server V2.0. In addition, you must apply any Extended Services patches prior to | |||
any installation of LAN Server V2.0 components. | |||
Note | |||
If you plan to install both Extended Services Database Manager and any | |||
components of LAN Server V2.0, please BE SURE to read the Database | |||
Manager restriction in 5.4.2, estrictions for Functions/Features Available in | |||
this Driver?on page 25 under "Database Copy Protection". | |||
5.2 Extended Services Restrictions | |||
? INSTALLATION AND CONFIGURATION | |||
?If you are planning to install this driver over the SE 1.30.1 or SE 2.0 base | |||
operating system, you must reformat your boot partition and re-install your | |||
base operating system. You must also follow the directions to remove | |||
Extended Services code from any previous driver by following the | |||
instructions in 6.1, 﨎efore You Install Extended Services?on page 38. | |||
?After following instructions in 6.1, 﨎efore You Install Extended Services? | |||
on page 38, the first installation of this driver is initiated with the | |||
A:ESINST. The initial A:ESINST to install this driver cannot be followed | |||
by a second A:ESINST without reformatting and reinstalling the base | |||
operating system. If your initial installation fails for some reason, and you | |||
must issue another A:ESINST, you may be able to perform the A:ESINST | |||
again by taking the following steps. | |||
? For the following files, issue ATTRIB filename -R, and then erase the | |||
file. | |||
? in the root directory of the boot drive, IBMLVL.INI | |||
? in \MUGLIB, SYSLEVEL.MUG | |||
? in \OS2\INSTALL, ESINST.HST | |||
?COPY x:\OS2\INSTALL\CONFIG.ES x:\CONFIG.SYS, where x is | |||
the logical drive letter for the boot drive | |||
?Press CTRL-ALT-DEL to reboot the PC | |||
?After you complete steps for installation of Communications Manager, you | |||
are instructed to stop active features and press CTRL-ALT-DEL to reboot | |||
Restrictions 20 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 21 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
the system. Instead of pressing CTRL-ALT-DEL, you should use | |||
Shutdown to stop the system. To do so, bring up a menu by pressing the | |||
right mouse button while the pointer is not on any object (i.e on blank | |||
space) on the workplace desktop. Then select Shutdown from the menu to | |||
stop the system and reboot again. | |||
? If you have installed Communications Manager with a feature that requires | |||
APPC/APPN support and you receive the following message, you should | |||
use the REINST command to re-install the Communications Manager | |||
configuration file for the feature. The re-installation will cause your | |||
CONFIG.SYS to be updated correctly. | |||
ACS0112C - Communications Manager - Originator APPC - Critical file | |||
CONFIG.SYS(DEVICE=C:\CMLIB\APPN\CMKFMDD.SYS) was not | |||
found or was modified or damaged: error type 0002. | |||
# ?Multiple Communications Manager ICONs will be installed on the | |||
# workplace desktop with this OS/2 2.0 driver. Duplicates can be ignored. | |||
# ?With this OS/2 2.0 driver, the ICONs in the Communications Manager | |||
# group, Database Manager group, and Extended Services group will run | |||
# together. To arrange them so that the lettering is legible, you can click with | |||
# the right mouse button on a blank area of the grouping and select Arrange | |||
# from the menu which displays. | |||
? REQUIREMENT TO EXIT CM BEFORE STOPPING THE SYSTEM | |||
?If you have entered the Communications Manager Subsystem Management | |||
or Advanced Configuration panels you MUST always select to Exit | |||
Communications Manager before attempting a Desktop Shutdown or | |||
CTRL-ALT-DEL. If you do not exit Communications Manager, | |||
CTRL-ALT-DEL and Shutdown may be disabled. | |||
In some cases, you may experience a trap d when exiting Communications | |||
Manager with either the Exit when Complete or Exit Immediately options. | |||
If the CSLIM is 1bffffff, this is a known problem. You can hit enter to | |||
continue the exit process. | |||
5.3 Communications Manager Restrictions | |||
# ? COMMUNICATIONS MANAGER PANELS AND OPERATION WITH | |||
# A MOUSE | |||
# ?With the OS/2 2.0 operating system, the mouse may be inoperable on some | |||
# of the Communications Manager panels. The keyboard may be used to | |||
# select options. For example, to go to the CM Configuration panels, press | |||
# F10 from the CM main menu and select Advanced and then select | |||
# Configuration. | |||
? PROGRAMMABLE CONFIGURATION | |||
?If you plan to use the APPN functions of Programmable Configuration, | |||
you MUST install the patches as described in 6.0, 﨓xtended Services | |||
Installation?on page 38. | |||
?If you plan to use Programmable Configuration, you should always change | |||
the directory to \CMLIB prior to executing your Programmable | |||
Restrictions 21 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 22 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Configuration program. If you do not change to the \CMLIB directory, | |||
your configuration file may not verify correctly, or you may receive errors | |||
for files not found. | |||
?The APPN feature of Programmable Configuration should not be used to | |||
perform LIST and GET, but may be used to perform ADD and PUT. | |||
? FUNCTIONS INVOLVING APPC/APPN SUPPORT | |||
?If you plan to use a Communications Manager function which requires | |||
APPC/APPN support (e.g. 5250 WSF, 3270 emulation over SDLC or | |||
Token ring, APPC, CPI-C, SNA Gateway), you MUST install the patches | |||
as described in 6.0, 﨓xtended Services Installation?on page 38. | |||
?MIGRATION WARNING. If you you plan to use a Communications | |||
Manager function which requires APPC/APPN support (e.g. 3270 | |||
non-DFT, 5250 WSF, APPC, CPI-C, SNA Gateway), you must ensure | |||
that your machine is configured with a unique Fully Qualified CP Name. | |||
This name is created under-the-cover during Extended Services | |||
installation/configuration upgrade based on the Network Name and PU | |||
name in your current configuration file. Be aware that a naming collision | |||
means that you may not be able to establish a 3270 session through an | |||
Extended Services SNA Gateway to a host, be able to establish a 5250 | |||
session to an AS/400, or be able to activate a link to another APPN node. | |||
If you encounter these problems after installation, use Advanced | |||
Configuration/SNA Feature Profiles/SNA network definitions/ Local Node | |||
Characteristics to change the Local Node Name to a unique name. | |||
? 5250 WORKSTATION FEATURE | |||
?In order to use the 5250 Workstation Feature in this driver, you MUST | |||
install the patches as described in 6.0, 﨓xtended Services Installation?on | |||
page 38. | |||
? 3270 DFT CONNECTIVITY FOR A PC AT | |||
?In order to use the 3270 DFT connectivity on a PC AT in this driver, you | |||
MUST install the patch for 3270 DFT as described in 6.0, 﨓xtended | |||
Services Installation?on page 38. This patch is NOT required if you are | |||
running on a PS/2. | |||
# ? 3270 EMULATION ON MODEL 95 WITH MULTIPLE ADAPTERS | |||
# ?On OS/2 2.0, when running 3270 emulation, BOTH DFT and non-DFT | |||
# connectivities on a PS/2 Model 95, selecting to stop and restart the | |||
# non-DFT sessions will cause all sessions to go away. | |||
? CONFIGURATION FILE MANAGER | |||
?If you plan to use the Configuration File Manager, you MUST install the | |||
patches required as described in 6.0, 﨓xtended Services Installation?on | |||
page 38. | |||
? 3270 HOST GRAPHICS | |||
?In order to use 3270 Host Graphics with Extended Services, your host | |||
system must have the following PTFs applied. If they are not applied you | |||
may experience problems with clipping, printing and plotting. | |||
Restrictions 22 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 23 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
?For MVS, PTFs UL89380, UN04644 | |||
?For VM/SP, PTFs UL89381, UN04645 | |||
?For VM/XA SP, PTFs UL89382, UN03715 | |||
?For DOS/VSE, PTFs UL89383, UN04646 | |||
?When running on the OS/2 2.0 operating system, the PF5=SAVE PIF | |||
option under the GDDM output function is not working correctly. To | |||
work around this problem, you should take the following steps. | |||
?From the OS/2 full screen prompt, type GQFTRACE. | |||
?From the window displayed, select Output from the Action bar and | |||
select File (rather than screen). | |||
?From that same window, select Options and select File Close/Open | |||
mode. | |||
?From your host session, type ADMCHART. You'll receive a pop up, | |||
and you should select All Set. | |||
?At this point, you should be able to select PF5=SAVE PIF. | |||
? | |||
DMA ASYNC | |||
?The DMA Async support for line speeds up to 64Kbps is not functioning | |||
correctly on the PS/2 Model 90 and Model 95. If you are using a PS/2 | |||
Model 90 or 95 with ASCII emulation or ACDI, you can still use line | |||
speeds up to 19.2 Kbps. You should add a REM statement to your | |||
CONFIG.SYS as follows. | |||
?REM DEVICE=x:\CMLIB\ASYNCDDC.SYS (where x is the logical | |||
drive on which Communications Manager is installed) | |||
? | |||
LAN ADAPTER AND PROTOCOL SUPPORT | |||
?When using the IBM Token Ring 16/4 Adapter or the IBM Token Ring | |||
16/4 adapter /A, and the adapter is set for 64K paged, a user application | |||
cannot take advantage of the 64K. | |||
? REMOTE OPERATIONS (ROP) SERVICE | |||
?Occasionally the CTRL-ALT-DEL and Desktop shutdown may fail to | |||
work after running ROP Service for an extended period of time on a system | |||
formatted with HPFS running OS/2 SE 1.0. In this case, the PC must be | |||
powered off. This can cause a significant delay in startup when the PC is | |||
restarted. | |||
# ?On OS/2 2.0, ROP service cannot be started by clicking on the Remote | |||
# Operations Icon. Instead, the following steps must be followed to start the | |||
# router and ROP service: | |||
# From an OS/2 full screen command prompt, type the following | |||
# rtr /desktop | |||
# roppm /fullscreen /nologo | |||
# ? EHLLAPI VIRTUAL DEVICE DRIVER (VDD) | |||
Restrictions 23 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 24 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
# ?With this OS/2 2.0 driver, the EHLLAPI Virtual Device Driver MUST not | |||
# be used. Inclusion of the EHLLAPI VDD statement in CONFIG.SYS will | |||
# result in the inability to start any DOS sessions. If the EHLLAPI VDD is | |||
# to be used, it should be used with the OS/2 2.0 driver level 6.605. | |||
# ? ACDI REDIRECTION | |||
# ?With this OS/2 2.0 driver, ACDI Redirection does not function correctly. If | |||
# you are planning to use ACDI redirection, you should use OS/2 2.0 level | |||
# 6.605. | |||
5.3.1 Communication Manager Publications Restrictions | |||
Workstation Installation Guide | |||
The following APPN information is missing: | |||
? | |||
a description of the NS/2 files which may need to be backed-up before you | |||
format your fixed disk at installation; | |||
? installation and upgrade considerations for NS/2; | |||
? the SNA networking defaults used by BCS. | |||
Communication Manager Host Connect Reference | |||
? incomplete APPN (NS/2) examples for the AS/400 chapter | |||
Example Scenarios | |||
? no APPN (NS/2) information. | |||
? 5250 Emulation steps have had minimal testing. | |||
? X.25 steps have had minimal testing. | |||
Network Administrator's Guide | |||
? | |||
There is missing conceptual information and product description. | |||
? The naming conventions are missing several names and details about the names. | |||
? Operating system features are missing from the Operating System steps. | |||
? Several of the Communication Manager steps are missing blanks for recording | |||
information. | |||
? Database steps are missing planning information for Remote Data Services | |||
(RDS) and Distributed Database Connection Services (DDCS). | |||
? The LAN step is missing cross-references to the LAN planning guides. | |||
? The summary Worksheets at the back of the book are incomplete. Please refer | |||
to the full worksheets found in the Workstation Installation Guide, the | |||
Communication Manager Configuration Guide, and the LAN Network | |||
Administrator's Reference Volume 1: Planning and Installation. | |||
Restrictions 24 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 25 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
5.4 Database Manager Restrictions | |||
5.4.1 Functions/Features NOT Available in this Driver | |||
? Advanced Backup/Restore (Backup to non-standard devices) | |||
5.4.2 Restrictions for Functions/Features Available in this Driver | |||
The following restrictions/limitations apply to Database Manager for this driver. | |||
These restrictions will be corrected in future drivers unless otherwise noted. | |||
Migration of EE 1.1, 1.2 and 1.3 Databases | |||
Migration of EE 1.1, 1.2 and 1.3 Databases | |||
Migration of existing EE 1.1, EE 1.2 and EE 1.3 databases IS SUPPORTED in | |||
this driver. Please refer to 8.1.1, 﨧igration of Databases?on page 55 for | |||
information about migration of these databases. Be SURE to backup all | |||
databases BEFORE you install this driver. | |||
Migration of existing Extended Services databases, however, IS NOT | |||
SUPPORTED in this driver. See below, under "Migration of Extended Services | |||
Databases" for information about how to preserve these databases for use with | |||
this driver. | |||
Migration of Extended Services Databases (from previous driver) | |||
Restrictions 25 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 26 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
WARNING | |||
Migration of existing Extended Services databases (from the previous | |||
Extended Services driver) is NOT SUPPORTED in this driver! | |||
BEFORE YOU INSTALL THIS DRIVER, do the following steps if you want | |||
to use existing Extended Services databases: | |||
1. Export all tables and QM objects. | |||
2. Save any view definitions that you will want to use with the new | |||
version of the database. | |||
3. Drop the database. | |||
AFTER YOU INSTALL THIS DRIVER, do the following: | |||
1. Create a new Extended Services database. | |||
2. Import the tables and QM objects. | |||
3. Redefine any views that you want to use. | |||
4. Re-bind any existing access plans that you intend to use. | |||
You will need to export all objects and drop the databases before you install each | |||
new driver. Any updates you make to the databases using early driver code will | |||
be lost unless you export your objects before installing each driver. | |||
Database Copy Protection | |||
If you plan to install any of the LAN Server V2.0 components on the same machine | |||
on which Extended Services is installed, it is STRONGLY URGED that you install | |||
the LAN Server V2.0 component(s) BEFORE you create or migrate any databases | |||
using this Database Manager driver. | |||
If you do create or migrate databases using this driver, and you then want to install | |||
LAN Server V2.0, you MUST turn "Copy Protection" off for these databases | |||
BEFORE you install the LAN component(s). If you do not, you will receive an | |||
SQL5122N error ("Machine Dependent Check") when issuing a Start Using | |||
Database, and the database will be unusable. | |||
You can change this database parameter by using Database Tools, if installed, or the | |||
Command Line Interface. | |||
General Restrictions | |||
? A message indicating a code page conversion error occurs sometimes when a | |||
Start Using Database is issued. This may happen if database has been used | |||
several times. Reboot the system if this occurs. | |||
? If you do a Control-Break during a REORG, a Trap D will occur. | |||
? REXX stored procedures do not work. | |||
Restrictions 26 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 27 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
? Using the DBM Alter Table command may cause a looping situation that will | |||
appear as a hang. | |||
? If a process is killed from a client/server, a Trap D will occur. | |||
? | |||
There is no support on a LAN server for redirected disk drives. | |||
? If you get an SQL1084 error, use the message text for message SQL0956. | |||
NETBIOS Restrictions | |||
? When Extended Services and LAN Server are both installed and both running | |||
concurrently, the value set for "maximum names" is lower than needed. Edit the | |||
PROTOCOL.INI file NETBEUI section which will contain the "maximum | |||
names" value. Or select "LAN Adapter and Protocol Support" from the | |||
Communications Manager Advanced Configuration menu. The value should | |||
be changed from 17 to 21. Then reboot. | |||
Remote Data Services Restrictions | |||
# ? Bind problem with EE 1.2/1.3 Database clients using Query Manager | |||
# EE 1.2/1.3 database clients using Query Manager to remotely access a database | |||
# on an Extended Services database server will fail with an SQL0040N error ("An | |||
# error occurred on one or more bind files in list 'QRWSBND4.LST'. The | |||
# following files were not found: "3,3".), the first time the database is accessed. | |||
# Subsequent attempts to open the same database from a 1.2/1.3 client will | |||
# receive an SQL0805N error ("NULLID.QRWS2B" is not found.). | |||
? Remote Data Services heap size on the server is too low. Increase the value | |||
from 2 to at least 3. | |||
? You must issue a STARTDBM at the database server before any database | |||
clients can connect to a database. If you do not, the database client will hang | |||
when attempting to connect to a database. | |||
DOS Database Client/DOS Windows Database Client Restrictions | |||
# ? You CANNOT run any DOS Database client or DOS Windows Database client | |||
# applications in OS/2 's 'DOS Windows Full Screen', 'DOS Window' or 'DOS | |||
# Full Screen' command prompt environments. | |||
? Terminating an application program on a client workstation without issuing a | |||
COMMIT and Stop Using Database may cause the client to hang. | |||
Roll Forward Recovery Restrictions | |||
Roll Forward Recovery has not had sufficient testing at this time to withstand | |||
extensive usage. It is included so that users may get familiar with the interfaces and | |||
function capabilities. If used, please remain within the restrictions below. These | |||
items will be corrected in future drivers. | |||
? In order to do a ROLLFORWARD STOP you must have the log files | |||
available that existed when the backup was taken. | |||
? In most cases, a ROLLFORWARD to a point-in-time will not work correctly. | |||
The ROLLFORWARD should be run to the end of the logs ( time = | |||
9999/12/31-23:59:59) | |||
? The USER EXIT option is not supported. | |||
Restrictions 27 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 28 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
? When using the LOG RETAIN option, it is recommended that you increase | |||
the size of the log files (logfilsiz) and the number of log files (logprimary) as | |||
much as possible. A TRAP D may occur after multiple log files have been used. | |||
? BEFORE installing the operating system and Extended Services, the databases | |||
must be backed up. If MIGRATE database fails, the database cannot be used | |||
and will require a RESTORE of your backed up database. | |||
? The logpath cannot be changed after turning the LOG RETAIN option 'ON'. | |||
If a new logpath is desired, change to the new logpath, perform a START | |||
USING DATABASE to activate the configuration change, perform a STOP | |||
USING DATABASE, and then turn the RETAIN option 'ON'. | |||
? You cannot ROLLFORWARD through a CREATE INDEX, DROP | |||
INDEX, CREATE INDEX. It is recommended that no indexes exist when | |||
using ROLLFORWARD. | |||
5.5 LAN Server Version 2.0 Hardware Restrictions | |||
5.5.1 Bridge Considerations | |||
If you intend to run a bridge program on a slow workstation (i.e. IBM PC AT, | |||
Family I), ensure that the parameter server value in the bridge configuration | |||
program is set to No. If the parameter server value is set to Yes, a slow or | |||
congested bridge machine will be unable to respond quickly enough to workstations | |||
on the network, preventing the workstations' adapters from opening. Workstations | |||
that cannot enter the LAN will display an message. error opening | |||
adapter | |||
5.5.2 Adapter Considerations | |||
If you have an IBM Token-Ring Network 16/4 Adapter or IBM Token-Ring | |||
Network 16/4 Adapter /A with a microcode level of C24550, your | |||
sessions may be disconnected due to insufficient adapter transmit | |||
buffers. To correct this problem you may do one of the following: | |||
? Replace your adapter with Engineering Change (EC) level ECA066. | |||
? Use the LAN Adapter and Protocol Support full-screen interface | |||
to change the Number of adapter transmit buffers parameter | |||
for your network adapter card from the default of 1 to 2. | |||
5.5.3 Multiple Adapter Considerations | |||
? IBM PC Network adapters cannot share interrupt levels, therefore, you must | |||
ensure that other adapters on the workstation do not have the same interrupt | |||
levels as your IBM PC Network adapters. The valid interrupt levels for an | |||
IBM PC Network adapter are 2 and 3. Remember that in Micro Channel | |||
workstations, interrupt level 9 is treated the same as an interrupt level of 2. If | |||
Restrictions 28 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 29 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
required, use a Reference diskette to view or change interrupt levels for your | |||
adapters. | |||
? The 3270 Connection Adapter for 3174 Peer Communications can only use an | |||
interrupt level of 2. To avoid conflict with an IBM PC Network adapter, you | |||
must change the default interrupt level on the IBM PC Network adapter from 2 | |||
to 3. | |||
? An important consideration with multiple adapters is the amount | |||
of total RAM used by the various adapters. The total RAM used by | |||
your adapter cards, including other hardware adapters (for example, | |||
displays or SCSI drives) must not exceed 128KB. If this limit is | |||
exceeded, the network may not be able to start. To calculate your | |||
RAM usage, see the IBM OS/2 LAN Server Version 2.0 Network Administrator | |||
Reference Volume 1: Planning and Installation for RAM requirements on | |||
supported adapters. To this total, add any RAM used by other hardware as | |||
indicated by the manufacturer's documentation. | |||
? When installing either a IBM Token-Ring Network Adapter /A or an | |||
IBM PC Network Adapter/A concurrently with a 3270 Connection | |||
Adapter in a Micro Channel workstation, it should be located in a | |||
higher numbered slot than the 3270 Connection Adapter. | |||
? | |||
Do not mix 8-bit and 16-bit adapters in the same workstation unless | |||
they are at least 128KB apart in address range. | |||
5.5.4 Remote IPL Adapter Considerations | |||
The following adapter restrictions apply to the Remote IPL service: | |||
? If multiple LAN adapters are installed in a remote IPL requester, only one of | |||
the adapters can be configured for the Remote IPL service. | |||
5.6 LAN Server Version 2.0 Server Restrictions | |||
5.6.1 General System Caveats | |||
If installing both extended services and LAN Server, you must install Extended | |||
Services before installing LAN Server. | |||
This release of LAN Server 2.0 may be installed under SE Manufacturing level | |||
# 1.30.1, (16 BIT). The server may also be installed under OS/2 driver level 6.167, (32 | |||
# BIT). We recommend running the server on SE 2.0 for evaluation purposes only. | |||
5.6.2 Restrictions and Special Considerations for Functional Components | |||
Restrictions 29 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 30 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Install/Config | |||
? If installing both ES and LS, ES must be installed first. | |||
? If you select to install DOS 5.0 you must create the DOS 5.0 diskettes before | |||
they can be copied by the LAN Services installation/ configuration program. | |||
Follow the instructions on the boot diskette for DOS 5.0 to create the diskettes. | |||
? | |||
When the server is chosen to be removed, if Local Security for 386 HPFS is | |||
installed, the RUNPRIV.EXE command is not removed from | |||
STARTUP.CMD. Edit the file and remove the RUNPRIV.EXE command. | |||
# ? Do not install both the Loop Back Driver support and the LAN adapter and | |||
# Protocol support together. | |||
# ? The 386 HPFS will not run on OS/2 Version 2.0. When installing the LAN | |||
# Server on an OS/2 2.0 Operating System, do not use the basic path to install; | |||
# use the advanced path and do not install the 386 HPFS support. On the Install | |||
# screen select "DO NOT INSTALL" the 386 HPFS. Because Local Security for | |||
# 386 HPFS and Fault Tolerance for Fixed Disk both require 386 HPFS, you will | |||
# not be able to install them either. | |||
# ? When using OS/2 2.0, always take the advanced path. | |||
# ? Anytime you do a re-install or a re-configure, you must select "Replace" for the | |||
# LAN adapter and the protocol support. | |||
Command Line Interface | |||
Changes have been made to the definitions of the /PASSWORDCHG and | |||
/PASSWORDREQ parameters of the NET USER command. These parameters | |||
are now defined as follows: | |||
/PASSWORDCHG:{YES | NO} Specifies whether users can change their | |||
own password. The default is YES. | |||
/PASSWORDREQ:{YES | NO} Specifies whether a password is required for | |||
this user account. | |||
YES means that a password is required. | |||
NO means that a password is not required, but | |||
may be used. The password restriction of | |||
MINPWLEN is applied to any password that is | |||
used. | |||
NO also means that other password restrictions | |||
such as MINPWAGE, MAXPWAGE, UNIQUEPW, and | |||
PASSWORDCHG will not be applied to this | |||
account. | |||
Restrictions 30 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 31 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Full Screen Interface | |||
? On the IBM OS/2 LAN Requester, when you select (Definitions + Users | |||
Logon Details + Program starters) for a user, the Manage Program Starter | |||
panel lists all applications the user may access. It highlights applications | |||
assigned to the user except DOS public applications added to that user ID at | |||
IBM DOS LAN Requesters. From the Manage Program Starter panel, pressing | |||
Enter without selecting these DOS public applications will automatically | |||
deselect them for the user. Subsequently the DOS public applications will be | |||
removed from the user's Served Applications panel the next time the user logs | |||
on at an IBM DOS LAN Requester. | |||
# ? From the OS/2 LAN Requester Full Screen Interface, if the number of users | |||
# defined in the domain is more than 875, selecting one of the following actions | |||
# will display the NET9808E error panel: | |||
# 1. Select Definitions + Access Control + User List to manage Access | |||
# Control Profile User List. | |||
# 2. Select Definitions + Applications + Program Starters + Add to Add | |||
# Applications to Program Starters. | |||
# 3. Select Definitions + Applications + Program Starters + Delete to Delete | |||
# Applications from Program Starters. | |||
# Bring up User Profile Management Services (UPM) and reduce the list to fewer | |||
# than 875 users by deleting users you no longer need and try the action again. | |||
? | |||
# If your base system is OS/2 Version 2.0, the Online Reference is not available | |||
# from the LAN Requester Full Screen Interface at this time. However, you can | |||
# view the Online Reference by issuing "view A3ALANOR.INF" from the OS/2 | |||
# prompt. | |||
# Please do not select Utilities + Reference information, or press F5=Reference | |||
# on any help panel. | |||
# Selecting Utilities + Reference information, or pressing F5=Reference on a | |||
# help panel will cause the following error panel to appear: | |||
# "ROIVIEW.EXE | |||
# SYS2070: The system could not demand load the application's | |||
# segment. ROIVIEW -> HELPMGR.30 is in error. For additional | |||
# detailed information also see SYS182. | |||
# End program/command/operation | |||
# Display help" | |||
# Press Enter to End program/command/operation and select LAN Requester | |||
# from the Task List panel to return to the LAN Requester Full Screen Interface. | |||
# ? Copying files from one drive to another using the Drives folder is not | |||
# functioning. Use the OS/2 and DOS command prompts instead. | |||
# ? To make new files show up, select refresh on a folder. | |||
Restrictions 31 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 32 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
HPFS/386 | |||
Local Security | |||
? The 386 HPFS local security essentially supersedes Print Manager's local | |||
security. When a workstation with the 386 HPFS local security is started, one | |||
must log on as either an administrator or a print operator in order for the Print | |||
Manager window to come up and for the Spooler to be enabled. If an | |||
administrator or a print operator is not logged on at startup time, the Print | |||
Manager can be started with one of the following ways: | |||
?Make sure that the C:\PRIVINIT.CMD file (or the file specified by the | |||
PROTSHELL= line of the CONFIG.SYS file) contains the line: | |||
SPOOL.EXE. In this case, the Print Manager will come up and will be | |||
enabled at every workstation restart. | |||
?After the workstation is started, perform the following steps: | |||
?log on locally an an administrator | |||
?enter "PRIV SPOOL" at the command prompt | |||
? If you do not log on with sufficient privilege or with sufficient access | |||
permission, some applications may return error messages that do not indicate | |||
access denied as a cause for the error. Try logging on as an administrator to see | |||
if you have insufficient access permission or insufficient privilege for that action. | |||
Access Control Profiles: Drive level access control profiles cannot be created on | |||
HPFS/386 drives. | |||
# Remote IPL (RIPL): The 32 bit remote IPL of OS/2 2.0 is not currently available | |||
# for Token Ring, PC NET, or ETHERNET. | |||
DOS LAN Requester / Windows | |||
Windows: MS Windows without network support installed will always print to a | |||
local printer, even if the LPT port is "net used" to a remote printer. | |||
Maximizing Memory Utilization with DOS 5.0: (This is not in the PUBS for this | |||
driver.) DOS 5.0 can make more memory available to applications than earlier | |||
DOS versions. One way this is accomplished is by DOS being loaded in the first | |||
64KB of extended memory, called the high memory area (HMA). HMA is | |||
available on workstations with a 286 (or greater) processor with at least 1MB of | |||
memory. Most systems also have 384KB of space called the upper memory area. | |||
DOS can store information in this upper memory area on workstations with 386 (or | |||
greater) processors and extended memory. DOS 5.0 can take advantage of available | |||
memory by installing various memory managers, such as HIMEM and EMM386. | |||
Refer to your DOS 5.0 documentation for more information about memory and | |||
memory managers. | |||
# DOS LAN Requester can take advantage of the high memory area (HMA) and | |||
# upper memory blocks (UMB) by using the NET START command or the | |||
# DOSLAN.INI file to have DOS 5.0 load the network components into UMBs. | |||
# The NET START parameter in /UMB. This parameter is Extended Memory | |||
# Adapter (XMA) card and a memory manager that supports upper UMBs. | |||
/UMB can be used in combination with /EMS or /HIM. If /UMB is used in | |||
combination with either of these parameters, the network first tries to load all code | |||
Restrictions 32 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 33 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
into the UMB area. If all network components do not fit, then components are | |||
loaded into other available memory specified by /HIM or /EMS. Conventional | |||
memory may be reduced if all network components do not fit into the UMB area. | |||
External Interface | |||
Disk Fault Tolerance: | |||
? Most data corruption problems have been fixed in this driver. The potential for | |||
data corruption in high stress environments still exists. | |||
? Do not attempt to command line "FORMAT" a currently mirrored drive to the | |||
FAT file system. | |||
? Do not create more than 24 disk partitions (including mirrors). | |||
? In a system with SCSI drives, if it appears that your system is "hanging" forever | |||
on reads/writes or you have excessive errors on SCSI drives, please be sure your | |||
SCSI adapters are terminated properly. The following information will help you | |||
do so: | |||
?A SCSI card has one bus, which extends internally and externally. Each | |||
end must be terminated exactly once. The different drives terminate | |||
differently. | |||
?If no drives are attached to a card internally, then a card edge terminator is | |||
installed on the gold tabs at the top of the card. If no drives are attached | |||
externally, then on the IBM SCSI adapter with cache an external | |||
pin-in-socket terminator is used. On an IBM SCSI adapter with no cache | |||
EITHER that terminator is used OR the on-board terminator near the | |||
external connector is inserted. | |||
?When drives are attached (internally, externally, or both), each cable must | |||
be terminated at the end. The black drives (60, 80, 120, 160) have | |||
terminators on the underside of the drive and usually have white slips of | |||
paper attached to them. The gold (>300 MB) drives have a terminator | |||
that gets inserted between the cable and the connector on the drive. | |||
Generic Alerter Service | |||
User Note: | |||
# The error log entry in the SYSLOG is not readable; however, the alert entry is | |||
# readable. This is not a Generica Alerter Service restriction as the alerts can be sent | |||
# to NETVIEW. | |||
Messages | |||
# ? The filename "NETWKSTA.SYS" in messages is the incorrect name. The | |||
# name should be "NETWKSTA.200". | |||
5.6.3 Restrictions and Special Considerations for Device Drivers | |||
? When using PCNET, the default in the IBMCOM\ PROTOCOL.INI in the | |||
MAC section for IBMNETA_NIF needs to be changed as follows: | |||
RECEIVEBUFFERS = 6 should be RECEIVEBUFFERS = 8 | |||
Restrictions 33 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 34 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
5.6.4 Restrictions and Special Considerations for Commands | |||
? NETCOPY or any other type of copy command (i.e. Xcopy) will trap after a | |||
long period of repeated use. | |||
5.7 LAN Server Version 2.0 Requester Restrictions | |||
5.7.1 General System Caveats | |||
If installing both extended services and LAN Server, you must install Extended | |||
Services before installing LAN Server. | |||
# This release of LAN Requester can be run under SE driver manufacturing level | |||
# 1.30.1,(16 BIT), or SE 2.0 driver level 6.167, (32 BIT). | |||
Please log on before attempting LAN functions. | |||
Install/Config | |||
? If installing both ES and LS, ES must be installed first. | |||
# ? When using OS/2 2.0, always take the advanced path. | |||
# ? Anytime you do a re-install or a re-configure, you must select "Replace" for the | |||
# LAN adapter and the protocol support. | |||
Command Line Interface | |||
Changes have been made to the definitions of the /PASSWORDCHG and | |||
/PASSWORDREQ parameters of the NET USER command. These parameters | |||
are now defined as follows: | |||
/PASSWORDCHG:{YES | NO} Specifies whether users can change their | |||
own password. The default is YES. | |||
/PASSWORDREQ:{YES | NO} Specifies whether a password is required for | |||
this user account. | |||
YES means that a password is required. | |||
NO means that a password is not required, but | |||
may be used. The password restriction of | |||
MINPWLEN is applied to any password that is | |||
used. | |||
NO also means that other password restrictions | |||
such as MINPWAGE, MAXPWAGE, UNIQUEPW, and | |||
PASSWORDCHG will not be applied to this | |||
account. | |||
Restrictions 34 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 35 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Full Screen Interface | |||
? On the IBM OS/2 LAN Requester, when you select (Definitions + Users + | |||
Logon Details + Program starters) for a user, the Manage Program Starter | |||
panel lists all applications the user may access. It highlights applications | |||
assigned to the user except DOS public applications added to that user ID at | |||
IBM DOS LAN Requesters. From the Manage Program Starter panel, pressing | |||
Enter without selecting these DOS public applications will automatically | |||
deselect them for the user. Subsequently the DOS public applications will be | |||
removed from the user's Served Applications panel the next time the user logs | |||
on at an IBM DOS LAN Requester. | |||
# ? From the OS/2 LAN Requester Full Screen Interface, if the number of users | |||
# defined in the domain is more than 875, selecting one of the following actions | |||
# will display the NET9808E error panel: | |||
# 1. Select Definitions + Access Control + User List to manage Access | |||
# Control Profile User List. | |||
# 2. Select Definitions + Applications + Program Starters + Add to Add | |||
# Applications to Program Starters. | |||
# 3. Select Definitions + Applications + Program Starters + Delete to Delete | |||
# Applications from Program Starters. | |||
# Bring up User Profile Management Services (UPM) and reduce the list to fewer | |||
# than 875 users by deleting users you no longer need and try the action again. | |||
# ? If your base system is OS/2 Version 2.0, the Online Reference is not available | |||
# from the LAN Requester Full Screen Interface at this time. However, you can | |||
# view the Online Reference by issuing "view A3ALANOR.INF" from the OS/2 | |||
# prompt. | |||
# Please do not select Utilities + Reference information, or press F5=Reference | |||
# on any help panel. | |||
# Selecting Utilities + Reference information, or pressing F5=Reference on a | |||
# help panel will cause the following error panel to appear: | |||
# "ROIVIEW.EXE | |||
# SYS2070: The system could not demand load the application's | |||
# segment. ROIVIEW -> HELPMGR.30 is in error. For additional | |||
# detailed information also see SYS182. | |||
# End program/command/operation | |||
# Display help" | |||
# Press Enter to End program/command/operation and select LAN Requester | |||
# from the Task List panel to return to the LAN Requester Full Screen Interface. | |||
# ? Copying files from one drive to another using the Drives folder is not | |||
# functioning. Use the OS/2 and DOS command prompts instead. | |||
# ? To make new files show up, you must select refresh on a folder. | |||
Restrictions 35 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 36 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
External Interface | |||
? In a system with SCSI drives, if it appears that your system is "hanging" forever | |||
on reads/writes or you have excessive errors on SCSI drives, please be sure your | |||
SCSI adapters are terminated properly. The following information will help you | |||
do so: | |||
?A SCSI card has one bus, which extends internally and externally. Each | |||
end must be terminated exactly once. The different drives terminate | |||
differently. | |||
?If no drives are attached to a card internally, then a card edge terminator is | |||
installed on the gold tabs at the top of the card. If no drives are attached | |||
externally, then on the IBM SCSI adapter with cache an external | |||
pin-in-socket terminator is used. On an IBM SCSI adapter with no cache | |||
EITHER that terminator is used OR the on-board terminator near the | |||
external connector is inserted. | |||
?When drives are attached (internally, externally, or both), each cable must | |||
be terminated at the end. The black drives (60, 80, 120, 160) have | |||
terminators on the underside of the drive and usually have white slips of | |||
paper attached to them. The gold (>300 MB) drives have a terminator | |||
that gets inserted between the cable and the connector on the drive. | |||
DOS LAN Requester / Windows | |||
Windows: MS Windows without network support installed will always print to a | |||
local printer, even if the LPT port is "net used" to a remote printer. | |||
Maximizing Memory Utilization with DOS 5.0: (This is not in the PUBS for this | |||
driver.) DOS 5.0 can make more memory available to applications than earlier | |||
DOS versions. One way this is accomplished is by DOS being loaded in the first | |||
64KB of extended memory, called the high memory area (HMA). HMA is | |||
available on workstations with a 286 (or greater) processor with at least 1MB of | |||
memory. Most systems also have 384KB of space called the upper memory area. | |||
DOS can store information in this upper memory area on workstations with 386 (or | |||
greater) processors and extended memory. DOS 5.0 can take advantage of available | |||
memory by installing various memory managers, such as HIMEM and EMM386. | |||
Refer to your DOS 5.0 documentation for more information about memory and | |||
memory managers. | |||
# DOS LAN Requester can take advantage of the high memory area (HMA) and | |||
# upper memory blocks (UMB) by using the NET START command or the | |||
# DOSLAN.INI file to have DOS 5.0 load the network components into UMBs. | |||
# The NET START parameter in /UMB. This parameter is Extended Memory | |||
# Adapter (XMA) card and a memory manager that supports upper UMBs. | |||
/UMB can be used in combination with /EMS or /HIM. If /UMB is used in | |||
combination with either of these parameters, the network first tries to load all code | |||
into the UMB area. If all network components do not fit, then components are | |||
loaded into other available memory specified by /HIM or /EMS. Conventional | |||
memory may be reduced if all network components do not fit into the UMB area. | |||
Restrictions 36 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 37 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
5.7.2 Restrictions and Special Considerations for Device Drivers | |||
? When using PCNET, change the \IBMCOM|PROTOCOL.INI in the MAC | |||
section for IBMNETA_NIF as follows: | |||
RECEIVE BUFFERS = 6 should be RECEIVEBUFFERS = 8 | |||
5.7.3 Restrictions and Special Considerations for Commands | |||
? NETCOPY or any other type of copy command (i.e Xcopy) will trap after a | |||
long period of repeated use. | |||
5.8 LAN Server Version 2.0 Publications Restrictions | |||
? Pagination may not be final for some of the publications. | |||
? Memory and fixed-disk requirements in the "Network Administrator Reference | |||
Volume 1: Planning and Installation" will be available in the final version. | |||
? On page 13-3 of the "Network Administrator Reference Volume 3: Network | |||
Administrator Tasks", the discussion on multiple adapter support for Remote | |||
IPL is not relevant to this release and will be removed in the final version. | |||
? The information in the "LAN Server V 2.0 Quick Reference" is for 16-bit only. | |||
Restrictions 37 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 38 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
6.0 Extended Services Installation | |||
During the installation of the IBM Extended Services for OS/2, pressing F1=HELP | |||
on menus and pop-ups will provide additional information to guide you through the | |||
process. | |||
Installation Notice | |||
This driver has a known problem which causes the installation to flip back and | |||
forth between screens while files are being transferred from diskette to the hard | |||
disk. Do not let this confuse you; you will eventually receive the correct prompt, | |||
panel or menu. | |||
6.1 Before You Install Extended Services | |||
? Before you install Extended Services, consider the following three cases: | |||
1. If you have a previously installed version of Extended Edition version 1.30.1 | |||
(EE 1.30.1), you can install Extended Services over it. | |||
If you install over EE 1.30.1, you may also select to install with an EE | |||
1.30.1 configuration file, and the file will be upgraded automatically during | |||
the installation process. | |||
If you install a Database Client over an existing EE 1.30.1 Database Client: | |||
?NETBIOS will be installed | |||
?SQLLOO definitions will be removed from the configuration file | |||
(assuming you are installing using Advanced Install and specify the EE | |||
1.30.1 XXX.CFG file), NETBIOS will be defined (if not already | |||
present), and a default NETBIOS configuration will be created in | |||
XXX.INI (the LAN configuration file associated with the XXX.CFG | |||
file). | |||
?Database Manager Workstation (Node) Directory entries will be | |||
converted from SQLLOO to NETBIOS. | |||
2. If you have a previously installed version of Extended Services (earlier | |||
driver), you MUST do the following: | |||
a. If Database Manager is currently installed, and you wish to preserve | |||
existing databases for use with this driver, follow the procedure in 5.4.2, | |||
estrictions for Functions/Features Available in this Driver?on | |||
page 25 under "Database Migration" before continuing to the next step. | |||
b. Copy all files on the boot drive that you wish to preserve | |||
c. Re-install one of the following base operating systems (and re-format | |||
the boot drive during the installation): | |||
?For a 16-bit base, SE V1.3 manufacturing refresh 1.30.1 is required. | |||
# ?For a 32-bit base, SE V2.0 driver level 6.167 is required. | |||
Extended Services Installation 38 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 39 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
d. Re-boot and bring up your newly installed operating system | |||
e. Remove all Extended Services components that were previously | |||
installed on other drives, by doing one of the following: | |||
1) Reformat the partition(s) where Extended Services components are | |||
currently installed (after copying any files you wish to keep) | |||
--- or --- | |||
2) Manually (or by using File Manager) erase all files (including | |||
"read-only" files) in the following directories, their subdirectories, | |||
AND the directories themselves: | |||
?\sqllib | |||
?\cmlib | |||
?\dbdrqlib | |||
3. If neither of the above cases apply, you must install one of the following | |||
operating systems as your base (and reformat the boot drive during the | |||
installation): | |||
?For a 16-bit base, SE V1.3 manufacturing refresh 1.30.1 is required. | |||
# ?For a 32-bit base, SE V2.0 driver level 6.167 is required. | |||
? If you are installing Extended Services with the OS/2 SE 2.0 base operating | |||
system you MUST select to INSTALL ALL FEATURES of the base operating | |||
system. | |||
? Before you install Extended Services, refer to section 5.0, estrictions?on | |||
page 20 for the limitations on Communications Manager and Database | |||
Manager. | |||
? | |||
If you have Database Manager databases from EE 1.1, EE 1.2 or EE 1.3 that | |||
you wish to use with this driver, you will be able to migrate them for use with | |||
Extended Services. Refer to 8.1.1, 﨧igration of Databases?on page 55 for | |||
more information about database migration. Make SURE you backup all | |||
databases BEFORE installing this driver. | |||
# ? At the end of the installation process, if you wish to view the installation history | |||
# file, the file can be browsed/printed by entering "VIEWLOG" at the OS/2 | |||
# command line. You can also select "View Install History File" from the | |||
# Extended Services group on workplace desktop. (see 6.2.4, 蘒nstallation Tools? | |||
# on page 41 for more information on this group). | |||
? The use of certain mouse device drivers may not be compatible with the | |||
Communications Manager SDLC or Async device drivers, particularly on the | |||
PC AT and PC XT/286. This is due to hardware interrupt conflicts. For PS/2's | |||
mouse device drivers which support interrupt sharing can work simultaneously | |||
with the SDLC and/or Async device drivers. | |||
The following is a table of the interrupt levels used for the most common | |||
communications adapters. You should also insure that the interrupt level used | |||
by an installed mouse device does not conflict with the levels used by your | |||
communications adapters. For an interrupt level to be sharable, both device | |||
drivers using the interrupt must be designed for interrupt sharing. Interrupt | |||
sharing is supported on PS/2's only. | |||
Extended Services Installation 39 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 40 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Table 2. Communication Adapter Interrupt Levels | |||
Adapter Interrupt Levels Comments | |||
DFT 2 Sharable on PS/2s | |||
SDLC 3 and 4 Sharable on PS/2s (if selected) | |||
ASYNC 3 or 4 Sharable on PS/2s | |||
TRN 2, 3, or 7 XT/286 or AT | |||
TRN 2, 3, 10, or 11Sharable on PS/2s | |||
PCN 2 or 3 Sharable on PS/2s | |||
6.2 Extended Services Installation Concepts | |||
6.2.1 Initial Installation | |||
ESINST | |||
For an initial install (first time), Extended Services installation is started by inserting | |||
the Extended Services diskette 1 and typing "A:ESINST" at the OS/2 Command | |||
prompt, which will then display the "Extended Services Copyright Panel". This | |||
invocation should only be used for your initial installation of Extended Services. | |||
During initial install (ESINST), you may choose to install using one of three | |||
installation options: | |||
? Basic Configuration Services | |||
? Advanced Installation | |||
? Custom Installation (requires a Custom Build diskette) | |||
6.2.2 Follow-on Installation | |||
REINST | |||
# After initially installing, Extended Services features can be added/removed through | |||
# reinstall (REINST) from command line, or by selecting "Add or Remove Features" | |||
# from the Extended Services group on workplace desktop. (see 6.2.4, 蘒nstallation | |||
# Tools?on page 41 for more information on this group). | |||
REINST is invoked at the OS/2 command prompt which will then display the | |||
"Extended Services Install/Remove Menu". Reinstall should be used to install any | |||
configuration file that was created/modified through Advanced Configuration, or to | |||
install any additional feature or any new components after initial installation. | |||
Extended Services Installation 40 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 41 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
ESCFG | |||
# After initially installing, if you need to modify an existing Basic Configuration | |||
# Services file or need to create one for yourself or another user, you may use ESCFG | |||
# or select "Basic Configuration and Installation" from the Extended Services group | |||
# on workplace desktop. (see 6.2.4, 蘒nstallation Tools?for more information on this | |||
# group). | |||
ESCFG is invoked at the OS/2 command prompt which will then display the | |||
"Extended Services Basic Configuration Services Panel". You will get the option to | |||
install the Basic Configuration Services files you have created/changed at the end of | |||
the processing. You can also choose not to install, but to install at a later time | |||
using REINST. | |||
6.2.3 Custom Build | |||
CUSTBLD | |||
This command is used to invoke Custom Build. Custom Build creates a Custom | |||
diskette with the selections that you have selected. This diskette will then be used | |||
to install Extended Services on another workstation, by selecting Custom | |||
Installation on the "IBM Extended Services Installation Options" menu during | |||
initial install on that workstation. | |||
6.2.4 Installation Tools | |||
After initial installation of Extended Services, you may access installation tools by | |||
selecting the Extended Services group from workplace desktop. You will be able to | |||
select from the following options. | |||
? Basic Configuration and Installation (ESCFG) | |||
? Add or Remove Features (REINST) | |||
? View Install History File (VIEWLOG) | |||
? Create Custom Install Diskette (CUSTBLD) | |||
? View Custom Build History File | |||
? Extended Services Command Reference | |||
6.3 Basic Configuration Services (BCS) | |||
6.3.1 BCS Overview | |||
BCS is designed to aid the user in doing a quick, simple installation by providing | |||
easy-to-use Configuration Services at install time. You can use BCS to configure | |||
and install the following features: | |||
? 3270 Terminal Emulation | |||
? ASCII Terminal Emulation to single host | |||
Extended Services Installation 41 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 42 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
? 5250 Work Station Feature (AS/400 or S/36) | |||
? Database Manager using Remote Data Services | |||
Each component has a section listing the steps to take for the BCS path. The order | |||
you see for your prompted steps may not correspond to what is listed in this | |||
documentation. You will be prompted to enter information unique to your | |||
workstation during BCS configuration. Commonly used default values are provided | |||
for other configuration parameters. Some defaults used by BCS may not be | |||
appropriate for your particular environment, for example, the Token Ring adapter | |||
type. However, BCS is highly recommended as a quick way to create a | |||
configuration file at install time and to customize it with the appropriate parameter | |||
values later via advanced configuration services. | |||
For more information on the features supported by Basic Configuration Services, | |||
please refer to the Extended Services Workstation Installation Guide. | |||
Note | |||
The configuration file created by the BCS is called a Basic Configuration File. | |||
To modify the basic configuration file, you can either use the Basic | |||
Configuration Services via ESCFG command OR the Communications | |||
Manager advanced configuration services. Please note that once the Basic | |||
Configuration File is modified by the Communications Manager advanced | |||
configuration services, it CANNOT be used by BCS. Both basic and regular | |||
configuration files can be used to bring up Communications Manager. | |||
6.3.2 Steps for Using BCS During Initial Install | |||
The steps below show you how to create a Basic Configuration file and to install | |||
from this file. Make sure you have installed the base operating system first or have | |||
Extended Edition version 1.30.1 installed. | |||
1. Insert the Extended Services diskette 1 in drive A: and type A:ESINST from an | |||
OS/2 full screen command prompt. | |||
2. Press enter on Extended Services Installation Version 1 Copyright panel. | |||
3. Press enter on the Welcome panel. | |||
4. Press enter on the Introduction panel. | |||
5. Select "Basic Configuration and Installation" from the IBM Extended Services | |||
Installation Options menu. Insert diskettes as prompted. | |||
6. Enter a name and an optional comment for the Basic Configuration file. | |||
7. You will see the Basic Configuration Services main menu. | |||
8. Install Communications Manager and/or Database Manager | |||
? Refer to section 7.2.1, 蘒nstalling Communications Manager Using Basic | |||
Configuration Services?on page 49 | |||
? Refer to section 8.2.1, 蘒nstalling Database Manager Using Basic | |||
Configuration Services?on page 56 | |||
Extended Services Installation 42 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 43 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
9. Apply Patches | |||
Appropriate Patches must be applied at this time. Refer to section 6.6, | |||
嗀pplying Patches to the Installed System?on page 44 for information on the | |||
patch process. This patch process must be followed to ensure you have a | |||
working environment. | |||
6.3.3 Using BCS After Initial Install | |||
For information on modifying your Extended Services installation using Basic | |||
Configuration Services, please refer to the Extended Services Workstation | |||
Installation Guide. | |||
6.4 Advanced Installation | |||
Advanced Installation can be selected on an initial installation or on a follow-on | |||
installation. It allows installation with a user defined configuration file from this or a | |||
previous release, installation of a default configuration file, and selective installation | |||
of additional features. | |||
If you choose to install a user defined configuration file from a previous release, the | |||
configuration information is automatically upgraded when you install Extended | |||
Services. | |||
6.4.1 Steps for Using Advanced Install During Initial Install | |||
The steps below show you how to use Advanced Install. Make sure you have | |||
installed the base operating system first or have Extended Edition version 1.30.1 | |||
installed. | |||
1. Place the Extended Services diskette 1, in drive A: and type A:ESINST from an | |||
OS/2 full screen command prompt. | |||
2. Press enter on Extended Services Installation Version 1 Copyright panel. | |||
3. Press enter on the Welcome panel. | |||
4. Press enter on the Introduction panel. | |||
5. Select "Advanced Installation" from the IBM Extended Services Installation | |||
Options menu. | |||
6. You will see the IBM Extended Services Install/Remove menu. | |||
7. Install Communications Manager and/or Database Manager | |||
? Refer to section 7.2.2, 蘒nstalling Communications Manager Using | |||
Advanced Installation?on page 50 | |||
? Refer to section 8.2.2, 蘒nstalling Database Manager Using Advanced | |||
Installation?on page 61 | |||
8. Apply Patches | |||
Appropriate Patches must be applied at this time. Refer to section 6.6, | |||
嗀pplying Patches to the Installed System?on page 44 for information on the | |||
Extended Services Installation 43 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 44 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
patch process. This patch process must be followed to ensure you have a | |||
working environment. | |||
6.4.2 Using Advanced Install After Initial Install | |||
After an initial installation, Advanced Installation can be invoked by using the | |||
REINST command or by selecting the Add or Remove Features option from the | |||
Extended Services Group on workplace desktop. For information on modifying | |||
your Extended Services installation through a follow-on installation, please refer to | |||
the Extended Services Workstation Installation Guide. | |||
6.5 Custom Installation | |||
For information on using Custom Installation, please refer to the Extended Services | |||
Workstation Installation Guide. | |||
6.6 Applying Patches to the Installed System | |||
After your Extended Services system is installed, you must apply the necessary | |||
patches. | |||
6.6.1 Description of Extended Services Patches | |||
Communications Manager Patches | |||
? 5250 Workstation Feature | |||
The ACS5ACS.DLL patch is required if you are planning on using the 5250 | |||
Workstation Feature in this driver. Without this patch 5250 WSF will not | |||
function. | |||
? LAN Adapter and Protocol Support | |||
The NETBEUI.NIF and NETBEUI.OS2 patches are required if you are | |||
planning on using the LAN Adapter and Protocol support in Extended Services | |||
along with the LAN Server driver. | |||
? Configuration File Manager | |||
The following patches are required if you are planning to use the Configuration | |||
File Manager in this driver. Without these patches, the CTRL-ESC key will | |||
not function, you may experience traps, some garbled text, and problems with | |||
help text when using the Configuration File Manager. | |||
?COPYCFG.EXE, COPYCFG.HLP, CCF.MSG, CCFH.MSG | |||
? Programmable Configuration | |||
The patches below are required if you are planning to use Programmable | |||
Configuration. Without the patches the APPN feature of Programmable | |||
Configuration does not function correctly. | |||
Extended Services Installation 44 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 45 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
?RCBMTD1.DLL, RCBMTD2.DLL, RCBMTD3.DLL, MAPPER.DLL, | |||
GATEWAY.TDF, SRPI.TDF, APPN.TDF, RCBUPG.CMD | |||
? APPC/APPN Support | |||
The APPC.DLL patch is required if you plan to use Communications Manager | |||
functions which require APPC/APPN support. Without this patch, you may | |||
experience problems starting Communications Manager using a configuration | |||
file involving APPC/APPN, or you may experience unpredictable results after | |||
starting Communications Manager. | |||
? 3270 DFT Support on SE 1.30.1 for the PC AT | |||
The ACS3EIAC.DLL patch is required if you plan to use Communications | |||
Manager 3270 DFT connectivity with the SE 1.30.1 operating system on a PC | |||
AT. Without this patch, the 3270 DFT connectivity will not function on a PC | |||
AT. | |||
? SQLLOO | |||
The RDSLAN.DLL patch is required if you plan to configure more than 50 | |||
NETBIOS sessions; or if you plan to have EE 1.2/1.3 Database clients using | |||
SQLLOO, connecting to an Extended Services Database server. | |||
Database Manager Patches | |||
If you have Database Manager installed, you must also install the Database | |||
Manager patches. | |||
6.6.2 Instructions for Applying Extended Services Patches | |||
*** NOTEs: *** | |||
1. In order for the patches to be applied correctly, you MUST take the steps | |||
below after Extended Services installation is complete. | |||
2. You MUST NOT start Communications Manager or Database Manager | |||
before applying the patches. | |||
3. These patches for IBM Extended Services for OS/2 MUST be installed prior | |||
to installing LAN Server if you plan to install the LAN Server product. | |||
4. If you need to re-install any of the Extended Services components, the patch | |||
process MUST be repeated after the re-installation. | |||
1. Insert the patch diskette #1 in drive A: | |||
2. From the OS/2 command prompt, enter the following commands. | |||
Note: The replace command will replace files based upon the features you have | |||
installed on your PC. If you have installed features which do not require any | |||
patches, then the replace command may not replace any files. | |||
? REPLACE A:\CMPATCH\*.* x:\CMLIB /S | |||
where x is the logical drive on which Communications Manager for | |||
Extended Services is installed. | |||
Extended Services Installation 45 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 46 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
? REPLACE A:\CMPATCH\*.* z:\IBMCOM /S | |||
where z is the logical drive on which OS/2 is installed. | |||
3. If you have installed the Communications Manager Configuration File Manager | |||
utility, you MUST enter the following command to install the correct help text | |||
file. | |||
COPY A:\CMPATCH\COPYCFG.HLP z:\OS2\HELP\ | |||
(where z is the logical drive (boot drive) on which OS/2 is installed) | |||
4. If you are planning to use Communications Manager, 3270 emulation with the | |||
DFT connectivity on a PC AT with the SE 1.30.1 operating system, you should | |||
enter the following to apply a patch for DFT. | |||
COPY A:\ATPATCH\ACS3EIAC.DLL x:\CMLIB\DLL\ | |||
(where x is the logical drive on which Communications Manager for Extended | |||
Services is installed) | |||
5. If you have NOT installed Database Manager on your workstation, you can | |||
skip this step. Otherwise, perform one of the following, depending on what you | |||
have installed. If you are not sure what you have installed, you can use | |||
VIEWLOG to look at your install history. In the steps below, specify the drive | |||
letter that indicates the drive on which Database Manager is installed. Make | |||
sure you have inserted patch diskette #2 in drive A:, and | |||
? If you have a Database Server or Database Client/Server or Database | |||
Standalone installed, type | |||
a:dbserver x: | |||
(where x is the drive on which Database Manager is installed) and press | |||
Enter. | |||
? If you have a Database Client with Local Databases installed, type | |||
a:dbclocal x: | |||
(where x is the drive on which Database Manager is installed) and press | |||
Enter. | |||
? If you have a Database Client installed, type | |||
a:dbclient x: | |||
(where x is the drive on which Database Manager is installed) and press | |||
Enter. | |||
6. Remove the patch diskette. | |||
# 7. Bring up a menu by pressing the right mouse button while the pointer is not | |||
# over any object (i.e. blank space) on the workplace desktop. | |||
# 8. Select shutdown from the menu to stop the system and then reboot the system. | |||
Extended Services Installation 46 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 47 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
7.0 Installing Communications Manager | |||
7.1 Before You Install Communications Manager | |||
Before installing IBM Extended Services for OS/2 (Extended Services), please be | |||
sure that you have read and understood all of the restrictions and limitations. Refer | |||
to 5.3, 﨏ommunications Manager Restrictions?on page 21 that apply to this | |||
driver. | |||
# After installation of Extended Services, "Communications Manager" group and | |||
# "Extended Services" group will be added to the workplace desktop. The contents | |||
# (i.e. options) of "Communications Manager" group depends on which features are | |||
# installed. The following is a complete list of available options. | |||
? Communications Manager | |||
? SNA Network Definitions Configuration | |||
? Verify SNA Network Definitions | |||
? Manage SNA Logical Links | |||
? Display Active SNA Configuration | |||
? Display SNA Configuration Log | |||
? | |||
Configuration File Manager | |||
? Start/Stop CM Trace | |||
? Format SNA Trace information | |||
Selecting the Extended Services group will display the following options to select | |||
from: | |||
? Basic Configuration and Installation | |||
? Add or Remove Features | |||
? View Install History File | |||
? Create Custom Install Diskette | |||
? Veiw Custom Build History File | |||
? Extended Services Command Reference | |||
You will note that Communications Manager Advanced Configuration profiles have | |||
changed for SNA configuration, and for LAN Adapter and Protocol configuration. | |||
We recommend that you read the APPENDIX section provided in this document, | |||
before using the Advanced Configuration Services for SNA configuration. In the | |||
APPENDIX section we have provided examples of configuration steps for SNA | |||
advanced configuration. For further information, refer to the "Communications | |||
Manager Configuration Guide" Volume 1. | |||
Installing Communications Manager 47 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 48 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
For LAN Adapter and Protocol configuration, refer to the "LAN Adapter and | |||
Protocol Support Configuration Guide". | |||
Communications Manager can be installed on any fixed disk and all changes to the | |||
CONFIG.SYS will be updated during the installation. Communications Manager | |||
will be installed into the \CMLIB directory and CMLIB sub-directories. | |||
The contents of the configuration file determines which program files will be | |||
installed on your workstation. To have appropriate program files installed on your | |||
system, you need to "install" the configuration file through the install process. To | |||
save DASD space, only the files you need for the connectivities and features that | |||
have been configured will be installed. For example, if your "installed" configuration | |||
file(s) contains no X.25 configuration information, X:\CMLIB and CMLIB | |||
subdirectories will not be loaded with any of the code which supports X.25 (X.25 | |||
DLC, X.25 device driver, etc.). *** WARNING: *** Merely copying or creating a | |||
configuration file in the X:\CMLIB will not install the proper feature files and | |||
update the CONFIG.SYS on your workstation. | |||
*** IMPORTANT NOTES: *** | |||
? If you plan to configure a new configuration file and copy to other | |||
workstations, we RECOMMEND that the "Configuration File Manager" utility | |||
be used, please refer to the "IBM Extended Services for OS/2 Network | |||
Administration Guide. With APPN integrated into Extended Services, there are | |||
APPN related files that MUST be copied with each .CFG file. | |||
? If your configuration file has been modified to add new features (for example: | |||
adding SRPI and 3270 features to the default ACSCFGUS.CFG via advanced | |||
configuration services, or adding the 5250 WSF feature to your basic | |||
configuration file via ESCFG.CMD), you will be required to go through the | |||
REINST process to have the new feature files installed and CONFIG.SYS | |||
updated on your system. If your configuration file has been customized via | |||
advanced configuration services to include new features, type "REINST" at the | |||
OS/2 command line, and be sure to select the "User Configuration File" option | |||
on the Communications Manager Install Menu during the re-installation | |||
process. | |||
? If you have a new configuration file (by copying one from another workstation | |||
or creating one via advanced configuration services), and it contains additional | |||
connectivities and features other than what you have on your workstation, | |||
re-installation is necessary to bring up Communications Manager with the new | |||
configuration file. Type "REINST" at the OS/2 command prompt; select the | |||
"User Configuration File" option on the Communications Manager Install | |||
Menu, and follow the prompts to install the new program files. | |||
7.1.1 Compiler Support | |||
Following is a list of the current compiler support for Communications Manager. | |||
? | |||
Support for the PASCAL language has been removed. | |||
? The Microsoft C Compiler V6.0 is the currently supported C compiler. | |||
** The IBM C/2 compiler is no longer supported **. | |||
Installing Communications Manager 48 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 49 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
? The Microfocus COBOL/2 Compiler is the currently supported COBOL | |||
compiler. | |||
** The IBM COBOL/2 compiler is no longer supported **. | |||
? | |||
The IBM FORTRAN/2 compiler is the currently supported FORTRAN | |||
compiler. | |||
? The IBM MACRO ASSEMBLER/2 compiler is supported. | |||
7.2 Installation Instructions for Communications Manager | |||
7.2.1 Installing Communications Manager Using Basic Configuration Services | |||
The steps below use default parameter values to create a basic configuration file with | |||
3270 terminal emulation using Token Ring. | |||
1. Select "3270 terminal emulation" from the BCS Main menu. | |||
2. Select the "LAN" option for the Connection Type, and take the defaults for the | |||
other options in the 3270 Terminal Emulation Defaults. | |||
3. Select "IBM Token-Ring Network" for Network Type. | |||
4. Select "IBM Token-Ring Adapter " from the Select Token Ring Network | |||
Adapter menu. (Select the appropriate adapter for your environment if it is | |||
different from the IBM Token-Ring Adapter.) | |||
5. Specify a "locally administered address" from the Select LAN Address Type | |||
menu. | |||
6. Specify the 12 digit hex address for the Local Adapter Address. | |||
7. On the 3270 Terminal Emulation LAN Defaults menu, specify the 12 digit hex | |||
address for the LAN Destination Address. | |||
8. Specify Local Node Name, Network Name, and Local Node ID on the | |||
Configuration Network Defaults menu to suit your environment. | |||
9. BCS Main Menu is displayed. | |||
10. If you are selecting to install Database Manager, refer to 8.2.1, 蘒nstalling | |||
Database Manager Using Basic Configuration Services?on page 56. | |||
11. If no more features are to be configured, press F3 to exit BCS. | |||
12. The target Drive Specification menu is displayed to specify the drive ID. | |||
13. Press F3 to exit the IBM Extended Services for OS/2 Install/Remove menu if | |||
you are done. | |||
14. Stop all active processes. | |||
# 15. Bring up a menu by pressing the right mouse button while pointer is not over | |||
# any object (i.e on blank space) on workplace desktop. | |||
# 16. Select Shutdown from the menu to stop the system and then reboot the system. | |||
17. Install patches (see 6.6, 嗀pplying Patches to the Installed System?on | |||
page 44). | |||
Installing Communications Manager 49 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 50 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
7.2.2 Installing Communications Manager Using Advanced Installation | |||
1. Select the "Install Communications Manager" option from the IBM Extended | |||
Services Install/Remove menu. | |||
2. The target Drive Specification menu is displayed to specify the drive ID for | |||
Communications Manager. You may install Communications Manager on any | |||
fixed disk or partition. | |||
3. Select "Configuration Files" from the Communications Manager Install menu. | |||
4. Select "Default Configuration Files" from the Communications Manager | |||
Configuration File menu. | |||
Note: At this point, you could also have selected to install "User configuration | |||
files." This would be the option that you would use to install a configuration file | |||
from this release or a previous release. If you select a configuration file from a | |||
previous release, the configuration information is automatically updated. | |||
5. Select one or both of the following IBM supplied Default Configuration files | |||
from the menu. | |||
? ACSCFG.CFG | |||
(This is a skeleton configuration file included with all model profiles and | |||
NLS keyboard profiles.) | |||
? ACSCFGUS.CFG | |||
(This is a skeleton configuration file included with all model profiles and US | |||
keyboard profiles.) | |||
After selecting the configuration file, you will be returned to the | |||
Communications Manager Install menu. | |||
6. To install any additional features, select "Additional Features" from the | |||
Communications Manager Install menu. | |||
7. Press spacebar to select each individual feature to install from the Additional | |||
Features menu. For example, if you are going to program to the | |||
Communications Manager API using the provided language interface, you need | |||
to install the API Data Structure files. Press enter when your are finished | |||
selecting features. | |||
8. Press F3 to exit the Communications Manager Install menu. Please note that | |||
when Exit (F3) is pressed, installation of your feature selections are being | |||
performed. Insert diskettes as required. | |||
9. If you installed more than one configuration file, the Select Configuration File | |||
to Update CONFIG.SYS File menu is displayed. By selecting the configuration | |||
file(s) you wish to activate, the CONFIG.SYS is automatically updated with | |||
DEVICE= and RUN= statements. | |||
10. Refer to 8.2.2, 蘒nstalling Database Manager Using Advanced Installation?on | |||
page 61 if you also need to install Database Manager. | |||
11. Press F3 to exit the Extended Services Install/Remove menu if you are done | |||
with Extended Services installation. | |||
12. Stop all active processes. | |||
Installing Communications Manager 50 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 51 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
# 13. Bring up a menu by pressing the right mouse button while mouse pointer is not | |||
# over any object (i.e on blank space) on workplace desktop. | |||
# 14. Select Shutdown from the menu to stop the system and then reboot the system. | |||
15. Install patches (see 6.6, 嗀pplying Patches to the Installed System?on | |||
page 44). | |||
7.2.3 Reconfiguring and Reinstalling Communications Manager | |||
1. Start Communications Manager by selecting Communications Manager from | |||
Communication Manager Group icon. | |||
2. Enter the appropriate configuration file name for starting the Communications | |||
Manager. | |||
3. Select "Configuration Services" from the Action Bar to configure your desired | |||
feature(s), for example: the SRPI, APPC, SNA Gateway, LUA, and X.25. | |||
4. When the user-defined configuration file(s) are built and verified, exit the | |||
Communications Manager. | |||
5. Type "REINST" at the OS/2 command prompt to re-install your configuration | |||
file(s) and the related feature files. | |||
6. Select "Install Communications Manager" option from the IBM Extended | |||
Services Install/Remove menu. | |||
7. Select "Configuration Files" from the Communications Manager Install menu. | |||
8. Select "User Configuration files" from the Communications Manager | |||
Configuration file menu. | |||
9. The Source Location menu is displayed. Specify the drive and path to your user | |||
configuration file. | |||
10. Select your desired configuration file(s) from the Select Configuration Files | |||
panel. | |||
11. Select the "Additional Features" option from the Communications Manager | |||
Install menu if so desired. | |||
12. Press F3 to exit the Communications Manager Install menu. Insert diskettes as | |||
required. | |||
13. Select the appropriate configuration file to update the CONFIG.SYS file. | |||
14. Press F3 to exit the Extended Services Install/Remove menu. | |||
15. Stop all active processes. | |||
# 16. Bring up a menu by pressing the right mouse button while pointer is not over | |||
# any object (i.e on blank space) on workplace desktop. | |||
# 17. Select Shutdown from the menu to stop the system and then reboot the system. | |||
18. Install patches (see 6.6, 嗀pplying Patches to the Installed System?on | |||
page 44). | |||
Installing Communications Manager 51 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 52 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
7.3 Re-installation of Communications Manager | |||
Re-installation is the process whereby the Communications Manager component, | |||
Communications Manager configuration file(s) with added NEW features and/or | |||
Additional Features are to be installed on a workstation that has previously been | |||
through the Extended Services installation process. The requisite Communications | |||
Manager program files are installed along with your configuration file. Enter | |||
"REINST" from the OS/2 command prompt line, and follow the prompts for | |||
installation instructions and inserting diskettes | |||
7.4 Communications Manager Installation Notes | |||
This section describes some specific notes that are related to installing the | |||
Communications Manager from this driver: | |||
? There are three types of configuration files that can be installed for | |||
Communications Manager: | |||
?Basic configuration file | |||
?Default (IBM-supplied) configuration file | |||
?User-defined configuration file. | |||
The basic configuration file is generated by the fast-path Basic Configuration | |||
Services. Please refer to 6.3, 﨎asic Configuration Services (BCS)?on page 41 | |||
for more detailed information. If the communication features cannot be | |||
configured using the BCS, most users will want to go to the Install Additional | |||
Features panel to select ACSCFG.CFG or ACSCFGUS.CFG from the Default | |||
Configuration Files option. The ACSCFGUS.CFG file is a general-purpose | |||
configuration file shipped with the system and contains all model profiles along | |||
with US-only keyboard support. It will require tailoring for your specific | |||
configuration before you can begin communicating. If you plan to make | |||
extensive changes, you may want to copy ACSCFG.CFG or ACSCFGUS.CFG | |||
to your own file, (e.g. MYCFG.CFG) and start the Communications Manager | |||
using MYCFG. | |||
Once ACSCFG.CFG or ACSCFGUS.CFG has been installed, you have the | |||
flexibility to customize your own features in the configuration file by utilizing | |||
the Communications Manager advanced configuration services function. After | |||
you build your own configuration file, you need to type "REINST" at the OS/2 | |||
command line, and select the "Configuration Files" and "Addition Features" | |||
options on the Communications Manager Install menu during the re-installation | |||
process. Refer to sections 7.2.2, 蘒nstalling Communications Manager Using | |||
Advanced Installation?on page 50 and 7.2.3, econfiguring and Reinstalling | |||
Communications Manager?on page 51 for more information. | |||
Installing Communications Manager 52 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 53 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
7.5 ROP Service and SPA Router Installation Instructions | |||
Remote Operations Service (ROP Service) and Service Point Application Router | |||
(SPA Router) can be installed on any fixed disk, and all changes to CONFIG.SYS | |||
will be updated during installation. SPA Router and ROP Service are installed in | |||
the \ROP directory of the drive you specify. Follow the steps below to install ROP | |||
Service and SPA Router. | |||
1. Place the IBM Extended Services for OS/2 diskette 1 in drive A. | |||
2. At the command prompt type: | |||
A:ROPS | |||
3. Press Enter. | |||
4. Follow instructions on the menus and insert diskettes as prompted. | |||
5. You will be asked to enter the drive where you want to install the SPA Router | |||
and ROP Service. Enter any valid drive letter of your choice. The SPA Router | |||
and ROP Service are installed in the \ROP directory of the drive you choose. | |||
6. On the "Remote Operations Installation Complete" menu, remove the diskette | |||
from drive A: and press enter. | |||
7. On the "Installation Complete" panel, select to "Return." | |||
8. You will return to the OS/2 command prompt. At this point, you should use | |||
Shutdown to stop and reboot the system so that the CONFIG.SYS changes | |||
take effect. | |||
*** NOTES: *** | |||
Before you can use the SPA Router and ROP Service, you will need to do the | |||
following. | |||
1. In your Communications Manager SNA Profile ensure that the Maximum RU | |||
Size is set to 512 or greater. ROP Service will only work with a value of 512 or | |||
greater. | |||
2. Configure and start a 3270 terminal emulation session (other than a 3270 DFT | |||
session) or configure Advanced Program-to-Program Communications (APPC) | |||
with session start in order to establish an SSCP-PU session. | |||
3. If you are going to use the User Profile Management (UPM) operator checking | |||
option, ensure that the operator ID of the NetView operator using ROP Service | |||
is defined to the UPM tables. To do this, define a new ID using an UPM | |||
administrator account. The password is optional. If the system is not security | |||
critical, it is recommended that the password not be set because use of a | |||
password requires sending the password with every RUNCMD. | |||
4. Start the Communications Manager before using the SPA Router and ROP | |||
Service. | |||
Installing Communications Manager 53 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 54 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
5. Open the Remote Operations group from the Desktop Manager group of OS/2 | |||
Presentation Manager. Start "Service Point Application Router" and then | |||
"Remote Operations Service". | |||
6. You are now ready to issue commands from NetView to this workstation. | |||
Installing Communications Manager 54 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 55 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
8.0 Installing Database Manager | |||
8.1 Before You Install Database Manager | |||
Before installing Database Manager, please be sure that you have read and | |||
understood all of the restrictions/limitations that apply to this driver. See 6.1, | |||
﨎efore You Install Extended Services?on page 38 and 5.4, 﨑atabase Manager | |||
Restrictions?on page 25. | |||
Database Manager can be installed on any fixed disk, and all changes to | |||
CONFIG.SYS will be updated during the installation. Database Manager will be | |||
installed into the \SQLLIB and \SQLLIB\DLL directories. | |||
8.1.1 Migration of Databases | |||
Extended Services databases (databases created using the previously shipped | |||
Extended Services driver), CANNOT BE MIGRATED FOR USE WITH THIS | |||
DRIVER. Please refer to 5.4, 﨑atabase Manager Restrictions?on page 25 for | |||
detailed instructions for using existing Extended Services databases with this driver. | |||
Existing databases from EE 1.1, EE 1.2 and EE 1.3 CAN BE MIGRATED for use | |||
with Extended Services. Currently, the only supported form of migration is | |||
Backup/Restore. Refer to Appendix A of the IBM Extended Services for OS/2 | |||
Guide to Database Manager for instructions on migrating databases. Be SURE to | |||
backup all databases BEFORE you install this driver. | |||
Corrections | |||
Appendix A of the IBM Extended Services for OS/2 Guide to Database Manager | |||
has some incorrect information. The references to migration of Version 1.0 | |||
databases is wrong: EE 1.0 databases can NOT be migrated. Also, there are no | |||
references to EE 1.2 or EE 1.3 databases in this appendix; however, migration | |||
DOES WORK for these databases. | |||
8.1.2 Compiler Support | |||
Following is a list of the current compiler support for Database Manager. | |||
? Support for the PASCAL language has been removed. | |||
? | |||
The Microsoft C Compiler V6.0 is the currently supported C compiler. | |||
** The IBM C/2 compiler is no longer supported **. | |||
? The Microfocus COBOL/2 Compiler V2.5 is the currently supported COBOL | |||
compiler. | |||
** The IBM COBOL/2 compiler is no longer supported **. | |||
Installing Database Manager 55 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 56 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
? The IBM FORTRAN/2 compiler is the currently supported FORTRAN | |||
compiler. | |||
8.2 Database Manager Installation Examples | |||
Note | |||
The following installation examples assume that you will be using IBM | |||
Token-Ring as your LAN network type. If you choose other network types, | |||
there will be some differences in the panels/menus that are displayed. | |||
Also, due to variables such as the sequence of component installation, all steps | |||
may not appear in the exact sequence listed in the examples. Additionally, if a | |||
connection type of "LAN" was previously configured (such as during 3270 | |||
Terminal Emulation configuration), some menus/panels may not appear at all. | |||
These are EXAMPLES only. Please refer to the IBM Extended Services for | |||
OS/2 Start Here and the IBM Extended Services for OS/2 Workstation | |||
Installation Guide for detailed installation instructions. | |||
8.2.1 Installing Database Manager Using Basic Configuration Services | |||
You can use Basic Configuration Services (BCS) to install any Database Manager | |||
configuration (Database Client, Database Server, Database Client/Server, Database | |||
Client with Local Databases, or Standalone). However, it is most commonly used to | |||
install those configurations which use Remote Data Services (RDS); this includes all | |||
configurations except Standalone. | |||
If you use Basic Configuration Services, and if you plan to use X.25 or SDLC for | |||
Remote Data Services, you will need to supplement your install with the | |||
Communications Manager Advanced Configuration services and re-installation | |||
process to configure and install them. Refer to the IBM Extended Services for OS/2 | |||
Configuration Guide for Communications for more information. | |||
The instructions that follow assume you will be installing Database Services, Query | |||
Manager, and Database Tools. Query Manager and Database Tools should be | |||
installed with Database Services if other application programs are not available to | |||
use when working with database information. | |||
If you choose not to install either Query Manager or Database Tools, then do not | |||
select those options from the Database Manager Install menu. In addition, you will | |||
be able to select DOS Database Client support and/or Windows Database Client | |||
support. This support can be installed on ANY configuration (see the IBM | |||
Extended Services for OS/2 Guide to Database Manager for additional information | |||
about DOS/Windows Database Clients). | |||
You may install Database Manager on any fixed disk or partition. | |||
Installing Database Manager 56 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 57 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Installing as a Database Client or Client with Local Databases | |||
1. At the Basic Configuration Services Main Menu: | |||
? Select "Database Manager using Remote Data Services" | |||
2. At the Specify Database Manager Communications menu: | |||
? Select "Database Client" | |||
3. At the Databases on Your Workstation pop-up: | |||
? Select "No" | |||
Note | |||
You can select "Yes", if you also want to create databases on this | |||
workstation. If you do, you will actually be installing as a Database | |||
Client with Local Databases. This is a new Database Manager | |||
configuration with Extended Services. | |||
4. If the Select LAN Network Type menu displays: | |||
? Select "IBM Token-Ring Network..." | |||
5. If the Select Token-Ring Network Adapter menu displays: | |||
? Select the appropriate adapter (e.g., Token-Ring adapter /A, Token-Ring | |||
adapter 16/4 /A, etc.) | |||
6. If the Select LAN Address Type menu displays: | |||
? Select "Use Universal address" if you want to use the unique address of the | |||
adapter card itself (and proceed to Step 7) | |||
-- or -- | |||
? Select "Specify a locally adminstered address" if you want to provide your | |||
own unique local adapter address. | |||
?At the Local LAN Adapter Address panel: | |||
?Enter a UNIQUE 12-digit adapter address, such as 400000000015. | |||
7. You will now be returned to the Basic Configuration Services Main Menu | |||
? Select another feature that you wish to install (i.e., 3270 Terminal | |||
Emulation, ASCII Terminal Emulation, etc.). See 7.2, 蘒nstallation | |||
Instructions for Communications Manager?on page 49 for information | |||
about installing these CM features. | |||
-- or -- | |||
? Select F3=Exit if you have made your last selection | |||
8. Follow the prompts to insert diskettes for installation of the Extended Services | |||
common code and the required Communications Manager code. | |||
If the Target Drive Specification panel displays (for Communications Manager), | |||
specify the target drive where you want CM installed. | |||
9. At the Target Drive Specification panel for Database Manager | |||
? Enter the target drive where you want Database Manager installed | |||
Installing Database Manager 57 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 58 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
10. At the Database Manager Install Menu: | |||
? Select "Database Services", "Query Manager" and "Database Tools" (note | |||
that this is now a multi-select menu) | |||
11. At the Workstation Name pop-up: | |||
? Specify a UNIQUE name for your workstation. (Note that BCS now | |||
defaults to the NETBIOS protocol for OS/2 clients. This requires that | |||
workstation names on a LAN be unique). | |||
12. Follow the prompts to insert diskettes for installation of Database Manager | |||
Installing as a Database Server | |||
1. At the Basic Configuration Services Main Menu: | |||
? Select "Database Manager using Remote Data Services" | |||
2. At the Specify Database Manager Communications menu: | |||
? Select "Database Server" | |||
3. At the Database Manager Target Drive Specification panel: | |||
? Enter the target drive where you want Database Manager installed | |||
4. If the Select LAN Network Type menu displays: | |||
? Select "IBM Token-Ring Network..." | |||
5. If the Select Token-Ring Network Adapter menu displays: | |||
? | |||
Select the appropriate adapter (i.e., Token-Ring adapter /A, Token-Ring | |||
adapter 16/4 /A, etc.) | |||
6. If the Select LAN Address Type menu displays: | |||
? Select "Use Universal address" if you want to use the unique address of the | |||
adapter card itself (and proceed to Step 7) | |||
-- or -- | |||
? | |||
Select "Specify a locally adminstered address" if you want to provide your | |||
own unique local adapter address. | |||
?At the Local LAN Adapter Address panel: | |||
?Enter a UNIQUE 12-digit adapter address, such as 400000000020. | |||
7. You will now be returned to the Basic Configuration Services Main Menu | |||
? Select another feature that you wish to install (i.e., 3270 Terminal | |||
Emulation, ASCII Terminal Emulation, etc.). See 7.2, 蘒nstallation | |||
Instructions for Communications Manager?on page 49 for information | |||
about installing these CM features. | |||
-- or -- | |||
? Select F3=Exit if you have made your last selection | |||
8. Follow the prompts to insert diskettes for installation of the Extended Services | |||
common code and the required Communications Manager code. | |||
Installing Database Manager 58 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 59 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
If the Target Drive Specification panel displays (for Communications Manager), | |||
specify the target drive where you want CM installed. | |||
9. At the Database Manager Install Menu: | |||
? | |||
Select "Database Services", "Query Manager" and "Database Tools" (note | |||
that this is now a multi-select menu) | |||
10. At the Workstation Name pop-up: | |||
? Specify a UNIQUE name for your workstation. (Note that BCS now | |||
defaults to the NETBIOS protocol for OS/2 clients. This requires that | |||
workstation names on a LAN be unique). | |||
11. Follow the prompts to insert diskettes for installation of Database Manager | |||
Installing as a Database Client/Server | |||
1. At the Basic Configuration Services Main Menu: | |||
? Select "Database Manager using Remote Data Services" | |||
2. At the Specify Database Manager Communications menu: | |||
? | |||
Select "Database Client/Server" | |||
3. At the Database Manager Target Drive Specification panel: | |||
? Enter the target drive where you want Database Manager installed | |||
4. If the Select LAN Network Type menu displays: | |||
? Select "IBM Token-Ring Network..." | |||
5. If the Select Token-Ring Network Adapter menu displays: | |||
? Select the appropriate adapter (i.e., Token-Ring adapter /A, Token-Ring | |||
adapter 16/4 /A, etc.) | |||
6. If the Select LAN Address Type menu displays: | |||
? Select "Use Universal address" if you want to use the unique address of the | |||
adapter card itself (and proceed to Step 7) | |||
-- or -- | |||
? Select "Specify a locally adminstered address" if you want to provide your | |||
own unique local adapter address. | |||
?At the Local LAN Adapter Address panel: | |||
?Enter a UNIQUE 12-digit adapter address, such as 400000000025. | |||
7. You will now be returned to the Basic Configuration Services Main Menu | |||
? | |||
Select another feature that you wish to install (i.e., 3270 Terminal | |||
Emulation, ASCII Terminal Emulation, etc.). See 7.2, 蘒nstallation | |||
Instructions for Communications Manager?on page 49 for information | |||
about installing these CM features. | |||
-- or -- | |||
? Select F3=Exit if you have made your last selection | |||
Installing Database Manager 59 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 60 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
8. Follow the prompts to insert diskettes for installation of the Extended Services | |||
common code and the required Communications Manager code. | |||
If the Target Drive Specification panel displays (for Communications Manager), | |||
specify the target drive where you want CM installed. | |||
9. At the Database Manager Install Menu: | |||
? Select "Database Services", "Query Manager" and "Database Tools" (note | |||
that this is now a multi-select menu) | |||
10. At the Workstation Name pop-up: | |||
? Specify a UNIQUE name for your workstation. (Note that BCS now | |||
defaults to the NETBIOS protocol for OS/2 clients. This requires that | |||
workstation names on a LAN be unique). | |||
11. Follow the prompts to insert diskettes for installation of Database Manager | |||
Installing as a Standalone | |||
Note | |||
Standalone DBM is usually installed using Advanced Installation, not BCS; | |||
however, if you want to install one or more of the Communications Manager | |||
features (3270 Terminal Emulation, ASCII Terminal Emulation or 5250 WSF) | |||
AND you want Standalone DBM, this procedure will work. | |||
1. At the Basic Configuration Services Main Menu: | |||
? Select one of the Communications Manager options ("3270 Terminal | |||
Emulation, ASCII Terminal Emulation, or 5250 Workstation Feature") | |||
2. Follow the prompts to insert diskettes for installation of the Extended Services | |||
common code and the required Communications Manager code. | |||
3. At the Target Drive Specification panel: | |||
? Specify the target drive where you want Communications Manager installed | |||
4. You will now be returned to the Basic Configuration Services Main Menu | |||
? | |||
Select F3=Exit | |||
5. At the IBM Extended Services/2 Install/Remove menu: | |||
? Select "Install Database Manager" | |||
6. At the Target Drive Specification panel: | |||
? Specify the target drive where you want Database Manager installed | |||
7. If a previous version of Database Manager is detected, select "Remove previous | |||
version" from the Remove Previous Version of Selected Component pop-up. | |||
8. At the Database Manager Install menu: | |||
9. Select "Database Services", "Query Manager", and "Database Tools" (note that | |||
this is now a multi-select menu). | |||
Installing Database Manager 60 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 61 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
10. At the Database Remote Data Services menu: | |||
? Select "No" | |||
11. Follow the prompts to insert diskettes. | |||
12. When you have finished installing Database Manager, select exit (F3), and | |||
follow the instructions. | |||
8.2.2 Installing Database Manager Using Advanced Installation | |||
You can use Advanced Installation to install any Database Manager configuration | |||
(Database Client, Database Server, Database Client/Server, Database Client with | |||
Local Databases, or Standalone); however, it is most commonly used to install | |||
Standalone. Those configurations which use Remote Data Services (RDS) are more | |||
commonly installed using Basic Configuration Services (BCS). | |||
The instructions that follow assume you will be installing Database Services, Query | |||
Manager, and Database Tools. Query Manager and Database Tools should be | |||
installed with Database Services if other application programs are not available to | |||
use when working with database information. | |||
If you choose not to install either Query Manager or Database Tools, then do not | |||
select those options from the Database Manager Install menu. In addition, you will | |||
be able to select DOS Database Client support and/or Windows Database Client | |||
support. This support can be installed on ANY configuration (see the IBM | |||
Extended Services for OS/2 Guide to Database Manager for additional information | |||
about DOS/Windows Database Clients). | |||
You may install Database Manager on any fixed disk or partition. | |||
Installing as a Standalone | |||
1. At the IBM Extended Services/2 Install/Remove menu: | |||
? Select "Install Database Manager" | |||
2. At the Target Drive Specification panel: | |||
? Specify the target drive where you want Database Manager installed | |||
3. If a previous version of Database Manager is detected, select "Remove previous | |||
version" from the Remove Previous Version of Selected Component pop-up. | |||
4. At the Database Manager Install menu: | |||
5. Select "Database Services", "Query Manager", and "Database Tools" (note that | |||
this is now a multi-select menu). | |||
6. At the Database Remote Data Services menu: | |||
? Select "No" | |||
7. Follow the prompts to insert diskettes. | |||
8. When you have finished installing Database Manager, select exit (F3), and | |||
follow the instructions. | |||
Installing Database Manager 61 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 62 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Installing as a Database Client or Client with Local Databases | |||
1. At the IBM Extended Services/2 Install/Remove menu: | |||
? Select "Install Database Manager" | |||
2. At the Target Drive Specification panel: | |||
? Specify the target drive where you want Database Manager installed | |||
3. If a previous version of Database Manager is detected, select "Remove previous | |||
version" from the Remove Previous Version of Selected Component pop-up. | |||
4. At the Database Manager Install menu: | |||
5. Select "Database Services", "Query Manager", and "Database Tools" (note that | |||
this is now a multi-select menu). | |||
6. At the Database Remote Data Services menu: | |||
? Select "Yes" | |||
7. At the Specify Database Manager Communications menu: | |||
? Select "Database Client" | |||
8. At the Databases on Your Workstation pop-up: | |||
? | |||
Select "No" | |||
Note | |||
You can select "Yes", if you also want to create databases on this | |||
workstation. If you do, you will actually be installing as a Database | |||
Client with Local Databases. This is a new Database Manager | |||
configuration with Extended Services. | |||
9. At the Workstation Name pop-up: | |||
? Specify a UNIQUE name for your workstation. (Note that if you plan to | |||
use NETBIOS as the protocol for this client, this name MUST be unique | |||
on the LAN). | |||
10. Follow the prompts to insert diskettes. | |||
11. If LAN Adapter and Protocol Support (LAPS) has not been installed, the | |||
'Warning: LAN Adapter and Protocol Support Not Installed' pop-up will | |||
display. | |||
12. At the IBM Extended Services/2 Install/Removemenu: | |||
? Select "Install Communications Manager" to configure and install the | |||
necessary CM features to support your configuration, if you have not | |||
already done so. You will need to configure and install the necessary | |||
communications adapter and protocol support in order to use Remote Data | |||
Services. | |||
-- or -- | |||
? | |||
Select F3=Exit to complete the Database Manager installation | |||
Installing Database Manager 62 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 63 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Installing as a Database Server | |||
1. At the IBM Extended Services/2 Install/Remove menu: | |||
? Select "Install Database Manager" | |||
2. At the Target Drive Specification panel: | |||
? Specify the target drive where you want Database Manager installed | |||
3. If a previous version of Database Manager is detected, select "Remove previous | |||
version" from the Remove Previous Version of Selected Component pop-up. | |||
4. At the Database Manager Install menu: | |||
5. Select "Database Services", "Query Manager", and "Database Tools" (note that | |||
this is now a multi-select menu). | |||
6. At the Database Remote Data Services menu: | |||
? Select "Yes" | |||
7. At the Specify Database Manager Communications menu: | |||
? Select "Database Server" | |||
8. At the Workstation Name pop-up: | |||
? Specify a UNIQUE name for your workstation. (Note that if you plan to | |||
use the NETBIOS protocol for client communications, this name MUST | |||
be unique on the LAN). | |||
9. Follow the prompts to insert diskettes. | |||
10. If LAN Adapter and Protocol Support (LAPS) has not been installed, the | |||
'Warning: LAN Adapter and Protocol Support Not Installed' pop-up will | |||
display. | |||
11. At the IBM Extended Services/2 Install/Remove menu: | |||
? Select "Install Communications Manager" to configure and install the | |||
necessary CM features to support your configuration, if you have not | |||
already done so. You will need to configure and install the necessary | |||
communications adapter and protocol support in order to use Remote Data | |||
Services. | |||
-- or -- | |||
? | |||
Select F3=Exit to complete the Database Manager installation | |||
Installing as a Database Client/Server | |||
1. At the IBM Extended Services/2 Install/Remove menu: | |||
? Select "Install Database Manager" | |||
2. At the Target Drive Specification panel: | |||
? Specify the target drive where you want Database Manager installed | |||
3. If a previous version of Database Manager is detected, select "Remove previous | |||
version" from the Remove Previous Version of Selected Component pop-up. | |||
4. At the Database Manager Install menu: | |||
Installing Database Manager 63 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 64 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
5. Select "Database Services", "Query Manager", and "Database Tools" (note that | |||
this is now a multi-select menu). | |||
6. At the Database Remote Data Services menu: | |||
? | |||
Select "Yes" | |||
7. At the Specify Database Manager Communications menu: | |||
? Select "Database Client/Server" | |||
8. At the Workstation Name pop-up: | |||
? Specify a UNIQUE name for your workstation. (Note that if you plan to | |||
use the NETBIOS protocol for communications, this name MUST be | |||
unique on the LAN). | |||
9. Follow the prompts to insert diskettes. | |||
10. If LAN Adapter and Protocol Support (LAPS) has not been installed, the | |||
'Warning: LAN Adapter and Protocol Support Not Installed' pop-up will | |||
display. | |||
11. At the IBM Extended Services/2 Install/Remove menu: | |||
? | |||
Select "Install Communications Manager" to configure and install the | |||
necessary CM features to support your configuration, if you have not | |||
already done so. You will need to configure and install the necessary | |||
communications adapter and protocol support in order to use Remote Data | |||
Services. | |||
-- or -- | |||
? Select F3=Exit to complete the Database Manager installation | |||
Installing Database Manager 64 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 65 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
9.0 Installing OS/2 LAN Requester | |||
Please read section 5.7, 﨤AN Server Version 2.0 Requester Restrictions?on | |||
page 34 before installing. | |||
*** PLEASE NOTE *** | |||
# For a 16-bit base IBM OS/2 LAN Requester, Version 2.0, driver level 281 will | |||
# run on SE manufacturing level 1.30.1. For a 32-bit base, IBM OS/2 LAN | |||
# requester will run on SE V.2.0 driver level 6.167. | |||
9.1 Basic Installation for OS/2 LAN Requester | |||
Please see the IBM Operating System/2 Local Area Network Server Version 2.0 | |||
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3, | |||
page 31. | |||
9.2 Advanced Installation for OS/2 LAN Requester | |||
Please see the IBM Operating System/2 Local Area Network Server Version 2.0 | |||
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3, | |||
page 33. | |||
9.3 Reinstalling, Reconfiguring or Removing | |||
Please see the IBM Operating System/2 Local Area Network Server Version 2.0 | |||
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3, | |||
page 43. | |||
Installing OS/2 LAN Requester 65 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 66 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
10.0 Installing OS/2 LAN Server | |||
Please read section 5.6, 﨤AN Server Version 2.0 Server Restrictions?on page 29 | |||
before installing. | |||
***PLEASE NOTE*** | |||
# The OS/2 LAN Server, V2.0, driver level 281, will run on the 16-bit based SE | |||
# manufacturing level 1.30.1, and on the 32-bit based SE driver level 6.167 | |||
10.1 Basic Installation for OS/2 LAN Server | |||
Please see the IBM Operating System/2 Local Area Network Server Version 2.0 | |||
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3, | |||
page 12. | |||
10.2 Advanced Installation for OS/2 LAN Server | |||
Please see the IBM Operating System/2 Local Area Network Server Version 2.0 | |||
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3, | |||
page 15. | |||
10.3 LAN Server 1.3 Migration Utility | |||
Please see the IBM Operating System/2 Local Area Network Server Version 2.0 | |||
Network Administrator Reference, Volume 1: Planning and Installation, chapter 1, | |||
page 20, and chapter 3, page 8. Also, please see the IBM OS/2 LAN Server V2.0 | |||
Migration Handbook . | |||
Installing OS/2 LAN Server 66 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 67 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
11.0 Installing IBM LAN Support Program and DOS LAN | |||
Requester | |||
Please read section 5.6, 﨤AN Server Version 2.0 Server Restrictions?on page 29 | |||
and 5.7, 﨤AN Server Version 2.0 Requester Restrictions?on page 34 before | |||
installing. | |||
11.1 Installing the IBM LAN Support Program, V.1.21 | |||
Please see the IBM Operating System/2 Local Area Network Server Version 2.0 | |||
Network Administrator Reference, Volume 1: Planning and Installation, chapter 5 | |||
and the IBM LAN Support Program User's Guide. | |||
11.2 Installing DOS LAN Requester | |||
Please see the IBM Operating System/2 Local Area Network Server Version 2.0 | |||
Network Administrator Reference, Volume 1: Planning and Installation, chapter 5. | |||
Installing IBM LAN Support Program and DOS LAN Requester 67 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 68 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Appendix | |||
Appendix 68 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 69 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Appendix A. SNA Advanced Configuration | |||
A.1 Overview | |||
Earlier this year, IBM introduced a software program product called Networking | |||
Services/2. This product was designed to enhance the performance of computers | |||
operating in OS/2 Extended Edition network environments. Networking Services/2 | |||
provides both APPN end node and network node support to workstations, allowing | |||
them greater flexibility when communicating with other workstations in the | |||
network. Networking Services/2 also offers the SAA Common Programming | |||
Interface (CPI) for communications, and an enhanced version of the Advanced | |||
Program to Program Communications (APPC) Application Programming Interface | |||
(API). Networking Services/2 greatly improved APPC throughput in | |||
performance-critical LAN environments. In addition, Networking Services/2 offers | |||
configuration and management services that provide both ease-of-use and improved | |||
function for network users. | |||
In this offering of Extended Services/2, the function provided by Networking | |||
Services/2 is incorporated into the Communications Manager product. This | |||
addition further enhances the usability and performance of APPN and | |||
Communications Manager, as well as the networking capability of your OS/2 EE | |||
system environment. With this added function, a workstation using Extended | |||
Services can participate in an APPN network as a low-entry networking (LEN) | |||
node, end node, or network node. | |||
A.1.1 The Configuration Process | |||
When you perform Advanced Configuration for SNA, Communications Manager | |||
builds a particular set of configuration files. All of these files have the same name as | |||
the configuration file you specify but different extensions. These files contain | |||
different information, based on the extension. The following list provides | |||
descriptions of the configuration files: | |||
.CFG Communications Manager binary configuration file, which contains DLC, | |||
SNA Gateway, X.25, 3270 LU, and LUA information. | |||
This file is updated following Verify and is placed in the \CMLIB directory. | |||
.NDF Node definitions configuration file, which contains an ASCII representation | |||
of the verbs used to configure APPN at startup time. You can use the .NDF | |||
file to perform additional SNA configuration by editing the file with any type | |||
of ASCII editor. | |||
This file is created following completion of the SNA Feature Configuration | |||
panel during configuration and is placed in the \CMLIB\APPN directory. | |||
.CF2 APPN binary configuration file, which contains a binary representation of | |||
the verbs used to configure APPN at startup time. This file must exist and | |||
cannot be empty to start APPN function. | |||
This file is created following Verify and is placed in the \CMLIB\APPN | |||
directory. | |||
Appendix A. SNA Advanced Configuration 69 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 70 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
.SEC Binary security configuration. | |||
This file is created following completion of the SNA Feature Configuration | |||
panel during configuration and is placed in the \CMLIB\APPN directory. | |||
.INI This file supports LAN adapter and protocol functions and is stored in the | |||
\IBMCOM directory. PROTOCOL.INI is the name of the .INI file for the | |||
active configuration on your workstation. | |||
The node definitions (.NDF) and .INI files can be modified using a text editor. | |||
You can modify the other configuration files using the Communications Manager | |||
configuration panels. | |||
Three scenarios for SNA Advanced Configuration are presented in this section: | |||
? | |||
5250 Advanced Configuration | |||
? 3270 over Token-Ring | |||
? 3270 over SDLC via Gateway. | |||
Sample Node Definitions files (NDF) for each of the scenarios are also included. | |||
A.2 Advanced Configuration for 5250 | |||
1. Copy and rename the ACSCFGUS.CFG file in the \CMLIB directory to create | |||
your new configuration file. | |||
(example: ) C>copy acscfgus.cfg 5250adv.cfg | |||
2. Restart Communications Manager using this file. | |||
(example: ) C>cm 5250adv | |||
3. Switch to the task list to access the Communications Manager Main Menu. | |||
4. Select the Advanced action bar item and then select the Configuration pulldown | |||
choice. Press Enter. | |||
A message box appears displaying the name of the configuration file. | |||
5. Press Enter. The Specify Configuration Usage panel appears. | |||
6. Select the first option if you intend to use this configuration on this workstation | |||
and press Enter. | |||
The Communication Configuration Menu appears. | |||
7. Select option 4, SNA feature profiles, and press Enter. | |||
The SNA Feature Configuration panel appears. | |||
8. Select Data Link Control (DLC) Profiles and press Enter. | |||
A message box appears showing the DLC types. | |||
9. Select option 3, Token-Ring or Other LAN type... and press Enter. | |||
The DLC Adapters and Operations panel appears. | |||
10. Select the two options Adapter 0 and Create and press Enter. | |||
The Create/Change IBM Token-Ring Network DLC Profile panel appears. | |||
Appendix A. SNA Advanced Configuration 70 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 71 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
11. Use all of the default values displayed for the fields on this panel, except for the | |||
C&SM LAN ID, where you must provide a value. Press Enter. | |||
The SNA Feature Configuration panel appears. | |||
12. Select SNA network definitions and press Enter. | |||
The SNA Definitions Options panel appears. | |||
13. Select Create/Change and press Enter. An informational message box appears. | |||
Press Enter. | |||
The Local Node Characteristics panel appears. | |||
14. For the Required Features, specify the following: | |||
Network ID | |||
The network ID is the same as that supplied in the SNA base of previous | |||
versions of Communications Manager. WARNING: The network ID | |||
CANNOT be blanks. | |||
Local node name | |||
The local node name is the same as that as that supplied for the PU or Control | |||
Point in previous versions of Communications Manager. | |||
Node type | |||
Accept the default node type of end node - no network node server. | |||
For the optional features: | |||
? Use the default supplied for the Local Node ID. | |||
? Use the same name you supplied for Local Node Name for the Local Node | |||
Alias Name, except enter the name in all caps. | |||
? Use the default supplied for the Activate Attach Manager at startup | |||
(selected). | |||
Select the OK push button and press Enter. The Basic SNA information | |||
message panel appears. Press Enter. The SNA Network Definitions Selection | |||
panel appears. | |||
15. Select Connections and select the Configure push button. | |||
The CM SNA Connections panel appears. | |||
16. Select To Primary Host and press Enter. | |||
The Adapter List panel appears. | |||
17. Select IBMTRNET and press Enter. | |||
The "Creating a Connection to a To Primary Host" panel appears. | |||
18. Use the default value supplied for the Link Name. | |||
Supply values for the Partner Network ID, Partner Node Name, and LAN | |||
Destination Address fields. | |||
Select the Define Partner LUs... push button. | |||
The "Creating Partner LU " panel appears. | |||
19. .Supply values for the LU name, and Alias fields (the Alias value must be in all | |||
caps) and then select the Add pushbutton. | |||
Appendix A. SNA Advanced Configuration 71 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 72 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
The LU name and alias you selected are added to the list box. | |||
Select the OK push button. | |||
The Creating a Connection to a To Primary Host panel appears. | |||
20. Select the OK push button to exit from this panel. | |||
The CM SNA Connections panel appears. | |||
21. Select the Configuration action bar choice and then select the Additional SNA | |||
Features... pulldown choice. | |||
The CM Additional SNA Features panel appears. | |||
22. Create a mode profile by selecting the Modes choice and pressing Enter. | |||
The Creating a Mode Definition panel appears. | |||
23. Supply the following values for the fields shown: | |||
Mode name: (supply a mode name) | |||
Class of service: #CONNECT (the default) | |||
Mode session limit: 64 | |||
Minimum contention winners: 32 | |||
Receive pacing window: 7 | |||
Select Default RU size. | |||
Select the OK push button. | |||
The CM Additional SNA Features panel appears. | |||
24. Select the File action bar choice and then select the Save and exit pulldown | |||
choice. | |||
The SNA Network Definitions Selection panel appears. | |||
25. Select the Exit push button. | |||
The SNA Feature Configuration panel appears. | |||
26. Press F3 to exit from the SNA Feature Configuration panel. | |||
The Communication Configuration Menu appears. | |||
27. Select option 6, LAN Adapter and Protocol Support and press Enter. | |||
The Options panel appears. | |||
28. Select Configure workstation (the default) and then select the OK pushbutton. | |||
A message appears stating that the configuration file is being read, and then the | |||
Configure Workstation panel appears. | |||
29. Select the OK pushbutton to use all of the defaults shown on this panel. | |||
The Options panel appears. | |||
30. Select Configuration complete (the default) and then select the OK pushbutton. | |||
The Communication Configuration Menu appears. | |||
Appendix A. SNA Advanced Configuration 72 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 73 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
31. Select option 7, 5250 workstation feature profiles and press Enter. | |||
The 5250 Workstation Feature Configuration panel appears. | |||
32. Select option 1, Terminal profiles... and press Enter. | |||
The Profile Operations panel appears. | |||
33. Select option 3, Create... and press Enter. The Specify Terminal Profile Names | |||
panel appears. | |||
34. Use the default supplied for the Model name (M1) and enter TERM in the | |||
Profile Name field. Press Enter. | |||
The Create/Change Terminal Options panel appears. | |||
35. Select option 1, Common terminal options and press Enter. | |||
The Common Terminal Options panel appears. | |||
36. Accept all the default values for the terminal options and press Enter. | |||
The Specify Workstation ID panel appears. | |||
Accept the defaults and leave the Workstation ID field blank. Press Enter. | |||
The Create/Change Terminal Options panel appears. | |||
37. Press F3 to exit from the Create/Change Terminal Options panel. | |||
The 5250 Workstation Features Configuration panel appears. | |||
38. Select option 3, Specify APPC LU alias... and press Enter. | |||
The Specify APPC LU Alias panel appears. | |||
39. Type the LU alias in the "APPC LU alias" field and press Enter. (This is the | |||
same value as the one supplied for the Local Node Name in step 14 on | |||
page 71.) | |||
40. The 5250 Workstation Features Configuration panel appears. | |||
41. Select option 4, Session assignments and press Enter. | |||
The 5250 Session Selection panel appears. | |||
42. Select Session Number 1 and press Enter. | |||
The 5250 Terminal/Printer Session Assignments panel appears. | |||
43. Supply the values for the following fields and press Enter. | |||
5250 Workstation Feature profile name | |||
Use the profile value "TERM", as shown in step 34. | |||
APPC partner LU alias | |||
Use the same value you used for supplying an alias in step 19 on page 71. | |||
APPC mode name | |||
Use the same value you used for supplying a mode name in step 23 on page 72. | |||
Short session ID | |||
Accept the default value for the short session ID (A). | |||
The 5250 Session Selection panel appears. | |||
Appendix A. SNA Advanced Configuration 73 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 74 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
44. Press F3 to exit the 5250 Session Selection panel. | |||
The 5250 Workstation Feature Configuration panel appears. | |||
45. Press F3 to exit the 5250 Workstation Feature Configuration panel. | |||
The Communication Configuration Menu panel appears. | |||
46. To verify your configuration file, press F10 and select the Verify action bar | |||
choice. Then select option 1, Run verify from the pulldown. | |||
A message box appears stating that the verification of the configuration file is in | |||
process. After the configuration file is verified, a message box appears that | |||
states the options for restarting and using the new configuration. | |||
47. Press Enter. Another message box appears stating that Communications | |||
Manager must be restarted to use the new configuration. | |||
48. Press Enter. The Communication Configuration Menu panel appears. | |||
49. Press F3 to exit from the Communication Configuration Menu. The | |||
Communications Manager Main Menu" panel appears. | |||
50. Press F3 to exit from the Communications Manager. | |||
A message box appears notifying that you are exiting from Communications | |||
Manager and asks you if you are sure. | |||
51. Select option 1, Yes and press Enter. | |||
Another message panel appears stating that the Communications Manager | |||
features have ended successfully. | |||
52. Press F3 to exit the Communications Manager. | |||
53. Restart Communications Manager using the new configuration file. | |||
(example: C>start cm 5250adv) | |||
Switch to the task list to access the Communications Manager Main Menu. | |||
54. Select option 1, Start emulators and press Enter. | |||
The Start Communications panel appears. | |||
55. Select option 4, 5250 Work Station Feature and press Enter. | |||
The Select 5250 Work Station Feature Sessions to Start panel appears. | |||
56. Select ALL and press enter. | |||
The Logon panel appears. | |||
57. Type the UPM user ID and password in the appropriate fields and press Enter. | |||
The 5250 host sign on screen appears for the active 5250 session. | |||
Appendix A. SNA Advanced Configuration 74 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 75 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
A.2.1 5250ADV .NDF File Example | |||
DEFINE_LOCAL_CP FQ_CP_NAME(NETNAME.NODENAME ) | |||
CP_ALIAS(ALIASNAM) | |||
NAU_ADDRESS(INDEPENDENT_LU) | |||
NODE_TYPE(EN) | |||
NODE_ID(X'00000') | |||
HOST_FP_SUPPORT(YES) | |||
HOST_FP_LINK_NAME(LINK0001); | |||
DEFINE_LOGICAL_LINK LINK_NAME(LINK0001) | |||
FQ_ADJACENT_CP_NAME(USIBMTH.AUSHATT ) | |||
ADJACENT_NODE_TYPE(LEN) | |||
DLC_NAME(IBMTRNET) | |||
ADAPTER_NUMBER(0) | |||
DESTINATION_ADDRESS(X'400033345678') | |||
CP_CP_SESSION_SUPPORT(NO) | |||
ACTIVATE_AT_STARTUP(YES) | |||
LIMITED_RESOURCE(USE_ADAPTER_DEFINITION) | |||
LINK_STATION_ROLE(USE_ADAPTER_DEFINITION) | |||
SOLICIT_SSCP_SESSION(YES) | |||
EFFECTIVE_CAPACITY(USE_ADAPTER_DEFINITION) | |||
COST_PER_CONNECT_TIME(USE_ADAPTER_DEFINITION) | |||
COST_PER_BYTE(USE_ADAPTER_DEFINITION) | |||
SECURITY(USE_ADAPTER_DEFINITION) | |||
PROPAGATION_DELAY(USE_ADAPTER_DEFINITION) | |||
USER_DEFINED_1(USE_ADAPTER_DEFINITION) | |||
USER_DEFINED_2(USE_ADAPTER_DEFINITION) | |||
USER_DEFINED_3(USE_ADAPTER_DEFINITION); | |||
DEFINE_PARTNER_LU FQ_PARTNER_LU_NAME(USIBMTH.AUSHATT ) | |||
PARTNER_LU_ALIAS(AUSHATT) | |||
MAX_MC_LL_SEND_SIZE(32767) | |||
CONV_SECURITY_VERIFICATION(NO) | |||
PARALLEL_SESSION_SUPPORT(YES); | |||
DEFINE_PARTNER_LU_LOCATION FQ_PARTNER_LU_NAME(USIBMTH.AUSHATT ) | |||
WILDCARD_ENTRY(NO) | |||
FQ_OWNING_CP_NAME(USIBMTH.AUSHATT ) | |||
LOCAL_NODE_NN_SERVER(NO); | |||
DEFINE_MODE MODE_NAME(QPCSUPP ) | |||
COS_NAME(#CONNECT) | |||
DEFAULT_RU_SIZE(YES) | |||
RECEIVE_PACING_WINDOW(7) | |||
MAX_NEGOTIABLE_SESSION_LIMIT(32767) | |||
PLU_MODE_SESSION_LIMIT(64) | |||
MIN_CONWINNERS_SOURCE(32); | |||
DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES) | |||
DEFAULT_MODE_NAME(BLANK) | |||
MAX_MC_LL_SEND_SIZE(32767) | |||
DIRECTORY_FOR_INBOUND_ATTACHES(*) | |||
Appendix A. SNA Advanced Configuration 75 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 76 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED) | |||
DEFAULT_TP_PROGRAM_TYPE(BACKGROUND) | |||
DEFAULT_TP_CONV_SECURITY_RQD(NO) | |||
MAX_HELD_ALERTS(10); | |||
START_ATTACH_MANAGER; | |||
A.3 Advanced Configuration for 3270 Over Token-Ring | |||
1. Copy and rename the ACSCFGUS.CFG file in the \CMLIB directory to create | |||
your new configuration file. | |||
(example: C>copy acscfgus.cfg 3270tr.cfg) | |||
2. Restart Communications Manager using this file. | |||
(example: C>start cm 3270tr) | |||
3. Switch to the task list to access the Communications Manager Main Menu. | |||
The Communications Manager Main Menu appears. | |||
4. Select the Advanced action bar item and then select the Configuration pulldown | |||
choice. Press Enter. | |||
A message box appears displaying the name of the configuration file. | |||
5. Press Enter. The Specify Configuration Usage panel appears. | |||
6. Select the first option if you intend to use this configuration on this workstation.. | |||
The Communication Configuration Menu appears. | |||
7. Select option 3, 3270 feature profiles and press Enter. The 3270 Feature | |||
Configuration panel appears. | |||
8. Select option 3, IBM Token-Ring or Other LAN type... and press Enter. The | |||
Profile Operations panel appears. | |||
9. Select option 2, Create/Change and press Enter. | |||
The Create/Change 3270 Profile panel appears. | |||
10. Select option 1, Connection. | |||
The Specify Link Information panel appears. | |||
11. Select Adapter 0 (the default) for the Adapter number field and supply the | |||
destination address in the Destination Address field and press Enter. | |||
The Create/Change 3270 Profile panel re-appears. | |||
12. Select sessions to configure for a terminal. | |||
The Create/Change 3270 Logical Terminal Profile panel appears. | |||
Use the default values supplied for all of the fields on this panel and supply a | |||
session ID and LU Local Address. | |||
Press F3 two times to return to the Communication Configuration Menu. You | |||
will receive a warning that the DLC must be configured; press Enter. Select | |||
option 4, SNA Feature Profiles and press Enter. | |||
Appendix A. SNA Advanced Configuration 76 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 77 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
The SNA Feature Configuration panel appears. | |||
13. Select Data Link Control (DLC) Profiles and press Enter. | |||
A message box appears showing the DLC types. | |||
14. Select option 3, Token-Ring or Other LAN type.. and press Enter. | |||
The DLC Adapters and Operations panel appears. | |||
15. Select the two options Adapter 0 and Create and press Enter. | |||
The Create/Change IBM Token-Ring Network DLC Profile panel appears. | |||
16. Use all of the default values displayed for the fields on this panel, except for the | |||
C&SM LAN ID, where you must provide a value. Press Enter. | |||
The SNA Feature Configuration panel appears. | |||
17. Select SNA network definitions and press Enter. | |||
The SNA network definitions options panel appears. Select Create/Change, and | |||
press enter. | |||
The "Creating Basic SNA Node Information" panel appears. | |||
18. Select OK. | |||
The Local Node Characteristics panel appears. | |||
19. For the Required Features, specify the following: | |||
Network ID | |||
The network ID is the same as that supplied in the SNA base of previous | |||
versions in Communications Manager. WARNING: The Network ID cannot | |||
be blanks. | |||
Local node name | |||
The local node name is the same as that as that supplied for the PU or Control | |||
Point in previous versions of Communications Manager. | |||
Node type | |||
Accept the default node type of end node - no network node server. | |||
For the optional features: | |||
? Use the default supplied for the Local Node ID. | |||
? Use the same name you supplied for Local Node Name for the Local Node | |||
Alias Name, except enter the name in all caps. | |||
? Select Activate Attach Manager at startup. | |||
Select the OK push button and press Enter. | |||
You will receive an informational message on the Basic SNA Node Information | |||
Created. Press the OK push button. | |||
You will see the SNA Network Definitions Selection. Select the Exit push | |||
button. | |||
The SNA Feature Configuration panel appears. | |||
20. Select F3 to exit from this panel. | |||
The Communication Configuration Menu appears. | |||
Appendix A. SNA Advanced Configuration 77 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 78 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
21. Select option 6, LAN Adapter and Protocol Support and press Enter. | |||
The Options screen appears. | |||
22. Select Configure Workstation and press Enter. | |||
The Configure Workstation panel appears. | |||
23. Select the following on this panel: | |||
? Select IBM Token-ring Adapters from Network Adapters. | |||
A pop-up screen appears showing the adapters in the current configuration. | |||
? | |||
Select IBM IEEE 802.2 from Protocols. | |||
A pop-up screen appears showing the current configuration for this item. | |||
At this point, you can either: | |||
? Select OK to complete configuration (and use the supplied defaults). | |||
Note: If you choose this action, you can bypass step 24. | |||
? Highlight the IBM Token-ring Adapters choice in the Current | |||
Configuration box and select the Edit push button to edit the parameters | |||
you created. | |||
24. Use the edit box to edit the parameters for the token-ring adapters or the IBM | |||
IEEE 802.2 entries. | |||
Select OK when you are finished editing. | |||
25. Select OK to exit the Configure Workstation panel. | |||
The Options panel appears. | |||
26. Select Configuration complete (the default). | |||
The Communication Configuration panel appears. | |||
27. Select the Verify action bar choice and then select the Run Verify pulldown | |||
choice to verify the configuration file. | |||
Note: A screen may appear stating that inconsistencies were found. If this occurs, | |||
access the message log to view the messages and perform the following steps. For | |||
example, you may be asked to do a REINST if the features you configured are not | |||
installed yet. | |||
1. Stop Communications Manager and type the command at the command REINST | |||
prompt. This action restarts Communications Manager using the configuration | |||
file you created. | |||
2. On the REINST screen, select Install Additional Features and press Enter. | |||
3. Select LAN Adapter and Protocol Support, for example, if this is the feature | |||
which needs to be installed. | |||
Appendix A. SNA Advanced Configuration 78 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 79 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
A.3.1 3270TR .NDF File Example | |||
DEFINE_LOCAL_CP FQ_CP_NAME(NETNAME.NODENAME ) | |||
CP_ALIAS(ALIASNAM) | |||
NAU_ADDRESS(INDEPENDENT_LU) | |||
NODE_TYPE(EN) | |||
NODE_ID(X'00000') | |||
HOST_FP_SUPPORT(NO); | |||
DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES) | |||
DEFAULT_MODE_NAME(BLANK) | |||
MAX_MC_LL_SEND_SIZE(32767) | |||
DIRECTORY_FOR_INBOUND_ATTACHES(*) | |||
DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED) | |||
DEFAULT_TP_PROGRAM_TYPE(BACKGROUND) | |||
DEFAULT_TP_CONV_SECURITY_RQD(NO) | |||
MAX_HELD_ALERTS(10); | |||
START_ATTACH_MANAGER; | |||
A.4 Advanced Configuration for 3270 Gateway | |||
1. Copy and rename the ACSCFGUS.CFG file in the \CMLIB directory. | |||
(example: ) C>copy acscfgus.cfg 3270gw.cfg | |||
2. Restart Communications Manager using this file. | |||
(example: ) C>start cm 3270gw | |||
3. Switch to the task list to access the Communications Manager Main Menu. | |||
4. Select the Advanced action bar item and then select the Configuration pulldown | |||
choice. Press Enter. | |||
A message box appears displaying the name of the configuration file. | |||
5. Press Enter. | |||
The Specify Configuration Usage panel appears. | |||
6. Select the first option if you intend to use this configuration on this workstation. | |||
The Communication Configuration Menu appears. | |||
7. Select option 3, 3270 feature profiles, and press Enter. The 3270 Feature | |||
Configuration panel appears. | |||
8. Select option 2, SDLC... and press Enter. | |||
The Profile Operations panel appears. | |||
9. Select option 2, Create/Change and press Enter. | |||
The Create/Change 3270 Profile panel appears. | |||
10. Select option 1, Connection, and press Enter. The Select SDLC Adapter panel | |||
appears. | |||
11. Select option 1, Adapter 0 and press Enter. The Create/Change 3270 Profile | |||
panel re-appears. | |||
Appendix A. SNA Advanced Configuration 79 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 80 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
12. Select the sessions to configure for the terminal. The Create/Change 3270 | |||
Logical Terminal Profile panel appears. Select Profile type panel appears. | |||
Select Option 1, Terminal and press Enter. | |||
13. Use the default values supplied for all of the fields on this panel and supply the | |||
values for the following fields: | |||
? Session ID/LU name | |||
? LU local address. | |||
14. Press Enter to return to the Create/Change 3270 Profile. | |||
15. Press F3 two times to return to the Communication Configuration Menu. | |||
A warning message appears stating that an appropriate DLC must be configured | |||
before 3270 emulation can be used. | |||
16. Press Enter to return to the Communication Configuration Menu. | |||
17. Select option 4, SNA Feature Profiles and press Enter. The SNA feature | |||
configuration panel appears. | |||
18. Select Data Link Control (DLC) profiles... and press Enter. A message box | |||
appears showing the DLC types. | |||
19. Select option 1, SDLC... and press Enter. The DLC Adapters and Operations | |||
panel appears. | |||
20. Select the two options Adapter 0 and Create and then press Enter. The | |||
Create/Change SDLC DLC Adapter Profile panel appears. | |||
21. Use all of the default values displayed for the fields on this panel, except for the | |||
Free unused link field. Select No for this field and press Enter. The Specify | |||
Data Set Ready Timeout panel appears. | |||
22. Accept the default value of 5 minutes and press Enter. The Specify Negotiable | |||
Link Station Data panel appears. | |||
23. Accept the defaults for the fields on this panel and press Enter. | |||
The SNA Feature Configuration panel re-appears. | |||
24. Select SNA network definitions and press Enter. | |||
The SNA network definitions options panel appears. Select Create/Change, and | |||
press Enter. | |||
An informational message appears on Creating basic SNA node information. | |||
25. Select the OK pushbutton to proceed to the Local Node Characteristics | |||
configuration panel. | |||
26. For the Required Features, specify the following: | |||
Network ID | |||
The network ID is the same as that supplied in the SNA base of previous | |||
versions of Communications Manager. WARNING: The Network ID cannot | |||
be blanks. | |||
Local node name | |||
The local node name is the same as that as that supplied for the PU or Control | |||
Point in previous versions of Communications Manager. | |||
Appendix A. SNA Advanced Configuration 80 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 81 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Node type | |||
Accept the default node type of End Node - No Network Node Server. | |||
For the Optional Features: | |||
? | |||
Use the default supplied for the Local Node ID. | |||
? Use the same name you supplied for Local Node Name for the Local Node | |||
Alias Name, except enter the name in all caps. | |||
27. Select the OK push button and press Enter. | |||
An informational message appears on the Basic SNA information created. Select | |||
the OK push button and press enter. | |||
The SNA Network Definition Selection panel appears. Select the Exit push | |||
button and press Enter. | |||
The SNA Feature Configuration panel appears. | |||
28. Select SNA gateway profiles... and press Enter. The Select Gateway Profile | |||
Type panel appears. | |||
29. Select option 1, Host Connection... and press Enter. The Profile Operations | |||
panel appears. | |||
30. Select option 3, Create and press Enter. The Create/Change SNA Gateway | |||
Host Connection Profile (1 of 2) panel appears. | |||
31. Set the values for the following fields and press Enter: | |||
DLC type SDLC (default) | |||
Permanent connection Yes | |||
Auto-logoff timeout (minutes) 61 | |||
The Select Adapter panel appears. | |||
32. Select option 1, Adapter 0 and press Enter. The Create/Change SNA Gateway | |||
Host Connection Profile (2 of 2) panel appears. | |||
33. Leave this panel blank and press Enter. The SNA Feature Configuration panel | |||
returns. | |||
34. Select SNA gateway profiles... again and press Enter. The Select Gateway | |||
Profile Type panel appears. | |||
35. Select option 2, Workstation LU... and press Enter. The Profile Operations | |||
panel appears. | |||
36. Select option 3, Create and press Enter. The Specify Profile Names panel | |||
appears. | |||
37. Accept the default for the Model profile name field (M6) and type ALICEWS1 | |||
in the profile name field. Press Enter. The Create/Change SNA Gateway | |||
Workstation LU Profile panel appears. | |||
38. Set the values for the following fields and press Enter: | |||
Appendix A. SNA Advanced Configuration 81 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 82 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
LU name at workstation ALICEWS1 | |||
Comment (Optional) | |||
PU name of workstation ALICEPU1 | |||
LU pooling Dedicated | |||
LU local address at workstation (hex) * | |||
Note: Enter the LU local address entered on the | |||
Create/Change 3270 Logical Terminal Profile. | |||
See 13 on page 80 for the | |||
LU local address field. | |||
DLC type SDLC | |||
The Specify Dedicated LU Parameters panel appears. | |||
39. Supply a value for the LU local address at host field and accept the default value | |||
for the Auto-logoff field (NO). Press Enter. The Select Adapter panel appears. | |||
40. Select option 1, Adapter 0 and press Enter. | |||
The SNA Feature Configuration panel re-appears. | |||
41. Press F3 to return to the Communication Configuration Menu. | |||
42. Verify the configuration and re-start the Communications Manager to use the | |||
new configuration. | |||
Verify from action bar, and press enter. | |||
Select Option 1, Run Verify and press enter. | |||
A.4.1 3270GW .NDF File Example | |||
A node definition file is built for you with the following set of default verbs: | |||
DEFINE_LOCAL_CP FQ_CP_NAME(APPN.ATIG ) | |||
CP_ALIAS(atig ) | |||
NAU_ADDRESS(INDEPENDENT_LU) | |||
NODE_TYPE(EN) | |||
NODE_ID(X'00000') | |||
HOST_FP_SUPPORT(NO); | |||
DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES) | |||
DEFAULT_MODE_NAME(BLANK) | |||
MAX_MC_LL_SEND_SIZE(32767) | |||
DIRECTORY_FOR_INBOUND_ATTACHES(*) | |||
DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED) | |||
DEFAULT_TP_PROGRAM_TYPE(BACKGROUND) | |||
DEFAULT_TP_CONV_SECURITY_RQD(NO) | |||
MAX_HELD_ALERTS(10); | |||
Appendix A. SNA Advanced Configuration 82 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 83 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Appendix B. EHLLAPI Virtual Device Driver (VDD) | |||
# *** NOTE *** | |||
# The EHLLAPI VDD does not function correctly with the OS/2 SE 2.0 driver | |||
# level 6.167. To use the EHLLAPI VDD, OS/2 2.0 level 6.605 must be used. | |||
B.1 Overview | |||
This IBM Extended Services for OS/2 driver contains a new EHLLAPI Virtual | |||
Device Driver (VDD) to allow existing DOS HLLAPI applications to run in the | |||
Virtual DOS Machine on the OS/2 2.0 operating system. This appendix gives the | |||
information on how to use the EHLLAPI VDD. | |||
The EHLLAPI Virtual Device Driver support is installed when you install | |||
Communications Manager with a 3270 configuration file. The Installation of the | |||
EHLLAPI VDD will enable the user to run existing DOS HLLAPI applications in | |||
the OS/2 2.0 Virtual DOS Machine (VDM) environment using Extended Services | |||
EHLLAPI with the Communications Manager. | |||
Although an effort was made to be compatable with the Personal Communications | |||
3270 EHLLAPI 2.0, some differences exist and are noted below. | |||
It is recommended the DOS application be recompiled and linked to be executed in | |||
the OS/2 environment if possible. This will enhance the overall performance of the | |||
system and allow for inclusion of the many enhancements available in the | |||
Communications Manager EHLLAPI. | |||
B.2 Installation | |||
The following statement should be added to the end of the CONFIG.SYS file (it | |||
must follow the loading of physical device drivers): | |||
? DEVICE=x:\CMLIB\VHAPI.OS2 | |||
(where x is the logical drive on which Communications Manager is installed) | |||
Note: Machine must be restarted after making changes to CONFIG.SYS. | |||
Appendix B. EHLLAPI Virtual Device Driver (VDD) 83 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 84 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
B.3 Usage | |||
Bring up the Communications Manager and start 3270 communications. Establish | |||
the same conditions in the host session window as are required in the DOS | |||
emulator session by the DOS HLLAPI application. Create an OS/2 2.0 VDM | |||
Window and start the DOS HLLAPI application. | |||
B.4 Compatability (With Personal Communications 3270 2.0) | |||
Appendix B. EHLLAPI Virtual Device Driver (VDD) 84 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 85 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Deviations: | |||
Because of existing differences between the Per Com and OS/2 3270 | |||
emulators there are some differences in the EHLLAPI support: | |||
1. ASCII mnemonic differences | |||
- The following mnemonics are not supported by PER COM 3270 2.0. | |||
However, since the OS/2 emulator generates them they may be | |||
received by EHLLAPI applications running in the DOS box under OS/2 2.0) | |||
1. @q End | |||
2. @A@D Word Delete | |||
3. @A@L Cursor Left fast | |||
4. @A@N Get Cursor | |||
5. @A@O Locate Cursor | |||
6. @A@Z Cursor Fast Right | |||
7. @A@9 Reverse Video | |||
8. @A@b Underscore | |||
9. @A@c Reset Reverse video | |||
10. @A@d Red | |||
11. @A@e Pink | |||
12. @A@f Green | |||
13. @A@g Yellow | |||
14. @A@h Blue | |||
15. @A@i Turquoise | |||
16. @A@j White | |||
17. @A@l Reset Host colors | |||
18. @/ Overrun of queue (get key function only) | |||
19. @S@T Jump to Task Mgr (Extended Services 1.0) | |||
- The following lists differences between mnemonics supported by | |||
both EHLLAPIs | |||
1. @< Backspace | |||
- Per Com treats this as a destructive backspace | |||
- OS2 treats this as a non destructive backspace | |||
note: When received by an EHLLAPI application running in the | |||
DOS box under OS/2 2.0 this mnemonic should be treated as | |||
a non destructive backspace. | |||
- The following mnemonics are not supported by EHLLAPI on a 3270 | |||
session | |||
1. @S@A Erase EOL | |||
2. @S@B Field Advance | |||
3. @S@C Field Backspace | |||
4. @S@D Valid Backspace character | |||
5. @r@t Pause | |||
2. Copy OIA content | |||
1. Column 21 | |||
- Per Com returns value of 0xF6 | |||
- OS2 returns value of 0x20 | |||
note: The value of 0x20 will be returned in the OS/2 2.0 | |||
DOS box. | |||
2. Columns 61-63 | |||
Appendix B. EHLLAPI Virtual Device Driver (VDD) 85 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 86 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
- Per Com will not return printer information | |||
note: Values in these columns may be returned in the OS/2 | |||
2.0 DOS box. | |||
3. Group 3 Shift State | |||
- bit 2 CAPS is not returned by OS2 | |||
(bit 0 set for both upper case and CAPSLOCK in OS2 with | |||
bit 2 reversed) | |||
note: Bit 2 will continue to be reserved in the OS/2 2.0 | |||
DOS box. | |||
4. Group 8 byte 1 Input Inhibited | |||
- bit 6 Device not working not returned by Per Com | |||
note: This bit may be set in the OS/2 2.0 DOS box. | |||
5. Group 8 byte 2 | |||
- bit 1 OS2 Terminal Wait not returned by Per Com | |||
note: This bit may be set in the OS/2 2.0 DOS box. | |||
6. Group 8 byte 3 | |||
- bit 1 Operation unauthorized not returned by Per Com. | |||
- bit 2 Operation unauthorized minus function not | |||
returned by Per Com. | |||
note: These bits may be set in the OS/2 2.0 DOS box. | |||
7. Group 10 Highlight #2 | |||
- bit 0 Selected not returned by Per Com | |||
note: This bit may be set in the OS/2 2.0 DOS box. | |||
8. Group 11 Color #2 | |||
- bit 0 Selected not returned by Per Com | |||
note: This bit may be set in the OS/2 2.0 DOS box. | |||
9. Group 13 Printer Status | |||
- This group is reserved in Per Com | |||
note: This group may be set in the OS/2 2.0 DOS box. | |||
10. Group 14 Graphics | |||
- bit 0 Graphics cursor not returned by OS2 | |||
note: This bit will not be returned in the OS/2 2.0 DOS | |||
box. | |||
3. Presentation Space character/field attributes translated under | |||
the XLATE parm do not match (both are supposed to be CGA format). | |||
Note: The purpose of this function is to provide a | |||
Char/Attribute buffer to be displayed on the applications | |||
Appendix B. EHLLAPI Virtual Device Driver (VDD) 86 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 87 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
screen that reflects exactly the text and colors of the | |||
host presentation space. Since the Per Com implementation | |||
performs this function incorrectly, the attributes | |||
returned under OS/2 will be returned without alteration. | |||
4. Host PS null characters (0x00) are translated to blanks (0x20) | |||
under Per Com. They are not translated under OS/2. This may | |||
affect searches (in Per Com EHLLAPI appls) for character strings | |||
that include blanks that are null characters under OS/2. | |||
5. Host Presentation Space sizes supported are different between the | |||
two emulators. A user running a Per Comm EHLLAPI application | |||
under OS/2 2.0 must make sure that he doesn't configure a PS mod | |||
type that is larger than the Per Com application can handle. PS | |||
sizes for Per Com are between 1920 (24x80) and 3564 (27x132). | |||
Sizes for OS/2 are between 1920 and 7446 (146x51). | |||
note: OS/2 2.0 DOS will support up the the maximum OS/2 size if | |||
the application can handle it. | |||
6. Storage Manager is different between the APIs. | |||
Note: Setup of Storage Manager during configuration is not | |||
required under OS/2. The maximum of 10 K bytes is | |||
automatically preallocated outside of the DOS heap. | |||
7. Considerations for using functions 90 & 91 in PER COM pub do not | |||
apply. | |||
8. PERCOM EHLLAPI messages are not generated under OS/2. | |||
9. In OS/2 Trace is sent to file. In PER COM it is sent to screen. | |||
Note: Under OS/2 2.0 OS/2 trace rules will be applied. | |||
10. Send/Receive: PM window will be created to display status | |||
messages (non Quiet mode). | |||
11. Send/Receive: PS Position parameter specification of 0 for | |||
Current directory is not supported in PERCOM. | |||
Note: Under OS/2 2.0 a specification of 0 will be supported if | |||
received. | |||
12. As in Per Com, the DOS EHLLAPI application running under OS/2 | |||
2.0 will run on the interrupt thread. This means that hitting | |||
Ctrl-C and Ctrl-Break, will have no effect when the thread is | |||
suspended, waiting for an EHLLAPI function to complete. | |||
However, under OS/2 2.0 the user may optionally close the DOS | |||
window running the EHLLAPI application even when the thread is | |||
suspended waiting for a function to complete (Warning: in this | |||
case the 3270 emulation resources remain allocated until the | |||
pending EHLLAPI function issued by the departed DOS application | |||
is complete). | |||
Appendix B. EHLLAPI Virtual Device Driver (VDD) 87 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 88 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
13. Functions 41-43 (Close Click Intercept) and 101-106 (Windowing) | |||
are not supported under Per Com. | |||
note: These functions will not be supported under OS/2 2.0. | |||
Appendix B. EHLLAPI Virtual Device Driver (VDD) 88 | |||
IBM CONFIDENTIAL Extended Services Driver S1A246 89 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167 | |||
Appendix C. Communications Manager Stop API | |||
C.1 Overview and Usage | |||
Included in this driver of Communications Manager is a new API to stop the | |||
Communications Manager. The following description is written using the same | |||
format as the OS/2 Control Program, Programming Reference. For additional | |||
information, see the OS/2 Control Program Programming Reference which is a | |||
volume of the IBM OS/2 Programmer's Toolkit version 1.2. | |||
CmkDeactivateService - | |||
Request to Stop the Communication Manager | |||
This call will have the Communications Manager start exit processing | |||
when the Main Menu is displayed. | |||
CmkDeactivateService (StopType, Service, Reserved_1, Reserved_2, rc) | |||
PARAMETERS | |||
StopType(USHORT) - input | |||
Type of stop process requested. | |||
StopType codes: | |||
* CMK_SOFT 0 - Exit when Complete | |||
* CMK_HARD 1 - Exit Immediate | |||
Service(ULONG) - input | |||
Service number of Communication Manager | |||
* CMK_ALL_FEATURES 1 - Stop Communications Manager | |||
Reserved_1(ULONG) - input | |||
Reserved and should be set to 0 | |||
Reserved_2(USHORT) - input | |||
Reserved and should be set to 0 | |||
rc(USHORT) - return | |||
Return code descriptions are: | |||
0 CMK_SUCCESSFUL | |||
22 CMK_ERR_INVALID_SERVICE | |||
23 CMK_ERR_SYSTEM_ERROR | |||
REMARKS | |||
This call will request the Communications Manager to start exit | |||
processing. The CMK_SOFT stop is the equivalent of selecting | |||
"Exit when Complete" from the EXIT pulldown on the Communications | |||
Manager Main Menu. The CMK_HARD stop corresponds to the "Exit | |||
immediately" option. | |||
Processing of the stop request will only occur when the Main Panel | |||
is being displayed, or when a user returns to the Main Panel after | |||
preforming some action like configuration. | |||
Appendix C. Communications Manager Stop API 89 | |||
� | |||
</pre> | |||
</div></div> | |||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
INDBC167.DOC | |||
<div class="mw-collapsible-content"> | |||
<pre width="87"> | |||
Restrictions and Installation Instructions for | |||
IBM Extended Services for OS/2 | |||
Database Manager Clients Feature (Driver S1A246) | |||
October 18, 1991 2:45 p.m. | |||
IBM CONFIDENTIAL Database Manager Clients Driver S1A246 | |||
This document contains information of a proprietary nature. ALL INFORMATION CONTAINED | |||
HEREIN SHALL BE KEPT IN CONFIDENCE. None of this information herein shall be divulged to | |||
persons other than IBM employees authorized by the nature of their duties to receive such information, or | |||
individuals or organizations who are authorized in writing in accordance with existing policy regarding release | |||
of company information. This material, if exported from the United States, is shipped under General | |||
License GTDR. | |||
Restrictions and Installation Instructions for | |||
IBM Extended Services for OS/2 | |||
Database Manager Clients Feature (Driver S1A246) | |||
October 18, 1991 2:45 p.m. | |||
IBM CONFIDENTIAL Database Manager Clients Driver S1A246 | |||
IBM CONFIDENTIAL Database Manager Clients Driver S1A246 | |||
Contents | |||
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 | |||
2.0 Database Manager Clients Restrictions/Limitations ............ . . . 2 | |||
3.0 Installation Instructions ............. . . . . . . . . . . . . . . . . . . 5 | |||
4.0 Applying Patches to the OS/2.NETBIOS.Client . . . . ....... . . . . 6 | |||
4.1 Instructions for Applying Database Manager Client.Patches . . . . . . . . 6 | |||
Contents ii | |||
IBM CONFIDENTIAL Database Manager Clients Driver S1A246 | |||
1.0 Introduction | |||
This document provides the driver restrictions and installation instructions for the | |||
Database Manager Clients feature of the IBM Extended Services for OS/2 program. | |||
The feature consists of the following code and publications: | |||
1. Diskettes (3 1/2" format): | |||
? 2 OS/2 NETBIOS Database Client diskettes | |||
? 2 DOS Database Client/DOS Windows Database Client diskettes | |||
? 1 PC LAN Support Program diskette (** shipped with the LAN Server | |||
V2.0 program) | |||
2. Publications | |||
? Guide to Database Manager Clients | |||
? Network Administrator's Guide (** part of Extended Services | |||
Administrator's Ship group) | |||
? LAN Adapter and Protocol Support Configuration Guide (** part of | |||
Extended Services Administrator's Ship group) | |||
? PC LAN Support Program User's Guide (** part of LS V2.0 ship group | |||
sent with previous Extended Services/LAN Server driver) | |||
Introduction 1 | |||
IBM CONFIDENTIAL Database Manager Clients Driver S1A246 | |||
2.0 Database Manager Clients Restrictions/Limitations | |||
The following restrictions/limitations apply to the Database Manager Clients feature | |||
for this driver. | |||
? | |||
OS/2 NETBIOS Client Installation/Custom Diskette Creation: | |||
?You must have at least 500K Bytes available on the C: drive for use by the | |||
OS/2 NETBIOS Client install program. If OS/2 is booted from a drive | |||
other than C:, the C: drive is still used for temporary working space for the | |||
install program. | |||
# ?If OS/2 is booted from a drive other than C:, the installation of the OS/2 | |||
# NETBIOS Client will not work. CONFIG.SYS is incorrectly updated | |||
# (causing multiple error messages during IPL) and several files do NOT get | |||
# installed. | |||
# The workaround, if you plan to install the client from an OS/2 system | |||
# which has been booted from a drive other than C:, is as follows: | |||
# ?Edit the INSTALL.CMD file on the OS/2 NETBIOS Database Client | |||
# Installation Diskette #1: | |||
# Change the designated drive in line PKUNZIP2 REQINSTR.ZIP C:\ | |||
# -o -d 1>NUL 2>NUL to the drive you have booted your system | |||
# from. | |||
?If you are attempting to install the OS/2 NETBIOS Client on top of a | |||
previous version of Extended Services, you must first erase the file | |||
x:\IBMLVL.INI (where x: is the drive which OS/2 is booted from). | |||
?During Install, the ONLY valid network adapters are the ones currently | |||
listed in the Guide to Database Manager Clients under "Software and | |||
Hardware Requirements. The menu that comes up during Install to allow | |||
you to select your network adapter incorrectly lists more adapters than can | |||
validly be selected. | |||
?You CANNOT create a Custom Build Diskette for an OS/2 SE V2.0 | |||
workstation. The diskette that gets created will ONLY work on OS/2 SE | |||
V1.30.1 workstations. | |||
?After creating a custom diskette, you are told to remove the diskette. If you | |||
do so BEFORE you press 'enter', you will get a "drive not ready" message. | |||
Leave the custom diskette in drive a: until after pressing 'enter'. | |||
?During Install, after selection of the network adapter, the "percentage of | |||
installation complete" indicator is not correctly displayed. (** OS/2 SE V2.0 | |||
Level 6.605 ONLY) | |||
?During Install and/or Custom Diskette creation, 'HELP' does not work | |||
from the following panels/menus: | |||
?Incompatible Versions | |||
?File Backup | |||
?Source Drive | |||
Database Manager Clients Restrictions/Limitations 2 | |||
IBM CONFIDENTIAL Database Manager Clients Driver S1A246 | |||
?On the panel asking you to check the terms and conditions of the licensing | |||
agreement, there is a 'HELP' pushbutton, but it has no effect. | |||
?On the Custom Diskette Panel, 'HELP' states that you will need a second | |||
diskette, however you do not always need one. | |||
? DOS Database Client/DOS Windows Database Client: | |||
?You CANNOT run any DOS Database client or DOS Windows Database | |||
client applications in OS/2's DOS Compatibility mode (i.e., from the DOS | |||
box) | |||
? There are NO online helps for Database Manager. You will need to refer to the | |||
Extended Services for OS/2 Messages and Error Recovery Guide, Database Only | |||
for the explanation of error messages. | |||
? Corrections to Guide to Database Manager Clients | |||
1. Pages 4-3, and 4-4: | |||
?Steps 1 and 2 should be replaced by: | |||
Type the following at the command prompt and press Enter: INSTDB | |||
2. Page 3-7 | |||
?In step 8 the Workstaion Name Panel is displayed instead of the | |||
Installation and Configuration Panel. | |||
?Step 9 should be replaced with: | |||
Type in the name of your workstation and select OK or press enter. | |||
The "Copying files - Please wait" popup is displayed. While the system | |||
copies files, the percentage of the diskette that is copied and the amount | |||
of time elasped is continually updated on this panel. The Options panel | |||
is displayed next. | |||
?Step 10 should be removed. | |||
?In steps 13 and 14 the cursor will not automatically move; it must be | |||
tabbed or selected via a mouse. | |||
?Step 14 should be replaced with: | |||
Select Add to accept IBM OS/2 NETBIOS. Your selection (IBM OS/2 | |||
NETBIOS) is displayed in the current configuration field (beneath the | |||
Network Adapters field). When all options are complete move to OK | |||
and press enter. The Options panel is now displayed. | |||
?Step 15 should be replaced with: | |||
When all configuring is complete, press Configuration Complete. A | |||
warning panel asking you to check the terms and conditions | |||
information to verify that you can copy the network driver information | |||
is displayed. | |||
3. Appendix B, page B-3, "DBM Catalog NETBIOS Node" | |||
?The syntax diagram has an error. You need to precede the adapter | |||
number (0 or 1) with the keyword 'ADAPTER' or you will get an | |||
error. | |||
Database Manager Clients Restrictions/Limitations 3 | |||
IBM CONFIDENTIAL Database Manager Clients Driver S1A246 | |||
Database Manager Clients Restrictions/Limitations 4 | |||
IBM CONFIDENTIAL Database Manager Clients Driver S1A246 | |||
3.0 Installation Instructions | |||
The installation instructions for this feature are included in the Guide to Database | |||
Manager Clients publication which has been included with this driver shipment. | |||
Once you have read and understood ALL restrictions and limitations that apply to | |||
this driver, please refer to the above-mentioned publication for all details of | |||
installing and configuring your client workstations. | |||
Important Installation Note | |||
If you are installing an OS/2 NETBIOS Client, you MUST apply some patches | |||
after you complete the installation. After you have completed the installation | |||
steps in the Guide to Database Manager Clients, return to this document and | |||
follow the instructions in 4.0, 嗀pplying Patches to the OS/2 NETBIOS Client? | |||
on page 6 | |||
Installation Instructions 5 | |||
IBM CONFIDENTIAL Database Manager Clients Driver S1A246 | |||
4.0 Applying Patches to the OS/2 NETBIOS Client | |||
After your OS/2 NETBIOS Client is installed, you must apply the necessary | |||
patches. | |||
Note | |||
This applies ONLY to OS/2 NETBIOS Clients; it DOES NOT apply to DOS | |||
Database Client or DOS Windows Database Client. | |||
4.1 Instructions for Applying Database Manager Client Patches | |||
*** NOTEs: *** | |||
1. In order for the patches to be applied correctly, you MUST take the steps | |||
below after Database Manager Client installation is complete. | |||
2. If you need to re-install the Database Manager Client, the patch process | |||
MUST be repeated after the re-installation. | |||
1. Insert the patch diskette #1 in drive A: | |||
2. From the OS/2 command prompt, enter the following command. | |||
Note: The replace command will replace files based upon the features you have | |||
installed on your PC. If you have installed features which do not require any | |||
patches, then the replace command may not replace any files. | |||
? REPLACE A:\CMPATCH\*.* z:\IBMCOM /S | |||
where z is the logical drive on which OS/2 is installed. | |||
3. Insert patch diskette #2 in driver A:, and type the following: | |||
a:dbclient x: | |||
(where x is the drive on which the Database Manager client is installed) and | |||
press Enter. | |||
4. Remove the patch diskette. | |||
# 5. Use the Desktop Manager Shutdown feature to stop and reboot your system, if | |||
# you are using OS/2 SE V1.3 with Manufacturing Refresh 1.30.1. If you are | |||
# using OS/2 SE V2.0 Level 6.167, you should move the mouse to a blank area of | |||
# the workplace desktop (i.e., not on an object or folder) and press mouse button | |||
# #2. From the pull-down that appears, select "Shutdown" and follow the | |||
# directions. | |||
Applying Patches to the OS/2 NETBIOS Client 6 | |||
� | |||
</pre> | |||
</div></div> | |||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
INST6167.DOC | |||
<div class="mw-collapsible-content"> | |||
<pre width="87"> | |||
OS/2 32-Bit Operating System | |||
Installation Guide | |||
PRE-RELEASE COPY | |||
October 10, 1991 | |||
First Edition October 1991 < * | |||
The following paragraph does not apply to the United Kingdom or any | |||
country where such provisions are inconsistent with local law: | |||
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS | |||
PUBLICATION 嗀S IS?WITHOUT WARRANTY OF ANY KIND, EITHER | |||
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED | |||
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR | |||
PURPOSE. Some states do not allow disclaimer of express or implied | |||
warranties in certain transactions, therefore, this statement may not apply | |||
to you. | |||
This publication could include technical inaccuracies or typographical | |||
errors. Changes are periodically made to the information herein; these | |||
changes will be incorporated in new editions of the publication. IBM may | |||
make improvements and/or changes in the product(s) and/or the | |||
program(s) described in this publication at any time. | |||
It is possible that this publication may contain reference to, or information | |||
about, IBM products (machines and programs), programming, or services | |||
that are not announced in your country. Such references or information | |||
must not be construed to mean that IBM intends to announce such IBM | |||
products, programming, or services in your country. | |||
Requests for technical information about IBM products should be made to | |||
your IBM Authorized Dealer or your IBM Marketing Representative. | |||
+ Copyright International Business Machines Corporation 1991. All rights | |||
reserved. | |||
Note to U.S. Government Users ?Documentation related to restricted | |||
rights ?Use, duplication or disclosure is subject to restrictions set forth | |||
in GSA ADP Schedule Contract with IBM Corp. | |||
Contents | |||
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii | |||
About This Book ..... . . . . . . . . . . . . . . . . . . . . . . . ix | |||
How This Book is Organized. ....... . . . . . . . . . . . . . ix | |||
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . x | |||
Chapter 1. Choosing an Installation.Procedure. ........ 1 | |||
Basic Installation. ..... . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
Advanced Installation Choices. . . . ....... . . . . . . . . . 4 | |||
Running OS/2 2.0 and DOS on the Same System. . . . . . . . 4 | |||
Multiple Operating System Installation ........... . . . 6 | |||
Alternative Ways to Install. . . . ....... . . . . . . . . . . 6 | |||
Choosing an Advanced Installation.Procedure. ...... . 6 | |||
Special Note about Reconfigurable Diskette.Drives . . . . . 7 | |||
Chapter 2. Installing OS/2 2.0 as the Only Operating System . . 9 | |||
Setting Up Your Hard Disk. . . . ....... . . . . . . . . . . . . 9 | |||
Selecting the Operating System.Features . . . . . ...... . 12 | |||
Configuring the System ....... . . . . . . . . . . . . . . . . . 14 | |||
Viewing the Tutorial ....... . . . . . . . . . . . . . . . . . . . 16 | |||
Chapter 3. Adding OS/2 2.0 to a DOS System. . . . . . . . . . 17 | |||
Dual Boot Requirements ....... . . . . . . . . . . . . . . . . 18 | |||
Setting Up Your System for Dual Boot. . . . . ......... . 19 | |||
Making Sure Your DOS Directory Structure Is.Correct . . . 19 | |||
Creating or Modifying the AUTOEXEC.BAT and CONFIG.SYS | |||
Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 | |||
Installing the OS/2 Version 2.0 Operating.System .... . . . 22 | |||
Viewing the OS/2 Tutorial. . . . ....... . . . . . . . . . . . 24 | |||
Starting the Dual Boot Feature ......... . . . . . . . . . . 24 | |||
Chapter 4. Installing Multiple Operating Systems .... . . . . 25 | |||
How This Chapter is Organized ......... . . . . . . . . . . 25 | |||
An Overview of the Boot Manager ......... . . . . . . . . 26 | |||
Hard Disk Management . . . . ....... . . . . . . . . . . . . . 27 | |||
Planning for a Boot Manager.Setup. . ..... . . ... . . 31 | |||
Sample FDISK Screen. . . ..... . . . . . . . . . . . . . . . 33 | |||
Getting Ready for Installation ......... . . . . . . . . . 35 | |||
+ Copyright IBM Corp. 1991 iii | |||
Starting the OS/2 2.0 Installation ......... . . . . . . . . . 36 | |||
Installing OS/2 2.0 on a New System. . . . . ......... 36 | |||
Installing OS/2 2.0 on an Existing System. . . . . . . . . . . 37 | |||
Setting Up Your Hard.Disk . . . ..... . . . . . . . . . . . . . 39 | |||
Deleting Existing Partitions ......... . . . . . . . . . . . 39 | |||
Creating the Boot Manager Partition. . . . . ......... 41 | |||
Creating Partitions for Operating Systems Other than OS/2 | |||
2.0 and for Logical Drives. . . . ....... . . . . . . . . . 42 | |||
Options Menu Choices ....... . . . . . . . . . . . . . . 44 | |||
Specifying Options . . . . . . . . . . . . . . . . . . . . . . . 46 | |||
Creating the Partition or Logical Drive for OS/2.2.0 . . . . 47 | |||
Specifying Options for the OS/2 2.0 Partition or Logical Drive 48 | |||
Saving Your Changes. . . ..... . . . . . . . . . . . . . . . 52 | |||
Continuing with OS/2 2.0 Installation. . . . . ......... . . 53 | |||
Selecting the Operating System.Features . . . . . .. . . . 53 | |||
Formatting Logical Drives. . . . ....... . . . . . . . . . . 53 | |||
Viewing the Tutorial. . . ..... . . . . . . . . . . . . . . . . . . 53 | |||
Installing Other Operating Systems ......... . . . . . . . 54 | |||
Chapter 5. Alternative Ways to.Install. ....... . . . . . . 59 | |||
Understanding the Response File Installation .......... 59 | |||
Modifying the Response File. . . . ....... . . . . . . . . . . 60 | |||
Installing OS/2 2.0 from a Source Other than Drive A . . . . . . 63 | |||
Redirecting the Installation ......... . . . . . . . . . . . 63 | |||
Setting Up an Alternative Installation.Source ..... . . . 64 | |||
Installing from a CD-ROM.Device . . . . ....... . . . . 64 | |||
Appendix A. Customizing the Operating.System ... . . . . 67 | |||
Features that You Can Change.or Add . ....... . . . . . . 67 | |||
Changing Your Setup or Adding Features. . . . . ........ 69 | |||
Appendix B. Diagnosing System Problems. . . . . ...... . 71 | |||
Recovering the CONFIG.SYS File. . . . ....... . . . . . . . 71 | |||
Recovering User and System INI.Files. . ..... . . ... . . 72 | |||
Recovering from Errors on the Hard Disk. . . . . ........ 74 | |||
Responding to Installation.Errors . . . . ....... . . . . . . 75 | |||
Making the Boot Manager Active. . . . ....... . . . . . . . 76 | |||
Appendix C. Examples of Installing OS/2 2.0 and Partitioning | |||
Your Hard Disk ..... . . . . . . . . . . . . . . . . . . . . . . . 77 | |||
ivOS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Example 1: Creating a Primary Partition and a Logical Drive for | |||
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 | |||
Example 2: Installing the Boot Manager, OS/2 2.0, and One | |||
Additional Operating.System . . . . ....... . . . . . . . . 80 | |||
Example 3: Installing the Boot Manager, OS/2 2.0, and Two | |||
Additional Operating Systems ......... . . . . . . . . . . 82 | |||
Example 4: Installing Boot Manager without Repartitioning the | |||
Entire Hard Disk. . . ..... . . . . . . . . . . . . . . . . . . . 85 | |||
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 | |||
Contents v | |||
viOS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Notices | |||
References in this publication to IBM products, programs, or | |||
services do not imply that IBM intends to make these available in | |||
all countries in which IBM operates. Any reference to an IBM | |||
product, program or service is not intended to state or imply that | |||
only IBM's product, program, or service may be used. Any | |||
functionally equivalent product, program, or service that does not | |||
infringe any of IBM's intellectual property rights or other legally | |||
protectible rights may be used instead of the IBM product, | |||
program, or service. Evaluation and verification of operation in | |||
conjunction with other products, programs, or services, except | |||
those expressly designated by IBM, are the user's responsibility. | |||
IBM may have patents or pending patent applications covering | |||
subject matter in this document. The furnishing of this document | |||
does not give you any license to these patents. You can send | |||
license inquiries, in writing, to the IBM Director of Commercial | |||
Relations, IBM Corporation, Purchase, NY 10577. | |||
The following terms, denoted by a single asterisk (*), used in this | |||
publication, are trademarks or service marks of the IBM | |||
Corporation in the United States or other countries: | |||
AIX IBM Operating System/2 | |||
OS/2 Personal System/2 Presentation Manager | |||
PS/2 SAA Systems Application | |||
Architecture | |||
The following terms, denoted by a double asterisk (**), used in this | |||
publication, are trademarks of other companies as follows: | |||
Adobe Adobe Systems Incorporated | |||
Adobe Type Adobe Systems Incorporated | |||
Manager | |||
Helvetica Linotype Company | |||
Microsoft Microsoft Corporation | |||
PostScript Adobe Systems Incorporated | |||
Windows Microsoft Corporation | |||
+ Copyright IBM Corp. 1991 vii | |||
viii OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
About This Book | |||
This book provides detailed instructions on installing the IBM * | |||
*OS/2 operating system. | |||
How This Book is Organized | |||
This book has the following chapters and appendixes: | |||
Chapter 1 provides you with an overview of the various | |||
installation options. | |||
Chapter 2 describes a basic installation procedure that installs | |||
the OS/2 operating system as the only operating system on | |||
your hard disk. | |||
Chapter 3 describes the procedure for adding OS/2 2.0 to an | |||
existing DOS system, so that you can switch between the | |||
operating systems. | |||
Chapter 4 describes how to partition your hard disk during | |||
installation, so that you can install multiple operating systems. | |||
Chapter 5 describes alternatives to the typical installation | |||
procedure, such as using the same installation choices for | |||
multiple computers. | |||
Appendix A briefly describes ways to customize your system | |||
after installation. | |||
Appendix B describes how to recover from errors. | |||
Appendix C provides four examples of partitioning the hard | |||
disk during installation. | |||
* Trademark of the IBM Corporation. | |||
+ Copyright IBM Corp. 1991 ix | |||
Related Information | |||
Overview This book contains general information about the OS/2 | |||
operating system. It also shows you which | |||
combinations of keys to use to perform specific actions. | |||
Quick Reference | |||
This card provides you with a very brief set of | |||
instructions on how to start the installation of the OS/2 | |||
operating system. It is intended primarily for those who | |||
want to accept most or all of the preselected choices | |||
during installation. Note that the card provides only | |||
limited instructions to get you started. If you want more | |||
detailed information about installing the operating | |||
system, use this book. | |||
The following publication will be available and can be ordered | |||
separately: | |||
OS/2 Version 2.0 Remote Installation and Maintenance (GG24-3780). | |||
This book provides detailed information about setting | |||
up remote installations (such as installations across a | |||
local area network). | |||
xOS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Chapter 1. Choosing an Installation Procedure | |||
This book describes how*to install the IBM * OS/2 Version 2.0 | |||
operating system. It describes the basic installation procedure, | |||
which installs OS/2 2.0 as the only operating system on your hard | |||
disk. It also describes advanced installation procedures, for those | |||
who have unique system requirements (such as the need to install | |||
multiple operating systems). | |||
If you follow the basic installation procedure, you will be able to | |||
** | |||
run programs written for DOS and Microsoft Windows as well as | |||
OS/2 programs--all under OS/2 2.0. | |||
* Trademark of the IBM Corporation | |||
** Trademark of the Microsoft Corporation. | |||
+ Copyright IBM Corp. 1991 1 | |||
+----------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+----------------------------+ | |||
2OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Basic Installation | |||
This book describes the basic installation procedure as well as | |||
more advanced procedures. Most people will find that the basic | |||
installation procedure works best for them because their programs | |||
written to run under DOS, Microsoft Windows, and the OS/2 | |||
operating system will run under OS/2 2.0. | |||
The installation procedure begins when you insert the Installation | |||
Diskette and restart the system. From that point on, most of the | |||
information you need to help you install the system can be found | |||
on the screens. | |||
During the installation, you will be asked to make choices about | |||
how you want your system set up. Each time you are asked to | |||
make a choice, a default (preselected) choice will be provided. If | |||
you want to accept these default choices, you can go now to the | |||
Quick Reference card, which will give you instructions on how to | |||
start the installation. | |||
However, if you want more information about the choices you can | |||
make during installation, or if you want assistance in completing | |||
the installation, you can refer to Chapter 2, 蘒nstalling OS/2 2.0 as | |||
the Only Operating System?on page 9. | |||
To complete the basic installation procedure and set up OS/2 2.0 | |||
as the only operating system, choose one of these: | |||
? | |||
�葺葺葺莨葺葺葺葙 | |||
�葺葺馆葺葙 �葺葺馆葺葙 | |||
�Quick � � Chapter � | |||
�Reference� � 2 � | |||
�card � � � | |||
� � � � | |||
�葺葺葺葺? �葺葺葺葺? | |||
If, instead, you want to install the OS/2 Version 2.0 operating | |||
system according to one of the more advanced procedures (for | |||
example, if you want to keep a version of DOS on the same system | |||
with OS/2 2.0), continue to 嗀dvanced Installation Choices?on | |||
page 4. | |||
Chapter 1. Choosing an Installation Procedure 3 | |||
Advanced Installation Choices | |||
Although installing OS/2 2.0 by itself is the procedure that will be | |||
best for most people, you might have specific requirements to | |||
install more than one operating system or to keep a version of | |||
DOS on your system when you install OS/2 2.0. | |||
Running OS/2 2.0 and DOS on the Same System | |||
The OS/2 Version 2.0 operating system is designed to run | |||
programs written for DOS and Microsoft Windows. These | |||
programs run in a version of DOS that is optimized for the OS/2 | |||
environment. However, some programs will run only under a | |||
specific version of DOS. If you have such a program, you might | |||
want to consider running a specific version of DOS with OS/2 2.0. | |||
There are three ways that you can set up your system to | |||
accomplish this. | |||
? You can load a version of DOS into a DOS session of OS/2 2.0. | |||
The version of DOS can exist on another partition on the hard | |||
disk or it can be on diskette. | |||
? | |||
You can install OS/2 2.0 on a system that already contains | |||
DOS and then use the BOOT command to switch between the | |||
operating systems. (This is called the Dual Boot feature.) | |||
? You can install multiple operating systems on the hard disk of | |||
your computer. Then, each time you start your computer, you | |||
can select which operating system you want to be active. (You | |||
use the Boot Manager feature to manage the startup of the | |||
operating system.) | |||
The following is a brief summary to help you decide which of these | |||
choices is right for you. | |||
4OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Run a version of Add OS/2 2.0 to a Install DOS and | |||
DOS from within DOS partition (Dual OS/2 in their own | |||
OS/2 2.0. Boot). partitions (Boot | |||
Manager). | |||
? You can either ? You do not have ? You must | |||
partition your to partition your partition the | |||
hard disk (and hard disk. hard disk during | |||
install DOS in its installation. | |||
own partition), | |||
or you can start | |||
DOS from a | |||
diskette. | |||
? You start DOS in ? You use the ? When you start | |||
a DOS session BOOT command the computer, | |||
of OS/2 to switch you select which | |||
whenever you between DOS operating | |||
need it. and OS/2 2.0. system to use. | |||
? DOS can run in ? OS/2 2.0 and ? OS/2 2.0 and | |||
a window while DOS do not DOS do not | |||
OS/2 2.0 operate at the operate at the | |||
continues to run. same time. same time. | |||
You do not have | |||
to shut down | |||
OS/2 2.0 and all | |||
OS/2 programs | |||
to run a specific | |||
version of DOS. | |||
? You must modify ? You might have ? You do not have | |||
DOS system to modify DOS to modify any | |||
files after you system files or DOS system | |||
install OS/2 2.0 change the files. | |||
and DOS. directory | |||
structure before | |||
you install OS/2 | |||
2.0. | |||
As you can see, each of the choices has certain advantages. For | |||
example, if you start a version of DOS from within the OS/2 | |||
operating system, you can run the DOS version while continuing to | |||
take advantage of the multitasking features of OS/2 2.0. | |||
Chapter 1. Choosing an Installation Procedure 5 | |||
Multiple Operating System Installation | |||
With the Boot Manager feature of OS/2 2.0, you can have multiple | |||
operating systems installed in separate partitions of your hard | |||
disk. Once the operating systems are installed, you use the Boot | |||
Manager to select which one you want to start. As mentioned in | |||
the previous section, you can install OS/2 2.0 and a version of DOS | |||
in their own partitions, and then use the Boot Manager to select | |||
one at startup time. You can install other operating systems (such | |||
as AIX * ) as well. | |||
Alternative Ways to Install | |||
You can install OS/2 2.0 using a response file, which contains | |||
information the installation program uses to set up a system. | |||
When a response file is used, the installation program does not | |||
prompt for decisions. This type of installation is typically used in | |||
multi-workstation environments, where many computers are being | |||
set up. You can also redirect the installation of OS/2 2.0 to a | |||
source other than the diskette in drive A. | |||
Choosing an Advanced Installation Procedure | |||
If you have chosen to do something other than the basic | |||
installation, select one of these advanced installation procedures: | |||
? | |||
�葺葺葺葺葺葺葺葺葺葺篙葺葺葺葺葺葺葺葺葺葙 | |||
�葺葺馆葺葙 �葺葺馆葺葙 �葺葺馆葺葙 | |||
� Chapter � � Chapter � � Chapter � | |||
� 3 � � 4 � � 5 � | |||
� � � � � � | |||
� � � � � � | |||
�葺葺葺葺? �葺葺葺葺? �葺葺葺葺? | |||
Add OS/2 2.0 to Install OS/2 2.0 Install using a | |||
a DOS system and other response file or | |||
(Dual Boot). operating systems install from a | |||
(Boot Manager). source other than | |||
drive A. | |||
* Trademark of the IBM Corporation. | |||
6OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
The procedure for starting a version of DOS from diskette is | |||
described in the online information, which is available on your | |||
screen after you install the OS/2 Version 2.0 operating system. | |||
Special Note about Reconfigurable Diskette Drives | |||
Some systems that contain multiple diskette drives provide the | |||
capability to read a self-starting diskette (such as the Installation | |||
Diskette) from a drive other than A. | |||
For example, suppose you have two diskette drives: A (for 3.5-inch | |||
diskettes) and B (for 5.25 diskettes). If you load a self-starting | |||
diskette in drive B and restart the system, the diskette in drive B | |||
will be loaded. | |||
If you have a system with multiple diskette drives and you want to | |||
load the installation diskettes from a drive other than A, you will | |||
need to reassign that other drive to make it the primary drive in | |||
the startup sequence. See the documentation that came with your | |||
computer for information on making a drive other than A the | |||
primary drive. | |||
Chapter 1. Choosing an Installation Procedure 7 | |||
8OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Chapter 2. Installing OS/2 2.0 as the Only | |||
Operating System | |||
This chapter describes how to install OS/2 2.0 as the only | |||
operating system on your computer. It also provides information | |||
to help you make choices about which features of the operating | |||
system you want to install. | |||
You can use the procedure in this chapter whether you are | |||
installing on a new system or on a system that already contains | |||
data. For example, if you already have OS/2 Version 1.3 on your | |||
hard disk, you can use the procedure in this chapter to replace it | |||
with OS/2 Version 2.0. | |||
You can also use the procedure in this chapter to replace a DOS | |||
system with OS/2 2.0. However, if you want to keep a version of | |||
DOS on your system, see Chapter 3, 嗀dding OS/2 2.0 to a DOS | |||
System?on page 17. | |||
Note: If an error message is displayed while you are installing the | |||
operating system, see esponding to Installation Errors? | |||
on page 75 for an explanation of the message and the | |||
corrective action. | |||
In the first part of the installation, you will make choices about how | |||
the hard disk on your system should be set up. | |||
Setting Up Your Hard Disk | |||
To begin the installation of the operating system, do the following: | |||
1. Insert the Installation Diskette into drive A. | |||
2. Turn on the computer. | |||
If the computer is already on, press and hold Ctrl+Alt and | |||
press Del to restart the system. The following screen appears: | |||
+ Copyright IBM Corp. 1991 9 | |||
+---------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+---------------------------+ | |||
3. Remove the Installation Diskette, insert Diskette 1, and press | |||
Enter. | |||
You will be prompted at various points during installation to | |||
remove the diskette in drive A and to insert another diskette. | |||
Be sure to leave the diskette in drive A until the instructions | |||
direct you to replace it. You will replace diskettes several | |||
times before the operating system finishes copying information | |||
from the diskettes to the hard disk of your computer. | |||
4. As information is displayed, either accept it or change it. If | |||
you want to set up a default system that works best for most | |||
people, you can accept the preselected choice on each screen | |||
by pressing Enter. | |||
During this part of the installation, you will be asked whether | |||
you want to accept the default installation partition or to | |||
specify your own partition. A partition is a fixed-sized area on | |||
the hard disk. If you are installing on a disk that contains no | |||
data and you accept the default installation partition, the | |||
installation program installs the operating system in one | |||
partition that takes up the entire hard disk. If you are installing | |||
on a system that already contains partitions, the installation | |||
10OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
program indicates which partition it will use to install OS/2 2.0. | |||
You can either accept this default choice or select another | |||
partition. | |||
Accepting the default partition works well for most people. If | |||
you want to install the operating system in the default partition, | |||
simply accept the preselected choices. | |||
If you are not sure of a choice, press F1 for help. | |||
A note about partitioning | |||
If you want to create more than one partition on your hard disk, | |||
or if you receive a message stating that an existing partition is | |||
not large enough to hold OS/2 2.0, you will need to specify | |||
information about partitions. When you select other than the | |||
default partition, you see the FDISK utility screen. On this | |||
screen, you use the Options menu to create the partitions. | |||
(The Options menu is displayed when you highlight an entry on | |||
the FDISK screen and press Enter.) | |||
An example of creating more than one partition on the hard | |||
disk is included in Appendix C, 﨓xamples of Installing OS/2 | |||
2.0 and Partitioning Your Hard Disk?on page 77. You might | |||
want to follow that example now if you are setting up more | |||
than one partition on the hard disk. | |||
At a certain point in the installation process, you will be notified | |||
that the hard disk setup is complete. You will then be asked to | |||
restart your system by removing the diskette and pressing Enter. | |||
Chapter 2. Installing OS/2 2.0 as the Only Operating System 11 | |||
Selecting the Operating System Features | |||
Once the hard disk of your computer is set up, you see the OS/2 | |||
Setup and Installation screen. In this part of installation, you make | |||
choices about which features of the operating system you want to | |||
install. | |||
+---------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+---------------+ | |||
The default choice on this screen is Learn how to use a mouse. If | |||
your system has a mouse attached, but you are unfamiliar with | |||
using the mouse, press Enter to select this choice. The Learn how | |||
to use a mouse program teaches you how to use the mouse to | |||
make selections from the screen. | |||
The Install preselected features choice copies the most commonly | |||
used features of the OS/2 operating system to your hard disk. It | |||
does not copy all the features of OS/2 2.0 to your hard disk. (For | |||
example, Install preselected features does not copy such features | |||
as the Command Reference or REXX Information online documents | |||
or the games that are provided with OS/2 2.0.) This choice is | |||
useful if you want to save hard disk space. | |||
The Install all features choice copies the entire OS/2 operating | |||
system to your hard disk. | |||
The Select features and install choice gives you the opportunity to | |||
indicate which features of the operating system you want to install. | |||
This choice is similar to Install preselected features because, by | |||
installing only certain features, you can save hard disk space. | |||
With this choice, however, you decide which features you want to | |||
12OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
install. Also, if you partitioned your hard disk during the first part | |||
of installation, you can format any logical drives that you | |||
previously set up. | |||
To select a choice, do one of the following: | |||
? Use the Down Arrow ( ? ) key to highlight the choice, and then | |||
press Enter. | |||
? Move the mouse pointer until it is on the choice, and quickly | |||
press mouse button one twice. | |||
You next see the System Configuration screen, which lists your | |||
country configuration and device support (for example, mouse, | |||
keyboard, and display). You can change any of the items by | |||
selecting the item and then selecting the OK push button. | |||
If you chose Select features and install, you see a screen on which | |||
you indicate which features you do not want to install. +-----------------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+-----------------------------------+ | |||
If there is a feature that you will not need, you can choose not to | |||
install it by removing the | next to the feature. To remove the |, | |||
do one of the following: | |||
? Move the mouse pointer to the feature and click once with the | |||
mouse. | |||
? Move the cursor to the feature and press the Spacebar. | |||
Chapter 2. Installing OS/2 2.0 as the Only Operating System 13 | |||
If a More push button is displayed next to a feature, select the | |||
push button to view more choices. | |||
For example, if you decide you want to install only some of the | |||
documentation, you select the More push button to the right of | |||
Documentation to display a list of the documentation. Then, you | |||
remove the | that is next to any documentation you do not want to | |||
install. | |||
Notice the number that is shown to the right of each feature. The | |||
number signifies the amount of hard-disk space required to install | |||
that feature. | |||
For a description of the features, press F1, or see 﨔eatures that | |||
You Can Change or Add?on page 67 for a description of all the | |||
features. | |||
The OS/2 Setup and Installation screen also contains a choice that | |||
lets you format any logical drives you might have set up earlier in | |||
the installation. If you partitioned your hard disk and set up logical | |||
drives for data, you can format them now. To do so, select the | |||
Options menu bar choice, and then select Format. Indicate which | |||
file system (High Performance File System or File Allocation Table) | |||
you want to use to format the logical drive. | |||
Configuring the System | |||
When most of the system files have been transferred, you will see | |||
the Advanced Options screen. Some of the choices on this screen | |||
are available only if you are installing on a hard disk that | |||
contained an existing operating system. For example, if you had a | |||
previous version of the OS/2 operating system on the hard disk, | |||
the Migrate CONFIG.SYS/AUTOEXEC.BAT choice is available. You | |||
use this choice to copy customization information from your | |||
existing operating system to OS/2 2.0. | |||
14OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Special note about migrating the CONFIG.SYS file | |||
If you select Automatically update CONFIG.SYS amd | |||
AUTOEXEC.BAT, you will notice that some device driver | |||
statements from the existing CONFIG.SYS file are copied to the | |||
new file but are preceded with a comment statement. These | |||
statements are commented out because some device drivers | |||
that were designed to operate with previous versions of DOS or | |||
the OS/2 operating system might not operate with OS/2 2.0. | |||
Such device drivers could cause problems with OS/2 2.0. | |||
You can edit the CONFIG.SYS file after installation and remove | |||
the comment statements from the lines that you want to be | |||
active. Save a copy of the CONFIG.SYS file before you modify | |||
it. In the event that a device driver causes problems, you can | |||
use the procedures described later in this book to recover the | |||
file. | |||
If you have existing DOS or Microsoft Windows programs on your | |||
hard disk, you will be asked whether you want to move these | |||
programs into your OS/2 system. | |||
On this screen, you will also indicate which printer should be used | |||
as your default printer. | |||
For specific information about these choices and for help using the | |||
choices, press F1. | |||
Chapter 2. Installing OS/2 2.0 as the Only Operating System 15 | |||
Viewing the Tutorial | |||
After the operating system is installed and you have restarted the | |||
system, the OS/2 Tutorial is displayed: +--------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+--------------------------+ | |||
The tutorial shows you how to use the features of the OS/2 | |||
operating system. View the tutorial now. When you have finished, | |||
explore the features of the operating system, and enjoy! | |||
16OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Chapter 3. Adding OS/2 2.0 to a DOS System | |||
This chapter describes how to install the OS/2 Version 2.0 | |||
operating system on a hard disk that already has DOS installed so | |||
that you can use both operating systems. The OS/2 Version 2.0 | |||
operating system is installed along with DOS in the primary | |||
partition of your hard disk. | |||
By following the procedures in this chapter, you set up your | |||
system to use Dual Boot. With Dual Boot, you can switch back and | |||
forth between the DOS and OS/2 operating systems. For example, | |||
if you have a DOS program that runs only under the DOS operating | |||
system, you could switch to DOS and run the program. | |||
Note: It is assumed that DOS is already installed on your system | |||
and that you are familiar with using DOS. | |||
You will add OS/2 2.0 to the same partition in which DOS resides. | |||
Keep in mind that the DOS and OS/2 operating systems cannot | |||
operate at the same time. You switch between the operating | |||
systems using the BOOT command. | |||
Another way to use DOS: | |||
With Version 2.0 of the OS/2 operating system, you can run a | |||
specific version of DOS (for example, DOS Version 5.0) from a | |||
DOS session within OS/2 2.0. You can run DOS Version 5.0, for | |||
example, while your other programs continue to run under | |||
OS/2 2.0. So, if you want to be able to run a version of DOS | |||
while OS/2 2.0 is running, you can set up DOS in its own | |||
partition on the hard disk (which is explained in Chapter 4, | |||
蘒nstalling Multiple Operating Systems?on page 25.) Or, you | |||
can run a version of DOS from a DOS diskette. For information | |||
on running a version of DOS from a DOS diskette, see the | |||
online information, which is displayed on your screen after you | |||
install the operating system. | |||
+ Copyright IBM Corp. 1991 17 | |||
Dual Boot Requirements | |||
Before you begin the procedures in this chapter, you should be | |||
aware of the following: | |||
? | |||
DOS Version 3.2 or higher must be installed on your hard disk. | |||
OS/2 2.0 will work with DOS Version 3.2; however, to take full | |||
advantage of OS/2 capabilities, use DOS Version 3.3 or higher. | |||
? The DOS operating system must exist on drive C before the | |||
OS/2 operating system is installed. The Dual Boot feature is | |||
operable only after OS/2 2.0 is installed. | |||
? You can start either DOS or the OS/2 operating system from | |||
the same partition on your hard disk. Note, however, that you | |||
cannot use this feature with the High Performance File System. | |||
The DOS operating system will not recognize or be able to use | |||
anything within a High Performance File System partition. | |||
? If you already have a previous version of the OS/2 operating | |||
system with the Dual Boot feature or DOS installed on the | |||
target hard drive, the existing operating systems must be | |||
startable for the Dual Boot feature to work correctly. (Use the | |||
FDISK utility program of DOS if you want to check whether the | |||
version of DOS is startable.) Be sure that the DOS operating | |||
system installed is the version you wish to use with the Dual | |||
Boot feature. | |||
? Your primary partition must be at least 24MB (MB equals 1 048 | |||
576 bytes) for the DOS and OS/2 operating systems to exist on | |||
drive C. You should consider the size of both operating | |||
systems and also leave room for the growth of a swap file. (A | |||
swap file contains segments of a program or data temporarily | |||
moved out of main storage.) A typical swap file is between 4 | |||
and 8MB. If your existing primary partition is not large | |||
enough, use the DOS FDISK command to change your hard | |||
disk setup. Follow the instructions in your DOS documentation. | |||
QUESTION | |||
Do you have OS/2 Version 1.2 or 1.3 with the Dual Boot feature | |||
currently installed on your hard disk? If so, go to 蘒nstalling | |||
the OS/2 Version 2.0 Operating System?on page 22. | |||
18OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Setting Up Your System for Dual Boot | |||
Before you install OS/2 Version 2.0, you will check to see that your | |||
DOS system is set up correctly. | |||
? All DOS commands and utility programs must be located in a | |||
subdirectory, such as C:\DOS, and not in the root directory. | |||
? You must create or modify the DOS operating system | |||
CONFIG.SYS and AUTOEXEC.BAT files on your system and put | |||
them in the root directory of your hard disk before the OS/2 | |||
operating system is installed. This includes setting the SHELL, | |||
COMSPEC, PATH, and APPEND statements to find the DOS | |||
command files in the appropriate subdirectory. | |||
In the next section of this chapter, you will check to see that your | |||
setup meets these conditions. | |||
Making Sure Your DOS Directory Structure Is Correct | |||
1. Start your computer using the DOS operating system that is on | |||
your hard disk, and go to the DOS command prompt. | |||
2. For the Dual Boot feature to work correctly, your CONFIG.SYS | |||
and AUTOEXEC.BAT files must remain in your root directory. | |||
All other DOS system files, including the COMMAND.COM file, | |||
must exist in a subdirectory. | |||
? If your DOS system files and the COMMAND.COM file | |||
already exist in a subdirectory, go directly to 﨏reating or | |||
Modifying the AUTOEXEC.BAT and CONFIG.SYS Files?on | |||
page 21. | |||
? If your DOS system files and COMMAND.COM do not | |||
already exist in a subdirectory, continue to step 3. | |||
3. Type the following command to create a DOS subdirectory on | |||
your C drive: | |||
MD C:\DOS | |||
and press Enter. | |||
Chapter 3. Adding OS/2 2.0 to a DOS System 19 | |||
4. To make sure your root directory and DOS subdirectory are set | |||
up properly, follow these steps: | |||
a. Copy all the files from the root directory of the hard disk to | |||
the DOS subdirectory by typing: | |||
COPY C:\*.* C:\DOS | |||
Then press Enter. | |||
Note: Although this step copies your CONFIG.SYS and | |||
AUTOEXEC.BAT files to the DOS subdirectory, step | |||
4c returns the files to where they properly belong. | |||
b. Delete all of your files from the root directory of the hard | |||
disk. | |||
Warning: Be sure to type the command correctly. When | |||
you enter the command, all files will be deleted, and you | |||
will not be able to recover the data. You will be asked if | |||
you are sure you want to use this command. | |||
Type: | |||
DEL C:\*.* | |||
Then press Enter. | |||
c. Place your existing AUTOEXEC.BAT file in the root | |||
directory by typing: | |||
COPY C:\DOS\AUTOEXEC.BAT C:\ | |||
Then press Enter. | |||
Place your existing CONFIG.SYS file back in the root | |||
directory by typing: | |||
COPY C:\DOS\CONFIG.SYS C:\ | |||
Then press Enter. | |||
d. Continue with 﨏reating or Modifying the AUTOEXEC.BAT | |||
and CONFIG.SYS Files?on page 21. | |||
20OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Creating or Modifying the AUTOEXEC.BAT and | |||
CONFIG.SYS Files | |||
Before installing the OS/2 operating system, you must create or | |||
modify the DOS CONFIG.SYS and AUTOEXEC.BAT files on your | |||
hard disk. This includes setting the SHELL, COMSPEC, PATH, and | |||
APPEND statements to find the DOS command files in the | |||
appropriate subdirectory. | |||
To create or modify the DOS AUTOEXEC.BAT and CONFIG.SYS | |||
files, do the following: | |||
1. Using any editor (for example, EDLIN), add the following | |||
statements, if they do not already exist, to the AUTOEXEC.BAT | |||
file: | |||
SET COMSPEC=C:\DOS\COMMAND.COM | |||
PATH C:\DOS | |||
APPEND=C:\DOS | |||
COPY C:\DOS\COMMAND.COM C:\ >NUL | |||
To the CONFIG.SYS file, add: | |||
SHELL=C:\DOS\COMMAND.COM /P | |||
Note: These statements include the minimum required | |||
parameters. You can specify additional parameters if | |||
you wish, but be sure that the DOS directory is specified | |||
as indicated. | |||
During OS/2 installation, OS/2 CONFIG.SYS and | |||
AUTOEXEC.BAT files are created. The OS/2 operating system | |||
places any existing DOS CONFIG.SYS and AUTOEXEC.BAT | |||
files in the C:\OS2\SYSTEM subdirectory with a .DOS | |||
extension. This is to make sure that the OS/2 operating | |||
system uses the correct AUTOEXEC.BAT and CONFIG.SYS files | |||
during system restart. | |||
Note: If you are using DOS Version 4.0 and you want to use | |||
the DOS shell, you must change the directory specified | |||
in DOSSHELL.BAT from CD to CD\DOS. If this change | |||
is not made, you will receive the message, Mouse file | |||
. missing or unreadable | |||
2. Remove any diskette from drive A. | |||
3. Press and hold Ctrl+Alt; then press Del to restart the system. | |||
Chapter 3. Adding OS/2 2.0 to a DOS System 21 | |||
If the system does not operate, review the previous steps to | |||
make sure you have completed all of them. Remember, you | |||
must have a working copy of DOS installed and it must not be | |||
in the root directory. | |||
Continue with 蘒nstalling the OS/2 Version 2.0 Operating System.? | |||
Remember, do not select the FORMAT option while installing the | |||
OS/2 operating system. After the operating system is installed, | |||
you can start the Dual Boot feature. (See tarting the Dual Boot | |||
Feature?on page 24.) | |||
Installing the OS/2 Version 2.0 Operating System | |||
If you have DOS or Microsoft Windows programs that you want to | |||
install, install them before you install the OS/2 operating system. | |||
Note: If an error message is displayed while you are installing the | |||
operating system, see esponding to Installation Errors? | |||
on page 75 for an explanation of the message and the | |||
corrective action. | |||
To install the operating system, do the following: | |||
1. Insert the Installation Diskette into drive A. | |||
2. Turn on the computer. | |||
If the computer is already on, press and hold Ctrl+Alt, and | |||
then press Del to restart the system. The following screen | |||
appears: | |||
22OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
+-----------------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+-----------------------------------+ | |||
3. Remove the Installation Diskette, insert Diskette 1, and press | |||
Enter. | |||
You will be prompted at various points during installation to | |||
remove the diskette in drive A and to insert another diskette. | |||
Be sure to leave the diskette in drive A until the instructions | |||
direct you to replace it. You will replace diskettes several | |||
times before the operating system finishes copying information | |||
from the diskettes to the hard disk of your computer. | |||
4. As information is displayed, either accept it or change it. | |||
Remember that you should not format your hard disk during | |||
installation. | |||
If you are not sure of a choice, press F1 for help. (Or, you can | |||
refer to Chapter 2, 蘒nstalling OS/2 2.0 as the Only Operating | |||
System?on page 9, which provides additional information | |||
about installing the operating system.) | |||
Chapter 3. Adding OS/2 2.0 to a DOS System 23 | |||
Viewing the OS/2 Tutorial | |||
When the operating system is installed and you have restarted the | |||
system, the OS/2 Tutorial is displayed. The tutorial shows you | |||
how to use the features of the OS/2 operating system. View the | |||
tutorial now, and enjoy the new world of OS/2 2.0. | |||
Starting the Dual Boot Feature | |||
After you have installed the OS/2 operating system, you use the | |||
BOOT command to switch from one operating system to another: | |||
? If you are running the OS/2 operating system and want to | |||
switch to DOS, display an OS/2 command prompt and type: | |||
BOOT /DOS | |||
Then press Enter. | |||
? | |||
If you are running DOS and want to switch to the OS/2 | |||
operating system, type: | |||
C:\OS2\BOOT /OS2 | |||
Then press Enter. | |||
For additional information about the BOOT command, refer to | |||
the OS/2 Command Reference. | |||
Each time the system is shut down and restarted, it starts in | |||
whichever operating system was last being used. For example, if | |||
you shut down the system while DOS is running, your system will | |||
start in DOS the next time you turn on the system. Remember, | |||
however, that the OS/2 operating system and DOS do not operate | |||
at the same time. | |||
24OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Chapter 4. Installing Multiple Operating Systems | |||
This chapter describes how you can install multiple operating | |||
systems on the hard disk of your computer. To install multiple | |||
operating systems, you will set up multiple partitions on the hard | |||
disk during the installation of the OS/2 operating system. You will | |||
also install the Boot Manager feature. | |||
After the Boot Manager is installed and all the operating systems | |||
are installed in their own partitions, you use the Boot Manager | |||
startup menu to select one of the operating systems. Each time | |||
you start your system, then, you decide which operating system | |||
you want to be active. | |||
How This Chapter is Organized | |||
This chapter is separated into three major sections. It is | |||
recommended that you read the entire chapter. In addition, | |||
examples of installing multiple operating systems are provided in | |||
Appendix C, 﨓xamples of Installing OS/2 2.0 and Partitioning Your | |||
Hard Disk?on page 77. For example, if you want to see a brief, | |||
step-by-step example of installing DOS and OS/2 2.0, see Appendix | |||
C. | |||
Section Page Number | |||
An overview of the Boot Manager 26 | |||
Hard disk management 27 | |||
Instructions for installing OS/2 2.0 and 34 | |||
partitioning the hard disk | |||
+ Copyright IBM Corp. 1991 25 | |||
An Overview of the Boot Manager | |||
If you are going to install multiple operating systems, you can use | |||
the Boot Manager feature to manage the selective startup of those | |||
systems. From the Boot Manager startup menu, you can select | |||
which operating system you want to use each time you start your | |||
system. | |||
The following is an example of a Boot Manager startup menu that | |||
includes three operating systems. +-----------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+-----------------------------+ | |||
You use the FDISK utility program during the installation of OS/2 | |||
2.0 to install the Boot Manager feature. The following is a brief list | |||
of the steps you follow to set up your hard disk for multiple | |||
operating systems. These steps are described in detail later in | |||
this chapter. Examples are provided in Appendix C, 﨓xamples of | |||
Installing OS/2 2.0 and Partitioning Your Hard Disk?on page 77. | |||
? First, you install the Boot Manager in its own partition (1MB in | |||
size). | |||
? You then create partitions for the other operating systems you | |||
are going to install. | |||
? Next, you install the OS/2 Version 2.0 operating system. | |||
? Finally, you install the other operating systems in the partitions | |||
you created for them. | |||
26OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Important: You should understand how a hard disk is partitioned | |||
before you begin your installation. Make sure you read the | |||
following section on hard disk management. | |||
Hard Disk Management | |||
During installation, you have the option of installing the OS/2 | |||
operating system in one partition that takes up the entire hard | |||
disk. If, however, you choose to separate your hard disk into | |||
multiple partitions, you see the FDISK screen. | |||
From the FDISK screen, you specify the number and type of | |||
partitions that you want created. You can create primary | |||
partitions, which are typically used for operating systems. You can | |||
also create logical drives in an area of the hard disk that is outside | |||
the primary partitions. This area is known as the extended | |||
partition. The logical drives within the extended partition are | |||
typically used to hold programs and data. | |||
Your hard disk can be separated into a maximum of four partitions. | |||
You can have four primary partitions or three primary partitions | |||
and the extended partition. If you are going to install multiple | |||
operating systems on your hard disk, you must create one primary | |||
partition to contain the programs that manage the startup of | |||
multiple operating systems. (This partition is referred to as the | |||
Boot Manager partition.) | |||
After the Boot Manager partition is created, you can create up to | |||
three additional primary partitions (to hold three operating | |||
systems), as in the following example: | |||
Chapter 4. Installing Multiple Operating Systems 27 | |||
�葺葺葺葺葺葺葺葺葺葺? | |||
� Boot Manager � | |||
谳葺葺葺葺葺葺葺葺葺莼 | |||
� DOS 5.0 � | |||
谳葺葺葺葺葺葺葺葺葺莼 | |||
� OS/2 1.3 � | |||
� � | |||
谳葺葺葺葺葺葺葺葺葺莼 | |||
� OS/2 2.0 � | |||
� � | |||
� � | |||
�葺葺葺葺葺葺葺葺葺葺� | |||
Figure 1. Hard Disk with Four Primary Partitions | |||
Another way of subdividing your hard disk is to create logical | |||
drives within an extended partition. Logical drives are typically | |||
used to hold programs and data. However, you can also install | |||
OS/2 2.0 in a logical drive, as in the following example: | |||
�葺葺葺葺葺葺葺葺葺葺葺葙 | |||
� Boot Manager � 葺葺葺?Primary Partition | |||
谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� DOS 5.0 � 葺葺葺?Primary Partition | |||
谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� OS/2 1.3 � 葺葺葺?Primary Partition | |||
� � | |||
谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� OS/2 2.0 � 葺?Logical Drive 葺葙 | |||
� � � | |||
谳葺葺葺葺葺葺葺葺葺葺葺? � 葺葸 Extended | |||
� Data � 葺?Logical Drive � Partition | |||
谳葺葺葺葺葺葺葺葺葺葺葺? � | |||
� Data � 葺?Logical Drive � | |||
�葺葺葺葺葺葺葺葺葺葺葺? 葺? | |||
Figure 2. Hard Disk with Primary Partitions and Logical Drives | |||
The extended partition takes the place of one of the primary | |||
partitions on your hard disk. In other words, if you create logical | |||
drives within an extended partition, your hard disk can contain | |||
only three primary partitions. Note that you must have one | |||
primary partition in addition to the Boot Manager partition. | |||
In Figure 2, notice that two logical drives have been set aside for | |||
data. That data can be shared by all the operating systems | |||
(provided the file system formats of the logical drives are | |||
compatible with the operating systems). | |||
28OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
All of the logical drives exist within one partitionhe extended | |||
partition. You don't explicitly create the extended partition. The | |||
extended partition is created the first time you create a logical | |||
(non-primary) drive. | |||
One of the differences between a logical drive and a primary | |||
partition is that each logical drive is assigned a unique drive letter. | |||
However, all primary partitions on a hard disk share the same | |||
drive letter. (On the first hard disk in your system, the primary | |||
partitions share drive C). This means that only one primary | |||
partition on a hard disk can be accessed at one time. (Note that | |||
the Boot Manager partition is different from other primary | |||
partitions because it is never assigned a drive letter.) | |||
�葺葺葺葺葺葺葺葺葺葺葺葙 | |||
� Primary (Boot Manager)� 葺葺葺葺葺?No drive letter. | |||
谳葺葺葺葺葺葺葺葺葺葺葺? 葙 | |||
� Primary (DOS 5.0) � �葺葺葺葺?These partitions share C: | |||
谳葺葺葺葺葺葺葺葺葺葺葺? � (Only one can be active) | |||
� Primary (OS/2 1.3) � � | |||
� � � | |||
谳葺葺葺葺葺葺葺葺葺葺葺? ? | |||
� Logical Drive � 葺葺葺葺葺? D: | |||
� (OS/2 2.0) � | |||
谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� Logical Drive (Data) � 葺葺葺葺葺? E: | |||
谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� Logical Drive (Data) � 葺葺葺葺葺? F: | |||
�葺葺葺葺葺葺葺葺葺葺葺? | |||
Figure 3. Drive Letter Assignment Example | |||
Notice the drive letter assignments in this illustration. The | |||
operating system that is active when you start the system | |||
performs a process known as drive mapping, in which partitions | |||
and logical drives are assigned drive letters. All the primary | |||
partitions are mapped first and all logical drives within extended | |||
partitions are assigned subsequent drive letters (up through Z). | |||
Only one primary partition per hard disk can be active at a time. | |||
So, only one primary partition is actually assigned the letter C at | |||
any one time. The other primary partitions are not mapped. | |||
An operating system maps only those drives with a format type | |||
that it supports. For example, DOS does not support the | |||
Chapter 4. Installing Multiple Operating Systems 29 | |||
installable file system (IFS) format. (The High Performance File | |||
System is an example of an IFS format.) Therefore, any partition | |||
or logical drive that is formatted with IFS is not mapped by DOS | |||
and is not assigned a drive letter. | |||
In the following figure, DOS is active in a primary partition. (The | |||
other primary partitions are not mapped.) Drive D is formatted for | |||
the File Allocation Table (FAT) file system, which DOS recognizes. | |||
However, the next drive is formatted with a file system that DOS | |||
does not recognize. Therefore, DOS ignores this drive. Some | |||
versions of DOS (such as DOS Version 5.0) will recognize the last | |||
partition on the hard disk and assign it the letter E. In other | |||
versions of DOS, no drives beyond the HPFS drive are recognized. | |||
Therefore, no data in those partitions can be used by DOS. | |||
�葺葺葺葺葺葺葺葺葺葺葺葙 | |||
� Primary (Boot Manager)� 葺葺葺葺葺?No drive letter. | |||
谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� Primary (DOS) � 葺葺葺葺葺? C: | |||
谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� Primary (OS/2 2.0) � | |||
谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� Logical (Data) � 葺葺葺葺葺? D: | |||
� FAT format � | |||
谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� Logical (Data) � 葺葺葺葺葺? DOS does not recognize this | |||
� HPFS format � | |||
谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� Logical (Data) � 葺葺葺葺葺? E: | |||
� FAT format � | |||
�葺葺葺葺葺葺葺葺葺葺葺? | |||
Figure 4. Example of Drive Mapping. This example illustrates the | |||
problem that can result when the operating system does not recognize a | |||
file format. You can avoid such a problem by placing the logical drive | |||
formatted for the High Performance File System at the end of the hard | |||
disk. | |||
Because of the problems that can result when drives are | |||
remapped, you should avoid deleting logical drives that exist in the | |||
middle of your hard disk. For example, if you were to delete a | |||
logical drive from the middle of your disk, the subsequent drives | |||
would be remapped. (Drive F would become drive E, and so on.) | |||
Problems would result if any programs refer to the former drive | |||
letter. | |||
30OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
The following figure is an example of how drives are mapped in a | |||
system that has two hard disks. | |||
Hard Disk #1 Hard Disk #2 | |||
�葺葺葺葺葺葺葺葺葺葺葺葙 �? �葺葺葺葺葺葺葺葺葺葺葺葙 | |||
� Boot Manager � 葺葺?No drive � � Primary � | |||
谳葺葺葺葺葺葺葺葺葺葺葺? 葙 letter � 谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� Primary � � � � Primary � | |||
� � �葺葺 C: D: 葺葺� 谳葺葺葺葺葺葺葺葺葺葺葺? | |||
谳葺葺葺葺葺葺葺葺葺葺葺? � � � � | |||
� Primary � � � � Primary � | |||
谳葺葺葺葺葺葺葺葺葺葺葺? ? �? 谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� Logical Drive � 葺葺葸 E: H: | |||
葺葺? � Logical Drive � | |||
� � � � | |||
谳葺葺葺葺葺葺葺葺葺葺葺? 谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� Logical Drive � 葺葺葸 F: I: | |||
葺葺? � Logical Drive � | |||
谳葺葺葺葺葺葺葺葺葺葺葺? 谳葺葺葺葺葺葺葺葺葺葺葺? | |||
� Logical Drive � 葺葺葸 G: J: | |||
葺葺? � Logical Drive � | |||
�葺葺葺葺葺葺葺葺葺葺葺? �葺葺葺葺葺葺葺葺葺葺葺? | |||
Figure 5. Example of Drive Mapping in a System with Two Hard Disks | |||
The important thing to remember when you are setting up your | |||
system is that only one primary partition can be accessible (active) | |||
on each hard disk at any system startup. On the other hand, all | |||
the logical drives within the extended partition are accessible | |||
(provided their file system formats are compatible with the starting | |||
operating system). | |||
Planning for a Boot Manager Setup | |||
When you are planning your Boot Manager setup, be aware of the | |||
following: | |||
? | |||
If you want to preserve existing partitions on your hard disk, | |||
you can install the Boot Manager partition at the end of the | |||
hard disk. Otherwise, create the Boot Manager partition at the | |||
beginning of the hard disk. | |||
? Use primary partitions for DOS systems or previous releases | |||
of the OS/2 operating system. | |||
? To prevent hard disk fragmentation and loss of usable disk | |||
space, create all primary partitions contiguously, at the | |||
beginning or end of the disk free space area. | |||
Chapter 4. Installing Multiple Operating Systems 31 | |||
? Put all installable file systems (such as the High Performance | |||
File System) at the end of the disk configuration. As | |||
mentioned earlier, some operating systems do not recognize | |||
installable file systems. By placing all installable file systems | |||
at the end of the disk, you can prevent the problem that results | |||
when drives are remapped. | |||
? | |||
Be aware of specific operating-system restrictions on the hard | |||
disk. For example, to run properly, DOS 3.3 must be installed | |||
in a primary partition that is within the first 32MB of the hard | |||
disk. | |||
? If you are installing a primary partition for DOS and you intend | |||
to load that version of DOS into a DOS session of OS/2 2.0, you | |||
will need to change the DOS CONFIG.SYS and AUTOEXEC.BAT | |||
files. (You do this after you finish installing the operating | |||
systems.) Refer to the online information, which is displayed | |||
on your screen after the OS/2 operating system is installed. | |||
? You can install both DOS and a version of the OS/2 operating | |||
system in the same primary partition if you want to use the | |||
Dual Boot feature within your Boot Manager setup. | |||
? If you are using the IBM DOS 5.00 Upgrade to update your DOS | |||
3.3 or DOS 4.0 system, you should be aware that some | |||
versions of the upgrade will not recognize the DOS partition | |||
unless it is the only partition on the hard disk. You might have | |||
to do the following: | |||
1. Make sure that the DOS partition is the only primary | |||
partition on your hard disk. | |||
2. Install the DOS 5.00 Upgrade. | |||
3. Add the Boot Manager partition and install OS/2 2.0. | |||
Note that an example of adding the Boot Manager to an | |||
existing system (without repartitioning the entire hard disk) is | |||
outlined in Appendix C, 﨓xamples of Installing OS/2 2.0 and | |||
Partitioning Your Hard Disk?on page 77. | |||
32OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Sample FDISK Screen | |||
The following FDISK screen represents a typical hard disk layout of | |||
a 120MB hard disk with three operating systems installed. +--------------------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+--------------------------------------+ | |||
In the previous screen, note the following: | |||
? The Boot Manager partition is marked Startable. When you | |||
start your system, the Boot Manager will be in control. You | |||
can then choose which operating system you want to run. | |||
? DOS 3.3 and DOS 5.0 are set up in primary partitions. | |||
However, only DOS Version 3.3 is accessible. Notice that the | |||
drive letter (C) is displayed on the line that contains | |||
information about the DOS 3.3 partition. The placement of the | |||
drive letter indicates which of the primary partitions is active. | |||
DOS and previous versions of the OS/2 operating system can | |||
reside only in a primary partition. They cannot reside in a | |||
logical drive within the extended partition. | |||
? OS/2 2.0 resides in a logical drive in the extended partition | |||
(drive D in this example). Remember that OS/2 2.0 can reside | |||
in either a primary partition or in a logical drive within the | |||
extended partition. | |||
? The logical drive labeled E is set aside for common tools or | |||
programs that can be shared by the operating systems. | |||
Chapter 4. Installing Multiple Operating Systems 33 | |||
? 55MB of free space is available. This area can be set aside for | |||
future use. For example, you could later add logical drives at | |||
the end of the free space without disturbing any currently | |||
installed partitions. | |||
34OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Getting Ready for Installation | |||
To partition your hard disk and install multiple operating systems, | |||
you will follow the steps that are described in detail in the next | |||
section. An overview of the steps is provided in the following list. | |||
Examples of setting up your hard disk for multiple operating | |||
systems are provided in Appendix C, 﨓xamples of Installing OS/2 | |||
2.0 and Partitioning Your Hard Disk?on page 77. | |||
1. Begin the installation of OS/2 2.0. | |||
2. Set up a partition for the Boot Manager. | |||
3. Set up any primary partitions on the first hard disk that you | |||
want to use to install other operating systems. | |||
Note: At this point, you can also set up logical drives within | |||
the extended partition for data or programs. | |||
4. Set up the primary partition or logical drive for the OS/2 | |||
Version 2.0 operating system. | |||
5. Install the OS/2 Version 2.0 operating system in that primary | |||
partition or logical drive. | |||
After you have installed OS/2 2.0, you can install the other | |||
operating systems in the primary partitions that you set up in step | |||
3. | |||
Note that OS/2 installation does not control the installation of the | |||
other operating systems. Each operating system must be installed | |||
with its own installation package. | |||
Back up your files! | |||
If you are going to change an existing partition on your hard | |||
disk, you must back up the data or programs in that partition | |||
before you begin installation. | |||
Chapter 4. Installing Multiple Operating Systems 35 | |||
Starting the OS/2 2.0 Installation | |||
1. Insert the OS/2 Installation Diskette into drive A. | |||
2. Turn on the computer. If the computer is already on, press | |||
and hold Ctrl+Alt, and press Del to restart the system. | |||
3. When prompted to do so, remove the Installation Diskette, | |||
insert Diskette 1, and press Enter. | |||
4. If you are installing OS/2 2.0 on a new system (on a hard disk | |||
that does not currently contain an operating system), follow the | |||
instructions listed below under 蘒nstalling OS/2 2.0 on a New | |||
System.?Otherwise, go to 蘒nstalling OS/2 2.0 on an Existing | |||
System?on page 37. | |||
Installing OS/2 2.0 on a New System | |||
If you are installing OS/2 2.0 on a new system (on a hard disk that | |||
does not currently contain an operating system), you see several | |||
introductory screens, followed by this screen: | |||
+-----------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+-----------------------------+ | |||
To install the Boot Manager, do the following: | |||
1. Select option 2 to display the FDISK screen. | |||
2. Go to 﨏reating the Boot Manager Partition?on page 41. | |||
36OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Installing OS/2 2.0 on an Existing System | |||
If you are installing OS/2 2.0 on an existing system (on a hard disk | |||
that currently contains an operating system), you see several | |||
introductory screens, followed by this screen: | |||
+--------------------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+--------------------------------------+ | |||
1. Select option 2. | |||
You see the following screen: | |||
+--------------------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+--------------------------------------+ | |||
2. If you want to save the programs or data in the partition, press | |||
F3 and then use the BACKUP command (or its equivalent) from | |||
your existing operating system. Note that if you do leave the | |||
installation at this point, you will have to restart the entire | |||
installation process. | |||
Chapter 4. Installing Multiple Operating Systems 37 | |||
3. If you have already backed up the data, or if you do not need | |||
to keep the data, press Enter to start the FDISK utility program. | |||
Note: If your hard disk has previously defined partitions, and none | |||
of the partitions is large enough to install OS/2 2.0, the | |||
following screen is displayed: | |||
+-----------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+-----------------------------+ | |||
To start the FDISK utility program and modify the partition sizes, | |||
press Enter. | |||
Warning: If you are increasing the size of an existing partition, | |||
you must back up any information you want to save in that | |||
partition. | |||
To continue with installation, you must modify your hard disk | |||
configuration. This is done with the FDISK utility program. Press | |||
Enter. You will see the Modifying Partitions Warning screen again. | |||
Press Enter, and the FDISK utility program will start. | |||
38OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Setting Up Your Hard Disk | |||
The FDISK screen shows all partitions that are currently set up on | |||
your system. +--------------------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+--------------------------------------+ | |||
If you are installing the OS/2 operating system on a new system, | |||
go to 﨏reating the Boot Manager Partition?on page 41. If | |||
partitions exist on your system, they are listed on the FDISK | |||
screen. Follow the procedures listed below under 﨑eleting | |||
Existing Partitions.? | |||
Deleting Existing Partitions | |||
To set up your system, you must make sure there is enough room | |||
on your hard disk to accommodate the desired setup. It might be | |||
necessary for you to delete some or all of the existing partitions on | |||
your hard disk. | |||
For example, if your hard disk currently has only one partition that | |||
takes up the entire hard disk, you must delete that partition. | |||
However, if your hard disk has ample free space, you can keep | |||
one or more existing partitions and add to them. (An example of | |||
installing the Boot Manager and OS/2 2.0 while preserving an | |||
Chapter 4. Installing Multiple Operating Systems 39 | |||
existing partition is shown in Appendix C, 﨓xamples of Installing | |||
OS/2 2.0 and Partitioning Your Hard Disk?on page 77.) | |||
Note that any changes you specify on the FDISK screen do not | |||
actually go into effect until you press F3 to exit FDISK. You will | |||
then be asked to confirm that you want to save your changes. | |||
Warning: All information you want to save must be backed up. | |||
Changing the size of a partition deletes all information about that | |||
partition, and the entire operating system must be reinstalled | |||
when the new partition is created. | |||
1. Use the Up Arrow ( ) or Down Arrow () key to ? the ? highlight | |||
partition you want to delete. | |||
2. Press Enter to display the Options menu. | |||
+-----------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+-----------------------------+ | |||
3. Select Delete Partition and press Enter. | |||
Notice that the information about the partition is deleted. The | |||
words Free Space are displayed in the space formerly occupied | |||
by the partition information. | |||
4. Repeat steps 1 through 3 for any other partitions that you need | |||
to delete. | |||
40OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
5. When you are finished deleting partitions, continue to | |||
﨏reating the Boot Manager Partition?on page 41. | |||
Creating the Boot Manager Partition | |||
The first partition you create is the Boot Manager partition. To | |||
create this partition: | |||
1. Make sure that the line is highlighted. IfFree Space it is not, | |||
press the Up Arrow ( ) or Down Arrow ( ? ? ) key until it is | |||
highlighted. | |||
2. Press Enter to display the Options menu. | |||
3. Select Install Boot Manager and press Enter. | |||
4. Specify whether the partition should be at the beginning or the | |||
end of the available space on the hard disk. | |||
Note: It is recommended that you install the Boot Manager | |||
partition at the beginning of the hard disk. However, | |||
the only restriction on the placement of the Boot | |||
Manager partition is that it be within the first 1GB | |||
(gigabyte) of the disk space. (A gigabyte is equal to 1 | |||
073 741 824 bytes.) | |||
Chapter 4. Installing Multiple Operating Systems 41 | |||
Creating Partitions for Operating Systems Other than | |||
OS/2 2.0 and for Logical Drives | |||
After you create the partition for the Boot Manager, create primary | |||
partitions for any DOS or previous versions of the OS/2 operating | |||
system you might want to install. Also create any logical drives to | |||
use for data or programs. (Some operating systems, such as AIX, | |||
require that their own disk utility program create the installation | |||
partition. The OS/2 Version 2.0 FDISK utility program cannot | |||
create the partition for these operating systems.) | |||
If you are creating only one partition (for OS/2 Version 2.0), go to | |||
﨏reating the Partition or Logical Drive for OS/2 2.0?on page 47. | |||
Otherwise, follow these steps to create partitions and logical | |||
drives: | |||
1. Make sure that the line is highlighted. Free Space If it is not, | |||
press the Up Arrow ( ) or Down Arrow ( ? ? ) key until it is | |||
highlighted. | |||
2. Press Enter to display the Options menu. | |||
3. Select Create Partition and press Enter. | |||
42OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
4. Type the size (in MB) of the partition you are creating. Use the | |||
following chart to help you determine how large the partition | |||
should be. For more specific information about partition sizes, | |||
see the documentation that came with the product you are | |||
installing. For example, if you are installing OS/2 Version 1.3 | |||
Extended Edition, you should refer to the IBM OS/2 Version 1.3 | |||
Information and Planning Guide for more specific guidance. | |||
Table 1. Planning Table for Partition Sizes | |||
Contents Size Hard Disk Considerations | |||
DOS 3.3 2MBMust be in a primary partition within the | |||
first 32MB on the first hard disk. | |||
DOS 4.0 3MBMust be in a primary partition on the first | |||
hard disk. | |||
DOS 5.0 4MBMust be in a primary partition on the first | |||
hard disk. | |||
OS/2 1.x 20MB Must be in a primary partition on the first | |||
SE hard disk. Installs in less than 20MB, but | |||
segment swapping is inhibited. | |||
OS/2 1.x 30MB Must be in a primary partition on the first | |||
EE hard disk. Installs in less than 30MB with | |||
reduced function. | |||
OS/2 2.0 15-30MB Can be in a primary partition or logical | |||
(See drive. Installs in less than 20MB with | |||
Note b.) reduced function. | |||
AIX Partition size determined and built by AIX | |||
Disk utility program. Partition is created | |||
at the end of the hard disk. | |||
Notes: | |||
a. Place system tools or common applications in a logical | |||
drive within the extended partition so that the data can be | |||
shared among the operating systems. | |||
b. If you will be installing LAN Requester or one of the | |||
Extended Services programs, you need to increase the size | |||
of the OS/2 2.0 partition. These programs require a certain | |||
amount of space in the OS/2 partition, even if you are | |||
Chapter 4. Installing Multiple Operating Systems 43 | |||
installing them in separate partitions. If you are going to | |||
add these programs, create an OS/2 partition of 32MB. | |||
5. Specify whether this is a primary partition or a logical drive | |||
within the extended partition. Consider the following: | |||
? All versions of DOS must reside in primary partitions. | |||
Versions of OS/2 before 2.0 must also reside in primary | |||
partitions. | |||
?Your hard disk can be separated into a maximum of | |||
three primary partitions (in addition to the Boot | |||
Manager partition.) If you are going to create logical | |||
drives within an extended partition, you can set up two | |||
primary partitions (in addition to the Boot Manager | |||
partition). | |||
?Remember that primary partitions cannot share data. | |||
? Logical drives within an extended partition are shareable. | |||
This means that any data installed in the logical drive can | |||
be used by an operating system running from any other | |||
active logical drive on the system, if the file system formats | |||
are compatible. | |||
6. Specify the location of the partition or logical drive you want to | |||
create. Select either Create at Start of Free Space or Create | |||
at End of Free Space. Note that all logical drives must be in | |||
contiguous space on the hard disk. Therefore, when you | |||
create more than one logical drive, make sure that you specify | |||
Create at Start of Free Space for the subsequent drive. | |||
Note: This option is not available when the amount of free | |||
space equals the size of the request. | |||
Once you have set up the partition, you use the Options menu | |||
choices to specify information about the partition. | |||
Options Menu Choices | |||
The following list describes each of the choices on the Options | |||
menu. Note that some of the options are available under certain | |||
conditions only. When an option is not available, it cannot be | |||
selected. (In other words, you cannot move the cursor to the | |||
option to select it.) | |||
44OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Install Boot Manager | |||
This choice is used only oncehen you create the | |||
partition for the Boot Manager. It is unavailable | |||
thereafter. | |||
Create Partitions | |||
This choice is used to create primary partitions and | |||
logical drives within the extended partition. You can | |||
use this choice whenever there is free space available | |||
on the hard disk. | |||
Add to Boot Manager Menu | |||
This choice is used to add the name of a partition or | |||
logical drive to the Boot Manager startup menu. You | |||
should use this choice for any operating system that | |||
you want to be able to select when you start the | |||
system. When you select this choice, the New Name | |||
window is displayed. You use the New Name window | |||
to assign a meaningful name to the partition or logical | |||
drive. | |||
Change Partition Name | |||
This choice is used to change the name that you have | |||
previously assigned to a partition or logical drive. | |||
Assign C: Partition | |||
This choice is used to specify which primary partition | |||
you want to be active (when more than one primary | |||
partition is installed on your system). The placement of | |||
the drive letter (C) tells you which primary partition will | |||
be visible (or accessible) after you restart the system. | |||
Set Startup Values | |||
This choice is used to specify the actions of the Boot | |||
Manager startup menu. For example, with Set Startup | |||
Values, you can specify how long you want the Boot | |||
Manager menu to be displayed before the default | |||
operating system is started. You can also specify which | |||
operating system you want as the default. | |||
Remove from Boot Manager Menu | |||
This choice is used to delete a name from the Boot | |||
Manager startup menu. When you delete the name, | |||
you can no longer select the operating system | |||
Chapter 4. Installing Multiple Operating Systems 45 | |||
associated with that name from the Boot Manager | |||
startup menu. | |||
Delete Partition | |||
This choice is used to delete information about a | |||
primary partition or logical drive. After you exit from | |||
FDISK, all the data in the partition or logical drive is | |||
deleted. | |||
Set Installable | |||
This choice is used to mark a partition or logical drive | |||
as the target for installation. For example, before you | |||
install the OS/2 Version 2.0 operating system, you set | |||
one primary partition (or logical drive) as installable. | |||
Later, when you install other operating systems, you | |||
mark their partitions as installable before you actually | |||
install the operating systems. | |||
After you install OS/2 2.0, the status of this partition is | |||
changed from Installable to Bootable. | |||
Make Startable | |||
This choice is used to determine which partition or | |||
logical drive is activated when you start your system. | |||
When you install the Boot Manager, it is automatically | |||
marked as startable. This means that the Boot | |||
Manager is in control when you start your system. Only | |||
one partition on the first hard disk can be made | |||
startable. If you set any other partition startable, the | |||
Boot Manager startup menu will not appear when you | |||
start the system. | |||
Specifying Options | |||
To specify options for the partition you just created: | |||
1. Press Enter to display the Options menu. | |||
2. Select Add to Boot Manager Menu if you want this partition | |||
displayed on the Boot Manager startup menu. If you do not | |||
select this choice for the partition, you cannot select the | |||
operating system that exists in this partition from the menu at | |||
startup time. | |||
46OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
a. If you select Add to Boot Manager Menu, you see the | |||
window in which you are asked to type a name for the | |||
partition. Type the name. | |||
b. Press the Enter key. | |||
If you have additional partitions to set up, follow the instructions | |||
outlined in 﨏reating Partitions for Operating Systems Other than | |||
OS/2 2.0 and for Logical Drives?on page 42. Otherwise, continue | |||
to 﨏reating the Partition or Logical Drive for OS/2 2.0.? | |||
Creating the Partition or Logical Drive for OS/2 2.0 | |||
After you have created the partitions for the Boot Manager and for | |||
each of the other operating systems you plan to install, create the | |||
partition or logical drive in which you will install OS/2 2.0. OS/2 | |||
2.0 can be installed in either a primary partition or a logical drive | |||
within the extended partition. | |||
Important: Some operating systems, such as AIX, use their own | |||
disk utility program to set up partitions. The partitions for such | |||
operating systems are created when you actually install the | |||
operating systems. You must leave sufficient space on the hard | |||
disk to accommodate these operating systems. | |||
To create the partition or logical drive for OS/2 2.0: | |||
1. Make sure that the line is highlighted. IfFree Space it is not, | |||
press the Up Arrow ( ) or Down Arrow ( ? ? ) key until it is | |||
highlighted. | |||
2. Press Enter to display the Options menu. | |||
3. Select Create Partition and press Enter. | |||
4. Type the size (in MB) of the partition or logical drive you are | |||
creating. | |||
5. Specify whether this partition is a primary partition or a logical | |||
drive within the extended partition. | |||
If you have already marked three partitions as primary | |||
partitions, you might want to select Extended Logical Drive for | |||
OS/2 2.0. Your hard disk can be made up of a maximum of | |||
four primary partitions or three primary partitions and multiple | |||
Chapter 4. Installing Multiple Operating Systems 47 | |||
logical drives within one extended partition. So, if you create a | |||
primary partition for OS/2 2.0 when three primary partitions | |||
already exist, you cannot create any logical drives. | |||
6. Specify the location of the partition or logical drive you want to | |||
create. | |||
Note: This option is not available when the amount of free | |||
space equals the size of the request. | |||
Specifying Options for the OS/2 2.0 Partition or Logical | |||
Drive | |||
Once you have set up the partition or logical drive, you use the | |||
Options menu choices to specify certain information. For example, | |||
you use the Options menu to give the partition or logical drive a | |||
name. | |||
To specify options: | |||
1. Press Enter to display the Options menu. | |||
2. Highlight Add to Boot Manager Menu and press Enter. | |||
3. Type the name you want to assign to this partition or logical | |||
drive, and press Enter. | |||
4. Press Enter to display the Options menu. | |||
5. Highlight Set Installable and press Enter. | |||
You must select Set Installable for this partition or logical drive. | |||
By selecting Set Installable, you indicate which partition or | |||
logical drive should be used for OS/2 2.0. | |||
6. Use the Set startup values choice if you are going to have | |||
multiple operating systems installed. (You use Set startup | |||
values to configure the Boot Manager environment. In this | |||
window, you indicate how you want the Boot Manager startup | |||
menu displayed.) | |||
Note: You can indicate how you want your Boot Manager | |||
environment configured during this part of installation, | |||
or you can choose to configure the environment after | |||
installation. To configure the Boot Manager | |||
environment after installation, use the FDISKPM utility | |||
48OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
program. (FDISKPM includes most of the features of | |||
FDISK, but it is displayed in a Presentation Manager | |||
window.) To start FDISKPM after installation, type | |||
FDISKPM at an OS/2 command prompt. | |||
Chapter 4. Installing Multiple Operating Systems 49 | |||
When you select Set startup values from the Options menu of | |||
FDISK, the following screen is displayed: | |||
+-----------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+-----------------------------+ | |||
a. Specify the default drive: | |||
1) Highlight the line that contains the information for the | |||
operating system you want preselected at startup time. | |||
For example, if you want OS/2 2.0 to be the preselected | |||
choice on the Boot Manager startup menu, highlight | |||
the line. OS/2 2.0 | |||
2) Press Enter to display the Options menu. | |||
3) Select Set startup values. | |||
4) With Default highlighted, press Enter. Notice that the | |||
name of the partition you chose is listed next to | |||
Default. | |||
b. Set the menu display time: | |||
1) Indicate how long you want the Boot Manager startup | |||
menu displayed when you start your system. If you | |||
want the menu displayed for a certain period of time | |||
before the default operating system starts, accept the | |||
value of Yes. If you want the menu to be displayed | |||
indefinitely (until you explicitly select a choice from the | |||
50OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
menu), highlight Timer and press Enter to change the | |||
value to No. | |||
2) If you selected Yes for Timer, indicate how long you | |||
want the menu displayed before the default operating | |||
system is started. You can either accept the value | |||
listed next to Timeout or you can change the value. To | |||
change the value: | |||
a) Select Timeout. | |||
b) Type the amount of time (in seconds) that you want | |||
the menu displayed before the preselected | |||
operating system is automatically started. | |||
c) Press Enter. | |||
c. Set the menu mode to indicate how you want the Boot | |||
Manager startup menu to be displayed. | |||
You can select Normal or Advanced. The normal mode | |||
menu looks like this: | |||
+--------------------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+--------------------------------------+ | |||
The following screen shows the same menu in the | |||
advanced mode format. | |||
Chapter 4. Installing Multiple Operating Systems 51 | |||
+-----------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+-----------------------------+ | |||
To change the mode that is currently displayed: | |||
1) Highlight Mode. | |||
2) Press Enter. | |||
d. Press F3 to update your FDISK screen. | |||
Saving Your Changes | |||
Once you have set up your hard disk, you must save your | |||
changes. | |||
1. Press F3. | |||
2. Select Save and Exit and press Enter. | |||
The options you select during your FDISK session will not be | |||
active until you select Save and Exit and press Enter. | |||
Note that you will be asked to reinsert the Installation Diskette and | |||
the numbered diskettes. | |||
52OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Continuing with OS/2 2.0 Installation | |||
Once all your partitions are set up, continue installing the OS/2 | |||
Version 2.0 operating system. Follow the instructions on the | |||
screen. | |||
When the Installation Drive Selection screen is displayed, select | |||
option 1, Accept the drive. | |||
Selecting the Operating System Features | |||
Once the hard disk of your computer is set up, you see the OS/2 | |||
Setup and Installation screen. In this part of installation, you make | |||
choices about which features of the operating system you want to | |||
install. | |||
If you need assistance in completing the screen, press the F1 key | |||
to see more information about your choices. (Or, you can refer to | |||
Chapter 2, 蘒nstalling OS/2 2.0 as the Only Operating System?on | |||
page 9, which provides additional information about making | |||
selections on the screen.) | |||
Formatting Logical Drives | |||
If you have any logical drives that you want to format, you can do | |||
so by selecting Format from the Options menu of the OS/2 Setup | |||
and Installation screen. For example, if you want to format one of | |||
your logical drives for the High Performance File System, you | |||
would do the following: | |||
1. Select Options from the menu bar of the OS/2 Setup and | |||
Installation screen. | |||
2. Select Format. | |||
3. Specify the High Performance File System. | |||
Viewing the Tutorial | |||
After OS/2 installation is completed, you will see the OS/2 Tutorial. | |||
After you complete the tutorial, install any other operating systems | |||
for which you have created partitions. | |||
Chapter 4. Installing Multiple Operating Systems 53 | |||
Installing Other Operating Systems | |||
When the Boot Manager and OS/2 2.0 are installed, you can install | |||
the other operating systems. | |||
54OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Do you have more than one primary partition? | |||
If you set up more than one primary partition (other than the | |||
Boot Manager partition) when you set up your hard disk, follow | |||
this procedure before you begin the installation of the operating | |||
systems. | |||
You need to indicate which primary partition should be used for | |||
the operating system you are installing. For example, suppose | |||
three partitions (in addition to the Boot Manager partition) are | |||
set up on your hard disk: two primary partitions and one | |||
extended partition containing logical drives. If you want to | |||
install OS/2 Version 1.3 in the first primary partition, you have | |||
to make sure that the first primary partition is marked as | |||
installable. | |||
To set the partition to installable, use FDISKPM. (FDISKPM | |||
includes most of the features of FDISK, but it is displayed in a | |||
Presentation Manager window.) | |||
1. Select OS/2 System. | |||
2. Select Command Prompts. | |||
3. Select OS/2 Window. | |||
4. Type fdiskpm and press Enter. | |||
The drive letter (for example, C:) is shown next to the primary | |||
partition that is active. (Remember that only one primary | |||
partition can be active, or accessible, at a time.) If the partition | |||
in which you want to install the operating system is not the | |||
active primary partition, do the following: | |||
1. Highlight the partition in which you want to install the | |||
operating system. | |||
2. Select Options from the menu bar. | |||
3. Select Set Installable. | |||
4. Select Options from the menu bar. | |||
5. Select Exit. | |||
6. Select the Save pushbutton from the window that is | |||
displayed. | |||
Chapter 4. Installing Multiple Operating Systems 55 | |||
Once you set the correct primary partition as installable (if you | |||
have more than one primary partition), you can begin the | |||
installation of the other operating systems. | |||
Note: If you going to install DOS and a version of the OS/2 | |||
operating system in the same primary partition, refer to | |||
Chapter 3, 嗀dding OS/2 2.0 to a DOS System?on page 17 | |||
for instructions. Remember that, to use the Dual Boot | |||
feature, you must install DOS in the partition before you | |||
install the OS/2 operating system. | |||
1. Insert the installation diskette from the operating system you | |||
are installing. Then, press and hold Ctrl+Alt, and press Del to | |||
restart the system. | |||
2. During installation, make sure that you install the operating | |||
system in the desired partition. If you are asked whether you | |||
want to format the partition, indicate that you do. FDISK sets | |||
up partitions but does not format them. | |||
3. Press and hold Ctrl+Alt, and press Del to restart the system. | |||
4. If you installed OS/2 Version 1.3 or DOS Version 5.0, you will | |||
need to make the Boot Manager partition startable. You | |||
should also follow the steps outlined below if, for any reason, | |||
the Boot Manager startup menu does not appear as you | |||
specified it during installation of the OS/2 Version 2.0 operating | |||
system. (For example, if you installed multiple operating | |||
systems and wanted the Boot Manager startup menu to appear | |||
but, instead, one of the other operating systems starts, you | |||
would need to make the Boot Manager partition startable. In | |||
DOS terminology, this is the same as making the partition | |||
active.) You can use the version of FDISK (or its equivalent) | |||
from the operating system that is active to make the Boot | |||
Manager partition startable. Or, you can do the following: | |||
a. Insert the OS/2 Installation Diskette into drive A. | |||
b. Press and hold Ctrl+Alt, and press Del to restart the | |||
system. | |||
c. When prompted to do so, remove the Installation Diskette, | |||
insert Diskette 1, and press Enter. | |||
d. When the Welcome screen is displayed, press Esc to | |||
display an OS/2 command prompt. | |||
56OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
e. Type fdisk and press Enter. | |||
f. Make sure that the Boot Manager partition is highlighted. | |||
If it is not, press the Up Arrow ( ) or Down Arrow () key ? ? | |||
until it is highlighted. | |||
g. Press Enter to display the Options menu. | |||
h. Select Make Startable and press Enter. | |||
i. Press F3 to save your changes. | |||
j. Select Save and Exit and press Enter. | |||
k. Remove the diskette from drive A. | |||
l. Press and hold Ctrl+Alt, and press Del to restart the | |||
system. | |||
5. If one of your primary partitions is set up for Dual Boot, copy | |||
the BOOT.COM file from OS/2 2.0 to the Dual Boot partition. | |||
(Copying the BOOT.COM file will replace the versions supplied | |||
by the other operating systems.) | |||
6. If you have installed AIX, you should add it to the Boot | |||
Manager startup menu. With OS/2 running, type FDISKPM at | |||
an OS/2 command prompt. Then do the following: | |||
a. Highlight the line that contains information about AIX. | |||
b. Select Options from the menu bar. | |||
c. Select Add to Boot Manager menu. | |||
d. Type a name for the partition and press Enter. | |||
e. Select Options from the menu bar. | |||
f. Select Exit. | |||
g. Select the Save pushbutton from the window that is | |||
displayed. | |||
You will now be able to select AIX from the Boot Manager | |||
startup menu. | |||
Chapter 4. Installing Multiple Operating Systems 57 | |||
58OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Chapter 5. Alternative Ways to Install | |||
This chapter describes alternative ways to install the OS/2 | |||
operating system. It is intended primarily for the person who will | |||
be setting up workstations for other users. | |||
Included in this chapter is information on installing OS/2 2.0 using | |||
a response file. The chapter also includes a section on modifying | |||
the response file that is shipped with the OS/2 installation | |||
diskettes. | |||
This chapter also explains how to redirect the installation process | |||
so that you can install from a source other than diskette drive A. | |||
Note that a brief overview of redirected installation is provided. | |||
Detailed information about managing remote installations can be | |||
found in OS/2 Version 2.0 Remote Installation and Maintenance | |||
(GG24-3780). | |||
Understanding the Response File Installation | |||
If you have installed a previous version of the OS/2 operating | |||
system or if you have installed other operating systems, you are | |||
probably familiar with the typical installation procedure: you insert | |||
diskettes and answer screen prompts. When you use a response | |||
file, it is not necessary to answer any prompts. All the answers | |||
are in the response file. You can place the response file on | |||
Diskette 1 and begin the installation as usual. Or, you can place | |||
the response file on another source. (See 蘒nstalling OS/2 2.0 from | |||
a Source Other than Drive A?on page 63.) In either case, the | |||
installation program will read the file (instead of prompting the | |||
user) for the installation information. | |||
+ Copyright IBM Corp. 1991 59 | |||
Modifying the Response File | |||
A response file is included on the OS/2 installation diskettes. | |||
When you install the operating system, this response file (named | |||
SAMPLE.RSP) is placed in the OS2\INSTALL directory. So, after | |||
you install the operating system on your own system, you can | |||
modify the sample response file and then use it for installation on | |||
another workstation. You use an editor (such as the System | |||
Editor) to modify the response file. | |||
The following is an example of what the response file looks like. | |||
60OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
************************************************************** | |||
*AlternateAdapter * | |||
* * | |||
* Specifies secondary adapter for two display systems. * | |||
* This should be a lower or equal resolution display since * | |||
* the highest resolution display will be primary for PM. * | |||
* * | |||
* Valid Parms: * | |||
* * | |||
* 0=none (DEFAULT) * | |||
* 1=Other than following (DDINSTAL will handle) * | |||
* 2=Monochrome Printer Adapter * | |||
* 3=Color Graphics Adapter * | |||
* 4=Enhanced Graphics Adapter * | |||
* 5=Video Graphics Adapter * | |||
* 6=8514/A Adapter * | |||
* 7=XGA Adapter * | |||
************************************************************** | |||
AlternateAdapter=0 | |||
************************************************************** | |||
*BaseFileSystem * | |||
* * | |||
* Specifies which file system should be used to format * | |||
* the install partition * | |||
* * | |||
* Valid Parms: * | |||
* * | |||
* 1=HPFS (DEFAULT) * | |||
* 2=FAT * | |||
************************************************************** | |||
BaseFileSystem=2 | |||
************************************************************** | |||
* CDROM * | |||
* * | |||
* Specifies which, if any, CD ROM IFS files should be * | |||
* installed. * | |||
* * | |||
* Valid Parms: * | |||
* * | |||
* 0 = None * | |||
* 1 = All * | |||
* 2 = CD-ROM IFS (DEFAULT) * | |||
* 3 = IBM CD-ROM Device Drivers * | |||
************************************************************** | |||
CDROM=2 | |||
As you can see, the file contains comments about the various | |||
options and lists the values you should enter if you want | |||
something other than the default value. If you do not modify a | |||
response, the default value is used. | |||
Chapter 5. Alternative Ways to Install 61 | |||
For example, suppose you want to set up a system in which no | |||
CD-ROM support is required. In the response file, you would | |||
indicate that no support be installed by entering: | |||
CDROM=0 | |||
The following is a list of the steps you would perform to modify a | |||
response file and then place the response file on Diskette 1. | |||
1. Make a copy of the SAMPLE.RSP file (located in the | |||
OS2\INSTALL directory). | |||
2. Use an editor (such as the System Editor) to modify the file. | |||
The file contains comments that explain each of the installation | |||
options. | |||
3. Once you have modified and saved the response file, copy it to | |||
Diskette 1 with the name OS2SE20.RSP. | |||
Note: You can place the response file in a location other than | |||
Diskette 1. For example, the response file could be | |||
located on the server in a local area network. The next | |||
section describes the process for pointing to a source | |||
other than drive A for installation information. | |||
4. Copy the RSPINST.EXE file (located in the OS2\INSTALL | |||
directory) to Diskette 1. | |||
5. Begin the installation of the workstation by inserting the | |||
Installation Diskette and restarting the system. | |||
6. When prompted, switch diskettes and press Enter. | |||
From this point, the installation program will prompt only for the | |||
insertion of diskettes. No other installation screens will appear. | |||
Note that you can use this procedure to install the same set of | |||
options on multiple workstations. Using a response file, you can | |||
make sure that all workstations in an area are set up with the | |||
same set of options. | |||
62OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Installing OS/2 2.0 from a Source Other than Drive A | |||
The operating system typically is installed from a diskette inserted | |||
into drive A. However, with OS/2 2.0, you can redirect the | |||
installation by specifying a source other than the diskettes in drive | |||
A. For example, you can direct the installation to a CD-ROM. In a | |||
local area network environment, for example, any or all of the | |||
workstations connected to a server could request that the | |||
installation source be a drive on the server. This type of | |||
installation requires additional software (such as a LAN support | |||
product). | |||
Redirecting the Installation | |||
There are several ways to redirect the installation of OS/2 2.0. | |||
You can modify information on Diskette 1 to point to another | |||
source. If that source contains a copy of the installation diskettes, | |||
the user is prompted for choices but is not asked to swap | |||
diskettes. The source can also be specified in a response file. If a | |||
response file exists on the redirected source, the user is not | |||
prompted for any choices. | |||
You can modify the CONFIG.SYS file that is found on Diskette 1 to | |||
indicate that installation should proceed from a source other than | |||
drive A. | |||
? One of the ways to indicate redirection is to modify the | |||
PROTSHELL statement of the CONFIG.SYS file. For example, | |||
to point to an alternative source for installation information, | |||
you would add a drive letter and file name to the | |||
PROTSHELL= statement: | |||
PROTSHELL=SYSINST1.EXE SYSINST2.EXE Z:\OS2SE20 | |||
When the system reads Diskette 1, it finds this statement and | |||
looks for the SYSINST1.EXE and SYSINST2.EXE installation | |||
programs in the specified directory of drive Z. Installation then | |||
proceeds from that drive, and there is no prompting for | |||
insertion of diskettes. | |||
? Instead of modifying the PROTSHELL statement, you can add | |||
an environment variable to the CONFIG.SYS file. For example, | |||
you could add the following statement to the file: | |||
Chapter 5. Alternative Ways to Install 63 | |||
SET SOURCEPATH=Z:\OS2SE20 | |||
You would then add the same drive and file name to the PATH | |||
and DPATH statements of the CONFIG.SYS file. | |||
Another way to specify redirection of installation is to use the | |||
response file on Diskette 1 to point to another source. For | |||
example, you can modify the sample response file by adding the | |||
following statement to the response file: | |||
SourcePath=Z:\OS2SE20 | |||
Then, when this response file is placed on Diskette 1, the | |||
installation program looks to the drive specified for its installation | |||
information. | |||
A response file can be copied to the directory specified above | |||
rather than to Diskette 1. If a response file (with the correct name | |||
OS2SE20.RSP) exists in both places, the file on the diskette is | |||
checked first. | |||
Setting Up an Alternative Installation Source | |||
The OS/2 installation program can use a drive other than A as its | |||
installation source. This redirected drive can be a CD-ROM, a | |||
drive on the hard disk, or a remote drive that is connected to a | |||
LAN. If the redirected drive requires special software, you will | |||
have to copy those files to Diskette 1 and modify the CONFIG.SYS | |||
file on Diskette 1. The following section describes the steps | |||
needed to install from a CD-ROM. For information on installing | |||
from other drives, refer to OS/2 Version 2.0 Remote Installation and | |||
Maintenance (GG24-3780). | |||
Installing from a CD-ROM Device | |||
When the installation program begins, it searches all the drives on | |||
a system for a file named OS2SE20.SRC. If that file is found by the | |||
installation program, it reads the first line of the file to find the | |||
installation source information. | |||
When OS/2 is delivered on a CD-ROM, it already contains the | |||
OS2SE20.SRC file. You begin the installation from diskette, as | |||
64OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
usual, but after a certain point, the installation is redirected to the | |||
CD-ROM. | |||
If the OS/2 Version 2.0 operating system was delivered on a | |||
CD-ROM, do the following: | |||
1. Insert the CD-ROM into its drive. | |||
2. Insert the Installation Diskette into drive A. | |||
3. Turn on the computer. If the computer is already on, press | |||
and hold the Ctrl and Alt keys, and press Del to restart the | |||
system. | |||
4. Follow the prompts that are displayed on the screen. You will | |||
be asked to switch diskettes before the installation program | |||
begins to read the OS2SE20.SRC file on the CD-ROM drive. | |||
Chapter 5. Alternative Ways to Install 65 | |||
66OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Appendix A. Customizing the Operating System | |||
This appendix describes how you can customize your operating | |||
system without completely reinstalling it. | |||
You can use the System Configuration folder to change choices | |||
such as the time and date, your screen colors and window | |||
borders, and to change your mouse for right- or left-hand use. | |||
Select the System Configuration folder from the OS/2 System | |||
folder to see the objects (for example, the mouse) that you can | |||
customize. | |||
You can also replace the user interface (sometimes called a shell) | |||
that comes with the OS/2 Version 2.0 operating system. You | |||
replace the user interface by modifying a statement in the | |||
CONFIG.SYS file. See the online Master Index for details on | |||
replacing the user interface. | |||
Features that You Can Change or Add | |||
After you install the operating system, you might decide to change | |||
your mouse or display. Or, you might decide that you want to add | |||
some features that you chose not to add during the initial | |||
installation. You can make the change or add the features without | |||
completely reinstalling the operating system. | |||
The following are the features you can add to your system: | |||
? | |||
CD-ROM Device Support | |||
Provides system support for CD-ROM devices. | |||
? | |||
Documentation | |||
Adds the OS/2 Tutorial, the OS/2 Command Reference, or the | |||
REXX Information. | |||
? Fonts | |||
+ Copyright IBM Corp. 1991 67 | |||
Determines the print style for your system. The OS/2 | |||
operating system offers bit-map fonts and fonts in Adobe ** Type | |||
1 format for displaying and printing data on many output | |||
devices; however, the bit-map fonts are not supported for | |||
printing on vector devices, such as plotters. For compatibility, | |||
the operating system also supports the Presentation Manager | |||
outline fonts. | |||
When no fonts are selected, the system default font and the | |||
Helvetica ** fonts are installed. | |||
? Optional System Utilities | |||
Provide a full set of system utility programs to: | |||
?Back up the hard disk | |||
?Change file attributes | |||
?Display the directory tree | |||
?Manage partitions | |||
?Label diskettes | |||
?Link object modules | |||
?Convert, display, and print pictures | |||
?Use PMREXX | |||
?Recover files | |||
?Restore backed-up files | |||
?Sort files | |||
?Install OS/2 compilers. | |||
? Tools and Games | |||
Provide productivity aids (such as an enhanced editor and a | |||
calculator) as well as games. | |||
? | |||
OS/2 DOS and Windows Support | |||
Enables DOS and Microsoft Windows programs to run on the | |||
OS/2 operating system. If you select this feature, you will be | |||
prompted to indicate which of your existing DOS and Windows | |||
applications you want to migrate to OS/2 2.0. | |||
? | |||
High Performance File System | |||
** Trademark of Adobe Systems Incorporated. | |||
** Trademark of the Linotype Company. | |||
68OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Provides fast access to large disk volumes. Features of the | |||
High Performance File System include: | |||
?File names up to 254 characters in length | |||
?Large file support | |||
?Strategic allocation of directory structures | |||
?Processing of metacharacters that are generally used for | |||
displaying and printing graphics. | |||
? | |||
REXX | |||
Installs the REXX Operating System/2 procedures language. | |||
This batch language can be used to develop Systems | |||
Application Architecture * (SAA*) programs. | |||
? Serial Device Support | |||
Provides system support for attached serial devices, such as a | |||
modem, a serial plotter, or a serial printer assigned to a | |||
communication port. This choice is not required for mouse | |||
support. | |||
? Serviceability and Diagnostic Aids | |||
Provide information primarily for a technical coordinator to | |||
isolate and correct system problems. | |||
? | |||
Optional Bitmaps | |||
Provides a set of bitmaps that you can use to change the | |||
background of your system. | |||
Changing Your Setup or Adding Features | |||
To change your setup or add a feature, do the following: | |||
1. Select OS/2 System. | |||
2. Select System Setup. | |||
3. Select Selective Install. | |||
* Trademark of the IBM Corporation. | |||
Appendix A. Customizing the Operating System 69 | |||
4. Select the item you want to change (for example, mouse, | |||
keyboard, display, or country). After making any changes, | |||
select the OK pushbutton. | |||
5. On the next screen, select the features that you want to install. | |||
Note: If a More pushbutton accompanies a feature, you must | |||
select the pushbutton to view the features. For | |||
example, if you want to install a document, select | |||
Documentation and then select the More pushbutton to | |||
display a list of documents. Then, select the document | |||
that you want to add. | |||
6. When prompted, insert the numbered installation diskettes to | |||
complete the process. | |||
70OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Appendix B. Diagnosing System Problems | |||
The operating system provides programs that help you gather | |||
information to isolate and correct system problems. You can learn | |||
more about this information by selecting topics under the Problem | |||
determination heading in the Master Index. | |||
If your system has failed, however, it will not be possible to get | |||
online help. This appendix provides information about such | |||
system failures, and about: | |||
? Recovering the CONFIG.SYS file | |||
? Recovering user and system INI files | |||
? Recovering from errors on the hard disk | |||
? Responding to installation errors. | |||
Note: Backing up your system regularly may help you avoid | |||
having to re-create files in the event of a system failure. | |||
Recovering the CONFIG.SYS File | |||
The CONFIG.SYS file contains command statements that set up | |||
your system. If the file is changed incorrectly, you cannot restart | |||
the system or edit the file. To recover the CONFIG.SYS file: | |||
1. Insert the Installation Diskette into drive A. | |||
2. Turn on the computer. | |||
If the computer is already on, press and hold Ctrl+Alt, and | |||
press Del to restart the system. | |||
3. When the logo screen appears, remove the Installation Diskette | |||
and insert Diskette 1. | |||
4. Press Enter. | |||
5. When the Welcome screen appears, press Esc. | |||
6. Change to the drive where your operating system resides. For | |||
example, if the operating system is in drive C, type: | |||
C: | |||
and press Enter. | |||
+ Copyright IBM Corp. 1991 71 | |||
7. Rename the damaged CONFIG.SYS file by typing | |||
REN CONFIG.SYS CONFIG.BAD | |||
and pressing Enter. | |||
8. Copy the CONFIG.SYS backup file to the root directory of the | |||
drive where your operating system resides. (The CONFIG.SYS | |||
backup file was created during installation.) For example, if | |||
the operating system is in drive C, type: | |||
COPY C:\OS2\INSTALL\CONFIG.SYS C:\CONFIG.SYS | |||
and press Enter. | |||
9. Remove Diskette 1 from drive A. | |||
10. Press and hold Ctrl+Alt, and press Del to restart the system. | |||
Note: If you changed the CONFIG.SYS file after installing the | |||
operating system, use an editor to either correct the | |||
damaged file (now named CONFIG.BAD) or update the | |||
current CONFIG.SYS file. | |||
Recovering User and System INI Files | |||
System settings, such as application defaults, display options, and | |||
file options, are defined in the OS2.INI startup file in the OS2 | |||
directory of your hard disk. Information about installed fonts and | |||
printer drivers is contained in a system file called OS2SYS.INI. If | |||
you receive a message that the OS2.INI file has been damaged, | |||
replace both of these files as follows: | |||
1. Insert the Installation Diskette into drive A. | |||
2. Turn on the computer. | |||
If the computer is already on, press and hold Ctrl+Alt, and | |||
press Del to restart the system. | |||
3. After the logo screen appears, remove the Installation Diskette | |||
and insert Diskette 1. | |||
4. Press Enter. | |||
5. When the Welcome screen is displayed, press Esc. | |||
6. Change to the drive where your operating system resides. For | |||
example, if the operating system is in drive C, type: | |||
72OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
C: | |||
and press Enter. | |||
7. Change to the OS2 subdirectory by typing | |||
CD \OS2 | |||
and pressing Enter. | |||
8. Erase the current OS2.INI file by typing | |||
ERASE OS2.INI | |||
and pressing Enter. | |||
9. Create a new user INI file by typing | |||
MAKEINI OS2.INI INI.RC | |||
and pressing Enter. | |||
10. Erase the current OS2SYS.INI file by typing | |||
ERASE OS2SYS.INI | |||
and pressing Enter. | |||
11. Create a new system INI file by typing | |||
MAKEINI OS2SYS.INI INISYS.RC | |||
and pressing Enter. | |||
Note: The MAKEINI.EXE file was added to the OS2 directory of | |||
your hard disk during installation of the operating | |||
system. | |||
12. Remove Diskette 1 from drive A. | |||
13. Press and hold Ctrl+Alt, and press Del to restart the system. | |||
You can protect your INI files by copying back levels of the files | |||
each time you start your system. For example, you could include | |||
the following statements in your CONFIG.SYS file: | |||
CALL=C:\OS2\XCOPY.EXE C:\OS2\*.INX c:\OS2\*.INY | |||
CALL=C:\OS2\XCOPY.EXE C:\OS2\OS2*.INI C:\OS2\*.INX | |||
These statements make a copy of your current INI files and also | |||
make a copy of the INI files you previously backed up. | |||
Appendix B. Diagnosing System Problems 73 | |||
By copying your files each time you start the system, you will | |||
always be able to recover an earlier verion of the INI files. | |||
Recovering from Errors on the Hard Disk | |||
The CHKDSK command with the parameter /F can be used to | |||
correct disk and directory errors. However, when you use the /F | |||
parameter, no activity can occur on the disk. Therefore, if you | |||
need to correct errors on the drive from which you normally start | |||
the operating system, you must use the version of CHKDSK that is | |||
on the installation diskettes (instead of the version that has been | |||
installed on the hard disk). | |||
To correct errors on the drive from which you normally start the | |||
operating system: | |||
1. Insert the Installation Diskette into drive A. | |||
2. Turn on the computer. | |||
If the computer is already on, press and hold Ctrl+Alt, and | |||
press Del to restart the system. | |||
3. When the logo screen appears, remove the Installation Diskette | |||
and insert Diskette 1. | |||
4. Press Enter. | |||
5. When the Welcome screen appears, press Esc. | |||
6. When the OS/2 command prompt appears, remove Diskette 1 | |||
and insert Diskette 2 (the diskette that contains the CHKDSK | |||
command). | |||
7. To correct the errors on your hard disk, type the following at | |||
the command prompt: | |||
CHKDSK C: /F | |||
and press Enter. (If your operating system resides on a drive | |||
other than C, type the appropriate drive letter after the | |||
CHKDSK command.) | |||
8. Remove the diskette from drive A. | |||
9. Press and hold Ctrl+Alt, and press Del to restart the system. | |||
74OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Responding to Installation Errors | |||
If you receive an error message while installing the operating | |||
system, take the appropriate corrective action. | |||
Only some files were copied. You might be out of disk space. | |||
Explanation: (1) The installation program could not transfer one or | |||
more files, because a version of the files already exists on the hard | |||
disk with the read-only, system, or hidden attributes set. | |||
(2) The installation program stopped transferring files because there | |||
was not enough hard disk space. | |||
Action: (1) Return the attributes of the OS/2 files to their original | |||
setting. Use the ATTRIB command to remove the read-only | |||
attributes. | |||
(2) Move non-OS/2 operating system files out of the installation | |||
partition. You can store these files in the extended partition or on a | |||
diskette. If you intend to format the installation partition, remember | |||
to use the BACKUP command to save any important files. | |||
An error occurred when the installation program tried to copy a file. | |||
Explanation: (1) The installation program could not transfer one or | |||
more files, because a version of the files already exists on the hard | |||
disk with the read-only, system, or hidden attributes set. | |||
(2) The installation program stopped transferring files because there | |||
was not enough hard disk space. | |||
(3) The hard disk might contain errors. | |||
Action: (1) Return the attributes of the OS/2 files to their original | |||
settings. Use the ATTRIB command to remove the read-only | |||
attributes. | |||
(2) Move non-OS/2 operating system files out of the installation | |||
partition. You can store these files in an extended partition or on a | |||
diskette. If you intend to format the installation partition, remember | |||
to use the BACKUP command to save any important files. | |||
(3) Follow the CHKDSK procedure outlined in the section | |||
ecovering from Errors on the Hard Disk?on page 74. | |||
Appendix B. Diagnosing System Problems 75 | |||
An error occurred when the installation program tried to transfer | |||
system files to your hard disk. Your hard disk might be unusable. | |||
Explanation: The installation program stopped transferring files | |||
because there was not enough hard disk space. The system files | |||
consist of the OS2LDR and OS2KRNLI files on the Installation | |||
Diskette. | |||
Action: Move non-OS/2 operating system files out of the installation | |||
partition. You can store these files in an extended partition or on a | |||
diskette. If you intend to format the installation partition, remember | |||
to use the BACKUP command to save any important files. | |||
An error occurred while trying to run a program. | |||
Explanation: (1) The installation program could not find one of the | |||
following programs: FDISK, MAKEINI, CHKDSK, FORMAT, or | |||
UNPACK. | |||
(2) The installation program could not run a program, because there | |||
is not enough memory to install it. | |||
Action: (1) Verify that the program exists on the diskette or | |||
installation partition. | |||
(2) Add more system memory. | |||
The installation program was unable to load a module into memory. | |||
Explanation: The installation program could not load a system | |||
module because there is not enough memory. | |||
Action: Add more system memory. | |||
Making the Boot Manager Active | |||
If you set up multiple operating systems but the Boot Manager | |||
startup menu does not appear as you specified it during | |||
installation, you will need to make the Boot Manager partition | |||
startable. See page 56 for instructions on making the Boot | |||
Manager partition startable. | |||
76OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Appendix C. Examples of Installing OS/2 2.0 and | |||
Partitioning Your Hard Disk | |||
This appendix shows four examples of partitioning the hard disk of | |||
your system during the installation of the OS/2 Version 2.0 | |||
operating system. | |||
Example 1 shows you how to delete an existing partition and set | |||
up two areas on the hard disk: a primary partition for OS/2 2.0 | |||
and a logical drive within the extended partition for data. The | |||
remaining examples show you how to set up your system so that | |||
you can install multiple operating systems in their own partitions. | |||
Example 1: Creating a Primary Partition and a Logical | |||
Drive for Data | |||
This example shows you how to set up a primary partition for OS/2 | |||
2.0 and a logical drive in the extended partition. The logical drive | |||
will be used to hold data. | |||
This example assumes that you are installing on a hard disk that | |||
currently has one partition that takes up the entire disk. | |||
In this example, you will create: | |||
? A 30MB primary partition | |||
? A 12MB logical drive within the extended partition. | |||
This example does not involve the installation of the Boot | |||
Manager. | |||
1. Back up any data you want to save from the existing partition. | |||
(Use the BACKUP command from your existing operating | |||
system.) | |||
2. Insert the Installation diskette, restart your system, and follow | |||
the instructions on the screen. | |||
3. At the Installation Drive Selection screen, select option 2, | |||
Specify a different drive or partition. | |||
4. Delete the existing partition (which you have backed up): | |||
+ Copyright IBM Corp. 1991 77 | |||
a. Press Enter to display the Options menu. | |||
b. Select Delete Partition. | |||
5. Create the primary partition: | |||
a. Press Enter to display the Options menu. | |||
b. Select Create Partition. | |||
c. Type the size of the primary partition (in this example, 30) | |||
and press Enter. | |||
d. Select Primary Partition and press Enter. | |||
e. Select Create at Start of Free Space and press Enter. | |||
6. Create the logical drive for data: | |||
a. Highlight the line. Free Space | |||
b. Press Enter to display the Options menu. | |||
c. Select Create Partition. | |||
d. Type the size of the extended logical drive (in this | |||
example, 12) and press Enter. | |||
e. Select Extended Logical Drive and press Enter. | |||
f. Select Create at Start of Free Space and press Enter. | |||
7. Exit FDISK: | |||
a. Press F3. | |||
b. Select Save and Exit and press Enter. | |||
8. Continue with OS/2 installation until you see the OS/2 Setup | |||
and Installation screen. | |||
9. Format the logical drive: | |||
a. When the OS/2 Setup and Installation screen is displayed, | |||
select Select features and install. | |||
b. Specify any changes to the System Configuration screen. | |||
c. When the next OS/2 Setup and Installation screen is | |||
displayed, select Options from the menu bar. | |||
d. Select Format. | |||
e. Indicate which file system you want to use to format the | |||
logical drive. | |||
Note that you can format the logical drive for a file system | |||
that is different from the one with which you formatted the | |||
primary partition. For example, if the primary partition is | |||
formatted for the High Performance File System, you can | |||
format the logical partition for the File Allocation Table file | |||
78OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
system. This way, you can have both file systems installed | |||
on the hard disk. | |||
10. Finish the installation of the OS/2 Version 2.0 operating | |||
system. | |||
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 79 | |||
Example 2: Installing the Boot Manager, OS/2 2.0, and | |||
One Additional Operating System | |||
This example shows you how to set up a partition for the Boot | |||
Manager, a primary partition for DOS, and a logical drive for OS/2 | |||
2.0. | |||
This example assumes that you are installing on a hard disk that | |||
currently has one partition that takes up the entire disk. | |||
In this example, you will create: | |||
? A 4MB primary partition for DOS | |||
? A 30MB logical drive for OS/2 2.0. | |||
You will also install the Boot Manager in its own partition. | |||
1. Back up any data you want to save from the existing partition. | |||
(Use the BACKUP command from your existing operating | |||
system.) | |||
2. Insert the Installation diskette, restart your system, and follow | |||
the instructions on the screen. | |||
3. At the Installation Drive Selection screen, select option 2, | |||
Specify a different drive or partition. | |||
4. Delete the existing partition (which you have backed up): | |||
a. Press Enter to display the Options menu. | |||
b. Select Delete Partition. | |||
5. Install the Boot Manager partition: | |||
a. Press Enter to display the Options menu. | |||
b. Select Install Boot Manager. | |||
c. Select Create at Start of Free Space and press Enter. | |||
6. Create the DOS partition: | |||
a. Highlight the line. Free Space | |||
b. Select Create Partition. | |||
c. Type the size of the primary partition (in this example, 4) | |||
and press Enter. | |||
d. Select Primary Partition and press Enter. | |||
e. Select Create at Start of Free Space and press Enter. | |||
80OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
f. Press Enter to display the Options menu. | |||
g. Select Add to Boot Manager Menu. | |||
h. Type DOS and press Enter. | |||
7. Create the OS/2 Version 2.0 logical drive: | |||
a. Highlight the line. Free Space | |||
b. Press Enter to display the Options menu. | |||
c. Select Create Partition. | |||
d. Type the size of the extended logical drive (in this | |||
example, 30) and press Enter. | |||
e. Select Extended Logical Drive and press Enter. | |||
f. Select Create at Start of Free Space and press Enter. | |||
g. Press Enter to display the Options menu. | |||
h. Select Add to Boot Manager Menu. | |||
i. Type OS/2 2.0 and press Enter. | |||
8. Set up OS/2 Version 2.0 as the default: | |||
a. Highlight the line. OS/2 2.0 | |||
b. Press Enter to display the Options menu. | |||
c. Select Set startup values. | |||
d. Select Default. | |||
e. Press F3. | |||
9. Indicate which partition should be used for the OS/2 2.0 | |||
installation: | |||
a. Highlight the line. OS/2 2.0 | |||
b. Press Enter to display the Options menu. | |||
c. Select Set installable. | |||
10. Exit FDISK: | |||
a. Press F3 to exit FDISK. | |||
b. Select Save and Exit and press Enter. | |||
11. Finish the installation of the OS/2 Version 2.0 operating | |||
system. | |||
12. When OS/2 installation is completed, insert the DOS | |||
installation diskette. Then, press and hold Ctrl+Alt, and press | |||
Del to restart the system. | |||
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 81 | |||
Example 3: Installing the Boot Manager, OS/2 2.0, and | |||
Two Additional Operating Systems | |||
This example shows you how to set up a partition for the Boot | |||
Manager, a primary partition for DOS, a primary partition for OS/2 | |||
Version 1.3, and a logical drive for OS/2 Version 2.0. | |||
This example assumes that you are installing on a hard disk that | |||
currently has one partition that takes up the entire disk. | |||
In this example, you will create: | |||
? A 4MB primary partition for DOS | |||
? A 20MB primary partition for OS/2 Version 1.3 | |||
? | |||
A 30MB logical drive for OS/2 Version 2.0. | |||
You will also install the Boot Manager in its own partition. | |||
1. Back up any data you want to save from the existing partition. | |||
(Use the BACKUP command from your existing operating | |||
system.) | |||
2. Insert the Installation diskette, restart your system, and follow | |||
the instructions on the screen. | |||
3. At the Installation Drive Selection screen, select option 2, | |||
Specify a different drive or partition. | |||
4. Delete the existing partition (which you have backed up): | |||
a. Press Enter to display the Options menu. | |||
b. Select Delete Partition. | |||
5. Install the Boot Manager partition: | |||
a. Press Enter to display the Options menu. | |||
b. Select Install Boot Manager. | |||
c. Select Create at Start of Free Space and press Enter. | |||
6. Create the DOS partition: | |||
a. Highlight the line. Free Space | |||
b. Select Create Partition. | |||
c. Type the size of the primary partition (in this example, 4) | |||
and press Enter. | |||
d. Select Primary Partition and press Enter. | |||
82OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
e. Select Create at Start of Free Space and press Enter. | |||
f. Press Enter to display the Options menu. | |||
g. Select Add to Boot Manager Menu. | |||
h. Type DOS and press Enter. | |||
7. Create the OS/2 Version 1.3 partition: | |||
a. Highlight the line. Free Space | |||
b. Select Create Partition. | |||
c. Type the size of the primary partition (20) and press Enter. | |||
d. Select Primary Partition and press Enter. | |||
e. Select Create at Start of Free Space and press Enter. | |||
f. Press Enter to display the Options menu. | |||
g. Select Add to Boot Manager Menu. | |||
h. Type OS2 1.3 and press Enter. | |||
8. Create the OS/2 2.0 logical drive: | |||
a. Highlight the line. Free Space | |||
b. Press Enter to display the Options menu. | |||
c. Select Create Partition. | |||
d. Type the size of the extended logical drive (in this | |||
example, 30) and press Enter. | |||
e. Select Extended Logical Drive and press Enter. | |||
f. Select Create at Start of Free Space and press Enter. | |||
g. Press Enter to display the Options menu. | |||
h. Select Add to Boot Manager Menu. | |||
i. Type OS/2 2.0 and press Enter. | |||
9. Set up OS/2 Version 2.0 as the default: | |||
a. Highlight the line. OS/2 2.0 | |||
b. Press Enter to display the Options menu. | |||
c. Select Set startup values. | |||
d. Select Default. | |||
e. Press F3. | |||
10. Indicate which partition should be used for the OS/2 2.0 | |||
installation: | |||
a. Highlight the line. OS/2 2.0 | |||
b. Press Enter to display the Options menu. | |||
c. Select Set installable. | |||
11. Exit FDISK and continue with installation: | |||
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 83 | |||
a. Press F3 to exit FDISK. | |||
b. Select Save and Exit and press Enter. | |||
c. Continue with OS/2 installation. | |||
12. Install DOS | |||
a. Insert the DOS installation diskette. | |||
b. Press the Ctrl and Alt keys, and then press Del to restart | |||
the system. | |||
13. Restart the system by pressing the Ctrl and Alt keys and then | |||
pressing the Del key. | |||
14. Select OS/2 2.0 from the Boot Manager startup menu. | |||
15. Make the OS/2 1.3 partition active. | |||
a. Select OS/2 System. | |||
b. Select Command Prompts. | |||
c. Select OS/2 Window. | |||
d. Type: | |||
fdisk | |||
and press Enter. | |||
e. Highlight the line. OS2 1.3 | |||
f. Press Enter to display the Options menu. | |||
g. Select Set Installable. | |||
h. Press F3 to exit. | |||
16. Install OS/2 Version 1.3 | |||
a. Insert the OS/2 Version 1.3 installation diskette. | |||
b. Press the Ctrl and Alt keys, and then press the Del key to | |||
restart the system. | |||
17. Make the Boot Manager Startable: | |||
a. With OS/2 1.3 running, select Manage Partitions from the | |||
Utilities group. | |||
b. Highlight the Boot Manager line. | |||
c. Select Options. | |||
d. Select Startable. | |||
18. Restart the system to see the Boot Manager startup menu. | |||
84OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Example 4: Installing Boot Manager without | |||
Repartitioning the Entire Hard Disk | |||
This example shows you how to install the Boot Manager and | |||
install OS/2 2.0 without repartitioning the entire hard disk. | |||
This example assumes that your current hard disk setup has a | |||
primary partition (with DOS Version 4.0) and an extended partition. | |||
In this example, you will preserve the primary partition that | |||
contains DOS Version 4.0. You will delete the extended partition to | |||
make room for OS/2 2.0 and the Boot Manager. In this example, | |||
you will put the Boot Manager partition at the end of the hard disk. | |||
In this example, you will create: | |||
? A 30MB logical drive for OS/2 2.0 | |||
? A 10MB logical drive for data. | |||
You will also install the Boot Manager in its own partition. | |||
1. Back up any data you want to save from the existing extended | |||
partition. (Use the BACKUP command from your existing | |||
operating system.) | |||
2. Insert the Installation diskette, restart your system, and follow | |||
the instructions on the screen. | |||
3. At the Installation Drive Selection screen, select option 2, | |||
Specify a different drive or partition. | |||
4. Delete the existing extended partition (which you have backed | |||
up): | |||
a. Highlight the line that contains information about the | |||
extended partition. | |||
b. Press Enter to display the Options menu. | |||
c. Select Delete Partition. | |||
5. Install the Boot Manager partition: | |||
a. Press Enter to display the Options menu. | |||
b. Select Install Boot Manager. | |||
c. Select Create at End of Free Space and press Enter. | |||
6. Create the OS/2 2.0 logical drive: | |||
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 85 | |||
a. Highlight the line. Free Space | |||
b. Press Enter to display the Options menu. | |||
c. Select Create Partition. | |||
d. Type the size of the extended logical drive (in this | |||
example, 30) and press Enter. | |||
e. Select Extended Logical Drive and press Enter. | |||
f. Select Create at Start of Free Space and press Enter. | |||
g. Press Enter to display the Options menu. | |||
h. Select Add to Boot Manager menu. | |||
i. Type OS/2 2.0 and press Enter. | |||
7. Create the logical drive for data: | |||
a. Highlight the line. Free Space | |||
b. Press Enter to display the Options menu. | |||
c. Select Create Partition. | |||
d. Type the size of the extended logical drive (in this | |||
example, 10) and press Enter. | |||
e. Select Extended Logical Drive and press Enter. | |||
f. Select Create at Start of Free Space and press Enter. | |||
8. Set up OS/2 2.0 as the default: | |||
a. Highlight the line. OS/2 2.0 | |||
b. Press Enter to display the Options menu. | |||
c. Select Set startup values. | |||
d. Select Default. | |||
e. Press F3. | |||
9. Indicate which partition should be used for the OS/2 2.0 | |||
installation: | |||
a. Highlight the line. OS/2 2.0 | |||
b. Press Enter to display the Options menu. | |||
c. Select Set installable. | |||
10. Add a name for the DOS partition to the Boot Manager startup | |||
menu: | |||
a. Highlight the line that contains information about the DOS | |||
partition. | |||
b. Press Enter to display the Options menu. | |||
c. Select Add to Boot Manager menu. | |||
d. Type DOS and press Enter. | |||
11. Exit FDISK: | |||
86OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
a. Press F3 to exit FDISK. | |||
b. Select Save and Exit and press Enter. | |||
12. Continue with OS/2 installation until you see the OS/2 Setup | |||
and Installation screen. | |||
13. Format the logical drive: | |||
a. When the OS/2 Setup and Installation screen is displayed, | |||
select Select features and install. | |||
b. Specify any changes to the System Configuration screen. | |||
c. When the next OS/2 Setup and Installation screen is | |||
displayed, select Options from the menu bar. | |||
d. Select Format. | |||
e. Indicate which file system you want to use to format the | |||
logical drive. | |||
14. Finish the installation of the OS/2 Version 2.0 operating | |||
system. | |||
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 87 | |||
88OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Index | |||
Boot Manager partition | |||
A creating 41 | |||
Add to Boot Manager Menu placement of 31 | |||
choice 45 Boot Manager startup menu | |||
adding OS/2 to a DOS system 17 | |||
configuring 48 | |||
after installation, adding example of 26 | |||
features 67 | |||
AIX, adding name to Boot Manager | |||
startup menu 57 C | |||
AIX, note about installing 42 caching 69 | |||
Assign C: Partition choice 45 CD-ROM, installing from 65 | |||
AUTOEXEC.BAT file Change Partition Name choice 45 | |||
creating or modifying for Dual changing partition sizes 38 | |||
Boot 21 CHKDSK command, recovering | |||
migrating from a previous from errors on the hard disk 74 | |||
version 14 colors, changing screen 67 | |||
modifying to load DOS from Command Reference | |||
within OS/2 32 adding after installation 70 | |||
choosing to install 14 | |||
communication port 69 | |||
B | |||
? configuration options 67 | |||
basic installation 9 16 CONFIG.SYS file | |||
bit-map fonts 67 creating or modifying for Dual | |||
bitmaps, adding additional 69 Boot 21 | |||
BOOT command 24 migrating from a previous | |||
Boot Manager | |||
version 14 | |||
example of setting up three modifying to load DOS from | |||
operating systems 82 within OS/2 32 | |||
example of setting up two recovering 71 | |||
operating systems 80 considerations for installing | |||
FDISK utility 39 | |||
multiple operating systems 4 | |||
hard disk architecture 30 Create Partitions choice 45 | |||
hard disk management 30 creating | |||
installation of 34partitions and logical drives 42 | |||
installation on existing the Boot Manager partition 41 | |||
system 37 | |||
the OS/2 partition 47 | |||
installation on new systems 36 creating or modifying | |||
startup menu time, setting 50 AUTOEXEC.BAT and | |||
system setup CONFIG.SYS 21 | |||
recommendations 31 | |||
+ Copyright IBM Corp. 1991 89 | |||
customization information, example of (continued) | |||
migrating 14 formatting a data partition 77 | |||
customizing the system 67 installing Boot Manager with | |||
three operating systems 82 | |||
installing Boot Manager with two | |||
D | |||
operating systems 80 | |||
date, changing 67 installing Boot Manager without | |||
default operating system, setting repartitioning the entire | |||
(for Boot Manager) 50 disk 85 | |||
default printer, choosing 15 installing DOS and OS/2 in | |||
Delete Partition choice 46 | |||
separate partitions 80 | |||
deleting partitions 39 installing multiple partitions 80 | |||
diagnostic aids 69 installing three operating | |||
directory structure, for Dual systems 82 | |||
Boot 19 setting up two partitions 77 | |||
documentation, online | |||
extended partition 27 | |||
adding after installation 70 | |||
choosing during installation 14 | |||
DOS F | |||
Dual Boot restriction 18 failures, system 71 | |||
DOS programs FDISK | |||
installing in a Dual Boot examples of using 77 | |||
setup 22 screen 39 | |||
migrating 14 FDISKPM, description of 49 | |||
DOS 5.00 Upgrade, note about file systems, installing both 78 | |||
installing 32 fonts, adding after installation 67 | |||
DOS 5.0, note about installing 56 formatting a logical drive 14 | |||
drive mapping 29 | |||
Dual Boot | |||
copying COMMAND.COM in a H | |||
Boot Manager hard disk architecture 30 | |||
hard disk management 30 | |||
environment 57 | |||
Dual Boot feature high performance file system | |||
requirements 19 Dual Boot restriction 18 | |||
restrictions 18 | |||
starting 24 | |||
I | |||
increasing partition size 38 | |||
E INI files, recovering 72 | |||
error messages, installation 75 Install Boot Manager choice 45 | |||
example of installable, marking a partition | |||
adding partitions to an existing as 46 | |||
hard disk 85 | |||
90OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
installation modem 69 | |||
after, adding features 67 more than one operating system, | |||
basic 9?6 installing 25 | |||
installation, redirecting 59 mouse | |||
installing customizing use of 67 | |||
AIX, note about 42tutorial on using 12 | |||
Boot Manager without multiple operating systems | |||
repartitioning the entire considerations for installing 4 | |||
disk 85 installing 25 | |||
both file systems 78 | |||
from a drive other than A 59 | |||
more than one operating O | |||
system 4 online documentation | |||
multiple partitions, example adding after installation 70 | |||
of 80, 82 choosing during installation 14 | |||
online help | |||
OS/2 on a DOS system 17 | |||
OS/2 only 9 for loading DOS from | |||
other operating systems 54 diskette 7 | |||
with a response file 59 problem determination 71 | |||
interface, replacing 67 operating systems | |||
installing additional 54 | |||
recommended partition sizes | |||
L for 43 | |||
LAN installation 59 optional bitmaps 69 | |||
logical drive optional utilities 68 | |||
description of 27OS/2 Tutorial | |||
formatting during adding after installation 70 | |||
installation 14 choosing to install 14 | |||
logo screen 10, 23OS/2 1.3, note about installing 56 | |||
outline fonts 67 | |||
M | |||
Make Startable choice 46 P | |||
marking a partition as partition | |||
installation 46 accepting the default 10 | |||
messages, installation 75 adding a second 11 | |||
metacharacters 69 partition size and considerations, | |||
migrating planning table 43 | |||
CONFIG.SYS and partitions | |||
AUTOEXEC.BAT files 14 defining 39 | |||
customization information 14 restriction on number of 27 | |||
DOS programs 14 setting up 39 | |||
Windows programs 14 | |||
Index 91 | |||
Partitions Too Small warning 38 S | |||
planning the Boot Manager | |||
setup 31 screen colors, changing 67 | |||
plotter, utilities 69 serial printer or plotter 69 | |||
PM fonts 67 Set Installable choice 46 | |||
Set Startup Values choice 45 | |||
primary drive, changing 7 setting a partition installable 46 | |||
primary partitions | |||
restriction on number of 27 setting the Boot Manager default | |||
specifying which should be used operating system 50 | |||
for installation 54 setting up | |||
partitions and logical drives 42 | |||
printer, choosing the default 15 two partitions, example of 77 | |||
problem determination 69, 71 | |||
problem information 71 sharing printer resources 69 | |||
shell, replacing 67 | |||
starting the Dual Boot feature 24 | |||
Q System Configuration folder 67 | |||
system problems, diagnosing 71 | |||
Quick Reference | |||
description of x | |||
installing with 3 | |||
T | |||
technical coordinator 69 | |||
R timeout values, Boot Manager 50 | |||
time, changing 67 | |||
recommendations for a Boot | |||
Manager setup 31 trouble shooting 71 | |||
recommended partition sizes 43 Tutorial | |||
reconfigurable diskette drives 7 adding after installation 70 | |||
recovering choosing to install 14 | |||
from errors on the hard disk 74 | |||
from system failures 71?4 | |||
the CONFIG.SYS file 71 U | |||
user and system INI files 72 Upgrade, DOS 5.00 32 | |||
redirecting installation 59 upgrading to DOS 5.00 before | |||
installing Boot Manager 32 | |||
Remove from Boot Manager Menu user INI files, recovering 72 | |||
choice 45 | |||
replacing the user interface 67 user interface, replacing 67 | |||
response file installation 59 utilities, system 68 | |||
REXX information | |||
adding after installation 70 W | |||
choosing to install 14 window borders, changing 67 | |||
REXX program 69 | |||
Windows programs | |||
installing in a Dual Boot | |||
setup 22 | |||
92OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY | |||
Windows programs (continued) | |||
migrating 14 | |||
Index 93 | |||
� | |||
</pre> | |||
</div></div> | |||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
OVER6167.DOC | |||
<div class="mw-collapsible-content"> | |||
<pre width="87"> | |||
IBM OS/2 32-bit | |||
Overview | |||
Pre-Release Copy | |||
Document Number 84F8465 | |||
October 15, 1991 | |||
First Edition October 1991 < * | |||
The following paragraph does not apply to the United Kingdom or any | |||
country where such provisions are inconsistent with local law: | |||
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS | |||
PUBLICATION 嗀S IS?WITHOUT WARRANTY OF ANY KIND, EITHER | |||
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED | |||
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR | |||
PURPOSE. Some states do not allow disclaimer of express or implied | |||
warranties in certain transactions, therefore, this statement may not apply | |||
to you. | |||
This publication could include technical inaccuracies or typographical | |||
errors. Changes are periodically made to the information herein; these | |||
changes will be incorporated in new editions of the publication. IBM may | |||
make improvements and/or changes in the product(s) and/or the | |||
program(s) described in this publication at any time. | |||
It is possible that this publication may contain reference to, or information | |||
about, IBM products (machines and programs), programming, or services | |||
that are not announced in your country. Such references or information | |||
must not be construed to mean that IBM intends to announce such IBM | |||
products, programming, or services in your country. | |||
Requests for technical information about IBM products should be made to | |||
your IBM Authorized Dealer or your IBM Marketing Representative. | |||
IBM may have patents or pending patent applications covering subject | |||
matter in this document. The furnishing of this document does not give | |||
you any license to these patents. You can send license inquiries, in | |||
writing, to the IBM Director of Commercial Relations, IBM Corporation, | |||
Purchase, NY 10577. | |||
+ Copyright International Business Machines Corporation 1991. All rights | |||
reserved. | |||
Note to U.S. Government Users ?Documentation related to restricted | |||
rights ?Use, duplication or disclosure is subject to restrictions set forth | |||
in GSA ADP Schedule Contract with IBM Corp. | |||
Contents | |||
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v | |||
About This Book ..... . . . . . . . . . . . . . . . . . . . . . . . vii | |||
Using This Book ..... . . . . . . . . . . . . . . . . . . . . . . . vii | |||
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . vii | |||
Changes from Previous Versions ......... . . . . . . . . . . x | |||
Chapter 1. Introducing OS/2 2.0 ......... . . . . . . . . . . 1 | |||
Introducing Folders and Objects ......... . . . . . . . . . . 2 | |||
Managing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . .5. | |||
Selecting Objects . . . . . . . . . . . . . . . . . . . . . . . . . .6. | |||
Using Pop-up Menus. . . ..... . . . . . . . . . . . . . . . . . 7 | |||
Working Directly with Objects. . . . ....... . . . . . . . . 8 | |||
Moving Objects . . . . . . . . . . . . . . . . . . . . . . . . . . .9. | |||
Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 10 | |||
Printing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 | |||
Deleting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 12 | |||
Arranging Objects . . . . . . . . . . . . . . . . . . . . . . . .13. | |||
Opening Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 14 | |||
Selecting Window Parts ....... . . . . . . . . . . . . . . . 15 | |||
Using the Window.List . . . ..... . . . . . . . . . . . . . . 16 | |||
Sizing a Window ..... . . . . . . . . . . . . . . . . . . . . . 17 | |||
Moving a Window . . . ..... . . . . . . . . . . . . . . . . . . 18 | |||
Introducing Online Information ......... . . . . . . . . . . 21 | |||
Using the Master Index ....... . . . . . . . . . . . . . . . 22 | |||
Searching for a.Topic. ..... . . . . . . . . . . . . . . . 23 | |||
Printing a Master Index Entry ......... . . . . . . . . 24 | |||
Using Related Information. . . . ....... . . . . . . . . 25 | |||
Using the Information Folder. . . . ....... . . . . . . . . 26 | |||
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 | |||
Displaying Help for an Object.or Folder. ......... 28 | |||
Displaying Help for a Pop-up Menu Choice. . . . . . . . . 28 | |||
Displaying Help for a Highlighted Word.or Phrase . . . 28 | |||
Displaying Help for OS/2 Messages. . . . . ........ 29 | |||
Displaying Help for OS/2 Commands. . . . . ...... . 30 | |||
Chapter 2. Features . . . . . . . . . . . . . . . . . . . . . . . . . . 33 | |||
Installation of OS/2.2.0. . ... . . . ... . . . . . . . . . . . . 33 | |||
+ Copyright IBM Corp. 1991 iii | |||
Multitasking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 | |||
DOS Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 | |||
Multiple Virtual DOS Machines . . . . . ......... . . . . 36 | |||
DOS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 | |||
Dual Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 | |||
Microsoft Windows Compatibility. . . . ....... . . . . . . . 37 | |||
Boot Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 | |||
Special Needs Support. . . ..... . . . . . . . . . . . . . . . . 37 | |||
Lockup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 | |||
High Performance File System. . . . ....... . . . . . . . . 40 | |||
Extended Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 40 | |||
OS/2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 | |||
Procedures Language/2.REXX . ..... . . . . . . . . . . . . . 41 | |||
System Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 | |||
Games Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 | |||
Productivity Programs . . . . . . . . . . . . . . . . . . . . . . . . 44 | |||
Appendix A. Keyboard and Mouse Use ......... . . . . . 47 | |||
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 | |||
ivIBM OS/2 32-bit Overview Pre-Release Copy | |||
Notices | |||
References in this publication to IBM products, programs, or | |||
services do not imply that IBM intends to make these available in | |||
all countries in which IBM operates. Any reference to an IBM | |||
product, program or service is not intended to state or imply that | |||
only IBM's product, program, or service may be used. Any | |||
functionally equivalent product, program, or service that does not | |||
infringe any of IBM's intellectual property rights or other legally | |||
protectible rights may be used instead of the IBM product, | |||
program, or service. Evaluation and verification of operation in | |||
conjunction with other products, programs, or services, except | |||
those expressly designated by IBM, are the user's responsibility. | |||
The following terms, denoted by a single asterisk (*) in this | |||
publication, are trademarks of the IBM Corporation in the United | |||
States and/or other countries: | |||
AIX IBM Operating System/2 | |||
OS/2 Presentation SAA | |||
Manager | |||
Systems Application | |||
Architecture | |||
The following terms, denoted by a double asterisk (**) are | |||
trademarks of other companies: | |||
AST AST Corporation | |||
Intel386 Intel Corporation | |||
Intel486 Intel Corporation | |||
Intel Intel Corporation | |||
Lotus Lotus Corporation | |||
Microsoft Microsoft Corporation | |||
Windows Microsoft Corporation | |||
+ Copyright IBM Corp. 1991 v | |||
viIBM OS/2 32-bit Overview Pre-Release Copy | |||
About This Book | |||
This book introduces you to IBM * Operating System/2 * (OS/2 * ) | |||
Version 2.00. It describes the graphical appearance of the | |||
operating system, the features of the operating system, and | |||
explains how to use the online information. It also introduces you | |||
to some important operating system concepts and describes the | |||
differences between this version and previous versions of the | |||
operating system. | |||
This book describes how to complete most tasks and actions using | |||
a mouse. If you are using a keyboard, see Appendix A, | |||
﨣eyboard and Mouse Use?on page 47 for information on how to | |||
most efficiently use the keyboard keys to perform tasks and | |||
actions. | |||
During installation, you are asked if you want to learn how to use | |||
the mouse. If this is the first time you are using a mouse, choose | |||
this option. After you install the operating system, you can learn | |||
more about using a mouse in the OS/2 Tutorial. | |||
Using This Book | |||
Everyone who will be using OS/2 Version 2.00 should read this | |||
book. | |||
Keep this book as a reference. | |||
Related Information | |||
The following describes the documentation and online information | |||
that comes with the product. Online describes information that | |||
can be displayed on your screen. | |||
* Trademark of the IBM Corporation | |||
+ Copyright IBM Corp. 1991 vii | |||
Quick Start | |||
This card provides a brief, limited set of instructions on | |||
how to install the operating system and quickly become | |||
productive. If you want to install the entire operating | |||
system (rather than select only certain features), use | |||
this card. If you want more detailed information about | |||
installing the operating system, use the Installation | |||
Guide. | |||
OS/2 Installation Guide | |||
This book describes how to prepare for and install the | |||
operating system. It also provides information about | |||
installing more than one operating system on your | |||
computer. | |||
OS/2 Tutorial | |||
This online, interactive program shows you the basics | |||
of the operating system. The tutorial starts | |||
automatically after you install the operating system. | |||
Master Index | |||
This online, alphabetic list contains most of the | |||
information you need to use OS/2 2.0. | |||
Glossary This online, alphabetic list contains computer and | |||
operating system terms and definitions. | |||
OS/2 Command Reference | |||
This online information describes how to use OS/2 | |||
commands. | |||
REXX Information | |||
This online information describes how to use the REXX | |||
procedure language. | |||
viii IBM OS/2 32-bit Overview Pre-Release Copy | |||
The following publications will be available and can be ordered | |||
separately: | |||
IBM Operating System/2 Keyboards and Code Pages | |||
This book contains reference information for those who | |||
use code-page switching to provide support for files that | |||
are received from or sent to other countries. | |||
OS/2 Version 2.00 Volume 1: Control Program, GG24-3730 | |||
This book provides detailed information about the | |||
Control Program component of the OS/2 Version 2.00 | |||
operating system. The book describes memory and | |||
task management, debugging support, and enhanced | |||
application programming interfaces. | |||
It also describes installation and national language | |||
considerations, and discusses enhanced hardware | |||
support. | |||
OS/2 Version 2.00 Volume 2: DOS and Windows Environment, | |||
GG24-3731 | |||
This book provides detailed information about the | |||
Multiple DOS Machines feature, and support for | |||
Microsoft ** Windows ** programs. The book describes | |||
the architecture of Multiple Virtual DOS Machines, 8086 | |||
emulation, device drivers, extended memory support, | |||
DOS settings, and using specific versions of DOS. | |||
It also provides technical information about using | |||
Microsoft Windows programs, and DOS Protect Mode | |||
Interface (DPMI). | |||
OS/2 Version 2.00 Volume 3: Presentation Manager, GG24-3732 | |||
This book provides detailed information about the | |||
* | |||
Presentation Manager component of OS/2 Version 2.00. | |||
The book introduces the Presentation Manager, and | |||
describes the enhanced graphical appearance of the | |||
operating system, and enhanced help facilities. | |||
** Trademark of the Microsoft Corporation | |||
* Trademark of the IBM Corporation | |||
About This Book ix | |||
It discusses programming considerations for 32-bit or a | |||
mix of both 16- and 32-bit code application | |||
development, and when migrating existing 16-bit | |||
applications. It also describes support for national | |||
languages and double-byte character sets. | |||
Changes from Previous Versions | |||
The operating system has a changed look and many new features. | |||
The Desktop Manager, File Manager, Print Manager, and Control | |||
Panel are replaced by folders and objects. The Task List is now | |||
called the Window List. | |||
Although the appearance of the operating system is changed, you | |||
can still use your existing programs with this version. To save | |||
your existing programs in a folder called OS/2 Programs, be sure | |||
you do not format your hard disk before or during installation of | |||
OS/2 Version 2.00. | |||
The following describes the new features in OS/2 Version 2.00. | |||
Enhanced DOS compatibility | |||
The Multiple Virtual DOS Machines feature removes the | |||
restriction of running only one DOS program at a time | |||
in DOS mode. | |||
The DOS Settings feature helps optimize performance | |||
of DOS programs. | |||
Previous versions of the operating system did not | |||
support DOS timing-dependent programs, such as | |||
communications and real-time programs. Many of | |||
these programs now run in OS/2 Version 2.00. | |||
Microsoft Windows Compatibility | |||
Microsoft Windows programs now run in OS/2 Version | |||
2.00. | |||
Boot Manager | |||
The Boot Manager feature provides support for | |||
installation of multiple operating systems. | |||
xIBM OS/2 32-bit Overview Pre-Release Copy | |||
Special Needs Support | |||
The Special Needs feature provides support for | |||
changing the way the keyboard keys work. | |||
Security Support | |||
The Lockup feature provides protection for information | |||
in your computer. | |||
Additional Programs | |||
Games and Productivity programs have been added. | |||
Use these programs to, for example, edit files, chart | |||
graphs, create to-do lists, or play games. | |||
About This Book xi | |||
xiiIBM OS/2 32-bit Overview Pre-Release Copy | |||
Chapter 1. Introducing OS/2 2.0 | |||
Welcome to OS/2 2.0. | |||
The OS/2 operating system transforms your computer into a | |||
powerful tool that helps you manage your work. It takes full | |||
advantage of Intel386 ** and Intel486 ** technology. Increased | |||
performance made possible by this technology means 32-bit and | |||
16-bit programs run faster. | |||
OS/2 2.0 supports multitasking (running more than one program at | |||
once), installation of other operating systems, and compatibility | |||
with existing programs that run under DOS and Microsoft ** | |||
** | |||
Windows . You can organize programs, communicate with other | |||
computers, write and print letters, and play games. | |||
A lockup feature helps protect important information. A special | |||
needs feature is available, if you need to change the way keyboard | |||
keys work because of manual dexterity preferences. | |||
The OS/2 operating system features a graphical appearance. | |||
Whether you are writing a letter, using a printer, or playing a | |||
game, you work with objects that graphically represent the letter, | |||
printer, or game. | |||
The OS/2 operating system is your lectronic workplace.? | |||
OS/2 2.0 also features online information. Whether you need help, | |||
want to learn about the operating system, need a term defined, or | |||
want to explore topics related to concepts, commands, or REXX, | |||
the information is online. | |||
The online information is your lectronic library.? | |||
This chapter describes folders and objects, explains how to use | |||
the online information, and introduces some operating system | |||
** Intel386 and Intel486 are trademarks of the Intel Corporation, and Microsoft and | |||
Windows are trademarks of the Microsoft Corporation. | |||
+ Copyright IBM Corp. 1991 1 | |||
concepts. Chapter 2, 﨔eatures?on page 33 describes other | |||
operating system features. | |||
Introducing Folders and Objects | |||
The OS/2 operating system is like your real workplace, except the | |||
things you work with are arranged on your computer screen, not | |||
on your desk or in your office. For example, in your real | |||
workplace, you might work with a letter, an appointment book, or a | |||
printer. With the OS/2 operating system, you work with an object | |||
that represents the letter, appointment book, or printer. | |||
An object that contains other objects is a folder. You can use | |||
folders to organize objects. For example, in your real workplace, | |||
you probably organize the things you frequently use to do your | |||
work in a convenient place. With the OS/2 operating system, you | |||
can organize the objects you frequently work with in a folder. | |||
Conceptual art | |||
2IBM OS/2 32-bit Overview Pre-Release Copy | |||
Folders and objects appear on your screen as miniature pictures | |||
that look similar to real things in your workplace. For example, if | |||
you install a printer, your printer object appears as a miniature | |||
picture of a printer. A miniature picture that represents a folder or | |||
an object is an icon. | |||
When you finish installing OS/2, the OS/2 Tutorial and the icons | |||
that represent the folders and objects that come with OS/2 appear | |||
on the screen, like this: | |||
Screen Capture of shell | |||
Note: The tutorial appears automatically only the first time you | |||
use the operating system. | |||
The tutorial has information about using a mouse and presents | |||
some operating system concepts. You also get a chance to | |||
practice using many of the features. When you complete the | |||
tutorial, you can start using the folders and objects that come with | |||
OS/2 2.0. | |||
There is one folder that comes with the OS/2 operating system that | |||
is unique, called the Desktop folder. It fills the entire screen, and | |||
contains all other folders and objects. | |||
Chapter 1. Introducing OS/2 2.0 3 | |||
The following list describes the contents of the other folders or | |||
objects. | |||
OS/2 System | |||
This folder contains other folders and objects that: | |||
? Show drive locations | |||
? Contain startup instructions | |||
? Help you customize the system | |||
? | |||
Contain games and productivity programs | |||
? Are used to select OS/2 or DOS command prompts. | |||
Master Index | |||
This object contains an alphabetic list of online topics | |||
related to understanding and using the operating | |||
system. | |||
For example, use the Master Index to find information | |||
about how to install programs or copy, move, print, and | |||
arrange objects. | |||
Information | |||
This folder contains objects that represent the: | |||
? Tutorial, which has information about using a | |||
mouse and how to use the operating system | |||
? Glossary, which lists terms and their definitions | |||
? OS/2 Command Reference, which describes | |||
commands and their usage | |||
? REXX Information, which describes using the REXX | |||
procedures language. | |||
Shredder This object is used to delete objects. | |||
Templates | |||
This folder contains templates (blank forms) for objects. | |||
Use the templates to create OS/2 or DOS full-screen or | |||
window sessions, or data, program, device, or | |||
installation objects. | |||
4IBM OS/2 32-bit Overview Pre-Release Copy | |||
During installation, you will make choices about the hardware and | |||
software you are using. Depending on the choices you make, the | |||
following folders or objects appear in the Desktop folder. | |||
Network This folder contains other folders and objects that | |||
represent a Local Area Network (LAN). | |||
Printer This object represents a printer. | |||
DOS Programs | |||
This folder contains programs previously installed using | |||
DOS. | |||
Microsoft Windows Programs | |||
This folder contains programs previously installed using | |||
Microsoft Windows. | |||
OS/2 Programs | |||
This folder contains programs previously installed using | |||
earlier versions of the OS/2 operating system. | |||
Note: If you format the hard disk before or during installation, any | |||
programs previously installed using DOS, Microsoft | |||
Windows, or an earlier version of the OS/2 operating | |||
system are not saved in a folder. | |||
Managing Objects | |||
You can manage objects in a way that is similar to the way you | |||
already manage your work. For example, during your work day, | |||
you might select letters or file folders you need to work with, | |||
arrange your work in order of importance, or copy letters at a | |||
copier. | |||
With objects, you can do the same kinds of tasks. You can select, | |||
arrange, or copy objects. In addition, you can open, move, | |||
discard, or print objects. | |||
Chapter 1. Introducing OS/2 2.0 5 | |||
Selecting Objects | |||
You must select (choose) an object before you can perform an | |||
action on it. This is similar to selecting what letters you will write | |||
or what files you will work with that day. For example, if you want | |||
to print or copy an object, you first select it. Then, you select the | |||
appropriate action on the pop-up menu (print or copy) that you | |||
want to apply to the selected object. | |||
To select an object: | |||
1. Move the mouse pointer to the object. | |||
2. Press the left mouse button (mouse button 1) once. | |||
(When you select an object, a shaded box appears around the | |||
object.) | |||
Screen Capture - Selected object | |||
Once you select an object, there are two ways to perform an | |||
action on the object: | |||
? Select the action from a pop-up menu. (A pop-up menu lists | |||
actions that can be applied to the object). | |||
? Perform the action directly on the object. | |||
6IBM OS/2 32-bit Overview Pre-Release Copy | |||
Using Pop-up Menus | |||
To display the pop-up menu for the selected object, move the | |||
mouse pointer to the object; then press the right mouse button | |||
(mouse button 2) once. | |||
Once the pop-up menu appears, you can select a choice from it. A | |||
typical pop-up menu for an object might look like this: | |||
Screen Capture - Typical menu for object | |||
To select a choice: | |||
1. Move the mouse pointer to the choice. | |||
2. Press the left mouse button (mouse button 1) once. | |||
Sometimes one or more choices on the menu have additional | |||
choices available. If additional choices are available, an arrow | |||
appears to the right of the pop-up menu choice. | |||
To display the additional choices: | |||
1. Move the mouse pointer to the arrow. | |||
2. Press the left mouse button (mouse button 1) once. | |||
Chapter 1. Introducing OS/2 2.0 7 | |||
Working Directly with Objects | |||
You have already read about how to select an object, and then | |||
how to apply an action to that object by selecting a choice on a | |||
pop-up menu. You can also directly manage objects. Generally, | |||
this means that without using a pop-up menu you can perform | |||
most actions directly on an object. | |||
The following list shows some of the terms associated with | |||
performing an action directly on an object. | |||
Click Press the left mouse button (mouse button 1) once. | |||
Double-click | |||
Press the left mouse button (mouse button 1) twice. | |||
Drag Move the mouse pointer to the object. Then, press and | |||
hold down a mouse button (either 1 or 2, depending on | |||
the action being performed) while moving the mouse | |||
pointer across the screen. | |||
As you move the mouse pointer, the object moves | |||
along with it. | |||
In addition to these actions, some actions must be done using both | |||
the keyboard and the mouse. When performing these actions, the | |||
key you press and hold down changes the way the basic mouse | |||
operation works. For example, when you copy an object, you | |||
press and hold down the Ctrl key and drag the object. Holding | |||
down the Ctrl key tells the operating system to copy the object, not | |||
move it. | |||
8IBM OS/2 32-bit Overview Pre-Release Copy | |||
Moving Objects | |||
You can move an object to another object. The object you move | |||
no longer appears in the previous location. This is similar to | |||
moving a letter from one file folder to another or moving a letter | |||
from your desk to a file cabinet. | |||
Conceptual Art | |||
To move an object, you do the following: | |||
1. Move the mouse pointer to the object. | |||
2. Press and hold down mouse button 2 while dragging the object | |||
to another object. | |||
3. When the object is over the object you want to move it to, | |||
release mouse button 2. | |||
Chapter 1. Introducing OS/2 2.0 9 | |||
Copying Objects | |||
You can copy an object to another object. A duplicate of the | |||
object is created and placed in the other object. This is similar to | |||
making a copy of a letter on a copier and then placing the original | |||
in one file folder and the copy in another. | |||
Conceptual Art | |||
To copy an object, you must use both the keyboard and the | |||
mouse, as follows: | |||
1. Move the mouse pointer to the object. | |||
2. Press and hold down mouse button 2. | |||
3. Press and hold down the Ctrl key. | |||
4. Drag the object to the object where you want a copy. | |||
5. When the object is over the object you want a copy to appear | |||
in, release mouse button 2. | |||
6. Release the Ctrl key. | |||
10IBM OS/2 32-bit Overview Pre-Release Copy | |||
Printing Objects | |||
If you are using a printer or plotter, you can print objects. | |||
Conceptual Art | |||
To print an object, you do the following: | |||
1. Move the mouse pointer to the object. | |||
2. Press and hold down mouse button 2 while dragging the object | |||
to the Printer. | |||
3. When the object is over the Printer, release mouse button 2. | |||
Chapter 1. Introducing OS/2 2.0 11 | |||
Deleting Objects | |||
You can delete or permanently remove an object that you are sure | |||
you no longer need. This is similar to shredding papers in a | |||
shredder. | |||
Conceptual Art | |||
To delete an object, you do the following: | |||
1. Move the mouse pointer to the object. | |||
2. Press and hold down mouse button 2 while dragging the object | |||
to the Shredder. | |||
3. When the object is over the Shredder, release mouse button 2. | |||
Once an object is deleted, it cannot be recovered. | |||
12IBM OS/2 32-bit Overview Pre-Release Copy | |||
Arranging Objects | |||
You can arrange objects on the screen according to your | |||
preference and work needs. This is similar to arranging or placing | |||
the things on your desk that you will need to work with that day. | |||
For example, if you work with certain objects every day, you might | |||
want to place them in a row at the bottom of your screen. | |||
Conceptual Art | |||
To arrange objects, you do the following: | |||
1. Move the mouse pointer to one of the objects you want to | |||
arrange. | |||
2. Press and hold down mouse button 2. | |||
3. Drag the object in the direction you want to move the object. | |||
4. When the object is in the new location, release mouse button | |||
2. | |||
Repeat these actions until you are satisfied with the arrangement. | |||
Chapter 1. Introducing OS/2 2.0 13 | |||
Opening Objects | |||
You can open an object to look at the contents of the object. This | |||
is similar to opening a file folder to look at the letters that are | |||
inside. For example, if you file a letter (object) in a folder and | |||
want to display the contents of the letter, first open the folder. | |||
Then, open the letter to look at its contents. | |||
To open an object, move the mouse pointer to the object, then | |||
press mouse button 1 twice (double-click). | |||
When you open an object, the contents appear in a separate area | |||
on the screen called a window. Each object opened appears in its | |||
own window. For example, if you install a database program and | |||
a text editor program, and open both programs, they appear in two | |||
separate windows, like this: | |||
Screen Capture - Two windows/titles | |||
While many programs can be opened and displayed in windows, | |||
you can work directly with only one. The program you choose to | |||
work with is the interactive program. | |||
14IBM OS/2 32-bit Overview Pre-Release Copy | |||
Selecting Window Parts | |||
The following describes some of the parts of a window and how to | |||
use them. For more detailed information about the parts of a | |||
window, review the OS/2 Tutorial. | |||
Screen Capture of Window | |||
?? Border . This part of the window is the boundary. When the | |||
border is highlighted, the window is interactive (contains the | |||
interactive program) and is usually the topmost window when two | |||
or more windows are displayed. Use the border to size the | |||
window. For more information about sizing a window, see izing | |||
a Window?on page 17. | |||
?? .Close button Use this button to close the window. Move the | |||
mouse pointer to the button and double-click on it. | |||
?? .Title bar This part of the window shows the title of the | |||
window. Use the title bar to move the window. For more | |||
information about moving a window, see 﨧oving a Window?on | |||
page 18. | |||
?? .Minimize button Use this button to make the window the | |||
smallest possible size. (Generally, when minimized, the window is | |||
invisible). Move the mouse pointer to the button and double-click | |||
on it. The contents of the window are not affected when you | |||
minimize it. | |||
?? .Maximize button Use this button to make the window the | |||
largest possible size. (Generally, when maximized, the window | |||
fills the entire screen). Move the mouse pointer to the button and | |||
double-click on it. The contents of the window are not affected | |||
when you maximize it. | |||
?? .Scroll bar Use the scroll bar to show more information in the | |||
window. Move the mouse pointer to the up, down, right, or left | |||
arrow; then press and hold down mouse button 1. When you press | |||
and hold down mouse button 1, the information in the window | |||
scrolls up, down, right, or left. Release the mouse button when | |||
you are done scrolling through the information in the window. | |||
Chapter 1. Introducing OS/2 2.0 15 | |||
Using the Window List | |||
The Window List shows a list of the objects and programs you are | |||
using. This includes objects or programs that you minimized | |||
(made invisible). | |||
To display the Window List, move the mouse pointer to any area of | |||
the Desktop folder that is blank, (not on a window or any part of a | |||
window, an object, or another folder); then press mouse button 2 | |||
once. The Window List looks like this: | |||
Screen Capture - Window List | |||
Use the Window List to quickly switch to an object or a program | |||
shown in the list, by double-clicking on the name of the object or | |||
program. | |||
16IBM OS/2 32-bit Overview Pre-Release Copy | |||
Sizing a Window | |||
You can make a window larger or smaller. Changing the size of a | |||
window does not affect the contents of the window. | |||
Conceptual Art | |||
To size a window, you do the following: | |||
1. Move the mouse pointer to the border of the window. (The | |||
mouse pointer changes shape to a double arrow when it is in | |||
position correctly on the border.) | |||
2. Press and hold down mouse button 2. | |||
3. Drag the border in the direction that you want. | |||
4. When you are satisfied with the new size, release mouse | |||
button 2. | |||
Chapter 1. Introducing OS/2 2.0 17 | |||
Moving a Window | |||
You can move a window to any location on the screen. For | |||
example, if two windows are open at the same time, you might | |||
want to place one window in the upper-left corner and the other in | |||
the lower-right corner of the screen. You can move the windows | |||
to those positions. | |||
Conceptual Art | |||
To move a window, you do the following: | |||
1. Move the mouse pointer to the title bar of the window. | |||
2. Press and hold down mouse button 2. | |||
3. Drag the window in the direction you want to move it. | |||
4. When the window is in the new location, release mouse button | |||
2. | |||
Repeat these actions until you are satisfied with the new | |||
arrangement. | |||
When you move a window (using the method described below) the | |||
contents and size of the window are not affected. | |||
18IBM OS/2 32-bit Overview Pre-Release Copy | |||
In addition to arranging windows by moving each one individually, | |||
you can arrange automatically all the windows you have open. | |||
1. Display the pop-up menu for the Window List. To do this, | |||
move the mouse pointer to an area (within the Window List | |||
window) that is blank. Then, press the right mouse button | |||
(mouse button 2) once. | |||
2. Move the mouse pointer to the Window choice. | |||
3. Move the mouse pointer to the right arrow; then press mouse | |||
button 1 once. | |||
4. Select the Cascade or Tile choice. | |||
If you cascade or tile windows, the contents of the windows are not | |||
affected. However, the contents may not be completely visible, but | |||
you will always be able to see the title bars. In addition, the size | |||
of the windows might change, and the windows might appear to | |||
overlap. | |||
The cascade arrangement places the window that contains the | |||
interactive program on top (closest to you). Other open windows | |||
are put behind this window. | |||
The cascade arrangement looks like this. | |||
Screen Capture - Cascade | |||
Chapter 1. Introducing OS/2 2.0 19 | |||
The tile arrangement places the window that contains the | |||
interactive program in the upper-left corner of your screen. Other | |||
open windows are put next to this window and to each other, until | |||
the screen is completely full. | |||
The tile arrangement looks like this. | |||
Screen Capture - Tile | |||
20IBM OS/2 32-bit Overview Pre-Release Copy | |||
Introducing Online Information | |||
Most of the information for the operating system is online. The | |||
information you need can be displayed on your screen while you | |||
are doing your work. The online information is your lectronic | |||
library.? | |||
Conceptual Art | |||
Chapter 1. Introducing OS/2 2.0 21 | |||
Using the Master Index | |||
The Master Index is an alphabetic list of topics related to | |||
understanding and using the OS/2 operating system. The list | |||
contains the following kinds of topics: | |||
? Things to consider before performing a task | |||
? | |||
The steps you need to take to complete a task | |||
? Operating system concepts | |||
? DOS error messages. | |||
After you install the OS/2 operating system and review the OS/2 | |||
Tutorial, open the Master Index by double-clicking on the Master | |||
Index folder. | |||
When the Master Index is open, it looks like this: | |||
+-------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+-------------+ | |||
The list of topics appears in an area within the window that looks | |||
like a notebook with tabs. Each tab has a letter of the alphabet on | |||
it that corresponds to the group of topics that start with that letter. | |||
Use the letters on the tabs to move through the index. For | |||
example, if you need information about the topic opying an | |||
object,?you do the following: | |||
1. Move the mouse pointer to the tab that has the letter C on it. | |||
2. Press mouse button 1 once to select the first topic that starts | |||
with the letter C. | |||
3. Move the mouse pointer to the down arrow on the scroll bar. | |||
22IBM OS/2 32-bit Overview Pre-Release Copy | |||
4. Press mouse button 1 to scroll through the topics that start | |||
with the letter C, until you locate the entry for copying an | |||
object. | |||
5. Double-click on the entry (copying an object). | |||
The information for the entry (copying an object) appears in a | |||
window to the right of the Master Index window, like this: | |||
Screen Capture - MI w/entry open | |||
If you leave the Master Index open while you work with the OS/2 | |||
operating system, it is always available for you to use. You can | |||
move the Master Index window to any location on the screen (just | |||
like other windows). | |||
Searching for a Topic | |||
The Master Index has a search action. You can search for an | |||
entry using one or more words that describe the topic. For | |||
example, to search for information about how to duplicate an | |||
object, you might search using the word uplicate,?uplicates,? | |||
or even uplicating.?The result of a search (using duplicate, | |||
duplicates, or duplicating), is opying an object.? | |||
Chapter 1. Introducing OS/2 2.0 23 | |||
To search for a topic: | |||
1. Display the Master Index pop-up menu. To do this, move the | |||
mouse pointer to an area (within the Master Index window) | |||
that is blank. Then, press the right mouse button (mouse | |||
button 2) once. | |||
2. Move the mouse pointer to the Search choice; then press | |||
mouse button 1 once. | |||
A window appears that looks like this: | |||
Screen Capture - Search pop-up | |||
3. Type the word or words that describe the topic. | |||
4. Move the mouse pointer to the word Search (located in the | |||
lower-left corner); then press mouse button 1 once. | |||
5. When the list of topics appears, double-click on the entry. | |||
Printing a Master Index Entry | |||
Once you locate a topic, you might want to print that entry. (You | |||
can only print one entry at a time). | |||
To print an entry: | |||
1. Move the mouse pointer to the entry you want to print; then | |||
press mouse button 1 once. | |||
24IBM OS/2 32-bit Overview Pre-Release Copy | |||
2. Display the Master Index pop-up menu. To do this, move the | |||
mouse pointer to an area (within the Master Index window) | |||
that is blank. Then, press the right mouse button (mouse | |||
button 2) once. | |||
3. Move the mouse pointer to the Print choice; then press mouse | |||
button 1 once. | |||
Using Related Information | |||
You have just read about using the Master Index, and searching | |||
for and printing entries. As you use the Master Index, you will | |||
often find that the entry you select has related topics, which you | |||
may find useful. Related topics are listed under the heading | |||
elated Information,?like this: | |||
Screen Capture - MI w/entry w/hypertext | |||
To select a related topic, move the mouse pointer to the entry; | |||
then double-click on the entry. | |||
For more information about using the Master Index, searching for | |||
topics, printing an entry, or using related information, review the | |||
OS/2 Tutorial. | |||
Chapter 1. Introducing OS/2 2.0 25 | |||
Using the Information Folder | |||
The Information folder contains the OS/2 Tutorial, Glossary, OS/2 | |||
Command Reference, and REXX Information. Use the contents of | |||
the Information folder to learn more about the operating system, to | |||
look for the definition of a term, to use OS/2 commands, or to use | |||
REXX. | |||
To open the Information folder, double-click on it. When the | |||
Information folder is open, it looks like this: | |||
Screen Capture - Info folder/open | |||
The OS/2 Tutorial has information about how to use a mouse, work | |||
with objects and folders, use windows, get help, and other general | |||
information. (The first time you use the operating system, the | |||
tutorial is opened automatically for you.) | |||
The Glossary is an alphabetic list of terms and their definitions. If | |||
you are not familiar with a term you read about in the online | |||
information or online help, use the Glossary to find the definition | |||
for the term. | |||
The OS/2 Command Reference describes the purpose of each | |||
command, and the syntax and parameters for each command. It | |||
26IBM OS/2 32-bit Overview Pre-Release Copy | |||
also has information about topics such as batch files, command | |||
operators, redirection symbols, and substitution variables. | |||
The REXX Information describes the commands you use to write | |||
simple batch programs. It also has information about topics such | |||
as procedures, elements, and comments. | |||
To open the OS/2 Tutorial, or the Glossary, or the OS/2 Command | |||
Reference, or the REXX Information, double-click on it. | |||
Getting Help | |||
Online help is always available. To get help, select the word | |||
﨟elp?when it is displayed on your screen or press F1. | |||
When you request help, the information appears in a help window, | |||
like this: | |||
Screen Capture - Help Window | |||
You can also get help for OS/2 messages and commands. | |||
The following describes some of the different ways you can get | |||
help. For more detailed information, review the OS/2 Tutorial or | |||
request help from within a help window. | |||
Chapter 1. Introducing OS/2 2.0 27 | |||
Displaying Help for an Object or Folder | |||
The help for an object or folder describes the object or contents of | |||
the folder. | |||
To display help for an object or folder: | |||
1. Move the mouse pointer to the object or folder. | |||
2. Press the right mouse button (mouse button 2) once. (The | |||
pop-up menu for the object appears.) | |||
3. Move the mouse pointer to the Help choice. | |||
4. Press mouse button 1 once. | |||
Displaying Help for a Pop-up Menu Choice | |||
The help for a pop-up menu choice describes the action you can | |||
apply to a selected object or folder. | |||
To display help for a pop-up menu choice: | |||
1. Move the mouse pointer to the pop-up menu choice. | |||
2. Press and hold down mouse button 1. (Do not release mouse | |||
button 1). | |||
3. Press the F1 key. | |||
4. When the help window appears, release mouse button 1. | |||
Displaying Help for a Highlighted Word or Phrase | |||
Sometimes a word or a phrase in a help window is highlighted. | |||
The highlighting means that additional help information is | |||
available. The additional help information might be a definition, or | |||
related information, or help for a field. | |||
28IBM OS/2 32-bit Overview Pre-Release Copy | |||
The following shows a help window with highlighted phrases. (In | |||
this example, the highlighted phrases show that additional help | |||
information is available for fields.) | |||
Screen Capture - Help Window w/highlighted phrases | |||
To display the additional help: | |||
1. Move the mouse pointer to the highlighted word or phrase. | |||
2. Press mouse button 1 twice. (The additional help information | |||
appears in another help window. The original help window is | |||
directly underneath the new help window and is not visible. | |||
However, the original help window is still open.) | |||
3. When you finish reviewing the additional help information, | |||
press Esc to return to the original help window. | |||
Displaying Help for OS/2 Messages | |||
The help for OS/2 messages describes how to correct an error or | |||
respond to a warning, or provides general information. The way | |||
you request help for a message depends on how the message is | |||
displayed. | |||
If the message appears in a message window with the word | |||
﨟elp?in it, then do the following: | |||
1. Move the mouse pointer to the word 﨟elp.? | |||
Chapter 1. Introducing OS/2 2.0 29 | |||
2. Press mouse button 1 once. | |||
If the message appears full-screen, and is enclosed in a box, then | |||
do the following: | |||
1. Move the mouse pointer to the phrase 﨑isplay Help.? | |||
2. Press mouse button 1 once. | |||
If the message appears and it has a message number, preceded | |||
by the letters SYS, then do the following: | |||
1. At the OS/2 command prompt, type HELP followed by a space. | |||
Type the message number. (It is not necessary to type the | |||
letters SYS). | |||
2. Press Enter. | |||
For example, if you received this message: | |||
SYS0002: The system cannot find the file specified. | |||
To request help, you type: | |||
HELP 2 | |||
Then, press Enter. | |||
The following help appears: | |||
SYS0002: The system cannot find the file specified. | |||
EXPLANATION: The file named in the command does | |||
not exist in the current directory or search path | |||
specified. Or, the file name was entered incorrectly. | |||
ACTION: Retry the command using the correct file name. | |||
Displaying Help for OS/2 Commands | |||
As described earlier, the OS/2 Command Reference contains the | |||
purpose of and syntax for commands. There are two ways to get | |||
help for a command: open the Command Reference or request | |||
help from the OS/2 command prompt. | |||
If you will be entering more than one command, you might find it | |||
more convenient to open the Command Reference in one window, | |||
while entering commands in another window. | |||
30IBM OS/2 32-bit Overview Pre-Release Copy | |||
If you just want to display help for a command and do not want to | |||
open the Command Reference, then do the following: | |||
1. At the OS/2 command prompt, type HELP followed by a space | |||
and the name of the command, like this: | |||
HELP COPY | |||
2. Press Enter. | |||
Chapter 1. Introducing OS/2 2.0 31 | |||
32IBM OS/2 32-bit Overview Pre-Release Copy | |||
Chapter 2. Features | |||
As described in Chapter 1, the operating system has a graphical | |||
appearance and most of the information you need is online. In | |||
addition to the features already described, the operating system | |||
has other features. This chapter describes some of them. | |||
Installation of OS/2 2.0 | |||
OS/2 2.0 features a graphical installation. For example, progress | |||
bars show you what percentage of features on each installation | |||
diskette is installed. | |||
During installation, you will be asked if you want to learn how to | |||
use the mouse. If this is the first time you are using a mouse, | |||
choose this option to learn how to use the mouse. | |||
For more information about installing OS/2 2.0, see the Quick Start | |||
card or the Installation Guide. | |||
Multitasking | |||
Multitasking is a feature that makes it possible to work with more | |||
than one program or task at a time. This feature is available as | |||
soon as you finish installing the OS/2 operating system. | |||
Think of each program or task you use as a session. | |||
A session can be one of two types: | |||
? Foreground Session | |||
You work directly with this interactive session. It receives | |||
input from your keyboard and mouse or displays information | |||
on your screen. | |||
? Background Session | |||
You do not work directly with this session. However, programs | |||
or tasks running in a background session can be processing | |||
data. | |||
+ Copyright IBM Corp. 1991 33 | |||
For example, if you have a large database, it may contain | |||
thousands of records. Normally, updating a database this size | |||
takes some time, and with other operating systems your | |||
computer cannot be used while the data is updating. | |||
Multitasking removes that barrier. You can instruct the | |||
database program to start processing data, and then you can | |||
place it in the background session. While the database | |||
program is running in the background session, you can be | |||
working with another program in the foreground session. | |||
A program or a task in a background session will stop running | |||
only when it needs further instructions from you. At that time | |||
you can end the session or bring it to the foreground. | |||
For more information about multitasking, see the Master Index. | |||
34IBM OS/2 32-bit Overview Pre-Release Copy | |||
DOS Compatibility | |||
DOS programs take full advantage of most of the features of the | |||
OS/2 operating system. For example, DOS programs use the | |||
multitasking feature, and run either full-screen or in windows. You | |||
can size, arrange, or move DOS programs running in windows, | |||
exactly like OS/2 programs running in windows. | |||
Conceptual Art | |||
Chapter 2. Features 35 | |||
There are also features in this version of the OS/2 operating | |||
system that enable DOS programs to run as well as programs | |||
written specifically for the OS/2 operating system. These features | |||
are described below. | |||
Multiple Virtual DOS Machines | |||
This feature makes it possible to run up to 16 DOS programs at the | |||
same time. Each DOS program can run in a foreground or | |||
background session. Up to 630KB (KB equals 1024 bytes) of | |||
memory are available for each program. DOS programs that use | |||
the Lotus****/ Intel /Microsoft ** (LIM) Expanded Memory Specification | |||
(EMS) and the Lotus/Intel/Microsoft/AST ** (LIMA) Extended Memory | |||
Support (XMS) can also be run. | |||
For more information about using Multiple Virtual DOS Machines, | |||
see the Master Index. | |||
DOS Settings | |||
DOS Settings can be used to tailor the way a DOS program runs. | |||
For example, you can prevent sounds normally heard when a | |||
program is running or you can specify the amount of memory (up | |||
to 630KB) that each DOS program uses. | |||
For more information about using DOS Settings, see the Master | |||
Index and the OS/2 Command Reference. | |||
Dual Boot | |||
The Dual Boot feature provides support for installing DOS Version | |||
3.2 or later and OS/2 2.0 on the same hard disk. With the dual | |||
boot feature, you can switch back and forth between the DOS and | |||
OS/2 operating systems. This feature is useful if you are using | |||
DOS programs that run only under DOS. | |||
For more information about installing the dual boot feature, see the | |||
Installation Guide. | |||
** Lotus is a trademark of the Lotus Corporation, Intel is a trademark of the Intel | |||
Corporation, Microsoft is a trademark of the Microsoft Corporation, and AST is a | |||
trademark of the AST Corporation. | |||
36IBM OS/2 32-bit Overview Pre-Release Copy | |||
Microsoft Windows Compatibility | |||
Text is under development. | |||
Boot Manager | |||
The Boot Manager feature makes it possible for OS/2 Version 2.00 | |||
to coexist with other operating systems (for example, DOS, | |||
* | |||
previous versions of the OS/2 operating system, and AIX ). If you | |||
install this feature, you choose which operating system you want to | |||
be active each time you start your computer. | |||
For more information about installing and using the Boot Manager, | |||
see the Installation Guide. | |||
Special Needs Support | |||
The Special Needs feature provides support for changing the way | |||
the keyboard keys work. This support is useful, for example, for | |||
individuals whose manual dexterity is impaired. | |||
The Special Needs feature is used to change: | |||
? The amount of time a key can be held down before it is | |||
considered to have been pressed | |||
? The amount of time a key can be held down before it begins | |||
repeating its function | |||
? The rate at which a key will repeat its function when it is held | |||
down | |||
? The way a series of keys is pressed and released. | |||
For example, to restart the computer, you press the | |||
Ctrl+Alt+Del keys at the same time. You can change the | |||
way this series of keys works (without changing the result they | |||
produce) by using the sticky keys function. | |||
The sticky keys function sets the keys (in this example, | |||
Ctrl+Alt+Del) to behave as if they were pressed at the same | |||
* Trademark of the IBM Corporation. | |||
Chapter 2. Features 37 | |||
time without actually having to press them at the same time. | |||
You can press the keys one at a time to produce the same | |||
result as pressing them together. | |||
For more information about the Special Needs feature, see the | |||
Master Index. | |||
38IBM OS/2 32-bit Overview Pre-Release Copy | |||
Lockup | |||
The Lockup feature provides protection for the information in your | |||
computer. When Lockup is used, the mouse and keyboard are | |||
locked. | |||
When you use Lockup, a password (known only by you) is set. | |||
Each time you want to unlock your system, you must type this | |||
password to gain access to the system. | |||
For more information about using Lockup, see the Master Index. | |||
Conceptual Art | |||
Chapter 2. Features 39 | |||
High Performance File System | |||
The High Performance File System feature provides fast access to | |||
information on your computer's hard disk. The High Performance | |||
File System is an installable file system like the DOS file system | |||
FAT (File Allocation Table). An installable file system manages the | |||
information stored on diskettes or the hard disk of your computer. | |||
The High Performance File System is faster than FAT because of | |||
the method that it uses to find information on the hard disk. | |||
The High Performance File System provides support for long file | |||
names (up to 254 characters). File names can contain blank | |||
spaces, if the part of the file name that contains the blank space is | |||
enclosed by quotation marks (). | |||
The High Performance File System saves file names exactly as | |||
typed. For example, if you create a file and name it AbC, it is | |||
saved as AbC, not ABC. However, when you search for the file, it | |||
is found whether you type ABC, AbC, or abc. | |||
For more information about installing the High Performance File | |||
System, see the Installation Guide. For more information about | |||
using the High Performance File System, see the Master Index. | |||
Extended Attributes | |||
Attributes are characteristics that describe a file to the operating | |||
system. For example, a file attribute might be the time or date the | |||
file was created. | |||
Extended attributes are additional attributes that describe the file. | |||
For example, an extended attribute might be the name of the | |||
person who created the file. If you use extended attributes to | |||
describe a file, you can search for the file using the extended | |||
attribute. For example, if the name of the person who created the | |||
file is 﨡oe,?you can search for the file using the name Joe as one | |||
of your search parameters. | |||
For more information about using extended attributes, see the | |||
Master Index. | |||
40IBM OS/2 32-bit Overview Pre-Release Copy | |||
OS/2 Commands | |||
Commands are words that you type that tell the OS/2 operating | |||
system to perform an action. Enter OS/2 commands from either | |||
the OS/2 full-screen or window command prompt. | |||
There are a number of OS/2 commands that you can use. Some | |||
examples of these are: COPY (to copy files), DATE (to display or | |||
change the date), and DISKCOPY (to copy diskettes). | |||
For more information about using commands, see the OS/2 | |||
Command Reference. | |||
Procedures Language/2 REXX | |||
Procedures Language/2 REXX is a generalized command | |||
language. This small, powerful language is the Systems | |||
Application Architecture * (SAA * ) procedures language for the OS/2 | |||
operating system. | |||
REXX is useful for writing batch programs, as well as other | |||
programs. It uses common English words and single number | |||
concepts. | |||
For more information about using REXX, see the REXX Information. | |||
System Editor | |||
The System Editor is a simple text editor. You can create, edit, or | |||
view files using the System Editor. Use the editor for simple | |||
editing tasks, for example, editing small batch programs. If you | |||
are doing extensive text editing or word processing, install an | |||
editor designed for those purposes. | |||
The System Editor supports both the mouse and keyboard, and has | |||
extensive online help. It also supports several different font styles, | |||
* Trademark of the IBM Corporation | |||
Chapter 2. Features 41 | |||
font sizes, and type styles. You can set the font to the same style | |||
your printer uses and see how the file looks before you print it. | |||
For more information about using the System Editor, see the | |||
Master Index. | |||
42IBM OS/2 32-bit Overview Pre-Release Copy | |||
Games Programs | |||
Use the Games programs for entertainment or educational | |||
purposes. For example, if you want to use a strategy game, try | |||
Reversi. The object of the game is to fill more squares (with red | |||
circles) than your opponent the computer does (with blue circles) | |||
Conceptual Art | |||
For more information about using the games programs, see the | |||
Master Index. | |||
Chapter 2. Features 43 | |||
Productivity Programs | |||
Productivity programs are simple programs that can help you with | |||
most operating system and business tasks. For example, use | |||
Presentation Manager * (PM) Chart to make graphs, or Calculator to | |||
add, subtract, multiply, and divide numbers. | |||
Conceptual Art | |||
For more information about using the productivity programs, see | |||
the Master Index. | |||
* Trademark of the IBM Corporation. | |||
44IBM OS/2 32-bit Overview Pre-Release Copy | |||
Chapter 2. Features 45 | |||
46IBM OS/2 32-bit Overview Pre-Release Copy | |||
Appendix A. Keyboard and Mouse Use | |||
The following lists some of the most common tasks you can do, | |||
using either the keyboard keys or a mouse. | |||
For a detailed list of keys assignments, do one of the following: | |||
? See the Master Index | |||
? From a pop-up menu, select Help; then select Keys Help | |||
? From within a help window, select Help; then select Keys Help. | |||
The plus sign (+) between key names means to press and hold | |||
down the keys in the order shown and release them together. | |||
System Tasks | |||
Task Keys Mouse | |||
Get Help. F1 Click on the word 﨟elp? | |||
Restart the system. Ctrl + Alt + Del | |||
Switch to next window. Alt + Tab Click on window | |||
Switch to next window or Alt + Esc Click on window or icon | |||
full-screen session. | |||
Display Window List. Ctrl + Esc Move mouse pointer to | |||
blank part of desktop; then | |||
press mouse button 2 once | |||
Folder and Object Tasks | |||
Task Keys Mouse | |||
Move among folders or ? , ? , ? , or ? Click on the folder or | |||
objects. object | |||
Display a pop-up menu. Shift + F2 Press both mouse buttons | |||
at the same time | |||
Select first choice in Home Click on choice | |||
pop-up menu. | |||
Select last choice in End Click on choice | |||
pop-up menu. | |||
Select a choice using the Type the underlined letter | |||
underlined letter. | |||
Open selected folder or Enter Double-click on folder or | |||
object. object | |||
+ Copyright IBM Corp. 1991 47 | |||
Task Keys Mouse | |||
Delete selected objects. Del Drag to Shredder | |||
Print selected objects. Shift + Print Screen(PrtSc) Drag to Printer | |||
Select a folder or object. Spacebar Click on folder or object | |||
Select more than one Shift + F8 (to begin Add Hold down Ctrl key while | |||
folder or object. mode), use arrow keys to clicking on each one | |||
move among folders and | |||
objects and press | |||
Spacebar to make each | |||
selection. Press ShiftF8 + | |||
again (to end Add mode) | |||
Select a range of folders Shift + F8 (to begin Add Click on first object in | |||
or objects from cursor's mode), use arrow key to range; then press and hold | |||
current position to move to first file in the down Shift. Click on last | |||
cursor's new position. range and press Spacebar object in range. | |||
to select. Press and hold | |||
down CtrlShift while + | |||
moving to last file in the | |||
range. Release CtrlShift. + | |||
Press ShiftF8 again (to + | |||
end Add mode). | |||
Move folder or object. F7 Drag to another folder or | |||
object | |||
Copy folder or object. F8 Hold down Ctrl key while | |||
dragging to folder or | |||
object where you want a | |||
copy to appear. | |||
Window Tasks | |||
Task Keys Mouse | |||
Move window. AltF7 Move mouse + | |||
pointer to title | |||
bar; then press | |||
and hold mouse | |||
button 2 while | |||
dragging to new | |||
location | |||
Size window. AltF8 Move mouse + | |||
pointer to | |||
border; then | |||
press and hold | |||
mouse button 2 | |||
while dragging | |||
border in any | |||
direction | |||
Minimize window. Alt on + F9 Click | |||
Minimize button | |||
48IBM OS/2 32-bit Overview Pre-Release Copy | |||
Task Keys Mouse | |||
Maximize window. Alt on + F10 Click Maximize | |||
button | |||
Close window. AltF4 Double-click on + | |||
Close button | |||
Scroll contents of window up one page. Page Up < PgUp * | |||
Scroll contents of window down one page. Page Down | |||
PgDn < * | |||
Scroll contents of window left one page. Ctrl + Page Up | |||
PgUp < * | |||
Scroll contents of window right one page. Ctrl + Page | |||
Down PgDn < * | |||
Help Window Tasks | |||
These tasks only work from within a help window. | |||
Task Keys Mouse | |||
Switch between Help and program. Alt + F6 Click on | |||
program | |||
Display General Help. F2 Click on | |||
General Help | |||
Display Keys Help. F9 Click on Keys | |||
Help | |||
Display Help Index. F11 Click on Help | |||
Index | |||
Display Using Help. Shift + F10 Click on Using | |||
Help | |||
Display Tutorial. Shift on + F2 Click | |||
Tutorial | |||
Display help for highlighted word or phrase. Use Tab key to Move mouse | |||
move cursor totopointer | |||
highlighted highlighted | |||
word or phrase; word or phrase; | |||
then press Enter then | |||
double-click | |||
Display previous help window. Esc Click on | |||
Previous | |||
Appendix A. Keyboard and Mouse Use 49 | |||
Master Index Tasks | |||
Task Keys Mouse | |||
Open Master Index. Select; then Double-click on | |||
press Enter Master Index | |||
icon. | |||
Move through topics one line at a time. Click on topic | |||
Move up through topics one page at a time. Page Up (PgUp) | |||
Move down through topics one page at a time. Page Down | |||
(PgDn) | |||
Move to topic areas. Type letter of Click on letter | |||
the alphabet of the alphabet | |||
Display related information. Use the Tab key Move mouse | |||
to move cursortopointer | |||
to related related | |||
information; information; | |||
then press Enter then | |||
double-click | |||
Remove related information help window. Esc Click on | |||
previous | |||
Change focus. Click on Master | |||
Index listing or | |||
topic | |||
50IBM OS/2 32-bit Overview Pre-Release Copy | |||
Index | |||
Index | |||
closing a window 15 | |||
A Command Reference | |||
arranging objects 13 description of viii | |||
arranging windows 18 displaying 27 | |||
attributes, definition of 40 | |||
commands, using 41 | |||
compatability | |||
DOS 35 | |||
B Microsoft Windows 37 | |||
background session 33 copying objects 10 | |||
Boot Manager 37 | |||
border, definition of 15 | |||
button D | |||
Close 15 deleting an object 12 | |||
Maximize 15 Desktop folder, defintion of 3 | |||
Minimize 15 discarding objects 12 | |||
displaying | |||
C Command Reference 27 | |||
Glossary 27 | |||
cascade arrangement 19 help for folders 28 | |||
Changes from previous versions help for highlighted phrases 28 | |||
Boot Manager x | |||
Control Panel x help for highlighted words 28 | |||
Desktop Manager x help for messages 29 | |||
help for objects 28 | |||
DOS compatibility x help for OS/2 commands 30 | |||
DOS Settings x help for pop-up menu | |||
File Manager x | |||
games xi choices 28 | |||
Lockup xi Information folder 26 | |||
Master Index 22 | |||
Microsoft Windows objects 14 | |||
compatibility x OS/2 Tutorial 27 | |||
Multiple Virtual DOS | |||
Machines x pop-up menu 7 | |||
Print Manager x related information 25 | |||
REXX Information 27 | |||
Productivity programs xi DOS compatibility 35 | |||
special needs x DOS Programs | |||
Task List x | |||
changing the location of an compatibility 35 | |||
object 9 DOS Settings 36 | |||
Dual Boot 36 | |||
click, definition of 8 Multiple Virtual DOS | |||
Machines 36 | |||
+ Copyright IBM Corp. 1991 51 | |||
Index | |||
DOS Programs (continued) features of OS/2 33 | |||
running more than one 36 file systems, definition of 40 | |||
DOS Programs folder, description folders | |||
of 5 DOS Programs 5 | |||
DOS Settings 36 help for 28 | |||
double-click, definition of 8 Information 4 | |||
dragging a window 18 introducing 2 | |||
drag, definition of 8 Microsoft Windows Programs 5 | |||
Dual Boot 36 Network 5 | |||
duplicating an object 10 OS/2 Programs 5 | |||
OS/2 System 4 | |||
Templates 4 | |||
E folder, definition of 2 | |||
editor, system 41 foreground session 33 | |||
erasing an object 12 | |||
extended attributes 40 | |||
G | |||
Games | |||
F getting help 27 | |||
features Glossary, displaying 27 | |||
Boot Manager 37 | |||
DOS compatiblity 35 | |||
DOS Settings 36 H | |||
Dual Boot 36 Help | |||
extended attributes 40 for a folder 28 | |||
Games programs 43 for a highlighted phrase 28 | |||
High Performance File for a highlighted word 28 | |||
System 40 for a pop-up menu choice 28 | |||
installation 33 for an object 28 | |||
learning to use a mouse 33 for messages 29 | |||
Lockup 39 for OS/2 commands 30 | |||
Microsoft Windowshelp window, description of 27 | |||
compatibility 37High Performance File System 40 | |||
Multiple Virtual DOS highlighted phrase, help for 28 | |||
Machines 36 highlighting, defintion of 28 | |||
multitasking 33 | |||
OS/2 Commands 41 | |||
I | |||
Procedures Language/2 | |||
REXX 41 icons, introducing 2 | |||
Productivity programs 44 icon, definition of 3 | |||
special needs support 37 index, online 22 | |||
System Editor 41 Information folder | |||
description of 4 | |||
52IBM OS/2 32-bit Overview Pre-Release Copy | |||
Index | |||
Information folder (continued) mouse | |||
displaying 26 introducing vii | |||
Installation Guide use of 6, 8 | |||
description of viii moving objects 9 | |||
installation of OS/2 33 Multiple Virtual DOS Machines 36 | |||
installing, more than one operating multitasking | |||
system 37 definition of 1 | |||
interactive program, definition description of 33 | |||
of 14 | |||
interactive window, definition | |||
N | |||
of 15 | |||
Network folder, description of 5 | |||
K | |||
keyboard and mouse use 47 O | |||
objects | |||
arranging 13 | |||
L copying 10 | |||
locking your system 39 discarding 12 | |||
Lockup 39 displaying 14 | |||
look at the contents of an displaying a pop-up menu 7 | |||
object 14 help for 28 | |||
introducing 2 | |||
managing 5 | |||
M Master Index 4 | |||
Master Index moving 9 | |||
description of 22 opening 14 | |||
displaying 22 | |||
Printer 5 | |||
printing an entry 24 printing 11 | |||
searching for a topic 23 Shredder 4 | |||
topics 22 working with 8 | |||
using 22 object, definition of 2 | |||
using related information 25 | |||
online information | |||
Master Index object, description27getting help | |||
of 4 Glossary 26 | |||
maximizing a window 15 Information folder 26 | |||
messages, help for 29 introducing 1, 21 | |||
Microsoft Windows | |||
Master Index 21 | |||
compatiblity 37 OS/2 Command Reference 26 | |||
Microsoft Windows Program folder,26OS/2 Tutorial | |||
description of 5 REXX Information 27 | |||
minimizing a window 15 searching for a topic 23 | |||
using 21 | |||
Index 53 | |||
Index | |||
open an object 14 R | |||
opening the Master Index 22 | |||
OS/2 commands 41 rearranging objects 13 | |||
displaying help for 30 related information, displaying 25 | |||
using 41 REXX Information | |||
description of viii | |||
OS/2 operating system displaying 27 | |||
changes from previous | |||
versions x REXX, description of 41 | |||
description of 1 running multiple DOS | |||
features 33 programs 36 | |||
running more than one | |||
program 33 S | |||
OS/2 Programs folder, description | |||
of 5 scroll bar 15 | |||
OS/2 System folder, description searching for a topic 23 | |||
securing your system 39 | |||
of 4 select, definition of 6 | |||
OS/2 Tutorial sessions | |||
description of viii | |||
displaying 27 background 33 | |||
foreground 33 | |||
mulitple DOS 36 | |||
Shredder object, description of 4 | |||
P shredding an object 12 | |||
pop-up menu | |||
definition of 6 sizing a window 17 | |||
displaying 7 special needs support 37 | |||
help for choices 28 sticky keys, definition of 37 | |||
System Editor 41 | |||
using 7 | |||
working with 7 | |||
preventing unauthorized use of | |||
system 39 T | |||
Printer object, description of 5 tailoring a DOS program 36 | |||
Templates folder, description of 4 | |||
printing a Master Index entry 24 throwing away an object 12 | |||
printing objects 11 tile arrangement 19 | |||
Procedures Language/2 REXX 41 | |||
productivity programs tiling windows 18 | |||
program, interactive 14 title bar 15 | |||
topmost window 15 | |||
protecting information on tutorial 27 | |||
system 39 | |||
Q U | |||
Quick Start using the keyboard 47 | |||
description of viii | |||
54IBM OS/2 32-bit Overview Pre-Release Copy | |||
Index | |||
V | |||
view the contents of an object 14 | |||
W | |||
Window List | |||
description of 16 | |||
using 16 | |||
windows | |||
arranging 18 | |||
border 15 | |||
cascade 18 | |||
closing 15 | |||
dragging 18 | |||
interactive 15 | |||
maximizing 15 | |||
minimizing 15 | |||
scroll bar 15 | |||
selecting parts 15 | |||
sizing 17 | |||
tile 18 | |||
title bar 15 | |||
Window List 16 | |||
window, definition of 14 | |||
working with objects 8 | |||
Index 55 | |||
� | |||
</pre> | |||
</div></div> | |||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
READ6167.DOC | |||
<div class="mw-collapsible-content"> | |||
<pre width="87"> | |||
Read Me First | |||
Welcome to IBM * OS/2 * Version 2.0, the integrating platform for the | |||
personal computer systems. | |||
This development version of the OS/2 operating system is intended | |||
to run existing OS/2, Windows ** and DOS applications. | |||
IBM and others are testing many DOS, Windows, and OS/2 appli- | |||
cations with this operating system. However, some applications, | |||
or functions within applications, might not currently work. We | |||
encourage you to use the support system provided to you to give | |||
us your comments. IBM needs your feedback to ensure that OS/2 | |||
Version 2.0 is the best possible product. | |||
Enjoy the new world of the OS/2 operating system! | |||
What's New in This Version? | |||
? The Workplace Shell is now the user interface. | |||
? You can run Windows applications in standard mode, | |||
unchanged, without installing Windows on your system. | |||
? You can start ANY version of DOS in DOS sessions. This | |||
means you can run even version-specific DOS applications. | |||
? Support for DOS unique device drivers has been added. | |||
? More mini-applications, including an asynchronous communi- | |||
cations connection and a LAN-based chess game, have been | |||
added. | |||
? PM installation has been simplified. The enhancements assist | |||
users in customizing the system to their needs. | |||
* Trademark of the IBM Corporation. | |||
** Trademark of the Microsoft Corporation. | |||
Read Me First 1 | |||
Installation | |||
Before installing this version of OS/2 2.0, you need to format the | |||
partition in which it will be installed. Otherwise, all your compo- | |||
nents might not work correctly. | |||
Select Features and Install | |||
If you choose the installation option elect Features and Install,? | |||
you must select DOS and all font choices. Otherwise, problems | |||
might occur later. | |||
Migration of Existing Applications | |||
Although you are prompted to migrate your existing applications | |||
during installation, this function has not been implemented in this | |||
development version. | |||
Printer Port Warning Message | |||
When you install a printer during system installation, you will | |||
receive the following pop-up message, even if you have not | |||
installed another printer: | |||
The port you have selected has a printer attached to it. | |||
Select OK and your printer will be installed, using the port you | |||
selected. | |||
Additionally, you will have an extra print object named LPT1Q. | |||
This object is attached to the IBMNULL driver and may be dis- | |||
carded. To discard the object, place the mouse pointer over the | |||
object, press and hold mouse button 2, and drag the object to the | |||
shredder. When you release the mouse button, the object will be | |||
discarded. | |||
2 | |||
Installing Printers after OS/2 Installation | |||
We recommend that you install printers during the OS/2 installa- | |||
tion. If you do not, you will need to manually copy IBMNULL.DRV | |||
from the Presentation Manager Device Driver diskette 1 to the | |||
\OS2\DLL\ subdirectory before you install the printer. | |||
In addition, you must make this printer your application default. To | |||
select the printer as your default printer: | |||
1. Move the mouse pointer to the printer object. | |||
2. Press mouse button 2 to get a pop-up menu for the print | |||
object. | |||
3. Select Set default. | |||
4. Select your printer. | |||
Minimum System Configuration Requirements | |||
To install and use the OS/2 operating system, you need a personal | |||
computer system with an 80386, 80386SX, 80486, or 80486SX micro- | |||
processor. | |||
Currently, you need 4MB of memory to install OS/2 2.0. | |||
We are continuing to work on improving the DASD usage of OS/2 | |||
2.0. The following numbers reflect current requirements and might | |||
be different in the final product. | |||
Currently, there are three installation options. The DASD require- | |||
ments for these are: | |||
? Install All Features: 26MB | |||
? Install Preselected Features: 18MB | |||
? Select Features and Install: 12MB?6MB | |||
Note: These numbers are more accurate than the numbers shown | |||
on the installation screens. | |||
You also need to plan for a swap file, which can be placed on any | |||
drive. The size of the swap file varies greatly, depending upon | |||
Read Me First 3 | |||
how much memory you have in your system and how much | |||
memory your applications use. We recommend a swap-file size of | |||
5MB to 9MB. | |||
If the system cannot extend the swap file when required, the oper- | |||
ation being attempted (for example, an application being loaded) | |||
will fail, and a pop-up message will appear. | |||
Currently, the installation program scans your hard disk and | |||
allows you to install OS/2 only if the target partition is at least | |||
18MB. | |||
If you are planning to install IBM Extended Services for OS/2 or | |||
IBM OS/2 LAN Server V2.0, refer to the estrictions and Installa- | |||
tion Instructions?for these products for more information about | |||
DASD requirements. | |||
Hardware Considerations | |||
XGA Displays | |||
The current version does not have an XGA driver. All XGA dis- | |||
plays will be run in VGA mode. | |||
Floating Point Emulator | |||
Applications that require the use of a math coprocessor might not | |||
run; those that can exploit the math coprocessor might run slower. | |||
This is because the system has a floating-point emulator, which | |||
emulates the math coprocessor when floating-point hardware is | |||
not present. In hardware configurations that have a ?86 B1 step- | |||
ping level,?the system will disable the 80387 hardware and use | |||
the floating-point emulator without notifying the user. | |||
The floating-point emulator will NOT generate denormal | |||
exceptions. | |||
4 | |||
Printing from a Serial Port with a PS/2 Model 90 or 95 | |||
* | |||
If you need to use the COM port in a PS/2 Model 90 or 95 with | |||
Enhanced set to ON, make sure that the Serial Transmit and Serial | |||
Receive Arbitration Levels shown in the hardware configuration | |||
are set to Dedicated, with different numbers. To do this, you need | |||
to use the Setup/Diagnostics diskette. When both levels of a serial | |||
port are set to Shared, data communication and printing from the | |||
COM port with Enhanced set to ON will not work correctly | |||
For example, when Serial Port is SERIAL 2 in the hardware config- | |||
uration, its corresponding Serial Transmit Arbitration Level should | |||
be DEDICATED 3, and Serial Receive Arbitration Level should be | |||
DEDICATED 4. | |||
Overall System Performance | |||
Because performance work on OS/2 2.0 is not finished, we recom- | |||
mend that you do not use this version for performance | |||
benchmarking or evaluation. | |||
FAT File System Performance | |||
Performance of the FAT file system is better than in earlier ver- | |||
sions. | |||
Performance enhancements that add intelligent read-ahead and | |||
lazy-writing were made to DISKCACHE. In the previous EEP | |||
version, OS/2 had the potential to lose data if bad sectors were | |||
found during lazy-write; this has been corrected. | |||
* Trademark of the IBM Corporation. | |||
Read Me First 5 | |||
High Performance File System Performance | |||
The performance work on HPFS is not yet finished. In partitions | |||
smaller than 60MB, performance is about the same as that of the | |||
FAT file system; in larger partitions, it is somewhat faster. | |||
In some configurations, formatting your hard disk for the HPFS | |||
might be slower than formatting the same disk for the FAT file | |||
system. | |||
Scheduler Performance | |||
OS/2 now uses dynamic time-slicing. Try the default first. If per- | |||
formance is not better, go back to your specific setting. | |||
Loader Performance | |||
Application load time is better than in previous versions, but still | |||
not as fast as in Version 1.3. To improve application load times, | |||
add ,128 to the end of the DISKCACHE statement | |||
(DISKCACHE=64,LW,128). This change improves load times for | |||
the FAT file system. | |||
DOS-Session Performance | |||
DOS performance is best in DOS full-screen sessions; DOS window | |||
sessions provide somewhat slower performance. The perform- | |||
ance of some applications can be increased by adjusting: | |||
? IDLE_SENSITIVITY | |||
? EMS_MEMORY_LIMIT and XMS_MEMORY_LIMIT. If your appli- | |||
cation does not need extended or expanded memory, you need | |||
not allocate it. | |||
Workplace Shell Performance | |||
The performance work on the Workplace Shell is not yet finished. | |||
6 | |||
Windows Performance | |||
The performance work on Windows is not yet finished. | |||
Printing Performance | |||
The performance on printing has been improved. | |||
Workplace Shell | |||
? We recommend that you use the Shutdown option from the | |||
desktop pop-up menu before powering down your system. | |||
? | |||
In this development version, be careful not to shred the OS/2 | |||
System and Startup folders. If these objects are shredded, you | |||
have to reinstall the operating system to recover them. | |||
? Some of the documentation states that you must press mouse | |||
buttons 1 and 2 at the same time to display a pop-up menu. | |||
The correct action is to single-click mouse button 2. | |||
? In this development version, Refresh has been included in the | |||
folder context menus to allow users to update the contents of a | |||
folder. This function enables folders to see objects that | |||
another program may have copied since the folder was | |||
opened. In the final version, folders will update automatically | |||
and Refresh will be removed from the menus. | |||
? Before using the diskette object, make sure that the diskette is | |||
properly inserted in the diskette drive. Failure to do so might | |||
cause unpredictable results. | |||
? Copying files from one drive to another using the Drives folder | |||
is not functioning. Use the OS/2 and DOS command prompts | |||
instead. | |||
? The edit icon option from the Icon page of a Settings notebook | |||
is not yet fully functional. | |||
? | |||
If you use the FIND command from a pop-up menu and specify | |||
?.*?as the item to find, the system will hang; you will have to | |||
restart it. | |||
? The Sort page of the Folder Settings notebook is not func- | |||
tioning, so the system will not sort the contents of a folder. | |||
Read Me First 7 | |||
? The Include page of the Folder Settings notebook is not func- | |||
tioning. Redefining the files to include in a folder does not | |||
work. | |||
? The Menu page of the Folder Settings notebook is not func- | |||
tioning, so you cannot modify folder menus. | |||
? The color palette can only be manipulated by using the mouse. | |||
Windows | |||
The current OS/2 version supports VGA only for Windows sessions. | |||
On the 8514/A and XGA, Windows will not run in VGA mode. | |||
Windows printing | |||
The current version supports printing only to the OS/2 default | |||
printer. | |||
The current version contains only a subset of the available | |||
Windows printer drivers. They are automatically installed when | |||
you install and configure the OS/2 printer drivers. The drivers | |||
shipped with this version of OS/2 2.0 are: | |||
? PSCRIPT.DRV | |||
? EPSON24.DRV | |||
? EPSON9.DRV | |||
? | |||
PROPRINT.DRV | |||
? PROPRN24.DRV | |||
? QWIII.DRV | |||
? IBMCOLOR.DRV | |||
? IBMGRX.DRV | |||
? TTY.DRV | |||
If you currently use the Windows program, you can install the | |||
printer drivers using the Windows control panel the same way you | |||
would under Windows. If you use a Windows driver that was not | |||
shipped with the OS/2 operating system, do the following: | |||
1. Start a Windows session by clicking on the Windows Session | |||
icon in the Command Prompts folder (in the OS/2 System | |||
folder). | |||
8 | |||
2. Start the Windows Control Panel. | |||
3. Double-click on the printer icon. | |||
4. Select Add Printer. | |||
5. Select Unlisted Printer from the list of printers to install. | |||
6. Select the Install push button. | |||
7. Search for the driver you wish to install. | |||
8. Select OK to exit this panel. | |||
9. Select Configure. | |||
10. Select LPT1.OS2 or LPT2.OS2 to associate the printer driver | |||
with a printer port. Do NOT use LPT1 or LPT2. | |||
11. Select Setup. | |||
12. Select the printer you wish to use. | |||
13. Select OK to exit this panel. | |||
14. Select OK to exit the next panel. | |||
15. Exit to an OS/2 session by double-clicking on the OS/2 icon at | |||
the bottom of the Windows screen. | |||
16. Select the OS/2 printer object. | |||
17. Use create another, copy, or copy from template to create | |||
another print destination. | |||
18. Use open settings to configure the required port (for example, | |||
LPT1) and printer driver (IBMNULL). | |||
19. OS/2 always installs IBMNULL during system installation. If | |||
IBMNULL is not shown in the list of available printer drivers, | |||
use the Install pop-up menu option on an existing printer driver | |||
to get the printer driver install dialog. Insert PM device driver | |||
diskette 1, and press Refresh. Select IBMNULL from the list, | |||
and press Install. Press Cancel and select IBMNULL for the | |||
print destination. | |||
Read Me First 9 | |||
Windows Information | |||
? To install Windows applications in the OS/2 operating system, | |||
follow the manufacturer's instructions. If the installation proce- | |||
dure does not work properly, open a DOS session and try the | |||
installation procedure again. If the procedure still does not | |||
work, run the installation command using RUN from the File | |||
menu. | |||
? To run Windows applications, choose one of the following: | |||
?Create a Windows full-screen object and type the name of | |||
the Windows application. | |||
?Create a DOS full-screen object and type WINOS2.COM | |||
and the name of the Windows application in the parameter | |||
field. | |||
?Select RUN in the Windows Program Manager. | |||
?Type WINOS2 followed by your program name in a DOS | |||
session. | |||
You cannot run DOS applications using RUN from the File | |||
menu. | |||
? If a Windows application produces an error indicating that | |||
there is insufficient memory available, increase the DOS | |||
setting, DPMI_MEMORY_LIMIT from the default (3MB) to 4MB | |||
or 5MB. This setting should not be set arbitrarily high since | |||
the OS/2 Swapper will grow by the amount of additional | |||
memory allocated. | |||
? To enable Ctrl+Esc to bring up the Windows task list or | |||
Alt+Esc to switch between your Windows applications only, | |||
change the DOS setting KBD_CTRL_BYPASS. | |||
? If you get FATAL ERROR 401 (or 410) when you try to start a | |||
multiple-application Windows session, the Windows video | |||
drivers were not properly configured. Make sure that the fol- | |||
lowing lines are in the SYSTEM.INI file in the directory | |||
c:\os2\mdos\winos2 (where c: is your OS/2 startup drive). | |||
display.drv=vga.drv | |||
fonts.fon=vgasys.fon | |||
fixedfon.fon=vgafix.fon | |||
oemfonts.fon=vgaoem.fon | |||
10 | |||
? If you are using multiple Windows applications, change the | |||
DOS setting, DOS_FCBS to improve performance. | |||
? Dynamic data exchange between Windows applications in sep- | |||
arate DOS sessions, or between Presentation Manager (PM) | |||
and Windows applications, might require switching between | |||
the DOS sessions (using Ctrl+Esc). | |||
? If you set the Windows Clipboard to PUBLIC: | |||
?PrintScreen in the Windows session will not copy data to | |||
the clipboard. | |||
?Any text string, bit map, or metafile that is greater than | |||
48KB will not be transferred to the Public Clipboard. | |||
DOS Applications and Environments | |||
Interrupt 21h Find First Call | |||
Some DOS applications that use the interrupt 21h find first call | |||
might not work properly (for example, TAPCIS). To fix this problem | |||
in this development version, execute FIX_FIND (located in | |||
\OS2\MDOS) in the DOS session before you run the failing applica- | |||
tion. It will not be necessary to correct this problem in future ver- | |||
sions. | |||
UNDELETE Command | |||
Currently, the UNDELETE command works only in OS/2 sessions. | |||
In later versions, UNDELETE also will be supported in DOS ses- | |||
sions. | |||
Background DOS Programs | |||
Some DOS programs need special DOS settings to run properly in | |||
the background. Without these settings, some applications appear | |||
to stop. | |||
The OS/2 operating system has a feature called 﨑OS Settings.? | |||
Its purpose is to provide the highest level of compatibility for indi- | |||
Read Me First 11 | |||
vidual DOS applications. DOS settings are defined for each DOS | |||
session and are set with the Settings choice in the pop-up menu. | |||
There are two DOS settings that might help when you run pro- | |||
grams in the background: | |||
? HW_TIMER: Changing this setting from Off to On enables the | |||
application to receive timer interrupts while running in the | |||
background. Some programs need these interrupts (for | |||
example, SuperKey****, or WordPerfect when it is running | |||
macros). Some communications programs also run better | |||
when this setting is On. | |||
? IDLE_SENSITIVITY: Increasing this property to a setting above | |||
the default of 75% will boost the priority of that individual DOS | |||
session. | |||
Double Mouse Pointers | |||
If you run an application in a DOS window session, and two mouse | |||
pointers are displayed, change the DOS setting, | |||
MOUSE_EXCLUSIVE_ACCESS to On. | |||
Generic Hardware Support | |||
Generic hardware support enables OS/2 2.0 to run many programs | |||
that were not possible in earlier versions. Scanners, FAX, 3270, | |||
network, and other specialized hardware can be used in a DOS | |||
session just as they are in DOS. | |||
Novell DOS LAN Requestor | |||
To use the Novell DOS LAN Requestor in a DOS session under | |||
OS/2 2.0, set the DOS settings as follows: | |||
DOS_DEVICE | |||
c:\dxma0mod.sys | |||
c:\dxmc0mod.sys | |||
** WordPerfect is a trademark of WordPerfect Corporation. SuperKey is a trade- | |||
mark of Borland International, Inc. | |||
12 | |||
Note that these are the settings for Token Ring. | |||
DOS_VERSION | |||
net4.com,4,0,255 | |||
DOS_LASTDRIVE | |||
m | |||
If you have more drives than m, change to the highest drive | |||
letter. | |||
The drive after the one you specified for LASTDRIVE will become | |||
your logon drive. | |||
Novell will use the adapter directly, so you will not be able to use | |||
the network adapter in another session. | |||
Expanded Memory Conflicts | |||
To function, expanded memory service (EMS) needs 64KB of con- | |||
tiguous space above 640KB. Unfortunately it must share this | |||
memory with adapters (network, disk, display, and 3270) that | |||
locate themselves in memory above 640KB. If you have used an | |||
EMS emulator under DOS, you are probably aware of these con- | |||
flicts and know some techniques to fix them. The OS/2 operating | |||
system also provides a technique that simplifies the resolution of | |||
these conflicts. | |||
The DOS setting, MEM_INCLUDE_REGIONS, enables you to disable | |||
the adapter memory for any session and let EMS use it instead. | |||
For example, if you have a 3270 adapter and already have OS/2 | |||
Communications Manager support, you will not need to use the | |||
3270 memory in a DOS session. To disable this memory, you will | |||
need to find the address of the 3270 adapter. Use the PS/2 Refer- | |||
ence Diskettes (or an equivalent method for your system). When | |||
the address is known, specify the range in the Include regions | |||
property. Most IBM 3270 adapters will start at CE00 (0xCE000 | |||
absolute). The property should be set to: | |||
CE000-CFFFF | |||
This will allow EMS to use this memory if there is enough near this | |||
range. | |||
Read Me First 13 | |||
If this is not sufficient because you need access to multiple | |||
adapters from a single DOS session, you will need to rearrange | |||
your memory addresses. This is the same process you follow | |||
under DOS. | |||
VCPI and Other Non-DPMI Extenders | |||
VCPI (Virtual Control Program Interface) and other non-DPMI (DOS | |||
Protect Mode Interface) extenders will not be supported in OS/2 | |||
DOS sessions. These extenders are believed to compromise | |||
system integrity in a multitasking environment such as OS/2 2.0. | |||
Disk Writes using Physical Sector Addressing | |||
Hard-disk writes using physical sector addressing are not sup- | |||
ported because they violate system integrity in a multitasking | |||
operating system. (Although most functions of the Norton Utilities ** | |||
are supported, the SORT/UNDELETE functions are not. Use the | |||
OS/2 UNDELETE command instead.) | |||
High Memory and Upper Memory Blocks | |||
The second parameter of the DOS= statement specifies whether | |||
applications can use memory above 640KB (upper memory | |||
blocks). The default for this release is DOS=LOW,NOUMB (low | |||
memory blocks). We encourage you to change the DOS settings | |||
DOS_UMB and DOS_HIGHL so that your applications have access | |||
to upper memory blocks and extra memory. | |||
Borland Turbo Assembler | |||
To run the Turbo Assembler ** (TASMX), you must set the DOS | |||
setting, DPMI_API to enabled. | |||
** Norton Utilities is a Trademark of Symantec Corporation. Turbo Assembler is a | |||
trademark of Borland International, Inc. | |||
14 | |||
Miscellaneous | |||
32-Bit Programs | |||
For this development version of OS/2 2.0, developers of 32-bit pro- | |||
grams need to relink their programs using the latest version of | |||
LINK386. | |||
Printing to Files | |||
The printer object Output to File option is not functioning properly. | |||
This will be corrected in the final version. | |||
High Performance File System | |||
We are aware of intermittent problems with the high performance | |||
file system on certain hardware configurations. If you experience | |||
these problems, insert the line 﨏ACHE /LAZY:OFF?in your | |||
STARTUP.CMD file. You may notice some performance degrada- | |||
tion as a result of this. | |||
Sticky Pad | |||
When you select Sticky Pad from the Productivity Folder, you will | |||
get the message: SHLERR_MESSAGE_NOT_FOUND. | |||
The Sticky Pad will not work and you will be returned to the Pro- | |||
ductivity folder. | |||
The DOS_VERSION Setting | |||
When you change the DOS setting, DOS_VERSION, you must save | |||
it immediately after entering the value. If you change another DOS | |||
setting before you save the DOS_VERSION value, the value will be | |||
lost. | |||
Read Me First 15 | |||
Print Object Pop-Up Menu | |||
The pop-up menu brought up from the title bar icon does not func- | |||
tion properly. Click on the window's background instead. | |||
16 | |||
� | |||
</pre> | |||
</div></div> | |||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
V2-WIN.DOC | |||
<div class="mw-collapsible-content"> | |||
<pre width="87"> | |||
IBM Internal Use Only | |||
1.0 Microsoft Windows Applications | |||
Editor's Note | |||
This component of the product was being extensively worked at the time of | |||
writing, and no firm information was available. The subject must be thor- | |||
oughly researched and documented prior to publication. | |||
OS/2 V2 provides the capability for Microsoft Windows applications to run under | |||
OS/2 V2. This support allows applications written for Windows 3.0 and previous | |||
versions of Windows to coexist and execute in the same machine under OS/2 V2. | |||
Each Windows application executes as a protected mode process. As such, | |||
Windows applications are subject to the same application protection facilities | |||
provided to other protected mode applications (both OS/2 and MVDM tasks) | |||
under OS/2 V2. Windows applications are protected from other Windows appli- | |||
cations and from DOS and OS/2 applications executing in the system. This is in | |||
contrast to the native Windows 3.0 environment, where protection is limited to | |||
Windows 3.0 applications only. | |||
The execution of Windows applications as protected mode tasks also allows | |||
these applications to take full advantage of the pre-emptive multitasking capabili- | |||
ties of OS/2 V2, with full pre-emptive multitasking between Windows applications, | |||
OS/2 applications and DOS applications. This is again in contrast to the native | |||
Windows 3.0 environment, where pre-emptive multitasking is available only when | |||
Windows 3.0 is running in enhanced mode, thereby impacting performance and | |||
preventing many applications written for previous versions of Windows from exe- | |||
cuting. OS/2 V2 has no such restriction. Windows applications running under | |||
OS/2 V2 will run in a mode equivalent to the real or standard modes of Windows | |||
3.0. The enhanced mode of Windows 3.0 is not required since OS/2 V2 operating | |||
system itself provides equivalent function. | |||
1.1 The Windows Environment | |||
Microsoft Windows 3.0 application support is provided by default during the | |||
installation of OS/2 V2. Should the user select Selective Install at time of installa- | |||
tion and highlight DOS + Windows Environment, then all the files necessary to | |||
provide Windows Application support will be installed in the following subdirecto- | |||
ries: | |||
? \OS2\MDOS\WINOS2 | |||
? \OS2\MDOS\WINOS2\SYSTEM | |||
OS/2 V2 CONFIG.SYS will be updated to include these directories in the PATH | |||
statement; MVDM (Multiple Virtual DOS Machine) support is also installed. | |||
Windows REAL Mode requires 640Kb of Conventional memory and several MB of | |||
Expanded memory (EMS). The EMS VDD (Virtual Device Driver) is also required. | |||
Windows STANDARD Mode requires that the following statements be included in | |||
the OS/2 2.0 CONFIG.SYS file: | |||
? DEVICE=C:\OS2\MDOS\VDPMI.SYS (DOS Protect Mode Interface) | |||
+ Copyright IBM Corp. 1991 1-1 | |||
IBM Internal Use Only | |||
? DEVICE=C:\OS2\MDOS\VDPX.SYS (DOS Extender Virtual Device Driver). | |||
If these device drivers are not loaded, Windows will execute in REAL Mode. | |||
Windows can use Expanded Memory which conforms to the LIM EMS 4.0 specifi- | |||
cation when running in REAL Mode. This memory is primarily used for storing | |||
background applications. An appropriate Expanded Memory Manager must be | |||
installed. Windows Applications can however use a LIM EMS 3.2 Expanded | |||
Memory manager to store data in memory. In STANDARD Mode, Windows will | |||
use Extended Memory. | |||
Upon completion of the installation process the user will be given the opportunity | |||
to migrate installed Windows Applications to the OS/2 V2 Workplace Shell. | |||
All Windows Applications which are migrated, will have the appropriate DOS and | |||
Windows Settings established, as defined in the Certified Application Database | |||
(shipped as a standard component of OS/2 2.0). | |||
Editor's Note | |||
The Certified Applications Datbase is currently under development. This | |||
aspect must be tested, once available. The procedures involved in updating | |||
this database must be investigated. | |||
1.1.1 The Certified Applications Database (CAD) | |||
The Certified Applications Database provides the vehicle to automatically set the | |||
DOS Property settings for both certified DOS and Windows applications. The user | |||
will be presented with a list of the certified applications found, which can be | |||
migrated. The user may select any or all of these applications. The CAD will be | |||
searched for each of the selected applications. The DOS and/or Windows proper- | |||
ties information found in the database will be used to automatically assign set- | |||
tings to the applications. Windows applications will be placed in a single | |||
Windows Folder. DOS applications are placed in a single DOS Applications | |||
Folder. | |||
Note only the property settings for applications which differ from the default set- | |||
tings will be held in the database. | |||
DOS Settings information for DOS applications will be stored in the OS2.INI file. | |||
Windows applications' settings are stored in the WIN.INI file. | |||
Note | |||
Only the settings for those applications which have been certified via | |||
approved IBM testing channels will be recorded in the Certified Applications | |||
Database (CAD). | |||
The CAD will be a binary database generated from an ASCII database and a pre- | |||
defined tag file. Each field in the ASCII database will start with a descriptive tag | |||
that is associated with a value between 0-225 in the predefined tag file. When the | |||
binary CAD generation tool encounters one of the descriptive tags, it will gen- | |||
erate an entry in the binary CAD with a 0-255 value specified in the predefined | |||
1-2 VMBOOT | |||
IBM Internal Use Only | |||
tag file. To add new or additional DOS properties, a short descriptive tag is | |||
created for the ASCII file and associated with an unused value between 0-255 in | |||
the predefined tag file. A length specification is also provided for the value in the | |||
tag file. | |||
Each field in the binary CAD starts with a predefined tag value of 0-255 that iden- | |||
tifies the field. This tag is followed by a "size" field, which in turn is followed by | |||
the actual value of the field. The maximum number of tags is 256. | |||
Each application in the CAD will have the following minimum information: | |||
? The filename used to start the application | |||
? A next application pointer | |||
? The title of the application. | |||
The filename that starts the application is used to identify the application on the | |||
hard drive. The next application pointer points directly to the next application | |||
entry in the CAD. This provides the ability to jump from one entry to the next | |||
without parsing all of the tags between entries in the CAD. The application title is | |||
displayed to the user if the application is found on the hard drive. The user will | |||
use this information to specify if the application is to be migrated. | |||
The filename extensions held in the CAD will determine what files are searched | |||
for, that is all .EXE, .COM and .BAT files. | |||
1.1.2 Single Application and Multiple Application VDMs | |||
Two Windows environments are supported: | |||
? SAVDMs (Single Application VDMs) which contain a single Windows Applica- | |||
tion. The icon supplied with the Windows Application will be defined in the | |||
SAVDM. | |||
? | |||
MAVDMs (Multiple Application VDMs). This activates the Windows Program | |||
Manager, allowing the user to access a number of Windows Applications. | |||
Each SAVDM will indicate the Windows execution mode based on the file type | |||
specified in the *.EXE header of the Windows Application. REAL Mode will be | |||
indicated for non-Windows 3.0 applications. Auto-Select (Real or Standard mode) | |||
is selected, based on processor type. | |||
The following components of Microsoft Windows 3.0 will be supported and are | |||
available within the OS/2 2.0 kernel: | |||
? Windows Real Mode kernel (WINOS2.COM and KERNEL.EXE) | |||
? Modified Windows Standard Mode kernel (OS2K286.EXE) | |||
? Modified DOS Extender (OS2DOSX.EXE) | |||
? Print Manager (Spool Function) | |||
? Program Manager: | |||
?Permit the starting of multiple Windows Applications in a VDM | |||
?Permit switching between Windows Applications in the VDM | |||
? Help Manager | |||
Microsoft Windows Applications 1-3 | |||
IBM Internal Use Only | |||
? Video Device Drivers | |||
? Keyboard, Mouse and Communications Device Drivers | |||
? TaskManager | |||
? Windows User and GDI DLLs | |||
? Printer Device Drivers | |||
? Clipboard support | |||
? Control Panel with functions limited to: | |||
?Printer Install | |||
?Color | |||
?Fonts | |||
?Sound | |||
?Mouse | |||
?International | |||
?Date/Time | |||
?KBD (Keyboard rate). | |||
The Clock program and Recorder Utility (Create/Recall keystroke macros) are | |||
available in Fullscreen Windows - (MAVDM) Multiple Application Virtual DOS | |||
Machine. | |||
Note | |||
1. Microsoft Windows 386 Enhanced Mode is not supported | |||
2. Microsoft Windows Multi-Media extensions are not supported. | |||
The following Microsoft Windows 3.0 components are not included within the | |||
OS/2 kernel, as OS/2 equivalents are provided, or are not required within an | |||
OS/2 environment: | |||
? File Manager | |||
? Systems Editor (SYSEDIT) | |||
? Games | |||
? Write | |||
? Terminal | |||
? Notepad | |||
? Cardfile | |||
? Calendar | |||
? Calculator | |||
? PIF Editor | |||
? Paintbrush | |||
? | |||
Wallpaper bitmaps | |||
1-4 VMBOOT | |||
IBM Internal Use Only | |||
? Setup (Windows' Installation and Configuration changes). | |||
1.2 Defining Windows Applications | |||
Figure 1-1. Program Reference Object's Setting Notebook. | |||
+-----------------------------------------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+-----------------------------------------------------------+ | |||
The Windows application execution environment is defined in the Program Page | |||
of the program reference object's settings notebook. The Windows Application | |||
name is entered as the Path and Filename. This entry will cause DOSQAppType | |||
to be issued to determine the application type. The Program Type in the Mode | |||
Page will be set to Windows Full Screen. A "Windows" page will appear for the | |||
Windows application containing a New Windows Setting. This defines whether | |||
the Windows kernel will execute in REAL, Standard, or Auto-Select mode. REAL | |||
mode is highlighted as the default if the Windows application is NOT a Protect | |||
mode Windows application, otherwise AUTO-SELECT is the default. All DOS set- | |||
tings are selectable for Windows applications via the Windows page, Windows | |||
settings are also included in the same list. | |||
Changes are effective immediately and are saved when the Settings Notebook is | |||
closed or when the system is shut down. The Reset Button resets to the previous | |||
settings. | |||
The Windows application is started by double-clicking on the icon within the | |||
folder. The application executes in the VDM in which it was defined. | |||
Microsoft Windows Applications 1-5 | |||
IBM Internal Use Only | |||
Operation | |||
The SAVDM is created for the execution of the Windows application. The | |||
Workplace Shell starts WINOS2.COM as the application to start in the VDM. | |||
The Windows Application to be executed is passed as a parameter to | |||
WINOS2. This process is transparent to the user. If the application is | |||
launched from an OS/2 Command Prompt, the user will notice the VDM being | |||
launched as the DOS prompt is momentarily displayed before the Windows | |||
application is launched. | |||
If WINOS2 is to execute in REAL Mode, the /r option will be inserted into the | |||
parameter list for the VDM creation, based on the WIN Setting. If STANDARD | |||
Mode was highlighted, /s is passed as a parameter to WINOS2. The default is | |||
to pass no Windows options, just the application name. | |||
When the Windows Application is terminated, WINOS2.COM terminates | |||
causing the VDM to be terminated. | |||
Each SAVDM will have an icon on the Desktop, for the application within the | |||
SAVDM. This icon will be the Windows icon for this application. The icon title will | |||
be the text specified in the Program Title field of the New Program dialog. | |||
Editors Note | |||
Check to ensure that the Windows Application icon is used and that the | |||
SAVDM does not display the default DOS icon. | |||
Ctrl-Esc is the key combination used to display the Task List. | |||
Alt-Esc is the key combination used to switch to the next session as defined in | |||
the Workplace Shell. | |||
In the case of MAVDM (Windows Application Group), the Windows Program | |||
Manager is loaded in the MAVDM transparently to the user. Applications are | |||
launched from the Windows Program Manager. Here the Task List will display | |||
the Windows Application currently executing in this VDM. | |||
Ctrl-Esc is used within the VDM to display the Task List. | |||
Alt-Esc is used to switch to the next session defined in the Workplace Shell. | |||
The Workplace Shell icon will represent the Windows VDM, not the application(s) | |||
executing within the VDM. | |||
The user must select Exit Windows in the Windows Programs Manager to termi- | |||
nate the VDM, or close the VDM from the Workplace Shell. | |||
The following applications are already started (iconized) on first entry into the | |||
VDM for both SAVDMs and MAVDMs: | |||
? Modified Windows Clipboard Viewer Program | |||
? DDE Server/Agent Application | |||
1-6 VMBOOT | |||
IBM Internal Use Only | |||
? Recorder (not started in MAVDM) | |||
? Presentation Manager icon | |||
? Task Manager (no icon) | |||
? Windows Program Manager (not visible in a SAVDM) | |||
? Clock (Iconized, MAVDM only) | |||
? Windows Control Panel (not started, MAVDM only). | |||
1.3 Launching Windows Applications in OS/2 2.0 | |||
The following methods may be used to start Windows Applications: | |||
1. Select the Application name from within File Manager | |||
2. Enter the Application name at an OS/2 Command line prompt | |||
3. Install the application in a folder, in the Workplace Shell Desktop. | |||
If the application is started from either the OS/2 File Manager or an OS/2 | |||
command prompt, an SAVDM will be created. If the Application is started from | |||
an icon, either a SAVDM or a MAVDM will be created, depending on how the | |||
application was defined at installation. | |||
When a MAVDM icon is selected, a Windows VDM will be created with the | |||
Windows Program Manager maximized. The user may then elect to start any | |||
Windows applications within the VDM via the Windows Program Manager. The | |||
user may also define a group of Windows applications which will be activated | |||
when this VDM is started. These applications are specified in the Parameters | |||
field of the of the New Program Dialog. Full path name and parameters should | |||
be specified. | |||
The syntax for the parameters field is: | |||
/R|/S 詛~?|泘 App1 App-parms ?~ | |||
?|洺 App2 App-parms | |||
? /R Windows REAL Mode | |||
? /S Windows Standard Mode | |||
? Optional Parameters ? ~ | |||
? | |||
! Start the Windows Application Minimized | |||
? | |||
?Start the Windows Application Maximized. | |||
If neither the Exclamation Mark nor the Caret is specified, the Windows Applica- | |||
tion will start Normalized, approximately one third the screen size. | |||
A MAVDM will be created if one of the following are present: | |||
? {} Braces | |||
? | |||
Comma separating the application names | |||
? An Application Name is not passed as a parameter. | |||
Microsoft Windows Applications 1-7 | |||
IBM Internal Use Only | |||
1.4 Windows Device Drivers and Environment Settings | |||
A WIN.INI file is built during OS/2 installation. The options for the devices | |||
selected for the OS/2 environment are included in this file. | |||
Should the user migrate from a Windows 3.0 environment, the Windows WIN.INI | |||
will be left unchanged. WINOS2 will look in C:\OS2\MDOS\WINOS2 subdirectory | |||
for the correct WIN.INI file. The initial WIN.INI file in the WINOS2 subdirectory is | |||
created from the Windows WIN.INI. | |||
The following initialization files are created (including the WIN.INI file): | |||
? PROGMAN.INI | |||
? CONTROL.INI | |||
? SYSTEM.INI. | |||
1.4.1 WIN.INI | |||
WIN.INI contains a number of sections which may be customized by the user, | |||
including which applications should be started or run, when Windows is started. | |||
Each Windows Application is recorded in a separate section indicating the drive | |||
and path to execute the application. The supported file extensions for each appli- | |||
cation installed, are recorded in the Extensions section. | |||
1.4.2 PROGMAN.INI | |||
PROGMAN.INI contains the Program Manager settings, the following sections are | |||
included: | |||
? Setting: Describes the settings of the Program Manager, the user's prefer- | |||
ence | |||
? Groups: Specifies the Program Groups that exist in Program Manager. | |||
1.4.3 CONTROL.INI | |||
CONTROL.INI contains the color and desktop settings for the Control Panel. The | |||
following options are available: | |||
? | |||
Current: Specifies the Window color setting | |||
? Color Schemes: Specifies the available color options | |||
? Custom Colors: Specifies up to 16 customization colors | |||
? Patterns: Specifies options for the Desktop pattern. | |||
1.4.4 SYSTEM.INI | |||
SYSTEM.INI contains the global system information used by Windows when it | |||
starts. Changes are not effective until Windows is restarted. | |||
The following sections are included: | |||
? Boot: Lists the drivers and Windows modules. The OS/2 file contains a sepa- | |||
rate Boot section which covers MAVDM and SAVDM default applications: | |||
?GOPM This program returns the user to the Workplace Shell | |||
?Clock The Windows clock program | |||
1-8 VMBOOT | |||
IBM Internal Use Only | |||
?Clipbrd The modified Clipboard program | |||
?DDEAGENT The modified DDE (Dynamic Data Exchange) program | |||
?Printman: MAVDM only, the Printer Manager program | |||
? Boot.description: Lists the names of devices the user can change using | |||
Windows Setup | |||
? Keyboard: Contains information about the keyboard | |||
? NonWindowsApp: This section should not contain any information, non | |||
Windows Applications are started from the OS/2 desktop | |||
? Standard: Contains information required by Windows to run in Standard | |||
Mode | |||
? 386Enh: Contains information used by Windows to operate in 386 Enhanced | |||
Mode. This section is not used as OS/2 provides equivalent function. | |||
The Initialization and Group files are required to restore a corrupted Windows | |||
environment. Backups of these files should be taken prior to making any | |||
changes to this environment. | |||
Note | |||
The Windows 3.0 APIs will access the new WIN.INI file. | |||
The WIN.INI file is updated by Install and OS/2 Print Manager. | |||
The WIN.INI file is updated with the appropriate information for the following | |||
options. Installation will install the Windows Device Driver files in the appropriate | |||
directories. | |||
? Keyboard | |||
? Mouse | |||
? Video | |||
? Printer | |||
? Codepage. | |||
If a device driver (Video, Mouse, Keyboard) is supported in Windows and NOT | |||
supported by OS/2, the Windows version will not be supported. | |||
Install will update the new WIN.INI file to include the printer device driver details | |||
that Windows requires for printers selected under OS/2. Install selects a | |||
Windows printer device driver comparable with an OS/2 printer device driver. | |||
The Windows printer device driver will operate in its default mode. If the printer | |||
device driver needs to be configured in a mode other than the default mode, the | |||
printer should be configured from within the Windows Control Panel. | |||
If there is no equivalent OS/2 printer device driver, the device driver should be | |||
installed and configured via the Windows Control panel. | |||
Microsoft Windows Applications 1-9 | |||
IBM Internal Use Only | |||
Note | |||
At the time of writing this facility/function could not be tested | |||
1-10 VMBOOT | |||
IBM Internal Use Only | |||
2.0 Dynamic Data Exchange (DDE) | |||
This chapter describes DDE support between Windows Applications in a full | |||
screen VDM. | |||
DDE is a message protocol for dynamic data exchange between Windows pro- | |||
grams. Data may be shared among applications, the intention being to create an | |||
integrated Windows environment. | |||
The native Windows environment supports the following mechanisms which | |||
applications can use to exchange data: | |||
? Clipboard transfers | |||
? Dynamic link libraries | |||
? Dynamic Data Exchange (DDE). | |||
Note | |||
DDE is the only mechanism that supports passing of Global Memory Handles | |||
between applications. | |||
2.1 Clipboard Transfers | |||
The Clipboard acts as a temporary repository of information. This process | |||
requires the direct involvement of the user to initiate and complete the data | |||
transfer process. | |||
2.2 Dynamic Link Libraries (DLL) | |||
A DLL can be designed to act as repository for data being shared between appli- | |||
cations. The data is stored in the static data area of the DLL's data segment. | |||
2.3 Data Exchange in Windows | |||
Windows is a Message-based Architecture and message passing is used to | |||
transfer information between applications. | |||
Windows messages however contain only two parameters, wParam and lParam | |||
for passing data. The DDE protocol defines how these message parameters will | |||
be used to pass large amounts of data by means of Global atoms and Global | |||
shared memory handles. | |||
A Global atom is a reference to a character string and is used to identify: | |||
? The applications exchanging data | |||
? The nature of the data being exchanged | |||
? | |||
The data items. | |||
+ Copyright IBM Corp. 1991 2-1 | |||
IBM Internal Use Only | |||
A Global shared memory handle is a handle to a block of allocated memory. | |||
Global shared memory objects store data items passed between applications, | |||
protocol options and remote execution strings. | |||
2.3.1 DDE Concepts | |||
Client, Server and Conversation: | |||
Two applications participating in dynamic data exchange are engaged in a DDE | |||
Conversation. The application that initiates the conversation is the Client Appli- | |||
cation. The application which responds to the client is the Server Application. | |||
An application may be engaged in several conversations at the same time, | |||
acting as a client in some applications and as a server in others. A DDE conver- | |||
sation takes place between two windows, one for each of the participating appli- | |||
cations. The window may be the main window of the application, a sub-window | |||
associated with the application, or a hidden window. The hidden window is used | |||
to process DDE messages. | |||
DDE identifies the units of data passed between the client and server with a | |||
three-level hierarchy of: | |||
? Item | |||
? | |||
Topic | |||
? Application Name. | |||
Each DDE conversation is uniquely identified by the application name and topic. | |||
The application name is normally the name of the server application. The topic is | |||
a general classification of data, within which multiple data items may be | |||
exchanged during the conversation. The item is the actual information related to | |||
the conversation topic that is exchanged between the applications. Values for the | |||
data item can be passed from the server to the client, or from client to server. | |||
The format of the data item may be any one of the clipboard formats. | |||
2.3.2 Permanent Data Links | |||
Once the DDE conversation has been initiated, the client can establish one or | |||
more permanent data links with a server. A data link is a communication mech- | |||
anism by which the server notifies the client whenever the value of a given data | |||
item changes. | |||
The link is permanent in the sense that the notification process continues until | |||
the data link or DDE conversation is terminated. | |||
The DDE link may be WARM or HOT. In a warm data link, the server notifies the | |||
client that a value of a given data item has changed, but the server does not | |||
actually send the data value to the client until the client requests it. In a hot data | |||
link, the server immediately sends the changed data value to the client. | |||
Applications which support DDE, typically provide a Copy/Paste Link command in | |||
the Edit menu to allow the user to establish a DDE link. | |||
2-2 VMBOOT | |||
IBM Internal Use Only | |||
2.4 OS/2 DDE Support in Fullscreen VDM | |||
In a native Windows 3.0 environment, a Windows Application (Client) will send a | |||
broadcast DDE Initiate message. Windows serially posts a message to every | |||
Windows Application currently running and then awaits a reply. As described | |||
above, the Initiate conversation message contains the DDE topic to which any | |||
Windows application can respond. The Client application continues execution | |||
when all other applications have serviced their message. At this time the Client | |||
application communicates directly with the Server applications, as opposed to | |||
the initial broadcast message. | |||
OS/2 provides two applications to support communications between VDMs, | |||
without altering the Windows code: | |||
1. A resident Windows application referred to as the DDE ServerAgent (SA) | |||
2. A DOS Protect Mode application referred to as the DDEServer | |||
(VDMSRVR.EXE). | |||
2.4.1 ServerAgent | |||
The Windows VDM resident ServerAgent consists of two parts: | |||
? A "ServerAgent" which sends and receives messages outside of the VDM | |||
? One or more "Agents" (each agent is a child window of the ServerAgent), | |||
which act as clones of applications running in other VDMs. | |||
DDE will not be available outside of the VDM, if either the DDEServer or the | |||
VDM's ServerAgent is not executing. The ServerAgent is automatically started | |||
when the Windows VDM is started. | |||
p.The ServerAgent provides a user interface with the following pulldown menus: | |||
1. File Menu: | |||
? Exit: The ServerAgent exits, all subsequent DDE is local to the VDM | |||
? Save As: The contents of the internal trace log buffer is written to the | |||
named file. | |||
2. Options Menu: | |||
? Trace: When selected this option traces and displays all DDE transactions | |||
taking place outside of the VDM. The default is No Trace/Display. Once | |||
enabled, this option remains in effect until explicitly disabled. | |||
? Public DDE: If selected, DDE communicates outside of the confines of the | |||
VDM. If not selected, DDE is local to the VDM. The default is Public DDE. | |||
Should the user choose to exit from the DDE Interchange Agent, an information | |||
message will be displayed indicating that DDE activity will be visible only to the | |||
Windows applications executing in the current VDM, discontinuing DDE commu- | |||
nication between Presentation Manager applications and other Windows applica- | |||
tions. | |||
The ServerAgent is responsible for all routing of DDE messages, including | |||
broadcast messages beyond the confines of the VDM to the DDEServer. The | |||
ServerAgent communicates to the DDEServer via named pipes. | |||
Dynamic Data Exchange (DDE) 2-3 | |||
IBM Internal Use Only | |||
Agent applications communicate with Windows applications in their VDM and the | |||
ServerAgent executing in their VDM. Only the ServerAgent uses named pipes. | |||
Agents send requests to the ServerAgent to be forwarded outside of the VDM. | |||
2.4.2 DDEServer | |||
The DDEServer is responsible for routing requests from ServerAgents to the | |||
appropriate VDMs. The DDE process is schematically represented below: | |||
�葺葺葺葺葺葺葺葺葺葺葺葺葙 | |||
� Windows Application A � | |||
� SAVDM � | |||
�葺葺葺葺葺?葺葺葺葺葺葺? | |||
�葺葺葺葺莨葺葺葺葺葺葺葙 | |||
1. � DDE Initiate Message � | |||
�葺葺葺葺?葺葺葺葺葺葺? | |||
�葺葺葺葺馆葺葺葺葺葺葺葙 �葺葺葺葺葺葺葺葺葙 | |||
� DDE ServerAgent App A 谳葺葺 4 葺葺葺?Child Window � | |||
�葺葺葺葺�葺葺葺葺葺�葺? �葺葺葺葺葙 � Agent for App D � | |||
2. �葺馆葺葺葙 �葺葺葺� � �葺葺葺葺�葺葺葺葺� | |||
�葺葺葺莼DDEServer谳葺葺葺葺葺葺葺葺? 3 � | |||
� �葺葺葺�葺� (Named Pipes) � � 5 | |||
�葺葺馆葺葺葺葙 �莨葺葺葺葺葺葺?�葺葺莨葺馆葺葺? � | |||
� ServerAgent � � ServerAgent � � ServerAgent � � | |||
� App B � � App C � � App D 谳葺? | |||
�葺葺葺葺葺葺? �葺葺葺葺葺葺葺� �葺葺葺�葺葺葺? | |||
6 | |||
�葺葺葺莨葺葺葺葺葙 | |||
� Child Window � | |||
� Agent for App A � | |||
�葺葺葺葺葺葺葺葺? | |||
Figure 2-1. DDE Process | |||
1. A DDE Initiate Message is broadcast from Windows Application A. | |||
2. The message is forwarded by the ServerAgent to the DDEServer, which in | |||
turn forwards the message to every Windows Application SeverAgent. | |||
3. ServerAgent for Windows Application D responds affirmatively to the DDE | |||
Initiate message. This response is forwarded back to the ServerAgent for | |||
Application A. This response includes the Windows Application handle and | |||
the VDM handle of the VDM running Windows Application D. | |||
4. The ServerAgent in Windows Application A creates a Child Task which | |||
serves as the Agent for Windows Application D. | |||
5. The Agent forwards the data to Windows Application D. | |||
6. When Windows Application D responds, the ServerAgent D creates a Child | |||
Window which acts as an Agent for Windows Application A. The response is | |||
forwarded by the application to the Agent, which in turn forwards the data to | |||
the ServerAgent for Application D. | |||
7. The ServerAgent for Windows Application D routes the DDE data to the | |||
DDEServer. The DDEServer determines which VDM this "DDE Packet" is des- | |||
tined for and forwards it to the ServerAgent for Windows Application A. | |||
2-4 VMBOOT | |||
IBM Internal Use Only | |||
Note | |||
If two Windows Applications require significant amounts of DDE, these appli- | |||
cations should be executed from within the same MAVDM, in this instance | |||
the ServerAgent and DDEServer applications would not be required, | |||
improving performance and usability. | |||
2.5 OS/2 DDE Environment | |||
Existing DDE support between PM Applications remains essentially unchanged. | |||
DDE support between Windows Applications and Presentation Manager Applica- | |||
tions requires that the DDEServer be linked with the Presentation Manager DDE | |||
APIs, both DDE messages and data formats are translated during the data | |||
exchange between the PM session and any given VDM running a Windows Appli- | |||
cation. This process consists of a Protect Mode DDEServer, a Windows DDE | |||
ServerAgent, as described above, and a PM DDE ServerAgent. The PM DDE | |||
ServerAgent is a mirror to the Windows DDE ServerAgent. The ServerAgent is | |||
responsible for routing all DDE messages beyond the confines of Presentation | |||
Manager to the DDEServer. The ServerAgent communicates with the DDEServer | |||
via named pipes. | |||
The following data formats will be translated between the PM environment and | |||
the Windows environment: | |||
? Bitmaps: Windows DIB to/from OS/2 BITMAPINFO2 and PM BITMAPINFO | |||
to/from Windows DIB format. | |||
? Windows Device Dependent Bitmaps: Pre-Windows 3.0 format to Windows | |||
DIB format to/from PM BITMAPINFO. | |||
? Windows Metafiles: Metafiles are converted to Window DIB format prior to | |||
being translated as above. | |||
? Text: Codepage translation is provided in both directions. | |||
The PM DDE ServerAgent will reside in a Productivity Folder as a Utility. Where | |||
there is a demand to provide DDE support between PM Applications and | |||
Windows Applications, the PM DDE ServerAgent should be placed in a | |||
WorkPlace Startup Folder. The DDE ServerAgent runs ONLY as a minimized | |||
icon. To shutdown global DDE, the PM DDE ServerAgent must be terminated | |||
through the Window List. | |||
Where DDE is only used between PM applications, the DDEServer should be | |||
deactivated to improve performance. | |||
Schematically the DDE process between PM Applications and Windows Applica- | |||
tions may be represented as follows: | |||
Dynamic Data Exchange (DDE) 2-5 | |||
IBM Internal Use Only | |||
Figure 2-2. DDE Process PM and Windows. | |||
�葺葺葺葺葺葺葺葺葺葙 �葺葺葺葺葺葺葺葺葺葺葺葺葙 | |||
� PM DDE Application� � Windows DDE Application � | |||
�葺葺葺葺�葺葺葺葺葺� �葺葺葺葺葺葺葺葺葺葺葺?? | |||
�葺葺葺葺? �葺葺葺葺葺葺葺葺葺葺葺? � | |||
� � DDE Initiate Message � � | |||
� � or � � | |||
� � DDE Conversion � � | |||
� �葺葺葺葺?葺葺葺葺葺葺� � | |||
� �葺葺葺葺葺葺葺葺莨葺葺葺葺葺葺葺? � | |||
� �葺葺葺馆葺葺葺葺? �葺葺葺馆葺葺葺葺? � | |||
�莼 DDE ServerAgent� � DDE ServerAgent谳? | |||
�葺葺葺�葺葺葺葺? �葺葺葺�葺葺葺葺? | |||
�莨葺葙 �莨葺葙 | |||
�Agent� �Agent� | |||
�?葺? �?葺? | |||
� �葺葺葺葺葺葺? � | |||
�葺葺葺葺葺莼 Named Pipes谳葺葺葺� | |||
�葺葺?葺葺葺� | |||
� | |||
� | |||
�葺葺馆葺葙 | |||
�DDEServer� | |||
�葺莨葺葺葺葺莨葺? | |||
�Data Translation� | |||
�葺葺葺葺葺葺葺葺� | |||
2.6 Object Linking and Embedding (OLE) | |||
Note | |||
As at OS/2 Driver 6.163 OLE is not available. | |||
Check to confirm whether OLE is planned for OS/2 2.0 or a later | |||
release/upgrade | |||
Object Linking and Embedding (OLE) focuses on document formats rather than | |||
an application's ability to exchange data - the DDE approach. OLE defines a | |||
format for compound documents, which contain multiple forms of data. The data | |||
formats are understood and managed by multiple applications. The application | |||
uses various combinations of data to construct a Compound Document. | |||
The concepts used in OLE are best described by contrasting them with the | |||
approach adopted by Clipboard and DDE. | |||
When using the Clipboard, an application obtains data from another application | |||
in a standard format, usually ASCII, a Bitmap or a Metafile. This data exists only | |||
as data, there is no link with the application that originally placed the data in the | |||
Clipboard. | |||
When using DDE, an application also obtains data from another application in a | |||
standard format, ASCII, Bitmap or Metafile. The Client can however establish | |||
and maintain a link with the application that delivered the data. Should the data | |||
change in the Server application, the Client application's data is also updated. | |||
2-6 VMBOOT | |||
IBM Internal Use Only | |||
OLE also enables an application to obtain data from another application; in this | |||
instance the data can be in two formats: | |||
? One format is understood only by the application sending the data | |||
? The Display format (ASCII, Bitmap or Metafile) for the receiving application to | |||
display on the screen. | |||
The significance of this approach may be appreciated by way of an example: | |||
Voice annotation may be attached to a Word Processing application, the Word | |||
Processing application need not have any facility to support or manage voice. | |||
The Word Processor will store the data in two formats - the digitized sound and | |||
a display format (an icon). When the icon is selected in the document, the Voice | |||
application is invoked and the Word Processing application passes the digitized | |||
sound to the Voice application, which then plays the sound. | |||
Dynamic Data Exchange (DDE) 2-7 | |||
IBM Internal Use Only | |||
2-8 VMBOOT | |||
IBM Internal Use Only | |||
3.0 OS/2 Clipboard Support | |||
OS/2 V2 provides Clipboard support between Windows applications in the same, | |||
or separate VDMs, as well as support between Windows Applications and OS/2 | |||
Applications. | |||
The Clipboard serves as a data-exchange feature acting as a common area to | |||
store data handles through which applications exchange formatted data. The | |||
same data may be represented in a number of different formats as specified by | |||
the application. Note that Clipboard objects may be of any size and format. | |||
Data is formatted in either a predefined or private format, before being copied to | |||
the Clipboard. In most cases the data is copied to pre-allocated global memory | |||
and a function call is used to copy the memory handle to the clipboard. | |||
Windows provides a number of predefined data formats: | |||
TEXT Null-terminated text | |||
OEMTEXT Null-terminated text using an OEM character set | |||
METAFILEPICT Metafile-picture structure | |||
BITMAP Device dependent bitmap | |||
DIB Device independent bitmap | |||
SYLK SYLK Standard data interchange format | |||
DIF DIF standard data interchange format | |||
TIFF TIFF standard data interchange format | |||
The OwnerDraw feature in the Windows Clipboard is only supported within a | |||
MAVDM, as shared memory is required. OwnerDraw is a process whereby a | |||
Windows Application takes control over the appearance of menu items and has | |||
responsibility for managing these menu items. | |||
The native Microsoft Windows 3.0 Clipboard provides support for both Windows | |||
applications and non-Windows applications. Non-Windows applications run in | |||
either fullscreen or "windowed" mode. Windowed mode requires that Windows | |||
run in 386 Enhanced mode, this mode is not supported under OS/2 V2. In REAL | |||
or STANDARD modes, non-Windows applications run in fullscreen mode only. | |||
386 Enhanced Mode is a mode which Windows 3.0 runs in to access the virtual | |||
memory capabilities of the Intel 80386 processor, to use more memory than is | |||
physically available and to provide multitasking capabilities for non-Windows | |||
applications. | |||
OS/2 V2 fully exploits the functions provided by the Intel 80386 processor, hence | |||
there is no need to support this mode under OS/2 V2. Moreover, because DOS | |||
applications may be run in a DOS Window (VDM), full Clipboard support is avail- | |||
able. | |||
Should the user wish to capture the contents of a VDM running in fullscreen | |||
mode, the following approach is adopted: | |||
1. Switch to the PM Screen containing the VDM | |||
+ Copyright IBM Corp. 1991 3-1 | |||
IBM Internal Use Only | |||
2. Select the System menu on the VDM icon | |||
3. Select Copy All. | |||
This procedure should copy the VDM's video buffer to the PM Clipboard (ASCII | |||
or PM Bitmap). | |||
Note | |||
Selective Copy is available in window'ed mode | |||
3.1 Windows Clipboard Support | |||
The Windows Clipboard view utility will display the captured data in a number of | |||
formats, either predefined or private. Auto displays the data in the format it had | |||
when placed onto the clipboard. | |||
The Clipboard Viewer program (CLIPBRD.EXE), installed in | |||
C:\OS2\MDOS\WINOS2, is available within each SAVDM and MAVDM by default. | |||
This is a modified version of the original Windows 3.0 Clipboard program. | |||
A Clipboard Server (Global Clipboard) runs as a Protect Mode background | |||
process to service clipboard functions between VDMs. If the Clipboard Server is | |||
not executing, clipboard functions are limited to that single VDM. The global | |||
VDM server is started from the CONFIG.SYS file at system boot: | |||
RUN=C:\OS2\MDOS\WINOS2\VDMSRVR.EXE | |||
Should a user elect to exit from the Windows Clipboard, a warning message will | |||
be displayed advising that exit will terminate public clipboard functions. The | |||
Clipboard functions within each VDM are public by default, unless expressly set | |||
to LOCAL, which restricts Clipboard activity to that Windows session only. | |||
The Windows Clipboard viewer pulldown menus have been enhanced to include | |||
support for an Options Menu, which contains the Public Clipboard option. | |||
Selecting this option causes changes to the Local clipboard to be reflected in the | |||
Public clipboard and vice versa. When deselected the contents of the Public clip- | |||
board and Local clipboard will not affect each other. | |||
The File pulldown menu now supports Import/Export functions; PUBLIC must be | |||
deselected from the Options pulldown menu before Import/Export can be | |||
selected. | |||
Implementation Notes | |||
The Import/Export functions communicate via named pipes to the | |||
\pipe\CLPAgent to the Clipboard program (CLIPBRD.EXE) within each VDM. | |||
Export will copy the current contents of the Local clipboard to the Public clip- | |||
board. | |||
Import will copy the contents of the Public clipboard to the Local clipboard. | |||
3-2 VMBOOT | |||
IBM Internal Use Only | |||
3.2 Using Cut and Paste | |||
The following three scenarios describe the clipboard functions: | |||
1. Cut and Paste from a Windows Application in a VDM to another application | |||
in a separate VDM - PUBLIC is deselected. | |||
2. Cut and Paste between two Windows applications within the same VDM | |||
(MAVDM) | |||
3. Cut and Paste between the OS/2 and Windows environments. Cut and Paste | |||
within the OS/2 environment remains essentially unchanged. | |||
3.2.1 Scenario 1 - Cut/Paste Between Windows VDMs | |||
1. CUT the data into the Local Windows VDM Clipboard. | |||
2. Select EXPORT from the Clipboard pulldown menu. The data is copied into | |||
the External Clipboard. | |||
3. Select the VDM containing the destination Windows application. | |||
4. Select IMPORT from the Clipboard pulldown menu. The data is copied from | |||
the external Clipboard into the local Clipboard of the receiving VDM. | |||
5. Paste the data into the destination Windows application. | |||
3.2.2 Scenario 2 - Cut/Paste Within A MAVDM | |||
1. CUT the data into the Windows VDM Clipboard | |||
2. PASTE the data from the Clipboard into the destination application. | |||
3.2.3 Scenario 3 - Cut/Paste Between OS/2 And Windows | |||
The OS/2 2.0 Clipboard is activated upon loading the Operating System. A new | |||
OS/2 PM utility, CLIPVIEW.EXE located in the OS2\APPS\ directory has been pro- | |||
vided to support the extended clipboard functions. CLIPVIEW.EXE must be | |||
launched in order to view and transfer the contents of the OS/2 2.0 clipboard. | |||
Excluding the File option of the Windows clipboard, the same pulldown menus | |||
are provided. The RENDER option is the same as the DISPLAY option in the | |||
Windows clipboard. RENDER will display the contents of the clipboard in a | |||
number of different formats. Because the contents of the clipboard are stored in | |||
separate areas in memory, it is possible to view both the ASCII (text) and | |||
graphics contents of the clipboard. | |||
Note | |||
An application may or may not clear the entire contents of the clipboard, | |||
prior to copying data to it. | |||
The Global Windows VDM Clipboard (DPMI Clipboard) is visible to the PM Clip- | |||
board. CLIPVIEW.EXE has been enhanced to perform the following two activities: | |||
1. Update the PM Clipboard when changes are made to the Global VDM Clip- | |||
board | |||
2. Update the the Global Windows VDM Clipboard when changes are made to | |||
the PM Clipboard. | |||
OS/2 Clipboard Support 3-3 | |||
IBM Internal Use Only | |||
The PM Clipboard server application is registered as "clipboard viewer" to | |||
receive notifications of clipboard updates. This ensures that the following mes- | |||
sages are forwarded to the Clipboard Server, so that when updates are made to | |||
the PM Clipboard, messages are sent to the PM CLIPVIEW.EXE. | |||
? WM_DESTROYCLIPBOARD: Signals that the contents of the clipboard are | |||
being destroyed | |||
? WM_DRAWCLIPBOARD: Signals an application to notify the next application | |||
in the chain of a change to the clipboard | |||
? WM_HSCROLLCLIPBOARD: Requests horizontal scrolling of the clipboard | |||
contents | |||
? WM_PAINTCLIPBOARD: Requests painting of the contents of the clipboard | |||
? WM_RENDERALLFMTS: Notifies the owner of the clipboard that it must | |||
render clipboard data in all possible formats | |||
? | |||
WM-RENDERFMT: Notifies the clipboard owner that it must format the last | |||
data copied to the clipboard | |||
? WM_SIZECLIPBOARD: Notifies the clipboard owner that the clipboard appli- | |||
cation's window size has changed | |||
? WM_VSCROLLCLIPBOARD: Requests vertical scrolling of the clipboard con- | |||
tents. | |||
Note | |||
No changes have been made to the PM APIs to accommodate this design. | |||
Data formats are translated from PM to Windows formats and vice versa, as and | |||
when required. This translation is performed when data is placed in the Global | |||
Clipboard. The following data formats will be translated between PM and | |||
Windows: | |||
? | |||
Bitmaps: The Windows DIB to/from OS/2 BITMAPINFO | |||
? Device Dependent Bitmaps: This is a pre-Windows 3.0 format to/from OS/2 | |||
BITMAPINFO | |||
? Windows Metafiles: Metafiles are first converted to WINDOWS DIB format by | |||
the Windows clipboard viewer, before being forwarded to the Global Clip- | |||
board | |||
? Text: ASCII with codepage translation will be translated in both directions. | |||
Schematically the Clipboard process may be represented as follows: | |||
3-4 VMBOOT | |||
IBM Internal Use Only | |||
Figure 3-1. . | |||
�葺葺葺葺葺葺葺葺葺葺? �葺葺葺葺葺葺葺? �葺葺葺葺葙 | |||
�SAVDM Windows App 1.� �SAVDM - App 2.谳葺莼 Windows � | |||
�葺葺葺?葺葺葺葺葺葺� �葺葺葺葺葺葺葺� �Clipboard� | |||
� �葺?葺葺? | |||
�葺葺葺莨葺葺葺葺葙 2. � | |||
1. �Windows Clipboard� � | |||
�葺葺葺?葺葺葺葺? � | |||
�葺葺葺葺葺葺葺葺葙 � | |||
(Named Pipes) � � | |||
�葺葺葺葺莨葺葺葺葺葺葙 � | |||
�DPMI Global Clipboard谳葺葺葺葺葺葺� | |||
� Data Translation � (Named Pipes) | |||
�葺葺葺葺?葺葺葺葺葺? | |||
�葺葺葺葺葙 3. � | |||
� OS/2 谳葺葺葺葺葺葺葺� | |||
�Clipboard� (Named Pipes) | |||
� Server � | |||
�葺葺�葺葺� | |||
� �葺葺葺葺葙 �葺葺葺葺葺葺葙 | |||
� � OS/2 谳葺葺葺?OS/2 PM � | |||
�葺葺葺葺莼Clipboard� �Applications � | |||
�葺葺�葺葺� �葺葺葺葺葺葺? | |||
� �葺葺葺葺葺葺葙 | |||
�葺葺葺葺葺葺籚DM Window'ed� | |||
�Applications � | |||
�葺葺葺葺葺葺? | |||
1. A Windows application (App.1) copies data to the Windows Clipboard. | |||
2. The contents of the Clipboard are available to Windows App.2 via the Global | |||
Clipoard (Clipboard Server). | |||
3. The OS/2 Clipboard Server is registered as a Windows "Clipboard Viewer". | |||
Data is translated into OS/2 formats via the DPMI Global Clipboard and vice | |||
versa as required. | |||
OS/2 Clipboard Support 3-5 | |||
IBM Internal Use Only | |||
Figure Definitions | |||
id File Page References | |||
FIGDEF 3731SU | |||
1-1 | |||
Table Definitions | |||
id File Page References | |||
TDEF 3731SU | |||
1-1 | |||
Figures | |||
id File Page References | |||
3731WI2 3731WIN | |||
3731DD1 1-5 1-1 3731DDE | |||
2-4 2-1 | |||
3731DD2 3731DDE | |||
2-6 2-2 | |||
3731CL1 3731CLIP | |||
3-5 3-1 | |||
Headings | |||
id File Page References | |||
WIN 3731WIN | |||
1-1 1.0, Microsoft Windows Applications | |||
Processing Options | |||
Runtime values: | |||
Document fileid V2-WIN SCRIPT | |||
Document type USERDOC | |||
Document style IBMXAGD | |||
Profile EDFPRF20 Service Level 0018 | |||
SCRIPT/VS Release 3.2.1 | |||
Date 91.10.15 | |||
Time 11:58:22 | |||
Device 3820A | |||
Number of Passes 2 | |||
Index YES | |||
SYSVAR G INLINE | |||
SYSVAR X YES | |||
Formatting values used: | |||
Annotation NO | |||
Cross reference listing YES | |||
Cross reference head prefix only NO Dialog LABEL | |||
Duplex YES | |||
DVCF conditions file (none) | |||
DVCF value 1 (none) | |||
DVCF value 2 (none) | |||
DVCF value 3 (none) | |||
DVCF value 4 (none) | |||
DVCF value 5 (none) | |||
DVCF value 6 (none) | |||
DVCF value 7 (none) | |||
DVCF value 8 (none) | |||
DVCF value 9 (none) | |||
Explode NO | |||
Figure list on new page YES | |||
Figure/table number separation YES Folio-by-chapter YES | |||
Head 0 body text Part | |||
IBM Internal Use Only | |||
Head 1 body text Chapter | |||
Hyphenation YES | |||
Justification YES | |||
Language ENGL | |||
Layout OFF | |||
Leader dots YES | |||
Master index (none) | |||
Partial TOC (maximum level) 4 | |||
Partial TOC (new page after) INLINE | |||
Print example id's NO | |||
Print cross reference page numbers YES | |||
Process value (none) | |||
Punctuation move characters ., | |||
Read cross-reference file (none) | |||
Running heading/footing rule NONE Show index entries NO | |||
Table of Contents (maximum level) 3 | |||
Table list on new page YES | |||
Title page (draft) alignment RIGHT | |||
Write cross-reference file (none) | |||
Imbed Trace | |||
Page 0 3731WIN Page 0 3731SU | |||
Page 0 3731VARS | |||
Page 1-10 3731DDE | |||
Page 2-7 3731CLIP | |||
Page 3-4 3731CL1 | |||
� | |||
</pre> | |||
</div></div> | |||
<div class="toccolours mw-collapsible mw-collapsed"> | |||
VMBOOT.DOC | |||
<div class="mw-collapsible-content"> | |||
<pre width="87"> | |||
IBM Internal Use Only | |||
1.0 Virtual Machine Boot | |||
IBM Internal Use Only | |||
Draft extract from ITSC Red Book OS/2 Version 2 GG24-3731. Subject to | |||
revision | |||
1.1 VMB Overview | |||
An important goal of OS/2 V2 is the ability to run past, current, and future PC | |||
DOS programs; indeed most DOS applications available today run unchanged in | |||
the MVDM DOS Emulation environment. | |||
However, it should be remembered that the 﨑OS?which runs in this case is | |||
highly optimized for (and specific to) an OS/2 V2 virtual 8086 machine. Because | |||
of this, there are subtle internal differences between DOS Emulation and real | |||
DOS. Unfortunately some DOS programs may be inherently bound to a specific | |||
DOS version, relying on internal DOS structures or features not present in MVDM | |||
DOS Emulation, such as internal DOS tables, LAN redirector hooks, or even | |||
absolute routine addresses or undocumented features. | |||
Another restriction of MVDM DOS Emulation is that only DOS character device | |||
drivers can be loaded. The user may own a block device (often a special disk or | |||
tape drive) for which no OS/2 driver is available. | |||
Virtual Machine Boot allows the user to boot ff-the-shelf?DOS 3.x, 4.0, or 5.0 in | |||
a VDM session, including DOS block device drivers. This gives the user the | |||
greatest possible compatibility with PC DOS. | |||
Another benefit of Virtual Machine Boot is the ability to run DOS of a different | |||
National Language to that of OS/2 V2. This may be useful in a multilingual or | |||
testing environment. | |||
1.2 Virtual Machine Boot Environment | |||
The 80386 processor and VDM component of OS/2 V2 together emulate a 8086 | |||
processor, keyboard, display, BIOS and other supporting hardware - a complete | |||
virtual Personal Computer. So it shouldn't really be too surprising that eal? | |||
DOS can run in a Virtual DOS Machine session. Control is passed to the boot | |||
record (the first sector) of the DOS system diskette, which in turn loads and ini- | |||
tializes the rest of the DOS kernel, just as it does when booting on a real PC. | |||
Indeed the VDM environment is so like a real PC system that Virtual Machine | |||
Boot can actually support any 8086 kernel, such as Digital Research DR-DOS and | |||
1 | |||
CP/M, Microsoft MS-DOS, or even a PS/2 Reference Diskette . However, since | |||
the purpose of Virtual Machine Boot is to run PC DOS applications, formal IBM | |||
support is announced for IBM DOS 3.x, 4.0, and 5.0 only. | |||
1 Do not attempt to run diagnostics or change the configuration from a VDM; the results are unpredictable. | |||
+ Copyright IBM Corp. 1991 1-1 | |||
IBM Internal Use Only | |||
Multiple DOS VDM kernels may be booted and operated concurrently. Each runs | |||
in its own virtual 8086 session; access to hardware and other system resources | |||
is managed by the underlying OS/2 V2 operating system. | |||
1.3 Using Virtual Machine Boot | |||
The booted DOS operating system can be: | |||
1. An actual DOS system diskette | |||
2. An image of a DOS system diskette saved to fixed disk | |||
3. A DOS partition on fixed disk. | |||
A Virtual Machine Boot session is created as a normal Program icon on the | |||
OS/2 desktop. Here is an sample Program notebook page: | |||
+-----------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+-----------------------+ | |||
Figure 1-1. VMB Program parameters | |||
Program title A suitable description | |||
Path and filename * (actually ignored, but must be valid) | |||
Optional Parameters (blank - ignored) | |||
Working directory (blank - ignored) | |||
The Session type may be DOS Fullscreen or DOS Window as desired. | |||
1.3.1 DOS Startup drive | |||
The difference from a normal DOS item is that the DOS Settings value 﨩ther: | |||
DOS startup drive?is set. This contains the location of the DOS kernel to be | |||
booted. | |||
1-2 VMBOOT | |||
IBM Internal Use Only | |||
+---------------------------------------------------+ | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
| | | |||
+---------------------------------------------------+ | |||
Figure 1-2. DOS Startup drive | |||
Example values for DOS startup drive are: | |||
Startup setting Meaning | |||
a: Boot the diskette in drive A: | |||
c: bootimgdos33.vmb \ \ Boot the specified DOS image file | |||
c: Boot the primary partition of the C: drive | |||
Note: | |||
? You cannot specify a second diskette drive (B:) or fixed disk (D:) as the | |||
startup drive. | |||
? To boot DOS from the C: partition, you must have Boot Manager installed, | |||
and OS/2 V2 must reside in an extended partition on the first fixed disk, or | |||
on another fixed disk. See 1.7, 﨎ooting a DOS partition?on page 1-9. | |||
1.3.2 Virtual Machine Boot and 5?inch drives | |||
You cannot specify 﨎:?or an external diskette drive as the startup drive. There | |||
may be situations where you wish to boot a 5?inch diskette; often the B: drive | |||
on PS/2 systems. One way to do this is by creating an image of the diskette, | |||
then booting this image. (See 1.4, MDISK?on page 1-4.) | |||
If a 5?inch diskette must be booted directly for some reason, this is possible if | |||
drive remapping is supported by the system (such as a PS/2 Model 57, 90 or 95). | |||
Normally A: is Drive 0 (3?inch), and B: is Drive 1 (5?inch, if fitted). To change | |||
this, run et Startup Sequence?from the Reference Diskette, and ensure Drive | |||
1 appears before Drive 0. Then the 5?inch drive will become the A: drive. | |||
Some 5?inch drives (such as the IBM External 1.2MB drive and associated | |||
adapter) require a device-driver, and are accessed as D: or higher. They cannot | |||
be specified as a startup drive, nor can they be readdressed as A:, but can be | |||
the source drive when creating a bootable image file. | |||
Virtual Machine Boot 1-3 | |||
IBM Internal Use Only | |||
1.3.3 Other DOS Settings | |||
DOS Settings which control the VDM hardware environment are applicable to the | |||
Virtual Machine Boot session and operate in the same way as for a DOS Emu- | |||
lation window or fullscreen session. Those which modify the virtual DOS environ- | |||
ment are ignored; these are instead determined by the CONFIG.SYS of the | |||
booted DOS kernel. Ignored settings include: | |||
? BREAK | |||
? | |||
DOS Device drivers | |||
? DOS owns UMBs | |||
? DOS SHELL | |||
? DOS High / Low | |||
? LASTDRIVE | |||
? Simulated DOS version | |||
The FCB limit is the lesser of either the booted DOS, or OS/2 V2 CONFIG.SYS | |||
value. The Virtual Machine Boot session will by default have 640 KB of real | |||
memory, mouse support, 2 MB Expanded (EMS) memory, 3 MB DPMI, and 2 MB | |||
XMS memory. | |||
In other respects the VMB session is no different to any other VIO window. It | |||
may be minimized, maximized and switched between windowed and fullscreen | |||
mode, and is subject to the same graphics limitations when windowed. The | |||
session cannot be ended by typing exit at its command prompt. The session can | |||
only be closed from its system icon or the Window List. | |||
1.4 VMDISK | |||
As already described, it is possible to boot from a diskette image which itself | |||
resides on fixed disk. This image is created using the VMDISK utility supplied | |||
with OS/2 V2. The syntax of the VMDISK command is: | |||
vmdisk <source drive> <image filename> | |||
For example: | |||
vmdisk a: c:\bootimg\dos33.vmb | |||
The image file is a complete binary ump?of the diskette, consisting of a short | |||
header record followed by the diskette's boot sector, FAT(s), and all data clus- | |||
ters. Its filesize corresponds to the source diskette capacity regardless of the | |||
amount of space actually used on the source diskette. No compression of the | |||
image is performed. The diskette must be of a normal DOS format (FAT, 512 byte | |||
sectors). It is not possible to create, then boot, an image of a copy-protected | |||
diskette which has a non-DOS format. It may be possible to boot such a diskette | |||
directly in a VDM. | |||
VMDISK can run under either DOS or OS/2, and supports all 3?inch (720KB, | |||
1.44MB and 2.88MB) and 5?inch (360KB and 1.2MB) source diskette formats. | |||
1-4 VMBOOT | |||
IBM Internal Use Only | |||
1.5 Drive letter allocation and access | |||
This is one of the more complex area of Virtual Machine Boot. The following pos- | |||
sible areas of confusion may arise for the user: | |||
? If DOS is booted from an image file, it sees this image file as its A: drive. | |||
This prevents access to the real A: diskette drive. Attempts to the write to the | |||
apparent A: drive will fail. | |||
? A DOS VDM cannot see an HPFS partition on the fixed disk. | |||
? A DOS 3.x VDM cannot see a large (>32MB) FAT partition on the fixed disk, | |||
or FAT partitions beyond HPFS. | |||
? | |||
Even if the booted DOS can otherwise see the fixed disk partition, it is only | |||
given read access. Attempts to write will fail with simulated errors such as | |||
. The 礼eneral failure writing drive C:? user might mistake this for genuine | |||
hardware fault. | |||
? If the booted DOS loads a block device-driver, the allocated drive letter may | |||
be the same as that of a different device outside this VDM. | |||
The results could be somewhat disorienting for the user. To help resolve these | |||
issues, two utilities FSFILTER and FSACCESS are provided with OS/2 V2. | |||
1.5.1 FSFILTER | |||
FSFILTER.SYS is a device driver which manages DOS VDM access to OS/2 disks. | |||
FSFILTER.SYS should be copied from the OS2MDOS directory to the DOS \ \ | |||
diskette, and the following statement added to the DOS CONFIG.SYS: | |||
device=a:fsfilter.sys | |||
This gives PC DOS full access to all OS/2 partitions - whatever the filesystem | |||
type or partition size. | |||
This is an important and somewhat surprising point. For example, DOS 3.3 (in a | |||
VDM) has no problem accessing a 300MB HPFS partition, once FSFILTER is | |||
loaded. I/O calls within the DOS virtual machine are passed transparently to | |||
OS/2 V2. DOS itself is unaware of the underlying filesystem. DOS can read, write | |||
and modify files on the fixed disk, and for most configurations the drive letter | |||
mapping within the VMB session will match those of OS/2 V2. | |||
Note | |||
FSFILTER.SYS is loaded via CONFIG.SYS of the booted DOS, not the OS/2 V2 | |||
CONFIG.SYS. It should be preceed any statements which load block device= | |||
device drivers. | |||
The FSFILTER device driver occupies approximately 11KB of memory. It can be | |||
loaded high (evicehigh=fsfilter.sys? under DOS 5.0. | |||
Some operating systems may be confused by FSFILTER's actions during their | |||
boot processing. For example the setting of the current drive or COMSPEC may | |||
be invalid, or AUTOEXEC.BAT may not run. This has been noted with DR-DOS | |||
and PC DOS 3.3 (but not 4.0 or 5.0). To avoid this problem specify the path to | |||
COMMAND.COM in the SHELL= statement of CONFIG.SYS (as well as the | |||
Virtual Machine Boot 1-5 | |||
IBM Internal Use Only | |||
command processor itself). For example, if you cave copied DOS files to C: DOS, | |||
\ | |||
the CONFIG.SYS of a diskette intended for VMB should contain a statement: | |||
shell=c:\dos\command.com c:\dos /p | |||
The first parameter specifies the comand procesor to load. The second param- | |||
eter specifies the reload path (ie the COMSPEC path). This is preferable to a et | |||
comspec= ...?line in AUTOEXEC.BAT. | |||
1.5.1.1 FSFILTER limitations | |||
Even when FSFILTER is loaded, the following restrictions still apply: | |||
? A DOS VMB cannot see HPFS files or directories which have: | |||
?long filenames (9 or more characters) | |||
?invalid FAT characters (eg plus, comma, blank). | |||
?multiple dot separators | |||
? HPFS filenames containing lowercase letters are folded to uppercase. | |||
? PC DOS commands which require low-level disk access will fail. These | |||
include: | |||
?CHKDSK | |||
?SYS | |||
?UNDELETE | |||
?FORMAT | |||
?UNFORMAT | |||
?MIRROR | |||
In such cases OS/2 V2 will simulate a disk error condition. DOS may inter- | |||
pret this as a hardware fault, or report that the command is not supported on | |||
a Network or Assigned drive. | |||
1.5.2 FSACCESS | |||
FSACCESS.EXE is a utility supplied with OS/2 V2 but intended to run in a Virtual | |||
Machine Boot session. It cooperates with FSFILTER to manage drive letters | |||
within the VMB session. This serves three purposes: | |||
1. Drives may be registered for filtering. | |||
2. The drive letter for a device can be changed, giving consistency across ses- | |||
sions. | |||
3. Letters can be removed in order to hide the OS/2 device from the VMB | |||
session. | |||
The syntax of the FSACCESS command is: | |||
FSACCESS 葺葺葺葺葺葺�葺葺葺葺葺葺葺葺葺葺葺葺?葺葺?葺 . | |||
谳�葺??DOSletter 葺葺葺? � | |||
� � ! � � | |||
谳葺葺?DOSletter - DOSletter 葺? | |||
� � | |||
�葺葺葺 DOSletter = OS2drive 葺� | |||
FSACCESS lists the current drive mapping. For example: | |||
1-6 VMBOOT | |||
IBM Internal Use Only | |||
Local C: is mapped to OS/2 C: | |||
Local D: is mapped to OS/2 D: | |||
Local E: is mapped to OS/2 K: | |||
FSACCESS F: registers DOS letter F: for filtering. References to F: will be | |||
sent to OS/2 V2. | |||
FSACCESS !F: deregisters DOS letter F: from filtering. | |||
FSACCESS F:-H: registers DOS letters F: through H: for filtering. | |||
FSACCESS M:=C: registers DOS letter M: and routes requests to OS/2 drive | |||
C: | |||
Parameters can be combined on a single command line, and the colon is | |||
optional. | |||
1.5.3 Practical Considerations | |||
? When booting from an image file, you will probably wish to issue the | |||
command ? fsaccess a: ?in order to access the A: diskette drive. | |||
?This will remove access to the image file, so the booted DOS will be | |||
unable to reload its COMMAND.COM when necessary. You may wish to | |||
copy all the DOS files to a subdirectory on fixed disk, ensuring the PATH | |||
and COMSPEC point there. | |||
An alternative is to access the diskette drive via a different letter. For | |||
example, you can issue the command ? ,?then use G: to fsaccess g=a | |||
access the real A: drive. The image file remains as A:, avoiding PATH | |||
and COMSPEC problems. | |||
? | |||
FSACCESS error messages are contained in the OS/2 file OSO001.MSG, | |||
which is in the OS2SYSTEM subdirectory. \ \ You should ensure that this file | |||
is accessible to the booted DOS via its APPEND search path, otherwise an | |||
FSACCESS error will only report that its message file cannot be found. | |||
? Each block device driver loaded in DOS CONFIG.SYS is allocated the next | |||
free OS/2 letter excluding LAN drives. This can result in a drive letter clash. | |||
An example may illustrate the point. OS/2 drives are: | |||
A: Diskette drive 0 | |||
B: Diskette drive 1 | |||
C: Fixed disk | |||
D: External Diskette drive | |||
E: Remote LAN drive on a Server | |||
FSFILTER will ensure that a booted DOS sees these drives by the same | |||
letter. The booted DOS has the same access to the external diskette drive | |||
and LAN resources as does OS/2 itself. This is true whether the VMB | |||
session is started before or after user Logon to the network, when remote | |||
drive letters are assigned. | |||
However, a VMB block device driver will also initialize as E:, so LAN drive | |||
access is lost. To remedy this, issue an command. The LAN saccess f=e? | |||
drive is now accessible as F: within the DOS session. | |||
? If a Virtual Machine Boot session hangs for any reason, you can close it from | |||
its system icon or the Window List. Remember that CTRL-ALT-DEL will | |||
reboot OS/2, not the foreground virtual machine session. | |||
Virtual Machine Boot 1-7 | |||
IBM Internal Use Only | |||
Hint | |||
Always give disk volumes a meaningful name - either when formatting or | |||
later using the LABEL command. The name will remain constant and help | |||
you identify where you are, even if the assigned drive letter is different some- | |||
times. | |||
1.6 XMS, EMS and MOUSE Support | |||
The booted DOS receives XMS (HIMEM), EMS, DPMI and mouse support services | |||
from its VDM environment (assuming the Virtual DOS Machine has default DOS | |||
Settings). It should not load its own HIMEM, EMS or mouse drivers - indeed they | |||
may cause errors in the VDM. | |||
DOS programs call these services via appropriate API register parameters and a | |||
designated Interrupt: | |||
Mouse INT 33h | |||
XMS INT 2Fh (multiplex) | |||
EMS INT 67h | |||
OS/2 V2 traps these interrupts from the virtual machine and handles the request | |||
accordingly. | |||
This may present a problem for certain programs which can use such services, | |||
but first test for their presence by issuing an OPEN to the associated device- | |||
driver, or check that a valid interrupt handler is pointed to by the Interrupt Vector | |||
Table. When a VMB session is started, these device driver names are not | |||
present, and the interrupt vectors point to null handlers. The application will | |||
therefore assume that these services are not useable. | |||
To resolve this, OS/2 V2 provides three alternative tub?drivers: | |||
? MOUSE.COM | |||
? | |||
HIMEM.SYS | |||
? EMM386.SYS | |||
These stub drivers are very small (and use minimal memory when loaded) but | |||
satisfy programs which depend on drivers with such names being present. They | |||
also set handler addresses in the Interrupt Vector Table. | |||
The user must load these OS/2 files rather than any similarly named files which | |||
may be shipped with DOS or applications, such as: | |||
DOS 4.0 XMAEM.SYS, XMA2EMS.SYS | |||
DOS 5.0 HIMEM.SYS, EMM386.EXE, MOUSE.COM | |||
Other MOUSE.SYS | |||
There are two ways to achieve this. Assuming OS/2 V2 is installed on drive C: | |||
Method 1 Copy the above OS/2 files from C: OS2MDOS to the DOS diskette, \ \ | |||
and edit CONFIG.SYS and AUTOEXEC.BAT accordingly to load these | |||
files from the A: drive. VMDISK may then be run to create a bootable | |||
image if desired. | |||
1-8 VMBOOT | |||
IBM Internal Use Only | |||
device=a:fsfilter.sys | |||
device=a:himem.sys | |||
device=a:emm386.sys | |||
Method 2 Edit CONFIG.SYS and AUTOEXEC.BAT to load these files directly from | |||
C:OS2 \ \ MDOS. (FSFILTER must be loaded first if the OS/2 drive would | |||
otherwise be inaccessible to the booted DOS). | |||
device=a:fsfilter.sys | |||
device=c:\os2\mdos\himem.sys | |||
device=c:\os2\mdos\emm386.sys | |||
The first method should be used if you wish to load FSFILTER high using DOS | |||
5.0: | |||
device=a:himem.sys | |||
device=a:emm386.sys | |||
devicehigh=a:fsfilter.sys | |||
The second method has one notable advantage; if and when Corrective Service | |||
is applied to the OS/2 V2 system, and HIMEM, EMM386 or MOUSE are updated, | |||
you won't need to update your DOS diskettes and recreate image files. FSFILTER | |||
itself will have to be updated manually (unless the OS/2 V2 partition is directly | |||
accessible to your DOS and you load FSFILTER from here too). | |||
Note: EMS memory size and frame location are determined by DOS Settings, | |||
not parameters on the EMS386.SYS statement. | |||
1.7 Booting a DOS partition | |||
If you anticipate using Virtual Machine Boot regularly, the most convenient | |||
method may be to do so from a DOS partition on the fixed disk, rather than via | |||
diskettes or diskette images. A partition boot proceeds more quickly and offers | |||
the user a more amiliar?working environment. Also, it is easier to apply DOS | |||
Corrective Service to a disk partition than to diskettes or images. | |||
The configuration requirements are: | |||
1. Boot Manager must be installed | |||
2. DOS must be installed on a primary partition on the first fixed disk | |||
3. OS/2 V2 must be installed on an extended partition on the first fixed disk, or | |||
on another fixed disk. | |||
This will require repartitioning on single drive systems if the disk initially con- | |||
taining DOS alone, or earlier versions of OS/2. | |||
Note: This is not the same as a single partition with the Dual Boot feature. | |||
To boot the DOS partition in a VMB session, enter the DOS Settings Startup | |||
Drive parameter as 﨏:? | |||
Virtual Machine Boot 1-9 | |||
IBM Internal Use Only | |||
1.7.1 Configuration files | |||
This particular setup presents one significant problem. The DOS partition is itself | |||
bootable directly via Boot Manager, should the user so choose, and there may a | |||
requirement to boot this DOS partition directly on occasions. The problem is: As | |||
there is only one CONFIG.SYS and one AUTOEXEC.BAT in the C: root directory, | |||
which drivers should be specified - DOS or OS/2 stub drivers? | |||
If the partition is booted via VMB the DOS drivers are inappropriate. | |||
If the partition is booted directly via Boot Manager the OS/2 stub drivers are | |||
inappropriate. | |||
It might appear that the user would have to maintain multiple configuration files | |||
and rename or copy them according to the next desired boot type. This is clearly | |||
rather unsatisfactory. Fortunately there is a solution which avoids this. The key is | |||
to specify both sets of drivers in CONFIG.SYS and AUTOEXEC.BAT. | |||
The following example assumes: | |||
? DOS 5.0 is installed on the C: Primary partition | |||
? OS/2 V2 is installed on the D: Extended partition | |||
CONFIG.SYS on the C: drive contains: | |||
device=c:\fsfilter.sys | |||
device=c:\dos\setver.exe | |||
device=c:\dos\himem.sys | |||
device=c:\dos\emm386.exe noems | |||
device=d:\os2\mdos\himem.sys | |||
device=d:\os2\mdos\emm386.sys | |||
dos=high,umb | |||
... etc ... | |||
When this file is processed under an OS/2 VMB, the DOS HIMEM load fails as it | |||
sees no available Extended memory. EMM386.EXE cannot load as it sees protect- | |||
mode software already running. Then, the OS/2 HIMEM and EMM386 stubs load | |||
as normal. | |||
When this file is processed as part of a native DOS boot, the DOS HIMEM and | |||
EMM386 load as normal, but the OS/2 stubs realize they are not running under | |||
OS/2 and do nothing. | |||
A similar technique works for mouse support in AUTOEXEC.BAT: | |||
@echo off | |||
prompt 減済 | |||
set path=c:\dos | |||
lh d:\os2\mdos\mouse | |||
lh c:\dos\mouse | |||
... etc ... | |||
Note that here the OS/2 driver is listed first. When booting DOS native, the OS/2 | |||
mouse stub will realize this, and not load. Then the DOS mouse driver loads as | |||
normal. | |||
1-10 VMBOOT | |||
IBM Internal Use Only | |||
When this file is processed under OS/2 VMB, the OS/2 stub loads first. Then, the | |||
DOS mouse driver sees that a mouse driver is already present, so does not | |||
install itself. | |||
Note: Unfortunately this technique cannot be taken too far. For example, you | |||
may need to load IBM LAN Support Program drivers for the Token Ring adapter | |||
(DXMxxMOD.SYS) files in your DOS CONFIG.SYS. If you already have sessions | |||
using the Token Ring adapter (either OS/2 Extended Services or previously | |||
started DOS communications) and then boot the DOS partition, its LAN device | |||
drivers attempt to reinitialize the adapter. This will corrupt existing Token Ring | |||
sessions. | |||
1.8 Virtual Machine Boot Limitations | |||
Virtual Machine Boot does not support: | |||
? VCPI and other non-DPMI DOS extenders | |||
? I/O to disk which bypasses the file system | |||
? Feature adapter sharing without a virtual device driver | |||
? Real-time or timing critical DOS applications | |||
? | |||
Some copy-protection schemes. | |||
1.9 Available Memory | |||
Table 1-1 shows the amount of available base memory for MVDM DOS Emu- | |||
lation, DOS in a VMB session, and native DOS. | |||
Table 1-1. Free Base Memory | |||
Setting VDM DOS Emu- DOS 5.0DOS 4.0 DOS 3.3 | |||
lation | |||
DOS low 610 KB 566 KB 588 KB 545 KB | |||
DOS high 633 KB 612 KB - - | |||
With mode728 KB 707 KB 653 KB 670 KB | |||
restriction | |||
(CGA) | |||
Native DOS - 564 KB (low) 545 KB 562 KB | |||
614 KB (high) | |||
Note: Each configuration has HIMEM, EMS and Mouse drivers loaded. Values are approximate. | |||
1.10 Customizing DOS | |||
There is little point in loading the following in a booted DOS: | |||
? Disk cache | |||
? Print spooler | |||
? RAM disk | |||
These are better left to &OS2V2.. | |||
Do not configure EMS or XMS if the DOS session doesn't use them, as this can | |||
impact the performance of the rest of the system. | |||
Virtual Machine Boot 1-11 | |||
IBM Internal Use Only | |||
1.11 Expanded Memory (EMS) and Upper Memory (UMB) | |||
The following section applies to both VDM DOS Emulation and DOS Virtual | |||
Machine Boot. | |||
Expanded Memory Specification (EMS) is discussed in detail in -- Heading | |||
'3731EMS' unknown --. One requirement of EMS is a page frame in real memory | |||
between 640KB and 1MB (hex addresses X A0000 to X FFFFF). Since IBM ' ' ' | |||
' | |||
systems reserve addresses X A0000 to X BFFFF for video, and X E0000 to ' ' ' ' | |||
' ' | |||
X FFFFF ' ' for BIOS, the EMS Page Frame is normally restricted to addresses | |||
between X C0000 and X E0000 ' ' ' ' . This area can also be used for Upper Memory | |||
Blocks, where DOS device drivers and resident programs can be loaded. This | |||
frees up valuable space below 640KB for conventional DOS programs. | |||
Unfortunately, memory between X C0000 and X E0000 is also needed for ' ' ' ' | |||
Option Adapter ROM and RAM. Indeed it can be difficult or even impossible to | |||
configure EMS on a system which has several intelligent adapters installed. | |||
There is really no solution to this problem (sometimes known as AM Cram? | |||
under DOS. However OS/2 V2 provides an elegant alternative. | |||
Normally a VDM inherits a memory map which mirrors the actual system hard- | |||
ware configuration; adapter ROM and RAM addreses set by the PS/2 Reference | |||
Diskette (or adapter switches on non Micro Channel systems) are mapped into | |||
the VDM address space and are not available for EMS or UMBs. | |||
But since the VDM occupies virtual memory this can easily be changed. The | |||
DOS Settings value Other: Include Regions parameter releases adapter | |||
addresses for use as EMS or UMBs. In most cases this can be set to the com- | |||
plete X C0000-X DFFFF range. ' ' ' ' | |||
If a VDM uses an adapter directly (usually via DOS device drivers), any adapter | |||
ROM or RAM address must not be specified in Include Regions. Addresses of | |||
adapters used indirectly by the VDM (through OS/2 V2) may be included. For | |||
example, the full X C0000 to X DFFFF ' ' ' ' range may be included on a | |||
SCSI-based | |||
PS/2, even though the SCSI adapter ROM may occupy X D8000 to X DFFFF. ' | |||
' ' ' | |||
The DOS VDM does not directly access the SCSI adapter so doesn't need SCSI | |||
ROM mapped into its address space. It can still access files on SCSI disks via | |||
the OS/2 V2 filesystem. | |||
Note (** this may change **) | |||
The Include Regions parameter should be entered as shown above, using | |||
5-digit hex addresses (not 4-digit segment addresses, as is often the case). | |||
Also, note that the range is inclusive - you must specify the second address | |||
as (for example) X DFFFF, not X E0000 ' ' ' ' . The parameter is not | |||
validity- | |||
checked when entered. If an invalid parameter is saved, the default (no | |||
include region) is used when the VDM is initialised; no error message is gen- | |||
erated. | |||
In summary, a typical DOS VDM may have a 64KB EMS page frame and 64KB of | |||
UMBs (or 128KB of UMBs) regardless of the hardware adapters installed. Such a | |||
configuration is not possible under PC DOS. | |||
1-12 VMBOOT | |||
IBM Internal Use Only | |||
2.0 Index | |||
A M | |||
Adapter memory 1-12 MOUSE.COM. 1-8 | |||
B O | |||
Block device driver 1-7 OSO001.MSG 1-7 | |||
Block device drivers 1-1 | |||
Boot Manager 1-9 | |||
P | |||
PC DOS 1-1 | |||
C | |||
COMSPEC 1-6 | |||
S | |||
Settings (DOS) 1-4 | |||
D Stub drivers 1-8 | |||
DOS 1-1 | |||
DOS Image 1-4 | |||
U | |||
DOS Settings 1-4 UMB 1-12 | |||
DOS Startup drive 1-2 | |||
Upper Memory 1-12 | |||
E | |||
V | |||
EMM386.SYS 1-8 VCPI 1-11 | |||
EMS 1-12 | |||
EMS. 1-8 Virtual Machine Boot 1-1 | |||
VMDISK 1-4 | |||
Expanded Memory 1-12 | |||
F X | |||
XMS 1-8 | |||
FAT 1-5 | |||
FCB 1-4 | |||
FSACCESS 1-6 Numerics | |||
FSFILTER 1-5 5?inch disks 1-3 | |||
H | |||
HIMEM.SYS. 1-8 | |||
HPFS 1-5 | |||
I | |||
IBM DOS 1-1 | |||
Include Regions 1-12 | |||
L | |||
LAN 1-1 | |||
large partitions 1-5 | |||
+ Copyright IBM Corp. 1991 2-1 | |||
IBM Internal Use Only | |||
Figure Definitions | |||
id File Page References | |||
FIGDEF 3731SU | |||
1-1 | |||
Table Definitions | |||
id File Page References | |||
TDEF 3731SU | |||
1-1 | |||
Headings | |||
id File Page References | |||
VMB 3731VMB | |||
VMDISK 1-1 1.0, Virtual Machine Boot 3731VMB | |||
1-4 1.4, VMDISK | |||
1-3 | |||
BOOTPRT 3731VMB | |||
1-9 1.7, Booting a DOS partition | |||
1-3 | |||
3731EMS ? | |||
? ? | |||
1-12 | |||
Footnotes | |||
id File Page References | |||
REFDISK 3731VMB | |||
1-1 1 | |||
1-1 | |||
Tables | |||
id File Page References | |||
FREEMEM 3731VMB | |||
1-11 1-1 | |||
1-11 | |||
Processing Options | |||
Runtime values: | |||
Document fileid VMBOOT SCRIPT | |||
Document type USERDOC | |||
Document style IBMXAGD Profile EDFPRF20 | |||
Service Level 0018 | |||
SCRIPT/VS Release 3.2.1 | |||
Date 91.10.15 | |||
Time 10:42:52 | |||
Device 3820A | |||
Number of Passes 2 | |||
Index YES | |||
SYSVAR G INLINE | |||
SYSVAR X YES | |||
Formatting values used: | |||
Annotation NO | |||
Cross reference listing YES Cross reference head prefix only NO | |||
Dialog LABEL | |||
Duplex YES | |||
IBM Internal Use Only | |||
DVCF conditions file (none) | |||
DVCF value 1 (none) | |||
DVCF value 2 (none) | |||
DVCF value 3 (none) | |||
DVCF value 4 (none) | |||
DVCF value 5 (none) | |||
DVCF value 6 (none) | |||
DVCF value 7 (none) | |||
DVCF value 8 (none) | |||
DVCF value 9 (none) | |||
Explode NO | |||
Figure list on new page YES | |||
Figure/table number separation YES | |||
Folio-by-chapter YES | |||
Head 0 body text Part Head 1 body text Chapter | |||
Hyphenation YES | |||
Justification YES | |||
Language ENGL | |||
Layout OFF | |||
Leader dots YES | |||
Master index (none) | |||
Partial TOC (maximum level) 4 | |||
Partial TOC (new page after) INLINE | |||
Print example id's NO | |||
Print cross reference page numbers YES | |||
Process value (none) | |||
Punctuation move characters ., | |||
Read cross-reference file (none) | |||
Running heading/footing rule NONE Show index entries NO | |||
Table of Contents (maximum level) 3 | |||
Table list on new page YES | |||
Title page (draft) alignment RIGHT | |||
Write cross-reference file (none) | |||
Imbed Trace | |||
Page 0 3731SU Page 0 3731VARS | |||
Page 0 3731VMB | |||
� | |||
</pre> | </pre> | ||
</div></div> | </div></div> | ||
2020年11月6日 (五) 19:01的版本
尚未添加到任何已有项目中的内容:
疑点暂存
Win 3.11 for workgroups Hebrew RTM(the one version 3.11.050):
该版hebrew rtm比后发RTM（无050标识）出的更早，两者皆为RTM。
Win 3.11 for workgroups Russian 1993-10-14 version:
情况可能和win3.2 redchina一样，但因为语言不通找不出决定性的证据。
可能有用的key
部分过于难看的内容经过排版，key本身不动。
WindowsXP 2520 Pro 英文版－－60天免激活序列号：
RK7J8-2PGYQ-P47VV-V6PMB-F6XPQ
Windows XP 2505 RC1－－序列号：
DTWB2-VX8WY-FG8R3-X696T-66Y46
Q3R8Y-MP9KD-3M6KB-383YB-7PK9Q
411Y0-URB45-34R3B-310N6-70U51
F0R6R-347JU-57IC3-M0V34-11Z16
50M38-0DY53-7UPU5-7H380-M8111
Microsoft Whistler Professional Beta 2 2462繁体中文版
S/N：QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
Microsoft Windows Millennium B2 V4.90.2438 98 第三版中文完整测试版
S/N：RBDC9-VTRC8-D7972-J97JY-PRVMG
Microsoft Windows Whistler Pro CD-Key：
F6PGG-4YYDJ-3FF3T-R328P-3BXTG
...............................................
Windows 2000 Professional RC3
VXKC4-2B3YF-W9MFK-QB3DB-9Y7MB
Windows 2000 Server RC3
H6TWQ-TQQM8-HXJYG-D69F7-R84VM
..............................................
Windows 95 v4.00.950 R2 : 875-7215850
Windows 95 v4.00.950 R3/R6 : 975-4769754
Windows98 build 1708 and 1720 and maybe others -
Serial Number: HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Memphis (WIN 98): K4HVD-Q9TJ9-6CRX9-C9G68-RQ2D3
Win98 Second Edition V 4.10.2174 A
Serial Number C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Microsoft Windows Whistler Build 2505RC1/2509postRC1
BJXGH-4TG7P-F9PRP-K6FJD-JQMPM
Microsoft Windows Whistler Beta 2 Build 2502/2504
JJWKH-7M9R8-26VM4-FX8CC-GDPD8
Microsoft Windows Whistler Beta 2 Build 2486
BJXGH-4TG7P-F9PRP-K6FJD-JQMPM
Microsoft Windows Whistler Beta 2 Build 2474-2499
DTWB2-VX8WY-FG8R3-X696T-66Y46
Microsoft Windows Whistler Beta 2 Build 2469
Q3R8Y-MP9KD-3M6KB-383YB-7PK9Q
Microsoft Windows Whistler Beta 1 Build 2462-2465
DW3CF-D7KYR-KMR6C-3X7FX-T8CVM
QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
DW3CF-D7KYR-KMR6C-3X7FX-T8CVM
Microsoft Windows Whistler Build 2296 & 2458
QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
VXKC4-2B3YF-W9MFK-QB3DB-9Y7MB
Windows 98 Build 1708/Build 1720:
HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Windows 98 Build 1708:
BBH2G-D2VK9-QD4M9-F63XB-43C33
Windows 98 Build 1720:
HGBRM-RBK3V- M9FXV-YCXDK-V38J4
Windows 98 Build 1723:
HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Windows 98 OSR Beta Refresh beta 2 and up to build 2150:C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 95(other build keys):
875-7215850
100-1208613
757-2573155
Windows 95 (build 490) : 100-1208613
Windows 98 OSR Beta Refresh - CD-Key: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 98 OSR1 Beta 2 - CD-Key: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 98 OSR1 Build 2150 - CD-Key: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 98 OSR1 v4.10.2126 - CD-Key: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 98 OSR1 v4.10.2131 - CD-Key: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 97 Code: 26495-OEM-0004791-53803
.............................................
Windows XP Home Build 2542-2600
s/n: 4C4DQ-323QV-XBWTX-CX8YQ-3KJKM
Microsoft Windows Vista Build 5308
S/N: Client_S/N: R4HB8-QGQK4-79X38-QH3HK-Q3PJ6
Server_S/N: WBVG8-4JPQB-6HJ6H-XH7YY-D2GQY
Windows Vista 5308
S/N: WGDJW-B8DYC-WVKX4-6MKF4-B8PK8
Windows Vista Beta 2 32bit
S/N: V4TYH-74MWQ-6VTBQ-XRD3V-9MMX2
Windows vista beta 2 build 5342
S/N: GKFV7-F2D9H-QKYXY-777P3-4M73W
TGX39-HB48W-R29DH-6BVKB-3XFDW
Q8WDJ-TR4KJ-X8WHM-GVGV3-H74C3
CKY24-Q8QRH-X3KMR-C6BCY-T847Y
C6RDR-7PC77-476GM-VYMGD-DDH2B
R4HB8-QGQK4-79X38-QH3HK-Q3PJ6
Windows Vista Beta 5259
S/N: TGX39-HB48W-R29DH-6BVKB-3XFDW
windows vista beta2
S/N: BV8W7-2Q9TX-KDHP9-9B98J-439WT
Windows Vista Beta2 Build 5384.4
S/N: PVYFQ-2JTBV-9KXQ2-FQHDY-MTBVH
Windows Vista build 5536
Name: Chris
S/N: 6BJ24-CGPHV-FKX6G-4RJ3C-T24FV
for any think ask me:) i am a webmaster
Windows Vista RC1 (build 5600)
S/N: BV8W7-2Q9TX-KDHP9-9B98J-439WT
Windows Vista RC2 5744
S/N: PVYFQ-2JTBV-9KXQ2-FQHDY-MTBVH
Windows Longhorn
s/n: WDRCM-DRVGY-T3YQY-V47YP-XMF9B or
s/n: WDRR9-TX2PH-R3633-6G882-KBKTM or
s/n: WDRYW-G682C-BCDFJ-FB2HJ-YCXTM or
s/n: WDTCJ-PQGH8-76CRJ-CCH4F-RYBPY or
s/n: WDTQ4-JTC3D-DQHD2-QBD2M-4DDGM or
s/n: WDV2M-H8QVB-JDV9X-HW7M4-HPCKB or
s/n: WDV47-MP3XD-D2MD6-7WDPX-X89TM or
s/n: WDVQX-KQRY7-9R6F4-W76K4-BJ9TM or
s/n: WDVRV-JHHYY-49893-HPGRB-78DGM
Windows Longhorn 40 CD-keys
Name: Windows Longhorn 40 CD-keys
S/N: DPTWG-M9PGK-2HT2J-JT9R9-6V8WM
WDYW9-4VJ63-RB8PW-46Q37-9M72Y
WF224-7QFP2-4H2H2-62DGW-KXFCY
WF2Q7-R9WJF-24JGX-G6CH8-VWYPY
WF3X4-8WV6F-G8XVK-QYP47-P92KB
WF4BF-QYRYM-TJMXP-BGMKP-CV4CY
WF4C4-29K22-RPTG6-WXW46-BVR9B
WF6BD-RHP7T-3BG4B-9PFH8-T3T6M
Windows Vista/Longhorn(Build 5308)
S/N: QGVK9-4Y2VT-6YXTH-74QJV-9G3GG
Got it as a beta tester
Windows 7 Beta 32-bit
S/N: GG4MQ-MGK72-HVXFW-KHCRF-KW6KY
Windows 7 beta Nov. 08 build 6801
S/N: J7PYM-6X6FJ-QRKYT-TW4KF-BY7H9
D67PP-QBKVV-6FWDJ-4K2XB-D4684
HQDKC-F3P6D-C9YYM-HRB89-QDBB7
76DX2-7YMCQ-K2WCP-672K2-BK44W
2RG93-6XVFJ-RKHQ7-D2RTT-3FMQT
TT63R-8JGWP-WWT97-R6WQC-4CVWY
YQJX6-D6TRM-VWBM7-PHDJK-YPXJH
Q7J7F-GQHBT-Q42RQ-2F8XV-2WKKM
Windows 7 Build 7000
7XRCQ-RPY28-YY9P8-R6HD8-84GH3
RFFTV-J6K7W-MHBQJ-XYMMJ-Q8DCH
482XP-6J9WR-4JXT3-VBPP6-FQF4M
GG4MQ-MGK72-HVXFW-KHCRF-KW6KY
TQ32R-WFBDM-GFHD2-QGVMH-3P9GC
8XPDH-PCKKG-6MPKT-FTM67-ZFMWG
4HJRK-X6Q28-HWRFY-WDYHJ-K8HDH
GG4MQ-MGK72-HVXFW-KHCRF-KW6KY
QXV7B-K78W2-QGPR6-9FWH9-KGMM7
6JKV2-QPB8H-RQ893-FW7TM-PBJ73
RFFTV-J6K7W-M HBQJ-XYMMJ-Q8DCH
JYDV8-H8VXG-74RPT-6BJPB-X42V4
D9RHV-JG8XC-C 77H2-3YF6D-RYRJ9
Windows 7 RC
S/N: Q3VMJ-TMJ3M-99RF9-CVPJ3-Q7VF3
Windows XP Beta 2 Build 2428
RBDC9-VTRC8-D7972-J97JY-PRVMG
s/n: : QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
WINDOWS 97 BETA : MENPHIS
2859500057111-34276（这啥？）
Microsoft Office 2007 2007 (keine Beta)
S/N: KGFVY-7733B-8WCK9-KTG64-BC7D8
ist die Serial für die Verkaufsversion - nix Beta oder so
Microsoft Office 2007 beta
S/N: HGJH4-9W9FY-8C7B6-P2H6X-9DQ9T
Microsoft Office Professional 2010 Beta
Product Key: 49QGP-V2MRB-XYMYK-Y26V2-YVXYK
Microsoft Office Professional Plus 2007 2007 - Beta2
Name: anything
S/N: MTP6Q-D868F-448FG-B6MG7-3DBKT
Microsoft Windows Server 2008 Beta
<u>Enterprise Edition:</u>
S/N: TFGPQ-J9267-T3R9G-99P7B-HXG47
<u>Standard Edition:</u>
S/N: 2T88R-MBH2C-M7V97-9HVDW-VXTGF
<u>Datacenter Edition:</u>
S/N: GQJJW-4RPC9-VGW22-6VTKV-7MCC6
<u>Itanium Based Systems Edition:</u>
S/N: CQ936-9K2T8-6GPRX-3JR9T-JF4CJ
<u>Windows Web Server Edition:</u>
S/N: GT8BY-FRKHB-7PB8W-GQ7YF-3DXJ6
Note: Product Keys for Evaluation
Microsoft Windows Seven (7) Beta
S/N: Windows 7 Beta 32 Bit:
* 6JKV2-QPB8H-RQ893-FW7TM-PBJ73
* QXV7B-K78W2-QGPR6-9FWH9-KGMM7
* 4HJRK-X6Q28-HWRFY-WDYHJ-K8HDH
* GG4MQ-MGK72-HVXFW-KHCRF-KW6KY
* TQ32R-WFBDM-GFHD2-QGVMH-3P9GC
Windows 7 Beta 64 Bit:（其他来源补足）
JYDV8-H8VXG-74RPT-6BJPB-X42V4
7XRCQ-RPY28-YY9P8-R6HD8-84GH3
D9RHV-JG8XC-C77H2-3YF6D-RYRJ9
RFFTV-J6K7W-MHBQJ-XYMMJ-Q8DCH
4HJRK-X6Q28-HWRFY-WDYHJ-K8HDH
office 2007 beta 2
Name: open lic key no nead to activate
S/N: RQCRJ-FCTYM-V3PDF-GRD46-9YHXQ
enjoy
Office Professional Plus 2007 Beta 2
S/N: MTP6Q-D868F-448FG-B6MG7-3DBKT
Windows Server 2003 Enterprise rc2 Beta2
S/N: s/n: VQ83Q-89DJ9-X9TG9-QF6MC-FRV2D
Windows .NET Server 2003 German
s/n: CKY24-Q8QRH-X3KMR-C6BCY-T847Y
Windows 2003 Candidated Release
s/n: HJYCJ-647BB-76FYQ-J76JT-P78XD
...........................................
Microsoft Windows 98 1720+
#/HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Microsoft Windows 98 Build 1723
#/HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Microsoft Windows 98 RC4
#/320DD-23GW3-2H9CJ-39FNE-3E3IS
Microsoft Windows 98 RC5
#/K4HVD-Q9TJ9-6CRX9-C9G68-RQ2D3
MS Frontpage 98 3.01 Beta（几个标题都一样）
8067-4039161
8123-0123512
9978-3492547
MS IE Administration Kit 3.1 (IEAK)
Install code: 1234567792
MS Outlook 98 Final Beta
#/1112-1111111
Windows 95 (build 490)
100-1208613
Windows 95 950 r2
8757215850
Windows 95 950 r6
9754769754
Windows 95 v4.00.950 R2
875-7215850
Windows 95 v4.00.950 R3/R6
975-4769754
WINDOWS 98
RC5 CD KEY - K4HVD-Q9TJ9-6CRX9-C9G68-RQ2D3
Windows 98 Build 1708
HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Windows 98 SE RC3 Build 2222
C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows 98 Second Edition RC3 Build 2222
C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
Windows RC5
Possible key is K4HVD-Q9TJ9-6CRX9-C9G68-RQ2D3
Memphis 1713 Released (Win98)
HGBRM-RBK3V-M9FXV-YCXDK-V38J4
Microsoft Money v2.01 beta for Windows
00-105-0200-99999979
...........................................
MicroSoft Windows 98 Second Edition RC1
C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
MicroSoft Windows 98 Second Edition RC2
FTBT6-96WDC-384FQ-WF482-Q3M73
...........................................
Windows 95 950 r2 - 875-7215850
Windows 95 950 r3 - 975-4769754
Windows 95 950 r6 - 975-4969754
...........................................
（这些看起来是被截断了）
Memphis 1410 beta 1 :09-A12345
Microsoft Money v2.01 beta (Win3) : #: 00-105-0200-99999979
Microsoft Office 97 Pro Beta : cdkey: 0701-0743365
Microsoft Works v4.0 beta : #: 33977-053-0111756
...........................................
Microsoft.Windows.Server.2003.RC2.3718.CHS.iso
SN : CKY24-Q8QRH-X3KMR-C6BCY-T847Y
SN : KRMXQ-BJDUW-J89MB-7767F-PVR8M
...........................................
windows vista rc2 中文版
FCDW7-QP4XD-R48GT-Q47Y3-HTR9P
...........................................
Windows Server 2008 R2 RC各版的测试产品序列号：
·Windows Server 2008 R2 Release Candidate Enterprise(标准版)
Product Code ： Q7Y83-W4FVQ-6MC6C-6QQTD-TPM88
·Windows Server 2008 R2 Release Candidate Standard(企业版)
Product Code ： V4KRB-QDWK2-GVT4X-BV4XG-34TV4
·Windows Server 2008 R2 Release Candidate Datacenter(数据中心版)
Product Code ： WXGKX-XXW8X-P8KTJ-PFX7T-DPYYW
·Windows Web Server 2008 R2 Release Candidate(WEB版)
Product Code： RBBKH-BVD6B-74FV9-RYPJ7-TCFXB
...................................................
Windows Server 2008 Enterprise RC1
产品密钥 1: HVFX4-C6DY3-M792V-DBXXG-8T24Q
产品密钥 2: 83XTG-V8DHP-TF73Y-G7MCX-4Q4XB
产品密钥 3: H6BXB-CQWDR-QRRJD-9HV7R-TMGKJ
产品密钥 4: CV3TD-JJ4G7-P2TJG-3MMXH-YXRWR
产品密钥 5: H6V9C-PJF42-H29WV-HW334-WYYM4
Windows Server 2008 Standard RC1
产品密钥 1: VWRJT-DJJYR-QG7YD-Q7X73-TQCHT
产品密钥 2: 87PC6-CTW7M-C3DVH-TYGGR-BRJPM
产品密钥 3: YKYMG-C68WD-4RCGB-3FMJT-FG637
产品密钥 4: TKGXB-G6PYQ-Q7F3M-G9HJW-TXCBT
产品密钥 5: Q642B-4WHQF-DPQT4-WCDJJ-J7RG2
Windows Server 2008 Datacenter RC1
产品密钥 1: QX9DX-DYXT8-G3CMF-G4F9F-Y9MPP
产品密钥 2: GDQRG-PX42M-YYYBK-7Y7XD-G76GP
产品密钥 3: RDPFX-8TPGR-3PMCX-P68W7-JTCWP
产品密钥 4: C2YRQ-4JVDJ-GCCTG-Y3JWB-GXTQJ
产品密钥 5: MXD74-82KC7-MV8MR-XRMK9-WVT7R
................................................
2000 RC-1/SP-1
K4CJ8-XHQMW-YF7HH-MYRGM-J3DRW
WINDOWS 7 Release Candidate 1:
C43GM-DWWV8-V6MGY-G834Y-Y8QH3
6JQ32-Y9CGY-3Y986-HDQKT-BPFPG
KBHBX-GP9P3-KH4H4-HKJP4-9VYKQ
GPRG6-H3WBB-WJK6G-XX2C7-QGWQ9
P72QK-2Y3B8-YDHDV-29DQB-QKWWM
Q3VMJ-TMJ3M-99RF9-CVPJ3-Q7VF3
BCGX7-P3XWP-PPPCV-Q2H7C-FCGFR
9JBBV-7Q7P7-CTDB7-KYBKG-X8HHC
KGMPT-GQ6XF-DM3VM-HW6PR-DX9G8
MT39G-9HYXX-J3V3Q-RPXJB-RQ6D7
MM7DF-G8XWM-J2VRG-4M3C4-GR27X
MVBCQ-B3VPW-CT369-VM9TB-YFGBP
MVYTY-QP8R7-6G6WG-87MGT-CRH2P
6F4BB-YCB3T-WK763-3P6YJ-BVH24
RGQ3V-MCMTC-6HP8R-98CDK-VP3FM
............................................
Microsoft Office 2000 Beta 2 :
s/n: BBH2G-D2VK9-QD4M9-F63XB-43C33 or
s/n: MP4F9-W6C8V-HTCCT-T7M7R-Y7K3Y
Microsoft SMS 2.0 beta2 For WindowsNT :
s/n: 11111-11111-11111-11111-11111
Microsoft SQL Server 7.0 Enterprise Edition Build 611 :
s/n: 111-1111111
Microsoft Windows 98 OEM Service Release 1 Beta 1 :
s/n: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
（此处合并）
Microsoft Windows 98 OSR Beta Refresh :
Microsoft Windows 98 OSR1 v4.10.2126 :
Microsoft Windows 98 OSR1 v4.10.2131 :
Microsoft Windows 98 OSR1 Build 2150 :
Microsoft Windows 98 OSR1 Beta 2 :
Microsoft Windows 98 Second edition Build 2162 :
CD-Key: C9TCH-G72Y6-G4DQK-QCQRM-K7XFQ
..................................................
Windows 95 (build 490) .........................................100-1208613
................................................................757-2573155
................................................................875-7215850
..................................................
Windows XP Build 2446, 2454 & 2458 CD-Key: QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
Windows XP Beta 2 (2462)
CD-Key: DW3CF-D7KYR-KMR6C-3X7FX-T8CVM
Windows XP Build 2469
CD-Key: Q3R8Y-MP9KD-3M6KB-383YB-7PK9Q
Windows XP Build 2474 - 2499
CD-Key: DTWB2-VX8WY-FG8R3-X696T-66Y46
Windows XP Build 2502-2505 (RC1)
CD-Key: BJXGH-4TG7P-F9PRP-K6FJD-JQMPM
Windows XP 25xx/350x (60 Days)
CD-Key: RK7J8-2PGYQ-P47VV-V6PMB-F6XPQ
Windows XP 2542+ (30 Days) Home
CD-Key: BQJG2-2MJT7-H7F6K-XW98B-4HQRQ
Windows XP 2542+ (30 Days) Pro
CD-Key: BX6HT-MDJKW-H2J4X-BX67W-TVVFG
Windows XP PRE-RTM 2600
CD-Key: BX6HT-MDJKW-H2J4X-BX67W-TVVFG
BX6HT-MDJKW-H2J4X-BX67W-TVVFG (2542專業人員僅僅)[2600]
BQJG2-2MJT7-H7F6K-XW98B-4HQRQ (2542個人僅僅）
Microsoft Whistler Professional Beta 2 2462繁體中文版 S/N：QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
Microsoft Windows Millennium B2 V4.90.2438 98 第三版中文完整測試版 S/N：RBDC9-VTRC8-D7972-J97JY-PRVMG
Microsoft Windows Whistler Pro CD-Key：
F6PGG-4YYDJ-3FF3T-R328P-3BXTG
Microsoft Windows XP 2428 中文版
S/N：F6PGG-4YYDJ-3FF3T-R328P-3BXTG or
S/N：RBDC9-VTRC8-D7972-J97JY-PRVMG or
S/N：QB2BW-8PJ2D-9X7JK-BCCRT-D233Y
Microsoft Windows XP Professional Beta2 build 2505) 中文繁體專業完整版
S/N：RK7J8-2PGYQ-P47VV-V6PMB-F6XPQ
..................................................
Windows Millennium Beta 2 Build 2419.5 S/N:RBDC9-VTRC8-D7972-J97JY-PRVMG
..................................................
Microsoft Whistler Person build 2410－－ SN：F6PGG-4YYDJ-3FF3T-R328P-3BXTG
Microsoft Windows Whistler Pro
CD-Key：F6PGG-4YYDJ-3FF3T-R328P-3BXTG
Microsoft Windows XP 2428 S/N：F6PGG-4YYDJ-3FF3T-R328P-3BXTG or
S/N：RBDC9-VTRC8-D7972-J97JY-PRVMG
..................................................
Microsoft Windows 2003 .NET
版本: Enterprise Edition
网址: www.microsoft.com
s/n: G4GC3-PWBMF-36BH6-3RXK8-D9V23 AktivationKey: 119501-164671-893012-496996-208900-871600-717516
Microsoft Windows Server 2003
版本: Enterprise rc2 Beta2
网址: www.microsoft.com
s/n: VQ83Q-89DJ9-X9TG9-QF6MC-FRV2D
Microsoft Windows Vista
版本: Beta 2 Build 5270
网址: www.microsoft.com
S/N: R4HB8-QGQK4-79X38-QH3HK-Q3PJ6
Microsoft Windows Vista
版本: Build 5308
网址: www.microsoft.com
S/N: Client_S/N: R4HB8-QGQK4-79X38-QH3HK-Q3PJ6
Server_S/N: WBVG8-4JPQB-6HJ6H-XH7YY-D2GQY
Microsoft Windows Whistler
版本: RC1 and RC2
s/n: BFB47-3C7FY-WHR6H-G9X4D-7TTFJ or s/n: RK7J8-2PGYQ-P47VV-V6PMB-F6XPQ
Microsoft Windows Whistler
版本: 2542 Pro
s/n: BX6HT-MDJKW-H2J4X-BX67W-TVVFG
Microsoft Windows Whistler
版本: 2542 Personal
s/n: BQJG2-2MJT7-H7F6K-XW98B-4HQRQ
WINDOWS 97 BETA : MENPHIS
网址: www.microsoft.com
2859500057111-34276
Windows
版本: Whistler
网址: www.microsoft.com
s/n: F6PGG-4YYDJ-3FF3T-R328P-3BXTG or s/n: DW3CF-D7KYR-KMR6C-3X7FX-T8CVM
Windows .NET Server 2003 German
版本: Enterprise RC2
网址: www.microsoft.com/windows.net
s/n: CKY24-Q8QRH-X3KMR-C6BCY-T847Y
Windows .Net Enterprise Server for itanium
网址: www.microsoft.com/
s/n: K74W7-WR4HR-H7P6B-4V9BF-XJD6Y
Windows 2003
版本: Candidated Release 2
网址: http://www.tcs.com
s/n: HJYCJ-647BB-76FYQ-J76JT-P78XD
Windows 2003
版本: Server.net
网址: http://www.tcs.com
s/n: K4RBR-F3K42-M9RXG-48TPR-H6BPB or s/n: C4C24-QDY9P-GQJ4F-2DB6G-PFQ9W
Windows 2003
版本: (.NET) German Retail
网址: http://www.tcs.com
s/n: C4C24-QDY9P-GQJ4F-2DB6G-PFQ9W
Windows 2003 Server
版本: .net
网址: www.microsoft.com
s/n: K4RBR-F3K42-M9RXG-48TPR-H6BPB or QW32K-48T2T-3D2PJ-DXBWY-C6WRJ or C4C24-QDY9P-GQJ4F-2DB6G-PFQ9W
microsoft windows xp home eidition
版本: sp2 built 2162
S/N: wwwjr-bx7cv-p32x2-c7vt3-qd6bp
Win95 Key计算
WINDOWS95 只要合於下述公式之序號，不必原告指定的「唯一」序號，仍可安裝。 ＡＢＣＤＥ-ＦＧＨ-ＩＪＫＬＭＮＯ-ＰＱＲＳＴ 1. ＡＢＣ 為 001 至 366 之間的三位數字。 2. Ｄ 為一固定數字 9 。 3. Ｅ為介於 5 至 9 之間的一位數字。 4. ＦＧＨ為英文字母 OEM 或 oem 皆可。 5. Ｉ為一固定數字 0。 6. ＪＫＬＭＮＯ 此六個數字之和為 7的倍數， 即Ｊ+Ｋ+Ｌ+Ｍ+Ｎ+Ｏ= 7×n ( n 為常整數 ) 7. ＰＱＲＳＴ 為介於 00000至99999之間的五位數字。 8. 此一公式，經測試，僅有一、二組無法使用。
Win3.2 doc
[Anonymous] 2020-01-18 23:05:01 3.2简体中文定制版那是微软中国专门定制的版本 [Anonymous] 2020-01-18 23:05:30 3.2的出现是被迫的。 [Anonymous] 2020-01-18 23:06:29 上次讨论的就是为什么明明有3.1，还要做3.2。 [Anonymous] 2020-01-18 23:08:06 3.2是中易宋体 [Anonymous] 2020-01-18 23:11:58 windows 3.2 之所以说是真正的官方定制版，是因为不仅仅系统深度汉化，而且系统中不支持中文的环境结构，也做了修改 [Anonymous] 23:12:39 让系统对于中文不再有“不兼容”的问题 [Anonymous] 23:13:21 而之前说的 3.1 的中文版，实际上只是个“浅显汉化版” [Anonymous] 23:14:59 3.1只是“UI”上汉化成了中文，然后加上了外挂式的中文显示环境 [Anonymous] 23:15:24 但实际上，3.1的内核，对于中文的支持是相当糟糕的 [Anonymous] 23:15:37 兼容性问题一大把 [Anonymous] 23:17:17 当时3.1刚出来时，只有“南极星”或者“中文之星”这样的“外挂汉字平台” [Anonymous] 2020-01-18 23:15:54 后来这件事还被传成了阴谋论，说微软发行3.2直接掐死了一些中文汉字软件 [Anonymous] 2020-01-18 23:16:46 所以我才说3.1和3.2背后的迷太多。 [Anonymous] 2020-01-18 23:17:22 说3.2是阴谋的也好，说3.2是我方强迫的也好， [Anonymous] 2020-01-18 23:22:55 7、8年前我专门给微软发过邮件，问过3.2这个版本是怎么来的时，微软有过粗略的解释 [Anonymous] 2020-01-18 23:33:42 当时微软回复的大概意思就是说： 3.2是为了适应市场需要，同时修复3.1版本对中文的核心兼容性问题，而专门定做和完善的版本，针对印刷和照排行业的需要，做了深度的改进 而且，3.2定制版的实践积累，为后来的朝鲜语、日语及其它东亚语言版本的完善，提供了宝贵的经验 [Anonymous] 2020-01-18 23:36:48 3.2这种东西有点类似于Windows 8 Chinese Language Edition吗 [Anonymous] 2020-01-18 23:37:47 实际上，3.2的重要性和意义，远超于你说的“单语言中文版” [Anonymous] 2020-01-18 23:38:21 3.2实际上是在积累东亚语言的定制经验 [Anonymous] 2020-01-18 23:39:36 也就是说，3.2中文版，是当时的“示例” [Anonymous] 2020-01-19 17:01:07 windows3.2+word6 几乎横扫所有非照排系统
Win95 RTM HellGod Warez(READNOW.TXT)
SuP all.... Well, here it is WINDOWS 95 GOLD.... this is the FINAL release that will be in stores on August 24th.... when you got to "System" to find out the version it'll say 4.00.950... DO NOT BE ALARMED.... you might say "duh, this is just 950!" WRONG.... the first version of 950 was 950 -r2 this is the GOLD version......the FINAL version This KICK ASS WaRe brought to you by the ONE AND ONLY: H e L L G o D Whenever ya see me in WaReZ or anywhere else, say, "SuP HeLL GoD!" This GREAT ware brought to you in accordance with swoop...... Greetz to aLL WaReZ gr00ps from HeLL GoD.....
其他细碎拮文
- 系统的启动问题！
我的机器装了Windows Whistler Advanced Server(5.00.2442)后，开始运行还能进系统，可差不多重启几次之后，就再也进不去了，老是定格在出现Logo之后，用Safe Mode也进不去，重装之后还是有问题，怎么办呢？万望赐教！
https://bbs.csdn.net/topics/10442785
- 关于在WindowsXP（ beta2 2442）下安装内猫的问题
我的内猫型号为TP—LINK的rockwell的11235芯片的5689HCF内猫，在WindowsXP（ beta2 2442）下安装TP—LINK公司的FOR WIN2000驱动，系统提示没有数字签名，继续安装系统自动重启，且显示为非正常关机。再次进入系统，能够找到猫但是驱动未安装，再次进行安装依然如此。但同样没有数字签名的NVIDIA的12.40驱动就能运行正常，请各位大虾赐教！
https://bbs.csdn.net/topics/115474
远古Windows 98 Beta版本列表
http://www.wintricks.it/faqlamer/win-ver.html
最迟的列表可能出现时间为2001年。仅供参考，列表中有错误信息！
- PAGINA 1/2
In questa tabella riassuntiva ho ritenuto utile inserire il semplice database di tutte le vers. di Windows 9x uscite sinora.....
da WINDOWS 95 a 98 VERSIONI + TABELLA
| RELEASE S.O. | VERSIONE | REVISIONE MS-DOS |
DATA + ORA | BUILD |
|---|---|---|---|---|
| Windows 95 final retail | 4.00.0950 | 7.00 [4.00.0950] | 07-11-95 + 09:50:00 | 4.00.0950 |
| Windows 95 final OEM | 4.00.0950 | 7.00 [4.00.0950] | 07-11-95 + 09:50:00 | 4.00.0950 |
| Windows 95a OSR1 final Update | 4.00.0950 a | 7.00 [4.00.0950] | 02-02-96 + 09:51:00 | 4.00.0951 |
| Windows 95B OSR 2.0 final OEM | 4.00.0950 B | 7.10 [4.00.1111] | 08-24-96 + 11:11:11 | 4.00.1111 |
| Windows 95B OSR 2.1 final Update | 4.00.0950 B | 7.10 [4.00.1111] | 04-10-97 + 12:14:00 | 4.03.1212 |
| Windows 95B OSR 2.1 final OEM | 4.01.0971 B | 7.10 [4.00.1111] | 06-25-97 + 09:07:10 | 4.01.0971 |
| Windows 95C OSR 2.5 final OEM | 4.00.0950 C | 7.10 [4.00.1111] | 11-26-97 + 12:16:00 | 4.03.1214 |
| Windows 98 Beta | ||||
| Windows 98 Beta pre-DR | 4.10.1351 | 7.10 [4.10.1351] | 12-16-96 + 13:51:00 | 4.10.1351 |
| Windows 98 Beta DR | 4.10.1358 | 7.10 [4.10.1358] | 12-20-96 + 13:58:00 | 4.10.1358 |
| Windows 98 pre Beta | 4.10.1378 | 7.10 [4.10.1378] | ? + ? | 4.10.1378 |
| Windows 98 pre Beta | 4.10.1410 | 7.10 [4.10.1410] | ? + ? | 4.10.1410 |
| Windows 98 pre Beta | 4.10.1423 | 7.10 [4.10.1423] | 04-08-97 + 04:23:00 | 4.10.1423 |
| Windows 98 Beta 1 | 4.10.1500 | 7.10 [4.10.1500] | ? + ? | 4.10.1500 |
| Windows 98 Beta 1 | 4.10.1508 | 7.10 [4.10.1508] | ? + ? | 4.10.1508 |
| Windows 98 Beta 1 | 4.10.1511 | 7.10 [4.10.1511] | ? + ? | 4.10.1511 |
| Windows 98 Beta 1 | 4.10.1525 | 7.10 [4.10.1525] | 06-18-97 + 10:09:00 | 4.10.1525 |
| Windows 98 Beta 1 | 4.10.1535 | 7.10 [4.10.1535] | 07-02-97 + 15:35:00 | 4.10.1535 |
| Windows 98 Beta 1 | 4.10.1538 | 7.10 [4.10.1538] | 07-12-97 + 15:38:00 | 4.10.1538 |
| Windows 98 Beta 1 | 4.10.1543 | 7.10 [4.10.1543] | ? + ? | 4.10.1543 |
| Windows 98 Beta 2 | 4.10.1544 | 7.10 [4.10.1544] | 07-31-97 + 15:44:00 | 4.10.1544 |
| Windows 98 Beta 2 | 4.10.1546 | 7.10 [4.10.1546] | 08-02-97 + 15:46:00 | 4.10.1546 |
| Windows 98 Beta 2 | 4.10.1550 | 7.10 [4.10.1550] | 08-10-97 + 17:21:00 | 4.10.1550 |
| Windows 98 Beta 2 | 4.10.1559 | 7.10 [4.10.1559] | 08-11-97 + 15:50:00 | 4.10.1559 |
| Windows 98 Beta 2 | 4.10.1564 | 7.10 [4.10.1564] | 08-14-97 + 15:50:00 | 4.10.1564 |
| Windows 98 Beta 2 | 4.10.1569 | 7.10 [4.10.1569] | 08-22-97 + 15:50:00 | 4.10.1569 |
| Windows 98 Beta 2 | 4.10.1577 | 7.10 [4.10.1577] | 09-04-97 + 15:50:00 | 4.10.1577 |
| Windows 98 Beta 2 | 4.10.1581 | 7.10 [4.10.1581] | 09-10-97 + 15:50:00 | 4.10.1581 |
| Windows 98 Beta 2 | 4.10.1593 | 7.10 [4.10.1593] | 09-25-97 + 15:50:00 | 4.10.1593 |
| Windows 98 Beta 2 | 4.10.1599 | 7.10 [4.10.1599] | 10-08-97 + 15:50:00 | 4.10.1599 |
| Windows 98 Beta 3 | 4.10.1602 | 7.10 [4.10.1602] | ? + ? | 4.10.1602 |
| Windows 98 Beta 3 | 4.10.1605 | 7.10 [4.10.1605] | ? + ? | 4.10.1605 |
| Windows 98 Beta 3 | 4.10.1614 | 7.10 [4.10.1614] | 10-24-97 + 16:14:00 | 4.10.1614 |
| Windows 98 Beta 3 | 4.10.1619 | 7.10 [4.10.1619] | 10-31-97 + 16:19:00 | 4.10.1619 |
| Windows 98 Beta 3 | 4.10.1624 | 7.10 [4.10.1624] | 11-06-97 + 16:24:00 | 4.10.1624 |
| Windows 98 Beta 3 | 4.10.1629 | 7.10 [4.10.1629] | 11-14-97 + 16:29:00 | 4.10.1629 |
| Windows 98 Beta 3 | 4.10.1633 | 7.10 [4.10.1633] | 11-18-97 + 16:33:00 | 4.10.1633 |
| Windows 98 Beta 3 | 4.10.1650 | 7.10 [4.10.1650] | 11-26-97 + 16:50:00 | 4.10.1650 |
| Windows 98 Beta 3 | 4.10.1650.3 | 7.10 [4.10.1653] | 12-03-97 + 16:50:03 | 4.10.1650.3 |
| Windows 98 Beta 3 | 4.10.1650.8 | 7.10 [4.10.1658] | 12-09-97 + 16:50:08 | 4.10.1650.8 |
| Windows 98 Beta 3 | 4.10.1666 | 7.10 [4.10.1666] | 01-14-98 + 16:06:06 | 4.10.1666 |
| Windows 98 Beta 3 | 4.10.1671 | 7.10 [4.10.1671] | 01-20-98 + 16:07:10 | 4.10.1671 |
| Windows 98 Beta 3 | 4.10.1677 | 7.10 [4.10.1677] | 01-30-98 + 16:07:07 | 4.10.1677 |
| Windows 98 Beta 3 | 4.10.1681 | 7.10 [4.10.1681] | 02-05-97 + 16:08:10 | 4.10.1681 |
| Windows 98 Beta 3 | 4.10.1687 | 7.10 [4.10.1687] | 02-12-98 + 16:08:07 | 4.10.1687 |
- PAGINA 2/2
Windows 98 a partire dalla vers. RC
WINDOWS 98 VERSIONI + TABELLA
| RELEASE S.O. | VERSIONE | REVISIONE MS-DOS |
DATA + ORA | BUILD |
|---|---|---|---|---|
| Windows 98 RC | ||||
| Windows 98 Beta RC0 | 4.10.1691 | 7.10 [4.10.1691] | 02-16-98 + 12:16:00 | 4.10.1691 |
| Windows 98 Beta RC0 | 4.10.1702 | 7.10 [4.10.1702] | 03-05-98 + 12:17:00 | 4.10.1702 |
| Windows 98 Beta RC0 | 4.10.1708 | 7.10 [4.10.1708] | 03-12-98 + 12:17:00 | 4.10.1708 |
| Windows 98 Beta RC0 | 4.10.1713 | 7.10 [4.10.1713] | 03-19-98 + 12:17:00 | 4.10.1713 |
| Windows 98 Beta RC1 | 4.10.1721.3 | 7.10 [4.10.1721] | 03-30-98 + 17:21:40 | 4.10.1721.3 |
| Windows 98 Beta RC2 | 4.10.1723.4 | 7.10 [4.10.1723] | 04-10-98 + 17:23:40 | 4.10.1723.4 |
| Windows 98 Beta RC2 | 4.10.1726 | 7.10 [4.10.1726] | 04-18-98 + 17:26:00 | 4.10.1726 |
| Windows 98 Beta RC3 | 4.10.1900.5 | 7.10 [4.10.1900] | 04-24-98 + 19:05:00 | 4.10.1900.5 |
| Windows 98 Beta RC4 | 4.10.1900.8 | 7.10 [4.10.1900] | 04-28-98 + 19:08:00 | 4.10.1900.8 |
| Windows 98 Beta RC5 | 4.10.1998 | 7.10 [4.10.1998] | 05-06-98 + 19:09:08 | 4.10.1998 |
| Windows 98 | ||||
| Windows 98 final retail | 4.10.1998.6 | 7.10 [4.10.1998] | 05-11-98 + 20:01:00 | 4.10.1998.6 |
| Windows 98 final OEM | 4.10.1998.6 | 7.10 [4.10.1998] | 05-11-98 + 20:01:00 | 4.10.1998.6 |
| Windows 98 OSR 1 Beta | ||||
| Windows 98 SP1 Beta 1 | 4.10.2088 | 7.10 [4.10.2088] | 10-01-98 + 20:08:08 | 4.10.2088 |
| Windows 98 OSR1 Beta 1 | 4.10.2106 | 7.10 [4.10.2106] | 11-18-98 + 21:06:00 | 4.10.2106 |
| Windows 98 OSR1 Beta 1 | 4.10.2120 | 7.10 [4.10.2120] | 12-20-98 + 21:20:00 | 4.10.2120 |
| Windows 98 OSR1 Beta 1 | 4.10.2126 | 7.10 [4.10.2126] | 01-08-99 + 21:26:00 | 4.10.2126 |
| Windows 98 OSR1 Beta 1 | 4.10.2131 | 7.10 [4.10.2131] | 01-21-99 + 21:31:00 | 4.10.2131 |
| Windows 98 SP1 Beta 2 | 4.10.2150.0 | 7.10 [4.10.2150] | 01-05-99 + 21:50:00 | 4.10.2150.0 |
| Windows 98 SP1 Beta 2 | 4.10.2150.4 | 7.10 [4.10.2150] | 02-25-99 + 21:50:04 | 4.10.2150.4 |
| Windows 98 SP1 final Update | 4.10.2000 | 7.10 [4.10.1998] | 05-26-99 + 08:00:00 | 4.10.2000 |
| Windows 98 OSR1 Beta 2 | 4.10.2174 | 7.10 [4.10.2174] | 03-21-99 + 21:07:40 | 4.10.2174 |
| Windows 98 SE Beta RC1 | 4.10.2183 | 7.10 [4.10.2183] | 04-11-99 + 21:08:30 | 4.10.2183 |
| Windows 98 SE Beta RC2 | 4.10.2185 | 7.10 [4.10.2185] | 04-18-99 + 21:08:50 | 4.10.2185 |
| Windows 98 SE Beta RC3 | 4.10.2222 | 7.10 [4.10.2222] | 04-20-99 + 22:22:00 | 4.10.2222 |
| Windows 98 Second edition | ||||
| Windows 98 SE final retail | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
| Windows 98 SE final OEM | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
| Windows 98 SE Updates final | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
远古Windows 98 Beta版本列表 2
最迟的列表可能出现时间为2004年。仅供参考，列表中有错误信息！
| OS RELEASE | VERSION | MS-DOS REVISION | DATE + TIME | BUILD |
|---|---|---|---|---|
| Windows 95 retail final | 4.00.0950 | 7.00 [4.00.0950] | 07-11-95 + 09:50:00 | 4.00.0950 |
| Windows 95 OEM final | 4.00.0950 | 7.00 [4.00.0950] | 07-11-95 + 09:50:00 | 4.00.0950 |
| Windows 95 Upgrade final | 4.00.0950 | 7.00 [4.00.0950] | 07-11-95 + 09:50:00 | 4.00.0950 |
| Windows 95a OSR1 Update final | 4.00.0950 a | 7.00 [4.00.0950] | 02-02-96 + 09:51:00 | 4.00.0951 |
| Windows 95B OSR 2.0 OEM final | 4.00.0950 B | 7.10 [4.00.1111] | 08-24-96 + 11:11:11 | 4.00.1111 |
| Windows 95B OSR 2.1 Update final | 4.00.0950 B | 7.10 [4.00.1111] | 04-10-97 + 12:14:00 | 4.03.1212 |
| Windows 95B OSR 2.1 OEM final | 4.01.0971 B | 7.10 [4.00.1111] | 06-25-97 + 09:07:10 | 4.01.0971 |
| Windows 95C OSR 2.5 OEM final | 4.00.0950 C | 7.10 [4.00.1111] | 11-26-97 + 12:16:00 | 4.03.1214 |
| Windows 98 Beta pre-DR | 4.10.1351 | 7.10 [4.10.1351] | 12-16-96 + 13:51:00 | 4.10.1351 |
| Windows 98 Beta DR | 4.10.1358 | 7.10 [4.10.1358] | 12-20-96 + 13:58:00 | 4.10.1358 |
| Windows 98 early Beta | 4.10.1378 | 7.10 [4.10.1378] | ? + ? | 4.10.1378 |
| Windows 98 early Beta | 4.10.1410 | 7.10 [4.10.1410] | ? + ? | 4.10.1410 |
| Windows 98 early Beta | 4.10.1423 | 7.10 [4.10.1423] | 04-08-97 + 04:23:00 | 4.10.1423 |
| Windows 98 Beta 1 | 4.10.1500 | 7.10 [4.10.1500] | ? + ? | 4.10.1500 |
| Windows 98 Beta 1 | 4.10.1508 | 7.10 [4.10.1508] | ? + ? | 4.10.1508 |
| Windows 98 Beta 1 | 4.10.1511 | 7.10 [4.10.1511] | ? + ? | 4.10.1511 |
| Windows 98 Beta 1 | 4.10.1525 | 7.10 [4.10.1525] | 06-18-97 + 10:09:00 | 4.10.1525 |
| Windows 98 Beta 1 | 4.10.1535 | 7.10 [4.10.1535] | 07-02-97 + 15:35:00 | 4.10.1535 |
| Windows 98 Beta 1 | 4.10.1538 | 7.10 [4.10.1538] | 07-12-97 + 15:38:00 | 4.10.1538 |
| Windows 98 Beta 1 | 4.10.1543 | 7.10 [4.10.1543] | ? + ? | 4.10.1543 |
| Windows 98 Beta 2 | 4.10.1544 | 7.10 [4.10.1544] | 07-31-97 + 15:44:00 | 4.10.1544 |
| Windows 98 Beta 2 | 4.10.1546 | 7.10 [4.10.1546] | 08-02-97 + 15:46:00 | 4.10.1546 |
| Windows 98 Beta 2 | 4.10.1550 | 7.10 [4.10.1550] | 08-10-97 + 17:21:00 | 4.10.1550 |
| Windows 98 Beta 2 | 4.10.1559 | 7.10 [4.10.1559] | 08-11-97 + 15:50:00 | 4.10.1559 |
| Windows 98 Beta 2 | 4.10.1564 | 7.10 [4.10.1564] | 08-14-97 + 15:50:00 | 4.10.1564 |
| Windows 98 Beta 2 | 4.10.1569 | 7.10 [4.10.1569] | 08-22-97 + 15:50:00 | 4.10.1569 |
| Windows 98 Beta 2 | 4.10.1577 | 7.10 [4.10.1577] | 09-04-97 + 15:50:00 | 4.10.1577 |
| Windows 98 Beta 2 | 4.10.1581 | 7.10 [4.10.1581] | 09-10-97 + 15:50:00 | 4.10.1581 |
| Windows 98 Beta 2 | 4.10.1593 | 7.10 [4.10.1593] | 09-25-97 + 15:50:00 | 4.10.1593 |
| Windows 98 Beta 2 | 4.10.1599 | 7.10 [4.10.1599] | 10-08-97 + 15:50:00 | 4.10.1599 |
| Windows 98 Beta 3 | 4.10.1602 | 7.10 [4.10.1602] | ? + ? | 4.10.1602 |
| Windows 98 Beta 3 | 4.10.1605 | 7.10 [4.10.1605] | ? + ? | 4.10.1605 |
| Windows 98 Beta 3 | 4.10.1614 | 7.10 [4.10.1614] | 10-24-97 + 16:14:00 | 4.10.1614 |
| Windows 98 Beta 3 | 4.10.1619 | 7.10 [4.10.1619] | 10-31-97 + 16:19:00 | 4.10.1619 |
| Windows 98 Beta 3 | 4.10.1624 | 7.10 [4.10.1624] | 11-06-97 + 16:24:00 | 4.10.1624 |
| Windows 98 Beta 3 | 4.10.1629 | 7.10 [4.10.1629] | 11-14-97 + 16:29:00 | 4.10.1629 |
| Windows 98 Beta 3 | 4.10.1633 | 7.10 [4.10.1633] | 11-18-97 + 16:33:00 | 4.10.1633 |
| Windows 98 Beta 3 | 4.10.1650 | 7.10 [4.10.1650] | 11-26-97 + 16:50:00 | 4.10.1650 |
| Windows 98 Beta 3 | 4.10.1650.3 | 7.10 [4.10.1653] | 12-03-97 + 16:50:03 | 4.10.1650.3 |
| Windows 98 Beta 3 | 4.10.1650.8 | 7.10 [4.10.1658] | 12-09-97 + 16:50:08 | 4.10.1650.8 |
| Windows 98 Beta 3 | 4.10.1666 | 7.10 [4.10.1666] | 01-14-98 + 16:06:06 | 4.10.1666 |
| Windows 98 Beta 3 | 4.10.1671 | 7.10 [4.10.1671] | 01-20-98 + 16:07:10 | 4.10.1671 |
| Windows 98 Beta 3 | 4.10.1677 | 7.10 [4.10.1677] | 01-30-98 + 16:07:07 | 4.10.1677 |
| Windows 98 Beta 3 | 4.10.1681 | 7.10 [4.10.1681] | 02-05-97 + 16:08:10 | 4.10.1681 |
| Windows 98 Beta 3 | 4.10.1687 | 7.10 [4.10.1687] | 02-12-98 + 16:08:07 | 4.10.1687 |
| Windows 98 RC0 | 4.10.1691 | 7.10 [4.10.1691] | 02-16-98 + 12:16:00 | 4.10.1691 |
| Windows 98 RC0 | 4.10.1702 | 7.10 [4.10.1702] | 03-05-98 + 12:17:00 | 4.10.1702 |
| Windows 98 RC0 | 4.10.1708 | 7.10 [4.10.1708] | 03-12-98 + 12:17:00 | 4.10.1708 |
| Windows 98 RC0 | 4.10.1713 | 7.10 [4.10.1713] | 03-19-98 + 12:17:00 | 4.10.1713 |
| Windows 98 RC1 | 4.10.1721.3 | 7.10 [4.10.1721] | 03-30-98 + 17:21:40 | 4.10.1721.3 |
| Windows 98 RC2 | 4.10.1723.4 | 7.10 [4.10.1723] | 04-10-98 + 17:23:40 | 4.10.1723.4 |
| Windows 98 RC2 | 4.10.1726 | 7.10 [4.10.1726] | 04-18-98 + 17:26:00 | 4.10.1726 |
| Windows 98 RC3 | 4.10.1900.5 | 7.10 [4.10.1900] | 04-24-98 + 19:05:00 | 4.10.1900.5 |
| Windows 98 RC4 | 4.10.1900.8 | 7.10 [4.10.1900] | 04-28-98 + 19:08:00 | 4.10.1900.8 |
| Windows 98 RC5 | 4.10.1998 | 7.10 [4.10.1998] | 05-06-98 + 19:09:08 | 4.10.1998 |
| Windows 98 retail final | 4.10.1998 | 7.10 [4.10.1998] | 05-11-98 + 20:01:00 | 4.10.1998.6 |
| Windows 98 OEM final | 4.10.1998 | 7.10 [4.10.1998] | 05-11-98 + 20:01:00 | 4.10.1998.6 |
| Windows 98 Upgrade final | 4.10.1998 | 7.10 [4.10.1998] | 05-11-98 + 20:01:00 | 4.10.1998.6 |
| Windows 98 SP1 Beta 1 | 4.10.2088 | 7.10 [4.10.2088] | 10-01-98 + 20:08:08 | 4.10.2088 |
| Windows 98 OSR1 Beta 1 | 4.10.2106 | 7.10 [4.10.2106] | 11-18-98 + 21:06:00 | 4.10.2106 |
| Windows 98 OSR1 Beta 1 | 4.10.2120 | 7.10 [4.10.2120] | 12-20-98 + 21:20:00 | 4.10.2120 |
| Windows 98 OSR1 Beta 1 | 4.10.2126 | 7.10 [4.10.2126] | 01-08-99 + 21:26:00 | 4.10.2126 |
| Windows 98 OSR1 Beta 1 | 4.10.2131 | 7.10 [4.10.2131] | 01-21-99 + 21:31:00 | 4.10.2131 |
| Windows 98 SP1 Beta 2 | 4.10.2150.0 | 7.10 [4.10.2150] | 01-05-99 + 21:50:00 | 4.10.2150.0 |
| Windows 98 SP1 Beta 2 | 4.10.2150.4 | 7.10 [4.10.2150] | 02-25-99 + 21:50:04 | 4.10.2150.4 |
| Windows 98 SP1 Update final | 4.10.2000 | 7.10 [4.10.1998] | 05-26-99 + 08:00:00 | 4.10.2000 |
| Windows 98 OSR1 Beta 2 | 4.10.2174 | 7.10 [4.10.2174] | 03-21-99 + 21:07:40 | 4.10.2174 |
| Windows 98 SE RC1 | 4.10.2183 | 7.10 [4.10.2183] | 04-11-99 + 21:08:30 | 4.10.2183 |
| Windows 98 SE RC2 | 4.10.2185 | 7.10 [4.10.2185] | 04-18-99 + 21:08:50 | 4.10.2185 |
| Windows 98 SE RC3 | 4.10.2222 | 7.10 [4.10.2222] | 04-20-99 + 22:22:00 | 4.10.2222 |
| Windows 98 SE retail final | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
| Windows 98 SE OEM final | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
| Windows 98 SE Upgrade final | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
| Windows 98 SE Updates final | 4.10.2222 A | 7.10 [4.10.2222] | 04-23-99 + 22:22:00 | 4.10.2222.3 |
| Windows ME Beta DR1 | 4.90.2332 | 8.00 [4.90.2332] | 07-23-99 + 22:33:00 | 4.90.2332 |
| Windows ME Beta DR2 | 4.90.2348 | 8.00 [4.90.2348] | 08-06-99 + 23:48:00 | 4.90.2348 |
| Windows ME Beta DR3 | 4.90.2358 | 8.00 [4.90.2358] | 08-20-99 + 23:58:00 | 4.90.2358 |
| Windows ME Beta DR4 | 4.90.2363 | 8.00 [4.90.2363] | 08-27-99 + 23:06:03 | 4.90.2363 |
| Windows ME early Beta | 4.90.2368 | 8.00 [4.90.2368] | 09-03-99 + 23:06:08 | 4.90.2368 |
| Windows ME early Beta | 4.90.2374 | 8.00 [4.90.2374] | 09-13-99 + 23:07:04 | 4.90.2374 |
| Windows ME Beta 1 | 4.90.2380 | 8.00 [4.90.2380] | 09-24-99 + 23:08:00 | 4.90.2380 |
| Windows ME Beta 1 | 4.90.2394 | 8.00 [4.90.2394] | 10-13-99 + 23:09:04 | 4.90.2394 |
| Windows ME Beta 1 | 4.90.2399 | 8.00 [4.90.2399] | 10-22-99 + 23:09:09 | 4.90.2399 |
| Windows ME Beta 1 | 4.90.2404 | 8.00 [4.90.2404] | 10-29-99 + 00:44:00 | 4.90.2404 |
| Windows ME Beta 1 | 4.90.2410 | 8.00 [4.90.2410] | 11-05-99 + 00:11:00 | 4.90.2410 |
| Windows ME Beta 1 | 4.90.2416 | 8.00 [4.90.2416] | 11-15-99 + 00:16:00 | 4.90.2416 |
| Windows ME Beta 1 | 4.90.2419.4 | 8.00 [4.90.2419] | 11-19-99 + 00:19:04 | 4.90.2419.4 |
| Windows ME Beta 2 | 4.90.2429 | 8.00 [4.90.2429] | 12-10-99 + 00:29:00 | 4.90.2429 |
| Windows ME Beta 2 | 4.90.2434 | 8.00 [4.90.2434] | 12-20-99 + 00:34:00 | 4.90.2434 |
| Windows ME Beta 2 | 4.90.2443 | 8.00 [4.90.2443] | 01-07-00 + 00:43:00 | 4.90.2443 |
| Windows ME Beta 2 | 4.90.2447 | 8.00 [4.90.2447] | 01-14-00 + 00:47:00 | 4.90.2447 |
| Windows ME Beta 2 | 4.90.2455 | 8.00 [4.90.2455] | 01-31-00 + 00:55:00 | 4.90.2455 |
| Windows ME Beta 2 | 4.90.2460 | 8.00 [4.90.2460] | 02-04-00 + 00:06:00 | 4.90.2460 |
| Windows ME Beta 2 | 4.90.2465 | 8.00 [4.90.2465] | 02-11-00 + 00:06:05 | 4.90.2465 |
| Windows ME Beta 2 | 4.90.2470 | 8.00 [4.90.2470] | 02-18-00 + 00:07:00 | 4.90.2470 |
| Windows ME Beta 2 | 4.90.2474 | 8.00 [4.90.2474] | 02-25-00 + 00:07:04 | 4.90.2474 |
| Windows ME Beta 2 | 4.90.2481 | 8.00 [4.90.2481] | 03-03-00 + 00:08:01 | 4.90.2481 |
| Windows ME Beta 2 | 4.90.2487 | 8.00 [4.90.2487] | 03-10-00 + 00:08:07 | 4.90.2487 |
| Windows ME Beta 2 | 4.90.2491 | 8.00 [4.90.2491] | 03-17-00 + 00:09:01 | 4.90.2491 |
| Windows ME Beta 3 | 4.90.2499 | 8.00 [4.90.2499] | 03-27-00 + 00:09:09 | 4.90.2499 |
| Windows ME Beta 3 | 4.90.2499.3 | 8.00 [4.90.2499] | 03-30-00 + 00:09:09 | 4.90.2499.3 |
| Windows ME Beta 3 | 4.90.2509 | 8.00 [4.90.2509] | 04-18-00 + 00:25:09 | 4.90.2509 |
| Windows ME Beta 3 | 4.90.2513 | 8.00 [4.90.2513] | 04-21-00 + 00:25:13 | 4.90.2513 |
| Windows ME Beta 3 | 4.90.2516 | 8.00 [4.90.2516] | 04-28-00 + 00:25:16 | 4.90.2516 |
| Windows ME RC0 | 4.90.2525 | 8.00 [4.90.2525] | 05-08-00 + 00:25:25 | 4.90.2525 |
| Windows ME RC1 | 4.90.2525.6 | 8.00 [4.90.2525] | 05-17-00 + 00:25:25 | 4.90.2525.6 |
| Windows ME RC2 | 4.90.2535 | 8.00 [4.90.2535] | 06-05-00 + 00:25:35 | 4.90.2535 |
| Windows ME retail final | 4.90.3000 | 8.00 [4.90.3000] | 06-08-00 + 17:00:00 | 4.90.3000.2 |
| Windows ME OEM final | 4.90.3000 | 8.00 [4.90.3000] | 06-08-00 + 17:00:00 | 4.90.3000.2 |
| Windows ME Upgrade final | 4.90.3000 | 8.00 [4.90.3000] | 06-08-00 + 17:00:00 | 4.90.3000.2 |
| Windows ME Step-Up final | 4.90.3000 | 8.00 [4.90.3000] | 06-08-00 + 17:00:00 | 4.90.3000.2 |
来自defacto的Win98新闻
Tuesday 26th May (8:25pm GMT) It maybe beating a dead horse, but what the hey it fills space. If you remember about three weeks ago Krypto was very doubtful that Reality Check Network would be returning and claimed if it did return he would never rejoin. Well he has already contracted a famous scene coder to start work on a new Windows 95 interface for the magazine. The coder won't start until he has told by Krypto to begin. After two plus months of idling Scenelink has returned with a new look (again). This time around they have replaced the monthly features section with an articles area and added the famed Dupelink. Sunday 24th May (5:05pm GMT) Just incase you where wondering about those rumours of a PWA NFO being slipped onto a gold master of Windows98 before it went to press. Well they are completely false, as is the so-called modified code. There was also a webpage quoting a press release from Microsoft, and if you read it properly you could easily tell it was a fake. It contained lines that would never be used in a press release, like the one below. "Remember, if you are approached by one of these ex-employees, and they offer you source code to one of the many fine Microsoft releases, you are not entitled to use this code by law. Not even PWA is entitled to its use. Please return it. Please." Monday 18th May (6:42pm GMT) Game Over Online Magazine is now open for business. Read the previous days news for more information. Well the biggest os release since Windows 95 is now upon us, PWA brings you Windows 98 Retail Full Install at 21*5meg disks. Here is a note for people who require the other versiosn of Windows 98 from the PWA nfo. You need to download the CABS and the RETAIL SETUP and unzip/unrar everything into one directory. The reason for this is that as soon as I get install keys, I can release RETAIL UPGRADE, OEM FULL and OEM UPGRADE versions and they will only take 4 meg each (the CAB zips are generic thruout all these versions, I can just package up the differences in seperate zips to save everyone space and time). You just unzip whichever one you want into the same directory as the generic CAB zips.
另外单独的一则（这就是你ProductType辣么多的理由？）
Monday 15th December Nothing much happening today so I thought I might regurgitate some news that can be found in your local newspapers. After US District Court judge Thomas Jackson's decision to temporally stop Microsoft shipping Ie4 with Windows 95 there are now doubts that Windows 98 may ship in April. Though more realistic people say it will most likely ship in two different versions, one with Ie4 and one with out. So you may see six different versions (2 full and 4 upgrade) of Windows 95 on the selves by the time it comes out.
未泄露文件信息 随手一记
MS WinXP SP1 v1069 (OEM) usa_1069_csd_wxpsp1.iso 289.09 MB MSDN XP SP1 build 1050 (unk name) 235.55 MB XPSP1 v1073 (unk name) 121mb ............................................................ Windows XP Service Pack 2 build.2082 简体中文版 ed2k://|file|xpsp2_2082_chs_x86fre.iso|441059328|de08833a9597c991f25250e858d6bcd9|/ 简介: 现本网站发布最新的Windows.XP.SP2.RC1.2096 简体中文版补丁，望朋友们浏览下载。我这个已过时了，本人的任务也该完成了。请极个别没下完的朋友抓紧时间，我再做一天源。特鞠躬致谢下面回复的朋友！！！ 此次传输量: 软件简介： 微软终于释放了Windows XP Service Pack 2 build.2082 简体中文版,这个SP的第一个最终测试版,我们第一时间从BetaPlace找到了最新的版本提供给你 还等什么,快快下载尝鲜 测试表明：XP的安全性能大大加强，另外增加了网络防火墙。连ＩＥ６也一块升级到了ＳＰ２可以拦截广告和弹出窗口和一些脚本程序。安完后，多了安全中心。在OEM版本上测试升级成功,限于条件，其它版本未测试。 ISO格式。 注意：具体安装程序在update文件夹里，update.exe。 最好作备份！我已经安装完，现在没感觉有什么问题。欢迎喜欢尝鲜的朋友可不要埋怨我！ 关于此次升级包sp2太大的问题我认为可能是因为里面含有网络防火墙及防毒软件捆绑发售造成的（完全免费的啊！）我是从sp1升级的（当然用的是已激活的D版）已经两天了，程序正在自动升级，一切OK。 本人带宽有限（ADSL）请下完的朋友帮忙作源，我保证一星期内有效，请尽快！ 紧急告知！！！ 现已证明WINXP－SP2升级包已经把俄罗斯破解版给封杀了！！！在知道消息后便马上通知朋友们，其实上面写得很清楚这是SP的第一个最终测试版，请喜欢尝鲜的朋友们一定用GHOST作好备份，切记！！！ 再有从朋友们回复中我感觉SP2对国产防杀软件好象不支持，因为系统升级后已带有网络防火墙及防毒软件。我也是个菜鸟，解决不了任何问题。此次SP2升级包对我们大家都是个新鲜未知的东西，有什么埋怨骂微软，希望别算在我头上。 ............................................................................... Windows.XP.SP2.RC1.2096 简体中文版 ed2k://|file|xpsp2_2096_chs_x86fre_RC1.iso|367886336|e1faef49be1ff3905f707cc5e2b8ddfa|/ 简介: 最新的Windows.XP.SP2.RC1.2096 简体中文版,呵呵,很快SP2正式版就快出来了 听说到6月份出,呵呵 推荐算号激活和VOL版本的朋友更新,注意:破解激活的Xp将要求激活,无法登陆 『图文』Windows XP SP2 RC1 简体中文版初体验(转自ssite.org) 环境 host os: windows server 2003 enterprise guest os: vmware workstation 4.5.1.7568 vm conf: CPU: P4 2.2 RAM: 256M HDD: 4G(单分区) NIC: NAT .............................................................................. Windows XP SP2 RC2 Build 2149 简体版[crsky deadlink] http://file.mydrivers.com/others/XP_SP2_RC22149CHS.rar http://file2.mydrivers.com/others/XP_SP2_RC22149CHS.rar 软件大小： 293380K 软件更新： 2004-6-16 17:11:00 软件介绍： 微软官方已经公布了Windows XP RC2的下载地址，有需要的朋友赶快行动吧。这是简体中文版，安装请执行i386\update目录下的update.exe文件。 .............................................................................
某个WinBeta IRC文件列表记录
<Winbeta-XDCC-252> Kiri Online >> Sends: 0/1, Queues: 0/3 <Winbeta-XDCC-252> Bandwidth >> Current: 0KB/s, Record: 1258KB/s <Winbeta-XDCC-252> [#1] ��4Winxp SP2 RC2 2162�� (271.38MB, 11 Gets) <Winbeta-XDCC-252> [#2] ��1Longhorn Build 4074�� (724.9MB, 4 Gets) <Winbeta-XDCC-252> [#3] ��2Acronis Partition Expert 9 Build 485�� (37.95MB, 6 Gets) <Winbeta-XDCC-252> [#4] ��6Win XP Pro AMD 64 Build 1184�� (457.6MB, 2 Gets) <Winbeta-XDCC-252> [#5] ��4Windows Installer 3.0 RC2�� (6.93MB, 4 Gets) <Winbeta-XDCC-252> [#6] ��3Microsoft Command Shell Preview V2�� (24.04MB, 2 Gets) <Winbeta-XDCC-252> To request a file, type /msg Winbeta-XDCC-252 xdcc send #x <Winbeta-XDCC-252> For pack info, type /msg Winbeta-XDCC-252 xdcc info #x <Winbeta-XDCC-252> Total transferred: 13136.81MB in 29 files <Winbeta-XDCC-252> ** ***** Read The NFO'S w/Notepad ***** Brought to you by Carvensno and Winbeta ** <Winbeta-XDCC-302> #15 1x [271.38M] ��4Microsoft Windows XP SP2 Build 2162�� <Winbeta-XDCC-302> ** Brought to you by Winbeta and dm2k4. ** <Winbeta-XDCC-302> Total Transferred: 9036.74MB <eugrus> xdcc list <Winbeta-XDCC-302> ** 15 packs ** 0 of 1 slots open, Record: 22KB/s <Winbeta-XDCC-302> ** Bandwidth Usage ** Current: 16KB/s, Record: 22KB/s <Winbeta-XDCC-302> ** To request a file type: "/msg Winbeta-XDCC-302 xdcc send #x" ** <Winbeta-XDCC-302> #1 0x [18.36M] ��3Microsoft .NET Framework v1.1 SP1 and v1.0 SP3 Beta 2�� <Winbeta-XDCC-302> #2 1x [22.14M] ��3Microsoft .NET Framework v2.0.3113.31�� <Winbeta-XDCC-302> #3 1x [24.04M] ��3Microsoft Command Shell Preview v2.0�� <Winbeta-XDCC-302> #4 0x [94.44M] ��3Microsoft Host Integration Server 2004 Release Candidate�� <Winbeta-XDCC-302> #5 0x [99M] ��3Microsoft Office 2003 SP1 Beta Build 6353�� <Winbeta-XDCC-302> #6 0x [103.73M] ��3Microsoft Operations Manager 2005 Beta 3 Bundle�� <Winbeta-XDCC-302> #7 0x [356.24M] ��3Microsoft SQL Server Yukon PDC Build�� <Winbeta-XDCC-302> #8 0x [3697.12M] ��4Microsoft Visual Studio .NET 2005 Beta 1 DVD�� <Winbeta-XDCC-302> #9 0x [6.93M] ��3Microsoft Windows Installer v3.0 RC2�� <Winbeta-XDCC-302> #10 1x [724.9M] ��7Microsoft Windows Longhorn WinHEC Build 4074�� <Winbeta-XDCC-302> #11 0x [4013.15M] ��7Microsoft Windows Longhorn WinHEC Build 4074 AIO DVD�� <Winbeta-XDCC-302> #12 0x [342.89M] ��3Microsoft Windows Longhorn WinHEC Build 4074 LDK�� <Winbeta-XDCC-302> #13 1x [371.42M] ��4Microsoft Windows Server 2003 SP1 Build 1218�� <Winbeta-XDCC-302> #14 3x [468.42M] ��4Microsoft Windows XP Professional AMD64 Build 1218�� <Winbeta-XDCC-302> #15 1x [271.38M] ��4Microsoft Windows XP SP2 Build 2162�� <Winbeta-XDCC-302> ** Brought to you by Winbeta and dm2k4. ** <Winbeta-XDCC-302> Total Transferred: 9041.18MB <WinBeta-XDCC-22245> Kiri Online >> Sends: 1/1, Queues: 0/5 <WinBeta-XDCC-22245> Bandwidth >> Current: 20KB/s, Record: 22KB/s, Cap: 20KB/s <WinBeta-XDCC-22245> [#1] ��2Windows XP Pro AMD64 ��4Build: 1184�� (457.61MB, 0 Gets) <WinBeta-XDCC-22245> [#2] ��3Windows Longhorn WinHEC ��4Build:4074�� (724.9MB, 0 Gets) <WinBeta-XDCC-22245> [#3] ��6Virutal Server 2005 ��4Build: 1.1.445�� (17.26MB, 0 Gets) <WinBeta-XDCC-22245> [#4] ��7Windows Installer v3.0 ��4Build: RC2�� (6.93MB, 0 Gets) <WinBeta-XDCC-22245> [#5] ��8Windows XP SP2 ��4Build 2162�� (271.38MB, 0 Gets) <WinBeta-XDCC-22245> To request a file, type /msg WinBeta-XDCC-22245 xdcc send #x <WinBeta-XDCC-22245> For pack info, type /msg WinBeta-XDCC-22245 xdcc info #x <WinBeta-XDCC-22245> Total transferred: 70.69MB in 0 files <WinBeta-XDCC-22245> ** ]::[Always read the .nfo]::[Brought to you by WinBeta and $injed]::[ ** <WinBeta-XDCC-110> Kiri Online >> Sends: 0/1, Queues: 0/2, Min Speed: 1KB/s <WinBeta-XDCC-110> Bandwidth >> Current: 0KB/s, Record: 56KB/s <WinBeta-XDCC-110> [#1] ��2Acronis.Partition.Expert.9.build.485-WinBeta�� (37.95MB, 2 Gets) <WinBeta-XDCC-110> [#2] ��4Microsoft.Command.Shell.Preview.v2.0-WinBeta�� (24.04MB, 1 Gets) <WinBeta-XDCC-110> [#3] ��2Microsoft.ISA.Server.2004.RC1.WInbeta�� (46.47MB, 0 Gets) <WinBeta-XDCC-110> [#4] ��2Windows Code Name "Longhorn" - #4074�� (724.9MB, 0 Gets) <WinBeta-XDCC-110> [#5] ��5Office 2003 SP1 #6353�� (99MB, 0 Gets) <WinBeta-XDCC-110> [#6] ��2Host Integration Server 2004 RC�� (94.44MB, 0 Gets) <WinBeta-XDCC-110> [#7] ��4"Royale" - new official theme for XP/2003�� (0.17MB, 1 Gets) <WinBeta-XDCC-110> [#8] ��1LH #4074 LDK�� (342.89MB, 0 Gets) <WinBeta-XDCC-110> [#9] ��3Windows XP Service Pack 2, Build 2162 ENG Full�� (271.38MB, 0 Gets) <WinBeta-XDCC-110> [#10] ��2Windows Installer 3.0 RC2�� (6.93MB, 0 Gets) <WinBeta-XDCC-110> [#11] ��2Windows Server 2003 SP1 #1218�� (371.42MB, 1 Gets) <WinBeta-XDCC-110> [#12] ��4Windows Server 2003 Enterprise Edition, AMD64 build 1218�� (505.78MB, 0 Gets) <WinBeta-XDCC-110> [#13] ��6Windows XP Pro, AMD64 build 1218�� (468.42MB, 4 Gets) <WinBeta-XDCC-110> [#14] ��4Windows Server 2003 Standard Edition, AMD64 build 1218�� (502.92MB, 0 Gets) <WinBeta-XDCC-110> To request a file, type /msg WinBeta-XDCC-110 xdcc send #x <WinBeta-XDCC-110> For pack info, type /msg WinBeta-XDCC-110 xdcc info #x <WinBeta-XDCC-110> Total transferred: 3568.15MB in 9 files <WinBeta-XDCC-110> ** always here from the beginning.. ** <WinBeta-XDCC-256> Kiri Online >> Sends: 0/1, Queues: 0/10, Min Speed: 10KB/s <WinBeta-XDCC-256> Bandwidth >> Current: 0KB/s, Record: 90KB/s <WinBeta-XDCC-256> [#1] Acronis.Partition.Expert.9.build.485-WinBeta.rar (37.95MB, N/A Gets) <WinBeta-XDCC-256> [#2] Microsoft_Virtual_Server_2005_Build_1.1.455.rar (17.26MB, N/A Gets) <WinBeta-XDCC-256> [#3] WB-LH4074.rar (724.9MB, N/A Gets) <WinBeta-XDCC-256> [#4] wb-p-wxpsp2b2149.rar (266.71MB, N/A Gets) <WinBeta-XDCC-256> [#5] wb-royale-mce.rar (0.17MB, N/A Gets) <WinBeta-XDCC-256> [#6] Windows.XP.SP2.Build.2162-WinBeta.rar (271.38MB, N/A Gets) <WinBeta-XDCC-256> [#7] Windows.XPSP2.Build.2144.full-WinBeta.rar (274.67MB, N/A Gets) <WinBeta-XDCC-256> To request a file, type /msg WinBeta-XDCC-256 xdcc send #x <WinBeta-XDCC-256> For pack info, type /msg WinBeta-XDCC-256 xdcc info #x <WinBeta-XDCC-256> Total transferred: 776.41MB in 0 files <WinBeta-XDCC-256> ** Brought to you by WinBeta **
文件文本
OS2VSCHG.TXT
WARP VS CHICAGO: A Decision Maker's Guide to 32-bit Operating
System Technology
IBM Personal Software Marketing
October 1994
EXECUTIVE SUMMARY
=================
This document is designed to provide the corporate decision maker
with benefits of OS/2 and important information about critical
weaknesses in Microsoft's forthcoming Chicago operating system.
At the heart of the discussion are key architectural,
operational, and strategic flaws in the Chicago OS design and
strategy - flaws that Microsoft has either downplayed or ignored
in its efforts to market Chicago as the "next generation" Windows
desktop platform.
For example, you'll learn:
Why OS/2's ability to isolate individual 16-bit Windows
applications into their own separate VDMs provides a level of
inter-application protection that is unavailable under Windows
3.1 or Chicago.
How this same isolation also allows OS/2 to preemptively multitask
existing 16-bit Windows applications, with no impact on native
application performance
Why having a comprehensive System Object Model (SOM) is important,
and how OS/2's SOM implementation acts as the "glue" to the
WorkPlace Shell interface.
Ways in which OS/2's Virtual DOS Machine implementation is more
flexible than Chicago's.
Major topics include:
Architectural flaws that compromise Chicago's stability when
running 16-bit Windows applications.
How these same flaws also limit Chicago's multitasking
capabilities with a mixture of application types.
Why the lack of a System Object Model makes the Chicago interface
"fragile."
Ways in which Chicago's DOS heritage render the product inflexible
when dealing with 16-bit DOS device drivers.
At the end of each section, a direct comparison is made between
the Chicago implementation of a particular subsystem or
feature/function, and that of the leader in 32-bit desktop
operating systems, IBM's Operating System/2.
The material is based on an in-depth analysis of Microsoft's
public statements regarding Chicago's design characteristics and
various presentations given at trade shows by industry
consultants.
OS/2 - THE RIGHT SOLUTION
Choosing the right operating system. In many ways it's the most
important personal computer technology decision you'll make in
this century. Choose wisely and you'll reap the benefits for
years. Choose poorly and you may find yourself in a quagmire of
under-performing software and inadequate computing power.
So just what constitutes a wise choice in today's confusing PC
marketplace? Simple: the product that does the best job of
preserving your existing investments while opening the door to
the future. In a nutshell, the wise choice is Operating
System/2.
OS/2 - THE WORLD'S MOST POPULAR 32-BIT OPERATING SYSTEM FOR IBM
AND IBM COMPATIBLE PC's
Why OS/2? Because it represents the most logical upgrade path
for today's PC users. OS/2 preserves your investment in 16-bit
DOS and Windows applications while providing access to a new
world of 32-bit, object-oriented technology.
Upgrading to OS/2 is a win-win proposition. Just ask any of the
more than five-million OS/2 users - over 8 times as many users as
Microsoft's current 32-bit offering, Windows NT. These are
people just like you who have outgrown their existing DOS or
Windows environments and who are looking for more - more power,
more functionality, more stability.
With OS/2 they've found a powerful mix of backward-compatibility,
32-bit processing power, and ease of use, along with the kind of
rock-solid reliability that only a mature, established operating
system platform can deliver. With the release of V3, OS/2 is
entering in its 3rd generation, and the product's reputation for
reliability and price/performance is unmatched in the PC
industry.
BUT WHAT ABOUT CHICAGO?
This is the question that perplexes both corporate decision
makers and end users alike. With all of the media hype
surrounding this "next generation" of Microsoft Windows, many
customers feel paralyzed when making operating system purchasing
decisions. The fear of "missing-out" on Chicago is overwhelming
for some.
But as experience with the initial beta release of Chicago has
demonstrated, Microsoft's "next generation" of Windows is far
less compelling than they would lead you to believe. In fact,
the core of Windows 4.0 is probably running on a PC near you:
it's called Microsoft Windows 3.1.
ARCHITECTURE
============
CHICAGO - SAME CODE, DIFFERENT PACKAGING
"How can that be? It looks so different!"
Looks can be deceiving. While Chicago indeed sports a radically
different user interface (more on that later), as you peel-away
the layers of GUI and packaging you'll discover a product that
looks remarkably like Windows 3.1. In fact, Chicago retains so
much of its original DOS/Windows heritage that it retains the
latter's most notorious operational characteristic: instability.
For example, under Windows 3.1 all applications, as well as the
operating system code itself, share a single memory address
space. While such a memory management model breeds performance,
it also means that an error in any single application can
potentially crash the entire operating system.
This crashing phenomena is often referred to as a General
Protection Fault or "GPF," and has been the bane of Windows users
since version 3.0. It is because of this inherent architectural
weakness that Windows 3.1 has gained a well-deserved reputation
of being an unstable, unreliable operating environment.
Under Chicago, this same single address space model (referred to
as the "System Virtual Machine") is retained, along with the
inherent weakness of leaving key portions of the operating system
code exposed to potentially buggy applications. Thus the same
application failures that crashed Windows 3.1 can potentially
bring down the entire Chicago operating system.
To their credit Microsoft has made great strides in "cleaning-up"
many of the bugs in the original Windows 3.1 code while
preparing it for inclusion with Chicago. However they cannot
avoid the inherent architectural flaws that the Windows 3.1
single System VM model introduces. There will always remain the
possibility of an errant application causing a disastrous system
crash.
OS/2 - SAME CODE, BETTER IMPLEMENTATION
OS/2 eliminates the Single System VM stability problem by letting
you run Windows applications in their own separate sessions, or
"VDMs" (Virtual DOS Machines). Thus if an application fails
under OS/2, the effect of the failure is limited to the
individual session. Other applications, as well as the operating
system itself, remain unaffected.
And by retaining much of the original Windows 3.1 code base,
OS/2's environment remains highly backward compatible with
Windows 3.1 applications and device drivers.
MULTITASKING
============
CHICAGO - A "SEMI-PREEMPTIVE" TASK SWITCHER?
One of Microsoft's biggest selling points for Chicago has been
the promise of a new breed of 32-bit Windows applications. These
applications are to be preemptively multitasked by the Chicago
operating system, and will have access to advanced performance
enhancing techniques like multi- threading.
Let's define the difference between preemptive and cooperative
multitasking. Preemption is an involuntary loss of control which
the application must handle. Cooperative multitasking is where
the application is given control and it is the application's
responsibility to give up control so that other applications may
execute.
The move to a preemptive multitasking model represents a a
significant departure from Windows 3.1. Under that environment
applications must "cooperate" in order for multitasking to occur.
Each program "yields" to the operating system so that it can
switch control of the PC's CPU to a different application (this
is often referred to as "cooperative multitasking" or
"task-switching").
It is a well know fact that the Windows "cooperative
multitasking" model is inefficient. It also forces programmers to
code their applications in a way that adds complexity and hinders
performance. So it comes as no surprise that Microsoft's promise
of preemptive multitasking in Chicago has been heralded as one of
the new platform's most important features.
But the truth is that Microsoft isn't telling the whole story
when it comes to Chicago's multitasking architecture. In
reality, unless you work exclusively with 32-bit "Win32"
applications, you won't reap the benefits of true preemptive
multitasking.
Why? Because of Chicago's heavy reliance on 16-bit, Windows
3.1-era code. Under Chicago, both 16-bit and 32-bit applications
rely on 16-bit code structures that reside within the System VM -
code that has been brought over from Windows 3.1.
While the "bitness" of the code itself isn't significant, the
environment from which it hails is. Windows 3.1 was written as a
cooperative, not preemptive, multitasking environment. When you
introduce portions of its code into a preemptive setting, where
more than one task may be vying for its services at any given
time, the code breaks.
To safeguard against this sort of "code breakdown," Microsoft has
serialized access to key portions of the Chicago infrastructure -
most notably the USER (window management) and GDI (graphics
device interface) subsystems. In technical terms, this is
referred to as a "non-reentrant" design, meaning that only one
application may execute within these modules at any given time.
While such an approach works with Win32 applications - which can
be preempted at any point during their execution - it breaks down
once a 16-bit Windows (Win16) application begins to execute. As
it stands, currently shipping Win16 applications cannot be
reliably preempted during execution. Attempting to do so while
such an application is calling on a non-reentrant, 16-bit code
module can cause the entire operating system to crash.
To avoid this latter scenario, and thus retain some semblance of
multitasking, Microsoft has implemented a special locking
mechanism. Dubbed "Win16LOCK," this mechanism denies access to
the older code when a 16-bit application has called on its
services. Thus only the currently running Win16 application has
access to the 16-bit code - all other applications, including
Win32 applications, are "blocked" from executing until the 16-bit
application has finished and the environment has been made safe
for the next task.
In practice, the performance hit associated with this locking
phenomena is minimal when running 32-bit applications
exclusively. However, when you introduce a mixture of 16 and
32-bit applications - the most likely scenario given the
projected lack of available Win32 products - Win16LOCK becomes a
major problem.
Most 16-bit Windows applications are notorious for failing to
yield properly under Windows 3.1, and until they do so under
Chicago, all other applications will be blocked from accessing
USER and/or GDI (in reality, only 50% of GDI calls are affected -
but these are the most common functions so the net result is the
same).
Taken as a whole, these two compromises - the serialization of
subsystem access and Win16LOCK - create what would best be
described as a "semi-preemptive" multitasking environment. And
while the resulting "hourglass" is expected under a cooperatively
multitasked environment, it seems out of place in a "next
generation" Windows that supposedly "preemptively multitasks"
native Win32 applications.
OS/2 - TRUE PREEMPTION FOR BETTER PERFORMANCE
OS/2 has featured true preemptive multitasking of native
applications since day one. Regardless of the mixture of
application types, OS/2 can continue to smoothly multitask dozens
of concurrent programs, and its reentrant subsystems allow it to
service multiple concurrent requests without the overhead of a
"Win16LOCK" implementation.
And thanks to its ability to run them in separate VDMs, OS/2 can
also preemptively multitask existing 16-bit Windows applications
which Chicago can not. Thus you can have DOS, Windows, and OS/2
applications running concurrently, side-by-side, without any
performance penalties and all preemptively multitasked. This is
a feature that Chicago will be unable to match without underlying
architecture changes, and a welcome addition to any power-user's
arsenal.
INTERFACE
=========
CHICAGO - BEAUTY THAT'S ONLY SKIN-DEEP
Another major feature of Chicago, and one that has drawn
considerable attention from the industry press, is its new user
interface. Terms like "object-oriented" and "desktop metaphor"
are often used to describe this radically different Windows look.
But as with most of Chicago's underpinnings, the actual
foundation underneath the product's user interface is nothing
more than an extension to what already existed in Windows 3.1.
Unlike a true object-oriented environment - where links between
individual objects are "live" and updated automatically - the
Chicago GUI is static. "Objects" on the Chicago desktop are
merely pointers to files on the disk. "Properties" for these
objects are stored in .INI files (for Windows applications) or
.PIF files (for DOS applications), and links between them (called
"shortcuts" under Chicago) are equally static.
For example, if you create a shortcut to an executable file and
place it on the Chicago desktop, then rename the original
executable, the shortcut will essentially be severed. To
re-establish it you'll have to re-create the shortcut from
scratch.
In a true object-oriented environment, all shortcut-like links to
the executable would have been updated automatically by the
underlying object management model. Chicago has no such
underpinnings, so links are easily broken by novice users who are
unfamiliar with the crudeness of the Chicago interface.
Going hand-in-hand with Chicago's shortcut mechanism is the
product's support for long file and directory names on FAT
volumes. Microsoft is emphasizing Chicago's ability to
automatically convert long file/directory names into 8.3
character abbreviations for compatibility with existing DOS and
Windows applications. What they seem to be ignoring, however, is
the fact that promoting the use of long names can be disastrous
when there is no underlying object model.
Take, for example, the novice user who, upon discovering long
filenames, decides to "reorganize" their hard disk. They
gleefully rename directories at will, unaware that they are
severing shortcut after shortcut in the process. Suddenly none
of their applications work, and I/S is called in to undo the
damage (which in some cases may mean reinstalling both operating
system and applications).
The Chicago desktop itself is not an OLE 2.0 object. This
statement in itself has no ramifications until you start
understanding what type of integration is lost due to this lack
of object technology. This deficiency in the product, means that
an application is not well integrated with the desktop and does
not inherit any of the advantages like Drag 'n' Drop support.
Heralded by Microsoft as one of Chicago's key selling points, the
new Windows interface may in the end prove to be one of its
biggest flaws. Without an underlying system object model to tie
everything together, this new "shell" may prove to be an I/S
support nightmare.
OS/2 - TRUE OBJECT-ORIENTATION
OS/2's WorkPlace Shell is a true object-oriented interface. The
underlying System Object Model (SOM) provides complete
object-tracking so simple operations like dragging a directory to
another directory won't invalidate links and other interface
structures. Thus it's easier on both novices and IS support
staff alike.
SOM also allows applications to fully manipulate the WorkPlace
Shell interface. A good example is cc:Mail for OS/2, which uses
SOM to seamlessly integrate its in/outbox interfaces with the
WorkPlace Shell desktop. This level of integration isn't
possible under Chicago since its shell is itself not an object.
APPLICATION SUPPORT
===================
CHICAGO - STILL DOS AFTER ALL THESE YEARS
"Chicago eliminates the need for DOS. It is a true operating
system..."
This is one of the more colorful myths surrounding Microsoft's
Chicago operating environment. Microsoft claims that Chicago
eliminates the need for DOS - that DOS and Windows are now
completely integrated and that all the old restrictions that DOS
brought to the table have been eliminated.
While it is true that you will no longer have to purchase a
separate DOS product in order to install and use Chicago, this in
no way constitutes the eradication of DOS as a part of the
Windows operating system equation. DOS is still there, lurking
in the shadows. It's just been cleverly disguised by a different
Windows GUI. And though much of its functionality - including
file system access - has been replaced by 32-bit Chicago VxDs
(Virtual Device Drivers), there are still ways in which DOS can
hinder the Windows environment.
Take real-mode device drivers, for example. Under DOS/Windows
3.1 you were forced to load all DOS device drivers at DOS
boot-time via the CONFIG.SYS file. These drivers would then
occupy all DOS sessions under Windows' 386 Enhanced Mode,
impacting their available conventional memory and limiting the
overall configurability of the Windows VDM architecture.
Chicago suffers from this very same limitation. Any real-mode
DOS device drivers that you wish to access from within Chicago
must be loaded via CONFIG.SYS at boot-time. Thus, if you want
access to a particular resource, and this resource requires a DOS
device driver, you'll be forced to pay a penalty in terms of lost
conventional memory and potential compatibility problems across
all Chicago VDMs.
And what about troublesome applications like games? Chicago
features a special DOS session - the "Single MS-DOS Application
Mode" - that allows such applications to execute unencumbered by
the confines of a traditional Virtual DOS Machine (virtual I/O,
video memory, etc.). What Microsoft doesn't publicize, however,
is the fact that, in order to invoke this mode, you must
essentially shut-down Chicago. All running applications close,
and the Chicago GUI itself is paged to disk. This entire process
can take up to a minute depending on the speed of the hardware in
use and the number of open applications - quite a disruption,
especially when you're trying to finish that last minute memo or
download a large file from a host system.
OS/2 - A BETTER DOS THAN DOS (OR CHICAGO)
OS/2 really does eliminate the need for DOS. It's VDMs are
completely configurable, allowing you to create individual
CONFIG.SYS and AUTOEXEC.BAT files for each DOS session. This is
an important option in those situations where a single device
driver or TSR configuration for all VDMs would be inadequate.
OS/2's VDMs are also highly backward-compatible and can also be
configured to allow direct hardware access for applications that
require it. And if an application truly refuses to run under
OS/2 you can use the "dual-boot" option to run real DOS in about
the same amount of time it takes you to invoke Chicago's "Single
MS-DOS Application Mode."
INDEPENDENT SOFTWARE VENDOR COMMITMENTS
=======================================
CHICAGO: AN ISV HEADACHE
One area where Microsoft continues to be uncertain is on the
subject of API standards. Independent Software Vendors (ISVs)
have been fighting an uphill battle in their efforts to pin-down
Microsoft's overall API strategy. This is especially true of the
native Chicago API, Win32c, which is itself a subset of the full
Win32 API published nearly two years ago and implemented on
Windows NT.
Further exacerbating the situation is Microsoft's continual
updating of the Win32c specification. New APIs emerge almost
monthly, many of which extend Win32 in ways that tie applications
to the Chicago platform. This has aggravated ISVs who wish to
write cross-platform applications for Windows, Windows NT, and
Chicago. The only way these ISV's can write cross-platform
applications, because of the different APIs support, is to poll
the Kernel, determine which API is available and write dual or
triple path code. With the APIs still in a state of flux there is
no guarantee that the multiple path code will work.
What this means to the 32-bit operating system customer is a
potential delay in the release of Chicago-compatible Win32
applications. Given the architectural limitations of Chicago's
Win16 application support - especially when multitasking and
stability are major considerations - lack of Win32 applications
could represent a serious obstacle to the platform's widespread
adoption. Chicago needs Win32 applications before it even begins
to make sense as a replacement for Windows 3.1. But given the
confusion and frustration in the ISV community it may be some
time before we see a substantial selection of Win32 titles.
OS/2 - A CONSISTENT MESSAGE
In contrast to Microsoft's "API du jour" strategy, IBM has stood
firm on its promises to support open standards and honor ISV
commitments. There is one 32-bit OS/2 Presentation Manager API
for both client and server systems. Applications written to that
API will work across OS/2 versions running on Intel-based PC's,
and will be easily portable to more advanced implementations in
the future (including OS/2 for PowerPC).
OS/2 currently boasts over 2000 native applications, all of which
tap into the superior multitasking and performance of the world's
most popular 32-bit operating system.
SUMMARY
=======
OS/2: THE RIGHT ANSWER
As you can see, Microsoft's Chicago operating system is long on
hype and somewhat short on technology. But if you've followed
their product offerings over the past few years, this revelation
should really come as no surprise. Microsoft has a track record
of delivering "cosmetically advanced" operating systems while
ignoring the more important issues like robustness, capacity, and
true object-orientation.
In contrast, IBM has a very different track record, one that
speaks of commitment to open standards and listening to customer
needs. This is the same company that has been developing cutting
edge OS technology for mainframe and minicomputer systems since
the dawn of the information age. With OS/2, IBM has laid the
foundation for a truly robust, high-capacity computing
environment that preserves your existing investments while
opening the door to the future.
You can see the difference in areas like the OS/2 user interface.
The WorkPlace Shell, in conjunction with the System Object Model
(SOM), provide a truly object-oriented computing environment, one
that thinks for you and doesn't break-down when you try to tap
into its power. Likewise, OS/2's multitasking represents a
no-compromises approach to bringing this powerful capability to
the masses. From native OS/2 applications to its robust Win-OS2
VDMs, it is an operating system that can juggle your most complex
tasks with ease.
So in the end, the wise choice is obvious: OS/2 has the backward
compatibility you want, the stability and reliability you need,
and the kind of rock-solid commitment to excellence you've come
to expect from the world's number one software company, IBM.
Chicago looks more and more like a warmed-over version of
yesterday's technology, not the "next generation Windows"
platform that Microsoft is advertising it to be.
So what about Chicago? Good question! With one foot still
buried in the DOS/Windows grave, Chicago is yesterday's
technology dressed-up to look like tomorrow's 32-bit OS. Why
wait for an impostor? OS/2 is here today, and represents the
real future in personal computer operating systems.
APPENDIX A: FEATURES CHARTS FOR OS/2 AND CHICAGO
================================================
The following charts provide a summary of OS/2 and Chicago
features, including multitasking characteristics, application
environments, and bundled productivity tools.
OS/2 VS CHICAGO ON ARCHITECTURE
WARP LAN
FEATURE WARP CLIENT CHICAGO
32-bit Window Management Yes Yes No (1)
32-bit Graphics Subsystem Yes Yes No (2)
32-bit Printing Subsystem Yes Yes Yes
32-bit Multimedia Subsystem Yes Yes Yes
32-bit Kernel Yes Yes Yes
Demand Paged Virtual Memory Yes Yes Yes
HPFS Support Yes Yes No
Non-locking Input Queue (3) Yes Yes No
(Applications can keep running)
(1) USER is 16-bit, non-reentrant code
(2) 50% of GDI calls are serviced by 16-bit, non-reentrant code
(3) WARP, new version of OS/2, has an engine that will unlock
the input queue if it is locked
OS/2 VS. CHICAGO ON APPLICATION ENVIRONMENTS
WARP LAN
FEATURE WARP CLIENT CHICAGO
16-bit OS/2 PM Applications Yes Yes No
32-bit OS/2 PM Applications Yes Yes No
Win32s Applications (Ver 1.0 & 1.1) Yes Yes Yes
Preemptive Multitasking (4) Yes Yes No
Win16 Application Support Yes Yes Yes
Win16 Device Driver Support Yes Yes Some (5)
Number of 32-bit Applications 2000+ 2000+ 0 (6)
Available
(4) See chart on multitasking comparison
(5) Windows 3.x communications drivers need to be re-written
(6) Native Chicago applications
OS/2 VS. CHICAGO ON MULTITASKING CHARACTERISTICS
WARP LAN
FEATURE WARP CLIENT CHICAGO
Preemptive of 32-bit Applications Yes Yes Yes
Preemptive of DOS Applications Yes Yes Yes
Preemptive of Win16 Applications Yes Yes No
Preemptive of mixed 16/32-bit Yes Yes No (7)
Applications
Multiple, Protected Win16 VDMs Yes Yes No (8)
Crash Protection Yes Yes No (9)
Preemptive Multi-threading Yes Yes Yes
(7) Win16LOCK prohibits access to USER and portions of GDI
when a Win16 application is executing
(8) All 16-bit applications share a single address space - the
System Virtual Machine (VM)
(9) Key operating system code structures (USER and GDI) share
the System VM address space with 16-bit applications
OS/2 VS. CHICAGO ON USER INTERFACE
WARP LAN
FEATURE WARP CLIENT CHICAGO
Folder Work Areas Yes Yes No
Integration with operating SOM Yes Yes No (10)
Launch Pad Yes Yes Yes
Drag & Drop Deletion Yes Yes No
Drag & Drop Faxing Yes Yes Yes
Drag & Drop Access Paths (change Yes Yes No
execution paths it will still work)
Object Type Templates Yes Yes No
Parent Folder Closing Options Yes Yes No
(10) Chicago shell components are not OLE 2.01 objects"
OS/2 VS. CHICAGO ON MULTIMEDIA
WARP LAN
FEATURE WARP CLIENT CHICAGO
Image Viewer Yes Yes No
Photo CD Support Yes Yes No
Autodesk Animation Yes Yes No
Play any Audio File from Internet Yes Yes No
Audio/Video Synch Manager Yes Yes No
MPEG Support Yes Yes Yes
32-bit Audio/Video Playback Yes Yes Yes
OS/2 VS. CHICAGO ON BUNDLED APPLICATIONS
WARP LAN
FEATURE WARP CLIENT CHICAGO
Internet Access Tools Yes Yes No
FTP Yes Yes No
Telnet Yes Yes No
Gopher Yes Yes No
Newsreader Yes Yes No
WEB Explorer Yes Yes No
CompuServe Front-End Yes Yes No
Word Processor Yes Yes No (11)
Spreadsheet Yes Yes No
Database Yes Yes No
Charting Yes Yes No
Report Writer Yes Yes No
Electronic Mail Yes Yes Yes
Image Viewer Yes Yes No
FAX Yes Yes Yes
Phonebook Yes Yes No
Personal Information Mgr Yes Yes No
Sys Info Yes Yes No
VideoIn Yes Yes No
Video Conferencing Yes Yes No
(11) Chicago comes with a simple text editor, not a word processor
DISCLAIMER
==========
The information contained in this document represents the current view
of IBM Corporation on the issues discussed at the date of publication.
Because IBM must respond to changing market conditions, it should not
be interpreted to be a commitment on the part of IBM, and IBM cannot
guarantee the accuracy of any information presented after the date of
publication.
This document is for informational purposes only. IBM makes NO
WARRANTIES, EXPRESSED OR IMPLIED, IN THIS SUMMARY.
1994 IBM Corporation. All Rights Reserved. Printed in the United
States of America.
OS/2 is a registered trademark of International Business Machines
Corporation.
Microsoft is a registered trademark and Windows is a trademark of
Microsoft, Inc.
NetWare is a registered trademark of Novell, Inc.
�
- OS2BETA.ZIP
OS2RPRTS.TXT [COMMENTS FROM OS2 BETA TESTERS]
Customer Experiences
OS/2 Version 2.0
"An odd thing happened when I loaded OS/2 2.0 on my PS/2 at work. The rains
stopped. Clouds parted. The sun came out. Birds began to chirp. And yes,
I even believe I heard the sound of small, happy children playing in a park.
I was converted....... I am sold. I want OS/2..... I'm nuts about OS /2 2.0.
It's everything that IBM has promised. I find it easy, intelligent, and yes,
even fun.... Here at work, myself and the other analysts are continually
amazed at what OS/2 2.0 can do. I've been recommending it to almost every
new department I service. I love telling people what it does.... Thanks for
letting me be a part of the Early Experience." PUGET SOUND BANK IN TACOMA,
WASHINGTON - ROBERT A. PIRNIE
"I've long looked for a way to integrate my workaday computing. OS/2 is the
answer...... My day begins calling various on-line services via modem,
opening numerous documents on my word processor, and starting a DOS-based
database I use for my students grades. Before OS/2 this took quite a bit of
time. But now I have these programs set to open on startup, and my overall
productivity has increased three-fold. I can answer a student's grade
queries as I confidently print a lecture I must give, compile some utility I
wrote in C++, download from the EEP BBS, all the while backing up the
directory containing my book to a floppy disk---try that with DOS or
Windows!...... I'm not a Big Iron guy, just a dedicated theology teacher and
scholar, but OS/2 is a God-send for my productivity and for the stability of
my work environment--which is precious to me, if to no one else. OS/2 is man
made, I know, and my jaded fellow theologians may find this heresy, but day
by day OS/2 seems to me to be a flat-out miracle." SAINT JOSEPHS COLLEGE IN
RENSSELAR, INDIANA - MARK JOHNSON, ASSISTANT PROFESSOR, DEPARTMENT OF
PHILOSOPHY & RELIGION
"My job requires that I continually juggle my time between a variety of
ongoing tasks. Furthermore, I must deal with frequent interruptions to
service customer telephone calls. In the past, my PC was a less than
adequate aid in helping me accomplish these work tasks in an efficient
manner...... OS/2 2.0 has finally elevated my PC from the level of aid to
that of a true tool in my work environment. Using the WPS, I have created a
PC environment that is the ideal best of all worlds. The various programs,
system connections (multiple terminal sessions to various systems, as well as
PC servers), and other productivity tools that I need to execute on my PC,
can now be executed (automatically) as soon as I turn on my PC in the
morning. I finally am able to have hot connections to all of these
facilities simultaneously. No longer do I suffer through the syndrome of
having to terminate one facility, and initiate a new one, due to the normal
interruptions of my daily environment. I simply hide and surface the old and
new activities, respectively, all with a few simple mouse clicks on my OS/2
WPS desktop. And when I return to a precious activity, it's just as I left
it..... We are a small, service oriented company. Our small size demands
that we achieve the maximum productivity among the few employees that we
have. The desktop environment available with OS/2 2.0 will finally allow us
to obtain the productivity multiplier promises, that have so long been used
as a selling point for PCs on every desktop..... It truly is a superior
product." ALLINSON-ROSS IN GOLDEN, COLORADO - MARVIN NIPPER, PRESIDENT
"To me, only three major breakthroughs in technology equal this product;
those being the invention of the light bulb, the invention of the wheel, and
the discovery of fire. I am truly impressed! Furthermore I find this system
so convenient and uncomplicated to use that most of my time is spent fighting
my SEVEN-YEAR-OLD son for control of my computer. I feel that IBM has once
again proven that it is not only the front runner of microcomputer
technology, but also the trail blazer of times to come!" SECURITY PACIFIC
AUTOMATION COMPANY, INC. IN SEATTLE, WA - DONALD K. CHAMPINE, TECHNICAL
CONSULTANT, SPAC-NW TECHNICAL SUPPORT
"OS/2 2.0 provides the best of all worlds....Additionally, IBM has scored a
major hit in the new powerful GUI Workplace Shell..... Not only is the base
operating system stable, but the LAN Program, Host Communications, and
Database are all rock solid. OS/2 2.0 provides stability for both the
standalone user as well as a user in a complex networked environment....
OS/2 2.0 performance is better than any DOS based multitasking system I have
used..... Power users need the features of OS/2 2.0 but so do new
users...... Some words for OS/2 2.0 -- Great, Excellent, Magnificent,
Superb, Extraordinary, Impressive, Noteworthy, Outstanding, Smashing,
Wonderful, Fabulous, Fantastic, Fine, Good, Marvelous, Super, Terrific,
Tremendous, Stupendous, Amazing, Premier, Glorious, Splendid, Distinguished,
and Number one.....you've given us what I've wanted for years.... Thank you
IBM." MISSOURI HIGHWAY & TRANSPORTATION DEPARTMENT - BOB HITT, PROGRAMMER
ANALYST
"OS/2 2.0 is for both the power user and the average user. In fact, I
suspect we will see a new breed of power users. These people will be able to
harness the power of their machines because OS/2 makes it easy. One does not
need to spend hours poring over manuals. You simply do what you want.
Quickly, they will be just as capable as today's power users. That is one of
the beauties of OS/2, making the today's power available to today's user.....
Perhaps it is unfair to compare Windows 3.0, a fully released product, to
OS/2 2.0, a beta still a month and a half away from general availability, but
I must say that under OS/2 I am able to get more done faster and more
reliably than I was ever able to under Windows. Ironic, isn't it? I can't
wait for general availability!" UNIVERSITY OF CALIFORNIA IN SANTA BARBARA,
CA - KEVIN W. LAIRD, MICROSYSTEMS GROUP COORDINATOR
"I think OS/2 is a real winner even for single workstations....the real
reason is that it's simply more productive.... True preemptive multitasking
is wonderful....and formatting disks, downloading or faxing in the background
really saves time.... I think one reason this product has improved so
dramatically is that IBM listened carefully to it's customers....... it's a
phenomenal product. I'm happy to say that your performance claims are real,
not just hype. The improved DOS & Windows support is ABSOLUTELY PHENOMENAL!
Your team has done a first rate customer-oriented job developing this
product. We are delighted with it's capabilities. I wanted to let you know
how much we appreciate the leadership role IBM has taken with this new OS/2.
Keep up the good work." MAYER BRYSON INVESTMENTS IN SAN FRANCISCO - ROBERT
MAYER, PRESIDENT
"The PC had a glorious birth, followed by some trying formulative years, but
now I see the PC on the edge of taking it's place as a productive member of
the DP society. I believe that OS/2 will make the PC the premier member of
this future DP Society..... OS/2 is finally moving the PC into a mature stage
of life....... When we evaluate a product (application software) the
evaluation can be solely based on the business need rather than limited by
the operating platform." MASS MUTUAL INSURANCE COMPANY - DENNIS AIROLDI
"It's like having a graphics workstation built into a mainframe as friendly
as a Macintosh.... With OS/2 and the Workplace Shell, we can, for the first
time, deliver the mainframe processing power and connectivity needed for our
complex applications with the flexibility and ease of use of a fourth
generation GUI....... OS/2 and the Workplace Shell gives our complex software
the processing power our users demand, combined with the ease of use needed
for first time users..... The Shell....far surpasses the Windows environment
(a DOS Extender) and other GUIs in performance/price, ease of integration,
utility, and program-manipulating and executing power." MANUFACTURING
INTEGRATED SYSTEMS, AN INDEPENDENT SOFTWARE VENDOR USING OS/2 2.0 FOR
MANUFACTURING APPLICATIONS - NORM HARRIS, PRESIDENT, (SAN YNEZ, CA)
"OS/2 2.0 has great affinity with my large system background. For example, I
appreciate the 4K demand paging, multi-threading, CUA compliance, and other
features that I first became acquainted with in the large systems
environment. Having struggled to obtain connectivity to both 5250 and 3270
hosts in the same DOS machine, I truly appreciate OS/2s ability to
communicate...... What do I run on my machine? Has OS/2 2.0 displaced MS
DOS and Windows as my operating environment? ABSOLUTELY!" DRESSER RAND IN
PAINTED POST NY -JAMES R. SMITH, SR. SYSTEMS PROGRAMMER
"OS/2 Version 2.0 is exactly what I need to perform my job, an industrial
strength personal computer operating system. In five months of heavy daily
use I have not experienced a single operating system crash..... In the final
analysis when you're finished playing games and ready to get to work, OS/2
version 2.0 is the product for you." LUCKY STORES IN DUBLIN, CA - BOB
GAUTHIER
"OS/2 has finally surpassed my expectations.... OS/2 definitely proved to me
that it is better Windows than Windows! I would not have believed it if I
had not experienced it myself!!! IBM has convinced me that if anything has
been done right, it is OS/2!" VAN WILLIAMS, ADVANCED TECHNOLOGY RESEARCHER
IN SAN ANTONIO TX
"OS/2 simply revolutionizes the desktop.... Designing and developing
applications for OS/2 is a dream come true. The machine works for the
developer now rather than being a recalcitrant hunk of iron to be man-handled
through it's paces." TEXAS INSTRUMENTS IN PLANO TX - RICHARD BROOKS,
OPERATOR WORKSTATION DEVELOPER
"I am looking forward to moving everyone to OS/2 just as quickly as possible
since it runs all of our applications while giving them full resource
availability and protecting them from interfering with each other. From the
support perspective, this is a dream come true. Instead of five
environments, I can see the day rapidly approaching when I'll only have to
support and train in one - OS/2..... The stability and reliability of the
platform means that I will get fewer service calls and increased client
satisfaction..... With OS/2 safe multitasking has finally arrived allowing
me to recover machine power that would otherwise have been wasted..... With
all of the applets that come with OS/2, a person can actually do productive
work without purchasing other products." CAJUN ELECTRIC POWER IN BATON ROUGE
- DON BABCOCK
"Multiple sessions is an absolute must in my job, and I can print mainframe
reports in the background!!!!.... Running OS/2 2.0 at work, at home, at the
unit, in a tent under fire, out on the runway, in a foxhole.....
anywhere...... everywhere!!!!!!!! What sets me apart from others is that I
am elated about OS/2 from maybe a different point of view from the rest, I am
a user!" MARC C. JONES AT CAJUN ELECTRIC POWER IN BATON ROUGE
"You have already proven to be a better Windows than Windows!..... I
consider myself a winner being in on the testing of the Operating System of
the '90's - OS/2 2.0" WASHINGTON PUBLIC POWER SUPPLY SYSTEM IN RICHLAND
WASHINGTON - PAT MURPHY
"OS/2 2.0 to a PC user is what a ratchet is to a mechanic. How did we ever
get along without it...?" TARGET STORES IN MINNEAPOLIS - CRAIG ANDERSON ,
MANAGER, END USER COMPUTING
"The years of waiting for the right operating system are over. Furthermore
our professionals can use PCs in their area of expertise without having to
become experts in the underlying operating system because of the friendly
interface known as the Workplace Shell! Power and Productivity without the
frustration PC users have known until now....hats off to IBM!" NORTHWEST
PIPELINE CORPORATION IN SALT LAKE CITY - LEE TORNOW, STAFF ANALYST
INFORMATION SYSTEMS
"The actual installation was completely painless and a pleasant surprise....
It is reassuring to know that I will not have to abandon existing software
when we migrate to a new operating system..... Cutting and pasting between
DOS application windows will allow the creating of new reports and visual
presentation aids...... I will be running V 2.0 on my home system as well as
in the office because once you get accustomed to the power and versatility in
one environment, it's hard to go back to something less at home." LOCKHEED
SPACE OPERATIONS IN TITUSVILLE, FLORIDA - RICHARD CLINTON NETWORK
ADMINISTRATOR
"Sort of like a good book, you just can't put it down or stay away from
it........ The use of preemptive multitasking along with the memory
protection provided by OS/2 makes those UAE's (Unrecoverable Application
Errors) nearly a thing of the past. However if it does occur, simply close
and then reopen the application. All other programs running on the system
are unaffected..... The system performs several operations, overlapping many
of the longer running functions without any fuss or muss on your part.....
The Workplace Shell (WPS) is the hottest thing to come down the PC pipeline
since the original PC.... OS/2 also includes a collection of bells and
whistles IBM call applets.... OS/2 2.0 has more applications available for
it (not tomorrow, not next week, but today) than any operating system in
history. It can run your DOS, Windows, and OS/2 applications
unmodified...... A today's operating system for today's hardware, that's
IBM's OS/2 Version 2.0" SHERRILL FURNITURE COMPANY IN HICKORY NC - DAVID
ELLER
"Any application plus OS/2 plus any machine should equal productivity. I
believe the Workplace Shell is one of the smartest features of OS/2."
AMERICAN AIRLINES IN TULSA OKLAHOMA - DENNIS P HAYES, SR. EDP SYSTEMS
ENGINEER
"OS/2 lets you do what YOU want to, because it does what you want!" CHASE
MANHATTAN BANK IN NEW YORK - DAVID GROSS, STAFF CONSULTANT
"OS/2 2.0 allows us to more effectively utilize our existing hardware by
supporting the simultaneous execution of OS/2 1.3, Windows, and DOS
applications on a single PC...... My 9 year old son messed around with
OS/2...and five minutes later I came back downstairs to find him changing
screen colors, moving folders, playing games, and working with various
applications that come with the system." AN OS /2 APPLICATION DEVELOPER -
WAYNE HOLMES IN BELLEVUE, WASHINGTON
"OS/2 is a truly empowering operating system for application developers. It
easily supplants AIX as the ideal development platform.... OS/2 is a
mainframe on the desktop..... While the advanced hardware has been there for
some time, it took OS/2 to finally make the promise of mainframes on the
desktop come true.... Whether you are a developer, a systems integrator, a
big iron MIS Professional, or an end user, OS/2 is the operating system of
choice for the desktop...and it's a lot of fun too. I'm having the time of
my life." HILBERT COMPUTING IN OLATHE, KANSAS - GARY MURPHY, SR. PROGRAMMER
"At home my 12 year old daughter finds no difficulty installing her game
software and using the system for recreation...... The system is a
programmer's dream.... OS/2 shines in the support area.... One technical
support staff person can support many technical workstations because of the
workplace shell and networking software installations. No other product can
make that claim. It is truly a open software..... OS/2 is affordable,
maintainable, and powerful. I do not believe it will have a competitor for a
long time to come. It is better business to use it to develop new user
applications than to redevelop it." ASHLAND OIL IN ASHLAND KY. - CHARLES
DUCK, PROJECT DIRECTOR OPERATIONS PLANNING
"OS/2 allows the marriage of tools that were better left divorced from one
another." BLUE CROSS & BLUE SHIELD IN CHICAGO - JONATHON HANDLER, SR.
CONSULTANT
"The reason I like OS/2 is simple. I get more work done when I use it....and
that's why I bought a computer in the first place." NATIONWIDE INSURANCE IN
CARROLL, OHIO - TERRANCE CROW.
"With the new folders, I can very easily arrange my computer work in a way
that is very convenient for me.... The Drag & Drop concept is also a real
time-saver. With it, doing things like discarding old items becomes
trivial.... The Workplace shell certainly gives me new freedoms to do things
the way I like, thus improving my work. The ability to run any software I
need gives me a real performance boost." TEXACO IN HOUSTON TEXAS - JIM
WILLIS, INFORMATION TECHNOLOGY DEPARTMENT
"Maximum Flexibility - that's OS/2 2.0..... Flexibility no other operating
system can provide. OS/2 2.0 has significantly improved my personal
productivity and flexibility." MCKESSON CORPORATION IN RANCHO CORDOVA, CA -
BUS S. SWINE, DIRECTOR, DATA CENTER SERVICES
"Mere mortals don't have the words to describe how impressed I am with what
OS/2 2.0 can do for me.... still to me the best part of all is the way the
Workplace shell ties it all together. The power of the new shell is amazing.
By changing the way I look at the system I am now much more efficient at what
I do... dragging and dropping confounds my co-workers who are used to the
endless sequence of keystrokes used for deleting, printing, and just about
everything else.... I must admit, though, that I did have to give up a lot.
A lot of frustration; a lot of headaches; and a lot of lost time that
is!..... The Windows-OS/2 battle from a technical standpoint was over long
ago and Windows never stood a chance." LEONARD'S METALS IN ST. CHARLES, MO -
DAVID BLAIR, PROGRAMMER, NETWORK SYSTEMS ADMINISTRATOR, CONNECTIVITY
SPECIALIST
"...and those from the land of Boca delivered on their promise and the child
was christened OS/2 2.0, and it was good!..... Freedom of choice is the
hallmark of OS/2..... OS/2 raises your level of expectation and fulfills
that expectation. This is the standard against which all operating systems
will be judged, and this is a very tough act to follow because users are
finding quietly, unobtrusively, OS/2 opens the doors to vistas that you've
only been able to dream of through Windows." PHILLIPS 66 IN BARTLESVILLE,
OKLAHOMA - BOB WESNESKI, ANALYST & POET
"OS/2 2.0's ability to multitask DOS applications, Microsoft Windows 3.0, and
all OS/2 applications in a protected environment is an incredible boon to my
productivity...... You can install OS/2 2.0 and begin work immediately.....
Workplace Shell is a new, extremely easy and powerful object-oriented
desktop... After using the Workplace shell for a while, I find the Macintosh
OS kind of klunky.... There is no equivalent on any other system.... I
finally have access to a stable, fast operating system that has tremendous
potential to carry me into the 21st century and beyond...... I currently
have OS/2 running on a non-IBM machine, and I haven't had a single problem
with incompatibility.....I know what operating system will be on ALL my
machines, and it's OS/2 2.0." SECURE MICRO SYSTEMS IN LAFAYETTE IN - GARRY
ADKINS, PRESIDENT & OWNER
"OS/2 can help! OS/2 can help! OS/2 can help! It does not matter what
business you are in or whether or not you are new in business.... It
WORKS!!!!! IBM and OS/2 are going to make my next professional 15 years the
best of my life in whatever environment I find myself..... It will be the
standard operating system for all of our personal computers worldwide. I
know that my company's investment in computer hardware and software are
secure now that IBM OS/2 is on the job.... Future developments in the
Ultimedia (Multimedia) market prove the value of OS/2 as the most viable
personal computer operating system to ever hit the market. The ability to
use touch screen technology in conjunction with audio visual systems for the
purpose of person-to-person communications in manufacturing and educational
environments can only help America regain her economic leadership
status....... IBM and OS/2 2.0 are America's best business partners and are
helping to make our best resource, our people, more productive!" TITLEIST &
FOOT JOY WORLDWIDE IN NEW BEDFORD, MA. - CARL S. NORMAN, SUPERVISOR, END
USER SERVICES.
"I would like to share my enthusiasm over your new product: OS/2 V 2.0. I am
currently going to college, and it is an excellent tool. It is a vast
improvement over any DOS version (I own 5.0) and while it makes the desktop
appear similar to Apple's MAC it is superior because it is compatible with
several different formats of applications and is a true multi-tasking
system.... OS/2 is also a much stable platform than Windows..... I also
won't have to listen to Mac users talk about how unfriendly IBM's are (GUIs).
I like mine just fine with OS/2 V 2.0." CHRIS NOLEN, COLLEGE STUDENT
"The OS/2 2.0 Workplace Shell's object-oriented environment makes the
computer desktop intuitive and flexible. It is a greater leap from 1.X than
1.X was from DOS..... The addition of multitasking DOS and Windows
applications makes 2.0 the most powerful desktop operating system ever ---by
far." JOEL POOLE IN CORTE MADERA, CA
"I was looking forward to the convenience of integrating the running of OS/2,
DOS, and Windows programs. This feature turned out to be great - better than
I had hoped. But it was OS/2's full use of extended memory which changed my
way of doing things. I feel like I've grown an extra pair of hands..... The
primary reason for my surprise at the way OS/2 has transformed office routine
into office dynamic is the manner in which mutitasking saves time; and this
must be experienced to be completely assessed. The result is phenomenal! So
what you are offering here is, among many other good things, the
computational equivalent of open stacks in the library, the sine qua non of
Search & Discover..." CHANDO ENTERPRISES IN COLUMBIA, MD - WM A. DONNELLY,
PH.D ANALYST
"The Workplace Shell certainly enables a sophisticated, function-rich
operating system, for use by many a user, whether they are computer people or
not.... The new OS/2 has the potential to become the development platform
for many a mainframe shop, at a substantial cost savings in cost per CPU
cycle. It will also improve the efficiency of the programming staffs and of
migrating code to larger platforms because of it's thirty two bit
architecture.... The new OS/2 removes any reason any one might have to go to
Windows. It also removes any excuse any one might have for staying with DOS
because anything else is too sophisticated.... The SAA features of OS/2 2.0
make it a connectivity platform for anyone needing to participate in a
mainframe dominated environment.... In conclusion, OS /2 2.0 has something
to offer the largest segment of users since the first coming of DOS." FORD
MOTOR IN LORAIN ASSEMBLY PLANT - NEIL PATTERSON, CIM COORDINATOR AT LORAIN
ASSEMBLY.
"The technology used to integrate these environments (DOS, Windows and the
Workplace Shell) is very impressive." STATE FARM INSURANCE IN BLOOMINGTON,
IL - JIM BETHMANN, SR. ANALYST FOR DP OFFICE SERVICES
"Basic Services installs easily as was promised. Great job!..... I'm
convinced that EVERY DOS PROGRAM out there can run..... OS/2 V. 2.0
certainly runs the widest base of PC applications of any PC operating
system..... I was on the team that reviewed PC operating systems to
determine which would be the operating system(s) that we would recommend in
Texaco LA/WA. The one we picked was OS/2 Version 2.0." TEXACO IN CORAL
GABLES, FLORIDA - CARL HERRERA, SYSTEMS ANALYST
"OS/2.... It's the greatest! I just wanted to express my enthusiasm for the
significant improvements in OS/2.... I believe this is truly the operating
system of the future--almost all things for all users!" UCAR EMULSION SYSTEMS
IN CARY, NC. - B.F. COLE
"As a programmer, I love being able to run a compiler in the background while
editing a file in the foreground." ALAN LAU, AN INDEPENDENT PROGRAMMER IN
WINDSOR CT
Object Oriented Interface
Plenty of Power
Excellent Development Platform
Robust API Services
All in One Solution
True Multitasking
Intuitive Help
No more segmentation
Great Flexibility
Sound Investment
Yours for the asking
Simplified Set Up
Truly Mature
Extraordinary Support
Most Reliable
Operating
System Around
/
2 good to be true!
THE TRAVELERS INSURANCE IN HARTFORD, CT - RON CALEBRESE, TECHNICAL DIRECTOR,
COMPUTER SCIENCE
"Thank you for following through on a promise to create what I believe will
be the small systems operating system of the future.... I have found that
IBM is delivering much more that was originally expected. The look and feel
of the new graphical interface is a pleasure to work with, and extremely easy
to use and understand. I am very pleased with all of the drag and drop
features that have been added and look forward to being able to use some of
the other newer features such as tear off menus. As a developer of software,
I can appreciate the effort that has been put into this project. It appears
to me that many of the best things out in the marketplace have been
incorporated into this environment and as a result, a most exciting product
has emerged. Even the installation process is to be commended.... Some of
the aspects of the environment that I was most impressed with were the speed
of the system once loaded, and the amount of work that was done to get the
Windows interface to run it's applications flawlessly and with great
speed.... This new 32 bit version takes the cake." DUN & BRADSTREET
CORPORATION IN PARSIPPANY NJ - ANTHONY PALASCIANO, SR. SYSTEMS ANALYST
"OS/2 is definitely for me and for you! We have had OS/2 in production since
Version 1.2 with tremendous success...... OS/2 2.0 is also the reason for
many support/development groups to centrally focus efforts to deploy common
services.... IBM enterprises can now expand to the desktop without fear of
disabling user productivity. The magnitude of this expansion can not be
covered entirely here. OS/2 2.0 is bringing added dimension to enterprise
computing.... Yes, I'm impressed! " USAA IN SAN ANTONIO, TEXAS - JOHN R.
MIRANDA, SR. SYSTEMS PROGRAMMER, COOPERATIVE PROCESSING
"OS/2 Version 2.0 is great! The level of functionality and versatility built
into this product is incredible.... OS/2 is a great value. Of course, OS/2
runs DOS and Windows software. But, it goes well beyond them by providing a
level of reliability and fault isolation unmatched by either of those
environments on their own..... This is really a bargain, OS/2 is an
incredible value!!! OS/2 is also a platform for improving productivity...a
user can manage the entities inhabiting his or her computer in a more natural
and intuitive way..... The WPS goes beyond that by allowing a user to
directly manipulate those beasties in the box in a consistent manner..... I
congratulate IBM on being bold enough to provide a major enhancement over the
standard GUI.... One aspect of OS/2 which hasn't been discussed much is how
easy OS/2 is to administer and run. There is a good deal of tinkering that
has to be done to use many of the DOS tools that expand the standard DOS
environment; for example, PIF tuning files may have to be established and
areas of memory usually have to be carefully managed for those tools to
work.... These problems melt away with OS/2. I also hope people realize
that, in all the talk about OS/2 and how it represents the new IBM, it also
represents one of the most admirable traits of the old IBM. IBM has always
been a company with integrity, it hasn't reneged on promises made to it's
customers...... OS/2 in all its versions continues that tradition..... a
user's original software investment is protected while also providing
considerably advanced functionality in the overall system.... Good luck on
the roll out of OS/2. I'll be using it here and pushing for its success where
I can... " PAUL FIRGENS IN WHITE PLAINS
"OS/2 2.0 is head and shoulders above anything PC users have seen to date.
OS/2's power yields a simplicity that is unheard of. PC users have never had
it this easy. I really feel that as soon as the computing public learns how
easy OS/2 is to use and how many of the nightmares of DOS it eliminates, the
demand for OS/2 and OS/2 applications will go through the roof.... OS/2
frees you to concentrate on using our computers rather than fighting with
them to get the job done. Personal Computer users no longer have to worry
about whether a program is for DOS, Windows, or OS/2. You simply install it
and run it. Nothing could be easier than that." PETER NORLOFF IN FAIRFAX,
VA
"I think OS/2 2.0 is a fantastic product with a very bright future....
Workplace shell has resolved the conflict (speed vs. quality) between pretty
and productive.....it makes my VGA screen seem to have better resolution than
before, and the speed is excellent.... OS/2 2.0 does an excellent job of
performing several background tasks while providing superb responsiveness to
the task at hand.... Not just having several applications open at once, but
actually having them all work productively without a performance impact. I
finally feel that my computer system is being used to it's fullest
potential.... I believe that IBM's MVS has been the most reliable operating
system in the world for many years, and now the PC industry will benefit from
IBM's vast experience in virtual memory and protected operating systems with
OS/2 2.0.... One of the most important features of OS/2 2.0 is that it
protects users investment in hardware, software, and training.... OS/2 is
running flawlessly on a wide variety of systems.... I don't have to buy any
new applications in order to start taking immediate advantage of many of the
benefits of OS /2 2.0. I can gradually migrate to native OS/2 applications at
my own pace as new versions and features warrant. The protection of my
investment in application programs and of my knowledge of using them allows a
smooth transition to a more powerful operating system.... I can safely run
several of my existing DOS & Windows programs simultaneously without any
interference between them. No more fighting with limited memory for TSR
(terminate and stay resident) programs either. I simply run each in it's own
DOS window!......and I can cut and paste data between DOS, Windows, and OS/2
programs easily. I'm glad that this manual memory management is a thing of
the past..... OS/2 2.0 is definitely a better DOS than DOS, and a better
Windows than Windows.... All in all IBM has ensured that users can upgrade
to OS/2 2.0 with a minimum of cost and pain that so often accompanies
significant changes in software.... I was especially pleased to find that I
could upgrade an old copy of PC DOS to OS/2 1.3 for $99...that in itself was
an outstanding value. Best of all, IBM will give me a free upgrade to
version 2.0 when it becomes generally available! I have to say that this is
absolutely the best software value I've ever seen! I have seen the future of
desktop computing, and it is OS/2." UNIVERSITY OF MICHIGAN HOSPITALS IN ANN
ARBOR, MI - EUGENE T. MANGUM, SYSTEMS PROGRAMMER AT TAUBMAN CENTER
"After using OS/2 for the last four months I feel very confident that OS/2
2.0 will be a major success for IBM and a substantial advance for
productivity for workstation users.... OS/2 2.0 is proving to be a well
crafted and a well designed operating system.... Especially noteworthy is the
dynamic data exchange feature between programs running in Microsoft Windows
and OS/2.... I am looking forward to rolling out the general availability of
OS/2 2.0 to both our system developers and end user communities." BLUE CROSS
& BLUE SHIELD IN JACKSONVILLE - FLORIDA OTIS J. GARBER, SYSTEMS DEVELOPMENT
PROJECT MANAGER
"Users finally get what they have been asking for.... So far with very
little tuning I am able to run the following programs simultaneously:
DOS-Professional Write 2.22, DOS-PC Tools 6.0 Desktop, DOS-Harvard Graphics,
OS/2-Communications Manager for 3270 session, 3270 print control,
Windows-Lotus 123 for Windows. I know that whatever the scenario a user
brings to the table OS/2 2.0 will solve it." LUTHERAN HOSPITAL IN FORT WAYNE,
IN - BRETT TAYLOR, NETWORK ADMINISTRATOR
"OS/2 was designed with business in mind.... with it's enhanced DOS
compatibility, OS/2 offers us a migration path which protects our heavy
investment in DOS software while giving us the additional capacity we need to
support future growth on our branch workstations.... IBM has taken a major
step in fulfilling the strategic plan mapped out in 1987 for Operating
System/2. I would encourage business users who have not seen OS/2 in a while
to take another look." NATIONS BANK IN NORFOLK, VA - FRED JACOBS, LEAD
SYSTEMS ANALYST
"Anyone who isn't excited about OS/2 V. 2.0 either hasn't seen it or they
simply aren't big enough to admit they were wrong. You've done it again
IBM!" TEXAS TECH UNIVERSITY IN LUBBOCK, TX - DONNA CHAFIN, ADMINISTRATIVE
INFORMATION SYSTEMS
"I write to you now as a last resort. You see, I have lost my boyfriend to
OS/2. For the last two weeks he has been locked in the computer room as if he
was a mad scientist on the verge of a momentous discovery. I knock, I pound,
I whimper into the keyhole, I slide notes under the door; all to no avail....
I could hear him cackling with glee and often I heard awe in his voice that
sounded as if he were witnessing the second coming.... I must go in after
him. Clearly this man of mine cannot help himself. The temptation of OS/2
is too great. He is hooked and I am the only chance he has left.... If you
can't beat em, join em! letter from the boyfriend: I became convinced only
when OS/2 2.0 was demonstrated with ENTHUSIASM, by IBM. Because of this I
cannot help but demonstrate OS/2 2.0, with ENTHUSIASM, to others. You have
succeeded!
You have given me something that I did not possess before: a choice, and a
chance to be better." UNIVERSITY OF CA AT BERKELEY, L CHRISTIAN CANDELMIRE
AND JOHN SCHULBERT
"The King is dead, long live the King!... It has been said throughout
history and it shall be said again...this time OS/2 is King. After 10 years
the PC has finally arrived. IBM has drawn another sharp dividing line in the
history of personal computing with OS/2 2.0. An operating system that works
with me - not against me. An operating system that lets me fully realize the
personal in personal computer. An operating system that lets me use the
strengths of the mainframe while utilizing the flexibility and the power of
the PC..... Finally, let me paraphrase from an old review by Robert Schumann
in reference to a little known composer of the day named Frederick Chopin:
Hats off Ladies and Gentlemen, a winner! Just as Chopin forever changed the
way people would play, listen, and compose music for the piano, OS/2 2.0 will
forever change the way people use and interact with a PC." INFORMATION
RETRIEVAL COMPANIES, INC.
"Without OS/2 2.0, I frequently found myself interrupting one PC application
to start up another. Often I had to reboot the machine to get a different
configuration to match a specific application's need. No more! Those days
are over, OS/2 can do it all.... No more wasted time saving files and
retrieving files. No more stopping and starting applications. No more
telling people: I can't do it right now, come back later. I can just
smoothly transition my PC along with my thinking from one task to another. I
can do my own job better and faster.... OS/2 has fulfilled it's promise. It
truly handles multiple applications in multiple environments and does it
well. OS/2, Windows, DOS ---OS/2 can do it all!" LOYOLA UNIVERSITY IN
CHICAGO - WALTER M. SLAZYK, LEAD SYSTEMS PROGRAMMER
"The idea of packaging OS/2 2.0 with all the tools necessary to do everything
from spreadsheet analysis to personal time management is a big incentive
where time and money is concerned..... Some people may not use two programs
at the same time but once they see what can be accomplished with multitasking
from within a single program I doubt they will see an advantage to DOS
afterwards.... I believe that OS/2 2.0 is a strong robust operating system
that does not only need to installed on file servers or the highest power
computers that corporate America has. The home computer is becoming 32 bit
and with the utilities, games, and editors that are available under OS/2 2.0
the home user could easily take advantage of the installed features. The
information age is upon us and OS/2 2.0 is a strong base upon which to
build." UNIVERSITY OF CA AT SANTA BARBARA - BRUCE WALLACE, DEVELOPMENT
ENGINEER
"Workplace Shell is fabulous. I'm constantly amazed at the number of
powerful, easy to use features you've incorporated.... I also think your
implementation of DOS and Windows is excellent. Both are fast, stable and
complete. Windows applications work great and DOS applications definitely
run better on OS/2 than on Windows.... I think IBM has got a winner here.
2.0 is fast, stable, flexible and easy to use. It runs great on my 1988 16
MHz clone despite the old BIOS. And you've incorporated a lot of good
customer suggestions. I'm definitely sold. Keep up the good work!" MAYER
BRYSON INVESTMENTS IN SAN FRANCISCO - ROBERT MAYER, PRESIDENT.
"The freedom provided by being able to pop open a new session, grab the
needed information and act upon it without disturbing my previous work is
invaluable. With OS/2 2.0 it does not matter if the data is on my local hard
disk, on the mainframe, or on one of our UNIX servers... OS/2 2.0 truly
integrates all of these disparate information sources into the PC on my
desktop.... No more wasted time getting in and out of applications. No more
worries about the system crashing when one more application is loaded.
Office visits are shorter, more productive and spawn fewer drop by later, I
can't get to that now results. Overall it's just a better way to work."
DAVID MATOCHA IN RICHMOND, TX
"I have to say that it (OS/2 2.0) is the only serious multitasking operating
system choice for desktop. The new Workplace Shell is powerful and
configurable, and icons stay where you put them. The system runs DOS better
than DOS itself, allows for fast 32 bit programs and even runs uncooperative
DOS shells (such as Windows) with no problem. I can leave my workstation on
for days without rebooting, and can debug large programs using DOS protected
mode interface. Nothing else even comes close. It's a real operating system
for everybody, not just servers, as some have claimed, and not just users who
have only perfect applications, as all the task switching DOS shells
require.... Thanks for sticking with OS/2 and with all of us who believe in
it." MICRO MAGIC SYSTEMS IN BOLIVAR, MO - JERRY L. MCKITTRICK, SR. SYSTEMS
PROGRAMMER
"The workplace shell ends the frustration of PC users who feel helpless with
technology. After a short introduction to the environment, a few examples of
the context sensitive help feature, and the simplified logic of the workplace
shell, I am certain empowered users are right around the corner. I am
actually looking forward to introducing people to a streamlined version of
the already powerful desktop.... The icing on the cake for your product (is
that) the documentation is clear and concise. You have made OS/2 2.0
accessible to people that are not techies. The casual home user market will
love it's simplicity and it makes it an all-around great and well thought-out
product.... Everything to gain and nothing to lose. I thought there was no
such thing as a free lunch. I do not know how you did it but I want to thank
you for the revolution of the PC world. I guess if you want something done
right you have to do it yourself. Now all you need to do is let everyone
know, then they will feel the same way as I do - I can't live without it!"
CIGNA INSURANCE IN HARTFORD, CT - CHRISTINE MONARCHIE, LAN ADMINISTRATOR
"OS/2 2.0 is a fantastic product and a much needed tool for knowledge workers
everywhere.... The Workplace Shell is exceptional.... OS/2 provides real
value.... A few more pluses for OS/2 2.0: the product documentation, both
online and hardcopy is superb....includes a 3 frame Super person cartoon
depicting OS/2 2.0 vs. Windows Unrecoverable Application Error." CIGNA
INSURANCE, BLOOMFIELD, CT - DAVID A. PINARD, LEAD SYSTEMS DESIGNER
"Compared to the dedicated single user software products that have become so
popular under Windows, major new enterprise applications will all require an
entirely new level of operating system support.... Multithreading is a key
OS/2 feature, and one that may impress more than a few individual users
because it increases the performance of application software..... The most
likeable feature of OS/2 2.0 for the individual user is the ability to keep
what that user has now (DOS with Windows) while adding some new benefits,
such as performance, and the ability to try some new OS/2 specific software.
Gain without taking a loss...easy to accept. OS/2 is perceived as a
potential cure to many ills that exist in the DOS Windows third party
communications and database software solutions being attempted today.... I
would like to suggest that you fight to characterize OS/2 as more than just a
better DOS than DOS, etc. Rather this is really a new generation operating
system that goes far beyond DOS. It is like the automobile compared to the
horse and buggy. They both get you there, but can you really compare them?
Although when the automobile first came out there were no interstate
highways, there are today. And we all know the value of the automobile.
OS/2 is for the computing equivalent of the interstate highway. We can't
live without it, but that vision has not occurred to everyone." CITIBANK
(PRIVATE BANK DIVISION) IN VALHALLA, NY - DAVID H. JANSON
"In a nutshell, it is Great! Flexibility that will be available for support
and testing functions by being able to boot different configurations of DOS
Windows concurrently......of great importance is the ability to have an
advanced level LAN Server with a Ring O Implementation. That ability with
the new cache optimization of 386HPFS and the ability to create layers of
administrators with specific function really will give your network operating
system some of the enhancements that have been severely lacking..... Most
everyone who walks by and sees my desktop becomes very interested in when
they can have this release on their machines." GULF STATES UTILITIES COMPANY
IN OCAUMONI, TX - DR. KAREN S. MCCONNELL, SCD., LAN TECHNICAL COORDINATOR
"When asked what my impressions are with OS/2 2.0 I would have to say three
things: Power, Reliability, and Support.... People now have choices...
Choices in not only what people may run, but also how they run. At last,
there is an operating system in which power complements flexibility....
Never have I been in a program in which the company was so concerned about
the product, not the release date. Never have I been in a program that was
designed to enhance and evolve as opposed to patch and move on. Support does
not just come after a product is released; it should start as soon as it is
designed. Intuitive interfaces (such as the WPS), compatibility with
existing standards (DOS, Windows, etc.) and knowledgeable help desk staff all
contribute to a well supported product. IBM's OS/2 2.0 has all of these
features and more with a complement of services such as Prodigy, IBM Link,
National Support, and those great SEs..... OS/2 2.0 is not an operating
system of exceptions; it is an exceptional operating system. Power,
Reliability, and Support---I say Push the Power! Thank you for an operating
system well done. " CA POLITECH STATE UNIVERSITY IN SAN LUIS OBISPO, CA -
DAVID B, MASON, ASSISTANT SYSTEMS ANALYST
"It was amazing to see IBMCAD, several host login sessions, X-Windows, and a
couple of PC DOS prompts all running at the same time.... It was a pleasant
surprise to find that nearly every DOS application I use works under OS/2
without any fuss. The Windows applications I tried under OS/2 worked without
a hitch and ran as fast as they would under Microsoft Windows. Even though
this is beta code, performance is quite good. In particular, switching
between multiple DOS applications is much faster under OS/2 than with
Microsoft Windows.... I finally realized I was hooked on OS/2 when I went
back to PC-DOS and found myself saying, 'If I only had OS/2 I could open
another DOS session and...' or '...if I had OS/2 running I could open a
window to the RS/6000 or DEC VAX and....' Congratulations on a fine product.
It has the potential to make the personal computer platform more usable than
ever." SMITH METER, INC. (A MOORCO CO.) IN ERIE, PA - BRAD HARRISON, SYSTEMS
SOFTWARE ADMINISTRATOR
"In my opinion IBM has successfully and aggressively addressed every issue
concerning the operating environment choice. It is competitively priced,
runs 32-bit applications, it can also run DOS, Windows, and existing OS/2
programs. It is fault-tolerant, and the only true multitasking environment
on the market. I have seen no other product that can make those claims. In
my opinion, I would have to say IBM has lived up to their promise of offering
a better DOS than DOS, better Windows than Windows, and yes, believe it or
not, a better OS/2 than OS/2." WILLIAM STEPHENS IN SAN ANTONIO, TX.
"There comes a time when a company should get excited about a new product
that it has created. Well, OS/2 2.0 is the product and 1992 will be the year
to be remembered. IBM and OS/2 will the standard of the computer industry,
the same as DOS was when it was introduced to personal computers many years
ago.... OS/2 is a true state of the art technology and nothing like it exists
on the market today. Anyone who is planning to purchase an operating system
should, without hesitation, make OS/2 a viable solution to their computer
needs. OS/2 has the power and flexibility to fit into any environment from
the base operating system to connectivity to a mainframe. The platforms that
it crosses with transparency are unbelievable. I can't imagine what would be
next from IBM." CITY OF RICHMOND, PUBLIC SAFETY DEPARTMENT IN RICHMOND, VA -
PATROLMAN BRIAN KATZ, NETWORK ADMINISTRATOR
"I refuse to read lengthy documentation - I installed OS/2 along with Windows
and Communications Manager without reading a single book --no kidding--the
on-line documentation is all you need! ...best of all, I could finally
utilize the big model 57PC I bought, running multiple applications
concurrently, DOS, OS/2, and Windows together --- I deleted DOS and haven't
used it since!" STAR BANC CORPORATION IN CINCINNATI, OHIO - ROBERT W.
ELBERFELD, VICE PRESIDENT, SERVICES.
"Since installing OS/2, I have been able to significantly increase my
productivity by taking advantage of the multitasking and multithreading
capabilities of this new operating system technology. The transition from
the 'other guys' operating system to OS/2 was a very smooth and cost
effective because OS/2 allowed me to continue to run applications which were
designed to run in the 'other guys' operating system... I have already made
the choice to use OS/2. OS/2 gives me the necessary platform to conduct the
work which needs to be done today and also gives me room to grow in the
future. Release your computers processing potential, free your machine,
embrace the future today with the operating system which will grow with you.
OS/2 breaks the rules and makes up new ones." MICHIGAN CONSOLIDATED GAS -
ROGER G. VINCENT
"We expect our applications to run on a variety of hardware and software
platforms. I am very impressed with the overall function of OS/2 2.0. The
support of the DOS and Windows environments is also very good, almost every
one of the programs running under those systems came up immediately. My
overall impression with OS/2 2.0 is excellent. It is a good product with
several very nice features. I would recommend it without reservation."
FROSYTH MEMORIAL HOSPITAL IN WINSTON SALEM, NC. - KENNETH WISEMAN,
APPLICATIONS MANAGER
"Once you let go of past systems and begin to concentrate on what you wish to
accomplish and not on how to do it, the beauty of the Workplace Shell begins
to show through.... The multitasking performance of OS/2 2.0 is excellent...
The multitasking capabilities of OS/2 allows a person to work with their PC
in interrupt mode much the same way they normally work in todays business
environment. The developers of OS/2 2.0 have created the operating system
that we have been needing for a number of years. They have done an excellent
job and are to be commended." GULFSTREAM AEROSPACE CORPORATION IN SAVANNAH,
GEORGIA - GREG CANADY, MANAGER OF TECHNICAL SUPPORT.
"Why be content to run when you can fly?... How could I ever clip my wings
once I have experienced flight?...Well I cannot afford to be content to run
in the DOS world. I must fly, otherwise I will never finish the race, never
get my job done. OS/2 2.0 seems to be the only way to fly..... Finally I
will add that OS/2 2.0 is exciting; it lives up to it's promises and delivers
even more." JEFF LANGR IN WASHINGTON DC
"OS/2 2.0 makes two significant changes in the way we interact with the
computer. First, the Workplace Shell removes many of the anxieties of the
end user who is uncomfortable with command lines and file structures.... The
second, and more significant change is OS/2's true multitasking ability...
Perhaps in a few years multitasking under OS/2 will be like the microwave
oven; people will wonder how they ever got along without it. Let's hope
so.... My job of integrating applications and devices into a useful
environment just got a lot easier. Most of all, OS/2 2.0 provides the
stability and reliability for use in the corporate marketplace. Trying to
describe in words something as rich, complex, and unique as OS/2 2.0, I'll
paraphrase an old saying: To those who have never experienced 2.0, no words
will suffice; to those who have, no words are necessary." GARY RAGAN IN
MERRITT ISLAND, FLORIDA
"For the last several years the PC industry's hottest keyword has been
WYSIWYG... With IBM's release of OS/2 2.0 the new key word is HYCAEIT: Have
your cake and eat it too!.... The real beauty of the operating system is the
ability to utilize all my existing DOS and Windows applications....
Congratulations on an excellent achievement. If Dr. Martin Luther King
hadn't already said, 'Free at last...I'm free at last,' I'd be shouting it
right now." LEN WINKLER AT PLACERVILLE, CALIF.
"I started pushing OS/2 last year because I knew that DOS was too tired to
handle what we needed. I wanted to be able to format a disk while I worked
on a spreadsheet or a document. Now, I have a 32 bit operating system that
works small miracles every time I open a folder. If I am forced to use a DOS
machine now, I am constantly thinking of what also I could be doing at the
same time with 2.0.... By the way, do you guys giggle like I do when you
hear someone yet again telling their woeful tale of setting up another DOS
LAN requester? " HALLIBURTON SERVICES IN HARVEY, LA. - NICHOLAS H.
GARDINER, DISTRICT ENGINEER
"Now, WOW!!!!, it is better than ever. The new Workplace Shell is
terrific!... I also like the ability of running Windows applications without
the need of purchasing Windows.....once again, Hooray for OS/2. No more
failures because some vendor didn't write clean code, and it crashed the
system....to sum it up, I guess I really have to say that it looks like
you've got yourselves a winner with OS/2 2.0. I can't wait to see what
wonderful things you put into the next release." SOUTHLAND LIFE OF GEORGIA -
STEVEN T. FRANCIS
"One of the key benefits that OS/2 has shown me so far is the ability to
enable access to these various platforms on a single workstation. Our
application support folks often need simultaneous access to 3270 and 5250
emulation sessions, as well as their PC based applications. No other
operating system or environment currently supports this need.... The
combination of OS/2 base code and extended services provides unique
possibilities that weren't even considered before with DOS-based
systems....there are two crucial factors in the acceptance of OS/2... First,
and rightly so is stability. The second key factor which is a smooth
migration path from the previous operating system.... OS/2 2.0 is an
excellent step in the right direction. I now feel comfortable in suggesting
this product to my end users. This product does not waste our previous
investment in DOS software, yet it offers an exceptionally better future with
GUI and multithreaded applications. The SEs who service my account are truly
impressed with this product and believe in it's capabilities. That
enthusiasm certainly helps me feel comfortable with my own purchasing
decisions.... It's been quite a while since I experienced the joy of
exploring my computer as a new toy. OS/2 is a technical marvel, and I can
truly appreciate the skills required to write such code. My hat is off to
your developers, and my thumb is waving at those who have said IBM can't
write good code. " SUNTRUST SERVICE CORPORATION IN ORLANDO, FLORIDA -
WILLIAM R. BEEM, PC SUPPORT MANAGER
"OS/2 2.0 is an incredibly innovative operating system for 80386 based
personal computer systems. To paraphrase an old television commercial, 'Try
It...you'll like it,' is how I tell folks to try the new OS/2 2.0 Workplace
Shell. Everyone I've demonstrated the Workplace Shell to has been just as
impressed with it as I am.... What's really great about OS/2 2.0 is that I
can be developing a Windows database application with Objectvision for
Windows, indexing the new documentation for the application with DeScribe for
OS/2 and communicating with the company mainframe with IRMA for DOS. And I'm
doing all of this real work and communicating at the same time. This is
great!.... OS/2 2.0 creates a more productive desktop at my office and makes
my work at home more productive and fun too! OS/2 2.0 really puts incredible
power at your command at home and in the office. I'm looking forward to
getting my shrink wrapped GA copy ASAP..... I would like to see OS/2 2.0
installed on every personal computer system that IBM sells!" HIGH PLAINS
BAPTIST HOSPITAL IN AMARILLO, TEXAS - GLENN R. BOUDREAUX, SR. SYSTEMS
PROGRAMMER
"I love OS/2..... I love OS/2.... I love OS/2.... I am walking around
saying I love OS/2 and now I really mean it!" US NAVY AT CAPE CANAVERAL, FL -
SR. CHIEF WILLIAM NEAL PORTER III, NAVAL ORDINANCE TEST UNIT
"OS/2 2.0 is like a shade tree in a thirsty land. What's the difference
between OS/2 2.0 and Windows? OS/2 2.0 is software and windows is shelfware.
Keep Windows 3.0. Use the documentation as bookends and the diskettes for
scratch diskettes. " BURLINGTON NORTHERN RAILROAD, PAUL MARTIN
"I find myself unconsciously adopting an air of smug superiority whenever I
talk to DOS or Windows users containing our different OS Platforms... OS/2
provides preemptive multitasking even on the 80286 platforms.... under OS/2,
programs can be interrupted by the system, under Windows a program has to
release it's control so other programs can run..... For software developers
in a PC environment, OS/2 is almost a necessity. Some people have
recommended OS/2 for only server applications, but it's value is much more
pronounced in a user environment. I now depend on the ability to easily and
conveniently interrupt what I'm doing without losing the context of my
work...... Compared to Windows 3.x, OS/2 offers better performance,
integrity, and reliability. It more fully exploits the capabilities of
modern hardware and provides an advanced operating system with the most
compatibility to DOS in the marketplace. Our group of testers cannot wait to
get their hands on the generally available product and all share my
enthusiasm for the system." MARTIN MARIETTA ENERGY SYSTEMS, INC. IN OAK
RIDGE, TN - BROOKS MCNEELY, DATABASE & SYSTEMS INTEGRATION SPECIALIST.
"I have come to the conclusion that OS/2 2.0 is like a McDonalds Combo Value
Meal.... A McDonalds Combo Value Meal is made up of three Great American
fast food staples: a Big Mac, large fries, and a medium Coke. All for just
$ 2.99; great food for a great price. OS/2 2.0 is made up of three great
products from every PC users wish list; a powerful 32 bit, non-preemptive,
multi-tasking operating system (Big Mac), a desktop shell/manager that has
the best of Mac and Windows (Large Fries), and full upward compatibility to
run anything ever written for DOS, Windows, and OS/2 1.X (Medium Coke). All
for just $99.00; great operating system for a great price. With OS/2 2.0 you
don't have to buy any extras and actually the desktop manager is even better
than large fries or Norton Desktop for Windows or a Mac(intosh)... Many fast
food chains have tried to imitate McDonalds, but McDonalds' commitment to
giving the customer what they want, a quality product for a fair price, has
kept them number one. You have the chance to be number one with OS/2 2.0. Go
for it!" UNIVERSITY OF MICHIGAN IN ANN ARBOR - KURT RICHARDSON OF UNIVERSITY
INFORMATION SYSTEMS
"I was able to install the OS/2 2.0 operating system, the developers kit, my
favorite DOS applications, and a 10-megabyte swap partition on an 89 megabyte
hard drive, with enough disk space left for my program development work. Try
doing that with UNIX! I believe OS/2 2.0 will define the current state of
the art in operating systems and overall computing capabilities for users
running 386/486 class computers.... I believe that OS/2 is destined to
become one of the most, if not the most, successful operating systems of the
90s. It is good to see operating system software take a step forward and get
into sync with current hardware." JEFFREY S. KILGORE, COMPUTER USER IN
GEORGETOWN, TEXAS.
"I can run my favorite PM applications and my favorite Window applications,
as well as those special character-based DOS and OS/2 applications I can't do
without....all at the same time. I have found OS/2 2.0 fulfills every need I
have in an operating system and then some. It is truly my window into our
enterprise computing environment." CITY OF TACOMA, TACOMA, WASHINGTON -
BRIAN M. DAVELAAR, SR. TECHNICAL ANALYST
"I can build a personal platform from which I can use the appropriate tool
for the appropriate task. Most of all, being able to run a DOS task in the
background will free me from having to give my PC entirely over to one of
those tasks. I'll now be able to continue working on something else, while
the DOS task executes on it's Virtual Machine. I love it! Other substantial
improvements include the master help index, the ease of installation,
selection of print drivers, the Seek and Scan files, and the ability to
create folders for organizing objects. Even the improved ability to control
screen colors and backgrounds helps make the environment one in which I feel
most comfortable and (most of all) productive. I feel like I'm living in the
future." NORTHWESTERN NATIONAL LIFE INSURANCE IN MINNEAPOLIS - WALT CYGAN
"I'm sold! I didn't think I'd be saying this, but I'm a believer. I have
become so callous towards the empty claims of software vendors that I flat
out refuse to even hope for a feature until I've tried it myself....
Congratulations for doing it right.... We believe this type of environment
improves productivity and lowers training costs, so we began the move to GUIs
almost two years ago... You have delivered on your promise, given us a
migration path that makes sense, and because of it the entire computing world
will come knocking at your door (not window). Thanks!" NORTHWESTERN
NATIONAL LIFE INSURANCE - JERRY WALKER, SENIOR ANALYST
"The features of OS/2 2.0 make it a real winner for use at home as well as in
my department... At the office the multitasking features make it a great
tool for our operators and technical support personnel, since they are always
being interrupted and keep many things going at once. With Extended Services
they keep active sessions to the ES/9000, AS/400, and the RS/6000 going all
the time..... For home use, OS/2 2.0 has the wonderful dual personality of
being more powerful than DOS or Windows, but at the same time being easier to
use. The backward compatibility is a tremendous benefit, allowing use of
virtually all the programs we have now with the potential for enhanced
applications that take advantage of the advanced features of the new system.
I'm already looking forward to replacing Word for Windows with DeScribe as my
word processor." SCHOOL BOARD OF ALACHUA COUNTY, GAINESVILLE, FLORIDA -
DANIEL H. CROMER, JR., MANAGER OF SYSTEMS & PROGRAMMING
"OS/2 2.0 provides the most user-friendly environment for the PC platform.
OS/2 2.0 gives the DOS and/or Windows user a no-loss upgrade to a friendlier
and more powerful system with minimal pain. Within an hour or two of first
sitting down with OS/2 2.0, he/she can be significantly more productive...
OS/2's excellent support of DOS, Windows and existing OS/2 applications, with
protection of the system and each process from each other, makes OS/2 the
most integrating operating system available on any computer platform. It is
an excellent choice for the novice end user, the power user, and the
DOS/Windows/OS/2 programmer." PSI COMP SOFTWARE, INC. IN SALT LAKE CITY,
UTAH - BILL HARRIS (CONSULTING AT UTAH DEPARTMENT OF ENVIRONMENTAL QUALITY.)
"OS/2 will bridge the chasm between PCs and TRUE individual exploitation of
the power of information technology. Up until now, we've only been led to
believe that it's been done...... OS/2 has demonstrated how my investment in
textual applications can be stretched further and at the same time, it has
also let me experience the thrill of new graphical tools. My palette of
tools is now much broader than I had ever imagined and my productivity is
greater than ever. OS/2 will remove existing constraints and bring new and
even more powerful tools to my desktop... What excitement the future holds
for us with a new foundation of OS/2! I'm thrilled with the opportunity to
explore OS/2 and guide my company into the future with OS/2 as the catalyst."
TALBOTS IN TAMPA, FLORIDA - DAVID A. NAGY, DIRECTOR, TECHNICAL SERVICES
- OS2-2DOC.ZIP [OS2 Beta 6.167 Docs]
6167DOCS.LST
This is a listing of the documents that can be found on this diskette.
OVER6167.DOC Overview of the 6.167 version of IBM 32 Bit OS/2
INST6167.DOC Installation instructions and list of restrictions for
IBM 32 Bit OS/2 internal driver level 6.167
READ6167.DOC Read me first file for IBM 32 Bit OS/2 driver 6.167
VMBOOT.DOC Paper discussing the Virtual Machine boot function of
IBM 32 Bit OS/2
V2-WIN.DOC Information on running Windows applications under IBM 32
Bit OS/2.
ESLS6167.DOC Installation instructions and list of restrictions when using
Extended Services/2 (version 246) and LAN Services 2.0 (version
281) with IBM 32 Bit OS/2 driver 6.167.
INDBC167.DOC Installation instructions and restrictions for use with IBM
Extended Services/2 Database Manager Client feature. �
ESLS6167.DOC
Restrictions and Installation Instructions for
IBM Extended Services for OS/2 (Driver Level S1A246)
and
IBM OS/2 LAN Server V2.0 (Driver Level 281)
on
IBM OS/2 Standard Edition V2.0 (Driver Level 6.167)
October 18, 1991 2:16 p.m.
IBM CONFIDENTIAL Extended Services Driver S1A246 & OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver
6.167
This document contains information of a proprietary nature. ALL INFORMATION CONTAINED
HEREIN SHALL BE KEPT IN CONFIDENCE. None of this information herein shall be divulged to
persons other than IBM employees authorized by the nature of their duties to receive such information, or
individuals or organizations who are authorized in writing in accordance with existing policy regarding release
of company information. This material, if exported from the United States, is shipped under General
License GTDR.
Restrictions and Installation Instructions for
IBM Extended Services for OS/2 (Driver Level S1A246)
and
IBM OS/2 LAN Server V2.0 (Driver Level 281)
on
IBM OS/2 Standard Edition V2.0 (Driver Level 6.167)
October 18, 1991 2:16 p.m.
IBM CONFIDENTIAL Extended Services Driver S1A246 & OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver
6.167
IBM CONFIDENTIAL Extended Services Driver S1A246 ii OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.0 System Requirements and Performance ............... . . . . . . . 3
2.1 Memory and Fixed-Disk.Requirements . . . . . . . ............. 3
2.2 Extended Services.Performance. ........... . . . . . . . . . . . . . 4
2.3 LAN Server/Requester.Performance. ........... . . . . . . . . . . 4
3.0 New and Enhanced.Function ... . . . . . . . . . ......... . . . . . . 6
3.1 New and Enhanced Function in Communications Manager .. . . . . . . . . 6
3.2 New and Enhanced Function in Database Manager ............ . . 7
3.3 New and Enhanced Function in.LAN.Server 2.0 . . ........... . 8
4.0 Quick Glance - Fixes in this.Driver ....... . . . . . . . . . . . . . . . 10
4.1 Fixes in Communications.Manager. . . ....... . . . . . . . . . .. . 10
4.2 Fixes in Database Manager ............. . . . . . . . . . . . . . . 16
4.3 Fixes in LAN Services. . . . . . ........... . . . . . . . . . . . . . 19
5.0 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.1 General Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.2 Extended Services Restrictions. . . . . . . ............. . . . . . . 20
5.3 Communications Manager.Restrictions . ............. . . . . . . 21
5.4 Database Manager Restrictions. . . . . . . ............. . . . . . 25
5.5 LAN Server Version 2.0 Hardware.Restrictions ... . . . . . . . . . . . . 28
5.6 LAN Server Version 2.0 Server.Restrictions ... . . . . . . . . . . . . . . 29
5.7 LAN Server Version 2.0 Requester Restrictions. . . . . . . . . . . . . . . . 34
5.8 LAN Server Version 2.0 Publications Restrictions. . . . . . . . . . . . . . 37
6.0 Extended Services Installation. . . . . . . ............. . . . . . . 38
6.1 Before You Install Extended.Services ..... . . . . . ......... . . 38
6.2 Extended Services Installation Concepts. . . . . . . . .......... . . 40
6.3 Basic Configuration Services (BCS) ............... . . . . . . . . 41
6.4 Advanced Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.5 Custom Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.6 Applying Patches to the Installed System. . . . . . . . ........ . . . 44
7.0 Installing Communications Manager ............... . . . . . . . . 47
7.1 Before You Install Communications Manager ................. 47
7.2 Installation Instructions for Communications Manager .... . . . . . . . 49
7.3 Re-installation of Communications Manager ................. 52
7.4 Communications Manager Installation Notes ................. 52
7.5 ROP Service and SPA Router Installation.Instructions .... . . . . . . 53
8.0 Installing Database Manager ............. . . . . . . . . . . . . . . 55
8.1 Before You Install Database Manager ............... . . . . . . 55
8.2 Database Manager Installation Examples. . . . . . . . ........ . . . 56
9.0 Installing OS/2 LAN.Requester. . ......... . . . ... . . . . . . . 65
9.1 Basic Installation for OS/2 LAN Requester ................. . 65
Contents ii
IBM CONFIDENTIAL Extended Services Driver S1A246 iii OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
9.2 Advanced Installation for OS/2 LAN Requester .............. . 65
9.3 Reinstalling, Reconfiguring.or Removing. . ........... . . . . . 65
10.0 Installing OS/2.LAN.Server . . ....... . . . . . . ... . . . . . . . 66
10.1 Basic Installation for OS/2 LAN Server. . . . . . . . .......... . . 66
10.2 Advanced Installation for OS/2.LAN.Server ..... . ....... . . 66
10.3 LAN Server 1.3 Migration Utility ............... . . . . . . . . 66
11.0 Installing IBM LAN Support Program and.DOS.LAN.Requester . . 67
11.1 Installing the IBM LAN Support.Program, V.1.21. ........ . . . 67
11.2 Installing DOS LAN.Requester. . ......... . . . ... . . . . . . 67
Appendix A. SNA Advanced Configuration . . . . . . . . ............ . 69
A.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
A.2 Advanced Configuration for 5250. ............. . . . . . . . . . . 70
A.3 Advanced Configuration for 3270.Over Token-Ring. ........ . . . 76
A.4 Advanced Configuration for 3270.Gateway. . . . ....... . . . . . . 79
Appendix B. EHLLAPI Virtual Device.Driver (VDD) ... . . . . . . . . . . 83
B.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
B.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
B.3 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
B.4 Compatability (With Personal Communications 3270.2.0) . . . . . . . . 84
Appendix C. Communications Manager Stop.API. ........... . . . . 89
C.1 Overview and Usage ........... . . . . . . . . . . . . . . . . . . . . 89
Contents iii
IBM CONFIDENTIAL Extended Services Driver S1A246 1 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
1.0 Introduction
This document provides the basic installation instructions for the IBM Extended
Services for OS/2 (Extended Services) and LAN Server (LS) V2.0 driver. For
additional information on installing these products, please refer to the Workstation
Install Guide publication for Extended Services and the LAN 2.0 Network
Administrator Reference Volume 1 publication for LS.
The Extended Services and LAN Server V2.0 driver consists of: ( 3 1/2" format):
- 8 Extended Services diskettes
- 2 patch diskettes
- 2 OS/2 LAN Server V2.0 diskettes
- 3 OS/2 LAN Requester V2.0 diskettes
- 1 OS/2 LAN Network Device Drivers diskette
- 1 OS/2 LAN Migration Utility V1.3 diskette
- 3 DOS LAN Requester diskettes
- 1 PC LAN Support Program diskette
The patch diskettes contain patches for Extended Services.
# Note:
# OS/2 LAN Server driver 281 and Alternate Diskette 1 for Extended Services driver
# S1A246 are required for use with SE 2.0 driver 6.167. The Alternate Diskette 1 for
# Extended Services must be used as a replacement for the Diskette 1 in the original
# Extended Services driver S1A246. This Alternate Diskette 1 must be used during
# initial Extended Services installation.
The entire Extended Services installation procedure starts with Diskette 1 of the
Extended Services diskettes. You will be guided to insert program diskettes 1
through n, depending on your system requirements. The CONFIG.SYS file is
updated automatically during the Extended Services installation process.
The installation of OS/2 Communications Manager, OS/2 Database Manager and
OS/2 LAN Server assumes that you have already installed the appropriate OS/2
base operating system, or that you already have EE 1.30.1 installed.
For a 16-bit base, SE V1.3 manufacturing refresh 1.30.1 is required. For a 32-bit
base, SE V2.0 driver level 6.167 is required.
# NOTE
# Although, these drivers will run on either a SE 16-bit base or a 32-bit base, this
# document was primarily written from a 32-bit installation and execution
# perspective. Thus, there may be slight differences when running in a 16-bit
# environment.
# Throughout this document, a revision code of # in the left margin denotes changes
# from the previous Restrictions and Installation document for Extended Services and
# OS/2 LAN Server running on SE 2.0 level 6.605.
Introduction 1
IBM CONFIDENTIAL Extended Services Driver S1A246 2 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Introduction 2
IBM CONFIDENTIAL Extended Services Driver S1A246 3 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
2.0 System Requirements and Performance
The following sections identify performance characteristics of these drivers.
2.1 Memory and Fixed-Disk Requirements
NOTE: THIS INFORMATION ONLY PERTAINS TO THESE DRIVERS, AND
IS SUBJECT TO SIGNIFICANT CHANGE IN THE FUTURE!
For OS/2 Standard Edition V 1.30.1, a base partition of 20MB is needed. This
partition must hold this SE base, swappper.dat file, and the Extended Services and
LAN Server V2.0 files that are installed in the boot partition.
# For OS/2 Standard Edition 2.0, the base partition should be no smaller than 40MB.
# This is to contain both the SE base and the common files used by Extended
# Services and LAN Server (files that are always installed in the boot partition), and
# to give some room for future expansion.
# In addition to the disk space required for the appropriate Standard Edition base, the
# minimum disk space used by Extended Services or LAN Server is 12MB. However,
# depending on the Extended Services and LAN Server features that are actually
# configured and installed, up to 32MB of disk space may be used by Extended
# Services and LS.
The memory requirements of the OS/2 base operating system depend upon which
version of the operating system is used and which features of the OS/2 base system
are concurrently used. The MINIMUM memory requirement for the OS/2 SE
Version 1.30.1 product is 2 MB. The MINIMUM memory requirement for OS/2
SE Version 2.0 is 4 MB.
For these drivers, the minimum RAM for Extended Services or LAN Server, in
ADDITION to the base operating system requirement, is 1MB.
In addition to the memory required by the base operating system, Extended Services
and LAN Server, the user should allow additional memory to be used by whatever
user applications that are concurrently executed. In general terms, small OS/2
applications (for example, WordPerfect or Excel) typically require about 1 MB of
memory while large OS/2 applications (for example, DeScribe or Lotus 123/G) need
2-3 MB of memory.
We continue to work to improve the disk and memory usage of the SE, Extended
Services, and LS products. The numbers above may not reflect the actual disk and
memory requirements of the final product.
These drivers are NOT suitable to be used as a benchmarking platform.
Performance improvements continue to be made and the performance of this early
code may not represent the performance of the final product.
System Requirements and Performance 3
IBM CONFIDENTIAL Extended Services Driver S1A246 4 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
More complete information regarding the disk and memory requirements for
Extended Services, LAN Server, and OS/2 SE Version 2.0 will be made available at
general availability.
2.2 Extended Services Performance
Performance evaluation is ongoing; and performance is expected to improve over
time. This level of code, however, may not accurately represent, in your
environment, the performance of the final product. It is therefore
RECOMMENDED that this level of code NOT be used for performance
benchmarking and evaluation.
2.3 LAN Server/Requester Performance
2.3.1 Performance Considerations
When using this driver of LS 2.0, you may notice very significant improvements or
some degradation from LS 1.3 depending on your particular environment and/or
application. Some of these situations are described below. For the environments in
which OS/2 1.3 requesters are upgraded to OS/2 2.0, the descriptions assume
sufficient memory in the requesters to avoid swapping during application execution.
Note: We recommend that you do not use this driver level of code for performance
benchmarking or evaluation.
Environment 1
Upgrading LS 1.3 servers to LS 2.0 but not upgrading the requester's operating
system from OS/2 1.3 to 2.0. Also includes DLR requesters with or without upgrade
to DLR 2.0.
LS 2.0 Advanced Version
? LS 2.0 Advanced performs up to 2 times faster than LS 1.3 for most HPFS file
I/O operations, including application loading, for both DLR and OS/2
requesters. The result is both shorter response times seen by the user and greater
throughput capacity of the server.
LS 2.0 Entry Version
? The performance will be about the same as LS 1.3.
Environment 2
Upgrading OS/2 requesters to OS/2 2.0 but not upgrading the server to LS 2.0 from
LS 1.3.
Application Loading Across LAN: Currently, OS/2 2.0 application load times
across the LAN are slower than when using OS/2 1.3 as the requester operating
system. This is related to OS/2 2.0 loader performance. Application loading from
the DOS session is about the same as OS/2 1.3.
System Requirements and Performance 4
IBM CONFIDENTIAL Extended Services Driver S1A246 5 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
File I/O Performance Across LAN: OS/2 file I/O performance is slightly slower
with OS/2 2.0 than 1.3 but is not perceivable in many environments. This is a
known problem and improvements will be made. DOS session I/O performance of
OS/2 2.0 has noticeably improved performance over 1.3 for many types of I/O
operations.
Environment 3
Upgrading OS/2 requesters with OS/2 2.0 and also upgrading LS 1.3 servers with LS
2.0.
LS 2.0 Advanced Version
? Performance will be similar to that of the Environment 1 Advanced version but
OS/2 application loading will be somewhat slower.
LS 2.0 Entry Version
? The performance will be about the same as LS 1.3.
System Requirements and Performance 5
IBM CONFIDENTIAL Extended Services Driver S1A246 6 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
3.0 New and Enhanced Function
The following sections identify the function available in this driver.
3.1 New and Enhanced Function in Communications Manager
Following is a list of the new or enhanced functions that will be available in this
driver for Extended Services Communications Manager. This list is NOT intended
to include ALL functions that will be available in the final product.
Note
Please be aware that there may be restrictions/limitations that apply to some of
these functions for this driver. Please BE SURE to refer to 5.3,
﨏ommunications Manager Restrictions?on page 21 for information about
these restrictions.
?
Advanced Peer-to-Peer Networking (APPN) Support
? Modification of the LAN Transport layer to improve performance across
supported LANS
? Enabling support for industry standard NDIS interface
? Programmable Configuration allowing REXX interface to the configuration file
? 3174 Peer Communication enabling
? EHLLAPI extensions including multiple simultaneous application access and
support for structured fields low level verbs
? ACDI extension allowing API to re-direct ACDI output (in addition to
command line)
? 370 Netview Remote Operations allow OS/2 commands from the Netview
operator, REXX, and CLIST
?
New LU pooling algorithm to allocate session when requested, not as
configured
? Persistent Verification: reduced ID exchanges for LU6.2 (W/S to host)
? File Transfer support for long file names
? 3270 Jump key
? Optionally installable Communications Manager Utilities
? Configuration File Manager to simplify the administration of configuration files
? Increased number of workstations for SNA Gateway support
? 5250 in a PM text window as default
? Migration path from EE 1.30.1
New and Enhanced Function 6
IBM CONFIDENTIAL Extended Services Driver S1A246 7 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? Auto-reactivate DLC after adapter failure
? REXX EHLLAPI interface (for information, see RXHLLAPI.DOC in
\CMLIB)
?
DOS session interface to EHLLAPI (for information, see Appendix)
? CM Stop API (for information, see Appendix)
? Command line upgrade function for upgrading configuration files
3.2 New and Enhanced Function in Database Manager
Following is a list of the new or enhanced functions for Extended Services for OS/2
Database Manager that are available in this driver. The list is NOT intended to
include ALL functions that will be available in the final product.
Note
Please be aware that there may be restrictions/limitations that apply to some of
these functions for this driver. Please BE SURE to refer to 5.4, 﨑atabase
Manager Restrictions?on page 25 for information about these restrictions.
? Roll Forward Recovery (except for User Exits)
?
DOS Windows Client Support
?
Database Manageability Tools
?Configuration Tool
?Recovery Tool
?Directory Tool
? Database Manager Command Line Interface
? Protocols for Extended Services
?Database server support for Extended Services clients using NETBIOS,
APPC and APPN protocols
?Database server support for EE 1.2/1.3 OS/2 clients using SQLLOO
? Reliability, Availability, Serviceability and Trace
?Independent Trace Facility (ITF)
?First Failure Support Technology/2 (FFST/2) support
? Translate Function
? SQLSTATE
? User Defined Collate Sequence
? Database Client with Local Databases
? Standards Compliance: SAA and MIA
?SQL Date/Time/Timestamp Arithmetic
New and Enhanced Function 7
IBM CONFIDENTIAL Extended Services Driver S1A246 8 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
?Packages
?Multivendor Integration Architecture (MIA) Version 1 implementation
3.2.1 Design Changes from Previous Database Manager Releases
Please note that the following design changes have been made to Database Manager
in IBM Extended Services for OS/2
? You cannot create a database on a diskette, except on a Standalone Database
Manager workstation.
? APPC/APPN will NOT issue a STARTDBM (as APPC formerly did with EE
1.3). You must issue a STARTDBM at the database server before any database
clients can connect to a database.
3.3 New and Enhanced Function in LAN Server 2.0
Following is a list of the new or enhanced functions for OS/2 LAN Server 2.0 that
are available in this driver. The list is NOT intended to include ALL functions that
will be available in the final product.
Note
Please be aware that there may be restrictions/limitations that apply to some of
these functions for this driver. Please BE SURE to refer to 5.6, 﨤AN Server
Version 2.0 Server Restrictions?on page 29 and 5.7, 﨤AN Server Version 2.0
Requester Restrictions?on page 34 for information about these restrictions.
Reorganized/Improved Publications
PM Hypertext Based OnLine Reference
PM Based Graphical Install
386 High-Performance File System
Local Security for 386 HPFS
Fault Tolerance
? UPS Support
? Disk Mirroring and Duplexing
Support for Multiple LAN Adapters
NDIS Support - (Network Device Interface Specifications)
IBM Token Ring Busmaster/A Support
Remote IPL Enhancements
New and Enhanced Function 8
IBM CONFIDENTIAL Extended Services Driver S1A246 9 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? Remote IPL of DOS or 1.3 OS/2 Workstations
? Ethernet (DOS and OS/2 1.3 Requesters)
DOS LAN Requester Enhancements
? Enhanced Windows 3.0 Support
?
DBCS Command Line Support
? DBCS Printer Support
? DOS 5.0 Compatibilty
Operator Priveleges
Time Source Service
Logon Enhancements
?
Fault Tolerant Logon Capability
? Backup Logon
? Logon From Multiple Workstations
Generic Alerter Service
First Failure Support Technology/2 (FFST/2)
LAN Over Coax
New and Enhanced Function 9
IBM CONFIDENTIAL Extended Services Driver S1A246 10 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
4.0 Quick Glance - Fixes in this Driver
The following sections identify fixes (to previous driver restrictions) that have been
incorporated into this driver.
4.1 Fixes in Communications Manager
? INSTALLATION AND CONFIGURATION
FIXED
If you are installing IBM Extended Services for OS/2 with the SE 2.0
operating system, you must take the following step after installing SE 2.0
and before installing IBM Extended Services for OS/2. You should copy the
file ABIOS.SYS from the \OS2 directory to the root directory of the logical
drive on which OS/2 is installed.
FIXED
If you plan to install Communications Manager through Advanced
Installation with the default configuration file ACSCFG.CFG, you MUST
select BOTH ACSCFG and ACSCFGUS from the Default Configuration
File menu during initial installation. If you select only ACSCFG,
installation will fail.
FIXED
If you have the Networking Services/2 product installed on your workstation
and you are planning to install IBM Extended Services for OS/2 on that
workstation with Standard Edition version 1.3 at the refresh level 1.30.1, you
should reformat your partition during the installation of Standard Edition.
FIXED
Basic Configuration Services should not be used to create a 5250 WSF
configuration file during initial installation. Instead, Advanced Installation
should be used to install a User Defined 5250 configuration file.
FIXED
The Install/Remove function to Remove Communications Manager (CM)
may not remove all the Communications Manager files from the system.
RESTRICTION
An initial IBM Extended Services for OS/2 installation using A:ESINST
cannot be followed by a second A:ESINST without reformatting and
reinstalling the base operating system. If additional features need to be
installed after the initial installation, the REINST command should be used.
Quick Glance - Fixes in this Driver 10
IBM CONFIDENTIAL Extended Services Driver S1A246 11 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
FIXED
After verifying a configuration file, you may see the following message in the
message log even though the configuration file verified without errors. This
message should be ignored.
The Communications Manager configuration does not start the SNA
support. Change and re-verify the Communications Manager configuration.
RESTRICTION
After you complete steps for installation of Communications Manager, you
are instructed to stop active features and press CTRL-ALT-DEL to reboot
the system. Instead of pressing CTRL-ALT-DEL, you should use the
DESKTOP Shutdown to stop the system if you have formatted your
hardfile using the High Performance File System (HPFS).
? INSTALLATION AND OPERATION OF CM WITH LAN SERVER (LS)
RESTRICTION
If you are planning to use both IBM Extended Services for OS/2 and LS,
you should install IBM Extended Services for OS/2 FIRST. When you
install Extended Services, you should select to install the LAN Adapter and
Protocol Support from Additional Features in Communications Manager
Advanced Installation (if it is not already installed based on a configuration
file you have selected).
FIXED
A NET START REQUESTER may fail if a NETBIOS application is
started at the same time. If this occurs, you should restart the requester.
? CUSTOM BUILD AND CUSTOM INSTALLATION
FIXED
Limited testing has been done with the Custom build and custom
installation feature.
FIXED
Custom build and custom installation should not be used for a configuration
file containing ACDI parameters.
FIXED
Custom build and custom installation should not be used for configurations
containing APPC/APPN parameters.
Quick Glance - Fixes in this Driver 11
IBM CONFIDENTIAL Extended Services Driver S1A246 12 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
FIXED
Custom build and custom installation does not function correctly to install
LAN for a configuration file with ACDI redirection.
After a custom build and custom installation, the Basic Configuratio n
Services (ESCFG command) is not accessible.
? PROGRAMMABLE CONFIGURATION
FIXED
The APPN feature of Programmable Configuration is not functioning in this
driver and should not be used.
? CONFIGURATION UPGRADE
FIXED
Limited testing has been done with the Configuration Upgrade and
installation with pre-existing Extended Edition configuration files to be
upgraded. Upgrade of Extended Edition 1.2 or 1.3 configuration files for
3270 or ASYNC should work correctly. You should not attempt to upgrade
a configuration file which contains combinations of other features with 3270
or ASYNC.
FIXED
Configuration Upgrade should not be used to upgrade EE 1.0 and EE 1.1
configuration files. For this first driver, advanced configuration should be
used to build the files rather than upgrading from the old EE 1.0 or 1.1 file.
FIXED
Communications Manager configuration files containing Database Remote
Data Services features cannot be upgraded.
FIXED
Communications Manager configuration files containing LAN Requester
cannot be upgraded.
FIXED
An Extended Edition 1.2 or 1.3 level configuration file cannot be upgraded if
it contains 3270 DFT and 3270 non-DFT with more than one session for
DFT or non-DFT.
FIXED
EE 1.2 and 1.3 configuration files containing only NETBIOS parameters
cannot be upgraded in this first driver.
Quick Glance - Fixes in this Driver 12
IBM CONFIDENTIAL Extended Services Driver S1A246 13 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
FIXED
EE 1.2 and 1.3 configuration files with APPC Transaction Program
parameters should not be upgraded in this first driver.
FIXED
Configuration upgrade should not be used to upgrade more than one EE 1.2
or EE 1.3 configuration file during installation.
FIXED
5250 WSF configuration files do not upgrade correctly.
FIXED
REINST should not be used to install an upgraded configuration file which
is stored in \CMLIB.
? SDLC CONNECTIVITY
FIXED
Intermittent TRAP D errors may occur with the SDLC connectivity.
? 3270 TERMINAL EMULATION
FIXED
The 3270 terminal emulator should not be restarted after selecting to stop
specific emulator sessions or a software error will occur. You should be able
to stop 3270 emulation and restart it without problems if you select to stop
ALL sessions.
? 3270 HOST GRAPHICS
FIXED
When running on the OS/2 2.0 operating system, host graphics files can be
printed or plotted only when using the PR option from the GDDM
directory panel.
RESTRICTION
When running on the OS/2 2.0 operating system, the PF5=SAVE PIF
option under the GDDM output function is not working correctly.
? SNA GATEWAY
Quick Glance - Fixes in this Driver 13
IBM CONFIDENTIAL Extended Services Driver S1A246 14 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
FIXED
If the SNA Gateway has a LAN connection to the host or to its attached
workstations, the gateway may hang when logging off the last workstation.
To avoid this problem, the FREE UNUSED LINKS parameter in the DLC
profile (accessed from CM Advanced Configuration SNA Feature Profiles)
should be set to NO on your SNA Gateway.
? DMA ASYNC
RESTRICTION
The DMA Async support for line speeds up to 64Kbps is not functioning
correctly on the PS/2 Model 90 and Model 95. If you are using a PS/2
Model 90 or 95 with ASCII emulation or ACDI redirection, you can still
use line speeds up to 19.2 Kbps. You should add a REM statement to your
CONFIG.SYS as follows. In this statement, d is the logical drive on which
Communications Manager is installed.
REM DEVICE=d:\CMLIB\ASYNCDDC.SYS
?
5250 WORKSTATION FEATURE (WSF)
FIXED
Basic Configuration Services (ESCFG command) should not be used to
create a 5250 WSF configuration file. Instead Advanced Configuration
should be used.
FIXED
When configuring 5250 WSF session assignments, red warning panels will be
displayed indicating that the APPC partner LU alias and the APPC mode
name do not exist. You will be asked if you want to continue. Select YES.
If you have configured these parameters, they do exist even though the
warning indicates that they do not.
FIXED
To use 5250 WSF with the auto sign-on feature, the LU name and the LU
alias name should be configured to match.
FIXED
The F4=LIST function from the 5250 Session profiles does not provide a
list of the mode and partner LU profiles.
FIXED
When using the twinax connectivity for 5250 Workstation Feature, only one
twinax attached workstation can access the AS/400 at a time. This occurs
because every twinax workstation connects to the AS/400 with a PU name
of PU00000.
Quick Glance - Fixes in this Driver 14
IBM CONFIDENTIAL Extended Services Driver S1A246 15 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
FIXED
Using the SE 2.0 operating system, 5250 fails to stop when it is selected to
be stopped from Communications Manager main menu. You should not
attempt to stop 5250 WSF if there are other Communications Manager
features running on the system. If you do attempt to stop 5250 WSF, you
should not attempt to restart 5250, or the other features running on the
system will be brought down. Your host line may need to be varied off and
back on after this scenario.
? LAN ADAPTER AND PROTOCOL SUPPORT
RESTRICTION
When using the IBM Token Ring 16/4 Adapter or the IBM Token Ring
16/4 adapter /A, and the adapter is set for 64K paged, a user application
cannot take advantage of the 64K.
FIXED
"Universally administered address reversed" is now a configuration option for
NETBIOS in the NETBEUI section of PROTOCOL.INI. For this first
driver, this option will not be operational.
FIXED
If you are writing NETBIOS applications, you may find that the return code
from NETBIOS in the AX register is not always correct. For this first
driver, you should rely on the NETBIOS return code in the NCB rather
than that in AX.
FIXED
The following statement should be added to the bottom of the CONFIG.
SYS to start the service required for LAN Adapter and Protocol Support
error handling. In this statement, d is the logical drive on which the OS2
operating system is installed.
RUN=d:\OS2\EPW.EXE
?
APPN
FIXED
The APPN function of routing traffic through an intermediate node is not
functioning correctly.
FIXED
The APPN messages in this driver are in a format such that the message
itself contains both the message and the help text. Therefore, if you choose
to view the help, you will get an indication that the help is not available. All
the information needed is contained in the message text itself.
Quick Glance - Fixes in this Driver 15
IBM CONFIDENTIAL Extended Services Driver S1A246 16 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? ACDI REDIRECTION API
FIXED
The MASM API data structure for ACDI Redirection API is incorrectly
named as REDIRECT.INT. You should rename this file to
REDIRECT.INC. This file is found in \CMLIB if you have selected to
install the API Data Structures.
? EHLLAPI
FIXED
The 5250 EHLLAPI TWAIT option on Set Session Parameters acts like an
LWAIT. It does not time out after the first minute.
?
REMOTE OPERATIONS (ROP) SERVICE
FIXED
For Remote Operations, an extra unwanted ICON and entry in the Task
List for ROP KERNEL is displayed. Neither the ICON nor the Task List
entry should be accessed.
FIXED
The ROP Service may not always start after initially starting the system or
after CTRL-ALT-DEL to reboot the system. If this problem occurs on
your system, you should select to start ROP Service again. It should start
correctly the second time.
FIXED FOR SE 2.0 ONLY
Occasionally the CTRL-ALT-DEL and Desktop shutdown may fail to
work after running ROP Service for an extended period of time. In this
case, the PC must be powered off. This can cause a significant delay in
startup when the PC is restarted.
? SUBSYSTEM MANAGEMENT
FIXED
The subsystem management functions to display class of service and
topology for the active configuration file are not working correctly.
4.2 Fixes in Database Manager
The following table shows what has been fixed and what has not been fixed since
the previous driver.
Quick Glance - Fixes in this Driver 16
IBM CONFIDENTIAL Extended Services Driver S1A246 17 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Table 1 (Page 1 of 2). Database Manager Fixes Since Previous Driver
Problem SE 1.30.1 or SE Status
2.0
Install SE 2.0 only Fixed
Musical notes may appear on screen during
the 'Transferring files...' message. No impact
to install.
Install SE 2.0 only Fixed
After Database Manager is installed, during
IPL the system message SYS1195 appears on
the screen. The message reads "The command
"SYSLOG" on line xx of the CONFIG.SYS
file is not recognized. Line xx is ignored."
Install Both Fixed
Database Manager messages are properly
installed, but no entry exists in Group Main.
(This applies to Standalone DBM only)
Create Database Both Fixed
After creating a new database with Extended
Services, change the following database
configuration parameters for that database:
? Log file size (# of 4K pages): change from
32 to 50
? Auto-restart: change from 'YES' to 'NO'
Backup/Restore SE 2.0 only Fixed
You can backup the 'Entire database' ONLY
(you CANNOT do a 'Changes Only'
backup).
Reinstallation (REINST) SE 2.0 only Fixed
Removal/reinstallation of Database Manager
components is unpredictable. If the user must
remove or reinstall components with this
driver, a disk format and a full install of the
operating system and Extended Services may
be required.
Reinstallation (REINST) Both Fixed
During a reinstallation, the system may
erroneously detect that a previous version of
Database Manager is installed. If you get the
Remove Previous Version of Selected
Component screen, select 'Remove Previous
Version' and the install should complete
normally.
Quick Glance - Fixes in this Driver 17
IBM CONFIDENTIAL Extended Services Driver S1A246 18 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Table 1 (Page 2 of 2). Database Manager Fixes Since Previous Driver
Problem SE 1.30.1 or SE Status
2.0
Command Line Interface does NOT work SE 2.0 only Fixed
Command Line Interface SE 1.30.1 only Fixed
? Cannot be run from the Desktop
? AUTOCOMMIT (the default) is not
working. The user will need to perform
commits ('dbm commit') manually.
? REORGCHK is not working.
? Message 'DBM.MSG file can't be found'
appears after normal completion
Install is failing to add x:\sqllib to
DPATH= statement of config.sys (where
x is the drive DBM is installed on).
Workaround is to add x:\sqllib to
DPATH= statement of config.sys
manually.
REXX Interfaces to Database Manager SE 2.0 only Fixed
If the user experiences difficulty with a REXX
application, the application should be
re-tokenized.
Independent Trace Facility (ITF) Both Fixed
The mask (-m) option is not working. If the
mask is used, the trace buffer will be empty.
Be aware that the mask option is invoked in
two ways. Neither one of these is working:
1. By starting trace using 'trc on
<options>' where one of the options is
-m (mask).
2. By starting trace with simply 'trc'.
This method of starting trace gives you a
full-screen menu of selectable options. If
you select any of the Products, Events or
Components this will also set a mask, and
the trace buffer will be empty.
Log Full Condition (SQL0964)Both Fixed
SQL0964 (DBM log full condition) received,
even though periodic 'commits' are being
done.
Quick Glance - Fixes in this Driver 18
IBM CONFIDENTIAL Extended Services Driver S1A246 19 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
4.3 Fixes in LAN Services
# NOTE TO OUR CUSTOMERS
# Since this is a new driver for LAN Server, it is highly recommended that you
# upgrade your system from the 274 LS driver to the 281 LS driver.
# Please note that the following are NO longer restrictions in the 281 LS driver:
#
FIXED
# Under Restrictions and Special Considerations for API's: The new 32 bit
# DosFindFirst() /DosFindNext() calls will not work properly on a network drive
#
FIXED
# Under Install/Config for the Server:
?
# If the requester is already installed on a workstation, the server cannot be
# installed. To install a server, remove the requester first.
# ? LAN Services cannot be moved to another drive, if already installed on a
# different fixed disk drive.
# FIXED
# Under Install/Config for the Requester:
# ? LAN Services cannot be moved to another drive, if already installed on a
# different fixed disk drive.
# ? Do not install the Loop Back Driver support.
#
FIXED
# Under Generic Alerter Services for the Server: The problem of the
# SYSLEVEL.SRV file not always being located in the :\IBMLAN subdirectory.
Quick Glance - Fixes in this Driver 19
IBM CONFIDENTIAL Extended Services Driver S1A246 20 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
5.0 Restrictions
The following sections identify inconsistencies, restrictions, and problems that we
are aware of in this driver. Our development groups are currently addressing these.
5.1 General Restrictions
You must install Extended Services before you install any components of LAN
Server V2.0. In addition, you must apply any Extended Services patches prior to
any installation of LAN Server V2.0 components.
Note
If you plan to install both Extended Services Database Manager and any
components of LAN Server V2.0, please BE SURE to read the Database
Manager restriction in 5.4.2, estrictions for Functions/Features Available in
this Driver?on page 25 under "Database Copy Protection".
5.2 Extended Services Restrictions
? INSTALLATION AND CONFIGURATION
?If you are planning to install this driver over the SE 1.30.1 or SE 2.0 base
operating system, you must reformat your boot partition and re-install your
base operating system. You must also follow the directions to remove
Extended Services code from any previous driver by following the
instructions in 6.1, 﨎efore You Install Extended Services?on page 38.
?After following instructions in 6.1, 﨎efore You Install Extended Services?
on page 38, the first installation of this driver is initiated with the
A:ESINST. The initial A:ESINST to install this driver cannot be followed
by a second A:ESINST without reformatting and reinstalling the base
operating system. If your initial installation fails for some reason, and you
must issue another A:ESINST, you may be able to perform the A:ESINST
again by taking the following steps.
? For the following files, issue ATTRIB filename -R, and then erase the
file.
? in the root directory of the boot drive, IBMLVL.INI
? in \MUGLIB, SYSLEVEL.MUG
? in \OS2\INSTALL, ESINST.HST
?COPY x:\OS2\INSTALL\CONFIG.ES x:\CONFIG.SYS, where x is
the logical drive letter for the boot drive
?Press CTRL-ALT-DEL to reboot the PC
?After you complete steps for installation of Communications Manager, you
are instructed to stop active features and press CTRL-ALT-DEL to reboot
Restrictions 20
IBM CONFIDENTIAL Extended Services Driver S1A246 21 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
the system. Instead of pressing CTRL-ALT-DEL, you should use
Shutdown to stop the system. To do so, bring up a menu by pressing the
right mouse button while the pointer is not on any object (i.e on blank
space) on the workplace desktop. Then select Shutdown from the menu to
stop the system and reboot again.
? If you have installed Communications Manager with a feature that requires
APPC/APPN support and you receive the following message, you should
use the REINST command to re-install the Communications Manager
configuration file for the feature. The re-installation will cause your
CONFIG.SYS to be updated correctly.
ACS0112C - Communications Manager - Originator APPC - Critical file
CONFIG.SYS(DEVICE=C:\CMLIB\APPN\CMKFMDD.SYS) was not
found or was modified or damaged: error type 0002.
# ?Multiple Communications Manager ICONs will be installed on the
# workplace desktop with this OS/2 2.0 driver. Duplicates can be ignored.
# ?With this OS/2 2.0 driver, the ICONs in the Communications Manager
# group, Database Manager group, and Extended Services group will run
# together. To arrange them so that the lettering is legible, you can click with
# the right mouse button on a blank area of the grouping and select Arrange
# from the menu which displays.
? REQUIREMENT TO EXIT CM BEFORE STOPPING THE SYSTEM
?If you have entered the Communications Manager Subsystem Management
or Advanced Configuration panels you MUST always select to Exit
Communications Manager before attempting a Desktop Shutdown or
CTRL-ALT-DEL. If you do not exit Communications Manager,
CTRL-ALT-DEL and Shutdown may be disabled.
In some cases, you may experience a trap d when exiting Communications
Manager with either the Exit when Complete or Exit Immediately options.
If the CSLIM is 1bffffff, this is a known problem. You can hit enter to
continue the exit process.
5.3 Communications Manager Restrictions
# ? COMMUNICATIONS MANAGER PANELS AND OPERATION WITH
# A MOUSE
# ?With the OS/2 2.0 operating system, the mouse may be inoperable on some
# of the Communications Manager panels. The keyboard may be used to
# select options. For example, to go to the CM Configuration panels, press
# F10 from the CM main menu and select Advanced and then select
# Configuration.
? PROGRAMMABLE CONFIGURATION
?If you plan to use the APPN functions of Programmable Configuration,
you MUST install the patches as described in 6.0, 﨓xtended Services
Installation?on page 38.
?If you plan to use Programmable Configuration, you should always change
the directory to \CMLIB prior to executing your Programmable
Restrictions 21
IBM CONFIDENTIAL Extended Services Driver S1A246 22 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Configuration program. If you do not change to the \CMLIB directory,
your configuration file may not verify correctly, or you may receive errors
for files not found.
?The APPN feature of Programmable Configuration should not be used to
perform LIST and GET, but may be used to perform ADD and PUT.
? FUNCTIONS INVOLVING APPC/APPN SUPPORT
?If you plan to use a Communications Manager function which requires
APPC/APPN support (e.g. 5250 WSF, 3270 emulation over SDLC or
Token ring, APPC, CPI-C, SNA Gateway), you MUST install the patches
as described in 6.0, 﨓xtended Services Installation?on page 38.
?MIGRATION WARNING. If you you plan to use a Communications
Manager function which requires APPC/APPN support (e.g. 3270
non-DFT, 5250 WSF, APPC, CPI-C, SNA Gateway), you must ensure
that your machine is configured with a unique Fully Qualified CP Name.
This name is created under-the-cover during Extended Services
installation/configuration upgrade based on the Network Name and PU
name in your current configuration file. Be aware that a naming collision
means that you may not be able to establish a 3270 session through an
Extended Services SNA Gateway to a host, be able to establish a 5250
session to an AS/400, or be able to activate a link to another APPN node.
If you encounter these problems after installation, use Advanced
Configuration/SNA Feature Profiles/SNA network definitions/ Local Node
Characteristics to change the Local Node Name to a unique name.
? 5250 WORKSTATION FEATURE
?In order to use the 5250 Workstation Feature in this driver, you MUST
install the patches as described in 6.0, 﨓xtended Services Installation?on
page 38.
? 3270 DFT CONNECTIVITY FOR A PC AT
?In order to use the 3270 DFT connectivity on a PC AT in this driver, you
MUST install the patch for 3270 DFT as described in 6.0, 﨓xtended
Services Installation?on page 38. This patch is NOT required if you are
running on a PS/2.
# ? 3270 EMULATION ON MODEL 95 WITH MULTIPLE ADAPTERS
# ?On OS/2 2.0, when running 3270 emulation, BOTH DFT and non-DFT
# connectivities on a PS/2 Model 95, selecting to stop and restart the
# non-DFT sessions will cause all sessions to go away.
? CONFIGURATION FILE MANAGER
?If you plan to use the Configuration File Manager, you MUST install the
patches required as described in 6.0, 﨓xtended Services Installation?on
page 38.
? 3270 HOST GRAPHICS
?In order to use 3270 Host Graphics with Extended Services, your host
system must have the following PTFs applied. If they are not applied you
may experience problems with clipping, printing and plotting.
Restrictions 22
IBM CONFIDENTIAL Extended Services Driver S1A246 23 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
?For MVS, PTFs UL89380, UN04644
?For VM/SP, PTFs UL89381, UN04645
?For VM/XA SP, PTFs UL89382, UN03715
?For DOS/VSE, PTFs UL89383, UN04646
?When running on the OS/2 2.0 operating system, the PF5=SAVE PIF
option under the GDDM output function is not working correctly. To
work around this problem, you should take the following steps.
?From the OS/2 full screen prompt, type GQFTRACE.
?From the window displayed, select Output from the Action bar and
select File (rather than screen).
?From that same window, select Options and select File Close/Open
mode.
?From your host session, type ADMCHART. You'll receive a pop up,
and you should select All Set.
?At this point, you should be able to select PF5=SAVE PIF.
?
DMA ASYNC
?The DMA Async support for line speeds up to 64Kbps is not functioning
correctly on the PS/2 Model 90 and Model 95. If you are using a PS/2
Model 90 or 95 with ASCII emulation or ACDI, you can still use line
speeds up to 19.2 Kbps. You should add a REM statement to your
CONFIG.SYS as follows.
?REM DEVICE=x:\CMLIB\ASYNCDDC.SYS (where x is the logical
drive on which Communications Manager is installed)
?
LAN ADAPTER AND PROTOCOL SUPPORT
?When using the IBM Token Ring 16/4 Adapter or the IBM Token Ring
16/4 adapter /A, and the adapter is set for 64K paged, a user application
cannot take advantage of the 64K.
? REMOTE OPERATIONS (ROP) SERVICE
?Occasionally the CTRL-ALT-DEL and Desktop shutdown may fail to
work after running ROP Service for an extended period of time on a system
formatted with HPFS running OS/2 SE 1.0. In this case, the PC must be
powered off. This can cause a significant delay in startup when the PC is
restarted.
# ?On OS/2 2.0, ROP service cannot be started by clicking on the Remote
# Operations Icon. Instead, the following steps must be followed to start the
# router and ROP service:
# From an OS/2 full screen command prompt, type the following
# rtr /desktop
# roppm /fullscreen /nologo
# ? EHLLAPI VIRTUAL DEVICE DRIVER (VDD)
Restrictions 23
IBM CONFIDENTIAL Extended Services Driver S1A246 24 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
# ?With this OS/2 2.0 driver, the EHLLAPI Virtual Device Driver MUST not
# be used. Inclusion of the EHLLAPI VDD statement in CONFIG.SYS will
# result in the inability to start any DOS sessions. If the EHLLAPI VDD is
# to be used, it should be used with the OS/2 2.0 driver level 6.605.
# ? ACDI REDIRECTION
# ?With this OS/2 2.0 driver, ACDI Redirection does not function correctly. If
# you are planning to use ACDI redirection, you should use OS/2 2.0 level
# 6.605.
5.3.1 Communication Manager Publications Restrictions
Workstation Installation Guide
The following APPN information is missing:
?
a description of the NS/2 files which may need to be backed-up before you
format your fixed disk at installation;
? installation and upgrade considerations for NS/2;
? the SNA networking defaults used by BCS.
Communication Manager Host Connect Reference
? incomplete APPN (NS/2) examples for the AS/400 chapter
Example Scenarios
? no APPN (NS/2) information.
? 5250 Emulation steps have had minimal testing.
? X.25 steps have had minimal testing.
Network Administrator's Guide
?
There is missing conceptual information and product description.
? The naming conventions are missing several names and details about the names.
? Operating system features are missing from the Operating System steps.
? Several of the Communication Manager steps are missing blanks for recording
information.
? Database steps are missing planning information for Remote Data Services
(RDS) and Distributed Database Connection Services (DDCS).
? The LAN step is missing cross-references to the LAN planning guides.
? The summary Worksheets at the back of the book are incomplete. Please refer
to the full worksheets found in the Workstation Installation Guide, the
Communication Manager Configuration Guide, and the LAN Network
Administrator's Reference Volume 1: Planning and Installation.
Restrictions 24
IBM CONFIDENTIAL Extended Services Driver S1A246 25 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
5.4 Database Manager Restrictions
5.4.1 Functions/Features NOT Available in this Driver
? Advanced Backup/Restore (Backup to non-standard devices)
5.4.2 Restrictions for Functions/Features Available in this Driver
The following restrictions/limitations apply to Database Manager for this driver.
These restrictions will be corrected in future drivers unless otherwise noted.
Migration of EE 1.1, 1.2 and 1.3 Databases
Migration of EE 1.1, 1.2 and 1.3 Databases
Migration of existing EE 1.1, EE 1.2 and EE 1.3 databases IS SUPPORTED in
this driver. Please refer to 8.1.1, 﨧igration of Databases?on page 55 for
information about migration of these databases. Be SURE to backup all
databases BEFORE you install this driver.
Migration of existing Extended Services databases, however, IS NOT
SUPPORTED in this driver. See below, under "Migration of Extended Services
Databases" for information about how to preserve these databases for use with
this driver.
Migration of Extended Services Databases (from previous driver)
Restrictions 25
IBM CONFIDENTIAL Extended Services Driver S1A246 26 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
WARNING
Migration of existing Extended Services databases (from the previous
Extended Services driver) is NOT SUPPORTED in this driver!
BEFORE YOU INSTALL THIS DRIVER, do the following steps if you want
to use existing Extended Services databases:
1. Export all tables and QM objects.
2. Save any view definitions that you will want to use with the new
version of the database.
3. Drop the database.
AFTER YOU INSTALL THIS DRIVER, do the following:
1. Create a new Extended Services database.
2. Import the tables and QM objects.
3. Redefine any views that you want to use.
4. Re-bind any existing access plans that you intend to use.
You will need to export all objects and drop the databases before you install each
new driver. Any updates you make to the databases using early driver code will
be lost unless you export your objects before installing each driver.
Database Copy Protection
If you plan to install any of the LAN Server V2.0 components on the same machine
on which Extended Services is installed, it is STRONGLY URGED that you install
the LAN Server V2.0 component(s) BEFORE you create or migrate any databases
using this Database Manager driver.
If you do create or migrate databases using this driver, and you then want to install
LAN Server V2.0, you MUST turn "Copy Protection" off for these databases
BEFORE you install the LAN component(s). If you do not, you will receive an
SQL5122N error ("Machine Dependent Check") when issuing a Start Using
Database, and the database will be unusable.
You can change this database parameter by using Database Tools, if installed, or the
Command Line Interface.
General Restrictions
? A message indicating a code page conversion error occurs sometimes when a
Start Using Database is issued. This may happen if database has been used
several times. Reboot the system if this occurs.
? If you do a Control-Break during a REORG, a Trap D will occur.
? REXX stored procedures do not work.
Restrictions 26
IBM CONFIDENTIAL Extended Services Driver S1A246 27 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? Using the DBM Alter Table command may cause a looping situation that will
appear as a hang.
? If a process is killed from a client/server, a Trap D will occur.
?
There is no support on a LAN server for redirected disk drives.
? If you get an SQL1084 error, use the message text for message SQL0956.
NETBIOS Restrictions
? When Extended Services and LAN Server are both installed and both running
concurrently, the value set for "maximum names" is lower than needed. Edit the
PROTOCOL.INI file NETBEUI section which will contain the "maximum
names" value. Or select "LAN Adapter and Protocol Support" from the
Communications Manager Advanced Configuration menu. The value should
be changed from 17 to 21. Then reboot.
Remote Data Services Restrictions
# ? Bind problem with EE 1.2/1.3 Database clients using Query Manager
# EE 1.2/1.3 database clients using Query Manager to remotely access a database
# on an Extended Services database server will fail with an SQL0040N error ("An
# error occurred on one or more bind files in list 'QRWSBND4.LST'. The
# following files were not found: "3,3".), the first time the database is accessed.
# Subsequent attempts to open the same database from a 1.2/1.3 client will
# receive an SQL0805N error ("NULLID.QRWS2B" is not found.).
? Remote Data Services heap size on the server is too low. Increase the value
from 2 to at least 3.
? You must issue a STARTDBM at the database server before any database
clients can connect to a database. If you do not, the database client will hang
when attempting to connect to a database.
DOS Database Client/DOS Windows Database Client Restrictions
# ? You CANNOT run any DOS Database client or DOS Windows Database client
# applications in OS/2 's 'DOS Windows Full Screen', 'DOS Window' or 'DOS
# Full Screen' command prompt environments.
? Terminating an application program on a client workstation without issuing a
COMMIT and Stop Using Database may cause the client to hang.
Roll Forward Recovery Restrictions
Roll Forward Recovery has not had sufficient testing at this time to withstand
extensive usage. It is included so that users may get familiar with the interfaces and
function capabilities. If used, please remain within the restrictions below. These
items will be corrected in future drivers.
? In order to do a ROLLFORWARD STOP you must have the log files
available that existed when the backup was taken.
? In most cases, a ROLLFORWARD to a point-in-time will not work correctly.
The ROLLFORWARD should be run to the end of the logs ( time =
9999/12/31-23:59:59)
? The USER EXIT option is not supported.
Restrictions 27
IBM CONFIDENTIAL Extended Services Driver S1A246 28 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? When using the LOG RETAIN option, it is recommended that you increase
the size of the log files (logfilsiz) and the number of log files (logprimary) as
much as possible. A TRAP D may occur after multiple log files have been used.
? BEFORE installing the operating system and Extended Services, the databases
must be backed up. If MIGRATE database fails, the database cannot be used
and will require a RESTORE of your backed up database.
? The logpath cannot be changed after turning the LOG RETAIN option 'ON'.
If a new logpath is desired, change to the new logpath, perform a START
USING DATABASE to activate the configuration change, perform a STOP
USING DATABASE, and then turn the RETAIN option 'ON'.
? You cannot ROLLFORWARD through a CREATE INDEX, DROP
INDEX, CREATE INDEX. It is recommended that no indexes exist when
using ROLLFORWARD.
5.5 LAN Server Version 2.0 Hardware Restrictions
5.5.1 Bridge Considerations
If you intend to run a bridge program on a slow workstation (i.e. IBM PC AT,
Family I), ensure that the parameter server value in the bridge configuration
program is set to No. If the parameter server value is set to Yes, a slow or
congested bridge machine will be unable to respond quickly enough to workstations
on the network, preventing the workstations' adapters from opening. Workstations
that cannot enter the LAN will display an message. error opening
adapter
5.5.2 Adapter Considerations
If you have an IBM Token-Ring Network 16/4 Adapter or IBM Token-Ring
Network 16/4 Adapter /A with a microcode level of C24550, your
sessions may be disconnected due to insufficient adapter transmit
buffers. To correct this problem you may do one of the following:
? Replace your adapter with Engineering Change (EC) level ECA066.
? Use the LAN Adapter and Protocol Support full-screen interface
to change the Number of adapter transmit buffers parameter
for your network adapter card from the default of 1 to 2.
5.5.3 Multiple Adapter Considerations
? IBM PC Network adapters cannot share interrupt levels, therefore, you must
ensure that other adapters on the workstation do not have the same interrupt
levels as your IBM PC Network adapters. The valid interrupt levels for an
IBM PC Network adapter are 2 and 3. Remember that in Micro Channel
workstations, interrupt level 9 is treated the same as an interrupt level of 2. If
Restrictions 28
IBM CONFIDENTIAL Extended Services Driver S1A246 29 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
required, use a Reference diskette to view or change interrupt levels for your
adapters.
? The 3270 Connection Adapter for 3174 Peer Communications can only use an
interrupt level of 2. To avoid conflict with an IBM PC Network adapter, you
must change the default interrupt level on the IBM PC Network adapter from 2
to 3.
? An important consideration with multiple adapters is the amount
of total RAM used by the various adapters. The total RAM used by
your adapter cards, including other hardware adapters (for example,
displays or SCSI drives) must not exceed 128KB. If this limit is
exceeded, the network may not be able to start. To calculate your
RAM usage, see the IBM OS/2 LAN Server Version 2.0 Network Administrator
Reference Volume 1: Planning and Installation for RAM requirements on
supported adapters. To this total, add any RAM used by other hardware as
indicated by the manufacturer's documentation.
? When installing either a IBM Token-Ring Network Adapter /A or an
IBM PC Network Adapter/A concurrently with a 3270 Connection
Adapter in a Micro Channel workstation, it should be located in a
higher numbered slot than the 3270 Connection Adapter.
?
Do not mix 8-bit and 16-bit adapters in the same workstation unless
they are at least 128KB apart in address range.
5.5.4 Remote IPL Adapter Considerations
The following adapter restrictions apply to the Remote IPL service:
? If multiple LAN adapters are installed in a remote IPL requester, only one of
the adapters can be configured for the Remote IPL service.
5.6 LAN Server Version 2.0 Server Restrictions
5.6.1 General System Caveats
If installing both extended services and LAN Server, you must install Extended
Services before installing LAN Server.
This release of LAN Server 2.0 may be installed under SE Manufacturing level
# 1.30.1, (16 BIT). The server may also be installed under OS/2 driver level 6.167, (32
# BIT). We recommend running the server on SE 2.0 for evaluation purposes only.
5.6.2 Restrictions and Special Considerations for Functional Components
Restrictions 29
IBM CONFIDENTIAL Extended Services Driver S1A246 30 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Install/Config
? If installing both ES and LS, ES must be installed first.
? If you select to install DOS 5.0 you must create the DOS 5.0 diskettes before
they can be copied by the LAN Services installation/ configuration program.
Follow the instructions on the boot diskette for DOS 5.0 to create the diskettes.
?
When the server is chosen to be removed, if Local Security for 386 HPFS is
installed, the RUNPRIV.EXE command is not removed from
STARTUP.CMD. Edit the file and remove the RUNPRIV.EXE command.
# ? Do not install both the Loop Back Driver support and the LAN adapter and
# Protocol support together.
# ? The 386 HPFS will not run on OS/2 Version 2.0. When installing the LAN
# Server on an OS/2 2.0 Operating System, do not use the basic path to install;
# use the advanced path and do not install the 386 HPFS support. On the Install
# screen select "DO NOT INSTALL" the 386 HPFS. Because Local Security for
# 386 HPFS and Fault Tolerance for Fixed Disk both require 386 HPFS, you will
# not be able to install them either.
# ? When using OS/2 2.0, always take the advanced path.
# ? Anytime you do a re-install or a re-configure, you must select "Replace" for the
# LAN adapter and the protocol support.
Command Line Interface
Changes have been made to the definitions of the /PASSWORDCHG and
/PASSWORDREQ parameters of the NET USER command. These parameters
are now defined as follows:
/PASSWORDCHG:{YES | NO} Specifies whether users can change their
own password. The default is YES.
/PASSWORDREQ:{YES | NO} Specifies whether a password is required for
this user account.
YES means that a password is required.
NO means that a password is not required, but
may be used. The password restriction of
MINPWLEN is applied to any password that is
used.
NO also means that other password restrictions
such as MINPWAGE, MAXPWAGE, UNIQUEPW, and
PASSWORDCHG will not be applied to this
account.
Restrictions 30
IBM CONFIDENTIAL Extended Services Driver S1A246 31 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Full Screen Interface
? On the IBM OS/2 LAN Requester, when you select (Definitions + Users
Logon Details + Program starters) for a user, the Manage Program Starter
panel lists all applications the user may access. It highlights applications
assigned to the user except DOS public applications added to that user ID at
IBM DOS LAN Requesters. From the Manage Program Starter panel, pressing
Enter without selecting these DOS public applications will automatically
deselect them for the user. Subsequently the DOS public applications will be
removed from the user's Served Applications panel the next time the user logs
on at an IBM DOS LAN Requester.
# ? From the OS/2 LAN Requester Full Screen Interface, if the number of users
# defined in the domain is more than 875, selecting one of the following actions
# will display the NET9808E error panel:
# 1. Select Definitions + Access Control + User List to manage Access
# Control Profile User List.
# 2. Select Definitions + Applications + Program Starters + Add to Add
# Applications to Program Starters.
# 3. Select Definitions + Applications + Program Starters + Delete to Delete
# Applications from Program Starters.
# Bring up User Profile Management Services (UPM) and reduce the list to fewer
# than 875 users by deleting users you no longer need and try the action again.
?
# If your base system is OS/2 Version 2.0, the Online Reference is not available
# from the LAN Requester Full Screen Interface at this time. However, you can
# view the Online Reference by issuing "view A3ALANOR.INF" from the OS/2
# prompt.
# Please do not select Utilities + Reference information, or press F5=Reference
# on any help panel.
# Selecting Utilities + Reference information, or pressing F5=Reference on a
# help panel will cause the following error panel to appear:
# "ROIVIEW.EXE
# SYS2070: The system could not demand load the application's
# segment. ROIVIEW -> HELPMGR.30 is in error. For additional
# detailed information also see SYS182.
# End program/command/operation
# Display help"
# Press Enter to End program/command/operation and select LAN Requester
# from the Task List panel to return to the LAN Requester Full Screen Interface.
# ? Copying files from one drive to another using the Drives folder is not
# functioning. Use the OS/2 and DOS command prompts instead.
# ? To make new files show up, select refresh on a folder.
Restrictions 31
IBM CONFIDENTIAL Extended Services Driver S1A246 32 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
HPFS/386
Local Security
? The 386 HPFS local security essentially supersedes Print Manager's local
security. When a workstation with the 386 HPFS local security is started, one
must log on as either an administrator or a print operator in order for the Print
Manager window to come up and for the Spooler to be enabled. If an
administrator or a print operator is not logged on at startup time, the Print
Manager can be started with one of the following ways:
?Make sure that the C:\PRIVINIT.CMD file (or the file specified by the
PROTSHELL= line of the CONFIG.SYS file) contains the line:
SPOOL.EXE. In this case, the Print Manager will come up and will be
enabled at every workstation restart.
?After the workstation is started, perform the following steps:
?log on locally an an administrator
?enter "PRIV SPOOL" at the command prompt
? If you do not log on with sufficient privilege or with sufficient access
permission, some applications may return error messages that do not indicate
access denied as a cause for the error. Try logging on as an administrator to see
if you have insufficient access permission or insufficient privilege for that action.
Access Control Profiles: Drive level access control profiles cannot be created on
HPFS/386 drives.
# Remote IPL (RIPL): The 32 bit remote IPL of OS/2 2.0 is not currently available
# for Token Ring, PC NET, or ETHERNET.
DOS LAN Requester / Windows
Windows: MS Windows without network support installed will always print to a
local printer, even if the LPT port is "net used" to a remote printer.
Maximizing Memory Utilization with DOS 5.0: (This is not in the PUBS for this
driver.) DOS 5.0 can make more memory available to applications than earlier
DOS versions. One way this is accomplished is by DOS being loaded in the first
64KB of extended memory, called the high memory area (HMA). HMA is
available on workstations with a 286 (or greater) processor with at least 1MB of
memory. Most systems also have 384KB of space called the upper memory area.
DOS can store information in this upper memory area on workstations with 386 (or
greater) processors and extended memory. DOS 5.0 can take advantage of available
memory by installing various memory managers, such as HIMEM and EMM386.
Refer to your DOS 5.0 documentation for more information about memory and
memory managers.
# DOS LAN Requester can take advantage of the high memory area (HMA) and
# upper memory blocks (UMB) by using the NET START command or the
# DOSLAN.INI file to have DOS 5.0 load the network components into UMBs.
# The NET START parameter in /UMB. This parameter is Extended Memory
# Adapter (XMA) card and a memory manager that supports upper UMBs.
/UMB can be used in combination with /EMS or /HIM. If /UMB is used in
combination with either of these parameters, the network first tries to load all code
Restrictions 32
IBM CONFIDENTIAL Extended Services Driver S1A246 33 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
into the UMB area. If all network components do not fit, then components are
loaded into other available memory specified by /HIM or /EMS. Conventional
memory may be reduced if all network components do not fit into the UMB area.
External Interface
Disk Fault Tolerance:
? Most data corruption problems have been fixed in this driver. The potential for
data corruption in high stress environments still exists.
? Do not attempt to command line "FORMAT" a currently mirrored drive to the
FAT file system.
? Do not create more than 24 disk partitions (including mirrors).
? In a system with SCSI drives, if it appears that your system is "hanging" forever
on reads/writes or you have excessive errors on SCSI drives, please be sure your
SCSI adapters are terminated properly. The following information will help you
do so:
?A SCSI card has one bus, which extends internally and externally. Each
end must be terminated exactly once. The different drives terminate
differently.
?If no drives are attached to a card internally, then a card edge terminator is
installed on the gold tabs at the top of the card. If no drives are attached
externally, then on the IBM SCSI adapter with cache an external
pin-in-socket terminator is used. On an IBM SCSI adapter with no cache
EITHER that terminator is used OR the on-board terminator near the
external connector is inserted.
?When drives are attached (internally, externally, or both), each cable must
be terminated at the end. The black drives (60, 80, 120, 160) have
terminators on the underside of the drive and usually have white slips of
paper attached to them. The gold (>300 MB) drives have a terminator
that gets inserted between the cable and the connector on the drive.
Generic Alerter Service
User Note:
# The error log entry in the SYSLOG is not readable; however, the alert entry is
# readable. This is not a Generica Alerter Service restriction as the alerts can be sent
# to NETVIEW.
Messages
# ? The filename "NETWKSTA.SYS" in messages is the incorrect name. The
# name should be "NETWKSTA.200".
5.6.3 Restrictions and Special Considerations for Device Drivers
? When using PCNET, the default in the IBMCOM\ PROTOCOL.INI in the
MAC section for IBMNETA_NIF needs to be changed as follows:
RECEIVEBUFFERS = 6 should be RECEIVEBUFFERS = 8
Restrictions 33
IBM CONFIDENTIAL Extended Services Driver S1A246 34 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
5.6.4 Restrictions and Special Considerations for Commands
? NETCOPY or any other type of copy command (i.e. Xcopy) will trap after a
long period of repeated use.
5.7 LAN Server Version 2.0 Requester Restrictions
5.7.1 General System Caveats
If installing both extended services and LAN Server, you must install Extended
Services before installing LAN Server.
# This release of LAN Requester can be run under SE driver manufacturing level
# 1.30.1,(16 BIT), or SE 2.0 driver level 6.167, (32 BIT).
Please log on before attempting LAN functions.
Install/Config
? If installing both ES and LS, ES must be installed first.
# ? When using OS/2 2.0, always take the advanced path.
# ? Anytime you do a re-install or a re-configure, you must select "Replace" for the
# LAN adapter and the protocol support.
Command Line Interface
Changes have been made to the definitions of the /PASSWORDCHG and
/PASSWORDREQ parameters of the NET USER command. These parameters
are now defined as follows:
/PASSWORDCHG:{YES | NO} Specifies whether users can change their
own password. The default is YES.
/PASSWORDREQ:{YES | NO} Specifies whether a password is required for
this user account.
YES means that a password is required.
NO means that a password is not required, but
may be used. The password restriction of
MINPWLEN is applied to any password that is
used.
NO also means that other password restrictions
such as MINPWAGE, MAXPWAGE, UNIQUEPW, and
PASSWORDCHG will not be applied to this
account.
Restrictions 34
IBM CONFIDENTIAL Extended Services Driver S1A246 35 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Full Screen Interface
? On the IBM OS/2 LAN Requester, when you select (Definitions + Users +
Logon Details + Program starters) for a user, the Manage Program Starter
panel lists all applications the user may access. It highlights applications
assigned to the user except DOS public applications added to that user ID at
IBM DOS LAN Requesters. From the Manage Program Starter panel, pressing
Enter without selecting these DOS public applications will automatically
deselect them for the user. Subsequently the DOS public applications will be
removed from the user's Served Applications panel the next time the user logs
on at an IBM DOS LAN Requester.
# ? From the OS/2 LAN Requester Full Screen Interface, if the number of users
# defined in the domain is more than 875, selecting one of the following actions
# will display the NET9808E error panel:
# 1. Select Definitions + Access Control + User List to manage Access
# Control Profile User List.
# 2. Select Definitions + Applications + Program Starters + Add to Add
# Applications to Program Starters.
# 3. Select Definitions + Applications + Program Starters + Delete to Delete
# Applications from Program Starters.
# Bring up User Profile Management Services (UPM) and reduce the list to fewer
# than 875 users by deleting users you no longer need and try the action again.
# ? If your base system is OS/2 Version 2.0, the Online Reference is not available
# from the LAN Requester Full Screen Interface at this time. However, you can
# view the Online Reference by issuing "view A3ALANOR.INF" from the OS/2
# prompt.
# Please do not select Utilities + Reference information, or press F5=Reference
# on any help panel.
# Selecting Utilities + Reference information, or pressing F5=Reference on a
# help panel will cause the following error panel to appear:
# "ROIVIEW.EXE
# SYS2070: The system could not demand load the application's
# segment. ROIVIEW -> HELPMGR.30 is in error. For additional
# detailed information also see SYS182.
# End program/command/operation
# Display help"
# Press Enter to End program/command/operation and select LAN Requester
# from the Task List panel to return to the LAN Requester Full Screen Interface.
# ? Copying files from one drive to another using the Drives folder is not
# functioning. Use the OS/2 and DOS command prompts instead.
# ? To make new files show up, you must select refresh on a folder.
Restrictions 35
IBM CONFIDENTIAL Extended Services Driver S1A246 36 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
External Interface
? In a system with SCSI drives, if it appears that your system is "hanging" forever
on reads/writes or you have excessive errors on SCSI drives, please be sure your
SCSI adapters are terminated properly. The following information will help you
do so:
?A SCSI card has one bus, which extends internally and externally. Each
end must be terminated exactly once. The different drives terminate
differently.
?If no drives are attached to a card internally, then a card edge terminator is
installed on the gold tabs at the top of the card. If no drives are attached
externally, then on the IBM SCSI adapter with cache an external
pin-in-socket terminator is used. On an IBM SCSI adapter with no cache
EITHER that terminator is used OR the on-board terminator near the
external connector is inserted.
?When drives are attached (internally, externally, or both), each cable must
be terminated at the end. The black drives (60, 80, 120, 160) have
terminators on the underside of the drive and usually have white slips of
paper attached to them. The gold (>300 MB) drives have a terminator
that gets inserted between the cable and the connector on the drive.
DOS LAN Requester / Windows
Windows: MS Windows without network support installed will always print to a
local printer, even if the LPT port is "net used" to a remote printer.
Maximizing Memory Utilization with DOS 5.0: (This is not in the PUBS for this
driver.) DOS 5.0 can make more memory available to applications than earlier
DOS versions. One way this is accomplished is by DOS being loaded in the first
64KB of extended memory, called the high memory area (HMA). HMA is
available on workstations with a 286 (or greater) processor with at least 1MB of
memory. Most systems also have 384KB of space called the upper memory area.
DOS can store information in this upper memory area on workstations with 386 (or
greater) processors and extended memory. DOS 5.0 can take advantage of available
memory by installing various memory managers, such as HIMEM and EMM386.
Refer to your DOS 5.0 documentation for more information about memory and
memory managers.
# DOS LAN Requester can take advantage of the high memory area (HMA) and
# upper memory blocks (UMB) by using the NET START command or the
# DOSLAN.INI file to have DOS 5.0 load the network components into UMBs.
# The NET START parameter in /UMB. This parameter is Extended Memory
# Adapter (XMA) card and a memory manager that supports upper UMBs.
/UMB can be used in combination with /EMS or /HIM. If /UMB is used in
combination with either of these parameters, the network first tries to load all code
into the UMB area. If all network components do not fit, then components are
loaded into other available memory specified by /HIM or /EMS. Conventional
memory may be reduced if all network components do not fit into the UMB area.
Restrictions 36
IBM CONFIDENTIAL Extended Services Driver S1A246 37 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
5.7.2 Restrictions and Special Considerations for Device Drivers
? When using PCNET, change the \IBMCOM|PROTOCOL.INI in the MAC
section for IBMNETA_NIF as follows:
RECEIVE BUFFERS = 6 should be RECEIVEBUFFERS = 8
5.7.3 Restrictions and Special Considerations for Commands
? NETCOPY or any other type of copy command (i.e Xcopy) will trap after a
long period of repeated use.
5.8 LAN Server Version 2.0 Publications Restrictions
? Pagination may not be final for some of the publications.
? Memory and fixed-disk requirements in the "Network Administrator Reference
Volume 1: Planning and Installation" will be available in the final version.
? On page 13-3 of the "Network Administrator Reference Volume 3: Network
Administrator Tasks", the discussion on multiple adapter support for Remote
IPL is not relevant to this release and will be removed in the final version.
? The information in the "LAN Server V 2.0 Quick Reference" is for 16-bit only.
Restrictions 37
IBM CONFIDENTIAL Extended Services Driver S1A246 38 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
6.0 Extended Services Installation
During the installation of the IBM Extended Services for OS/2, pressing F1=HELP
on menus and pop-ups will provide additional information to guide you through the
process.
Installation Notice
This driver has a known problem which causes the installation to flip back and
forth between screens while files are being transferred from diskette to the hard
disk. Do not let this confuse you; you will eventually receive the correct prompt,
panel or menu.
6.1 Before You Install Extended Services
? Before you install Extended Services, consider the following three cases:
1. If you have a previously installed version of Extended Edition version 1.30.1
(EE 1.30.1), you can install Extended Services over it.
If you install over EE 1.30.1, you may also select to install with an EE
1.30.1 configuration file, and the file will be upgraded automatically during
the installation process.
If you install a Database Client over an existing EE 1.30.1 Database Client:
?NETBIOS will be installed
?SQLLOO definitions will be removed from the configuration file
(assuming you are installing using Advanced Install and specify the EE
1.30.1 XXX.CFG file), NETBIOS will be defined (if not already
present), and a default NETBIOS configuration will be created in
XXX.INI (the LAN configuration file associated with the XXX.CFG
file).
?Database Manager Workstation (Node) Directory entries will be
converted from SQLLOO to NETBIOS.
2. If you have a previously installed version of Extended Services (earlier
driver), you MUST do the following:
a. If Database Manager is currently installed, and you wish to preserve
existing databases for use with this driver, follow the procedure in 5.4.2,
estrictions for Functions/Features Available in this Driver?on
page 25 under "Database Migration" before continuing to the next step.
b. Copy all files on the boot drive that you wish to preserve
c. Re-install one of the following base operating systems (and re-format
the boot drive during the installation):
?For a 16-bit base, SE V1.3 manufacturing refresh 1.30.1 is required.
# ?For a 32-bit base, SE V2.0 driver level 6.167 is required.
Extended Services Installation 38
IBM CONFIDENTIAL Extended Services Driver S1A246 39 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
d. Re-boot and bring up your newly installed operating system
e. Remove all Extended Services components that were previously
installed on other drives, by doing one of the following:
1) Reformat the partition(s) where Extended Services components are
currently installed (after copying any files you wish to keep)
--- or ---
2) Manually (or by using File Manager) erase all files (including
"read-only" files) in the following directories, their subdirectories,
AND the directories themselves:
?\sqllib
?\cmlib
?\dbdrqlib
3. If neither of the above cases apply, you must install one of the following
operating systems as your base (and reformat the boot drive during the
installation):
?For a 16-bit base, SE V1.3 manufacturing refresh 1.30.1 is required.
# ?For a 32-bit base, SE V2.0 driver level 6.167 is required.
? If you are installing Extended Services with the OS/2 SE 2.0 base operating
system you MUST select to INSTALL ALL FEATURES of the base operating
system.
? Before you install Extended Services, refer to section 5.0, estrictions?on
page 20 for the limitations on Communications Manager and Database
Manager.
?
If you have Database Manager databases from EE 1.1, EE 1.2 or EE 1.3 that
you wish to use with this driver, you will be able to migrate them for use with
Extended Services. Refer to 8.1.1, 﨧igration of Databases?on page 55 for
more information about database migration. Make SURE you backup all
databases BEFORE installing this driver.
# ? At the end of the installation process, if you wish to view the installation history
# file, the file can be browsed/printed by entering "VIEWLOG" at the OS/2
# command line. You can also select "View Install History File" from the
# Extended Services group on workplace desktop. (see 6.2.4, 蘒nstallation Tools?
# on page 41 for more information on this group).
? The use of certain mouse device drivers may not be compatible with the
Communications Manager SDLC or Async device drivers, particularly on the
PC AT and PC XT/286. This is due to hardware interrupt conflicts. For PS/2's
mouse device drivers which support interrupt sharing can work simultaneously
with the SDLC and/or Async device drivers.
The following is a table of the interrupt levels used for the most common
communications adapters. You should also insure that the interrupt level used
by an installed mouse device does not conflict with the levels used by your
communications adapters. For an interrupt level to be sharable, both device
drivers using the interrupt must be designed for interrupt sharing. Interrupt
sharing is supported on PS/2's only.
Extended Services Installation 39
IBM CONFIDENTIAL Extended Services Driver S1A246 40 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Table 2. Communication Adapter Interrupt Levels
Adapter Interrupt Levels Comments
DFT 2 Sharable on PS/2s
SDLC 3 and 4 Sharable on PS/2s (if selected)
ASYNC 3 or 4 Sharable on PS/2s
TRN 2, 3, or 7 XT/286 or AT
TRN 2, 3, 10, or 11Sharable on PS/2s
PCN 2 or 3 Sharable on PS/2s
6.2 Extended Services Installation Concepts
6.2.1 Initial Installation
ESINST
For an initial install (first time), Extended Services installation is started by inserting
the Extended Services diskette 1 and typing "A:ESINST" at the OS/2 Command
prompt, which will then display the "Extended Services Copyright Panel". This
invocation should only be used for your initial installation of Extended Services.
During initial install (ESINST), you may choose to install using one of three
installation options:
? Basic Configuration Services
? Advanced Installation
? Custom Installation (requires a Custom Build diskette)
6.2.2 Follow-on Installation
REINST
# After initially installing, Extended Services features can be added/removed through
# reinstall (REINST) from command line, or by selecting "Add or Remove Features"
# from the Extended Services group on workplace desktop. (see 6.2.4, 蘒nstallation
# Tools?on page 41 for more information on this group).
REINST is invoked at the OS/2 command prompt which will then display the
"Extended Services Install/Remove Menu". Reinstall should be used to install any
configuration file that was created/modified through Advanced Configuration, or to
install any additional feature or any new components after initial installation.
Extended Services Installation 40
IBM CONFIDENTIAL Extended Services Driver S1A246 41 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
ESCFG
# After initially installing, if you need to modify an existing Basic Configuration
# Services file or need to create one for yourself or another user, you may use ESCFG
# or select "Basic Configuration and Installation" from the Extended Services group
# on workplace desktop. (see 6.2.4, 蘒nstallation Tools?for more information on this
# group).
ESCFG is invoked at the OS/2 command prompt which will then display the
"Extended Services Basic Configuration Services Panel". You will get the option to
install the Basic Configuration Services files you have created/changed at the end of
the processing. You can also choose not to install, but to install at a later time
using REINST.
6.2.3 Custom Build
CUSTBLD
This command is used to invoke Custom Build. Custom Build creates a Custom
diskette with the selections that you have selected. This diskette will then be used
to install Extended Services on another workstation, by selecting Custom
Installation on the "IBM Extended Services Installation Options" menu during
initial install on that workstation.
6.2.4 Installation Tools
After initial installation of Extended Services, you may access installation tools by
selecting the Extended Services group from workplace desktop. You will be able to
select from the following options.
? Basic Configuration and Installation (ESCFG)
? Add or Remove Features (REINST)
? View Install History File (VIEWLOG)
? Create Custom Install Diskette (CUSTBLD)
? View Custom Build History File
? Extended Services Command Reference
6.3 Basic Configuration Services (BCS)
6.3.1 BCS Overview
BCS is designed to aid the user in doing a quick, simple installation by providing
easy-to-use Configuration Services at install time. You can use BCS to configure
and install the following features:
? 3270 Terminal Emulation
? ASCII Terminal Emulation to single host
Extended Services Installation 41
IBM CONFIDENTIAL Extended Services Driver S1A246 42 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? 5250 Work Station Feature (AS/400 or S/36)
? Database Manager using Remote Data Services
Each component has a section listing the steps to take for the BCS path. The order
you see for your prompted steps may not correspond to what is listed in this
documentation. You will be prompted to enter information unique to your
workstation during BCS configuration. Commonly used default values are provided
for other configuration parameters. Some defaults used by BCS may not be
appropriate for your particular environment, for example, the Token Ring adapter
type. However, BCS is highly recommended as a quick way to create a
configuration file at install time and to customize it with the appropriate parameter
values later via advanced configuration services.
For more information on the features supported by Basic Configuration Services,
please refer to the Extended Services Workstation Installation Guide.
Note
The configuration file created by the BCS is called a Basic Configuration File.
To modify the basic configuration file, you can either use the Basic
Configuration Services via ESCFG command OR the Communications
Manager advanced configuration services. Please note that once the Basic
Configuration File is modified by the Communications Manager advanced
configuration services, it CANNOT be used by BCS. Both basic and regular
configuration files can be used to bring up Communications Manager.
6.3.2 Steps for Using BCS During Initial Install
The steps below show you how to create a Basic Configuration file and to install
from this file. Make sure you have installed the base operating system first or have
Extended Edition version 1.30.1 installed.
1. Insert the Extended Services diskette 1 in drive A: and type A:ESINST from an
OS/2 full screen command prompt.
2. Press enter on Extended Services Installation Version 1 Copyright panel.
3. Press enter on the Welcome panel.
4. Press enter on the Introduction panel.
5. Select "Basic Configuration and Installation" from the IBM Extended Services
Installation Options menu. Insert diskettes as prompted.
6. Enter a name and an optional comment for the Basic Configuration file.
7. You will see the Basic Configuration Services main menu.
8. Install Communications Manager and/or Database Manager
? Refer to section 7.2.1, 蘒nstalling Communications Manager Using Basic
Configuration Services?on page 49
? Refer to section 8.2.1, 蘒nstalling Database Manager Using Basic
Configuration Services?on page 56
Extended Services Installation 42
IBM CONFIDENTIAL Extended Services Driver S1A246 43 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
9. Apply Patches
Appropriate Patches must be applied at this time. Refer to section 6.6,
嗀pplying Patches to the Installed System?on page 44 for information on the
patch process. This patch process must be followed to ensure you have a
working environment.
6.3.3 Using BCS After Initial Install
For information on modifying your Extended Services installation using Basic
Configuration Services, please refer to the Extended Services Workstation
Installation Guide.
6.4 Advanced Installation
Advanced Installation can be selected on an initial installation or on a follow-on
installation. It allows installation with a user defined configuration file from this or a
previous release, installation of a default configuration file, and selective installation
of additional features.
If you choose to install a user defined configuration file from a previous release, the
configuration information is automatically upgraded when you install Extended
Services.
6.4.1 Steps for Using Advanced Install During Initial Install
The steps below show you how to use Advanced Install. Make sure you have
installed the base operating system first or have Extended Edition version 1.30.1
installed.
1. Place the Extended Services diskette 1, in drive A: and type A:ESINST from an
OS/2 full screen command prompt.
2. Press enter on Extended Services Installation Version 1 Copyright panel.
3. Press enter on the Welcome panel.
4. Press enter on the Introduction panel.
5. Select "Advanced Installation" from the IBM Extended Services Installation
Options menu.
6. You will see the IBM Extended Services Install/Remove menu.
7. Install Communications Manager and/or Database Manager
? Refer to section 7.2.2, 蘒nstalling Communications Manager Using
Advanced Installation?on page 50
? Refer to section 8.2.2, 蘒nstalling Database Manager Using Advanced
Installation?on page 61
8. Apply Patches
Appropriate Patches must be applied at this time. Refer to section 6.6,
嗀pplying Patches to the Installed System?on page 44 for information on the
Extended Services Installation 43
IBM CONFIDENTIAL Extended Services Driver S1A246 44 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
patch process. This patch process must be followed to ensure you have a
working environment.
6.4.2 Using Advanced Install After Initial Install
After an initial installation, Advanced Installation can be invoked by using the
REINST command or by selecting the Add or Remove Features option from the
Extended Services Group on workplace desktop. For information on modifying
your Extended Services installation through a follow-on installation, please refer to
the Extended Services Workstation Installation Guide.
6.5 Custom Installation
For information on using Custom Installation, please refer to the Extended Services
Workstation Installation Guide.
6.6 Applying Patches to the Installed System
After your Extended Services system is installed, you must apply the necessary
patches.
6.6.1 Description of Extended Services Patches
Communications Manager Patches
? 5250 Workstation Feature
The ACS5ACS.DLL patch is required if you are planning on using the 5250
Workstation Feature in this driver. Without this patch 5250 WSF will not
function.
? LAN Adapter and Protocol Support
The NETBEUI.NIF and NETBEUI.OS2 patches are required if you are
planning on using the LAN Adapter and Protocol support in Extended Services
along with the LAN Server driver.
? Configuration File Manager
The following patches are required if you are planning to use the Configuration
File Manager in this driver. Without these patches, the CTRL-ESC key will
not function, you may experience traps, some garbled text, and problems with
help text when using the Configuration File Manager.
?COPYCFG.EXE, COPYCFG.HLP, CCF.MSG, CCFH.MSG
? Programmable Configuration
The patches below are required if you are planning to use Programmable
Configuration. Without the patches the APPN feature of Programmable
Configuration does not function correctly.
Extended Services Installation 44
IBM CONFIDENTIAL Extended Services Driver S1A246 45 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
?RCBMTD1.DLL, RCBMTD2.DLL, RCBMTD3.DLL, MAPPER.DLL,
GATEWAY.TDF, SRPI.TDF, APPN.TDF, RCBUPG.CMD
? APPC/APPN Support
The APPC.DLL patch is required if you plan to use Communications Manager
functions which require APPC/APPN support. Without this patch, you may
experience problems starting Communications Manager using a configuration
file involving APPC/APPN, or you may experience unpredictable results after
starting Communications Manager.
? 3270 DFT Support on SE 1.30.1 for the PC AT
The ACS3EIAC.DLL patch is required if you plan to use Communications
Manager 3270 DFT connectivity with the SE 1.30.1 operating system on a PC
AT. Without this patch, the 3270 DFT connectivity will not function on a PC
AT.
? SQLLOO
The RDSLAN.DLL patch is required if you plan to configure more than 50
NETBIOS sessions; or if you plan to have EE 1.2/1.3 Database clients using
SQLLOO, connecting to an Extended Services Database server.
Database Manager Patches
If you have Database Manager installed, you must also install the Database
Manager patches.
6.6.2 Instructions for Applying Extended Services Patches
*** NOTEs: ***
1. In order for the patches to be applied correctly, you MUST take the steps
below after Extended Services installation is complete.
2. You MUST NOT start Communications Manager or Database Manager
before applying the patches.
3. These patches for IBM Extended Services for OS/2 MUST be installed prior
to installing LAN Server if you plan to install the LAN Server product.
4. If you need to re-install any of the Extended Services components, the patch
process MUST be repeated after the re-installation.
1. Insert the patch diskette #1 in drive A:
2. From the OS/2 command prompt, enter the following commands.
Note: The replace command will replace files based upon the features you have
installed on your PC. If you have installed features which do not require any
patches, then the replace command may not replace any files.
? REPLACE A:\CMPATCH\*.* x:\CMLIB /S
where x is the logical drive on which Communications Manager for
Extended Services is installed.
Extended Services Installation 45
IBM CONFIDENTIAL Extended Services Driver S1A246 46 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? REPLACE A:\CMPATCH\*.* z:\IBMCOM /S
where z is the logical drive on which OS/2 is installed.
3. If you have installed the Communications Manager Configuration File Manager
utility, you MUST enter the following command to install the correct help text
file.
COPY A:\CMPATCH\COPYCFG.HLP z:\OS2\HELP\
(where z is the logical drive (boot drive) on which OS/2 is installed)
4. If you are planning to use Communications Manager, 3270 emulation with the
DFT connectivity on a PC AT with the SE 1.30.1 operating system, you should
enter the following to apply a patch for DFT.
COPY A:\ATPATCH\ACS3EIAC.DLL x:\CMLIB\DLL\
(where x is the logical drive on which Communications Manager for Extended
Services is installed)
5. If you have NOT installed Database Manager on your workstation, you can
skip this step. Otherwise, perform one of the following, depending on what you
have installed. If you are not sure what you have installed, you can use
VIEWLOG to look at your install history. In the steps below, specify the drive
letter that indicates the drive on which Database Manager is installed. Make
sure you have inserted patch diskette #2 in drive A:, and
? If you have a Database Server or Database Client/Server or Database
Standalone installed, type
a:dbserver x:
(where x is the drive on which Database Manager is installed) and press
Enter.
? If you have a Database Client with Local Databases installed, type
a:dbclocal x:
(where x is the drive on which Database Manager is installed) and press
Enter.
? If you have a Database Client installed, type
a:dbclient x:
(where x is the drive on which Database Manager is installed) and press
Enter.
6. Remove the patch diskette.
# 7. Bring up a menu by pressing the right mouse button while the pointer is not
# over any object (i.e. blank space) on the workplace desktop.
# 8. Select shutdown from the menu to stop the system and then reboot the system.
Extended Services Installation 46
IBM CONFIDENTIAL Extended Services Driver S1A246 47 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
7.0 Installing Communications Manager
7.1 Before You Install Communications Manager
Before installing IBM Extended Services for OS/2 (Extended Services), please be
sure that you have read and understood all of the restrictions and limitations. Refer
to 5.3, 﨏ommunications Manager Restrictions?on page 21 that apply to this
driver.
# After installation of Extended Services, "Communications Manager" group and
# "Extended Services" group will be added to the workplace desktop. The contents
# (i.e. options) of "Communications Manager" group depends on which features are
# installed. The following is a complete list of available options.
? Communications Manager
? SNA Network Definitions Configuration
? Verify SNA Network Definitions
? Manage SNA Logical Links
? Display Active SNA Configuration
? Display SNA Configuration Log
?
Configuration File Manager
? Start/Stop CM Trace
? Format SNA Trace information
Selecting the Extended Services group will display the following options to select
from:
? Basic Configuration and Installation
? Add or Remove Features
? View Install History File
? Create Custom Install Diskette
? Veiw Custom Build History File
? Extended Services Command Reference
You will note that Communications Manager Advanced Configuration profiles have
changed for SNA configuration, and for LAN Adapter and Protocol configuration.
We recommend that you read the APPENDIX section provided in this document,
before using the Advanced Configuration Services for SNA configuration. In the
APPENDIX section we have provided examples of configuration steps for SNA
advanced configuration. For further information, refer to the "Communications
Manager Configuration Guide" Volume 1.
Installing Communications Manager 47
IBM CONFIDENTIAL Extended Services Driver S1A246 48 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
For LAN Adapter and Protocol configuration, refer to the "LAN Adapter and
Protocol Support Configuration Guide".
Communications Manager can be installed on any fixed disk and all changes to the
CONFIG.SYS will be updated during the installation. Communications Manager
will be installed into the \CMLIB directory and CMLIB sub-directories.
The contents of the configuration file determines which program files will be
installed on your workstation. To have appropriate program files installed on your
system, you need to "install" the configuration file through the install process. To
save DASD space, only the files you need for the connectivities and features that
have been configured will be installed. For example, if your "installed" configuration
file(s) contains no X.25 configuration information, X:\CMLIB and CMLIB
subdirectories will not be loaded with any of the code which supports X.25 (X.25
DLC, X.25 device driver, etc.). *** WARNING: *** Merely copying or creating a
configuration file in the X:\CMLIB will not install the proper feature files and
update the CONFIG.SYS on your workstation.
*** IMPORTANT NOTES: ***
? If you plan to configure a new configuration file and copy to other
workstations, we RECOMMEND that the "Configuration File Manager" utility
be used, please refer to the "IBM Extended Services for OS/2 Network
Administration Guide. With APPN integrated into Extended Services, there are
APPN related files that MUST be copied with each .CFG file.
? If your configuration file has been modified to add new features (for example:
adding SRPI and 3270 features to the default ACSCFGUS.CFG via advanced
configuration services, or adding the 5250 WSF feature to your basic
configuration file via ESCFG.CMD), you will be required to go through the
REINST process to have the new feature files installed and CONFIG.SYS
updated on your system. If your configuration file has been customized via
advanced configuration services to include new features, type "REINST" at the
OS/2 command line, and be sure to select the "User Configuration File" option
on the Communications Manager Install Menu during the re-installation
process.
? If you have a new configuration file (by copying one from another workstation
or creating one via advanced configuration services), and it contains additional
connectivities and features other than what you have on your workstation,
re-installation is necessary to bring up Communications Manager with the new
configuration file. Type "REINST" at the OS/2 command prompt; select the
"User Configuration File" option on the Communications Manager Install
Menu, and follow the prompts to install the new program files.
7.1.1 Compiler Support
Following is a list of the current compiler support for Communications Manager.
?
Support for the PASCAL language has been removed.
? The Microsoft C Compiler V6.0 is the currently supported C compiler.
** The IBM C/2 compiler is no longer supported **.
Installing Communications Manager 48
IBM CONFIDENTIAL Extended Services Driver S1A246 49 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? The Microfocus COBOL/2 Compiler is the currently supported COBOL
compiler.
** The IBM COBOL/2 compiler is no longer supported **.
?
The IBM FORTRAN/2 compiler is the currently supported FORTRAN
compiler.
? The IBM MACRO ASSEMBLER/2 compiler is supported.
7.2 Installation Instructions for Communications Manager
7.2.1 Installing Communications Manager Using Basic Configuration Services
The steps below use default parameter values to create a basic configuration file with
3270 terminal emulation using Token Ring.
1. Select "3270 terminal emulation" from the BCS Main menu.
2. Select the "LAN" option for the Connection Type, and take the defaults for the
other options in the 3270 Terminal Emulation Defaults.
3. Select "IBM Token-Ring Network" for Network Type.
4. Select "IBM Token-Ring Adapter " from the Select Token Ring Network
Adapter menu. (Select the appropriate adapter for your environment if it is
different from the IBM Token-Ring Adapter.)
5. Specify a "locally administered address" from the Select LAN Address Type
menu.
6. Specify the 12 digit hex address for the Local Adapter Address.
7. On the 3270 Terminal Emulation LAN Defaults menu, specify the 12 digit hex
address for the LAN Destination Address.
8. Specify Local Node Name, Network Name, and Local Node ID on the
Configuration Network Defaults menu to suit your environment.
9. BCS Main Menu is displayed.
10. If you are selecting to install Database Manager, refer to 8.2.1, 蘒nstalling
Database Manager Using Basic Configuration Services?on page 56.
11. If no more features are to be configured, press F3 to exit BCS.
12. The target Drive Specification menu is displayed to specify the drive ID.
13. Press F3 to exit the IBM Extended Services for OS/2 Install/Remove menu if
you are done.
14. Stop all active processes.
# 15. Bring up a menu by pressing the right mouse button while pointer is not over
# any object (i.e on blank space) on workplace desktop.
# 16. Select Shutdown from the menu to stop the system and then reboot the system.
17. Install patches (see 6.6, 嗀pplying Patches to the Installed System?on
page 44).
Installing Communications Manager 49
IBM CONFIDENTIAL Extended Services Driver S1A246 50 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
7.2.2 Installing Communications Manager Using Advanced Installation
1. Select the "Install Communications Manager" option from the IBM Extended
Services Install/Remove menu.
2. The target Drive Specification menu is displayed to specify the drive ID for
Communications Manager. You may install Communications Manager on any
fixed disk or partition.
3. Select "Configuration Files" from the Communications Manager Install menu.
4. Select "Default Configuration Files" from the Communications Manager
Configuration File menu.
Note: At this point, you could also have selected to install "User configuration
files." This would be the option that you would use to install a configuration file
from this release or a previous release. If you select a configuration file from a
previous release, the configuration information is automatically updated.
5. Select one or both of the following IBM supplied Default Configuration files
from the menu.
? ACSCFG.CFG
(This is a skeleton configuration file included with all model profiles and
NLS keyboard profiles.)
? ACSCFGUS.CFG
(This is a skeleton configuration file included with all model profiles and US
keyboard profiles.)
After selecting the configuration file, you will be returned to the
Communications Manager Install menu.
6. To install any additional features, select "Additional Features" from the
Communications Manager Install menu.
7. Press spacebar to select each individual feature to install from the Additional
Features menu. For example, if you are going to program to the
Communications Manager API using the provided language interface, you need
to install the API Data Structure files. Press enter when your are finished
selecting features.
8. Press F3 to exit the Communications Manager Install menu. Please note that
when Exit (F3) is pressed, installation of your feature selections are being
performed. Insert diskettes as required.
9. If you installed more than one configuration file, the Select Configuration File
to Update CONFIG.SYS File menu is displayed. By selecting the configuration
file(s) you wish to activate, the CONFIG.SYS is automatically updated with
DEVICE= and RUN= statements.
10. Refer to 8.2.2, 蘒nstalling Database Manager Using Advanced Installation?on
page 61 if you also need to install Database Manager.
11. Press F3 to exit the Extended Services Install/Remove menu if you are done
with Extended Services installation.
12. Stop all active processes.
Installing Communications Manager 50
IBM CONFIDENTIAL Extended Services Driver S1A246 51 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
# 13. Bring up a menu by pressing the right mouse button while mouse pointer is not
# over any object (i.e on blank space) on workplace desktop.
# 14. Select Shutdown from the menu to stop the system and then reboot the system.
15. Install patches (see 6.6, 嗀pplying Patches to the Installed System?on
page 44).
7.2.3 Reconfiguring and Reinstalling Communications Manager
1. Start Communications Manager by selecting Communications Manager from
Communication Manager Group icon.
2. Enter the appropriate configuration file name for starting the Communications
Manager.
3. Select "Configuration Services" from the Action Bar to configure your desired
feature(s), for example: the SRPI, APPC, SNA Gateway, LUA, and X.25.
4. When the user-defined configuration file(s) are built and verified, exit the
Communications Manager.
5. Type "REINST" at the OS/2 command prompt to re-install your configuration
file(s) and the related feature files.
6. Select "Install Communications Manager" option from the IBM Extended
Services Install/Remove menu.
7. Select "Configuration Files" from the Communications Manager Install menu.
8. Select "User Configuration files" from the Communications Manager
Configuration file menu.
9. The Source Location menu is displayed. Specify the drive and path to your user
configuration file.
10. Select your desired configuration file(s) from the Select Configuration Files
panel.
11. Select the "Additional Features" option from the Communications Manager
Install menu if so desired.
12. Press F3 to exit the Communications Manager Install menu. Insert diskettes as
required.
13. Select the appropriate configuration file to update the CONFIG.SYS file.
14. Press F3 to exit the Extended Services Install/Remove menu.
15. Stop all active processes.
# 16. Bring up a menu by pressing the right mouse button while pointer is not over
# any object (i.e on blank space) on workplace desktop.
# 17. Select Shutdown from the menu to stop the system and then reboot the system.
18. Install patches (see 6.6, 嗀pplying Patches to the Installed System?on
page 44).
Installing Communications Manager 51
IBM CONFIDENTIAL Extended Services Driver S1A246 52 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
7.3 Re-installation of Communications Manager
Re-installation is the process whereby the Communications Manager component,
Communications Manager configuration file(s) with added NEW features and/or
Additional Features are to be installed on a workstation that has previously been
through the Extended Services installation process. The requisite Communications
Manager program files are installed along with your configuration file. Enter
"REINST" from the OS/2 command prompt line, and follow the prompts for
installation instructions and inserting diskettes
7.4 Communications Manager Installation Notes
This section describes some specific notes that are related to installing the
Communications Manager from this driver:
? There are three types of configuration files that can be installed for
Communications Manager:
?Basic configuration file
?Default (IBM-supplied) configuration file
?User-defined configuration file.
The basic configuration file is generated by the fast-path Basic Configuration
Services. Please refer to 6.3, 﨎asic Configuration Services (BCS)?on page 41
for more detailed information. If the communication features cannot be
configured using the BCS, most users will want to go to the Install Additional
Features panel to select ACSCFG.CFG or ACSCFGUS.CFG from the Default
Configuration Files option. The ACSCFGUS.CFG file is a general-purpose
configuration file shipped with the system and contains all model profiles along
with US-only keyboard support. It will require tailoring for your specific
configuration before you can begin communicating. If you plan to make
extensive changes, you may want to copy ACSCFG.CFG or ACSCFGUS.CFG
to your own file, (e.g. MYCFG.CFG) and start the Communications Manager
using MYCFG.
Once ACSCFG.CFG or ACSCFGUS.CFG has been installed, you have the
flexibility to customize your own features in the configuration file by utilizing
the Communications Manager advanced configuration services function. After
you build your own configuration file, you need to type "REINST" at the OS/2
command line, and select the "Configuration Files" and "Addition Features"
options on the Communications Manager Install menu during the re-installation
process. Refer to sections 7.2.2, 蘒nstalling Communications Manager Using
Advanced Installation?on page 50 and 7.2.3, econfiguring and Reinstalling
Communications Manager?on page 51 for more information.
Installing Communications Manager 52
IBM CONFIDENTIAL Extended Services Driver S1A246 53 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
7.5 ROP Service and SPA Router Installation Instructions
Remote Operations Service (ROP Service) and Service Point Application Router
(SPA Router) can be installed on any fixed disk, and all changes to CONFIG.SYS
will be updated during installation. SPA Router and ROP Service are installed in
the \ROP directory of the drive you specify. Follow the steps below to install ROP
Service and SPA Router.
1. Place the IBM Extended Services for OS/2 diskette 1 in drive A.
2. At the command prompt type:
A:ROPS
3. Press Enter.
4. Follow instructions on the menus and insert diskettes as prompted.
5. You will be asked to enter the drive where you want to install the SPA Router
and ROP Service. Enter any valid drive letter of your choice. The SPA Router
and ROP Service are installed in the \ROP directory of the drive you choose.
6. On the "Remote Operations Installation Complete" menu, remove the diskette
from drive A: and press enter.
7. On the "Installation Complete" panel, select to "Return."
8. You will return to the OS/2 command prompt. At this point, you should use
Shutdown to stop and reboot the system so that the CONFIG.SYS changes
take effect.
*** NOTES: ***
Before you can use the SPA Router and ROP Service, you will need to do the
following.
1. In your Communications Manager SNA Profile ensure that the Maximum RU
Size is set to 512 or greater. ROP Service will only work with a value of 512 or
greater.
2. Configure and start a 3270 terminal emulation session (other than a 3270 DFT
session) or configure Advanced Program-to-Program Communications (APPC)
with session start in order to establish an SSCP-PU session.
3. If you are going to use the User Profile Management (UPM) operator checking
option, ensure that the operator ID of the NetView operator using ROP Service
is defined to the UPM tables. To do this, define a new ID using an UPM
administrator account. The password is optional. If the system is not security
critical, it is recommended that the password not be set because use of a
password requires sending the password with every RUNCMD.
4. Start the Communications Manager before using the SPA Router and ROP
Service.
Installing Communications Manager 53
IBM CONFIDENTIAL Extended Services Driver S1A246 54 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
5. Open the Remote Operations group from the Desktop Manager group of OS/2
Presentation Manager. Start "Service Point Application Router" and then
"Remote Operations Service".
6. You are now ready to issue commands from NetView to this workstation.
Installing Communications Manager 54
IBM CONFIDENTIAL Extended Services Driver S1A246 55 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
8.0 Installing Database Manager
8.1 Before You Install Database Manager
Before installing Database Manager, please be sure that you have read and
understood all of the restrictions/limitations that apply to this driver. See 6.1,
﨎efore You Install Extended Services?on page 38 and 5.4, 﨑atabase Manager
Restrictions?on page 25.
Database Manager can be installed on any fixed disk, and all changes to
CONFIG.SYS will be updated during the installation. Database Manager will be
installed into the \SQLLIB and \SQLLIB\DLL directories.
8.1.1 Migration of Databases
Extended Services databases (databases created using the previously shipped
Extended Services driver), CANNOT BE MIGRATED FOR USE WITH THIS
DRIVER. Please refer to 5.4, 﨑atabase Manager Restrictions?on page 25 for
detailed instructions for using existing Extended Services databases with this driver.
Existing databases from EE 1.1, EE 1.2 and EE 1.3 CAN BE MIGRATED for use
with Extended Services. Currently, the only supported form of migration is
Backup/Restore. Refer to Appendix A of the IBM Extended Services for OS/2
Guide to Database Manager for instructions on migrating databases. Be SURE to
backup all databases BEFORE you install this driver.
Corrections
Appendix A of the IBM Extended Services for OS/2 Guide to Database Manager
has some incorrect information. The references to migration of Version 1.0
databases is wrong: EE 1.0 databases can NOT be migrated. Also, there are no
references to EE 1.2 or EE 1.3 databases in this appendix; however, migration
DOES WORK for these databases.
8.1.2 Compiler Support
Following is a list of the current compiler support for Database Manager.
? Support for the PASCAL language has been removed.
?
The Microsoft C Compiler V6.0 is the currently supported C compiler.
** The IBM C/2 compiler is no longer supported **.
? The Microfocus COBOL/2 Compiler V2.5 is the currently supported COBOL
compiler.
** The IBM COBOL/2 compiler is no longer supported **.
Installing Database Manager 55
IBM CONFIDENTIAL Extended Services Driver S1A246 56 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
? The IBM FORTRAN/2 compiler is the currently supported FORTRAN
compiler.
8.2 Database Manager Installation Examples
Note
The following installation examples assume that you will be using IBM
Token-Ring as your LAN network type. If you choose other network types,
there will be some differences in the panels/menus that are displayed.
Also, due to variables such as the sequence of component installation, all steps
may not appear in the exact sequence listed in the examples. Additionally, if a
connection type of "LAN" was previously configured (such as during 3270
Terminal Emulation configuration), some menus/panels may not appear at all.
These are EXAMPLES only. Please refer to the IBM Extended Services for
OS/2 Start Here and the IBM Extended Services for OS/2 Workstation
Installation Guide for detailed installation instructions.
8.2.1 Installing Database Manager Using Basic Configuration Services
You can use Basic Configuration Services (BCS) to install any Database Manager
configuration (Database Client, Database Server, Database Client/Server, Database
Client with Local Databases, or Standalone). However, it is most commonly used to
install those configurations which use Remote Data Services (RDS); this includes all
configurations except Standalone.
If you use Basic Configuration Services, and if you plan to use X.25 or SDLC for
Remote Data Services, you will need to supplement your install with the
Communications Manager Advanced Configuration services and re-installation
process to configure and install them. Refer to the IBM Extended Services for OS/2
Configuration Guide for Communications for more information.
The instructions that follow assume you will be installing Database Services, Query
Manager, and Database Tools. Query Manager and Database Tools should be
installed with Database Services if other application programs are not available to
use when working with database information.
If you choose not to install either Query Manager or Database Tools, then do not
select those options from the Database Manager Install menu. In addition, you will
be able to select DOS Database Client support and/or Windows Database Client
support. This support can be installed on ANY configuration (see the IBM
Extended Services for OS/2 Guide to Database Manager for additional information
about DOS/Windows Database Clients).
You may install Database Manager on any fixed disk or partition.
Installing Database Manager 56
IBM CONFIDENTIAL Extended Services Driver S1A246 57 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Installing as a Database Client or Client with Local Databases
1. At the Basic Configuration Services Main Menu:
? Select "Database Manager using Remote Data Services"
2. At the Specify Database Manager Communications menu:
? Select "Database Client"
3. At the Databases on Your Workstation pop-up:
? Select "No"
Note
You can select "Yes", if you also want to create databases on this
workstation. If you do, you will actually be installing as a Database
Client with Local Databases. This is a new Database Manager
configuration with Extended Services.
4. If the Select LAN Network Type menu displays:
? Select "IBM Token-Ring Network..."
5. If the Select Token-Ring Network Adapter menu displays:
? Select the appropriate adapter (e.g., Token-Ring adapter /A, Token-Ring
adapter 16/4 /A, etc.)
6. If the Select LAN Address Type menu displays:
? Select "Use Universal address" if you want to use the unique address of the
adapter card itself (and proceed to Step 7)
-- or --
? Select "Specify a locally adminstered address" if you want to provide your
own unique local adapter address.
?At the Local LAN Adapter Address panel:
?Enter a UNIQUE 12-digit adapter address, such as 400000000015.
7. You will now be returned to the Basic Configuration Services Main Menu
? Select another feature that you wish to install (i.e., 3270 Terminal
Emulation, ASCII Terminal Emulation, etc.). See 7.2, 蘒nstallation
Instructions for Communications Manager?on page 49 for information
about installing these CM features.
-- or --
? Select F3=Exit if you have made your last selection
8. Follow the prompts to insert diskettes for installation of the Extended Services
common code and the required Communications Manager code.
If the Target Drive Specification panel displays (for Communications Manager),
specify the target drive where you want CM installed.
9. At the Target Drive Specification panel for Database Manager
? Enter the target drive where you want Database Manager installed
Installing Database Manager 57
IBM CONFIDENTIAL Extended Services Driver S1A246 58 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
10. At the Database Manager Install Menu:
? Select "Database Services", "Query Manager" and "Database Tools" (note
that this is now a multi-select menu)
11. At the Workstation Name pop-up:
? Specify a UNIQUE name for your workstation. (Note that BCS now
defaults to the NETBIOS protocol for OS/2 clients. This requires that
workstation names on a LAN be unique).
12. Follow the prompts to insert diskettes for installation of Database Manager
Installing as a Database Server
1. At the Basic Configuration Services Main Menu:
? Select "Database Manager using Remote Data Services"
2. At the Specify Database Manager Communications menu:
? Select "Database Server"
3. At the Database Manager Target Drive Specification panel:
? Enter the target drive where you want Database Manager installed
4. If the Select LAN Network Type menu displays:
? Select "IBM Token-Ring Network..."
5. If the Select Token-Ring Network Adapter menu displays:
?
Select the appropriate adapter (i.e., Token-Ring adapter /A, Token-Ring
adapter 16/4 /A, etc.)
6. If the Select LAN Address Type menu displays:
? Select "Use Universal address" if you want to use the unique address of the
adapter card itself (and proceed to Step 7)
-- or --
?
Select "Specify a locally adminstered address" if you want to provide your
own unique local adapter address.
?At the Local LAN Adapter Address panel:
?Enter a UNIQUE 12-digit adapter address, such as 400000000020.
7. You will now be returned to the Basic Configuration Services Main Menu
? Select another feature that you wish to install (i.e., 3270 Terminal
Emulation, ASCII Terminal Emulation, etc.). See 7.2, 蘒nstallation
Instructions for Communications Manager?on page 49 for information
about installing these CM features.
-- or --
? Select F3=Exit if you have made your last selection
8. Follow the prompts to insert diskettes for installation of the Extended Services
common code and the required Communications Manager code.
Installing Database Manager 58
IBM CONFIDENTIAL Extended Services Driver S1A246 59 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
If the Target Drive Specification panel displays (for Communications Manager),
specify the target drive where you want CM installed.
9. At the Database Manager Install Menu:
?
Select "Database Services", "Query Manager" and "Database Tools" (note
that this is now a multi-select menu)
10. At the Workstation Name pop-up:
? Specify a UNIQUE name for your workstation. (Note that BCS now
defaults to the NETBIOS protocol for OS/2 clients. This requires that
workstation names on a LAN be unique).
11. Follow the prompts to insert diskettes for installation of Database Manager
Installing as a Database Client/Server
1. At the Basic Configuration Services Main Menu:
? Select "Database Manager using Remote Data Services"
2. At the Specify Database Manager Communications menu:
?
Select "Database Client/Server"
3. At the Database Manager Target Drive Specification panel:
? Enter the target drive where you want Database Manager installed
4. If the Select LAN Network Type menu displays:
? Select "IBM Token-Ring Network..."
5. If the Select Token-Ring Network Adapter menu displays:
? Select the appropriate adapter (i.e., Token-Ring adapter /A, Token-Ring
adapter 16/4 /A, etc.)
6. If the Select LAN Address Type menu displays:
? Select "Use Universal address" if you want to use the unique address of the
adapter card itself (and proceed to Step 7)
-- or --
? Select "Specify a locally adminstered address" if you want to provide your
own unique local adapter address.
?At the Local LAN Adapter Address panel:
?Enter a UNIQUE 12-digit adapter address, such as 400000000025.
7. You will now be returned to the Basic Configuration Services Main Menu
?
Select another feature that you wish to install (i.e., 3270 Terminal
Emulation, ASCII Terminal Emulation, etc.). See 7.2, 蘒nstallation
Instructions for Communications Manager?on page 49 for information
about installing these CM features.
-- or --
? Select F3=Exit if you have made your last selection
Installing Database Manager 59
IBM CONFIDENTIAL Extended Services Driver S1A246 60 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
8. Follow the prompts to insert diskettes for installation of the Extended Services
common code and the required Communications Manager code.
If the Target Drive Specification panel displays (for Communications Manager),
specify the target drive where you want CM installed.
9. At the Database Manager Install Menu:
? Select "Database Services", "Query Manager" and "Database Tools" (note
that this is now a multi-select menu)
10. At the Workstation Name pop-up:
? Specify a UNIQUE name for your workstation. (Note that BCS now
defaults to the NETBIOS protocol for OS/2 clients. This requires that
workstation names on a LAN be unique).
11. Follow the prompts to insert diskettes for installation of Database Manager
Installing as a Standalone
Note
Standalone DBM is usually installed using Advanced Installation, not BCS;
however, if you want to install one or more of the Communications Manager
features (3270 Terminal Emulation, ASCII Terminal Emulation or 5250 WSF)
AND you want Standalone DBM, this procedure will work.
1. At the Basic Configuration Services Main Menu:
? Select one of the Communications Manager options ("3270 Terminal
Emulation, ASCII Terminal Emulation, or 5250 Workstation Feature")
2. Follow the prompts to insert diskettes for installation of the Extended Services
common code and the required Communications Manager code.
3. At the Target Drive Specification panel:
? Specify the target drive where you want Communications Manager installed
4. You will now be returned to the Basic Configuration Services Main Menu
?
Select F3=Exit
5. At the IBM Extended Services/2 Install/Remove menu:
? Select "Install Database Manager"
6. At the Target Drive Specification panel:
? Specify the target drive where you want Database Manager installed
7. If a previous version of Database Manager is detected, select "Remove previous
version" from the Remove Previous Version of Selected Component pop-up.
8. At the Database Manager Install menu:
9. Select "Database Services", "Query Manager", and "Database Tools" (note that
this is now a multi-select menu).
Installing Database Manager 60
IBM CONFIDENTIAL Extended Services Driver S1A246 61 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
10. At the Database Remote Data Services menu:
? Select "No"
11. Follow the prompts to insert diskettes.
12. When you have finished installing Database Manager, select exit (F3), and
follow the instructions.
8.2.2 Installing Database Manager Using Advanced Installation
You can use Advanced Installation to install any Database Manager configuration
(Database Client, Database Server, Database Client/Server, Database Client with
Local Databases, or Standalone); however, it is most commonly used to install
Standalone. Those configurations which use Remote Data Services (RDS) are more
commonly installed using Basic Configuration Services (BCS).
The instructions that follow assume you will be installing Database Services, Query
Manager, and Database Tools. Query Manager and Database Tools should be
installed with Database Services if other application programs are not available to
use when working with database information.
If you choose not to install either Query Manager or Database Tools, then do not
select those options from the Database Manager Install menu. In addition, you will
be able to select DOS Database Client support and/or Windows Database Client
support. This support can be installed on ANY configuration (see the IBM
Extended Services for OS/2 Guide to Database Manager for additional information
about DOS/Windows Database Clients).
You may install Database Manager on any fixed disk or partition.
Installing as a Standalone
1. At the IBM Extended Services/2 Install/Remove menu:
? Select "Install Database Manager"
2. At the Target Drive Specification panel:
? Specify the target drive where you want Database Manager installed
3. If a previous version of Database Manager is detected, select "Remove previous
version" from the Remove Previous Version of Selected Component pop-up.
4. At the Database Manager Install menu:
5. Select "Database Services", "Query Manager", and "Database Tools" (note that
this is now a multi-select menu).
6. At the Database Remote Data Services menu:
? Select "No"
7. Follow the prompts to insert diskettes.
8. When you have finished installing Database Manager, select exit (F3), and
follow the instructions.
Installing Database Manager 61
IBM CONFIDENTIAL Extended Services Driver S1A246 62 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Installing as a Database Client or Client with Local Databases
1. At the IBM Extended Services/2 Install/Remove menu:
? Select "Install Database Manager"
2. At the Target Drive Specification panel:
? Specify the target drive where you want Database Manager installed
3. If a previous version of Database Manager is detected, select "Remove previous
version" from the Remove Previous Version of Selected Component pop-up.
4. At the Database Manager Install menu:
5. Select "Database Services", "Query Manager", and "Database Tools" (note that
this is now a multi-select menu).
6. At the Database Remote Data Services menu:
? Select "Yes"
7. At the Specify Database Manager Communications menu:
? Select "Database Client"
8. At the Databases on Your Workstation pop-up:
?
Select "No"
Note
You can select "Yes", if you also want to create databases on this
workstation. If you do, you will actually be installing as a Database
Client with Local Databases. This is a new Database Manager
configuration with Extended Services.
9. At the Workstation Name pop-up:
? Specify a UNIQUE name for your workstation. (Note that if you plan to
use NETBIOS as the protocol for this client, this name MUST be unique
on the LAN).
10. Follow the prompts to insert diskettes.
11. If LAN Adapter and Protocol Support (LAPS) has not been installed, the
'Warning: LAN Adapter and Protocol Support Not Installed' pop-up will
display.
12. At the IBM Extended Services/2 Install/Removemenu:
? Select "Install Communications Manager" to configure and install the
necessary CM features to support your configuration, if you have not
already done so. You will need to configure and install the necessary
communications adapter and protocol support in order to use Remote Data
Services.
-- or --
?
Select F3=Exit to complete the Database Manager installation
Installing Database Manager 62
IBM CONFIDENTIAL Extended Services Driver S1A246 63 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Installing as a Database Server
1. At the IBM Extended Services/2 Install/Remove menu:
? Select "Install Database Manager"
2. At the Target Drive Specification panel:
? Specify the target drive where you want Database Manager installed
3. If a previous version of Database Manager is detected, select "Remove previous
version" from the Remove Previous Version of Selected Component pop-up.
4. At the Database Manager Install menu:
5. Select "Database Services", "Query Manager", and "Database Tools" (note that
this is now a multi-select menu).
6. At the Database Remote Data Services menu:
? Select "Yes"
7. At the Specify Database Manager Communications menu:
? Select "Database Server"
8. At the Workstation Name pop-up:
? Specify a UNIQUE name for your workstation. (Note that if you plan to
use the NETBIOS protocol for client communications, this name MUST
be unique on the LAN).
9. Follow the prompts to insert diskettes.
10. If LAN Adapter and Protocol Support (LAPS) has not been installed, the
'Warning: LAN Adapter and Protocol Support Not Installed' pop-up will
display.
11. At the IBM Extended Services/2 Install/Remove menu:
? Select "Install Communications Manager" to configure and install the
necessary CM features to support your configuration, if you have not
already done so. You will need to configure and install the necessary
communications adapter and protocol support in order to use Remote Data
Services.
-- or --
?
Select F3=Exit to complete the Database Manager installation
Installing as a Database Client/Server
1. At the IBM Extended Services/2 Install/Remove menu:
? Select "Install Database Manager"
2. At the Target Drive Specification panel:
? Specify the target drive where you want Database Manager installed
3. If a previous version of Database Manager is detected, select "Remove previous
version" from the Remove Previous Version of Selected Component pop-up.
4. At the Database Manager Install menu:
Installing Database Manager 63
IBM CONFIDENTIAL Extended Services Driver S1A246 64 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
5. Select "Database Services", "Query Manager", and "Database Tools" (note that
this is now a multi-select menu).
6. At the Database Remote Data Services menu:
?
Select "Yes"
7. At the Specify Database Manager Communications menu:
? Select "Database Client/Server"
8. At the Workstation Name pop-up:
? Specify a UNIQUE name for your workstation. (Note that if you plan to
use the NETBIOS protocol for communications, this name MUST be
unique on the LAN).
9. Follow the prompts to insert diskettes.
10. If LAN Adapter and Protocol Support (LAPS) has not been installed, the
'Warning: LAN Adapter and Protocol Support Not Installed' pop-up will
display.
11. At the IBM Extended Services/2 Install/Remove menu:
?
Select "Install Communications Manager" to configure and install the
necessary CM features to support your configuration, if you have not
already done so. You will need to configure and install the necessary
communications adapter and protocol support in order to use Remote Data
Services.
-- or --
? Select F3=Exit to complete the Database Manager installation
Installing Database Manager 64
IBM CONFIDENTIAL Extended Services Driver S1A246 65 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
9.0 Installing OS/2 LAN Requester
Please read section 5.7, 﨤AN Server Version 2.0 Requester Restrictions?on
page 34 before installing.
*** PLEASE NOTE ***
# For a 16-bit base IBM OS/2 LAN Requester, Version 2.0, driver level 281 will
# run on SE manufacturing level 1.30.1. For a 32-bit base, IBM OS/2 LAN
# requester will run on SE V.2.0 driver level 6.167.
9.1 Basic Installation for OS/2 LAN Requester
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3,
page 31.
9.2 Advanced Installation for OS/2 LAN Requester
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3,
page 33.
9.3 Reinstalling, Reconfiguring or Removing
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3,
page 43.
Installing OS/2 LAN Requester 65
IBM CONFIDENTIAL Extended Services Driver S1A246 66 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
10.0 Installing OS/2 LAN Server
Please read section 5.6, 﨤AN Server Version 2.0 Server Restrictions?on page 29
before installing.
***PLEASE NOTE***
# The OS/2 LAN Server, V2.0, driver level 281, will run on the 16-bit based SE
# manufacturing level 1.30.1, and on the 32-bit based SE driver level 6.167
10.1 Basic Installation for OS/2 LAN Server
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3,
page 12.
10.2 Advanced Installation for OS/2 LAN Server
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 3,
page 15.
10.3 LAN Server 1.3 Migration Utility
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 1,
page 20, and chapter 3, page 8. Also, please see the IBM OS/2 LAN Server V2.0
Migration Handbook .
Installing OS/2 LAN Server 66
IBM CONFIDENTIAL Extended Services Driver S1A246 67 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
11.0 Installing IBM LAN Support Program and DOS LAN
Requester
Please read section 5.6, 﨤AN Server Version 2.0 Server Restrictions?on page 29
and 5.7, 﨤AN Server Version 2.0 Requester Restrictions?on page 34 before
installing.
11.1 Installing the IBM LAN Support Program, V.1.21
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 5
and the IBM LAN Support Program User's Guide.
11.2 Installing DOS LAN Requester
Please see the IBM Operating System/2 Local Area Network Server Version 2.0
Network Administrator Reference, Volume 1: Planning and Installation, chapter 5.
Installing IBM LAN Support Program and DOS LAN Requester 67
IBM CONFIDENTIAL Extended Services Driver S1A246 68 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Appendix
Appendix 68
IBM CONFIDENTIAL Extended Services Driver S1A246 69 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Appendix A. SNA Advanced Configuration
A.1 Overview
Earlier this year, IBM introduced a software program product called Networking
Services/2. This product was designed to enhance the performance of computers
operating in OS/2 Extended Edition network environments. Networking Services/2
provides both APPN end node and network node support to workstations, allowing
them greater flexibility when communicating with other workstations in the
network. Networking Services/2 also offers the SAA Common Programming
Interface (CPI) for communications, and an enhanced version of the Advanced
Program to Program Communications (APPC) Application Programming Interface
(API). Networking Services/2 greatly improved APPC throughput in
performance-critical LAN environments. In addition, Networking Services/2 offers
configuration and management services that provide both ease-of-use and improved
function for network users.
In this offering of Extended Services/2, the function provided by Networking
Services/2 is incorporated into the Communications Manager product. This
addition further enhances the usability and performance of APPN and
Communications Manager, as well as the networking capability of your OS/2 EE
system environment. With this added function, a workstation using Extended
Services can participate in an APPN network as a low-entry networking (LEN)
node, end node, or network node.
A.1.1 The Configuration Process
When you perform Advanced Configuration for SNA, Communications Manager
builds a particular set of configuration files. All of these files have the same name as
the configuration file you specify but different extensions. These files contain
different information, based on the extension. The following list provides
descriptions of the configuration files:
.CFG Communications Manager binary configuration file, which contains DLC,
SNA Gateway, X.25, 3270 LU, and LUA information.
This file is updated following Verify and is placed in the \CMLIB directory.
.NDF Node definitions configuration file, which contains an ASCII representation
of the verbs used to configure APPN at startup time. You can use the .NDF
file to perform additional SNA configuration by editing the file with any type
of ASCII editor.
This file is created following completion of the SNA Feature Configuration
panel during configuration and is placed in the \CMLIB\APPN directory.
.CF2 APPN binary configuration file, which contains a binary representation of
the verbs used to configure APPN at startup time. This file must exist and
cannot be empty to start APPN function.
This file is created following Verify and is placed in the \CMLIB\APPN
directory.
Appendix A. SNA Advanced Configuration 69
IBM CONFIDENTIAL Extended Services Driver S1A246 70 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
.SEC Binary security configuration.
This file is created following completion of the SNA Feature Configuration
panel during configuration and is placed in the \CMLIB\APPN directory.
.INI This file supports LAN adapter and protocol functions and is stored in the
\IBMCOM directory. PROTOCOL.INI is the name of the .INI file for the
active configuration on your workstation.
The node definitions (.NDF) and .INI files can be modified using a text editor.
You can modify the other configuration files using the Communications Manager
configuration panels.
Three scenarios for SNA Advanced Configuration are presented in this section:
?
5250 Advanced Configuration
? 3270 over Token-Ring
? 3270 over SDLC via Gateway.
Sample Node Definitions files (NDF) for each of the scenarios are also included.
A.2 Advanced Configuration for 5250
1. Copy and rename the ACSCFGUS.CFG file in the \CMLIB directory to create
your new configuration file.
(example: ) C>copy acscfgus.cfg 5250adv.cfg
2. Restart Communications Manager using this file.
(example: ) C>cm 5250adv
3. Switch to the task list to access the Communications Manager Main Menu.
4. Select the Advanced action bar item and then select the Configuration pulldown
choice. Press Enter.
A message box appears displaying the name of the configuration file.
5. Press Enter. The Specify Configuration Usage panel appears.
6. Select the first option if you intend to use this configuration on this workstation
and press Enter.
The Communication Configuration Menu appears.
7. Select option 4, SNA feature profiles, and press Enter.
The SNA Feature Configuration panel appears.
8. Select Data Link Control (DLC) Profiles and press Enter.
A message box appears showing the DLC types.
9. Select option 3, Token-Ring or Other LAN type... and press Enter.
The DLC Adapters and Operations panel appears.
10. Select the two options Adapter 0 and Create and press Enter.
The Create/Change IBM Token-Ring Network DLC Profile panel appears.
Appendix A. SNA Advanced Configuration 70
IBM CONFIDENTIAL Extended Services Driver S1A246 71 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
11. Use all of the default values displayed for the fields on this panel, except for the
C&SM LAN ID, where you must provide a value. Press Enter.
The SNA Feature Configuration panel appears.
12. Select SNA network definitions and press Enter.
The SNA Definitions Options panel appears.
13. Select Create/Change and press Enter. An informational message box appears.
Press Enter.
The Local Node Characteristics panel appears.
14. For the Required Features, specify the following:
Network ID
The network ID is the same as that supplied in the SNA base of previous
versions of Communications Manager. WARNING: The network ID
CANNOT be blanks.
Local node name
The local node name is the same as that as that supplied for the PU or Control
Point in previous versions of Communications Manager.
Node type
Accept the default node type of end node - no network node server.
For the optional features:
? Use the default supplied for the Local Node ID.
? Use the same name you supplied for Local Node Name for the Local Node
Alias Name, except enter the name in all caps.
? Use the default supplied for the Activate Attach Manager at startup
(selected).
Select the OK push button and press Enter. The Basic SNA information
message panel appears. Press Enter. The SNA Network Definitions Selection
panel appears.
15. Select Connections and select the Configure push button.
The CM SNA Connections panel appears.
16. Select To Primary Host and press Enter.
The Adapter List panel appears.
17. Select IBMTRNET and press Enter.
The "Creating a Connection to a To Primary Host" panel appears.
18. Use the default value supplied for the Link Name.
Supply values for the Partner Network ID, Partner Node Name, and LAN
Destination Address fields.
Select the Define Partner LUs... push button.
The "Creating Partner LU " panel appears.
19. .Supply values for the LU name, and Alias fields (the Alias value must be in all
caps) and then select the Add pushbutton.
Appendix A. SNA Advanced Configuration 71
IBM CONFIDENTIAL Extended Services Driver S1A246 72 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
The LU name and alias you selected are added to the list box.
Select the OK push button.
The Creating a Connection to a To Primary Host panel appears.
20. Select the OK push button to exit from this panel.
The CM SNA Connections panel appears.
21. Select the Configuration action bar choice and then select the Additional SNA
Features... pulldown choice.
The CM Additional SNA Features panel appears.
22. Create a mode profile by selecting the Modes choice and pressing Enter.
The Creating a Mode Definition panel appears.
23. Supply the following values for the fields shown:
Mode name: (supply a mode name)
Class of service: #CONNECT (the default)
Mode session limit: 64
Minimum contention winners: 32
Receive pacing window: 7
Select Default RU size.
Select the OK push button.
The CM Additional SNA Features panel appears.
24. Select the File action bar choice and then select the Save and exit pulldown
choice.
The SNA Network Definitions Selection panel appears.
25. Select the Exit push button.
The SNA Feature Configuration panel appears.
26. Press F3 to exit from the SNA Feature Configuration panel.
The Communication Configuration Menu appears.
27. Select option 6, LAN Adapter and Protocol Support and press Enter.
The Options panel appears.
28. Select Configure workstation (the default) and then select the OK pushbutton.
A message appears stating that the configuration file is being read, and then the
Configure Workstation panel appears.
29. Select the OK pushbutton to use all of the defaults shown on this panel.
The Options panel appears.
30. Select Configuration complete (the default) and then select the OK pushbutton.
The Communication Configuration Menu appears.
Appendix A. SNA Advanced Configuration 72
IBM CONFIDENTIAL Extended Services Driver S1A246 73 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
31. Select option 7, 5250 workstation feature profiles and press Enter.
The 5250 Workstation Feature Configuration panel appears.
32. Select option 1, Terminal profiles... and press Enter.
The Profile Operations panel appears.
33. Select option 3, Create... and press Enter. The Specify Terminal Profile Names
panel appears.
34. Use the default supplied for the Model name (M1) and enter TERM in the
Profile Name field. Press Enter.
The Create/Change Terminal Options panel appears.
35. Select option 1, Common terminal options and press Enter.
The Common Terminal Options panel appears.
36. Accept all the default values for the terminal options and press Enter.
The Specify Workstation ID panel appears.
Accept the defaults and leave the Workstation ID field blank. Press Enter.
The Create/Change Terminal Options panel appears.
37. Press F3 to exit from the Create/Change Terminal Options panel.
The 5250 Workstation Features Configuration panel appears.
38. Select option 3, Specify APPC LU alias... and press Enter.
The Specify APPC LU Alias panel appears.
39. Type the LU alias in the "APPC LU alias" field and press Enter. (This is the
same value as the one supplied for the Local Node Name in step 14 on
page 71.)
40. The 5250 Workstation Features Configuration panel appears.
41. Select option 4, Session assignments and press Enter.
The 5250 Session Selection panel appears.
42. Select Session Number 1 and press Enter.
The 5250 Terminal/Printer Session Assignments panel appears.
43. Supply the values for the following fields and press Enter.
5250 Workstation Feature profile name
Use the profile value "TERM", as shown in step 34.
APPC partner LU alias
Use the same value you used for supplying an alias in step 19 on page 71.
APPC mode name
Use the same value you used for supplying a mode name in step 23 on page 72.
Short session ID
Accept the default value for the short session ID (A).
The 5250 Session Selection panel appears.
Appendix A. SNA Advanced Configuration 73
IBM CONFIDENTIAL Extended Services Driver S1A246 74 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
44. Press F3 to exit the 5250 Session Selection panel.
The 5250 Workstation Feature Configuration panel appears.
45. Press F3 to exit the 5250 Workstation Feature Configuration panel.
The Communication Configuration Menu panel appears.
46. To verify your configuration file, press F10 and select the Verify action bar
choice. Then select option 1, Run verify from the pulldown.
A message box appears stating that the verification of the configuration file is in
process. After the configuration file is verified, a message box appears that
states the options for restarting and using the new configuration.
47. Press Enter. Another message box appears stating that Communications
Manager must be restarted to use the new configuration.
48. Press Enter. The Communication Configuration Menu panel appears.
49. Press F3 to exit from the Communication Configuration Menu. The
Communications Manager Main Menu" panel appears.
50. Press F3 to exit from the Communications Manager.
A message box appears notifying that you are exiting from Communications
Manager and asks you if you are sure.
51. Select option 1, Yes and press Enter.
Another message panel appears stating that the Communications Manager
features have ended successfully.
52. Press F3 to exit the Communications Manager.
53. Restart Communications Manager using the new configuration file.
(example: C>start cm 5250adv)
Switch to the task list to access the Communications Manager Main Menu.
54. Select option 1, Start emulators and press Enter.
The Start Communications panel appears.
55. Select option 4, 5250 Work Station Feature and press Enter.
The Select 5250 Work Station Feature Sessions to Start panel appears.
56. Select ALL and press enter.
The Logon panel appears.
57. Type the UPM user ID and password in the appropriate fields and press Enter.
The 5250 host sign on screen appears for the active 5250 session.
Appendix A. SNA Advanced Configuration 74
IBM CONFIDENTIAL Extended Services Driver S1A246 75 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
A.2.1 5250ADV .NDF File Example
DEFINE_LOCAL_CP FQ_CP_NAME(NETNAME.NODENAME )
CP_ALIAS(ALIASNAM)
NAU_ADDRESS(INDEPENDENT_LU)
NODE_TYPE(EN)
NODE_ID(X'00000')
HOST_FP_SUPPORT(YES)
HOST_FP_LINK_NAME(LINK0001);
DEFINE_LOGICAL_LINK LINK_NAME(LINK0001)
FQ_ADJACENT_CP_NAME(USIBMTH.AUSHATT )
ADJACENT_NODE_TYPE(LEN)
DLC_NAME(IBMTRNET)
ADAPTER_NUMBER(0)
DESTINATION_ADDRESS(X'400033345678')
CP_CP_SESSION_SUPPORT(NO)
ACTIVATE_AT_STARTUP(YES)
LIMITED_RESOURCE(USE_ADAPTER_DEFINITION)
LINK_STATION_ROLE(USE_ADAPTER_DEFINITION)
SOLICIT_SSCP_SESSION(YES)
EFFECTIVE_CAPACITY(USE_ADAPTER_DEFINITION)
COST_PER_CONNECT_TIME(USE_ADAPTER_DEFINITION)
COST_PER_BYTE(USE_ADAPTER_DEFINITION)
SECURITY(USE_ADAPTER_DEFINITION)
PROPAGATION_DELAY(USE_ADAPTER_DEFINITION)
USER_DEFINED_1(USE_ADAPTER_DEFINITION)
USER_DEFINED_2(USE_ADAPTER_DEFINITION)
USER_DEFINED_3(USE_ADAPTER_DEFINITION);
DEFINE_PARTNER_LU FQ_PARTNER_LU_NAME(USIBMTH.AUSHATT )
PARTNER_LU_ALIAS(AUSHATT)
MAX_MC_LL_SEND_SIZE(32767)
CONV_SECURITY_VERIFICATION(NO)
PARALLEL_SESSION_SUPPORT(YES);
DEFINE_PARTNER_LU_LOCATION FQ_PARTNER_LU_NAME(USIBMTH.AUSHATT )
WILDCARD_ENTRY(NO)
FQ_OWNING_CP_NAME(USIBMTH.AUSHATT )
LOCAL_NODE_NN_SERVER(NO);
DEFINE_MODE MODE_NAME(QPCSUPP )
COS_NAME(#CONNECT)
DEFAULT_RU_SIZE(YES)
RECEIVE_PACING_WINDOW(7)
MAX_NEGOTIABLE_SESSION_LIMIT(32767)
PLU_MODE_SESSION_LIMIT(64)
MIN_CONWINNERS_SOURCE(32);
DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES)
DEFAULT_MODE_NAME(BLANK)
MAX_MC_LL_SEND_SIZE(32767)
DIRECTORY_FOR_INBOUND_ATTACHES(*)
Appendix A. SNA Advanced Configuration 75
IBM CONFIDENTIAL Extended Services Driver S1A246 76 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED)
DEFAULT_TP_PROGRAM_TYPE(BACKGROUND)
DEFAULT_TP_CONV_SECURITY_RQD(NO)
MAX_HELD_ALERTS(10);
START_ATTACH_MANAGER;
A.3 Advanced Configuration for 3270 Over Token-Ring
1. Copy and rename the ACSCFGUS.CFG file in the \CMLIB directory to create
your new configuration file.
(example: C>copy acscfgus.cfg 3270tr.cfg)
2. Restart Communications Manager using this file.
(example: C>start cm 3270tr)
3. Switch to the task list to access the Communications Manager Main Menu.
The Communications Manager Main Menu appears.
4. Select the Advanced action bar item and then select the Configuration pulldown
choice. Press Enter.
A message box appears displaying the name of the configuration file.
5. Press Enter. The Specify Configuration Usage panel appears.
6. Select the first option if you intend to use this configuration on this workstation..
The Communication Configuration Menu appears.
7. Select option 3, 3270 feature profiles and press Enter. The 3270 Feature
Configuration panel appears.
8. Select option 3, IBM Token-Ring or Other LAN type... and press Enter. The
Profile Operations panel appears.
9. Select option 2, Create/Change and press Enter.
The Create/Change 3270 Profile panel appears.
10. Select option 1, Connection.
The Specify Link Information panel appears.
11. Select Adapter 0 (the default) for the Adapter number field and supply the
destination address in the Destination Address field and press Enter.
The Create/Change 3270 Profile panel re-appears.
12. Select sessions to configure for a terminal.
The Create/Change 3270 Logical Terminal Profile panel appears.
Use the default values supplied for all of the fields on this panel and supply a
session ID and LU Local Address.
Press F3 two times to return to the Communication Configuration Menu. You
will receive a warning that the DLC must be configured; press Enter. Select
option 4, SNA Feature Profiles and press Enter.
Appendix A. SNA Advanced Configuration 76
IBM CONFIDENTIAL Extended Services Driver S1A246 77 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
The SNA Feature Configuration panel appears.
13. Select Data Link Control (DLC) Profiles and press Enter.
A message box appears showing the DLC types.
14. Select option 3, Token-Ring or Other LAN type.. and press Enter.
The DLC Adapters and Operations panel appears.
15. Select the two options Adapter 0 and Create and press Enter.
The Create/Change IBM Token-Ring Network DLC Profile panel appears.
16. Use all of the default values displayed for the fields on this panel, except for the
C&SM LAN ID, where you must provide a value. Press Enter.
The SNA Feature Configuration panel appears.
17. Select SNA network definitions and press Enter.
The SNA network definitions options panel appears. Select Create/Change, and
press enter.
The "Creating Basic SNA Node Information" panel appears.
18. Select OK.
The Local Node Characteristics panel appears.
19. For the Required Features, specify the following:
Network ID
The network ID is the same as that supplied in the SNA base of previous
versions in Communications Manager. WARNING: The Network ID cannot
be blanks.
Local node name
The local node name is the same as that as that supplied for the PU or Control
Point in previous versions of Communications Manager.
Node type
Accept the default node type of end node - no network node server.
For the optional features:
? Use the default supplied for the Local Node ID.
? Use the same name you supplied for Local Node Name for the Local Node
Alias Name, except enter the name in all caps.
? Select Activate Attach Manager at startup.
Select the OK push button and press Enter.
You will receive an informational message on the Basic SNA Node Information
Created. Press the OK push button.
You will see the SNA Network Definitions Selection. Select the Exit push
button.
The SNA Feature Configuration panel appears.
20. Select F3 to exit from this panel.
The Communication Configuration Menu appears.
Appendix A. SNA Advanced Configuration 77
IBM CONFIDENTIAL Extended Services Driver S1A246 78 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
21. Select option 6, LAN Adapter and Protocol Support and press Enter.
The Options screen appears.
22. Select Configure Workstation and press Enter.
The Configure Workstation panel appears.
23. Select the following on this panel:
? Select IBM Token-ring Adapters from Network Adapters.
A pop-up screen appears showing the adapters in the current configuration.
?
Select IBM IEEE 802.2 from Protocols.
A pop-up screen appears showing the current configuration for this item.
At this point, you can either:
? Select OK to complete configuration (and use the supplied defaults).
Note: If you choose this action, you can bypass step 24.
? Highlight the IBM Token-ring Adapters choice in the Current
Configuration box and select the Edit push button to edit the parameters
you created.
24. Use the edit box to edit the parameters for the token-ring adapters or the IBM
IEEE 802.2 entries.
Select OK when you are finished editing.
25. Select OK to exit the Configure Workstation panel.
The Options panel appears.
26. Select Configuration complete (the default).
The Communication Configuration panel appears.
27. Select the Verify action bar choice and then select the Run Verify pulldown
choice to verify the configuration file.
Note: A screen may appear stating that inconsistencies were found. If this occurs,
access the message log to view the messages and perform the following steps. For
example, you may be asked to do a REINST if the features you configured are not
installed yet.
1. Stop Communications Manager and type the command at the command REINST
prompt. This action restarts Communications Manager using the configuration
file you created.
2. On the REINST screen, select Install Additional Features and press Enter.
3. Select LAN Adapter and Protocol Support, for example, if this is the feature
which needs to be installed.
Appendix A. SNA Advanced Configuration 78
IBM CONFIDENTIAL Extended Services Driver S1A246 79 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
A.3.1 3270TR .NDF File Example
DEFINE_LOCAL_CP FQ_CP_NAME(NETNAME.NODENAME )
CP_ALIAS(ALIASNAM)
NAU_ADDRESS(INDEPENDENT_LU)
NODE_TYPE(EN)
NODE_ID(X'00000')
HOST_FP_SUPPORT(NO);
DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES)
DEFAULT_MODE_NAME(BLANK)
MAX_MC_LL_SEND_SIZE(32767)
DIRECTORY_FOR_INBOUND_ATTACHES(*)
DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED)
DEFAULT_TP_PROGRAM_TYPE(BACKGROUND)
DEFAULT_TP_CONV_SECURITY_RQD(NO)
MAX_HELD_ALERTS(10);
START_ATTACH_MANAGER;
A.4 Advanced Configuration for 3270 Gateway
1. Copy and rename the ACSCFGUS.CFG file in the \CMLIB directory.
(example: ) C>copy acscfgus.cfg 3270gw.cfg
2. Restart Communications Manager using this file.
(example: ) C>start cm 3270gw
3. Switch to the task list to access the Communications Manager Main Menu.
4. Select the Advanced action bar item and then select the Configuration pulldown
choice. Press Enter.
A message box appears displaying the name of the configuration file.
5. Press Enter.
The Specify Configuration Usage panel appears.
6. Select the first option if you intend to use this configuration on this workstation.
The Communication Configuration Menu appears.
7. Select option 3, 3270 feature profiles, and press Enter. The 3270 Feature
Configuration panel appears.
8. Select option 2, SDLC... and press Enter.
The Profile Operations panel appears.
9. Select option 2, Create/Change and press Enter.
The Create/Change 3270 Profile panel appears.
10. Select option 1, Connection, and press Enter. The Select SDLC Adapter panel
appears.
11. Select option 1, Adapter 0 and press Enter. The Create/Change 3270 Profile
panel re-appears.
Appendix A. SNA Advanced Configuration 79
IBM CONFIDENTIAL Extended Services Driver S1A246 80 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
12. Select the sessions to configure for the terminal. The Create/Change 3270
Logical Terminal Profile panel appears. Select Profile type panel appears.
Select Option 1, Terminal and press Enter.
13. Use the default values supplied for all of the fields on this panel and supply the
values for the following fields:
? Session ID/LU name
? LU local address.
14. Press Enter to return to the Create/Change 3270 Profile.
15. Press F3 two times to return to the Communication Configuration Menu.
A warning message appears stating that an appropriate DLC must be configured
before 3270 emulation can be used.
16. Press Enter to return to the Communication Configuration Menu.
17. Select option 4, SNA Feature Profiles and press Enter. The SNA feature
configuration panel appears.
18. Select Data Link Control (DLC) profiles... and press Enter. A message box
appears showing the DLC types.
19. Select option 1, SDLC... and press Enter. The DLC Adapters and Operations
panel appears.
20. Select the two options Adapter 0 and Create and then press Enter. The
Create/Change SDLC DLC Adapter Profile panel appears.
21. Use all of the default values displayed for the fields on this panel, except for the
Free unused link field. Select No for this field and press Enter. The Specify
Data Set Ready Timeout panel appears.
22. Accept the default value of 5 minutes and press Enter. The Specify Negotiable
Link Station Data panel appears.
23. Accept the defaults for the fields on this panel and press Enter.
The SNA Feature Configuration panel re-appears.
24. Select SNA network definitions and press Enter.
The SNA network definitions options panel appears. Select Create/Change, and
press Enter.
An informational message appears on Creating basic SNA node information.
25. Select the OK pushbutton to proceed to the Local Node Characteristics
configuration panel.
26. For the Required Features, specify the following:
Network ID
The network ID is the same as that supplied in the SNA base of previous
versions of Communications Manager. WARNING: The Network ID cannot
be blanks.
Local node name
The local node name is the same as that as that supplied for the PU or Control
Point in previous versions of Communications Manager.
Appendix A. SNA Advanced Configuration 80
IBM CONFIDENTIAL Extended Services Driver S1A246 81 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Node type
Accept the default node type of End Node - No Network Node Server.
For the Optional Features:
?
Use the default supplied for the Local Node ID.
? Use the same name you supplied for Local Node Name for the Local Node
Alias Name, except enter the name in all caps.
27. Select the OK push button and press Enter.
An informational message appears on the Basic SNA information created. Select
the OK push button and press enter.
The SNA Network Definition Selection panel appears. Select the Exit push
button and press Enter.
The SNA Feature Configuration panel appears.
28. Select SNA gateway profiles... and press Enter. The Select Gateway Profile
Type panel appears.
29. Select option 1, Host Connection... and press Enter. The Profile Operations
panel appears.
30. Select option 3, Create and press Enter. The Create/Change SNA Gateway
Host Connection Profile (1 of 2) panel appears.
31. Set the values for the following fields and press Enter:
DLC type SDLC (default)
Permanent connection Yes
Auto-logoff timeout (minutes) 61
The Select Adapter panel appears.
32. Select option 1, Adapter 0 and press Enter. The Create/Change SNA Gateway
Host Connection Profile (2 of 2) panel appears.
33. Leave this panel blank and press Enter. The SNA Feature Configuration panel
returns.
34. Select SNA gateway profiles... again and press Enter. The Select Gateway
Profile Type panel appears.
35. Select option 2, Workstation LU... and press Enter. The Profile Operations
panel appears.
36. Select option 3, Create and press Enter. The Specify Profile Names panel
appears.
37. Accept the default for the Model profile name field (M6) and type ALICEWS1
in the profile name field. Press Enter. The Create/Change SNA Gateway
Workstation LU Profile panel appears.
38. Set the values for the following fields and press Enter:
Appendix A. SNA Advanced Configuration 81
IBM CONFIDENTIAL Extended Services Driver S1A246 82 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
LU name at workstation ALICEWS1
Comment (Optional)
PU name of workstation ALICEPU1
LU pooling Dedicated
LU local address at workstation (hex) *
Note: Enter the LU local address entered on the
Create/Change 3270 Logical Terminal Profile.
See 13 on page 80 for the
LU local address field.
DLC type SDLC
The Specify Dedicated LU Parameters panel appears.
39. Supply a value for the LU local address at host field and accept the default value
for the Auto-logoff field (NO). Press Enter. The Select Adapter panel appears.
40. Select option 1, Adapter 0 and press Enter.
The SNA Feature Configuration panel re-appears.
41. Press F3 to return to the Communication Configuration Menu.
42. Verify the configuration and re-start the Communications Manager to use the
new configuration.
Verify from action bar, and press enter.
Select Option 1, Run Verify and press enter.
A.4.1 3270GW .NDF File Example
A node definition file is built for you with the following set of default verbs:
DEFINE_LOCAL_CP FQ_CP_NAME(APPN.ATIG )
CP_ALIAS(atig )
NAU_ADDRESS(INDEPENDENT_LU)
NODE_TYPE(EN)
NODE_ID(X'00000')
HOST_FP_SUPPORT(NO);
DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES)
DEFAULT_MODE_NAME(BLANK)
MAX_MC_LL_SEND_SIZE(32767)
DIRECTORY_FOR_INBOUND_ATTACHES(*)
DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED)
DEFAULT_TP_PROGRAM_TYPE(BACKGROUND)
DEFAULT_TP_CONV_SECURITY_RQD(NO)
MAX_HELD_ALERTS(10);
Appendix A. SNA Advanced Configuration 82
IBM CONFIDENTIAL Extended Services Driver S1A246 83 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Appendix B. EHLLAPI Virtual Device Driver (VDD)
# *** NOTE ***
# The EHLLAPI VDD does not function correctly with the OS/2 SE 2.0 driver
# level 6.167. To use the EHLLAPI VDD, OS/2 2.0 level 6.605 must be used.
B.1 Overview
This IBM Extended Services for OS/2 driver contains a new EHLLAPI Virtual
Device Driver (VDD) to allow existing DOS HLLAPI applications to run in the
Virtual DOS Machine on the OS/2 2.0 operating system. This appendix gives the
information on how to use the EHLLAPI VDD.
The EHLLAPI Virtual Device Driver support is installed when you install
Communications Manager with a 3270 configuration file. The Installation of the
EHLLAPI VDD will enable the user to run existing DOS HLLAPI applications in
the OS/2 2.0 Virtual DOS Machine (VDM) environment using Extended Services
EHLLAPI with the Communications Manager.
Although an effort was made to be compatable with the Personal Communications
3270 EHLLAPI 2.0, some differences exist and are noted below.
It is recommended the DOS application be recompiled and linked to be executed in
the OS/2 environment if possible. This will enhance the overall performance of the
system and allow for inclusion of the many enhancements available in the
Communications Manager EHLLAPI.
B.2 Installation
The following statement should be added to the end of the CONFIG.SYS file (it
must follow the loading of physical device drivers):
? DEVICE=x:\CMLIB\VHAPI.OS2
(where x is the logical drive on which Communications Manager is installed)
Note: Machine must be restarted after making changes to CONFIG.SYS.
Appendix B. EHLLAPI Virtual Device Driver (VDD) 83
IBM CONFIDENTIAL Extended Services Driver S1A246 84 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
B.3 Usage
Bring up the Communications Manager and start 3270 communications. Establish
the same conditions in the host session window as are required in the DOS
emulator session by the DOS HLLAPI application. Create an OS/2 2.0 VDM
Window and start the DOS HLLAPI application.
B.4 Compatability (With Personal Communications 3270 2.0)
Appendix B. EHLLAPI Virtual Device Driver (VDD) 84
IBM CONFIDENTIAL Extended Services Driver S1A246 85 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Deviations:
Because of existing differences between the Per Com and OS/2 3270
emulators there are some differences in the EHLLAPI support:
1. ASCII mnemonic differences
- The following mnemonics are not supported by PER COM 3270 2.0.
However, since the OS/2 emulator generates them they may be
received by EHLLAPI applications running in the DOS box under OS/2 2.0)
1. @q End
2. @A@D Word Delete
3. @A@L Cursor Left fast
4. @A@N Get Cursor
5. @A@O Locate Cursor
6. @A@Z Cursor Fast Right
7. @A@9 Reverse Video
8. @A@b Underscore
9. @A@c Reset Reverse video
10. @A@d Red
11. @A@e Pink
12. @A@f Green
13. @A@g Yellow
14. @A@h Blue
15. @A@i Turquoise
16. @A@j White
17. @A@l Reset Host colors
18. @/ Overrun of queue (get key function only)
19. @S@T Jump to Task Mgr (Extended Services 1.0)
- The following lists differences between mnemonics supported by
both EHLLAPIs
1. @< Backspace
- Per Com treats this as a destructive backspace
- OS2 treats this as a non destructive backspace
note: When received by an EHLLAPI application running in the
DOS box under OS/2 2.0 this mnemonic should be treated as
a non destructive backspace.
- The following mnemonics are not supported by EHLLAPI on a 3270
session
1. @S@A Erase EOL
2. @S@B Field Advance
3. @S@C Field Backspace
4. @S@D Valid Backspace character
5. @r@t Pause
2. Copy OIA content
1. Column 21
- Per Com returns value of 0xF6
- OS2 returns value of 0x20
note: The value of 0x20 will be returned in the OS/2 2.0
DOS box.
2. Columns 61-63
Appendix B. EHLLAPI Virtual Device Driver (VDD) 85
IBM CONFIDENTIAL Extended Services Driver S1A246 86 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
- Per Com will not return printer information
note: Values in these columns may be returned in the OS/2
2.0 DOS box.
3. Group 3 Shift State
- bit 2 CAPS is not returned by OS2
(bit 0 set for both upper case and CAPSLOCK in OS2 with
bit 2 reversed)
note: Bit 2 will continue to be reserved in the OS/2 2.0
DOS box.
4. Group 8 byte 1 Input Inhibited
- bit 6 Device not working not returned by Per Com
note: This bit may be set in the OS/2 2.0 DOS box.
5. Group 8 byte 2
- bit 1 OS2 Terminal Wait not returned by Per Com
note: This bit may be set in the OS/2 2.0 DOS box.
6. Group 8 byte 3
- bit 1 Operation unauthorized not returned by Per Com.
- bit 2 Operation unauthorized minus function not
returned by Per Com.
note: These bits may be set in the OS/2 2.0 DOS box.
7. Group 10 Highlight #2
- bit 0 Selected not returned by Per Com
note: This bit may be set in the OS/2 2.0 DOS box.
8. Group 11 Color #2
- bit 0 Selected not returned by Per Com
note: This bit may be set in the OS/2 2.0 DOS box.
9. Group 13 Printer Status
- This group is reserved in Per Com
note: This group may be set in the OS/2 2.0 DOS box.
10. Group 14 Graphics
- bit 0 Graphics cursor not returned by OS2
note: This bit will not be returned in the OS/2 2.0 DOS
box.
3. Presentation Space character/field attributes translated under
the XLATE parm do not match (both are supposed to be CGA format).
Note: The purpose of this function is to provide a
Char/Attribute buffer to be displayed on the applications
Appendix B. EHLLAPI Virtual Device Driver (VDD) 86
IBM CONFIDENTIAL Extended Services Driver S1A246 87 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
screen that reflects exactly the text and colors of the
host presentation space. Since the Per Com implementation
performs this function incorrectly, the attributes
returned under OS/2 will be returned without alteration.
4. Host PS null characters (0x00) are translated to blanks (0x20)
under Per Com. They are not translated under OS/2. This may
affect searches (in Per Com EHLLAPI appls) for character strings
that include blanks that are null characters under OS/2.
5. Host Presentation Space sizes supported are different between the
two emulators. A user running a Per Comm EHLLAPI application
under OS/2 2.0 must make sure that he doesn't configure a PS mod
type that is larger than the Per Com application can handle. PS
sizes for Per Com are between 1920 (24x80) and 3564 (27x132).
Sizes for OS/2 are between 1920 and 7446 (146x51).
note: OS/2 2.0 DOS will support up the the maximum OS/2 size if
the application can handle it.
6. Storage Manager is different between the APIs.
Note: Setup of Storage Manager during configuration is not
required under OS/2. The maximum of 10 K bytes is
automatically preallocated outside of the DOS heap.
7. Considerations for using functions 90 & 91 in PER COM pub do not
apply.
8. PERCOM EHLLAPI messages are not generated under OS/2.
9. In OS/2 Trace is sent to file. In PER COM it is sent to screen.
Note: Under OS/2 2.0 OS/2 trace rules will be applied.
10. Send/Receive: PM window will be created to display status
messages (non Quiet mode).
11. Send/Receive: PS Position parameter specification of 0 for
Current directory is not supported in PERCOM.
Note: Under OS/2 2.0 a specification of 0 will be supported if
received.
12. As in Per Com, the DOS EHLLAPI application running under OS/2
2.0 will run on the interrupt thread. This means that hitting
Ctrl-C and Ctrl-Break, will have no effect when the thread is
suspended, waiting for an EHLLAPI function to complete.
However, under OS/2 2.0 the user may optionally close the DOS
window running the EHLLAPI application even when the thread is
suspended waiting for a function to complete (Warning: in this
case the 3270 emulation resources remain allocated until the
pending EHLLAPI function issued by the departed DOS application
is complete).
Appendix B. EHLLAPI Virtual Device Driver (VDD) 87
IBM CONFIDENTIAL Extended Services Driver S1A246 88 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
13. Functions 41-43 (Close Click Intercept) and 101-106 (Windowing)
are not supported under Per Com.
note: These functions will not be supported under OS/2 2.0.
Appendix B. EHLLAPI Virtual Device Driver (VDD) 88
IBM CONFIDENTIAL Extended Services Driver S1A246 89 OS/2 LS V2.0 Driver 281 on OS/2 2.0 Driver 6.167
Appendix C. Communications Manager Stop API
C.1 Overview and Usage
Included in this driver of Communications Manager is a new API to stop the
Communications Manager. The following description is written using the same
format as the OS/2 Control Program, Programming Reference. For additional
information, see the OS/2 Control Program Programming Reference which is a
volume of the IBM OS/2 Programmer's Toolkit version 1.2.
CmkDeactivateService -
Request to Stop the Communication Manager
This call will have the Communications Manager start exit processing
when the Main Menu is displayed.
CmkDeactivateService (StopType, Service, Reserved_1, Reserved_2, rc)
PARAMETERS
StopType(USHORT) - input
Type of stop process requested.
StopType codes:
* CMK_SOFT 0 - Exit when Complete
* CMK_HARD 1 - Exit Immediate
Service(ULONG) - input
Service number of Communication Manager
* CMK_ALL_FEATURES 1 - Stop Communications Manager
Reserved_1(ULONG) - input
Reserved and should be set to 0
Reserved_2(USHORT) - input
Reserved and should be set to 0
rc(USHORT) - return
Return code descriptions are:
0 CMK_SUCCESSFUL
22 CMK_ERR_INVALID_SERVICE
23 CMK_ERR_SYSTEM_ERROR
REMARKS
This call will request the Communications Manager to start exit
processing. The CMK_SOFT stop is the equivalent of selecting
"Exit when Complete" from the EXIT pulldown on the Communications
Manager Main Menu. The CMK_HARD stop corresponds to the "Exit
immediately" option.
Processing of the stop request will only occur when the Main Panel
is being displayed, or when a user returns to the Main Panel after
preforming some action like configuration.
Appendix C. Communications Manager Stop API 89
�
INDBC167.DOC
Restrictions and Installation Instructions for
IBM Extended Services for OS/2
Database Manager Clients Feature (Driver S1A246)
October 18, 1991 2:45 p.m.
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
This document contains information of a proprietary nature. ALL INFORMATION CONTAINED
HEREIN SHALL BE KEPT IN CONFIDENCE. None of this information herein shall be divulged to
persons other than IBM employees authorized by the nature of their duties to receive such information, or
individuals or organizations who are authorized in writing in accordance with existing policy regarding release
of company information. This material, if exported from the United States, is shipped under General
License GTDR.
Restrictions and Installation Instructions for
IBM Extended Services for OS/2
Database Manager Clients Feature (Driver S1A246)
October 18, 1991 2:45 p.m.
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2.0 Database Manager Clients Restrictions/Limitations ............ . . . 2
3.0 Installation Instructions ............. . . . . . . . . . . . . . . . . . . 5
4.0 Applying Patches to the OS/2.NETBIOS.Client . . . . ....... . . . . 6
4.1 Instructions for Applying Database Manager Client.Patches . . . . . . . . 6
Contents ii
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
1.0 Introduction
This document provides the driver restrictions and installation instructions for the
Database Manager Clients feature of the IBM Extended Services for OS/2 program.
The feature consists of the following code and publications:
1. Diskettes (3 1/2" format):
? 2 OS/2 NETBIOS Database Client diskettes
? 2 DOS Database Client/DOS Windows Database Client diskettes
? 1 PC LAN Support Program diskette (** shipped with the LAN Server
V2.0 program)
2. Publications
? Guide to Database Manager Clients
? Network Administrator's Guide (** part of Extended Services
Administrator's Ship group)
? LAN Adapter and Protocol Support Configuration Guide (** part of
Extended Services Administrator's Ship group)
? PC LAN Support Program User's Guide (** part of LS V2.0 ship group
sent with previous Extended Services/LAN Server driver)
Introduction 1
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
2.0 Database Manager Clients Restrictions/Limitations
The following restrictions/limitations apply to the Database Manager Clients feature
for this driver.
?
OS/2 NETBIOS Client Installation/Custom Diskette Creation:
?You must have at least 500K Bytes available on the C: drive for use by the
OS/2 NETBIOS Client install program. If OS/2 is booted from a drive
other than C:, the C: drive is still used for temporary working space for the
install program.
# ?If OS/2 is booted from a drive other than C:, the installation of the OS/2
# NETBIOS Client will not work. CONFIG.SYS is incorrectly updated
# (causing multiple error messages during IPL) and several files do NOT get
# installed.
# The workaround, if you plan to install the client from an OS/2 system
# which has been booted from a drive other than C:, is as follows:
# ?Edit the INSTALL.CMD file on the OS/2 NETBIOS Database Client
# Installation Diskette #1:
# Change the designated drive in line PKUNZIP2 REQINSTR.ZIP C:\
# -o -d 1>NUL 2>NUL to the drive you have booted your system
# from.
?If you are attempting to install the OS/2 NETBIOS Client on top of a
previous version of Extended Services, you must first erase the file
x:\IBMLVL.INI (where x: is the drive which OS/2 is booted from).
?During Install, the ONLY valid network adapters are the ones currently
listed in the Guide to Database Manager Clients under "Software and
Hardware Requirements. The menu that comes up during Install to allow
you to select your network adapter incorrectly lists more adapters than can
validly be selected.
?You CANNOT create a Custom Build Diskette for an OS/2 SE V2.0
workstation. The diskette that gets created will ONLY work on OS/2 SE
V1.30.1 workstations.
?After creating a custom diskette, you are told to remove the diskette. If you
do so BEFORE you press 'enter', you will get a "drive not ready" message.
Leave the custom diskette in drive a: until after pressing 'enter'.
?During Install, after selection of the network adapter, the "percentage of
installation complete" indicator is not correctly displayed. (** OS/2 SE V2.0
Level 6.605 ONLY)
?During Install and/or Custom Diskette creation, 'HELP' does not work
from the following panels/menus:
?Incompatible Versions
?File Backup
?Source Drive
Database Manager Clients Restrictions/Limitations 2
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
?On the panel asking you to check the terms and conditions of the licensing
agreement, there is a 'HELP' pushbutton, but it has no effect.
?On the Custom Diskette Panel, 'HELP' states that you will need a second
diskette, however you do not always need one.
? DOS Database Client/DOS Windows Database Client:
?You CANNOT run any DOS Database client or DOS Windows Database
client applications in OS/2's DOS Compatibility mode (i.e., from the DOS
box)
? There are NO online helps for Database Manager. You will need to refer to the
Extended Services for OS/2 Messages and Error Recovery Guide, Database Only
for the explanation of error messages.
? Corrections to Guide to Database Manager Clients
1. Pages 4-3, and 4-4:
?Steps 1 and 2 should be replaced by:
Type the following at the command prompt and press Enter: INSTDB
2. Page 3-7
?In step 8 the Workstaion Name Panel is displayed instead of the
Installation and Configuration Panel.
?Step 9 should be replaced with:
Type in the name of your workstation and select OK or press enter.
The "Copying files - Please wait" popup is displayed. While the system
copies files, the percentage of the diskette that is copied and the amount
of time elasped is continually updated on this panel. The Options panel
is displayed next.
?Step 10 should be removed.
?In steps 13 and 14 the cursor will not automatically move; it must be
tabbed or selected via a mouse.
?Step 14 should be replaced with:
Select Add to accept IBM OS/2 NETBIOS. Your selection (IBM OS/2
NETBIOS) is displayed in the current configuration field (beneath the
Network Adapters field). When all options are complete move to OK
and press enter. The Options panel is now displayed.
?Step 15 should be replaced with:
When all configuring is complete, press Configuration Complete. A
warning panel asking you to check the terms and conditions
information to verify that you can copy the network driver information
is displayed.
3. Appendix B, page B-3, "DBM Catalog NETBIOS Node"
?The syntax diagram has an error. You need to precede the adapter
number (0 or 1) with the keyword 'ADAPTER' or you will get an
error.
Database Manager Clients Restrictions/Limitations 3
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
Database Manager Clients Restrictions/Limitations 4
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
3.0 Installation Instructions
The installation instructions for this feature are included in the Guide to Database
Manager Clients publication which has been included with this driver shipment.
Once you have read and understood ALL restrictions and limitations that apply to
this driver, please refer to the above-mentioned publication for all details of
installing and configuring your client workstations.
Important Installation Note
If you are installing an OS/2 NETBIOS Client, you MUST apply some patches
after you complete the installation. After you have completed the installation
steps in the Guide to Database Manager Clients, return to this document and
follow the instructions in 4.0, 嗀pplying Patches to the OS/2 NETBIOS Client?
on page 6
Installation Instructions 5
IBM CONFIDENTIAL Database Manager Clients Driver S1A246
4.0 Applying Patches to the OS/2 NETBIOS Client
After your OS/2 NETBIOS Client is installed, you must apply the necessary
patches.
Note
This applies ONLY to OS/2 NETBIOS Clients; it DOES NOT apply to DOS
Database Client or DOS Windows Database Client.
4.1 Instructions for Applying Database Manager Client Patches
*** NOTEs: ***
1. In order for the patches to be applied correctly, you MUST take the steps
below after Database Manager Client installation is complete.
2. If you need to re-install the Database Manager Client, the patch process
MUST be repeated after the re-installation.
1. Insert the patch diskette #1 in drive A:
2. From the OS/2 command prompt, enter the following command.
Note: The replace command will replace files based upon the features you have
installed on your PC. If you have installed features which do not require any
patches, then the replace command may not replace any files.
? REPLACE A:\CMPATCH\*.* z:\IBMCOM /S
where z is the logical drive on which OS/2 is installed.
3. Insert patch diskette #2 in driver A:, and type the following:
a:dbclient x:
(where x is the drive on which the Database Manager client is installed) and
press Enter.
4. Remove the patch diskette.
# 5. Use the Desktop Manager Shutdown feature to stop and reboot your system, if
# you are using OS/2 SE V1.3 with Manufacturing Refresh 1.30.1. If you are
# using OS/2 SE V2.0 Level 6.167, you should move the mouse to a blank area of
# the workplace desktop (i.e., not on an object or folder) and press mouse button
# #2. From the pull-down that appears, select "Shutdown" and follow the
# directions.
Applying Patches to the OS/2 NETBIOS Client 6
�
INST6167.DOC
OS/2 32-Bit Operating System
Installation Guide
PRE-RELEASE COPY
October 10, 1991
First Edition October 1991 < *
The following paragraph does not apply to the United Kingdom or any
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION 嗀S IS?WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not apply
to you.
This publication could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time.
It is possible that this publication may contain reference to, or information
about, IBM products (machines and programs), programming, or services
that are not announced in your country. Such references or information
must not be construed to mean that IBM intends to announce such IBM
products, programming, or services in your country.
Requests for technical information about IBM products should be made to
your IBM Authorized Dealer or your IBM Marketing Representative.
+ Copyright International Business Machines Corporation 1991. All rights
reserved.
Note to U.S. Government Users ?Documentation related to restricted
rights ?Use, duplication or disclosure is subject to restrictions set forth
in GSA ADP Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
About This Book ..... . . . . . . . . . . . . . . . . . . . . . . . ix
How This Book is Organized. ....... . . . . . . . . . . . . . ix
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Chapter 1. Choosing an Installation.Procedure. ........ 1
Basic Installation. ..... . . . . . . . . . . . . . . . . . . . . . . . 3
Advanced Installation Choices. . . . ....... . . . . . . . . . 4
Running OS/2 2.0 and DOS on the Same System. . . . . . . . 4
Multiple Operating System Installation ........... . . . 6
Alternative Ways to Install. . . . ....... . . . . . . . . . . 6
Choosing an Advanced Installation.Procedure. ...... . 6
Special Note about Reconfigurable Diskette.Drives . . . . . 7
Chapter 2. Installing OS/2 2.0 as the Only Operating System . . 9
Setting Up Your Hard Disk. . . . ....... . . . . . . . . . . . . 9
Selecting the Operating System.Features . . . . . ...... . 12
Configuring the System ....... . . . . . . . . . . . . . . . . . 14
Viewing the Tutorial ....... . . . . . . . . . . . . . . . . . . . 16
Chapter 3. Adding OS/2 2.0 to a DOS System. . . . . . . . . . 17
Dual Boot Requirements ....... . . . . . . . . . . . . . . . . 18
Setting Up Your System for Dual Boot. . . . . ......... . 19
Making Sure Your DOS Directory Structure Is.Correct . . . 19
Creating or Modifying the AUTOEXEC.BAT and CONFIG.SYS
Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Installing the OS/2 Version 2.0 Operating.System .... . . . 22
Viewing the OS/2 Tutorial. . . . ....... . . . . . . . . . . . 24
Starting the Dual Boot Feature ......... . . . . . . . . . . 24
Chapter 4. Installing Multiple Operating Systems .... . . . . 25
How This Chapter is Organized ......... . . . . . . . . . . 25
An Overview of the Boot Manager ......... . . . . . . . . 26
Hard Disk Management . . . . ....... . . . . . . . . . . . . . 27
Planning for a Boot Manager.Setup. . ..... . . ... . . 31
Sample FDISK Screen. . . ..... . . . . . . . . . . . . . . . 33
Getting Ready for Installation ......... . . . . . . . . . 35
+ Copyright IBM Corp. 1991 iii
Starting the OS/2 2.0 Installation ......... . . . . . . . . . 36
Installing OS/2 2.0 on a New System. . . . . ......... 36
Installing OS/2 2.0 on an Existing System. . . . . . . . . . . 37
Setting Up Your Hard.Disk . . . ..... . . . . . . . . . . . . . 39
Deleting Existing Partitions ......... . . . . . . . . . . . 39
Creating the Boot Manager Partition. . . . . ......... 41
Creating Partitions for Operating Systems Other than OS/2
2.0 and for Logical Drives. . . . ....... . . . . . . . . . 42
Options Menu Choices ....... . . . . . . . . . . . . . . 44
Specifying Options . . . . . . . . . . . . . . . . . . . . . . . 46
Creating the Partition or Logical Drive for OS/2.2.0 . . . . 47
Specifying Options for the OS/2 2.0 Partition or Logical Drive 48
Saving Your Changes. . . ..... . . . . . . . . . . . . . . . 52
Continuing with OS/2 2.0 Installation. . . . . ......... . . 53
Selecting the Operating System.Features . . . . . .. . . . 53
Formatting Logical Drives. . . . ....... . . . . . . . . . . 53
Viewing the Tutorial. . . ..... . . . . . . . . . . . . . . . . . . 53
Installing Other Operating Systems ......... . . . . . . . 54
Chapter 5. Alternative Ways to.Install. ....... . . . . . . 59
Understanding the Response File Installation .......... 59
Modifying the Response File. . . . ....... . . . . . . . . . . 60
Installing OS/2 2.0 from a Source Other than Drive A . . . . . . 63
Redirecting the Installation ......... . . . . . . . . . . . 63
Setting Up an Alternative Installation.Source ..... . . . 64
Installing from a CD-ROM.Device . . . . ....... . . . . 64
Appendix A. Customizing the Operating.System ... . . . . 67
Features that You Can Change.or Add . ....... . . . . . . 67
Changing Your Setup or Adding Features. . . . . ........ 69
Appendix B. Diagnosing System Problems. . . . . ...... . 71
Recovering the CONFIG.SYS File. . . . ....... . . . . . . . 71
Recovering User and System INI.Files. . ..... . . ... . . 72
Recovering from Errors on the Hard Disk. . . . . ........ 74
Responding to Installation.Errors . . . . ....... . . . . . . 75
Making the Boot Manager Active. . . . ....... . . . . . . . 76
Appendix C. Examples of Installing OS/2 2.0 and Partitioning
Your Hard Disk ..... . . . . . . . . . . . . . . . . . . . . . . . 77
ivOS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Example 1: Creating a Primary Partition and a Logical Drive for
Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Example 2: Installing the Boot Manager, OS/2 2.0, and One
Additional Operating.System . . . . ....... . . . . . . . . 80
Example 3: Installing the Boot Manager, OS/2 2.0, and Two
Additional Operating Systems ......... . . . . . . . . . . 82
Example 4: Installing Boot Manager without Repartitioning the
Entire Hard Disk. . . ..... . . . . . . . . . . . . . . . . . . . 85
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Contents v
viOS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Notices
References in this publication to IBM products, programs, or
services do not imply that IBM intends to make these available in
all countries in which IBM operates. Any reference to an IBM
product, program or service is not intended to state or imply that
only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not
infringe any of IBM's intellectual property rights or other legally
protectible rights may be used instead of the IBM product,
program, or service. Evaluation and verification of operation in
conjunction with other products, programs, or services, except
those expressly designated by IBM, are the user's responsibility.
IBM may have patents or pending patent applications covering
subject matter in this document. The furnishing of this document
does not give you any license to these patents. You can send
license inquiries, in writing, to the IBM Director of Commercial
Relations, IBM Corporation, Purchase, NY 10577.
The following terms, denoted by a single asterisk (*), used in this
publication, are trademarks or service marks of the IBM
Corporation in the United States or other countries:
AIX IBM Operating System/2
OS/2 Personal System/2 Presentation Manager
PS/2 SAA Systems Application
Architecture
The following terms, denoted by a double asterisk (**), used in this
publication, are trademarks of other companies as follows:
Adobe Adobe Systems Incorporated
Adobe Type Adobe Systems Incorporated
Manager
Helvetica Linotype Company
Microsoft Microsoft Corporation
PostScript Adobe Systems Incorporated
Windows Microsoft Corporation
+ Copyright IBM Corp. 1991 vii
viii OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
About This Book
This book provides detailed instructions on installing the IBM *
*OS/2 operating system.
How This Book is Organized
This book has the following chapters and appendixes:
Chapter 1 provides you with an overview of the various
installation options.
Chapter 2 describes a basic installation procedure that installs
the OS/2 operating system as the only operating system on
your hard disk.
Chapter 3 describes the procedure for adding OS/2 2.0 to an
existing DOS system, so that you can switch between the
operating systems.
Chapter 4 describes how to partition your hard disk during
installation, so that you can install multiple operating systems.
Chapter 5 describes alternatives to the typical installation
procedure, such as using the same installation choices for
multiple computers.
Appendix A briefly describes ways to customize your system
after installation.
Appendix B describes how to recover from errors.
Appendix C provides four examples of partitioning the hard
disk during installation.
* Trademark of the IBM Corporation.
+ Copyright IBM Corp. 1991 ix
Related Information
Overview This book contains general information about the OS/2
operating system. It also shows you which
combinations of keys to use to perform specific actions.
Quick Reference
This card provides you with a very brief set of
instructions on how to start the installation of the OS/2
operating system. It is intended primarily for those who
want to accept most or all of the preselected choices
during installation. Note that the card provides only
limited instructions to get you started. If you want more
detailed information about installing the operating
system, use this book.
The following publication will be available and can be ordered
separately:
OS/2 Version 2.0 Remote Installation and Maintenance (GG24-3780).
This book provides detailed information about setting
up remote installations (such as installations across a
local area network).
xOS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Chapter 1. Choosing an Installation Procedure
This book describes how*to install the IBM * OS/2 Version 2.0
operating system. It describes the basic installation procedure,
which installs OS/2 2.0 as the only operating system on your hard
disk. It also describes advanced installation procedures, for those
who have unique system requirements (such as the need to install
multiple operating systems).
If you follow the basic installation procedure, you will be able to
**
run programs written for DOS and Microsoft Windows as well as
OS/2 programs--all under OS/2 2.0.
* Trademark of the IBM Corporation
** Trademark of the Microsoft Corporation.
+ Copyright IBM Corp. 1991 1
+----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+----------------------------+
2OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Basic Installation
This book describes the basic installation procedure as well as
more advanced procedures. Most people will find that the basic
installation procedure works best for them because their programs
written to run under DOS, Microsoft Windows, and the OS/2
operating system will run under OS/2 2.0.
The installation procedure begins when you insert the Installation
Diskette and restart the system. From that point on, most of the
information you need to help you install the system can be found
on the screens.
During the installation, you will be asked to make choices about
how you want your system set up. Each time you are asked to
make a choice, a default (preselected) choice will be provided. If
you want to accept these default choices, you can go now to the
Quick Reference card, which will give you instructions on how to
start the installation.
However, if you want more information about the choices you can
make during installation, or if you want assistance in completing
the installation, you can refer to Chapter 2, 蘒nstalling OS/2 2.0 as
the Only Operating System?on page 9.
To complete the basic installation procedure and set up OS/2 2.0
as the only operating system, choose one of these:
?
�葺葺葺莨葺葺葺葙
�葺葺馆葺葙 �葺葺馆葺葙
�Quick � � Chapter �
�Reference� � 2 �
�card � � �
� � � �
�葺葺葺葺? �葺葺葺葺?
If, instead, you want to install the OS/2 Version 2.0 operating
system according to one of the more advanced procedures (for
example, if you want to keep a version of DOS on the same system
with OS/2 2.0), continue to 嗀dvanced Installation Choices?on
page 4.
Chapter 1. Choosing an Installation Procedure 3
Advanced Installation Choices
Although installing OS/2 2.0 by itself is the procedure that will be
best for most people, you might have specific requirements to
install more than one operating system or to keep a version of
DOS on your system when you install OS/2 2.0.
Running OS/2 2.0 and DOS on the Same System
The OS/2 Version 2.0 operating system is designed to run
programs written for DOS and Microsoft Windows. These
programs run in a version of DOS that is optimized for the OS/2
environment. However, some programs will run only under a
specific version of DOS. If you have such a program, you might
want to consider running a specific version of DOS with OS/2 2.0.
There are three ways that you can set up your system to
accomplish this.
? You can load a version of DOS into a DOS session of OS/2 2.0.
The version of DOS can exist on another partition on the hard
disk or it can be on diskette.
?
You can install OS/2 2.0 on a system that already contains
DOS and then use the BOOT command to switch between the
operating systems. (This is called the Dual Boot feature.)
? You can install multiple operating systems on the hard disk of
your computer. Then, each time you start your computer, you
can select which operating system you want to be active. (You
use the Boot Manager feature to manage the startup of the
operating system.)
The following is a brief summary to help you decide which of these
choices is right for you.
4OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Run a version of Add OS/2 2.0 to a Install DOS and
DOS from within DOS partition (Dual OS/2 in their own
OS/2 2.0. Boot). partitions (Boot
Manager).
? You can either ? You do not have ? You must
partition your to partition your partition the
hard disk (and hard disk. hard disk during
install DOS in its installation.
own partition),
or you can start
DOS from a
diskette.
? You start DOS in ? You use the ? When you start
a DOS session BOOT command the computer,
of OS/2 to switch you select which
whenever you between DOS operating
need it. and OS/2 2.0. system to use.
? DOS can run in ? OS/2 2.0 and ? OS/2 2.0 and
a window while DOS do not DOS do not
OS/2 2.0 operate at the operate at the
continues to run. same time. same time.
You do not have
to shut down
OS/2 2.0 and all
OS/2 programs
to run a specific
version of DOS.
? You must modify ? You might have ? You do not have
DOS system to modify DOS to modify any
files after you system files or DOS system
install OS/2 2.0 change the files.
and DOS. directory
structure before
you install OS/2
2.0.
As you can see, each of the choices has certain advantages. For
example, if you start a version of DOS from within the OS/2
operating system, you can run the DOS version while continuing to
take advantage of the multitasking features of OS/2 2.0.
Chapter 1. Choosing an Installation Procedure 5
Multiple Operating System Installation
With the Boot Manager feature of OS/2 2.0, you can have multiple
operating systems installed in separate partitions of your hard
disk. Once the operating systems are installed, you use the Boot
Manager to select which one you want to start. As mentioned in
the previous section, you can install OS/2 2.0 and a version of DOS
in their own partitions, and then use the Boot Manager to select
one at startup time. You can install other operating systems (such
as AIX * ) as well.
Alternative Ways to Install
You can install OS/2 2.0 using a response file, which contains
information the installation program uses to set up a system.
When a response file is used, the installation program does not
prompt for decisions. This type of installation is typically used in
multi-workstation environments, where many computers are being
set up. You can also redirect the installation of OS/2 2.0 to a
source other than the diskette in drive A.
Choosing an Advanced Installation Procedure
If you have chosen to do something other than the basic
installation, select one of these advanced installation procedures:
?
�葺葺葺葺葺葺葺葺葺葺篙葺葺葺葺葺葺葺葺葺葙
�葺葺馆葺葙 �葺葺馆葺葙 �葺葺馆葺葙
� Chapter � � Chapter � � Chapter �
� 3 � � 4 � � 5 �
� � � � � �
� � � � � �
�葺葺葺葺? �葺葺葺葺? �葺葺葺葺?
Add OS/2 2.0 to Install OS/2 2.0 Install using a
a DOS system and other response file or
(Dual Boot). operating systems install from a
(Boot Manager). source other than
drive A.
* Trademark of the IBM Corporation.
6OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
The procedure for starting a version of DOS from diskette is
described in the online information, which is available on your
screen after you install the OS/2 Version 2.0 operating system.
Special Note about Reconfigurable Diskette Drives
Some systems that contain multiple diskette drives provide the
capability to read a self-starting diskette (such as the Installation
Diskette) from a drive other than A.
For example, suppose you have two diskette drives: A (for 3.5-inch
diskettes) and B (for 5.25 diskettes). If you load a self-starting
diskette in drive B and restart the system, the diskette in drive B
will be loaded.
If you have a system with multiple diskette drives and you want to
load the installation diskettes from a drive other than A, you will
need to reassign that other drive to make it the primary drive in
the startup sequence. See the documentation that came with your
computer for information on making a drive other than A the
primary drive.
Chapter 1. Choosing an Installation Procedure 7
8OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Chapter 2. Installing OS/2 2.0 as the Only
Operating System
This chapter describes how to install OS/2 2.0 as the only
operating system on your computer. It also provides information
to help you make choices about which features of the operating
system you want to install.
You can use the procedure in this chapter whether you are
installing on a new system or on a system that already contains
data. For example, if you already have OS/2 Version 1.3 on your
hard disk, you can use the procedure in this chapter to replace it
with OS/2 Version 2.0.
You can also use the procedure in this chapter to replace a DOS
system with OS/2 2.0. However, if you want to keep a version of
DOS on your system, see Chapter 3, 嗀dding OS/2 2.0 to a DOS
System?on page 17.
Note: If an error message is displayed while you are installing the
operating system, see esponding to Installation Errors?
on page 75 for an explanation of the message and the
corrective action.
In the first part of the installation, you will make choices about how
the hard disk on your system should be set up.
Setting Up Your Hard Disk
To begin the installation of the operating system, do the following:
1. Insert the Installation Diskette into drive A.
2. Turn on the computer.
If the computer is already on, press and hold Ctrl+Alt and
press Del to restart the system. The following screen appears:
+ Copyright IBM Corp. 1991 9
+---------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+---------------------------+
3. Remove the Installation Diskette, insert Diskette 1, and press
Enter.
You will be prompted at various points during installation to
remove the diskette in drive A and to insert another diskette.
Be sure to leave the diskette in drive A until the instructions
direct you to replace it. You will replace diskettes several
times before the operating system finishes copying information
from the diskettes to the hard disk of your computer.
4. As information is displayed, either accept it or change it. If
you want to set up a default system that works best for most
people, you can accept the preselected choice on each screen
by pressing Enter.
During this part of the installation, you will be asked whether
you want to accept the default installation partition or to
specify your own partition. A partition is a fixed-sized area on
the hard disk. If you are installing on a disk that contains no
data and you accept the default installation partition, the
installation program installs the operating system in one
partition that takes up the entire hard disk. If you are installing
on a system that already contains partitions, the installation
10OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
program indicates which partition it will use to install OS/2 2.0.
You can either accept this default choice or select another
partition.
Accepting the default partition works well for most people. If
you want to install the operating system in the default partition,
simply accept the preselected choices.
If you are not sure of a choice, press F1 for help.
A note about partitioning
If you want to create more than one partition on your hard disk,
or if you receive a message stating that an existing partition is
not large enough to hold OS/2 2.0, you will need to specify
information about partitions. When you select other than the
default partition, you see the FDISK utility screen. On this
screen, you use the Options menu to create the partitions.
(The Options menu is displayed when you highlight an entry on
the FDISK screen and press Enter.)
An example of creating more than one partition on the hard
disk is included in Appendix C, 﨓xamples of Installing OS/2
2.0 and Partitioning Your Hard Disk?on page 77. You might
want to follow that example now if you are setting up more
than one partition on the hard disk.
At a certain point in the installation process, you will be notified
that the hard disk setup is complete. You will then be asked to
restart your system by removing the diskette and pressing Enter.
Chapter 2. Installing OS/2 2.0 as the Only Operating System 11
Selecting the Operating System Features
Once the hard disk of your computer is set up, you see the OS/2
Setup and Installation screen. In this part of installation, you make
choices about which features of the operating system you want to
install.
+---------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+---------------+
The default choice on this screen is Learn how to use a mouse. If
your system has a mouse attached, but you are unfamiliar with
using the mouse, press Enter to select this choice. The Learn how
to use a mouse program teaches you how to use the mouse to
make selections from the screen.
The Install preselected features choice copies the most commonly
used features of the OS/2 operating system to your hard disk. It
does not copy all the features of OS/2 2.0 to your hard disk. (For
example, Install preselected features does not copy such features
as the Command Reference or REXX Information online documents
or the games that are provided with OS/2 2.0.) This choice is
useful if you want to save hard disk space.
The Install all features choice copies the entire OS/2 operating
system to your hard disk.
The Select features and install choice gives you the opportunity to
indicate which features of the operating system you want to install.
This choice is similar to Install preselected features because, by
installing only certain features, you can save hard disk space.
With this choice, however, you decide which features you want to
12OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
install. Also, if you partitioned your hard disk during the first part
of installation, you can format any logical drives that you
previously set up.
To select a choice, do one of the following:
? Use the Down Arrow ( ? ) key to highlight the choice, and then
press Enter.
? Move the mouse pointer until it is on the choice, and quickly
press mouse button one twice.
You next see the System Configuration screen, which lists your
country configuration and device support (for example, mouse,
keyboard, and display). You can change any of the items by
selecting the item and then selecting the OK push button.
If you chose Select features and install, you see a screen on which
you indicate which features you do not want to install. +-----------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------------+
If there is a feature that you will not need, you can choose not to
install it by removing the | next to the feature. To remove the |,
do one of the following:
? Move the mouse pointer to the feature and click once with the
mouse.
? Move the cursor to the feature and press the Spacebar.
Chapter 2. Installing OS/2 2.0 as the Only Operating System 13
If a More push button is displayed next to a feature, select the
push button to view more choices.
For example, if you decide you want to install only some of the
documentation, you select the More push button to the right of
Documentation to display a list of the documentation. Then, you
remove the | that is next to any documentation you do not want to
install.
Notice the number that is shown to the right of each feature. The
number signifies the amount of hard-disk space required to install
that feature.
For a description of the features, press F1, or see 﨔eatures that
You Can Change or Add?on page 67 for a description of all the
features.
The OS/2 Setup and Installation screen also contains a choice that
lets you format any logical drives you might have set up earlier in
the installation. If you partitioned your hard disk and set up logical
drives for data, you can format them now. To do so, select the
Options menu bar choice, and then select Format. Indicate which
file system (High Performance File System or File Allocation Table)
you want to use to format the logical drive.
Configuring the System
When most of the system files have been transferred, you will see
the Advanced Options screen. Some of the choices on this screen
are available only if you are installing on a hard disk that
contained an existing operating system. For example, if you had a
previous version of the OS/2 operating system on the hard disk,
the Migrate CONFIG.SYS/AUTOEXEC.BAT choice is available. You
use this choice to copy customization information from your
existing operating system to OS/2 2.0.
14OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Special note about migrating the CONFIG.SYS file
If you select Automatically update CONFIG.SYS amd
AUTOEXEC.BAT, you will notice that some device driver
statements from the existing CONFIG.SYS file are copied to the
new file but are preceded with a comment statement. These
statements are commented out because some device drivers
that were designed to operate with previous versions of DOS or
the OS/2 operating system might not operate with OS/2 2.0.
Such device drivers could cause problems with OS/2 2.0.
You can edit the CONFIG.SYS file after installation and remove
the comment statements from the lines that you want to be
active. Save a copy of the CONFIG.SYS file before you modify
it. In the event that a device driver causes problems, you can
use the procedures described later in this book to recover the
file.
If you have existing DOS or Microsoft Windows programs on your
hard disk, you will be asked whether you want to move these
programs into your OS/2 system.
On this screen, you will also indicate which printer should be used
as your default printer.
For specific information about these choices and for help using the
choices, press F1.
Chapter 2. Installing OS/2 2.0 as the Only Operating System 15
Viewing the Tutorial
After the operating system is installed and you have restarted the
system, the OS/2 Tutorial is displayed: +--------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------------------------+
The tutorial shows you how to use the features of the OS/2
operating system. View the tutorial now. When you have finished,
explore the features of the operating system, and enjoy!
16OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Chapter 3. Adding OS/2 2.0 to a DOS System
This chapter describes how to install the OS/2 Version 2.0
operating system on a hard disk that already has DOS installed so
that you can use both operating systems. The OS/2 Version 2.0
operating system is installed along with DOS in the primary
partition of your hard disk.
By following the procedures in this chapter, you set up your
system to use Dual Boot. With Dual Boot, you can switch back and
forth between the DOS and OS/2 operating systems. For example,
if you have a DOS program that runs only under the DOS operating
system, you could switch to DOS and run the program.
Note: It is assumed that DOS is already installed on your system
and that you are familiar with using DOS.
You will add OS/2 2.0 to the same partition in which DOS resides.
Keep in mind that the DOS and OS/2 operating systems cannot
operate at the same time. You switch between the operating
systems using the BOOT command.
Another way to use DOS:
With Version 2.0 of the OS/2 operating system, you can run a
specific version of DOS (for example, DOS Version 5.0) from a
DOS session within OS/2 2.0. You can run DOS Version 5.0, for
example, while your other programs continue to run under
OS/2 2.0. So, if you want to be able to run a version of DOS
while OS/2 2.0 is running, you can set up DOS in its own
partition on the hard disk (which is explained in Chapter 4,
蘒nstalling Multiple Operating Systems?on page 25.) Or, you
can run a version of DOS from a DOS diskette. For information
on running a version of DOS from a DOS diskette, see the
online information, which is displayed on your screen after you
install the operating system.
+ Copyright IBM Corp. 1991 17
Dual Boot Requirements
Before you begin the procedures in this chapter, you should be
aware of the following:
?
DOS Version 3.2 or higher must be installed on your hard disk.
OS/2 2.0 will work with DOS Version 3.2; however, to take full
advantage of OS/2 capabilities, use DOS Version 3.3 or higher.
? The DOS operating system must exist on drive C before the
OS/2 operating system is installed. The Dual Boot feature is
operable only after OS/2 2.0 is installed.
? You can start either DOS or the OS/2 operating system from
the same partition on your hard disk. Note, however, that you
cannot use this feature with the High Performance File System.
The DOS operating system will not recognize or be able to use
anything within a High Performance File System partition.
? If you already have a previous version of the OS/2 operating
system with the Dual Boot feature or DOS installed on the
target hard drive, the existing operating systems must be
startable for the Dual Boot feature to work correctly. (Use the
FDISK utility program of DOS if you want to check whether the
version of DOS is startable.) Be sure that the DOS operating
system installed is the version you wish to use with the Dual
Boot feature.
? Your primary partition must be at least 24MB (MB equals 1 048
576 bytes) for the DOS and OS/2 operating systems to exist on
drive C. You should consider the size of both operating
systems and also leave room for the growth of a swap file. (A
swap file contains segments of a program or data temporarily
moved out of main storage.) A typical swap file is between 4
and 8MB. If your existing primary partition is not large
enough, use the DOS FDISK command to change your hard
disk setup. Follow the instructions in your DOS documentation.
QUESTION
Do you have OS/2 Version 1.2 or 1.3 with the Dual Boot feature
currently installed on your hard disk? If so, go to 蘒nstalling
the OS/2 Version 2.0 Operating System?on page 22.
18OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Setting Up Your System for Dual Boot
Before you install OS/2 Version 2.0, you will check to see that your
DOS system is set up correctly.
? All DOS commands and utility programs must be located in a
subdirectory, such as C:\DOS, and not in the root directory.
? You must create or modify the DOS operating system
CONFIG.SYS and AUTOEXEC.BAT files on your system and put
them in the root directory of your hard disk before the OS/2
operating system is installed. This includes setting the SHELL,
COMSPEC, PATH, and APPEND statements to find the DOS
command files in the appropriate subdirectory.
In the next section of this chapter, you will check to see that your
setup meets these conditions.
Making Sure Your DOS Directory Structure Is Correct
1. Start your computer using the DOS operating system that is on
your hard disk, and go to the DOS command prompt.
2. For the Dual Boot feature to work correctly, your CONFIG.SYS
and AUTOEXEC.BAT files must remain in your root directory.
All other DOS system files, including the COMMAND.COM file,
must exist in a subdirectory.
? If your DOS system files and the COMMAND.COM file
already exist in a subdirectory, go directly to 﨏reating or
Modifying the AUTOEXEC.BAT and CONFIG.SYS Files?on
page 21.
? If your DOS system files and COMMAND.COM do not
already exist in a subdirectory, continue to step 3.
3. Type the following command to create a DOS subdirectory on
your C drive:
MD C:\DOS
and press Enter.
Chapter 3. Adding OS/2 2.0 to a DOS System 19
4. To make sure your root directory and DOS subdirectory are set
up properly, follow these steps:
a. Copy all the files from the root directory of the hard disk to
the DOS subdirectory by typing:
COPY C:\*.* C:\DOS
Then press Enter.
Note: Although this step copies your CONFIG.SYS and
AUTOEXEC.BAT files to the DOS subdirectory, step
4c returns the files to where they properly belong.
b. Delete all of your files from the root directory of the hard
disk.
Warning: Be sure to type the command correctly. When
you enter the command, all files will be deleted, and you
will not be able to recover the data. You will be asked if
you are sure you want to use this command.
Type:
DEL C:\*.*
Then press Enter.
c. Place your existing AUTOEXEC.BAT file in the root
directory by typing:
COPY C:\DOS\AUTOEXEC.BAT C:\
Then press Enter.
Place your existing CONFIG.SYS file back in the root
directory by typing:
COPY C:\DOS\CONFIG.SYS C:\
Then press Enter.
d. Continue with 﨏reating or Modifying the AUTOEXEC.BAT
and CONFIG.SYS Files?on page 21.
20OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Creating or Modifying the AUTOEXEC.BAT and
CONFIG.SYS Files
Before installing the OS/2 operating system, you must create or
modify the DOS CONFIG.SYS and AUTOEXEC.BAT files on your
hard disk. This includes setting the SHELL, COMSPEC, PATH, and
APPEND statements to find the DOS command files in the
appropriate subdirectory.
To create or modify the DOS AUTOEXEC.BAT and CONFIG.SYS
files, do the following:
1. Using any editor (for example, EDLIN), add the following
statements, if they do not already exist, to the AUTOEXEC.BAT
file:
SET COMSPEC=C:\DOS\COMMAND.COM
PATH C:\DOS
APPEND=C:\DOS
COPY C:\DOS\COMMAND.COM C:\ >NUL
To the CONFIG.SYS file, add:
SHELL=C:\DOS\COMMAND.COM /P
Note: These statements include the minimum required
parameters. You can specify additional parameters if
you wish, but be sure that the DOS directory is specified
as indicated.
During OS/2 installation, OS/2 CONFIG.SYS and
AUTOEXEC.BAT files are created. The OS/2 operating system
places any existing DOS CONFIG.SYS and AUTOEXEC.BAT
files in the C:\OS2\SYSTEM subdirectory with a .DOS
extension. This is to make sure that the OS/2 operating
system uses the correct AUTOEXEC.BAT and CONFIG.SYS files
during system restart.
Note: If you are using DOS Version 4.0 and you want to use
the DOS shell, you must change the directory specified
in DOSSHELL.BAT from CD to CD\DOS. If this change
is not made, you will receive the message, Mouse file
. missing or unreadable
2. Remove any diskette from drive A.
3. Press and hold Ctrl+Alt; then press Del to restart the system.
Chapter 3. Adding OS/2 2.0 to a DOS System 21
If the system does not operate, review the previous steps to
make sure you have completed all of them. Remember, you
must have a working copy of DOS installed and it must not be
in the root directory.
Continue with 蘒nstalling the OS/2 Version 2.0 Operating System.?
Remember, do not select the FORMAT option while installing the
OS/2 operating system. After the operating system is installed,
you can start the Dual Boot feature. (See tarting the Dual Boot
Feature?on page 24.)
Installing the OS/2 Version 2.0 Operating System
If you have DOS or Microsoft Windows programs that you want to
install, install them before you install the OS/2 operating system.
Note: If an error message is displayed while you are installing the
operating system, see esponding to Installation Errors?
on page 75 for an explanation of the message and the
corrective action.
To install the operating system, do the following:
1. Insert the Installation Diskette into drive A.
2. Turn on the computer.
If the computer is already on, press and hold Ctrl+Alt, and
then press Del to restart the system. The following screen
appears:
22OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
+-----------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------------+
3. Remove the Installation Diskette, insert Diskette 1, and press
Enter.
You will be prompted at various points during installation to
remove the diskette in drive A and to insert another diskette.
Be sure to leave the diskette in drive A until the instructions
direct you to replace it. You will replace diskettes several
times before the operating system finishes copying information
from the diskettes to the hard disk of your computer.
4. As information is displayed, either accept it or change it.
Remember that you should not format your hard disk during
installation.
If you are not sure of a choice, press F1 for help. (Or, you can
refer to Chapter 2, 蘒nstalling OS/2 2.0 as the Only Operating
System?on page 9, which provides additional information
about installing the operating system.)
Chapter 3. Adding OS/2 2.0 to a DOS System 23
Viewing the OS/2 Tutorial
When the operating system is installed and you have restarted the
system, the OS/2 Tutorial is displayed. The tutorial shows you
how to use the features of the OS/2 operating system. View the
tutorial now, and enjoy the new world of OS/2 2.0.
Starting the Dual Boot Feature
After you have installed the OS/2 operating system, you use the
BOOT command to switch from one operating system to another:
? If you are running the OS/2 operating system and want to
switch to DOS, display an OS/2 command prompt and type:
BOOT /DOS
Then press Enter.
?
If you are running DOS and want to switch to the OS/2
operating system, type:
C:\OS2\BOOT /OS2
Then press Enter.
For additional information about the BOOT command, refer to
the OS/2 Command Reference.
Each time the system is shut down and restarted, it starts in
whichever operating system was last being used. For example, if
you shut down the system while DOS is running, your system will
start in DOS the next time you turn on the system. Remember,
however, that the OS/2 operating system and DOS do not operate
at the same time.
24OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Chapter 4. Installing Multiple Operating Systems
This chapter describes how you can install multiple operating
systems on the hard disk of your computer. To install multiple
operating systems, you will set up multiple partitions on the hard
disk during the installation of the OS/2 operating system. You will
also install the Boot Manager feature.
After the Boot Manager is installed and all the operating systems
are installed in their own partitions, you use the Boot Manager
startup menu to select one of the operating systems. Each time
you start your system, then, you decide which operating system
you want to be active.
How This Chapter is Organized
This chapter is separated into three major sections. It is
recommended that you read the entire chapter. In addition,
examples of installing multiple operating systems are provided in
Appendix C, 﨓xamples of Installing OS/2 2.0 and Partitioning Your
Hard Disk?on page 77. For example, if you want to see a brief,
step-by-step example of installing DOS and OS/2 2.0, see Appendix
C.
Section Page Number
An overview of the Boot Manager 26
Hard disk management 27
Instructions for installing OS/2 2.0 and 34
partitioning the hard disk
+ Copyright IBM Corp. 1991 25
An Overview of the Boot Manager
If you are going to install multiple operating systems, you can use
the Boot Manager feature to manage the selective startup of those
systems. From the Boot Manager startup menu, you can select
which operating system you want to use each time you start your
system.
The following is an example of a Boot Manager startup menu that
includes three operating systems. +-----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------+
You use the FDISK utility program during the installation of OS/2
2.0 to install the Boot Manager feature. The following is a brief list
of the steps you follow to set up your hard disk for multiple
operating systems. These steps are described in detail later in
this chapter. Examples are provided in Appendix C, 﨓xamples of
Installing OS/2 2.0 and Partitioning Your Hard Disk?on page 77.
? First, you install the Boot Manager in its own partition (1MB in
size).
? You then create partitions for the other operating systems you
are going to install.
? Next, you install the OS/2 Version 2.0 operating system.
? Finally, you install the other operating systems in the partitions
you created for them.
26OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Important: You should understand how a hard disk is partitioned
before you begin your installation. Make sure you read the
following section on hard disk management.
Hard Disk Management
During installation, you have the option of installing the OS/2
operating system in one partition that takes up the entire hard
disk. If, however, you choose to separate your hard disk into
multiple partitions, you see the FDISK screen.
From the FDISK screen, you specify the number and type of
partitions that you want created. You can create primary
partitions, which are typically used for operating systems. You can
also create logical drives in an area of the hard disk that is outside
the primary partitions. This area is known as the extended
partition. The logical drives within the extended partition are
typically used to hold programs and data.
Your hard disk can be separated into a maximum of four partitions.
You can have four primary partitions or three primary partitions
and the extended partition. If you are going to install multiple
operating systems on your hard disk, you must create one primary
partition to contain the programs that manage the startup of
multiple operating systems. (This partition is referred to as the
Boot Manager partition.)
After the Boot Manager partition is created, you can create up to
three additional primary partitions (to hold three operating
systems), as in the following example:
Chapter 4. Installing Multiple Operating Systems 27
�葺葺葺葺葺葺葺葺葺葺?
� Boot Manager �
谳葺葺葺葺葺葺葺葺葺莼
� DOS 5.0 �
谳葺葺葺葺葺葺葺葺葺莼
� OS/2 1.3 �
� �
谳葺葺葺葺葺葺葺葺葺莼
� OS/2 2.0 �
� �
� �
�葺葺葺葺葺葺葺葺葺葺�
Figure 1. Hard Disk with Four Primary Partitions
Another way of subdividing your hard disk is to create logical
drives within an extended partition. Logical drives are typically
used to hold programs and data. However, you can also install
OS/2 2.0 in a logical drive, as in the following example:
�葺葺葺葺葺葺葺葺葺葺葺葙
� Boot Manager � 葺葺葺?Primary Partition
谳葺葺葺葺葺葺葺葺葺葺葺?
� DOS 5.0 � 葺葺葺?Primary Partition
谳葺葺葺葺葺葺葺葺葺葺葺?
� OS/2 1.3 � 葺葺葺?Primary Partition
� �
谳葺葺葺葺葺葺葺葺葺葺葺?
� OS/2 2.0 � 葺?Logical Drive 葺葙
� � �
谳葺葺葺葺葺葺葺葺葺葺葺? � 葺葸 Extended
� Data � 葺?Logical Drive � Partition
谳葺葺葺葺葺葺葺葺葺葺葺? �
� Data � 葺?Logical Drive �
�葺葺葺葺葺葺葺葺葺葺葺? 葺?
Figure 2. Hard Disk with Primary Partitions and Logical Drives
The extended partition takes the place of one of the primary
partitions on your hard disk. In other words, if you create logical
drives within an extended partition, your hard disk can contain
only three primary partitions. Note that you must have one
primary partition in addition to the Boot Manager partition.
In Figure 2, notice that two logical drives have been set aside for
data. That data can be shared by all the operating systems
(provided the file system formats of the logical drives are
compatible with the operating systems).
28OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
All of the logical drives exist within one partitionhe extended
partition. You don't explicitly create the extended partition. The
extended partition is created the first time you create a logical
(non-primary) drive.
One of the differences between a logical drive and a primary
partition is that each logical drive is assigned a unique drive letter.
However, all primary partitions on a hard disk share the same
drive letter. (On the first hard disk in your system, the primary
partitions share drive C). This means that only one primary
partition on a hard disk can be accessed at one time. (Note that
the Boot Manager partition is different from other primary
partitions because it is never assigned a drive letter.)
�葺葺葺葺葺葺葺葺葺葺葺葙
� Primary (Boot Manager)� 葺葺葺葺葺?No drive letter.
谳葺葺葺葺葺葺葺葺葺葺葺? 葙
� Primary (DOS 5.0) � �葺葺葺葺?These partitions share C:
谳葺葺葺葺葺葺葺葺葺葺葺? � (Only one can be active)
� Primary (OS/2 1.3) � �
� � �
谳葺葺葺葺葺葺葺葺葺葺葺? ?
� Logical Drive � 葺葺葺葺葺? D:
� (OS/2 2.0) �
谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical Drive (Data) � 葺葺葺葺葺? E:
谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical Drive (Data) � 葺葺葺葺葺? F:
�葺葺葺葺葺葺葺葺葺葺葺?
Figure 3. Drive Letter Assignment Example
Notice the drive letter assignments in this illustration. The
operating system that is active when you start the system
performs a process known as drive mapping, in which partitions
and logical drives are assigned drive letters. All the primary
partitions are mapped first and all logical drives within extended
partitions are assigned subsequent drive letters (up through Z).
Only one primary partition per hard disk can be active at a time.
So, only one primary partition is actually assigned the letter C at
any one time. The other primary partitions are not mapped.
An operating system maps only those drives with a format type
that it supports. For example, DOS does not support the
Chapter 4. Installing Multiple Operating Systems 29
installable file system (IFS) format. (The High Performance File
System is an example of an IFS format.) Therefore, any partition
or logical drive that is formatted with IFS is not mapped by DOS
and is not assigned a drive letter.
In the following figure, DOS is active in a primary partition. (The
other primary partitions are not mapped.) Drive D is formatted for
the File Allocation Table (FAT) file system, which DOS recognizes.
However, the next drive is formatted with a file system that DOS
does not recognize. Therefore, DOS ignores this drive. Some
versions of DOS (such as DOS Version 5.0) will recognize the last
partition on the hard disk and assign it the letter E. In other
versions of DOS, no drives beyond the HPFS drive are recognized.
Therefore, no data in those partitions can be used by DOS.
�葺葺葺葺葺葺葺葺葺葺葺葙
� Primary (Boot Manager)� 葺葺葺葺葺?No drive letter.
谳葺葺葺葺葺葺葺葺葺葺葺?
� Primary (DOS) � 葺葺葺葺葺? C:
谳葺葺葺葺葺葺葺葺葺葺葺?
� Primary (OS/2 2.0) �
谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical (Data) � 葺葺葺葺葺? D:
� FAT format �
谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical (Data) � 葺葺葺葺葺? DOS does not recognize this
� HPFS format �
谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical (Data) � 葺葺葺葺葺? E:
� FAT format �
�葺葺葺葺葺葺葺葺葺葺葺?
Figure 4. Example of Drive Mapping. This example illustrates the
problem that can result when the operating system does not recognize a
file format. You can avoid such a problem by placing the logical drive
formatted for the High Performance File System at the end of the hard
disk.
Because of the problems that can result when drives are
remapped, you should avoid deleting logical drives that exist in the
middle of your hard disk. For example, if you were to delete a
logical drive from the middle of your disk, the subsequent drives
would be remapped. (Drive F would become drive E, and so on.)
Problems would result if any programs refer to the former drive
letter.
30OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
The following figure is an example of how drives are mapped in a
system that has two hard disks.
Hard Disk #1 Hard Disk #2
�葺葺葺葺葺葺葺葺葺葺葺葙 �? �葺葺葺葺葺葺葺葺葺葺葺葙
� Boot Manager � 葺葺?No drive � � Primary �
谳葺葺葺葺葺葺葺葺葺葺葺? 葙 letter � 谳葺葺葺葺葺葺葺葺葺葺葺?
� Primary � � � � Primary �
� � �葺葺 C: D: 葺葺� 谳葺葺葺葺葺葺葺葺葺葺葺?
谳葺葺葺葺葺葺葺葺葺葺葺? � � � �
� Primary � � � � Primary �
谳葺葺葺葺葺葺葺葺葺葺葺? ? �? 谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical Drive � 葺葺葸 E: H:
葺葺? � Logical Drive �
� � � �
谳葺葺葺葺葺葺葺葺葺葺葺? 谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical Drive � 葺葺葸 F: I:
葺葺? � Logical Drive �
谳葺葺葺葺葺葺葺葺葺葺葺? 谳葺葺葺葺葺葺葺葺葺葺葺?
� Logical Drive � 葺葺葸 G: J:
葺葺? � Logical Drive �
�葺葺葺葺葺葺葺葺葺葺葺? �葺葺葺葺葺葺葺葺葺葺葺?
Figure 5. Example of Drive Mapping in a System with Two Hard Disks
The important thing to remember when you are setting up your
system is that only one primary partition can be accessible (active)
on each hard disk at any system startup. On the other hand, all
the logical drives within the extended partition are accessible
(provided their file system formats are compatible with the starting
operating system).
Planning for a Boot Manager Setup
When you are planning your Boot Manager setup, be aware of the
following:
?
If you want to preserve existing partitions on your hard disk,
you can install the Boot Manager partition at the end of the
hard disk. Otherwise, create the Boot Manager partition at the
beginning of the hard disk.
? Use primary partitions for DOS systems or previous releases
of the OS/2 operating system.
? To prevent hard disk fragmentation and loss of usable disk
space, create all primary partitions contiguously, at the
beginning or end of the disk free space area.
Chapter 4. Installing Multiple Operating Systems 31
? Put all installable file systems (such as the High Performance
File System) at the end of the disk configuration. As
mentioned earlier, some operating systems do not recognize
installable file systems. By placing all installable file systems
at the end of the disk, you can prevent the problem that results
when drives are remapped.
?
Be aware of specific operating-system restrictions on the hard
disk. For example, to run properly, DOS 3.3 must be installed
in a primary partition that is within the first 32MB of the hard
disk.
? If you are installing a primary partition for DOS and you intend
to load that version of DOS into a DOS session of OS/2 2.0, you
will need to change the DOS CONFIG.SYS and AUTOEXEC.BAT
files. (You do this after you finish installing the operating
systems.) Refer to the online information, which is displayed
on your screen after the OS/2 operating system is installed.
? You can install both DOS and a version of the OS/2 operating
system in the same primary partition if you want to use the
Dual Boot feature within your Boot Manager setup.
? If you are using the IBM DOS 5.00 Upgrade to update your DOS
3.3 or DOS 4.0 system, you should be aware that some
versions of the upgrade will not recognize the DOS partition
unless it is the only partition on the hard disk. You might have
to do the following:
1. Make sure that the DOS partition is the only primary
partition on your hard disk.
2. Install the DOS 5.00 Upgrade.
3. Add the Boot Manager partition and install OS/2 2.0.
Note that an example of adding the Boot Manager to an
existing system (without repartitioning the entire hard disk) is
outlined in Appendix C, 﨓xamples of Installing OS/2 2.0 and
Partitioning Your Hard Disk?on page 77.
32OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Sample FDISK Screen
The following FDISK screen represents a typical hard disk layout of
a 120MB hard disk with three operating systems installed. +--------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------------------------------------+
In the previous screen, note the following:
? The Boot Manager partition is marked Startable. When you
start your system, the Boot Manager will be in control. You
can then choose which operating system you want to run.
? DOS 3.3 and DOS 5.0 are set up in primary partitions.
However, only DOS Version 3.3 is accessible. Notice that the
drive letter (C) is displayed on the line that contains
information about the DOS 3.3 partition. The placement of the
drive letter indicates which of the primary partitions is active.
DOS and previous versions of the OS/2 operating system can
reside only in a primary partition. They cannot reside in a
logical drive within the extended partition.
? OS/2 2.0 resides in a logical drive in the extended partition
(drive D in this example). Remember that OS/2 2.0 can reside
in either a primary partition or in a logical drive within the
extended partition.
? The logical drive labeled E is set aside for common tools or
programs that can be shared by the operating systems.
Chapter 4. Installing Multiple Operating Systems 33
? 55MB of free space is available. This area can be set aside for
future use. For example, you could later add logical drives at
the end of the free space without disturbing any currently
installed partitions.
34OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Getting Ready for Installation
To partition your hard disk and install multiple operating systems,
you will follow the steps that are described in detail in the next
section. An overview of the steps is provided in the following list.
Examples of setting up your hard disk for multiple operating
systems are provided in Appendix C, 﨓xamples of Installing OS/2
2.0 and Partitioning Your Hard Disk?on page 77.
1. Begin the installation of OS/2 2.0.
2. Set up a partition for the Boot Manager.
3. Set up any primary partitions on the first hard disk that you
want to use to install other operating systems.
Note: At this point, you can also set up logical drives within
the extended partition for data or programs.
4. Set up the primary partition or logical drive for the OS/2
Version 2.0 operating system.
5. Install the OS/2 Version 2.0 operating system in that primary
partition or logical drive.
After you have installed OS/2 2.0, you can install the other
operating systems in the primary partitions that you set up in step
3.
Note that OS/2 installation does not control the installation of the
other operating systems. Each operating system must be installed
with its own installation package.
Back up your files!
If you are going to change an existing partition on your hard
disk, you must back up the data or programs in that partition
before you begin installation.
Chapter 4. Installing Multiple Operating Systems 35
Starting the OS/2 2.0 Installation
1. Insert the OS/2 Installation Diskette into drive A.
2. Turn on the computer. If the computer is already on, press
and hold Ctrl+Alt, and press Del to restart the system.
3. When prompted to do so, remove the Installation Diskette,
insert Diskette 1, and press Enter.
4. If you are installing OS/2 2.0 on a new system (on a hard disk
that does not currently contain an operating system), follow the
instructions listed below under 蘒nstalling OS/2 2.0 on a New
System.?Otherwise, go to 蘒nstalling OS/2 2.0 on an Existing
System?on page 37.
Installing OS/2 2.0 on a New System
If you are installing OS/2 2.0 on a new system (on a hard disk that
does not currently contain an operating system), you see several
introductory screens, followed by this screen:
+-----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------+
To install the Boot Manager, do the following:
1. Select option 2 to display the FDISK screen.
2. Go to 﨏reating the Boot Manager Partition?on page 41.
36OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Installing OS/2 2.0 on an Existing System
If you are installing OS/2 2.0 on an existing system (on a hard disk
that currently contains an operating system), you see several
introductory screens, followed by this screen:
+--------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------------------------------------+
1. Select option 2.
You see the following screen:
+--------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------------------------------------+
2. If you want to save the programs or data in the partition, press
F3 and then use the BACKUP command (or its equivalent) from
your existing operating system. Note that if you do leave the
installation at this point, you will have to restart the entire
installation process.
Chapter 4. Installing Multiple Operating Systems 37
3. If you have already backed up the data, or if you do not need
to keep the data, press Enter to start the FDISK utility program.
Note: If your hard disk has previously defined partitions, and none
of the partitions is large enough to install OS/2 2.0, the
following screen is displayed:
+-----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------+
To start the FDISK utility program and modify the partition sizes,
press Enter.
Warning: If you are increasing the size of an existing partition,
you must back up any information you want to save in that
partition.
To continue with installation, you must modify your hard disk
configuration. This is done with the FDISK utility program. Press
Enter. You will see the Modifying Partitions Warning screen again.
Press Enter, and the FDISK utility program will start.
38OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Setting Up Your Hard Disk
The FDISK screen shows all partitions that are currently set up on
your system. +--------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------------------------------------+
If you are installing the OS/2 operating system on a new system,
go to 﨏reating the Boot Manager Partition?on page 41. If
partitions exist on your system, they are listed on the FDISK
screen. Follow the procedures listed below under 﨑eleting
Existing Partitions.?
Deleting Existing Partitions
To set up your system, you must make sure there is enough room
on your hard disk to accommodate the desired setup. It might be
necessary for you to delete some or all of the existing partitions on
your hard disk.
For example, if your hard disk currently has only one partition that
takes up the entire hard disk, you must delete that partition.
However, if your hard disk has ample free space, you can keep
one or more existing partitions and add to them. (An example of
installing the Boot Manager and OS/2 2.0 while preserving an
Chapter 4. Installing Multiple Operating Systems 39
existing partition is shown in Appendix C, 﨓xamples of Installing
OS/2 2.0 and Partitioning Your Hard Disk?on page 77.)
Note that any changes you specify on the FDISK screen do not
actually go into effect until you press F3 to exit FDISK. You will
then be asked to confirm that you want to save your changes.
Warning: All information you want to save must be backed up.
Changing the size of a partition deletes all information about that
partition, and the entire operating system must be reinstalled
when the new partition is created.
1. Use the Up Arrow ( ) or Down Arrow () key to ? the ? highlight
partition you want to delete.
2. Press Enter to display the Options menu.
+-----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------+
3. Select Delete Partition and press Enter.
Notice that the information about the partition is deleted. The
words Free Space are displayed in the space formerly occupied
by the partition information.
4. Repeat steps 1 through 3 for any other partitions that you need
to delete.
40OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
5. When you are finished deleting partitions, continue to
﨏reating the Boot Manager Partition?on page 41.
Creating the Boot Manager Partition
The first partition you create is the Boot Manager partition. To
create this partition:
1. Make sure that the line is highlighted. IfFree Space it is not,
press the Up Arrow ( ) or Down Arrow ( ? ? ) key until it is
highlighted.
2. Press Enter to display the Options menu.
3. Select Install Boot Manager and press Enter.
4. Specify whether the partition should be at the beginning or the
end of the available space on the hard disk.
Note: It is recommended that you install the Boot Manager
partition at the beginning of the hard disk. However,
the only restriction on the placement of the Boot
Manager partition is that it be within the first 1GB
(gigabyte) of the disk space. (A gigabyte is equal to 1
073 741 824 bytes.)
Chapter 4. Installing Multiple Operating Systems 41
Creating Partitions for Operating Systems Other than
OS/2 2.0 and for Logical Drives
After you create the partition for the Boot Manager, create primary
partitions for any DOS or previous versions of the OS/2 operating
system you might want to install. Also create any logical drives to
use for data or programs. (Some operating systems, such as AIX,
require that their own disk utility program create the installation
partition. The OS/2 Version 2.0 FDISK utility program cannot
create the partition for these operating systems.)
If you are creating only one partition (for OS/2 Version 2.0), go to
﨏reating the Partition or Logical Drive for OS/2 2.0?on page 47.
Otherwise, follow these steps to create partitions and logical
drives:
1. Make sure that the line is highlighted. Free Space If it is not,
press the Up Arrow ( ) or Down Arrow ( ? ? ) key until it is
highlighted.
2. Press Enter to display the Options menu.
3. Select Create Partition and press Enter.
42OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
4. Type the size (in MB) of the partition you are creating. Use the
following chart to help you determine how large the partition
should be. For more specific information about partition sizes,
see the documentation that came with the product you are
installing. For example, if you are installing OS/2 Version 1.3
Extended Edition, you should refer to the IBM OS/2 Version 1.3
Information and Planning Guide for more specific guidance.
Table 1. Planning Table for Partition Sizes
Contents Size Hard Disk Considerations
DOS 3.3 2MBMust be in a primary partition within the
first 32MB on the first hard disk.
DOS 4.0 3MBMust be in a primary partition on the first
hard disk.
DOS 5.0 4MBMust be in a primary partition on the first
hard disk.
OS/2 1.x 20MB Must be in a primary partition on the first
SE hard disk. Installs in less than 20MB, but
segment swapping is inhibited.
OS/2 1.x 30MB Must be in a primary partition on the first
EE hard disk. Installs in less than 30MB with
reduced function.
OS/2 2.0 15-30MB Can be in a primary partition or logical
(See drive. Installs in less than 20MB with
Note b.) reduced function.
AIX Partition size determined and built by AIX
Disk utility program. Partition is created
at the end of the hard disk.
Notes:
a. Place system tools or common applications in a logical
drive within the extended partition so that the data can be
shared among the operating systems.
b. If you will be installing LAN Requester or one of the
Extended Services programs, you need to increase the size
of the OS/2 2.0 partition. These programs require a certain
amount of space in the OS/2 partition, even if you are
Chapter 4. Installing Multiple Operating Systems 43
installing them in separate partitions. If you are going to
add these programs, create an OS/2 partition of 32MB.
5. Specify whether this is a primary partition or a logical drive
within the extended partition. Consider the following:
? All versions of DOS must reside in primary partitions.
Versions of OS/2 before 2.0 must also reside in primary
partitions.
?Your hard disk can be separated into a maximum of
three primary partitions (in addition to the Boot
Manager partition.) If you are going to create logical
drives within an extended partition, you can set up two
primary partitions (in addition to the Boot Manager
partition).
?Remember that primary partitions cannot share data.
? Logical drives within an extended partition are shareable.
This means that any data installed in the logical drive can
be used by an operating system running from any other
active logical drive on the system, if the file system formats
are compatible.
6. Specify the location of the partition or logical drive you want to
create. Select either Create at Start of Free Space or Create
at End of Free Space. Note that all logical drives must be in
contiguous space on the hard disk. Therefore, when you
create more than one logical drive, make sure that you specify
Create at Start of Free Space for the subsequent drive.
Note: This option is not available when the amount of free
space equals the size of the request.
Once you have set up the partition, you use the Options menu
choices to specify information about the partition.
Options Menu Choices
The following list describes each of the choices on the Options
menu. Note that some of the options are available under certain
conditions only. When an option is not available, it cannot be
selected. (In other words, you cannot move the cursor to the
option to select it.)
44OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Install Boot Manager
This choice is used only oncehen you create the
partition for the Boot Manager. It is unavailable
thereafter.
Create Partitions
This choice is used to create primary partitions and
logical drives within the extended partition. You can
use this choice whenever there is free space available
on the hard disk.
Add to Boot Manager Menu
This choice is used to add the name of a partition or
logical drive to the Boot Manager startup menu. You
should use this choice for any operating system that
you want to be able to select when you start the
system. When you select this choice, the New Name
window is displayed. You use the New Name window
to assign a meaningful name to the partition or logical
drive.
Change Partition Name
This choice is used to change the name that you have
previously assigned to a partition or logical drive.
Assign C: Partition
This choice is used to specify which primary partition
you want to be active (when more than one primary
partition is installed on your system). The placement of
the drive letter (C) tells you which primary partition will
be visible (or accessible) after you restart the system.
Set Startup Values
This choice is used to specify the actions of the Boot
Manager startup menu. For example, with Set Startup
Values, you can specify how long you want the Boot
Manager menu to be displayed before the default
operating system is started. You can also specify which
operating system you want as the default.
Remove from Boot Manager Menu
This choice is used to delete a name from the Boot
Manager startup menu. When you delete the name,
you can no longer select the operating system
Chapter 4. Installing Multiple Operating Systems 45
associated with that name from the Boot Manager
startup menu.
Delete Partition
This choice is used to delete information about a
primary partition or logical drive. After you exit from
FDISK, all the data in the partition or logical drive is
deleted.
Set Installable
This choice is used to mark a partition or logical drive
as the target for installation. For example, before you
install the OS/2 Version 2.0 operating system, you set
one primary partition (or logical drive) as installable.
Later, when you install other operating systems, you
mark their partitions as installable before you actually
install the operating systems.
After you install OS/2 2.0, the status of this partition is
changed from Installable to Bootable.
Make Startable
This choice is used to determine which partition or
logical drive is activated when you start your system.
When you install the Boot Manager, it is automatically
marked as startable. This means that the Boot
Manager is in control when you start your system. Only
one partition on the first hard disk can be made
startable. If you set any other partition startable, the
Boot Manager startup menu will not appear when you
start the system.
Specifying Options
To specify options for the partition you just created:
1. Press Enter to display the Options menu.
2. Select Add to Boot Manager Menu if you want this partition
displayed on the Boot Manager startup menu. If you do not
select this choice for the partition, you cannot select the
operating system that exists in this partition from the menu at
startup time.
46OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
a. If you select Add to Boot Manager Menu, you see the
window in which you are asked to type a name for the
partition. Type the name.
b. Press the Enter key.
If you have additional partitions to set up, follow the instructions
outlined in 﨏reating Partitions for Operating Systems Other than
OS/2 2.0 and for Logical Drives?on page 42. Otherwise, continue
to 﨏reating the Partition or Logical Drive for OS/2 2.0.?
Creating the Partition or Logical Drive for OS/2 2.0
After you have created the partitions for the Boot Manager and for
each of the other operating systems you plan to install, create the
partition or logical drive in which you will install OS/2 2.0. OS/2
2.0 can be installed in either a primary partition or a logical drive
within the extended partition.
Important: Some operating systems, such as AIX, use their own
disk utility program to set up partitions. The partitions for such
operating systems are created when you actually install the
operating systems. You must leave sufficient space on the hard
disk to accommodate these operating systems.
To create the partition or logical drive for OS/2 2.0:
1. Make sure that the line is highlighted. IfFree Space it is not,
press the Up Arrow ( ) or Down Arrow ( ? ? ) key until it is
highlighted.
2. Press Enter to display the Options menu.
3. Select Create Partition and press Enter.
4. Type the size (in MB) of the partition or logical drive you are
creating.
5. Specify whether this partition is a primary partition or a logical
drive within the extended partition.
If you have already marked three partitions as primary
partitions, you might want to select Extended Logical Drive for
OS/2 2.0. Your hard disk can be made up of a maximum of
four primary partitions or three primary partitions and multiple
Chapter 4. Installing Multiple Operating Systems 47
logical drives within one extended partition. So, if you create a
primary partition for OS/2 2.0 when three primary partitions
already exist, you cannot create any logical drives.
6. Specify the location of the partition or logical drive you want to
create.
Note: This option is not available when the amount of free
space equals the size of the request.
Specifying Options for the OS/2 2.0 Partition or Logical
Drive
Once you have set up the partition or logical drive, you use the
Options menu choices to specify certain information. For example,
you use the Options menu to give the partition or logical drive a
name.
To specify options:
1. Press Enter to display the Options menu.
2. Highlight Add to Boot Manager Menu and press Enter.
3. Type the name you want to assign to this partition or logical
drive, and press Enter.
4. Press Enter to display the Options menu.
5. Highlight Set Installable and press Enter.
You must select Set Installable for this partition or logical drive.
By selecting Set Installable, you indicate which partition or
logical drive should be used for OS/2 2.0.
6. Use the Set startup values choice if you are going to have
multiple operating systems installed. (You use Set startup
values to configure the Boot Manager environment. In this
window, you indicate how you want the Boot Manager startup
menu displayed.)
Note: You can indicate how you want your Boot Manager
environment configured during this part of installation,
or you can choose to configure the environment after
installation. To configure the Boot Manager
environment after installation, use the FDISKPM utility
48OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
program. (FDISKPM includes most of the features of
FDISK, but it is displayed in a Presentation Manager
window.) To start FDISKPM after installation, type
FDISKPM at an OS/2 command prompt.
Chapter 4. Installing Multiple Operating Systems 49
When you select Set startup values from the Options menu of
FDISK, the following screen is displayed:
+-----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------+
a. Specify the default drive:
1) Highlight the line that contains the information for the
operating system you want preselected at startup time.
For example, if you want OS/2 2.0 to be the preselected
choice on the Boot Manager startup menu, highlight
the line. OS/2 2.0
2) Press Enter to display the Options menu.
3) Select Set startup values.
4) With Default highlighted, press Enter. Notice that the
name of the partition you chose is listed next to
Default.
b. Set the menu display time:
1) Indicate how long you want the Boot Manager startup
menu displayed when you start your system. If you
want the menu displayed for a certain period of time
before the default operating system starts, accept the
value of Yes. If you want the menu to be displayed
indefinitely (until you explicitly select a choice from the
50OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
menu), highlight Timer and press Enter to change the
value to No.
2) If you selected Yes for Timer, indicate how long you
want the menu displayed before the default operating
system is started. You can either accept the value
listed next to Timeout or you can change the value. To
change the value:
a) Select Timeout.
b) Type the amount of time (in seconds) that you want
the menu displayed before the preselected
operating system is automatically started.
c) Press Enter.
c. Set the menu mode to indicate how you want the Boot
Manager startup menu to be displayed.
You can select Normal or Advanced. The normal mode
menu looks like this:
+--------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+--------------------------------------+
The following screen shows the same menu in the
advanced mode format.
Chapter 4. Installing Multiple Operating Systems 51
+-----------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------+
To change the mode that is currently displayed:
1) Highlight Mode.
2) Press Enter.
d. Press F3 to update your FDISK screen.
Saving Your Changes
Once you have set up your hard disk, you must save your
changes.
1. Press F3.
2. Select Save and Exit and press Enter.
The options you select during your FDISK session will not be
active until you select Save and Exit and press Enter.
Note that you will be asked to reinsert the Installation Diskette and
the numbered diskettes.
52OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Continuing with OS/2 2.0 Installation
Once all your partitions are set up, continue installing the OS/2
Version 2.0 operating system. Follow the instructions on the
screen.
When the Installation Drive Selection screen is displayed, select
option 1, Accept the drive.
Selecting the Operating System Features
Once the hard disk of your computer is set up, you see the OS/2
Setup and Installation screen. In this part of installation, you make
choices about which features of the operating system you want to
install.
If you need assistance in completing the screen, press the F1 key
to see more information about your choices. (Or, you can refer to
Chapter 2, 蘒nstalling OS/2 2.0 as the Only Operating System?on
page 9, which provides additional information about making
selections on the screen.)
Formatting Logical Drives
If you have any logical drives that you want to format, you can do
so by selecting Format from the Options menu of the OS/2 Setup
and Installation screen. For example, if you want to format one of
your logical drives for the High Performance File System, you
would do the following:
1. Select Options from the menu bar of the OS/2 Setup and
Installation screen.
2. Select Format.
3. Specify the High Performance File System.
Viewing the Tutorial
After OS/2 installation is completed, you will see the OS/2 Tutorial.
After you complete the tutorial, install any other operating systems
for which you have created partitions.
Chapter 4. Installing Multiple Operating Systems 53
Installing Other Operating Systems
When the Boot Manager and OS/2 2.0 are installed, you can install
the other operating systems.
54OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Do you have more than one primary partition?
If you set up more than one primary partition (other than the
Boot Manager partition) when you set up your hard disk, follow
this procedure before you begin the installation of the operating
systems.
You need to indicate which primary partition should be used for
the operating system you are installing. For example, suppose
three partitions (in addition to the Boot Manager partition) are
set up on your hard disk: two primary partitions and one
extended partition containing logical drives. If you want to
install OS/2 Version 1.3 in the first primary partition, you have
to make sure that the first primary partition is marked as
installable.
To set the partition to installable, use FDISKPM. (FDISKPM
includes most of the features of FDISK, but it is displayed in a
Presentation Manager window.)
1. Select OS/2 System.
2. Select Command Prompts.
3. Select OS/2 Window.
4. Type fdiskpm and press Enter.
The drive letter (for example, C:) is shown next to the primary
partition that is active. (Remember that only one primary
partition can be active, or accessible, at a time.) If the partition
in which you want to install the operating system is not the
active primary partition, do the following:
1. Highlight the partition in which you want to install the
operating system.
2. Select Options from the menu bar.
3. Select Set Installable.
4. Select Options from the menu bar.
5. Select Exit.
6. Select the Save pushbutton from the window that is
displayed.
Chapter 4. Installing Multiple Operating Systems 55
Once you set the correct primary partition as installable (if you
have more than one primary partition), you can begin the
installation of the other operating systems.
Note: If you going to install DOS and a version of the OS/2
operating system in the same primary partition, refer to
Chapter 3, 嗀dding OS/2 2.0 to a DOS System?on page 17
for instructions. Remember that, to use the Dual Boot
feature, you must install DOS in the partition before you
install the OS/2 operating system.
1. Insert the installation diskette from the operating system you
are installing. Then, press and hold Ctrl+Alt, and press Del to
restart the system.
2. During installation, make sure that you install the operating
system in the desired partition. If you are asked whether you
want to format the partition, indicate that you do. FDISK sets
up partitions but does not format them.
3. Press and hold Ctrl+Alt, and press Del to restart the system.
4. If you installed OS/2 Version 1.3 or DOS Version 5.0, you will
need to make the Boot Manager partition startable. You
should also follow the steps outlined below if, for any reason,
the Boot Manager startup menu does not appear as you
specified it during installation of the OS/2 Version 2.0 operating
system. (For example, if you installed multiple operating
systems and wanted the Boot Manager startup menu to appear
but, instead, one of the other operating systems starts, you
would need to make the Boot Manager partition startable. In
DOS terminology, this is the same as making the partition
active.) You can use the version of FDISK (or its equivalent)
from the operating system that is active to make the Boot
Manager partition startable. Or, you can do the following:
a. Insert the OS/2 Installation Diskette into drive A.
b. Press and hold Ctrl+Alt, and press Del to restart the
system.
c. When prompted to do so, remove the Installation Diskette,
insert Diskette 1, and press Enter.
d. When the Welcome screen is displayed, press Esc to
display an OS/2 command prompt.
56OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
e. Type fdisk and press Enter.
f. Make sure that the Boot Manager partition is highlighted.
If it is not, press the Up Arrow ( ) or Down Arrow () key ? ?
until it is highlighted.
g. Press Enter to display the Options menu.
h. Select Make Startable and press Enter.
i. Press F3 to save your changes.
j. Select Save and Exit and press Enter.
k. Remove the diskette from drive A.
l. Press and hold Ctrl+Alt, and press Del to restart the
system.
5. If one of your primary partitions is set up for Dual Boot, copy
the BOOT.COM file from OS/2 2.0 to the Dual Boot partition.
(Copying the BOOT.COM file will replace the versions supplied
by the other operating systems.)
6. If you have installed AIX, you should add it to the Boot
Manager startup menu. With OS/2 running, type FDISKPM at
an OS/2 command prompt. Then do the following:
a. Highlight the line that contains information about AIX.
b. Select Options from the menu bar.
c. Select Add to Boot Manager menu.
d. Type a name for the partition and press Enter.
e. Select Options from the menu bar.
f. Select Exit.
g. Select the Save pushbutton from the window that is
displayed.
You will now be able to select AIX from the Boot Manager
startup menu.
Chapter 4. Installing Multiple Operating Systems 57
58OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Chapter 5. Alternative Ways to Install
This chapter describes alternative ways to install the OS/2
operating system. It is intended primarily for the person who will
be setting up workstations for other users.
Included in this chapter is information on installing OS/2 2.0 using
a response file. The chapter also includes a section on modifying
the response file that is shipped with the OS/2 installation
diskettes.
This chapter also explains how to redirect the installation process
so that you can install from a source other than diskette drive A.
Note that a brief overview of redirected installation is provided.
Detailed information about managing remote installations can be
found in OS/2 Version 2.0 Remote Installation and Maintenance
(GG24-3780).
Understanding the Response File Installation
If you have installed a previous version of the OS/2 operating
system or if you have installed other operating systems, you are
probably familiar with the typical installation procedure: you insert
diskettes and answer screen prompts. When you use a response
file, it is not necessary to answer any prompts. All the answers
are in the response file. You can place the response file on
Diskette 1 and begin the installation as usual. Or, you can place
the response file on another source. (See 蘒nstalling OS/2 2.0 from
a Source Other than Drive A?on page 63.) In either case, the
installation program will read the file (instead of prompting the
user) for the installation information.
+ Copyright IBM Corp. 1991 59
Modifying the Response File
A response file is included on the OS/2 installation diskettes.
When you install the operating system, this response file (named
SAMPLE.RSP) is placed in the OS2\INSTALL directory. So, after
you install the operating system on your own system, you can
modify the sample response file and then use it for installation on
another workstation. You use an editor (such as the System
Editor) to modify the response file.
The following is an example of what the response file looks like.
60OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
**************************************************************
*AlternateAdapter *
* *
* Specifies secondary adapter for two display systems. *
* This should be a lower or equal resolution display since *
* the highest resolution display will be primary for PM. *
* *
* Valid Parms: *
* *
* 0=none (DEFAULT) *
* 1=Other than following (DDINSTAL will handle) *
* 2=Monochrome Printer Adapter *
* 3=Color Graphics Adapter *
* 4=Enhanced Graphics Adapter *
* 5=Video Graphics Adapter *
* 6=8514/A Adapter *
* 7=XGA Adapter *
**************************************************************
AlternateAdapter=0
**************************************************************
*BaseFileSystem *
* *
* Specifies which file system should be used to format *
* the install partition *
* *
* Valid Parms: *
* *
* 1=HPFS (DEFAULT) *
* 2=FAT *
**************************************************************
BaseFileSystem=2
**************************************************************
* CDROM *
* *
* Specifies which, if any, CD ROM IFS files should be *
* installed. *
* *
* Valid Parms: *
* *
* 0 = None *
* 1 = All *
* 2 = CD-ROM IFS (DEFAULT) *
* 3 = IBM CD-ROM Device Drivers *
**************************************************************
CDROM=2
As you can see, the file contains comments about the various
options and lists the values you should enter if you want
something other than the default value. If you do not modify a
response, the default value is used.
Chapter 5. Alternative Ways to Install 61
For example, suppose you want to set up a system in which no
CD-ROM support is required. In the response file, you would
indicate that no support be installed by entering:
CDROM=0
The following is a list of the steps you would perform to modify a
response file and then place the response file on Diskette 1.
1. Make a copy of the SAMPLE.RSP file (located in the
OS2\INSTALL directory).
2. Use an editor (such as the System Editor) to modify the file.
The file contains comments that explain each of the installation
options.
3. Once you have modified and saved the response file, copy it to
Diskette 1 with the name OS2SE20.RSP.
Note: You can place the response file in a location other than
Diskette 1. For example, the response file could be
located on the server in a local area network. The next
section describes the process for pointing to a source
other than drive A for installation information.
4. Copy the RSPINST.EXE file (located in the OS2\INSTALL
directory) to Diskette 1.
5. Begin the installation of the workstation by inserting the
Installation Diskette and restarting the system.
6. When prompted, switch diskettes and press Enter.
From this point, the installation program will prompt only for the
insertion of diskettes. No other installation screens will appear.
Note that you can use this procedure to install the same set of
options on multiple workstations. Using a response file, you can
make sure that all workstations in an area are set up with the
same set of options.
62OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Installing OS/2 2.0 from a Source Other than Drive A
The operating system typically is installed from a diskette inserted
into drive A. However, with OS/2 2.0, you can redirect the
installation by specifying a source other than the diskettes in drive
A. For example, you can direct the installation to a CD-ROM. In a
local area network environment, for example, any or all of the
workstations connected to a server could request that the
installation source be a drive on the server. This type of
installation requires additional software (such as a LAN support
product).
Redirecting the Installation
There are several ways to redirect the installation of OS/2 2.0.
You can modify information on Diskette 1 to point to another
source. If that source contains a copy of the installation diskettes,
the user is prompted for choices but is not asked to swap
diskettes. The source can also be specified in a response file. If a
response file exists on the redirected source, the user is not
prompted for any choices.
You can modify the CONFIG.SYS file that is found on Diskette 1 to
indicate that installation should proceed from a source other than
drive A.
? One of the ways to indicate redirection is to modify the
PROTSHELL statement of the CONFIG.SYS file. For example,
to point to an alternative source for installation information,
you would add a drive letter and file name to the
PROTSHELL= statement:
PROTSHELL=SYSINST1.EXE SYSINST2.EXE Z:\OS2SE20
When the system reads Diskette 1, it finds this statement and
looks for the SYSINST1.EXE and SYSINST2.EXE installation
programs in the specified directory of drive Z. Installation then
proceeds from that drive, and there is no prompting for
insertion of diskettes.
? Instead of modifying the PROTSHELL statement, you can add
an environment variable to the CONFIG.SYS file. For example,
you could add the following statement to the file:
Chapter 5. Alternative Ways to Install 63
SET SOURCEPATH=Z:\OS2SE20
You would then add the same drive and file name to the PATH
and DPATH statements of the CONFIG.SYS file.
Another way to specify redirection of installation is to use the
response file on Diskette 1 to point to another source. For
example, you can modify the sample response file by adding the
following statement to the response file:
SourcePath=Z:\OS2SE20
Then, when this response file is placed on Diskette 1, the
installation program looks to the drive specified for its installation
information.
A response file can be copied to the directory specified above
rather than to Diskette 1. If a response file (with the correct name
OS2SE20.RSP) exists in both places, the file on the diskette is
checked first.
Setting Up an Alternative Installation Source
The OS/2 installation program can use a drive other than A as its
installation source. This redirected drive can be a CD-ROM, a
drive on the hard disk, or a remote drive that is connected to a
LAN. If the redirected drive requires special software, you will
have to copy those files to Diskette 1 and modify the CONFIG.SYS
file on Diskette 1. The following section describes the steps
needed to install from a CD-ROM. For information on installing
from other drives, refer to OS/2 Version 2.0 Remote Installation and
Maintenance (GG24-3780).
Installing from a CD-ROM Device
When the installation program begins, it searches all the drives on
a system for a file named OS2SE20.SRC. If that file is found by the
installation program, it reads the first line of the file to find the
installation source information.
When OS/2 is delivered on a CD-ROM, it already contains the
OS2SE20.SRC file. You begin the installation from diskette, as
64OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
usual, but after a certain point, the installation is redirected to the
CD-ROM.
If the OS/2 Version 2.0 operating system was delivered on a
CD-ROM, do the following:
1. Insert the CD-ROM into its drive.
2. Insert the Installation Diskette into drive A.
3. Turn on the computer. If the computer is already on, press
and hold the Ctrl and Alt keys, and press Del to restart the
system.
4. Follow the prompts that are displayed on the screen. You will
be asked to switch diskettes before the installation program
begins to read the OS2SE20.SRC file on the CD-ROM drive.
Chapter 5. Alternative Ways to Install 65
66OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Appendix A. Customizing the Operating System
This appendix describes how you can customize your operating
system without completely reinstalling it.
You can use the System Configuration folder to change choices
such as the time and date, your screen colors and window
borders, and to change your mouse for right- or left-hand use.
Select the System Configuration folder from the OS/2 System
folder to see the objects (for example, the mouse) that you can
customize.
You can also replace the user interface (sometimes called a shell)
that comes with the OS/2 Version 2.0 operating system. You
replace the user interface by modifying a statement in the
CONFIG.SYS file. See the online Master Index for details on
replacing the user interface.
Features that You Can Change or Add
After you install the operating system, you might decide to change
your mouse or display. Or, you might decide that you want to add
some features that you chose not to add during the initial
installation. You can make the change or add the features without
completely reinstalling the operating system.
The following are the features you can add to your system:
?
CD-ROM Device Support
Provides system support for CD-ROM devices.
?
Documentation
Adds the OS/2 Tutorial, the OS/2 Command Reference, or the
REXX Information.
? Fonts
+ Copyright IBM Corp. 1991 67
Determines the print style for your system. The OS/2
operating system offers bit-map fonts and fonts in Adobe ** Type
1 format for displaying and printing data on many output
devices; however, the bit-map fonts are not supported for
printing on vector devices, such as plotters. For compatibility,
the operating system also supports the Presentation Manager
outline fonts.
When no fonts are selected, the system default font and the
Helvetica ** fonts are installed.
? Optional System Utilities
Provide a full set of system utility programs to:
?Back up the hard disk
?Change file attributes
?Display the directory tree
?Manage partitions
?Label diskettes
?Link object modules
?Convert, display, and print pictures
?Use PMREXX
?Recover files
?Restore backed-up files
?Sort files
?Install OS/2 compilers.
? Tools and Games
Provide productivity aids (such as an enhanced editor and a
calculator) as well as games.
?
OS/2 DOS and Windows Support
Enables DOS and Microsoft Windows programs to run on the
OS/2 operating system. If you select this feature, you will be
prompted to indicate which of your existing DOS and Windows
applications you want to migrate to OS/2 2.0.
?
High Performance File System
** Trademark of Adobe Systems Incorporated.
** Trademark of the Linotype Company.
68OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Provides fast access to large disk volumes. Features of the
High Performance File System include:
?File names up to 254 characters in length
?Large file support
?Strategic allocation of directory structures
?Processing of metacharacters that are generally used for
displaying and printing graphics.
?
REXX
Installs the REXX Operating System/2 procedures language.
This batch language can be used to develop Systems
Application Architecture * (SAA*) programs.
? Serial Device Support
Provides system support for attached serial devices, such as a
modem, a serial plotter, or a serial printer assigned to a
communication port. This choice is not required for mouse
support.
? Serviceability and Diagnostic Aids
Provide information primarily for a technical coordinator to
isolate and correct system problems.
?
Optional Bitmaps
Provides a set of bitmaps that you can use to change the
background of your system.
Changing Your Setup or Adding Features
To change your setup or add a feature, do the following:
1. Select OS/2 System.
2. Select System Setup.
3. Select Selective Install.
* Trademark of the IBM Corporation.
Appendix A. Customizing the Operating System 69
4. Select the item you want to change (for example, mouse,
keyboard, display, or country). After making any changes,
select the OK pushbutton.
5. On the next screen, select the features that you want to install.
Note: If a More pushbutton accompanies a feature, you must
select the pushbutton to view the features. For
example, if you want to install a document, select
Documentation and then select the More pushbutton to
display a list of documents. Then, select the document
that you want to add.
6. When prompted, insert the numbered installation diskettes to
complete the process.
70OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Appendix B. Diagnosing System Problems
The operating system provides programs that help you gather
information to isolate and correct system problems. You can learn
more about this information by selecting topics under the Problem
determination heading in the Master Index.
If your system has failed, however, it will not be possible to get
online help. This appendix provides information about such
system failures, and about:
? Recovering the CONFIG.SYS file
? Recovering user and system INI files
? Recovering from errors on the hard disk
? Responding to installation errors.
Note: Backing up your system regularly may help you avoid
having to re-create files in the event of a system failure.
Recovering the CONFIG.SYS File
The CONFIG.SYS file contains command statements that set up
your system. If the file is changed incorrectly, you cannot restart
the system or edit the file. To recover the CONFIG.SYS file:
1. Insert the Installation Diskette into drive A.
2. Turn on the computer.
If the computer is already on, press and hold Ctrl+Alt, and
press Del to restart the system.
3. When the logo screen appears, remove the Installation Diskette
and insert Diskette 1.
4. Press Enter.
5. When the Welcome screen appears, press Esc.
6. Change to the drive where your operating system resides. For
example, if the operating system is in drive C, type:
C:
and press Enter.
+ Copyright IBM Corp. 1991 71
7. Rename the damaged CONFIG.SYS file by typing
REN CONFIG.SYS CONFIG.BAD
and pressing Enter.
8. Copy the CONFIG.SYS backup file to the root directory of the
drive where your operating system resides. (The CONFIG.SYS
backup file was created during installation.) For example, if
the operating system is in drive C, type:
COPY C:\OS2\INSTALL\CONFIG.SYS C:\CONFIG.SYS
and press Enter.
9. Remove Diskette 1 from drive A.
10. Press and hold Ctrl+Alt, and press Del to restart the system.
Note: If you changed the CONFIG.SYS file after installing the
operating system, use an editor to either correct the
damaged file (now named CONFIG.BAD) or update the
current CONFIG.SYS file.
Recovering User and System INI Files
System settings, such as application defaults, display options, and
file options, are defined in the OS2.INI startup file in the OS2
directory of your hard disk. Information about installed fonts and
printer drivers is contained in a system file called OS2SYS.INI. If
you receive a message that the OS2.INI file has been damaged,
replace both of these files as follows:
1. Insert the Installation Diskette into drive A.
2. Turn on the computer.
If the computer is already on, press and hold Ctrl+Alt, and
press Del to restart the system.
3. After the logo screen appears, remove the Installation Diskette
and insert Diskette 1.
4. Press Enter.
5. When the Welcome screen is displayed, press Esc.
6. Change to the drive where your operating system resides. For
example, if the operating system is in drive C, type:
72OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
C:
and press Enter.
7. Change to the OS2 subdirectory by typing
CD \OS2
and pressing Enter.
8. Erase the current OS2.INI file by typing
ERASE OS2.INI
and pressing Enter.
9. Create a new user INI file by typing
MAKEINI OS2.INI INI.RC
and pressing Enter.
10. Erase the current OS2SYS.INI file by typing
ERASE OS2SYS.INI
and pressing Enter.
11. Create a new system INI file by typing
MAKEINI OS2SYS.INI INISYS.RC
and pressing Enter.
Note: The MAKEINI.EXE file was added to the OS2 directory of
your hard disk during installation of the operating
system.
12. Remove Diskette 1 from drive A.
13. Press and hold Ctrl+Alt, and press Del to restart the system.
You can protect your INI files by copying back levels of the files
each time you start your system. For example, you could include
the following statements in your CONFIG.SYS file:
CALL=C:\OS2\XCOPY.EXE C:\OS2\*.INX c:\OS2\*.INY
CALL=C:\OS2\XCOPY.EXE C:\OS2\OS2*.INI C:\OS2\*.INX
These statements make a copy of your current INI files and also
make a copy of the INI files you previously backed up.
Appendix B. Diagnosing System Problems 73
By copying your files each time you start the system, you will
always be able to recover an earlier verion of the INI files.
Recovering from Errors on the Hard Disk
The CHKDSK command with the parameter /F can be used to
correct disk and directory errors. However, when you use the /F
parameter, no activity can occur on the disk. Therefore, if you
need to correct errors on the drive from which you normally start
the operating system, you must use the version of CHKDSK that is
on the installation diskettes (instead of the version that has been
installed on the hard disk).
To correct errors on the drive from which you normally start the
operating system:
1. Insert the Installation Diskette into drive A.
2. Turn on the computer.
If the computer is already on, press and hold Ctrl+Alt, and
press Del to restart the system.
3. When the logo screen appears, remove the Installation Diskette
and insert Diskette 1.
4. Press Enter.
5. When the Welcome screen appears, press Esc.
6. When the OS/2 command prompt appears, remove Diskette 1
and insert Diskette 2 (the diskette that contains the CHKDSK
command).
7. To correct the errors on your hard disk, type the following at
the command prompt:
CHKDSK C: /F
and press Enter. (If your operating system resides on a drive
other than C, type the appropriate drive letter after the
CHKDSK command.)
8. Remove the diskette from drive A.
9. Press and hold Ctrl+Alt, and press Del to restart the system.
74OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Responding to Installation Errors
If you receive an error message while installing the operating
system, take the appropriate corrective action.
Only some files were copied. You might be out of disk space.
Explanation: (1) The installation program could not transfer one or
more files, because a version of the files already exists on the hard
disk with the read-only, system, or hidden attributes set.
(2) The installation program stopped transferring files because there
was not enough hard disk space.
Action: (1) Return the attributes of the OS/2 files to their original
setting. Use the ATTRIB command to remove the read-only
attributes.
(2) Move non-OS/2 operating system files out of the installation
partition. You can store these files in the extended partition or on a
diskette. If you intend to format the installation partition, remember
to use the BACKUP command to save any important files.
An error occurred when the installation program tried to copy a file.
Explanation: (1) The installation program could not transfer one or
more files, because a version of the files already exists on the hard
disk with the read-only, system, or hidden attributes set.
(2) The installation program stopped transferring files because there
was not enough hard disk space.
(3) The hard disk might contain errors.
Action: (1) Return the attributes of the OS/2 files to their original
settings. Use the ATTRIB command to remove the read-only
attributes.
(2) Move non-OS/2 operating system files out of the installation
partition. You can store these files in an extended partition or on a
diskette. If you intend to format the installation partition, remember
to use the BACKUP command to save any important files.
(3) Follow the CHKDSK procedure outlined in the section
ecovering from Errors on the Hard Disk?on page 74.
Appendix B. Diagnosing System Problems 75
An error occurred when the installation program tried to transfer
system files to your hard disk. Your hard disk might be unusable.
Explanation: The installation program stopped transferring files
because there was not enough hard disk space. The system files
consist of the OS2LDR and OS2KRNLI files on the Installation
Diskette.
Action: Move non-OS/2 operating system files out of the installation
partition. You can store these files in an extended partition or on a
diskette. If you intend to format the installation partition, remember
to use the BACKUP command to save any important files.
An error occurred while trying to run a program.
Explanation: (1) The installation program could not find one of the
following programs: FDISK, MAKEINI, CHKDSK, FORMAT, or
UNPACK.
(2) The installation program could not run a program, because there
is not enough memory to install it.
Action: (1) Verify that the program exists on the diskette or
installation partition.
(2) Add more system memory.
The installation program was unable to load a module into memory.
Explanation: The installation program could not load a system
module because there is not enough memory.
Action: Add more system memory.
Making the Boot Manager Active
If you set up multiple operating systems but the Boot Manager
startup menu does not appear as you specified it during
installation, you will need to make the Boot Manager partition
startable. See page 56 for instructions on making the Boot
Manager partition startable.
76OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Appendix C. Examples of Installing OS/2 2.0 and
Partitioning Your Hard Disk
This appendix shows four examples of partitioning the hard disk of
your system during the installation of the OS/2 Version 2.0
operating system.
Example 1 shows you how to delete an existing partition and set
up two areas on the hard disk: a primary partition for OS/2 2.0
and a logical drive within the extended partition for data. The
remaining examples show you how to set up your system so that
you can install multiple operating systems in their own partitions.
Example 1: Creating a Primary Partition and a Logical
Drive for Data
This example shows you how to set up a primary partition for OS/2
2.0 and a logical drive in the extended partition. The logical drive
will be used to hold data.
This example assumes that you are installing on a hard disk that
currently has one partition that takes up the entire disk.
In this example, you will create:
? A 30MB primary partition
? A 12MB logical drive within the extended partition.
This example does not involve the installation of the Boot
Manager.
1. Back up any data you want to save from the existing partition.
(Use the BACKUP command from your existing operating
system.)
2. Insert the Installation diskette, restart your system, and follow
the instructions on the screen.
3. At the Installation Drive Selection screen, select option 2,
Specify a different drive or partition.
4. Delete the existing partition (which you have backed up):
+ Copyright IBM Corp. 1991 77
a. Press Enter to display the Options menu.
b. Select Delete Partition.
5. Create the primary partition:
a. Press Enter to display the Options menu.
b. Select Create Partition.
c. Type the size of the primary partition (in this example, 30)
and press Enter.
d. Select Primary Partition and press Enter.
e. Select Create at Start of Free Space and press Enter.
6. Create the logical drive for data:
a. Highlight the line. Free Space
b. Press Enter to display the Options menu.
c. Select Create Partition.
d. Type the size of the extended logical drive (in this
example, 12) and press Enter.
e. Select Extended Logical Drive and press Enter.
f. Select Create at Start of Free Space and press Enter.
7. Exit FDISK:
a. Press F3.
b. Select Save and Exit and press Enter.
8. Continue with OS/2 installation until you see the OS/2 Setup
and Installation screen.
9. Format the logical drive:
a. When the OS/2 Setup and Installation screen is displayed,
select Select features and install.
b. Specify any changes to the System Configuration screen.
c. When the next OS/2 Setup and Installation screen is
displayed, select Options from the menu bar.
d. Select Format.
e. Indicate which file system you want to use to format the
logical drive.
Note that you can format the logical drive for a file system
that is different from the one with which you formatted the
primary partition. For example, if the primary partition is
formatted for the High Performance File System, you can
format the logical partition for the File Allocation Table file
78OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
system. This way, you can have both file systems installed
on the hard disk.
10. Finish the installation of the OS/2 Version 2.0 operating
system.
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 79
Example 2: Installing the Boot Manager, OS/2 2.0, and
One Additional Operating System
This example shows you how to set up a partition for the Boot
Manager, a primary partition for DOS, and a logical drive for OS/2
2.0.
This example assumes that you are installing on a hard disk that
currently has one partition that takes up the entire disk.
In this example, you will create:
? A 4MB primary partition for DOS
? A 30MB logical drive for OS/2 2.0.
You will also install the Boot Manager in its own partition.
1. Back up any data you want to save from the existing partition.
(Use the BACKUP command from your existing operating
system.)
2. Insert the Installation diskette, restart your system, and follow
the instructions on the screen.
3. At the Installation Drive Selection screen, select option 2,
Specify a different drive or partition.
4. Delete the existing partition (which you have backed up):
a. Press Enter to display the Options menu.
b. Select Delete Partition.
5. Install the Boot Manager partition:
a. Press Enter to display the Options menu.
b. Select Install Boot Manager.
c. Select Create at Start of Free Space and press Enter.
6. Create the DOS partition:
a. Highlight the line. Free Space
b. Select Create Partition.
c. Type the size of the primary partition (in this example, 4)
and press Enter.
d. Select Primary Partition and press Enter.
e. Select Create at Start of Free Space and press Enter.
80OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
f. Press Enter to display the Options menu.
g. Select Add to Boot Manager Menu.
h. Type DOS and press Enter.
7. Create the OS/2 Version 2.0 logical drive:
a. Highlight the line. Free Space
b. Press Enter to display the Options menu.
c. Select Create Partition.
d. Type the size of the extended logical drive (in this
example, 30) and press Enter.
e. Select Extended Logical Drive and press Enter.
f. Select Create at Start of Free Space and press Enter.
g. Press Enter to display the Options menu.
h. Select Add to Boot Manager Menu.
i. Type OS/2 2.0 and press Enter.
8. Set up OS/2 Version 2.0 as the default:
a. Highlight the line. OS/2 2.0
b. Press Enter to display the Options menu.
c. Select Set startup values.
d. Select Default.
e. Press F3.
9. Indicate which partition should be used for the OS/2 2.0
installation:
a. Highlight the line. OS/2 2.0
b. Press Enter to display the Options menu.
c. Select Set installable.
10. Exit FDISK:
a. Press F3 to exit FDISK.
b. Select Save and Exit and press Enter.
11. Finish the installation of the OS/2 Version 2.0 operating
system.
12. When OS/2 installation is completed, insert the DOS
installation diskette. Then, press and hold Ctrl+Alt, and press
Del to restart the system.
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 81
Example 3: Installing the Boot Manager, OS/2 2.0, and
Two Additional Operating Systems
This example shows you how to set up a partition for the Boot
Manager, a primary partition for DOS, a primary partition for OS/2
Version 1.3, and a logical drive for OS/2 Version 2.0.
This example assumes that you are installing on a hard disk that
currently has one partition that takes up the entire disk.
In this example, you will create:
? A 4MB primary partition for DOS
? A 20MB primary partition for OS/2 Version 1.3
?
A 30MB logical drive for OS/2 Version 2.0.
You will also install the Boot Manager in its own partition.
1. Back up any data you want to save from the existing partition.
(Use the BACKUP command from your existing operating
system.)
2. Insert the Installation diskette, restart your system, and follow
the instructions on the screen.
3. At the Installation Drive Selection screen, select option 2,
Specify a different drive or partition.
4. Delete the existing partition (which you have backed up):
a. Press Enter to display the Options menu.
b. Select Delete Partition.
5. Install the Boot Manager partition:
a. Press Enter to display the Options menu.
b. Select Install Boot Manager.
c. Select Create at Start of Free Space and press Enter.
6. Create the DOS partition:
a. Highlight the line. Free Space
b. Select Create Partition.
c. Type the size of the primary partition (in this example, 4)
and press Enter.
d. Select Primary Partition and press Enter.
82OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
e. Select Create at Start of Free Space and press Enter.
f. Press Enter to display the Options menu.
g. Select Add to Boot Manager Menu.
h. Type DOS and press Enter.
7. Create the OS/2 Version 1.3 partition:
a. Highlight the line. Free Space
b. Select Create Partition.
c. Type the size of the primary partition (20) and press Enter.
d. Select Primary Partition and press Enter.
e. Select Create at Start of Free Space and press Enter.
f. Press Enter to display the Options menu.
g. Select Add to Boot Manager Menu.
h. Type OS2 1.3 and press Enter.
8. Create the OS/2 2.0 logical drive:
a. Highlight the line. Free Space
b. Press Enter to display the Options menu.
c. Select Create Partition.
d. Type the size of the extended logical drive (in this
example, 30) and press Enter.
e. Select Extended Logical Drive and press Enter.
f. Select Create at Start of Free Space and press Enter.
g. Press Enter to display the Options menu.
h. Select Add to Boot Manager Menu.
i. Type OS/2 2.0 and press Enter.
9. Set up OS/2 Version 2.0 as the default:
a. Highlight the line. OS/2 2.0
b. Press Enter to display the Options menu.
c. Select Set startup values.
d. Select Default.
e. Press F3.
10. Indicate which partition should be used for the OS/2 2.0
installation:
a. Highlight the line. OS/2 2.0
b. Press Enter to display the Options menu.
c. Select Set installable.
11. Exit FDISK and continue with installation:
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 83
a. Press F3 to exit FDISK.
b. Select Save and Exit and press Enter.
c. Continue with OS/2 installation.
12. Install DOS
a. Insert the DOS installation diskette.
b. Press the Ctrl and Alt keys, and then press Del to restart
the system.
13. Restart the system by pressing the Ctrl and Alt keys and then
pressing the Del key.
14. Select OS/2 2.0 from the Boot Manager startup menu.
15. Make the OS/2 1.3 partition active.
a. Select OS/2 System.
b. Select Command Prompts.
c. Select OS/2 Window.
d. Type:
fdisk
and press Enter.
e. Highlight the line. OS2 1.3
f. Press Enter to display the Options menu.
g. Select Set Installable.
h. Press F3 to exit.
16. Install OS/2 Version 1.3
a. Insert the OS/2 Version 1.3 installation diskette.
b. Press the Ctrl and Alt keys, and then press the Del key to
restart the system.
17. Make the Boot Manager Startable:
a. With OS/2 1.3 running, select Manage Partitions from the
Utilities group.
b. Highlight the Boot Manager line.
c. Select Options.
d. Select Startable.
18. Restart the system to see the Boot Manager startup menu.
84OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Example 4: Installing Boot Manager without
Repartitioning the Entire Hard Disk
This example shows you how to install the Boot Manager and
install OS/2 2.0 without repartitioning the entire hard disk.
This example assumes that your current hard disk setup has a
primary partition (with DOS Version 4.0) and an extended partition.
In this example, you will preserve the primary partition that
contains DOS Version 4.0. You will delete the extended partition to
make room for OS/2 2.0 and the Boot Manager. In this example,
you will put the Boot Manager partition at the end of the hard disk.
In this example, you will create:
? A 30MB logical drive for OS/2 2.0
? A 10MB logical drive for data.
You will also install the Boot Manager in its own partition.
1. Back up any data you want to save from the existing extended
partition. (Use the BACKUP command from your existing
operating system.)
2. Insert the Installation diskette, restart your system, and follow
the instructions on the screen.
3. At the Installation Drive Selection screen, select option 2,
Specify a different drive or partition.
4. Delete the existing extended partition (which you have backed
up):
a. Highlight the line that contains information about the
extended partition.
b. Press Enter to display the Options menu.
c. Select Delete Partition.
5. Install the Boot Manager partition:
a. Press Enter to display the Options menu.
b. Select Install Boot Manager.
c. Select Create at End of Free Space and press Enter.
6. Create the OS/2 2.0 logical drive:
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 85
a. Highlight the line. Free Space
b. Press Enter to display the Options menu.
c. Select Create Partition.
d. Type the size of the extended logical drive (in this
example, 30) and press Enter.
e. Select Extended Logical Drive and press Enter.
f. Select Create at Start of Free Space and press Enter.
g. Press Enter to display the Options menu.
h. Select Add to Boot Manager menu.
i. Type OS/2 2.0 and press Enter.
7. Create the logical drive for data:
a. Highlight the line. Free Space
b. Press Enter to display the Options menu.
c. Select Create Partition.
d. Type the size of the extended logical drive (in this
example, 10) and press Enter.
e. Select Extended Logical Drive and press Enter.
f. Select Create at Start of Free Space and press Enter.
8. Set up OS/2 2.0 as the default:
a. Highlight the line. OS/2 2.0
b. Press Enter to display the Options menu.
c. Select Set startup values.
d. Select Default.
e. Press F3.
9. Indicate which partition should be used for the OS/2 2.0
installation:
a. Highlight the line. OS/2 2.0
b. Press Enter to display the Options menu.
c. Select Set installable.
10. Add a name for the DOS partition to the Boot Manager startup
menu:
a. Highlight the line that contains information about the DOS
partition.
b. Press Enter to display the Options menu.
c. Select Add to Boot Manager menu.
d. Type DOS and press Enter.
11. Exit FDISK:
86OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
a. Press F3 to exit FDISK.
b. Select Save and Exit and press Enter.
12. Continue with OS/2 installation until you see the OS/2 Setup
and Installation screen.
13. Format the logical drive:
a. When the OS/2 Setup and Installation screen is displayed,
select Select features and install.
b. Specify any changes to the System Configuration screen.
c. When the next OS/2 Setup and Installation screen is
displayed, select Options from the menu bar.
d. Select Format.
e. Indicate which file system you want to use to format the
logical drive.
14. Finish the installation of the OS/2 Version 2.0 operating
system.
Appendix C. Examples of Installing OS/2 2.0 and Partitioning Your Hard Disk 87
88OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Index
Boot Manager partition
A creating 41
Add to Boot Manager Menu placement of 31
choice 45 Boot Manager startup menu
adding OS/2 to a DOS system 17
configuring 48
after installation, adding example of 26
features 67
AIX, adding name to Boot Manager
startup menu 57 C
AIX, note about installing 42 caching 69
Assign C: Partition choice 45 CD-ROM, installing from 65
AUTOEXEC.BAT file Change Partition Name choice 45
creating or modifying for Dual changing partition sizes 38
Boot 21 CHKDSK command, recovering
migrating from a previous from errors on the hard disk 74
version 14 colors, changing screen 67
modifying to load DOS from Command Reference
within OS/2 32 adding after installation 70
choosing to install 14
communication port 69
B
? configuration options 67
basic installation 9 16 CONFIG.SYS file
bit-map fonts 67 creating or modifying for Dual
bitmaps, adding additional 69 Boot 21
BOOT command 24 migrating from a previous
Boot Manager
version 14
example of setting up three modifying to load DOS from
operating systems 82 within OS/2 32
example of setting up two recovering 71
operating systems 80 considerations for installing
FDISK utility 39
multiple operating systems 4
hard disk architecture 30 Create Partitions choice 45
hard disk management 30 creating
installation of 34partitions and logical drives 42
installation on existing the Boot Manager partition 41
system 37
the OS/2 partition 47
installation on new systems 36 creating or modifying
startup menu time, setting 50 AUTOEXEC.BAT and
system setup CONFIG.SYS 21
recommendations 31
+ Copyright IBM Corp. 1991 89
customization information, example of (continued)
migrating 14 formatting a data partition 77
customizing the system 67 installing Boot Manager with
three operating systems 82
installing Boot Manager with two
D
operating systems 80
date, changing 67 installing Boot Manager without
default operating system, setting repartitioning the entire
(for Boot Manager) 50 disk 85
default printer, choosing 15 installing DOS and OS/2 in
Delete Partition choice 46
separate partitions 80
deleting partitions 39 installing multiple partitions 80
diagnostic aids 69 installing three operating
directory structure, for Dual systems 82
Boot 19 setting up two partitions 77
documentation, online
extended partition 27
adding after installation 70
choosing during installation 14
DOS F
Dual Boot restriction 18 failures, system 71
DOS programs FDISK
installing in a Dual Boot examples of using 77
setup 22 screen 39
migrating 14 FDISKPM, description of 49
DOS 5.00 Upgrade, note about file systems, installing both 78
installing 32 fonts, adding after installation 67
DOS 5.0, note about installing 56 formatting a logical drive 14
drive mapping 29
Dual Boot
copying COMMAND.COM in a H
Boot Manager hard disk architecture 30
hard disk management 30
environment 57
Dual Boot feature high performance file system
requirements 19 Dual Boot restriction 18
restrictions 18
starting 24
I
increasing partition size 38
E INI files, recovering 72
error messages, installation 75 Install Boot Manager choice 45
example of installable, marking a partition
adding partitions to an existing as 46
hard disk 85
90OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
installation modem 69
after, adding features 67 more than one operating system,
basic 9?6 installing 25
installation, redirecting 59 mouse
installing customizing use of 67
AIX, note about 42tutorial on using 12
Boot Manager without multiple operating systems
repartitioning the entire considerations for installing 4
disk 85 installing 25
both file systems 78
from a drive other than A 59
more than one operating O
system 4 online documentation
multiple partitions, example adding after installation 70
of 80, 82 choosing during installation 14
online help
OS/2 on a DOS system 17
OS/2 only 9 for loading DOS from
other operating systems 54 diskette 7
with a response file 59 problem determination 71
interface, replacing 67 operating systems
installing additional 54
recommended partition sizes
L for 43
LAN installation 59 optional bitmaps 69
logical drive optional utilities 68
description of 27OS/2 Tutorial
formatting during adding after installation 70
installation 14 choosing to install 14
logo screen 10, 23OS/2 1.3, note about installing 56
outline fonts 67
M
Make Startable choice 46 P
marking a partition as partition
installation 46 accepting the default 10
messages, installation 75 adding a second 11
metacharacters 69 partition size and considerations,
migrating planning table 43
CONFIG.SYS and partitions
AUTOEXEC.BAT files 14 defining 39
customization information 14 restriction on number of 27
DOS programs 14 setting up 39
Windows programs 14
Index 91
Partitions Too Small warning 38 S
planning the Boot Manager
setup 31 screen colors, changing 67
plotter, utilities 69 serial printer or plotter 69
PM fonts 67 Set Installable choice 46
Set Startup Values choice 45
primary drive, changing 7 setting a partition installable 46
primary partitions
restriction on number of 27 setting the Boot Manager default
specifying which should be used operating system 50
for installation 54 setting up
partitions and logical drives 42
printer, choosing the default 15 two partitions, example of 77
problem determination 69, 71
problem information 71 sharing printer resources 69
shell, replacing 67
starting the Dual Boot feature 24
Q System Configuration folder 67
system problems, diagnosing 71
Quick Reference
description of x
installing with 3
T
technical coordinator 69
R timeout values, Boot Manager 50
time, changing 67
recommendations for a Boot
Manager setup 31 trouble shooting 71
recommended partition sizes 43 Tutorial
reconfigurable diskette drives 7 adding after installation 70
recovering choosing to install 14
from errors on the hard disk 74
from system failures 71?4
the CONFIG.SYS file 71 U
user and system INI files 72 Upgrade, DOS 5.00 32
redirecting installation 59 upgrading to DOS 5.00 before
installing Boot Manager 32
Remove from Boot Manager Menu user INI files, recovering 72
choice 45
replacing the user interface 67 user interface, replacing 67
response file installation 59 utilities, system 68
REXX information
adding after installation 70 W
choosing to install 14 window borders, changing 67
REXX program 69
Windows programs
installing in a Dual Boot
setup 22
92OS/2 32-Bit Operating System Installation Guide PRE-RELEASE COPY
Windows programs (continued)
migrating 14
Index 93
�
OVER6167.DOC
IBM OS/2 32-bit
Overview
Pre-Release Copy
Document Number 84F8465
October 15, 1991
First Edition October 1991 < *
The following paragraph does not apply to the United Kingdom or any
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION 嗀S IS?WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not apply
to you.
This publication could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time.
It is possible that this publication may contain reference to, or information
about, IBM products (machines and programs), programming, or services
that are not announced in your country. Such references or information
must not be construed to mean that IBM intends to announce such IBM
products, programming, or services in your country.
Requests for technical information about IBM products should be made to
your IBM Authorized Dealer or your IBM Marketing Representative.
IBM may have patents or pending patent applications covering subject
matter in this document. The furnishing of this document does not give
you any license to these patents. You can send license inquiries, in
writing, to the IBM Director of Commercial Relations, IBM Corporation,
Purchase, NY 10577.
+ Copyright International Business Machines Corporation 1991. All rights
reserved.
Note to U.S. Government Users ?Documentation related to restricted
rights ?Use, duplication or disclosure is subject to restrictions set forth
in GSA ADP Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v
About This Book ..... . . . . . . . . . . . . . . . . . . . . . . . vii
Using This Book ..... . . . . . . . . . . . . . . . . . . . . . . . vii
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Changes from Previous Versions ......... . . . . . . . . . . x
Chapter 1. Introducing OS/2 2.0 ......... . . . . . . . . . . 1
Introducing Folders and Objects ......... . . . . . . . . . . 2
Managing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . .5.
Selecting Objects . . . . . . . . . . . . . . . . . . . . . . . . . .6.
Using Pop-up Menus. . . ..... . . . . . . . . . . . . . . . . . 7
Working Directly with Objects. . . . ....... . . . . . . . . 8
Moving Objects . . . . . . . . . . . . . . . . . . . . . . . . . . .9.
Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Printing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Deleting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Arranging Objects . . . . . . . . . . . . . . . . . . . . . . . .13.
Opening Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Selecting Window Parts ....... . . . . . . . . . . . . . . . 15
Using the Window.List . . . ..... . . . . . . . . . . . . . . 16
Sizing a Window ..... . . . . . . . . . . . . . . . . . . . . . 17
Moving a Window . . . ..... . . . . . . . . . . . . . . . . . . 18
Introducing Online Information ......... . . . . . . . . . . 21
Using the Master Index ....... . . . . . . . . . . . . . . . 22
Searching for a.Topic. ..... . . . . . . . . . . . . . . . 23
Printing a Master Index Entry ......... . . . . . . . . 24
Using Related Information. . . . ....... . . . . . . . . 25
Using the Information Folder. . . . ....... . . . . . . . . 26
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Displaying Help for an Object.or Folder. ......... 28
Displaying Help for a Pop-up Menu Choice. . . . . . . . . 28
Displaying Help for a Highlighted Word.or Phrase . . . 28
Displaying Help for OS/2 Messages. . . . . ........ 29
Displaying Help for OS/2 Commands. . . . . ...... . 30
Chapter 2. Features . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Installation of OS/2.2.0. . ... . . . ... . . . . . . . . . . . . 33
+ Copyright IBM Corp. 1991 iii
Multitasking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
DOS Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Multiple Virtual DOS Machines . . . . . ......... . . . . 36
DOS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Dual Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Microsoft Windows Compatibility. . . . ....... . . . . . . . 37
Boot Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Special Needs Support. . . ..... . . . . . . . . . . . . . . . . 37
Lockup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
High Performance File System. . . . ....... . . . . . . . . 40
Extended Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 40
OS/2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Procedures Language/2.REXX . ..... . . . . . . . . . . . . . 41
System Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Games Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Productivity Programs . . . . . . . . . . . . . . . . . . . . . . . . 44
Appendix A. Keyboard and Mouse Use ......... . . . . . 47
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
ivIBM OS/2 32-bit Overview Pre-Release Copy
Notices
References in this publication to IBM products, programs, or
services do not imply that IBM intends to make these available in
all countries in which IBM operates. Any reference to an IBM
product, program or service is not intended to state or imply that
only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not
infringe any of IBM's intellectual property rights or other legally
protectible rights may be used instead of the IBM product,
program, or service. Evaluation and verification of operation in
conjunction with other products, programs, or services, except
those expressly designated by IBM, are the user's responsibility.
The following terms, denoted by a single asterisk (*) in this
publication, are trademarks of the IBM Corporation in the United
States and/or other countries:
AIX IBM Operating System/2
OS/2 Presentation SAA
Manager
Systems Application
Architecture
The following terms, denoted by a double asterisk (**) are
trademarks of other companies:
AST AST Corporation
Intel386 Intel Corporation
Intel486 Intel Corporation
Intel Intel Corporation
Lotus Lotus Corporation
Microsoft Microsoft Corporation
Windows Microsoft Corporation
+ Copyright IBM Corp. 1991 v
viIBM OS/2 32-bit Overview Pre-Release Copy
About This Book
This book introduces you to IBM * Operating System/2 * (OS/2 * )
Version 2.00. It describes the graphical appearance of the
operating system, the features of the operating system, and
explains how to use the online information. It also introduces you
to some important operating system concepts and describes the
differences between this version and previous versions of the
operating system.
This book describes how to complete most tasks and actions using
a mouse. If you are using a keyboard, see Appendix A,
﨣eyboard and Mouse Use?on page 47 for information on how to
most efficiently use the keyboard keys to perform tasks and
actions.
During installation, you are asked if you want to learn how to use
the mouse. If this is the first time you are using a mouse, choose
this option. After you install the operating system, you can learn
more about using a mouse in the OS/2 Tutorial.
Using This Book
Everyone who will be using OS/2 Version 2.00 should read this
book.
Keep this book as a reference.
Related Information
The following describes the documentation and online information
that comes with the product. Online describes information that
can be displayed on your screen.
* Trademark of the IBM Corporation
+ Copyright IBM Corp. 1991 vii
Quick Start
This card provides a brief, limited set of instructions on
how to install the operating system and quickly become
productive. If you want to install the entire operating
system (rather than select only certain features), use
this card. If you want more detailed information about
installing the operating system, use the Installation
Guide.
OS/2 Installation Guide
This book describes how to prepare for and install the
operating system. It also provides information about
installing more than one operating system on your
computer.
OS/2 Tutorial
This online, interactive program shows you the basics
of the operating system. The tutorial starts
automatically after you install the operating system.
Master Index
This online, alphabetic list contains most of the
information you need to use OS/2 2.0.
Glossary This online, alphabetic list contains computer and
operating system terms and definitions.
OS/2 Command Reference
This online information describes how to use OS/2
commands.
REXX Information
This online information describes how to use the REXX
procedure language.
viii IBM OS/2 32-bit Overview Pre-Release Copy
The following publications will be available and can be ordered
separately:
IBM Operating System/2 Keyboards and Code Pages
This book contains reference information for those who
use code-page switching to provide support for files that
are received from or sent to other countries.
OS/2 Version 2.00 Volume 1: Control Program, GG24-3730
This book provides detailed information about the
Control Program component of the OS/2 Version 2.00
operating system. The book describes memory and
task management, debugging support, and enhanced
application programming interfaces.
It also describes installation and national language
considerations, and discusses enhanced hardware
support.
OS/2 Version 2.00 Volume 2: DOS and Windows Environment,
GG24-3731
This book provides detailed information about the
Multiple DOS Machines feature, and support for
Microsoft ** Windows ** programs. The book describes
the architecture of Multiple Virtual DOS Machines, 8086
emulation, device drivers, extended memory support,
DOS settings, and using specific versions of DOS.
It also provides technical information about using
Microsoft Windows programs, and DOS Protect Mode
Interface (DPMI).
OS/2 Version 2.00 Volume 3: Presentation Manager, GG24-3732
This book provides detailed information about the
*
Presentation Manager component of OS/2 Version 2.00.
The book introduces the Presentation Manager, and
describes the enhanced graphical appearance of the
operating system, and enhanced help facilities.
** Trademark of the Microsoft Corporation
* Trademark of the IBM Corporation
About This Book ix
It discusses programming considerations for 32-bit or a
mix of both 16- and 32-bit code application
development, and when migrating existing 16-bit
applications. It also describes support for national
languages and double-byte character sets.
Changes from Previous Versions
The operating system has a changed look and many new features.
The Desktop Manager, File Manager, Print Manager, and Control
Panel are replaced by folders and objects. The Task List is now
called the Window List.
Although the appearance of the operating system is changed, you
can still use your existing programs with this version. To save
your existing programs in a folder called OS/2 Programs, be sure
you do not format your hard disk before or during installation of
OS/2 Version 2.00.
The following describes the new features in OS/2 Version 2.00.
Enhanced DOS compatibility
The Multiple Virtual DOS Machines feature removes the
restriction of running only one DOS program at a time
in DOS mode.
The DOS Settings feature helps optimize performance
of DOS programs.
Previous versions of the operating system did not
support DOS timing-dependent programs, such as
communications and real-time programs. Many of
these programs now run in OS/2 Version 2.00.
Microsoft Windows Compatibility
Microsoft Windows programs now run in OS/2 Version
2.00.
Boot Manager
The Boot Manager feature provides support for
installation of multiple operating systems.
xIBM OS/2 32-bit Overview Pre-Release Copy
Special Needs Support
The Special Needs feature provides support for
changing the way the keyboard keys work.
Security Support
The Lockup feature provides protection for information
in your computer.
Additional Programs
Games and Productivity programs have been added.
Use these programs to, for example, edit files, chart
graphs, create to-do lists, or play games.
About This Book xi
xiiIBM OS/2 32-bit Overview Pre-Release Copy
Chapter 1. Introducing OS/2 2.0
Welcome to OS/2 2.0.
The OS/2 operating system transforms your computer into a
powerful tool that helps you manage your work. It takes full
advantage of Intel386 ** and Intel486 ** technology. Increased
performance made possible by this technology means 32-bit and
16-bit programs run faster.
OS/2 2.0 supports multitasking (running more than one program at
once), installation of other operating systems, and compatibility
with existing programs that run under DOS and Microsoft **
**
Windows . You can organize programs, communicate with other
computers, write and print letters, and play games.
A lockup feature helps protect important information. A special
needs feature is available, if you need to change the way keyboard
keys work because of manual dexterity preferences.
The OS/2 operating system features a graphical appearance.
Whether you are writing a letter, using a printer, or playing a
game, you work with objects that graphically represent the letter,
printer, or game.
The OS/2 operating system is your lectronic workplace.?
OS/2 2.0 also features online information. Whether you need help,
want to learn about the operating system, need a term defined, or
want to explore topics related to concepts, commands, or REXX,
the information is online.
The online information is your lectronic library.?
This chapter describes folders and objects, explains how to use
the online information, and introduces some operating system
** Intel386 and Intel486 are trademarks of the Intel Corporation, and Microsoft and
Windows are trademarks of the Microsoft Corporation.
+ Copyright IBM Corp. 1991 1
concepts. Chapter 2, 﨔eatures?on page 33 describes other
operating system features.
Introducing Folders and Objects
The OS/2 operating system is like your real workplace, except the
things you work with are arranged on your computer screen, not
on your desk or in your office. For example, in your real
workplace, you might work with a letter, an appointment book, or a
printer. With the OS/2 operating system, you work with an object
that represents the letter, appointment book, or printer.
An object that contains other objects is a folder. You can use
folders to organize objects. For example, in your real workplace,
you probably organize the things you frequently use to do your
work in a convenient place. With the OS/2 operating system, you
can organize the objects you frequently work with in a folder.
Conceptual art
2IBM OS/2 32-bit Overview Pre-Release Copy
Folders and objects appear on your screen as miniature pictures
that look similar to real things in your workplace. For example, if
you install a printer, your printer object appears as a miniature
picture of a printer. A miniature picture that represents a folder or
an object is an icon.
When you finish installing OS/2, the OS/2 Tutorial and the icons
that represent the folders and objects that come with OS/2 appear
on the screen, like this:
Screen Capture of shell
Note: The tutorial appears automatically only the first time you
use the operating system.
The tutorial has information about using a mouse and presents
some operating system concepts. You also get a chance to
practice using many of the features. When you complete the
tutorial, you can start using the folders and objects that come with
OS/2 2.0.
There is one folder that comes with the OS/2 operating system that
is unique, called the Desktop folder. It fills the entire screen, and
contains all other folders and objects.
Chapter 1. Introducing OS/2 2.0 3
The following list describes the contents of the other folders or
objects.
OS/2 System
This folder contains other folders and objects that:
? Show drive locations
? Contain startup instructions
? Help you customize the system
?
Contain games and productivity programs
? Are used to select OS/2 or DOS command prompts.
Master Index
This object contains an alphabetic list of online topics
related to understanding and using the operating
system.
For example, use the Master Index to find information
about how to install programs or copy, move, print, and
arrange objects.
Information
This folder contains objects that represent the:
? Tutorial, which has information about using a
mouse and how to use the operating system
? Glossary, which lists terms and their definitions
? OS/2 Command Reference, which describes
commands and their usage
? REXX Information, which describes using the REXX
procedures language.
Shredder This object is used to delete objects.
Templates
This folder contains templates (blank forms) for objects.
Use the templates to create OS/2 or DOS full-screen or
window sessions, or data, program, device, or
installation objects.
4IBM OS/2 32-bit Overview Pre-Release Copy
During installation, you will make choices about the hardware and
software you are using. Depending on the choices you make, the
following folders or objects appear in the Desktop folder.
Network This folder contains other folders and objects that
represent a Local Area Network (LAN).
Printer This object represents a printer.
DOS Programs
This folder contains programs previously installed using
DOS.
Microsoft Windows Programs
This folder contains programs previously installed using
Microsoft Windows.
OS/2 Programs
This folder contains programs previously installed using
earlier versions of the OS/2 operating system.
Note: If you format the hard disk before or during installation, any
programs previously installed using DOS, Microsoft
Windows, or an earlier version of the OS/2 operating
system are not saved in a folder.
Managing Objects
You can manage objects in a way that is similar to the way you
already manage your work. For example, during your work day,
you might select letters or file folders you need to work with,
arrange your work in order of importance, or copy letters at a
copier.
With objects, you can do the same kinds of tasks. You can select,
arrange, or copy objects. In addition, you can open, move,
discard, or print objects.
Chapter 1. Introducing OS/2 2.0 5
Selecting Objects
You must select (choose) an object before you can perform an
action on it. This is similar to selecting what letters you will write
or what files you will work with that day. For example, if you want
to print or copy an object, you first select it. Then, you select the
appropriate action on the pop-up menu (print or copy) that you
want to apply to the selected object.
To select an object:
1. Move the mouse pointer to the object.
2. Press the left mouse button (mouse button 1) once.
(When you select an object, a shaded box appears around the
object.)
Screen Capture - Selected object
Once you select an object, there are two ways to perform an
action on the object:
? Select the action from a pop-up menu. (A pop-up menu lists
actions that can be applied to the object).
? Perform the action directly on the object.
6IBM OS/2 32-bit Overview Pre-Release Copy
Using Pop-up Menus
To display the pop-up menu for the selected object, move the
mouse pointer to the object; then press the right mouse button
(mouse button 2) once.
Once the pop-up menu appears, you can select a choice from it. A
typical pop-up menu for an object might look like this:
Screen Capture - Typical menu for object
To select a choice:
1. Move the mouse pointer to the choice.
2. Press the left mouse button (mouse button 1) once.
Sometimes one or more choices on the menu have additional
choices available. If additional choices are available, an arrow
appears to the right of the pop-up menu choice.
To display the additional choices:
1. Move the mouse pointer to the arrow.
2. Press the left mouse button (mouse button 1) once.
Chapter 1. Introducing OS/2 2.0 7
Working Directly with Objects
You have already read about how to select an object, and then
how to apply an action to that object by selecting a choice on a
pop-up menu. You can also directly manage objects. Generally,
this means that without using a pop-up menu you can perform
most actions directly on an object.
The following list shows some of the terms associated with
performing an action directly on an object.
Click Press the left mouse button (mouse button 1) once.
Double-click
Press the left mouse button (mouse button 1) twice.
Drag Move the mouse pointer to the object. Then, press and
hold down a mouse button (either 1 or 2, depending on
the action being performed) while moving the mouse
pointer across the screen.
As you move the mouse pointer, the object moves
along with it.
In addition to these actions, some actions must be done using both
the keyboard and the mouse. When performing these actions, the
key you press and hold down changes the way the basic mouse
operation works. For example, when you copy an object, you
press and hold down the Ctrl key and drag the object. Holding
down the Ctrl key tells the operating system to copy the object, not
move it.
8IBM OS/2 32-bit Overview Pre-Release Copy
Moving Objects
You can move an object to another object. The object you move
no longer appears in the previous location. This is similar to
moving a letter from one file folder to another or moving a letter
from your desk to a file cabinet.
Conceptual Art
To move an object, you do the following:
1. Move the mouse pointer to the object.
2. Press and hold down mouse button 2 while dragging the object
to another object.
3. When the object is over the object you want to move it to,
release mouse button 2.
Chapter 1. Introducing OS/2 2.0 9
Copying Objects
You can copy an object to another object. A duplicate of the
object is created and placed in the other object. This is similar to
making a copy of a letter on a copier and then placing the original
in one file folder and the copy in another.
Conceptual Art
To copy an object, you must use both the keyboard and the
mouse, as follows:
1. Move the mouse pointer to the object.
2. Press and hold down mouse button 2.
3. Press and hold down the Ctrl key.
4. Drag the object to the object where you want a copy.
5. When the object is over the object you want a copy to appear
in, release mouse button 2.
6. Release the Ctrl key.
10IBM OS/2 32-bit Overview Pre-Release Copy
Printing Objects
If you are using a printer or plotter, you can print objects.
Conceptual Art
To print an object, you do the following:
1. Move the mouse pointer to the object.
2. Press and hold down mouse button 2 while dragging the object
to the Printer.
3. When the object is over the Printer, release mouse button 2.
Chapter 1. Introducing OS/2 2.0 11
Deleting Objects
You can delete or permanently remove an object that you are sure
you no longer need. This is similar to shredding papers in a
shredder.
Conceptual Art
To delete an object, you do the following:
1. Move the mouse pointer to the object.
2. Press and hold down mouse button 2 while dragging the object
to the Shredder.
3. When the object is over the Shredder, release mouse button 2.
Once an object is deleted, it cannot be recovered.
12IBM OS/2 32-bit Overview Pre-Release Copy
Arranging Objects
You can arrange objects on the screen according to your
preference and work needs. This is similar to arranging or placing
the things on your desk that you will need to work with that day.
For example, if you work with certain objects every day, you might
want to place them in a row at the bottom of your screen.
Conceptual Art
To arrange objects, you do the following:
1. Move the mouse pointer to one of the objects you want to
arrange.
2. Press and hold down mouse button 2.
3. Drag the object in the direction you want to move the object.
4. When the object is in the new location, release mouse button
2.
Repeat these actions until you are satisfied with the arrangement.
Chapter 1. Introducing OS/2 2.0 13
Opening Objects
You can open an object to look at the contents of the object. This
is similar to opening a file folder to look at the letters that are
inside. For example, if you file a letter (object) in a folder and
want to display the contents of the letter, first open the folder.
Then, open the letter to look at its contents.
To open an object, move the mouse pointer to the object, then
press mouse button 1 twice (double-click).
When you open an object, the contents appear in a separate area
on the screen called a window. Each object opened appears in its
own window. For example, if you install a database program and
a text editor program, and open both programs, they appear in two
separate windows, like this:
Screen Capture - Two windows/titles
While many programs can be opened and displayed in windows,
you can work directly with only one. The program you choose to
work with is the interactive program.
14IBM OS/2 32-bit Overview Pre-Release Copy
Selecting Window Parts
The following describes some of the parts of a window and how to
use them. For more detailed information about the parts of a
window, review the OS/2 Tutorial.
Screen Capture of Window
?? Border . This part of the window is the boundary. When the
border is highlighted, the window is interactive (contains the
interactive program) and is usually the topmost window when two
or more windows are displayed. Use the border to size the
window. For more information about sizing a window, see izing
a Window?on page 17.
?? .Close button Use this button to close the window. Move the
mouse pointer to the button and double-click on it.
?? .Title bar This part of the window shows the title of the
window. Use the title bar to move the window. For more
information about moving a window, see 﨧oving a Window?on
page 18.
?? .Minimize button Use this button to make the window the
smallest possible size. (Generally, when minimized, the window is
invisible). Move the mouse pointer to the button and double-click
on it. The contents of the window are not affected when you
minimize it.
?? .Maximize button Use this button to make the window the
largest possible size. (Generally, when maximized, the window
fills the entire screen). Move the mouse pointer to the button and
double-click on it. The contents of the window are not affected
when you maximize it.
?? .Scroll bar Use the scroll bar to show more information in the
window. Move the mouse pointer to the up, down, right, or left
arrow; then press and hold down mouse button 1. When you press
and hold down mouse button 1, the information in the window
scrolls up, down, right, or left. Release the mouse button when
you are done scrolling through the information in the window.
Chapter 1. Introducing OS/2 2.0 15
Using the Window List
The Window List shows a list of the objects and programs you are
using. This includes objects or programs that you minimized
(made invisible).
To display the Window List, move the mouse pointer to any area of
the Desktop folder that is blank, (not on a window or any part of a
window, an object, or another folder); then press mouse button 2
once. The Window List looks like this:
Screen Capture - Window List
Use the Window List to quickly switch to an object or a program
shown in the list, by double-clicking on the name of the object or
program.
16IBM OS/2 32-bit Overview Pre-Release Copy
Sizing a Window
You can make a window larger or smaller. Changing the size of a
window does not affect the contents of the window.
Conceptual Art
To size a window, you do the following:
1. Move the mouse pointer to the border of the window. (The
mouse pointer changes shape to a double arrow when it is in
position correctly on the border.)
2. Press and hold down mouse button 2.
3. Drag the border in the direction that you want.
4. When you are satisfied with the new size, release mouse
button 2.
Chapter 1. Introducing OS/2 2.0 17
Moving a Window
You can move a window to any location on the screen. For
example, if two windows are open at the same time, you might
want to place one window in the upper-left corner and the other in
the lower-right corner of the screen. You can move the windows
to those positions.
Conceptual Art
To move a window, you do the following:
1. Move the mouse pointer to the title bar of the window.
2. Press and hold down mouse button 2.
3. Drag the window in the direction you want to move it.
4. When the window is in the new location, release mouse button
2.
Repeat these actions until you are satisfied with the new
arrangement.
When you move a window (using the method described below) the
contents and size of the window are not affected.
18IBM OS/2 32-bit Overview Pre-Release Copy
In addition to arranging windows by moving each one individually,
you can arrange automatically all the windows you have open.
1. Display the pop-up menu for the Window List. To do this,
move the mouse pointer to an area (within the Window List
window) that is blank. Then, press the right mouse button
(mouse button 2) once.
2. Move the mouse pointer to the Window choice.
3. Move the mouse pointer to the right arrow; then press mouse
button 1 once.
4. Select the Cascade or Tile choice.
If you cascade or tile windows, the contents of the windows are not
affected. However, the contents may not be completely visible, but
you will always be able to see the title bars. In addition, the size
of the windows might change, and the windows might appear to
overlap.
The cascade arrangement places the window that contains the
interactive program on top (closest to you). Other open windows
are put behind this window.
The cascade arrangement looks like this.
Screen Capture - Cascade
Chapter 1. Introducing OS/2 2.0 19
The tile arrangement places the window that contains the
interactive program in the upper-left corner of your screen. Other
open windows are put next to this window and to each other, until
the screen is completely full.
The tile arrangement looks like this.
Screen Capture - Tile
20IBM OS/2 32-bit Overview Pre-Release Copy
Introducing Online Information
Most of the information for the operating system is online. The
information you need can be displayed on your screen while you
are doing your work. The online information is your lectronic
library.?
Conceptual Art
Chapter 1. Introducing OS/2 2.0 21
Using the Master Index
The Master Index is an alphabetic list of topics related to
understanding and using the OS/2 operating system. The list
contains the following kinds of topics:
? Things to consider before performing a task
?
The steps you need to take to complete a task
? Operating system concepts
? DOS error messages.
After you install the OS/2 operating system and review the OS/2
Tutorial, open the Master Index by double-clicking on the Master
Index folder.
When the Master Index is open, it looks like this:
+-------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-------------+
The list of topics appears in an area within the window that looks
like a notebook with tabs. Each tab has a letter of the alphabet on
it that corresponds to the group of topics that start with that letter.
Use the letters on the tabs to move through the index. For
example, if you need information about the topic opying an
object,?you do the following:
1. Move the mouse pointer to the tab that has the letter C on it.
2. Press mouse button 1 once to select the first topic that starts
with the letter C.
3. Move the mouse pointer to the down arrow on the scroll bar.
22IBM OS/2 32-bit Overview Pre-Release Copy
4. Press mouse button 1 to scroll through the topics that start
with the letter C, until you locate the entry for copying an
object.
5. Double-click on the entry (copying an object).
The information for the entry (copying an object) appears in a
window to the right of the Master Index window, like this:
Screen Capture - MI w/entry open
If you leave the Master Index open while you work with the OS/2
operating system, it is always available for you to use. You can
move the Master Index window to any location on the screen (just
like other windows).
Searching for a Topic
The Master Index has a search action. You can search for an
entry using one or more words that describe the topic. For
example, to search for information about how to duplicate an
object, you might search using the word uplicate,?uplicates,?
or even uplicating.?The result of a search (using duplicate,
duplicates, or duplicating), is opying an object.?
Chapter 1. Introducing OS/2 2.0 23
To search for a topic:
1. Display the Master Index pop-up menu. To do this, move the
mouse pointer to an area (within the Master Index window)
that is blank. Then, press the right mouse button (mouse
button 2) once.
2. Move the mouse pointer to the Search choice; then press
mouse button 1 once.
A window appears that looks like this:
Screen Capture - Search pop-up
3. Type the word or words that describe the topic.
4. Move the mouse pointer to the word Search (located in the
lower-left corner); then press mouse button 1 once.
5. When the list of topics appears, double-click on the entry.
Printing a Master Index Entry
Once you locate a topic, you might want to print that entry. (You
can only print one entry at a time).
To print an entry:
1. Move the mouse pointer to the entry you want to print; then
press mouse button 1 once.
24IBM OS/2 32-bit Overview Pre-Release Copy
2. Display the Master Index pop-up menu. To do this, move the
mouse pointer to an area (within the Master Index window)
that is blank. Then, press the right mouse button (mouse
button 2) once.
3. Move the mouse pointer to the Print choice; then press mouse
button 1 once.
Using Related Information
You have just read about using the Master Index, and searching
for and printing entries. As you use the Master Index, you will
often find that the entry you select has related topics, which you
may find useful. Related topics are listed under the heading
elated Information,?like this:
Screen Capture - MI w/entry w/hypertext
To select a related topic, move the mouse pointer to the entry;
then double-click on the entry.
For more information about using the Master Index, searching for
topics, printing an entry, or using related information, review the
OS/2 Tutorial.
Chapter 1. Introducing OS/2 2.0 25
Using the Information Folder
The Information folder contains the OS/2 Tutorial, Glossary, OS/2
Command Reference, and REXX Information. Use the contents of
the Information folder to learn more about the operating system, to
look for the definition of a term, to use OS/2 commands, or to use
REXX.
To open the Information folder, double-click on it. When the
Information folder is open, it looks like this:
Screen Capture - Info folder/open
The OS/2 Tutorial has information about how to use a mouse, work
with objects and folders, use windows, get help, and other general
information. (The first time you use the operating system, the
tutorial is opened automatically for you.)
The Glossary is an alphabetic list of terms and their definitions. If
you are not familiar with a term you read about in the online
information or online help, use the Glossary to find the definition
for the term.
The OS/2 Command Reference describes the purpose of each
command, and the syntax and parameters for each command. It
26IBM OS/2 32-bit Overview Pre-Release Copy
also has information about topics such as batch files, command
operators, redirection symbols, and substitution variables.
The REXX Information describes the commands you use to write
simple batch programs. It also has information about topics such
as procedures, elements, and comments.
To open the OS/2 Tutorial, or the Glossary, or the OS/2 Command
Reference, or the REXX Information, double-click on it.
Getting Help
Online help is always available. To get help, select the word
﨟elp?when it is displayed on your screen or press F1.
When you request help, the information appears in a help window,
like this:
Screen Capture - Help Window
You can also get help for OS/2 messages and commands.
The following describes some of the different ways you can get
help. For more detailed information, review the OS/2 Tutorial or
request help from within a help window.
Chapter 1. Introducing OS/2 2.0 27
Displaying Help for an Object or Folder
The help for an object or folder describes the object or contents of
the folder.
To display help for an object or folder:
1. Move the mouse pointer to the object or folder.
2. Press the right mouse button (mouse button 2) once. (The
pop-up menu for the object appears.)
3. Move the mouse pointer to the Help choice.
4. Press mouse button 1 once.
Displaying Help for a Pop-up Menu Choice
The help for a pop-up menu choice describes the action you can
apply to a selected object or folder.
To display help for a pop-up menu choice:
1. Move the mouse pointer to the pop-up menu choice.
2. Press and hold down mouse button 1. (Do not release mouse
button 1).
3. Press the F1 key.
4. When the help window appears, release mouse button 1.
Displaying Help for a Highlighted Word or Phrase
Sometimes a word or a phrase in a help window is highlighted.
The highlighting means that additional help information is
available. The additional help information might be a definition, or
related information, or help for a field.
28IBM OS/2 32-bit Overview Pre-Release Copy
The following shows a help window with highlighted phrases. (In
this example, the highlighted phrases show that additional help
information is available for fields.)
Screen Capture - Help Window w/highlighted phrases
To display the additional help:
1. Move the mouse pointer to the highlighted word or phrase.
2. Press mouse button 1 twice. (The additional help information
appears in another help window. The original help window is
directly underneath the new help window and is not visible.
However, the original help window is still open.)
3. When you finish reviewing the additional help information,
press Esc to return to the original help window.
Displaying Help for OS/2 Messages
The help for OS/2 messages describes how to correct an error or
respond to a warning, or provides general information. The way
you request help for a message depends on how the message is
displayed.
If the message appears in a message window with the word
﨟elp?in it, then do the following:
1. Move the mouse pointer to the word 﨟elp.?
Chapter 1. Introducing OS/2 2.0 29
2. Press mouse button 1 once.
If the message appears full-screen, and is enclosed in a box, then
do the following:
1. Move the mouse pointer to the phrase 﨑isplay Help.?
2. Press mouse button 1 once.
If the message appears and it has a message number, preceded
by the letters SYS, then do the following:
1. At the OS/2 command prompt, type HELP followed by a space.
Type the message number. (It is not necessary to type the
letters SYS).
2. Press Enter.
For example, if you received this message:
SYS0002: The system cannot find the file specified.
To request help, you type:
HELP 2
Then, press Enter.
The following help appears:
SYS0002: The system cannot find the file specified.
EXPLANATION: The file named in the command does
not exist in the current directory or search path
specified. Or, the file name was entered incorrectly.
ACTION: Retry the command using the correct file name.
Displaying Help for OS/2 Commands
As described earlier, the OS/2 Command Reference contains the
purpose of and syntax for commands. There are two ways to get
help for a command: open the Command Reference or request
help from the OS/2 command prompt.
If you will be entering more than one command, you might find it
more convenient to open the Command Reference in one window,
while entering commands in another window.
30IBM OS/2 32-bit Overview Pre-Release Copy
If you just want to display help for a command and do not want to
open the Command Reference, then do the following:
1. At the OS/2 command prompt, type HELP followed by a space
and the name of the command, like this:
HELP COPY
2. Press Enter.
Chapter 1. Introducing OS/2 2.0 31
32IBM OS/2 32-bit Overview Pre-Release Copy
Chapter 2. Features
As described in Chapter 1, the operating system has a graphical
appearance and most of the information you need is online. In
addition to the features already described, the operating system
has other features. This chapter describes some of them.
Installation of OS/2 2.0
OS/2 2.0 features a graphical installation. For example, progress
bars show you what percentage of features on each installation
diskette is installed.
During installation, you will be asked if you want to learn how to
use the mouse. If this is the first time you are using a mouse,
choose this option to learn how to use the mouse.
For more information about installing OS/2 2.0, see the Quick Start
card or the Installation Guide.
Multitasking
Multitasking is a feature that makes it possible to work with more
than one program or task at a time. This feature is available as
soon as you finish installing the OS/2 operating system.
Think of each program or task you use as a session.
A session can be one of two types:
? Foreground Session
You work directly with this interactive session. It receives
input from your keyboard and mouse or displays information
on your screen.
? Background Session
You do not work directly with this session. However, programs
or tasks running in a background session can be processing
data.
+ Copyright IBM Corp. 1991 33
For example, if you have a large database, it may contain
thousands of records. Normally, updating a database this size
takes some time, and with other operating systems your
computer cannot be used while the data is updating.
Multitasking removes that barrier. You can instruct the
database program to start processing data, and then you can
place it in the background session. While the database
program is running in the background session, you can be
working with another program in the foreground session.
A program or a task in a background session will stop running
only when it needs further instructions from you. At that time
you can end the session or bring it to the foreground.
For more information about multitasking, see the Master Index.
34IBM OS/2 32-bit Overview Pre-Release Copy
DOS Compatibility
DOS programs take full advantage of most of the features of the
OS/2 operating system. For example, DOS programs use the
multitasking feature, and run either full-screen or in windows. You
can size, arrange, or move DOS programs running in windows,
exactly like OS/2 programs running in windows.
Conceptual Art
Chapter 2. Features 35
There are also features in this version of the OS/2 operating
system that enable DOS programs to run as well as programs
written specifically for the OS/2 operating system. These features
are described below.
Multiple Virtual DOS Machines
This feature makes it possible to run up to 16 DOS programs at the
same time. Each DOS program can run in a foreground or
background session. Up to 630KB (KB equals 1024 bytes) of
memory are available for each program. DOS programs that use
the Lotus****/ Intel /Microsoft ** (LIM) Expanded Memory Specification
(EMS) and the Lotus/Intel/Microsoft/AST ** (LIMA) Extended Memory
Support (XMS) can also be run.
For more information about using Multiple Virtual DOS Machines,
see the Master Index.
DOS Settings
DOS Settings can be used to tailor the way a DOS program runs.
For example, you can prevent sounds normally heard when a
program is running or you can specify the amount of memory (up
to 630KB) that each DOS program uses.
For more information about using DOS Settings, see the Master
Index and the OS/2 Command Reference.
Dual Boot
The Dual Boot feature provides support for installing DOS Version
3.2 or later and OS/2 2.0 on the same hard disk. With the dual
boot feature, you can switch back and forth between the DOS and
OS/2 operating systems. This feature is useful if you are using
DOS programs that run only under DOS.
For more information about installing the dual boot feature, see the
Installation Guide.
** Lotus is a trademark of the Lotus Corporation, Intel is a trademark of the Intel
Corporation, Microsoft is a trademark of the Microsoft Corporation, and AST is a
trademark of the AST Corporation.
36IBM OS/2 32-bit Overview Pre-Release Copy
Microsoft Windows Compatibility
Text is under development.
Boot Manager
The Boot Manager feature makes it possible for OS/2 Version 2.00
to coexist with other operating systems (for example, DOS,
*
previous versions of the OS/2 operating system, and AIX ). If you
install this feature, you choose which operating system you want to
be active each time you start your computer.
For more information about installing and using the Boot Manager,
see the Installation Guide.
Special Needs Support
The Special Needs feature provides support for changing the way
the keyboard keys work. This support is useful, for example, for
individuals whose manual dexterity is impaired.
The Special Needs feature is used to change:
? The amount of time a key can be held down before it is
considered to have been pressed
? The amount of time a key can be held down before it begins
repeating its function
? The rate at which a key will repeat its function when it is held
down
? The way a series of keys is pressed and released.
For example, to restart the computer, you press the
Ctrl+Alt+Del keys at the same time. You can change the
way this series of keys works (without changing the result they
produce) by using the sticky keys function.
The sticky keys function sets the keys (in this example,
Ctrl+Alt+Del) to behave as if they were pressed at the same
* Trademark of the IBM Corporation.
Chapter 2. Features 37
time without actually having to press them at the same time.
You can press the keys one at a time to produce the same
result as pressing them together.
For more information about the Special Needs feature, see the
Master Index.
38IBM OS/2 32-bit Overview Pre-Release Copy
Lockup
The Lockup feature provides protection for the information in your
computer. When Lockup is used, the mouse and keyboard are
locked.
When you use Lockup, a password (known only by you) is set.
Each time you want to unlock your system, you must type this
password to gain access to the system.
For more information about using Lockup, see the Master Index.
Conceptual Art
Chapter 2. Features 39
High Performance File System
The High Performance File System feature provides fast access to
information on your computer's hard disk. The High Performance
File System is an installable file system like the DOS file system
FAT (File Allocation Table). An installable file system manages the
information stored on diskettes or the hard disk of your computer.
The High Performance File System is faster than FAT because of
the method that it uses to find information on the hard disk.
The High Performance File System provides support for long file
names (up to 254 characters). File names can contain blank
spaces, if the part of the file name that contains the blank space is
enclosed by quotation marks ().
The High Performance File System saves file names exactly as
typed. For example, if you create a file and name it AbC, it is
saved as AbC, not ABC. However, when you search for the file, it
is found whether you type ABC, AbC, or abc.
For more information about installing the High Performance File
System, see the Installation Guide. For more information about
using the High Performance File System, see the Master Index.
Extended Attributes
Attributes are characteristics that describe a file to the operating
system. For example, a file attribute might be the time or date the
file was created.
Extended attributes are additional attributes that describe the file.
For example, an extended attribute might be the name of the
person who created the file. If you use extended attributes to
describe a file, you can search for the file using the extended
attribute. For example, if the name of the person who created the
file is 﨡oe,?you can search for the file using the name Joe as one
of your search parameters.
For more information about using extended attributes, see the
Master Index.
40IBM OS/2 32-bit Overview Pre-Release Copy
OS/2 Commands
Commands are words that you type that tell the OS/2 operating
system to perform an action. Enter OS/2 commands from either
the OS/2 full-screen or window command prompt.
There are a number of OS/2 commands that you can use. Some
examples of these are: COPY (to copy files), DATE (to display or
change the date), and DISKCOPY (to copy diskettes).
For more information about using commands, see the OS/2
Command Reference.
Procedures Language/2 REXX
Procedures Language/2 REXX is a generalized command
language. This small, powerful language is the Systems
Application Architecture * (SAA * ) procedures language for the OS/2
operating system.
REXX is useful for writing batch programs, as well as other
programs. It uses common English words and single number
concepts.
For more information about using REXX, see the REXX Information.
System Editor
The System Editor is a simple text editor. You can create, edit, or
view files using the System Editor. Use the editor for simple
editing tasks, for example, editing small batch programs. If you
are doing extensive text editing or word processing, install an
editor designed for those purposes.
The System Editor supports both the mouse and keyboard, and has
extensive online help. It also supports several different font styles,
* Trademark of the IBM Corporation
Chapter 2. Features 41
font sizes, and type styles. You can set the font to the same style
your printer uses and see how the file looks before you print it.
For more information about using the System Editor, see the
Master Index.
42IBM OS/2 32-bit Overview Pre-Release Copy
Games Programs
Use the Games programs for entertainment or educational
purposes. For example, if you want to use a strategy game, try
Reversi. The object of the game is to fill more squares (with red
circles) than your opponent the computer does (with blue circles)
Conceptual Art
For more information about using the games programs, see the
Master Index.
Chapter 2. Features 43
Productivity Programs
Productivity programs are simple programs that can help you with
most operating system and business tasks. For example, use
Presentation Manager * (PM) Chart to make graphs, or Calculator to
add, subtract, multiply, and divide numbers.
Conceptual Art
For more information about using the productivity programs, see
the Master Index.
* Trademark of the IBM Corporation.
44IBM OS/2 32-bit Overview Pre-Release Copy
Chapter 2. Features 45
46IBM OS/2 32-bit Overview Pre-Release Copy
Appendix A. Keyboard and Mouse Use
The following lists some of the most common tasks you can do,
using either the keyboard keys or a mouse.
For a detailed list of keys assignments, do one of the following:
? See the Master Index
? From a pop-up menu, select Help; then select Keys Help
? From within a help window, select Help; then select Keys Help.
The plus sign (+) between key names means to press and hold
down the keys in the order shown and release them together.
System Tasks
Task Keys Mouse
Get Help. F1 Click on the word 﨟elp?
Restart the system. Ctrl + Alt + Del
Switch to next window. Alt + Tab Click on window
Switch to next window or Alt + Esc Click on window or icon
full-screen session.
Display Window List. Ctrl + Esc Move mouse pointer to
blank part of desktop; then
press mouse button 2 once
Folder and Object Tasks
Task Keys Mouse
Move among folders or ? , ? , ? , or ? Click on the folder or
objects. object
Display a pop-up menu. Shift + F2 Press both mouse buttons
at the same time
Select first choice in Home Click on choice
pop-up menu.
Select last choice in End Click on choice
pop-up menu.
Select a choice using the Type the underlined letter
underlined letter.
Open selected folder or Enter Double-click on folder or
object. object
+ Copyright IBM Corp. 1991 47
Task Keys Mouse
Delete selected objects. Del Drag to Shredder
Print selected objects. Shift + Print Screen(PrtSc) Drag to Printer
Select a folder or object. Spacebar Click on folder or object
Select more than one Shift + F8 (to begin Add Hold down Ctrl key while
folder or object. mode), use arrow keys to clicking on each one
move among folders and
objects and press
Spacebar to make each
selection. Press ShiftF8 +
again (to end Add mode)
Select a range of folders Shift + F8 (to begin Add Click on first object in
or objects from cursor's mode), use arrow key to range; then press and hold
current position to move to first file in the down Shift. Click on last
cursor's new position. range and press Spacebar object in range.
to select. Press and hold
down CtrlShift while +
moving to last file in the
range. Release CtrlShift. +
Press ShiftF8 again (to +
end Add mode).
Move folder or object. F7 Drag to another folder or
object
Copy folder or object. F8 Hold down Ctrl key while
dragging to folder or
object where you want a
copy to appear.
Window Tasks
Task Keys Mouse
Move window. AltF7 Move mouse +
pointer to title
bar; then press
and hold mouse
button 2 while
dragging to new
location
Size window. AltF8 Move mouse +
pointer to
border; then
press and hold
mouse button 2
while dragging
border in any
direction
Minimize window. Alt on + F9 Click
Minimize button
48IBM OS/2 32-bit Overview Pre-Release Copy
Task Keys Mouse
Maximize window. Alt on + F10 Click Maximize
button
Close window. AltF4 Double-click on +
Close button
Scroll contents of window up one page. Page Up < PgUp *
Scroll contents of window down one page. Page Down
PgDn < *
Scroll contents of window left one page. Ctrl + Page Up
PgUp < *
Scroll contents of window right one page. Ctrl + Page
Down PgDn < *
Help Window Tasks
These tasks only work from within a help window.
Task Keys Mouse
Switch between Help and program. Alt + F6 Click on
program
Display General Help. F2 Click on
General Help
Display Keys Help. F9 Click on Keys
Help
Display Help Index. F11 Click on Help
Index
Display Using Help. Shift + F10 Click on Using
Help
Display Tutorial. Shift on + F2 Click
Tutorial
Display help for highlighted word or phrase. Use Tab key to Move mouse
move cursor totopointer
highlighted highlighted
word or phrase; word or phrase;
then press Enter then
double-click
Display previous help window. Esc Click on
Previous
Appendix A. Keyboard and Mouse Use 49
Master Index Tasks
Task Keys Mouse
Open Master Index. Select; then Double-click on
press Enter Master Index
icon.
Move through topics one line at a time. Click on topic
Move up through topics one page at a time. Page Up (PgUp)
Move down through topics one page at a time. Page Down
(PgDn)
Move to topic areas. Type letter of Click on letter
the alphabet of the alphabet
Display related information. Use the Tab key Move mouse
to move cursortopointer
to related related
information; information;
then press Enter then
double-click
Remove related information help window. Esc Click on
previous
Change focus. Click on Master
Index listing or
topic
50IBM OS/2 32-bit Overview Pre-Release Copy
Index
Index
closing a window 15
A Command Reference
arranging objects 13 description of viii
arranging windows 18 displaying 27
attributes, definition of 40
commands, using 41
compatability
DOS 35
B Microsoft Windows 37
background session 33 copying objects 10
Boot Manager 37
border, definition of 15
button D
Close 15 deleting an object 12
Maximize 15 Desktop folder, defintion of 3
Minimize 15 discarding objects 12
displaying
C Command Reference 27
Glossary 27
cascade arrangement 19 help for folders 28
Changes from previous versions help for highlighted phrases 28
Boot Manager x
Control Panel x help for highlighted words 28
Desktop Manager x help for messages 29
help for objects 28
DOS compatibility x help for OS/2 commands 30
DOS Settings x help for pop-up menu
File Manager x
games xi choices 28
Lockup xi Information folder 26
Master Index 22
Microsoft Windows objects 14
compatibility x OS/2 Tutorial 27
Multiple Virtual DOS
Machines x pop-up menu 7
Print Manager x related information 25
REXX Information 27
Productivity programs xi DOS compatibility 35
special needs x DOS Programs
Task List x
changing the location of an compatibility 35
object 9 DOS Settings 36
Dual Boot 36
click, definition of 8 Multiple Virtual DOS
Machines 36
+ Copyright IBM Corp. 1991 51
Index
DOS Programs (continued) features of OS/2 33
running more than one 36 file systems, definition of 40
DOS Programs folder, description folders
of 5 DOS Programs 5
DOS Settings 36 help for 28
double-click, definition of 8 Information 4
dragging a window 18 introducing 2
drag, definition of 8 Microsoft Windows Programs 5
Dual Boot 36 Network 5
duplicating an object 10 OS/2 Programs 5
OS/2 System 4
Templates 4
E folder, definition of 2
editor, system 41 foreground session 33
erasing an object 12
extended attributes 40
G
Games
F getting help 27
features Glossary, displaying 27
Boot Manager 37
DOS compatiblity 35
DOS Settings 36 H
Dual Boot 36 Help
extended attributes 40 for a folder 28
Games programs 43 for a highlighted phrase 28
High Performance File for a highlighted word 28
System 40 for a pop-up menu choice 28
installation 33 for an object 28
learning to use a mouse 33 for messages 29
Lockup 39 for OS/2 commands 30
Microsoft Windowshelp window, description of 27
compatibility 37High Performance File System 40
Multiple Virtual DOS highlighted phrase, help for 28
Machines 36 highlighting, defintion of 28
multitasking 33
OS/2 Commands 41
I
Procedures Language/2
REXX 41 icons, introducing 2
Productivity programs 44 icon, definition of 3
special needs support 37 index, online 22
System Editor 41 Information folder
description of 4
52IBM OS/2 32-bit Overview Pre-Release Copy
Index
Information folder (continued) mouse
displaying 26 introducing vii
Installation Guide use of 6, 8
description of viii moving objects 9
installation of OS/2 33 Multiple Virtual DOS Machines 36
installing, more than one operating multitasking
system 37 definition of 1
interactive program, definition description of 33
of 14
interactive window, definition
N
of 15
Network folder, description of 5
K
keyboard and mouse use 47 O
objects
arranging 13
L copying 10
locking your system 39 discarding 12
Lockup 39 displaying 14
look at the contents of an displaying a pop-up menu 7
object 14 help for 28
introducing 2
managing 5
M Master Index 4
Master Index moving 9
description of 22 opening 14
displaying 22
Printer 5
printing an entry 24 printing 11
searching for a topic 23 Shredder 4
topics 22 working with 8
using 22 object, definition of 2
using related information 25
online information
Master Index object, description27getting help
of 4 Glossary 26
maximizing a window 15 Information folder 26
messages, help for 29 introducing 1, 21
Microsoft Windows
Master Index 21
compatiblity 37 OS/2 Command Reference 26
Microsoft Windows Program folder,26OS/2 Tutorial
description of 5 REXX Information 27
minimizing a window 15 searching for a topic 23
using 21
Index 53
Index
open an object 14 R
opening the Master Index 22
OS/2 commands 41 rearranging objects 13
displaying help for 30 related information, displaying 25
using 41 REXX Information
description of viii
OS/2 operating system displaying 27
changes from previous
versions x REXX, description of 41
description of 1 running multiple DOS
features 33 programs 36
running more than one
program 33 S
OS/2 Programs folder, description
of 5 scroll bar 15
OS/2 System folder, description searching for a topic 23
securing your system 39
of 4 select, definition of 6
OS/2 Tutorial sessions
description of viii
displaying 27 background 33
foreground 33
mulitple DOS 36
Shredder object, description of 4
P shredding an object 12
pop-up menu
definition of 6 sizing a window 17
displaying 7 special needs support 37
help for choices 28 sticky keys, definition of 37
System Editor 41
using 7
working with 7
preventing unauthorized use of
system 39 T
Printer object, description of 5 tailoring a DOS program 36
Templates folder, description of 4
printing a Master Index entry 24 throwing away an object 12
printing objects 11 tile arrangement 19
Procedures Language/2 REXX 41
productivity programs tiling windows 18
program, interactive 14 title bar 15
topmost window 15
protecting information on tutorial 27
system 39
Q U
Quick Start using the keyboard 47
description of viii
54IBM OS/2 32-bit Overview Pre-Release Copy
Index
V
view the contents of an object 14
W
Window List
description of 16
using 16
windows
arranging 18
border 15
cascade 18
closing 15
dragging 18
interactive 15
maximizing 15
minimizing 15
scroll bar 15
selecting parts 15
sizing 17
tile 18
title bar 15
Window List 16
window, definition of 14
working with objects 8
Index 55
�
READ6167.DOC
Read Me First
Welcome to IBM * OS/2 * Version 2.0, the integrating platform for the
personal computer systems.
This development version of the OS/2 operating system is intended
to run existing OS/2, Windows ** and DOS applications.
IBM and others are testing many DOS, Windows, and OS/2 appli-
cations with this operating system. However, some applications,
or functions within applications, might not currently work. We
encourage you to use the support system provided to you to give
us your comments. IBM needs your feedback to ensure that OS/2
Version 2.0 is the best possible product.
Enjoy the new world of the OS/2 operating system!
What's New in This Version?
? The Workplace Shell is now the user interface.
? You can run Windows applications in standard mode,
unchanged, without installing Windows on your system.
? You can start ANY version of DOS in DOS sessions. This
means you can run even version-specific DOS applications.
? Support for DOS unique device drivers has been added.
? More mini-applications, including an asynchronous communi-
cations connection and a LAN-based chess game, have been
added.
? PM installation has been simplified. The enhancements assist
users in customizing the system to their needs.
* Trademark of the IBM Corporation.
** Trademark of the Microsoft Corporation.
Read Me First 1
Installation
Before installing this version of OS/2 2.0, you need to format the
partition in which it will be installed. Otherwise, all your compo-
nents might not work correctly.
Select Features and Install
If you choose the installation option elect Features and Install,?
you must select DOS and all font choices. Otherwise, problems
might occur later.
Migration of Existing Applications
Although you are prompted to migrate your existing applications
during installation, this function has not been implemented in this
development version.
Printer Port Warning Message
When you install a printer during system installation, you will
receive the following pop-up message, even if you have not
installed another printer:
The port you have selected has a printer attached to it.
Select OK and your printer will be installed, using the port you
selected.
Additionally, you will have an extra print object named LPT1Q.
This object is attached to the IBMNULL driver and may be dis-
carded. To discard the object, place the mouse pointer over the
object, press and hold mouse button 2, and drag the object to the
shredder. When you release the mouse button, the object will be
discarded.
2
Installing Printers after OS/2 Installation
We recommend that you install printers during the OS/2 installa-
tion. If you do not, you will need to manually copy IBMNULL.DRV
from the Presentation Manager Device Driver diskette 1 to the
\OS2\DLL\ subdirectory before you install the printer.
In addition, you must make this printer your application default. To
select the printer as your default printer:
1. Move the mouse pointer to the printer object.
2. Press mouse button 2 to get a pop-up menu for the print
object.
3. Select Set default.
4. Select your printer.
Minimum System Configuration Requirements
To install and use the OS/2 operating system, you need a personal
computer system with an 80386, 80386SX, 80486, or 80486SX micro-
processor.
Currently, you need 4MB of memory to install OS/2 2.0.
We are continuing to work on improving the DASD usage of OS/2
2.0. The following numbers reflect current requirements and might
be different in the final product.
Currently, there are three installation options. The DASD require-
ments for these are:
? Install All Features: 26MB
? Install Preselected Features: 18MB
? Select Features and Install: 12MB?6MB
Note: These numbers are more accurate than the numbers shown
on the installation screens.
You also need to plan for a swap file, which can be placed on any
drive. The size of the swap file varies greatly, depending upon
Read Me First 3
how much memory you have in your system and how much
memory your applications use. We recommend a swap-file size of
5MB to 9MB.
If the system cannot extend the swap file when required, the oper-
ation being attempted (for example, an application being loaded)
will fail, and a pop-up message will appear.
Currently, the installation program scans your hard disk and
allows you to install OS/2 only if the target partition is at least
18MB.
If you are planning to install IBM Extended Services for OS/2 or
IBM OS/2 LAN Server V2.0, refer to the estrictions and Installa-
tion Instructions?for these products for more information about
DASD requirements.
Hardware Considerations
XGA Displays
The current version does not have an XGA driver. All XGA dis-
plays will be run in VGA mode.
Floating Point Emulator
Applications that require the use of a math coprocessor might not
run; those that can exploit the math coprocessor might run slower.
This is because the system has a floating-point emulator, which
emulates the math coprocessor when floating-point hardware is
not present. In hardware configurations that have a ?86 B1 step-
ping level,?the system will disable the 80387 hardware and use
the floating-point emulator without notifying the user.
The floating-point emulator will NOT generate denormal
exceptions.
4
Printing from a Serial Port with a PS/2 Model 90 or 95
*
If you need to use the COM port in a PS/2 Model 90 or 95 with
Enhanced set to ON, make sure that the Serial Transmit and Serial
Receive Arbitration Levels shown in the hardware configuration
are set to Dedicated, with different numbers. To do this, you need
to use the Setup/Diagnostics diskette. When both levels of a serial
port are set to Shared, data communication and printing from the
COM port with Enhanced set to ON will not work correctly
For example, when Serial Port is SERIAL 2 in the hardware config-
uration, its corresponding Serial Transmit Arbitration Level should
be DEDICATED 3, and Serial Receive Arbitration Level should be
DEDICATED 4.
Overall System Performance
Because performance work on OS/2 2.0 is not finished, we recom-
mend that you do not use this version for performance
benchmarking or evaluation.
FAT File System Performance
Performance of the FAT file system is better than in earlier ver-
sions.
Performance enhancements that add intelligent read-ahead and
lazy-writing were made to DISKCACHE. In the previous EEP
version, OS/2 had the potential to lose data if bad sectors were
found during lazy-write; this has been corrected.
* Trademark of the IBM Corporation.
Read Me First 5
High Performance File System Performance
The performance work on HPFS is not yet finished. In partitions
smaller than 60MB, performance is about the same as that of the
FAT file system; in larger partitions, it is somewhat faster.
In some configurations, formatting your hard disk for the HPFS
might be slower than formatting the same disk for the FAT file
system.
Scheduler Performance
OS/2 now uses dynamic time-slicing. Try the default first. If per-
formance is not better, go back to your specific setting.
Loader Performance
Application load time is better than in previous versions, but still
not as fast as in Version 1.3. To improve application load times,
add ,128 to the end of the DISKCACHE statement
(DISKCACHE=64,LW,128). This change improves load times for
the FAT file system.
DOS-Session Performance
DOS performance is best in DOS full-screen sessions; DOS window
sessions provide somewhat slower performance. The perform-
ance of some applications can be increased by adjusting:
? IDLE_SENSITIVITY
? EMS_MEMORY_LIMIT and XMS_MEMORY_LIMIT. If your appli-
cation does not need extended or expanded memory, you need
not allocate it.
Workplace Shell Performance
The performance work on the Workplace Shell is not yet finished.
6
Windows Performance
The performance work on Windows is not yet finished.
Printing Performance
The performance on printing has been improved.
Workplace Shell
? We recommend that you use the Shutdown option from the
desktop pop-up menu before powering down your system.
?
In this development version, be careful not to shred the OS/2
System and Startup folders. If these objects are shredded, you
have to reinstall the operating system to recover them.
? Some of the documentation states that you must press mouse
buttons 1 and 2 at the same time to display a pop-up menu.
The correct action is to single-click mouse button 2.
? In this development version, Refresh has been included in the
folder context menus to allow users to update the contents of a
folder. This function enables folders to see objects that
another program may have copied since the folder was
opened. In the final version, folders will update automatically
and Refresh will be removed from the menus.
? Before using the diskette object, make sure that the diskette is
properly inserted in the diskette drive. Failure to do so might
cause unpredictable results.
? Copying files from one drive to another using the Drives folder
is not functioning. Use the OS/2 and DOS command prompts
instead.
? The edit icon option from the Icon page of a Settings notebook
is not yet fully functional.
?
If you use the FIND command from a pop-up menu and specify
?.*?as the item to find, the system will hang; you will have to
restart it.
? The Sort page of the Folder Settings notebook is not func-
tioning, so the system will not sort the contents of a folder.
Read Me First 7
? The Include page of the Folder Settings notebook is not func-
tioning. Redefining the files to include in a folder does not
work.
? The Menu page of the Folder Settings notebook is not func-
tioning, so you cannot modify folder menus.
? The color palette can only be manipulated by using the mouse.
Windows
The current OS/2 version supports VGA only for Windows sessions.
On the 8514/A and XGA, Windows will not run in VGA mode.
Windows printing
The current version supports printing only to the OS/2 default
printer.
The current version contains only a subset of the available
Windows printer drivers. They are automatically installed when
you install and configure the OS/2 printer drivers. The drivers
shipped with this version of OS/2 2.0 are:
? PSCRIPT.DRV
? EPSON24.DRV
? EPSON9.DRV
?
PROPRINT.DRV
? PROPRN24.DRV
? QWIII.DRV
? IBMCOLOR.DRV
? IBMGRX.DRV
? TTY.DRV
If you currently use the Windows program, you can install the
printer drivers using the Windows control panel the same way you
would under Windows. If you use a Windows driver that was not
shipped with the OS/2 operating system, do the following:
1. Start a Windows session by clicking on the Windows Session
icon in the Command Prompts folder (in the OS/2 System
folder).
8
2. Start the Windows Control Panel.
3. Double-click on the printer icon.
4. Select Add Printer.
5. Select Unlisted Printer from the list of printers to install.
6. Select the Install push button.
7. Search for the driver you wish to install.
8. Select OK to exit this panel.
9. Select Configure.
10. Select LPT1.OS2 or LPT2.OS2 to associate the printer driver
with a printer port. Do NOT use LPT1 or LPT2.
11. Select Setup.
12. Select the printer you wish to use.
13. Select OK to exit this panel.
14. Select OK to exit the next panel.
15. Exit to an OS/2 session by double-clicking on the OS/2 icon at
the bottom of the Windows screen.
16. Select the OS/2 printer object.
17. Use create another, copy, or copy from template to create
another print destination.
18. Use open settings to configure the required port (for example,
LPT1) and printer driver (IBMNULL).
19. OS/2 always installs IBMNULL during system installation. If
IBMNULL is not shown in the list of available printer drivers,
use the Install pop-up menu option on an existing printer driver
to get the printer driver install dialog. Insert PM device driver
diskette 1, and press Refresh. Select IBMNULL from the list,
and press Install. Press Cancel and select IBMNULL for the
print destination.
Read Me First 9
Windows Information
? To install Windows applications in the OS/2 operating system,
follow the manufacturer's instructions. If the installation proce-
dure does not work properly, open a DOS session and try the
installation procedure again. If the procedure still does not
work, run the installation command using RUN from the File
menu.
? To run Windows applications, choose one of the following:
?Create a Windows full-screen object and type the name of
the Windows application.
?Create a DOS full-screen object and type WINOS2.COM
and the name of the Windows application in the parameter
field.
?Select RUN in the Windows Program Manager.
?Type WINOS2 followed by your program name in a DOS
session.
You cannot run DOS applications using RUN from the File
menu.
? If a Windows application produces an error indicating that
there is insufficient memory available, increase the DOS
setting, DPMI_MEMORY_LIMIT from the default (3MB) to 4MB
or 5MB. This setting should not be set arbitrarily high since
the OS/2 Swapper will grow by the amount of additional
memory allocated.
? To enable Ctrl+Esc to bring up the Windows task list or
Alt+Esc to switch between your Windows applications only,
change the DOS setting KBD_CTRL_BYPASS.
? If you get FATAL ERROR 401 (or 410) when you try to start a
multiple-application Windows session, the Windows video
drivers were not properly configured. Make sure that the fol-
lowing lines are in the SYSTEM.INI file in the directory
c:\os2\mdos\winos2 (where c: is your OS/2 startup drive).
display.drv=vga.drv
fonts.fon=vgasys.fon
fixedfon.fon=vgafix.fon
oemfonts.fon=vgaoem.fon
10
? If you are using multiple Windows applications, change the
DOS setting, DOS_FCBS to improve performance.
? Dynamic data exchange between Windows applications in sep-
arate DOS sessions, or between Presentation Manager (PM)
and Windows applications, might require switching between
the DOS sessions (using Ctrl+Esc).
? If you set the Windows Clipboard to PUBLIC:
?PrintScreen in the Windows session will not copy data to
the clipboard.
?Any text string, bit map, or metafile that is greater than
48KB will not be transferred to the Public Clipboard.
DOS Applications and Environments
Interrupt 21h Find First Call
Some DOS applications that use the interrupt 21h find first call
might not work properly (for example, TAPCIS). To fix this problem
in this development version, execute FIX_FIND (located in
\OS2\MDOS) in the DOS session before you run the failing applica-
tion. It will not be necessary to correct this problem in future ver-
sions.
UNDELETE Command
Currently, the UNDELETE command works only in OS/2 sessions.
In later versions, UNDELETE also will be supported in DOS ses-
sions.
Background DOS Programs
Some DOS programs need special DOS settings to run properly in
the background. Without these settings, some applications appear
to stop.
The OS/2 operating system has a feature called 﨑OS Settings.?
Its purpose is to provide the highest level of compatibility for indi-
Read Me First 11
vidual DOS applications. DOS settings are defined for each DOS
session and are set with the Settings choice in the pop-up menu.
There are two DOS settings that might help when you run pro-
grams in the background:
? HW_TIMER: Changing this setting from Off to On enables the
application to receive timer interrupts while running in the
background. Some programs need these interrupts (for
example, SuperKey****, or WordPerfect when it is running
macros). Some communications programs also run better
when this setting is On.
? IDLE_SENSITIVITY: Increasing this property to a setting above
the default of 75% will boost the priority of that individual DOS
session.
Double Mouse Pointers
If you run an application in a DOS window session, and two mouse
pointers are displayed, change the DOS setting,
MOUSE_EXCLUSIVE_ACCESS to On.
Generic Hardware Support
Generic hardware support enables OS/2 2.0 to run many programs
that were not possible in earlier versions. Scanners, FAX, 3270,
network, and other specialized hardware can be used in a DOS
session just as they are in DOS.
Novell DOS LAN Requestor
To use the Novell DOS LAN Requestor in a DOS session under
OS/2 2.0, set the DOS settings as follows:
DOS_DEVICE
c:\dxma0mod.sys
c:\dxmc0mod.sys
** WordPerfect is a trademark of WordPerfect Corporation. SuperKey is a trade-
mark of Borland International, Inc.
12
Note that these are the settings for Token Ring.
DOS_VERSION
net4.com,4,0,255
DOS_LASTDRIVE
m
If you have more drives than m, change to the highest drive
letter.
The drive after the one you specified for LASTDRIVE will become
your logon drive.
Novell will use the adapter directly, so you will not be able to use
the network adapter in another session.
Expanded Memory Conflicts
To function, expanded memory service (EMS) needs 64KB of con-
tiguous space above 640KB. Unfortunately it must share this
memory with adapters (network, disk, display, and 3270) that
locate themselves in memory above 640KB. If you have used an
EMS emulator under DOS, you are probably aware of these con-
flicts and know some techniques to fix them. The OS/2 operating
system also provides a technique that simplifies the resolution of
these conflicts.
The DOS setting, MEM_INCLUDE_REGIONS, enables you to disable
the adapter memory for any session and let EMS use it instead.
For example, if you have a 3270 adapter and already have OS/2
Communications Manager support, you will not need to use the
3270 memory in a DOS session. To disable this memory, you will
need to find the address of the 3270 adapter. Use the PS/2 Refer-
ence Diskettes (or an equivalent method for your system). When
the address is known, specify the range in the Include regions
property. Most IBM 3270 adapters will start at CE00 (0xCE000
absolute). The property should be set to:
CE000-CFFFF
This will allow EMS to use this memory if there is enough near this
range.
Read Me First 13
If this is not sufficient because you need access to multiple
adapters from a single DOS session, you will need to rearrange
your memory addresses. This is the same process you follow
under DOS.
VCPI and Other Non-DPMI Extenders
VCPI (Virtual Control Program Interface) and other non-DPMI (DOS
Protect Mode Interface) extenders will not be supported in OS/2
DOS sessions. These extenders are believed to compromise
system integrity in a multitasking environment such as OS/2 2.0.
Disk Writes using Physical Sector Addressing
Hard-disk writes using physical sector addressing are not sup-
ported because they violate system integrity in a multitasking
operating system. (Although most functions of the Norton Utilities **
are supported, the SORT/UNDELETE functions are not. Use the
OS/2 UNDELETE command instead.)
High Memory and Upper Memory Blocks
The second parameter of the DOS= statement specifies whether
applications can use memory above 640KB (upper memory
blocks). The default for this release is DOS=LOW,NOUMB (low
memory blocks). We encourage you to change the DOS settings
DOS_UMB and DOS_HIGHL so that your applications have access
to upper memory blocks and extra memory.
Borland Turbo Assembler
To run the Turbo Assembler ** (TASMX), you must set the DOS
setting, DPMI_API to enabled.
** Norton Utilities is a Trademark of Symantec Corporation. Turbo Assembler is a
trademark of Borland International, Inc.
14
Miscellaneous
32-Bit Programs
For this development version of OS/2 2.0, developers of 32-bit pro-
grams need to relink their programs using the latest version of
LINK386.
Printing to Files
The printer object Output to File option is not functioning properly.
This will be corrected in the final version.
High Performance File System
We are aware of intermittent problems with the high performance
file system on certain hardware configurations. If you experience
these problems, insert the line 﨏ACHE /LAZY:OFF?in your
STARTUP.CMD file. You may notice some performance degrada-
tion as a result of this.
Sticky Pad
When you select Sticky Pad from the Productivity Folder, you will
get the message: SHLERR_MESSAGE_NOT_FOUND.
The Sticky Pad will not work and you will be returned to the Pro-
ductivity folder.
The DOS_VERSION Setting
When you change the DOS setting, DOS_VERSION, you must save
it immediately after entering the value. If you change another DOS
setting before you save the DOS_VERSION value, the value will be
lost.
Read Me First 15
Print Object Pop-Up Menu
The pop-up menu brought up from the title bar icon does not func-
tion properly. Click on the window's background instead.
16
�
V2-WIN.DOC
IBM Internal Use Only
1.0 Microsoft Windows Applications
Editor's Note
This component of the product was being extensively worked at the time of
writing, and no firm information was available. The subject must be thor-
oughly researched and documented prior to publication.
OS/2 V2 provides the capability for Microsoft Windows applications to run under
OS/2 V2. This support allows applications written for Windows 3.0 and previous
versions of Windows to coexist and execute in the same machine under OS/2 V2.
Each Windows application executes as a protected mode process. As such,
Windows applications are subject to the same application protection facilities
provided to other protected mode applications (both OS/2 and MVDM tasks)
under OS/2 V2. Windows applications are protected from other Windows appli-
cations and from DOS and OS/2 applications executing in the system. This is in
contrast to the native Windows 3.0 environment, where protection is limited to
Windows 3.0 applications only.
The execution of Windows applications as protected mode tasks also allows
these applications to take full advantage of the pre-emptive multitasking capabili-
ties of OS/2 V2, with full pre-emptive multitasking between Windows applications,
OS/2 applications and DOS applications. This is again in contrast to the native
Windows 3.0 environment, where pre-emptive multitasking is available only when
Windows 3.0 is running in enhanced mode, thereby impacting performance and
preventing many applications written for previous versions of Windows from exe-
cuting. OS/2 V2 has no such restriction. Windows applications running under
OS/2 V2 will run in a mode equivalent to the real or standard modes of Windows
3.0. The enhanced mode of Windows 3.0 is not required since OS/2 V2 operating
system itself provides equivalent function.
1.1 The Windows Environment
Microsoft Windows 3.0 application support is provided by default during the
installation of OS/2 V2. Should the user select Selective Install at time of installa-
tion and highlight DOS + Windows Environment, then all the files necessary to
provide Windows Application support will be installed in the following subdirecto-
ries:
? \OS2\MDOS\WINOS2
? \OS2\MDOS\WINOS2\SYSTEM
OS/2 V2 CONFIG.SYS will be updated to include these directories in the PATH
statement; MVDM (Multiple Virtual DOS Machine) support is also installed.
Windows REAL Mode requires 640Kb of Conventional memory and several MB of
Expanded memory (EMS). The EMS VDD (Virtual Device Driver) is also required.
Windows STANDARD Mode requires that the following statements be included in
the OS/2 2.0 CONFIG.SYS file:
? DEVICE=C:\OS2\MDOS\VDPMI.SYS (DOS Protect Mode Interface)
+ Copyright IBM Corp. 1991 1-1
IBM Internal Use Only
? DEVICE=C:\OS2\MDOS\VDPX.SYS (DOS Extender Virtual Device Driver).
If these device drivers are not loaded, Windows will execute in REAL Mode.
Windows can use Expanded Memory which conforms to the LIM EMS 4.0 specifi-
cation when running in REAL Mode. This memory is primarily used for storing
background applications. An appropriate Expanded Memory Manager must be
installed. Windows Applications can however use a LIM EMS 3.2 Expanded
Memory manager to store data in memory. In STANDARD Mode, Windows will
use Extended Memory.
Upon completion of the installation process the user will be given the opportunity
to migrate installed Windows Applications to the OS/2 V2 Workplace Shell.
All Windows Applications which are migrated, will have the appropriate DOS and
Windows Settings established, as defined in the Certified Application Database
(shipped as a standard component of OS/2 2.0).
Editor's Note
The Certified Applications Datbase is currently under development. This
aspect must be tested, once available. The procedures involved in updating
this database must be investigated.
1.1.1 The Certified Applications Database (CAD)
The Certified Applications Database provides the vehicle to automatically set the
DOS Property settings for both certified DOS and Windows applications. The user
will be presented with a list of the certified applications found, which can be
migrated. The user may select any or all of these applications. The CAD will be
searched for each of the selected applications. The DOS and/or Windows proper-
ties information found in the database will be used to automatically assign set-
tings to the applications. Windows applications will be placed in a single
Windows Folder. DOS applications are placed in a single DOS Applications
Folder.
Note only the property settings for applications which differ from the default set-
tings will be held in the database.
DOS Settings information for DOS applications will be stored in the OS2.INI file.
Windows applications' settings are stored in the WIN.INI file.
Note
Only the settings for those applications which have been certified via
approved IBM testing channels will be recorded in the Certified Applications
Database (CAD).
The CAD will be a binary database generated from an ASCII database and a pre-
defined tag file. Each field in the ASCII database will start with a descriptive tag
that is associated with a value between 0-225 in the predefined tag file. When the
binary CAD generation tool encounters one of the descriptive tags, it will gen-
erate an entry in the binary CAD with a 0-255 value specified in the predefined
1-2 VMBOOT
IBM Internal Use Only
tag file. To add new or additional DOS properties, a short descriptive tag is
created for the ASCII file and associated with an unused value between 0-255 in
the predefined tag file. A length specification is also provided for the value in the
tag file.
Each field in the binary CAD starts with a predefined tag value of 0-255 that iden-
tifies the field. This tag is followed by a "size" field, which in turn is followed by
the actual value of the field. The maximum number of tags is 256.
Each application in the CAD will have the following minimum information:
? The filename used to start the application
? A next application pointer
? The title of the application.
The filename that starts the application is used to identify the application on the
hard drive. The next application pointer points directly to the next application
entry in the CAD. This provides the ability to jump from one entry to the next
without parsing all of the tags between entries in the CAD. The application title is
displayed to the user if the application is found on the hard drive. The user will
use this information to specify if the application is to be migrated.
The filename extensions held in the CAD will determine what files are searched
for, that is all .EXE, .COM and .BAT files.
1.1.2 Single Application and Multiple Application VDMs
Two Windows environments are supported:
? SAVDMs (Single Application VDMs) which contain a single Windows Applica-
tion. The icon supplied with the Windows Application will be defined in the
SAVDM.
?
MAVDMs (Multiple Application VDMs). This activates the Windows Program
Manager, allowing the user to access a number of Windows Applications.
Each SAVDM will indicate the Windows execution mode based on the file type
specified in the *.EXE header of the Windows Application. REAL Mode will be
indicated for non-Windows 3.0 applications. Auto-Select (Real or Standard mode)
is selected, based on processor type.
The following components of Microsoft Windows 3.0 will be supported and are
available within the OS/2 2.0 kernel:
? Windows Real Mode kernel (WINOS2.COM and KERNEL.EXE)
? Modified Windows Standard Mode kernel (OS2K286.EXE)
? Modified DOS Extender (OS2DOSX.EXE)
? Print Manager (Spool Function)
? Program Manager:
?Permit the starting of multiple Windows Applications in a VDM
?Permit switching between Windows Applications in the VDM
? Help Manager
Microsoft Windows Applications 1-3
IBM Internal Use Only
? Video Device Drivers
? Keyboard, Mouse and Communications Device Drivers
? TaskManager
? Windows User and GDI DLLs
? Printer Device Drivers
? Clipboard support
? Control Panel with functions limited to:
?Printer Install
?Color
?Fonts
?Sound
?Mouse
?International
?Date/Time
?KBD (Keyboard rate).
The Clock program and Recorder Utility (Create/Recall keystroke macros) are
available in Fullscreen Windows - (MAVDM) Multiple Application Virtual DOS
Machine.
Note
1. Microsoft Windows 386 Enhanced Mode is not supported
2. Microsoft Windows Multi-Media extensions are not supported.
The following Microsoft Windows 3.0 components are not included within the
OS/2 kernel, as OS/2 equivalents are provided, or are not required within an
OS/2 environment:
? File Manager
? Systems Editor (SYSEDIT)
? Games
? Write
? Terminal
? Notepad
? Cardfile
? Calendar
? Calculator
? PIF Editor
? Paintbrush
?
Wallpaper bitmaps
1-4 VMBOOT
IBM Internal Use Only
? Setup (Windows' Installation and Configuration changes).
1.2 Defining Windows Applications
Figure 1-1. Program Reference Object's Setting Notebook.
+-----------------------------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------------------------------------------+
The Windows application execution environment is defined in the Program Page
of the program reference object's settings notebook. The Windows Application
name is entered as the Path and Filename. This entry will cause DOSQAppType
to be issued to determine the application type. The Program Type in the Mode
Page will be set to Windows Full Screen. A "Windows" page will appear for the
Windows application containing a New Windows Setting. This defines whether
the Windows kernel will execute in REAL, Standard, or Auto-Select mode. REAL
mode is highlighted as the default if the Windows application is NOT a Protect
mode Windows application, otherwise AUTO-SELECT is the default. All DOS set-
tings are selectable for Windows applications via the Windows page, Windows
settings are also included in the same list.
Changes are effective immediately and are saved when the Settings Notebook is
closed or when the system is shut down. The Reset Button resets to the previous
settings.
The Windows application is started by double-clicking on the icon within the
folder. The application executes in the VDM in which it was defined.
Microsoft Windows Applications 1-5
IBM Internal Use Only
Operation
The SAVDM is created for the execution of the Windows application. The
Workplace Shell starts WINOS2.COM as the application to start in the VDM.
The Windows Application to be executed is passed as a parameter to
WINOS2. This process is transparent to the user. If the application is
launched from an OS/2 Command Prompt, the user will notice the VDM being
launched as the DOS prompt is momentarily displayed before the Windows
application is launched.
If WINOS2 is to execute in REAL Mode, the /r option will be inserted into the
parameter list for the VDM creation, based on the WIN Setting. If STANDARD
Mode was highlighted, /s is passed as a parameter to WINOS2. The default is
to pass no Windows options, just the application name.
When the Windows Application is terminated, WINOS2.COM terminates
causing the VDM to be terminated.
Each SAVDM will have an icon on the Desktop, for the application within the
SAVDM. This icon will be the Windows icon for this application. The icon title will
be the text specified in the Program Title field of the New Program dialog.
Editors Note
Check to ensure that the Windows Application icon is used and that the
SAVDM does not display the default DOS icon.
Ctrl-Esc is the key combination used to display the Task List.
Alt-Esc is the key combination used to switch to the next session as defined in
the Workplace Shell.
In the case of MAVDM (Windows Application Group), the Windows Program
Manager is loaded in the MAVDM transparently to the user. Applications are
launched from the Windows Program Manager. Here the Task List will display
the Windows Application currently executing in this VDM.
Ctrl-Esc is used within the VDM to display the Task List.
Alt-Esc is used to switch to the next session defined in the Workplace Shell.
The Workplace Shell icon will represent the Windows VDM, not the application(s)
executing within the VDM.
The user must select Exit Windows in the Windows Programs Manager to termi-
nate the VDM, or close the VDM from the Workplace Shell.
The following applications are already started (iconized) on first entry into the
VDM for both SAVDMs and MAVDMs:
? Modified Windows Clipboard Viewer Program
? DDE Server/Agent Application
1-6 VMBOOT
IBM Internal Use Only
? Recorder (not started in MAVDM)
? Presentation Manager icon
? Task Manager (no icon)
? Windows Program Manager (not visible in a SAVDM)
? Clock (Iconized, MAVDM only)
? Windows Control Panel (not started, MAVDM only).
1.3 Launching Windows Applications in OS/2 2.0
The following methods may be used to start Windows Applications:
1. Select the Application name from within File Manager
2. Enter the Application name at an OS/2 Command line prompt
3. Install the application in a folder, in the Workplace Shell Desktop.
If the application is started from either the OS/2 File Manager or an OS/2
command prompt, an SAVDM will be created. If the Application is started from
an icon, either a SAVDM or a MAVDM will be created, depending on how the
application was defined at installation.
When a MAVDM icon is selected, a Windows VDM will be created with the
Windows Program Manager maximized. The user may then elect to start any
Windows applications within the VDM via the Windows Program Manager. The
user may also define a group of Windows applications which will be activated
when this VDM is started. These applications are specified in the Parameters
field of the of the New Program Dialog. Full path name and parameters should
be specified.
The syntax for the parameters field is:
/R|/S 詛~?|泘 App1 App-parms ?~
?|洺 App2 App-parms
? /R Windows REAL Mode
? /S Windows Standard Mode
? Optional Parameters ? ~
?
! Start the Windows Application Minimized
?
?Start the Windows Application Maximized.
If neither the Exclamation Mark nor the Caret is specified, the Windows Applica-
tion will start Normalized, approximately one third the screen size.
A MAVDM will be created if one of the following are present:
? {} Braces
?
Comma separating the application names
? An Application Name is not passed as a parameter.
Microsoft Windows Applications 1-7
IBM Internal Use Only
1.4 Windows Device Drivers and Environment Settings
A WIN.INI file is built during OS/2 installation. The options for the devices
selected for the OS/2 environment are included in this file.
Should the user migrate from a Windows 3.0 environment, the Windows WIN.INI
will be left unchanged. WINOS2 will look in C:\OS2\MDOS\WINOS2 subdirectory
for the correct WIN.INI file. The initial WIN.INI file in the WINOS2 subdirectory is
created from the Windows WIN.INI.
The following initialization files are created (including the WIN.INI file):
? PROGMAN.INI
? CONTROL.INI
? SYSTEM.INI.
1.4.1 WIN.INI
WIN.INI contains a number of sections which may be customized by the user,
including which applications should be started or run, when Windows is started.
Each Windows Application is recorded in a separate section indicating the drive
and path to execute the application. The supported file extensions for each appli-
cation installed, are recorded in the Extensions section.
1.4.2 PROGMAN.INI
PROGMAN.INI contains the Program Manager settings, the following sections are
included:
? Setting: Describes the settings of the Program Manager, the user's prefer-
ence
? Groups: Specifies the Program Groups that exist in Program Manager.
1.4.3 CONTROL.INI
CONTROL.INI contains the color and desktop settings for the Control Panel. The
following options are available:
?
Current: Specifies the Window color setting
? Color Schemes: Specifies the available color options
? Custom Colors: Specifies up to 16 customization colors
? Patterns: Specifies options for the Desktop pattern.
1.4.4 SYSTEM.INI
SYSTEM.INI contains the global system information used by Windows when it
starts. Changes are not effective until Windows is restarted.
The following sections are included:
? Boot: Lists the drivers and Windows modules. The OS/2 file contains a sepa-
rate Boot section which covers MAVDM and SAVDM default applications:
?GOPM This program returns the user to the Workplace Shell
?Clock The Windows clock program
1-8 VMBOOT
IBM Internal Use Only
?Clipbrd The modified Clipboard program
?DDEAGENT The modified DDE (Dynamic Data Exchange) program
?Printman: MAVDM only, the Printer Manager program
? Boot.description: Lists the names of devices the user can change using
Windows Setup
? Keyboard: Contains information about the keyboard
? NonWindowsApp: This section should not contain any information, non
Windows Applications are started from the OS/2 desktop
? Standard: Contains information required by Windows to run in Standard
Mode
? 386Enh: Contains information used by Windows to operate in 386 Enhanced
Mode. This section is not used as OS/2 provides equivalent function.
The Initialization and Group files are required to restore a corrupted Windows
environment. Backups of these files should be taken prior to making any
changes to this environment.
Note
The Windows 3.0 APIs will access the new WIN.INI file.
The WIN.INI file is updated by Install and OS/2 Print Manager.
The WIN.INI file is updated with the appropriate information for the following
options. Installation will install the Windows Device Driver files in the appropriate
directories.
? Keyboard
? Mouse
? Video
? Printer
? Codepage.
If a device driver (Video, Mouse, Keyboard) is supported in Windows and NOT
supported by OS/2, the Windows version will not be supported.
Install will update the new WIN.INI file to include the printer device driver details
that Windows requires for printers selected under OS/2. Install selects a
Windows printer device driver comparable with an OS/2 printer device driver.
The Windows printer device driver will operate in its default mode. If the printer
device driver needs to be configured in a mode other than the default mode, the
printer should be configured from within the Windows Control Panel.
If there is no equivalent OS/2 printer device driver, the device driver should be
installed and configured via the Windows Control panel.
Microsoft Windows Applications 1-9
IBM Internal Use Only
Note
At the time of writing this facility/function could not be tested
1-10 VMBOOT
IBM Internal Use Only
2.0 Dynamic Data Exchange (DDE)
This chapter describes DDE support between Windows Applications in a full
screen VDM.
DDE is a message protocol for dynamic data exchange between Windows pro-
grams. Data may be shared among applications, the intention being to create an
integrated Windows environment.
The native Windows environment supports the following mechanisms which
applications can use to exchange data:
? Clipboard transfers
? Dynamic link libraries
? Dynamic Data Exchange (DDE).
Note
DDE is the only mechanism that supports passing of Global Memory Handles
between applications.
2.1 Clipboard Transfers
The Clipboard acts as a temporary repository of information. This process
requires the direct involvement of the user to initiate and complete the data
transfer process.
2.2 Dynamic Link Libraries (DLL)
A DLL can be designed to act as repository for data being shared between appli-
cations. The data is stored in the static data area of the DLL's data segment.
2.3 Data Exchange in Windows
Windows is a Message-based Architecture and message passing is used to
transfer information between applications.
Windows messages however contain only two parameters, wParam and lParam
for passing data. The DDE protocol defines how these message parameters will
be used to pass large amounts of data by means of Global atoms and Global
shared memory handles.
A Global atom is a reference to a character string and is used to identify:
? The applications exchanging data
? The nature of the data being exchanged
?
The data items.
+ Copyright IBM Corp. 1991 2-1
IBM Internal Use Only
A Global shared memory handle is a handle to a block of allocated memory.
Global shared memory objects store data items passed between applications,
protocol options and remote execution strings.
2.3.1 DDE Concepts
Client, Server and Conversation:
Two applications participating in dynamic data exchange are engaged in a DDE
Conversation. The application that initiates the conversation is the Client Appli-
cation. The application which responds to the client is the Server Application.
An application may be engaged in several conversations at the same time,
acting as a client in some applications and as a server in others. A DDE conver-
sation takes place between two windows, one for each of the participating appli-
cations. The window may be the main window of the application, a sub-window
associated with the application, or a hidden window. The hidden window is used
to process DDE messages.
DDE identifies the units of data passed between the client and server with a
three-level hierarchy of:
? Item
?
Topic
? Application Name.
Each DDE conversation is uniquely identified by the application name and topic.
The application name is normally the name of the server application. The topic is
a general classification of data, within which multiple data items may be
exchanged during the conversation. The item is the actual information related to
the conversation topic that is exchanged between the applications. Values for the
data item can be passed from the server to the client, or from client to server.
The format of the data item may be any one of the clipboard formats.
2.3.2 Permanent Data Links
Once the DDE conversation has been initiated, the client can establish one or
more permanent data links with a server. A data link is a communication mech-
anism by which the server notifies the client whenever the value of a given data
item changes.
The link is permanent in the sense that the notification process continues until
the data link or DDE conversation is terminated.
The DDE link may be WARM or HOT. In a warm data link, the server notifies the
client that a value of a given data item has changed, but the server does not
actually send the data value to the client until the client requests it. In a hot data
link, the server immediately sends the changed data value to the client.
Applications which support DDE, typically provide a Copy/Paste Link command in
the Edit menu to allow the user to establish a DDE link.
2-2 VMBOOT
IBM Internal Use Only
2.4 OS/2 DDE Support in Fullscreen VDM
In a native Windows 3.0 environment, a Windows Application (Client) will send a
broadcast DDE Initiate message. Windows serially posts a message to every
Windows Application currently running and then awaits a reply. As described
above, the Initiate conversation message contains the DDE topic to which any
Windows application can respond. The Client application continues execution
when all other applications have serviced their message. At this time the Client
application communicates directly with the Server applications, as opposed to
the initial broadcast message.
OS/2 provides two applications to support communications between VDMs,
without altering the Windows code:
1. A resident Windows application referred to as the DDE ServerAgent (SA)
2. A DOS Protect Mode application referred to as the DDEServer
(VDMSRVR.EXE).
2.4.1 ServerAgent
The Windows VDM resident ServerAgent consists of two parts:
? A "ServerAgent" which sends and receives messages outside of the VDM
? One or more "Agents" (each agent is a child window of the ServerAgent),
which act as clones of applications running in other VDMs.
DDE will not be available outside of the VDM, if either the DDEServer or the
VDM's ServerAgent is not executing. The ServerAgent is automatically started
when the Windows VDM is started.
p.The ServerAgent provides a user interface with the following pulldown menus:
1. File Menu:
? Exit: The ServerAgent exits, all subsequent DDE is local to the VDM
? Save As: The contents of the internal trace log buffer is written to the
named file.
2. Options Menu:
? Trace: When selected this option traces and displays all DDE transactions
taking place outside of the VDM. The default is No Trace/Display. Once
enabled, this option remains in effect until explicitly disabled.
? Public DDE: If selected, DDE communicates outside of the confines of the
VDM. If not selected, DDE is local to the VDM. The default is Public DDE.
Should the user choose to exit from the DDE Interchange Agent, an information
message will be displayed indicating that DDE activity will be visible only to the
Windows applications executing in the current VDM, discontinuing DDE commu-
nication between Presentation Manager applications and other Windows applica-
tions.
The ServerAgent is responsible for all routing of DDE messages, including
broadcast messages beyond the confines of the VDM to the DDEServer. The
ServerAgent communicates to the DDEServer via named pipes.
Dynamic Data Exchange (DDE) 2-3
IBM Internal Use Only
Agent applications communicate with Windows applications in their VDM and the
ServerAgent executing in their VDM. Only the ServerAgent uses named pipes.
Agents send requests to the ServerAgent to be forwarded outside of the VDM.
2.4.2 DDEServer
The DDEServer is responsible for routing requests from ServerAgents to the
appropriate VDMs. The DDE process is schematically represented below:
�葺葺葺葺葺葺葺葺葺葺葺葺葙
� Windows Application A �
� SAVDM �
�葺葺葺葺葺?葺葺葺葺葺葺?
�葺葺葺葺莨葺葺葺葺葺葺葙
1. � DDE Initiate Message �
�葺葺葺葺?葺葺葺葺葺葺?
�葺葺葺葺馆葺葺葺葺葺葺葙 �葺葺葺葺葺葺葺葺葙
� DDE ServerAgent App A 谳葺葺 4 葺葺葺?Child Window �
�葺葺葺葺�葺葺葺葺葺�葺? �葺葺葺葺葙 � Agent for App D �
2. �葺馆葺葺葙 �葺葺葺� � �葺葺葺葺�葺葺葺葺�
�葺葺葺莼DDEServer谳葺葺葺葺葺葺葺葺? 3 �
� �葺葺葺�葺� (Named Pipes) � � 5
�葺葺馆葺葺葺葙 �莨葺葺葺葺葺葺?�葺葺莨葺馆葺葺? �
� ServerAgent � � ServerAgent � � ServerAgent � �
� App B � � App C � � App D 谳葺?
�葺葺葺葺葺葺? �葺葺葺葺葺葺葺� �葺葺葺�葺葺葺?
6
�葺葺葺莨葺葺葺葺葙
� Child Window �
� Agent for App A �
�葺葺葺葺葺葺葺葺?
Figure 2-1. DDE Process
1. A DDE Initiate Message is broadcast from Windows Application A.
2. The message is forwarded by the ServerAgent to the DDEServer, which in
turn forwards the message to every Windows Application SeverAgent.
3. ServerAgent for Windows Application D responds affirmatively to the DDE
Initiate message. This response is forwarded back to the ServerAgent for
Application A. This response includes the Windows Application handle and
the VDM handle of the VDM running Windows Application D.
4. The ServerAgent in Windows Application A creates a Child Task which
serves as the Agent for Windows Application D.
5. The Agent forwards the data to Windows Application D.
6. When Windows Application D responds, the ServerAgent D creates a Child
Window which acts as an Agent for Windows Application A. The response is
forwarded by the application to the Agent, which in turn forwards the data to
the ServerAgent for Application D.
7. The ServerAgent for Windows Application D routes the DDE data to the
DDEServer. The DDEServer determines which VDM this "DDE Packet" is des-
tined for and forwards it to the ServerAgent for Windows Application A.
2-4 VMBOOT
IBM Internal Use Only
Note
If two Windows Applications require significant amounts of DDE, these appli-
cations should be executed from within the same MAVDM, in this instance
the ServerAgent and DDEServer applications would not be required,
improving performance and usability.
2.5 OS/2 DDE Environment
Existing DDE support between PM Applications remains essentially unchanged.
DDE support between Windows Applications and Presentation Manager Applica-
tions requires that the DDEServer be linked with the Presentation Manager DDE
APIs, both DDE messages and data formats are translated during the data
exchange between the PM session and any given VDM running a Windows Appli-
cation. This process consists of a Protect Mode DDEServer, a Windows DDE
ServerAgent, as described above, and a PM DDE ServerAgent. The PM DDE
ServerAgent is a mirror to the Windows DDE ServerAgent. The ServerAgent is
responsible for routing all DDE messages beyond the confines of Presentation
Manager to the DDEServer. The ServerAgent communicates with the DDEServer
via named pipes.
The following data formats will be translated between the PM environment and
the Windows environment:
? Bitmaps: Windows DIB to/from OS/2 BITMAPINFO2 and PM BITMAPINFO
to/from Windows DIB format.
? Windows Device Dependent Bitmaps: Pre-Windows 3.0 format to Windows
DIB format to/from PM BITMAPINFO.
? Windows Metafiles: Metafiles are converted to Window DIB format prior to
being translated as above.
? Text: Codepage translation is provided in both directions.
The PM DDE ServerAgent will reside in a Productivity Folder as a Utility. Where
there is a demand to provide DDE support between PM Applications and
Windows Applications, the PM DDE ServerAgent should be placed in a
WorkPlace Startup Folder. The DDE ServerAgent runs ONLY as a minimized
icon. To shutdown global DDE, the PM DDE ServerAgent must be terminated
through the Window List.
Where DDE is only used between PM applications, the DDEServer should be
deactivated to improve performance.
Schematically the DDE process between PM Applications and Windows Applica-
tions may be represented as follows:
Dynamic Data Exchange (DDE) 2-5
IBM Internal Use Only
Figure 2-2. DDE Process PM and Windows.
�葺葺葺葺葺葺葺葺葺葙 �葺葺葺葺葺葺葺葺葺葺葺葺葙
� PM DDE Application� � Windows DDE Application �
�葺葺葺葺�葺葺葺葺葺� �葺葺葺葺葺葺葺葺葺葺葺??
�葺葺葺葺? �葺葺葺葺葺葺葺葺葺葺葺? �
� � DDE Initiate Message � �
� � or � �
� � DDE Conversion � �
� �葺葺葺葺?葺葺葺葺葺葺� �
� �葺葺葺葺葺葺葺葺莨葺葺葺葺葺葺葺? �
� �葺葺葺馆葺葺葺葺? �葺葺葺馆葺葺葺葺? �
�莼 DDE ServerAgent� � DDE ServerAgent谳?
�葺葺葺�葺葺葺葺? �葺葺葺�葺葺葺葺?
�莨葺葙 �莨葺葙
�Agent� �Agent�
�?葺? �?葺?
� �葺葺葺葺葺葺? �
�葺葺葺葺葺莼 Named Pipes谳葺葺葺�
�葺葺?葺葺葺�
�
�
�葺葺馆葺葙
�DDEServer�
�葺莨葺葺葺葺莨葺?
�Data Translation�
�葺葺葺葺葺葺葺葺�
2.6 Object Linking and Embedding (OLE)
Note
As at OS/2 Driver 6.163 OLE is not available.
Check to confirm whether OLE is planned for OS/2 2.0 or a later
release/upgrade
Object Linking and Embedding (OLE) focuses on document formats rather than
an application's ability to exchange data - the DDE approach. OLE defines a
format for compound documents, which contain multiple forms of data. The data
formats are understood and managed by multiple applications. The application
uses various combinations of data to construct a Compound Document.
The concepts used in OLE are best described by contrasting them with the
approach adopted by Clipboard and DDE.
When using the Clipboard, an application obtains data from another application
in a standard format, usually ASCII, a Bitmap or a Metafile. This data exists only
as data, there is no link with the application that originally placed the data in the
Clipboard.
When using DDE, an application also obtains data from another application in a
standard format, ASCII, Bitmap or Metafile. The Client can however establish
and maintain a link with the application that delivered the data. Should the data
change in the Server application, the Client application's data is also updated.
2-6 VMBOOT
IBM Internal Use Only
OLE also enables an application to obtain data from another application; in this
instance the data can be in two formats:
? One format is understood only by the application sending the data
? The Display format (ASCII, Bitmap or Metafile) for the receiving application to
display on the screen.
The significance of this approach may be appreciated by way of an example:
Voice annotation may be attached to a Word Processing application, the Word
Processing application need not have any facility to support or manage voice.
The Word Processor will store the data in two formats - the digitized sound and
a display format (an icon). When the icon is selected in the document, the Voice
application is invoked and the Word Processing application passes the digitized
sound to the Voice application, which then plays the sound.
Dynamic Data Exchange (DDE) 2-7
IBM Internal Use Only
2-8 VMBOOT
IBM Internal Use Only
3.0 OS/2 Clipboard Support
OS/2 V2 provides Clipboard support between Windows applications in the same,
or separate VDMs, as well as support between Windows Applications and OS/2
Applications.
The Clipboard serves as a data-exchange feature acting as a common area to
store data handles through which applications exchange formatted data. The
same data may be represented in a number of different formats as specified by
the application. Note that Clipboard objects may be of any size and format.
Data is formatted in either a predefined or private format, before being copied to
the Clipboard. In most cases the data is copied to pre-allocated global memory
and a function call is used to copy the memory handle to the clipboard.
Windows provides a number of predefined data formats:
TEXT Null-terminated text
OEMTEXT Null-terminated text using an OEM character set
METAFILEPICT Metafile-picture structure
BITMAP Device dependent bitmap
DIB Device independent bitmap
SYLK SYLK Standard data interchange format
DIF DIF standard data interchange format
TIFF TIFF standard data interchange format
The OwnerDraw feature in the Windows Clipboard is only supported within a
MAVDM, as shared memory is required. OwnerDraw is a process whereby a
Windows Application takes control over the appearance of menu items and has
responsibility for managing these menu items.
The native Microsoft Windows 3.0 Clipboard provides support for both Windows
applications and non-Windows applications. Non-Windows applications run in
either fullscreen or "windowed" mode. Windowed mode requires that Windows
run in 386 Enhanced mode, this mode is not supported under OS/2 V2. In REAL
or STANDARD modes, non-Windows applications run in fullscreen mode only.
386 Enhanced Mode is a mode which Windows 3.0 runs in to access the virtual
memory capabilities of the Intel 80386 processor, to use more memory than is
physically available and to provide multitasking capabilities for non-Windows
applications.
OS/2 V2 fully exploits the functions provided by the Intel 80386 processor, hence
there is no need to support this mode under OS/2 V2. Moreover, because DOS
applications may be run in a DOS Window (VDM), full Clipboard support is avail-
able.
Should the user wish to capture the contents of a VDM running in fullscreen
mode, the following approach is adopted:
1. Switch to the PM Screen containing the VDM
+ Copyright IBM Corp. 1991 3-1
IBM Internal Use Only
2. Select the System menu on the VDM icon
3. Select Copy All.
This procedure should copy the VDM's video buffer to the PM Clipboard (ASCII
or PM Bitmap).
Note
Selective Copy is available in window'ed mode
3.1 Windows Clipboard Support
The Windows Clipboard view utility will display the captured data in a number of
formats, either predefined or private. Auto displays the data in the format it had
when placed onto the clipboard.
The Clipboard Viewer program (CLIPBRD.EXE), installed in
C:\OS2\MDOS\WINOS2, is available within each SAVDM and MAVDM by default.
This is a modified version of the original Windows 3.0 Clipboard program.
A Clipboard Server (Global Clipboard) runs as a Protect Mode background
process to service clipboard functions between VDMs. If the Clipboard Server is
not executing, clipboard functions are limited to that single VDM. The global
VDM server is started from the CONFIG.SYS file at system boot:
RUN=C:\OS2\MDOS\WINOS2\VDMSRVR.EXE
Should a user elect to exit from the Windows Clipboard, a warning message will
be displayed advising that exit will terminate public clipboard functions. The
Clipboard functions within each VDM are public by default, unless expressly set
to LOCAL, which restricts Clipboard activity to that Windows session only.
The Windows Clipboard viewer pulldown menus have been enhanced to include
support for an Options Menu, which contains the Public Clipboard option.
Selecting this option causes changes to the Local clipboard to be reflected in the
Public clipboard and vice versa. When deselected the contents of the Public clip-
board and Local clipboard will not affect each other.
The File pulldown menu now supports Import/Export functions; PUBLIC must be
deselected from the Options pulldown menu before Import/Export can be
selected.
Implementation Notes
The Import/Export functions communicate via named pipes to the
\pipe\CLPAgent to the Clipboard program (CLIPBRD.EXE) within each VDM.
Export will copy the current contents of the Local clipboard to the Public clip-
board.
Import will copy the contents of the Public clipboard to the Local clipboard.
3-2 VMBOOT
IBM Internal Use Only
3.2 Using Cut and Paste
The following three scenarios describe the clipboard functions:
1. Cut and Paste from a Windows Application in a VDM to another application
in a separate VDM - PUBLIC is deselected.
2. Cut and Paste between two Windows applications within the same VDM
(MAVDM)
3. Cut and Paste between the OS/2 and Windows environments. Cut and Paste
within the OS/2 environment remains essentially unchanged.
3.2.1 Scenario 1 - Cut/Paste Between Windows VDMs
1. CUT the data into the Local Windows VDM Clipboard.
2. Select EXPORT from the Clipboard pulldown menu. The data is copied into
the External Clipboard.
3. Select the VDM containing the destination Windows application.
4. Select IMPORT from the Clipboard pulldown menu. The data is copied from
the external Clipboard into the local Clipboard of the receiving VDM.
5. Paste the data into the destination Windows application.
3.2.2 Scenario 2 - Cut/Paste Within A MAVDM
1. CUT the data into the Windows VDM Clipboard
2. PASTE the data from the Clipboard into the destination application.
3.2.3 Scenario 3 - Cut/Paste Between OS/2 And Windows
The OS/2 2.0 Clipboard is activated upon loading the Operating System. A new
OS/2 PM utility, CLIPVIEW.EXE located in the OS2\APPS\ directory has been pro-
vided to support the extended clipboard functions. CLIPVIEW.EXE must be
launched in order to view and transfer the contents of the OS/2 2.0 clipboard.
Excluding the File option of the Windows clipboard, the same pulldown menus
are provided. The RENDER option is the same as the DISPLAY option in the
Windows clipboard. RENDER will display the contents of the clipboard in a
number of different formats. Because the contents of the clipboard are stored in
separate areas in memory, it is possible to view both the ASCII (text) and
graphics contents of the clipboard.
Note
An application may or may not clear the entire contents of the clipboard,
prior to copying data to it.
The Global Windows VDM Clipboard (DPMI Clipboard) is visible to the PM Clip-
board. CLIPVIEW.EXE has been enhanced to perform the following two activities:
1. Update the PM Clipboard when changes are made to the Global VDM Clip-
board
2. Update the the Global Windows VDM Clipboard when changes are made to
the PM Clipboard.
OS/2 Clipboard Support 3-3
IBM Internal Use Only
The PM Clipboard server application is registered as "clipboard viewer" to
receive notifications of clipboard updates. This ensures that the following mes-
sages are forwarded to the Clipboard Server, so that when updates are made to
the PM Clipboard, messages are sent to the PM CLIPVIEW.EXE.
? WM_DESTROYCLIPBOARD: Signals that the contents of the clipboard are
being destroyed
? WM_DRAWCLIPBOARD: Signals an application to notify the next application
in the chain of a change to the clipboard
? WM_HSCROLLCLIPBOARD: Requests horizontal scrolling of the clipboard
contents
? WM_PAINTCLIPBOARD: Requests painting of the contents of the clipboard
? WM_RENDERALLFMTS: Notifies the owner of the clipboard that it must
render clipboard data in all possible formats
?
WM-RENDERFMT: Notifies the clipboard owner that it must format the last
data copied to the clipboard
? WM_SIZECLIPBOARD: Notifies the clipboard owner that the clipboard appli-
cation's window size has changed
? WM_VSCROLLCLIPBOARD: Requests vertical scrolling of the clipboard con-
tents.
Note
No changes have been made to the PM APIs to accommodate this design.
Data formats are translated from PM to Windows formats and vice versa, as and
when required. This translation is performed when data is placed in the Global
Clipboard. The following data formats will be translated between PM and
Windows:
?
Bitmaps: The Windows DIB to/from OS/2 BITMAPINFO
? Device Dependent Bitmaps: This is a pre-Windows 3.0 format to/from OS/2
BITMAPINFO
? Windows Metafiles: Metafiles are first converted to WINDOWS DIB format by
the Windows clipboard viewer, before being forwarded to the Global Clip-
board
? Text: ASCII with codepage translation will be translated in both directions.
Schematically the Clipboard process may be represented as follows:
3-4 VMBOOT
IBM Internal Use Only
Figure 3-1. .
�葺葺葺葺葺葺葺葺葺葺? �葺葺葺葺葺葺葺? �葺葺葺葺葙
�SAVDM Windows App 1.� �SAVDM - App 2.谳葺莼 Windows �
�葺葺葺?葺葺葺葺葺葺� �葺葺葺葺葺葺葺� �Clipboard�
� �葺?葺葺?
�葺葺葺莨葺葺葺葺葙 2. �
1. �Windows Clipboard� �
�葺葺葺?葺葺葺葺? �
�葺葺葺葺葺葺葺葺葙 �
(Named Pipes) � �
�葺葺葺葺莨葺葺葺葺葺葙 �
�DPMI Global Clipboard谳葺葺葺葺葺葺�
� Data Translation � (Named Pipes)
�葺葺葺葺?葺葺葺葺葺?
�葺葺葺葺葙 3. �
� OS/2 谳葺葺葺葺葺葺葺�
�Clipboard� (Named Pipes)
� Server �
�葺葺�葺葺�
� �葺葺葺葺葙 �葺葺葺葺葺葺葙
� � OS/2 谳葺葺葺?OS/2 PM �
�葺葺葺葺莼Clipboard� �Applications �
�葺葺�葺葺� �葺葺葺葺葺葺?
� �葺葺葺葺葺葺葙
�葺葺葺葺葺葺籚DM Window'ed�
�Applications �
�葺葺葺葺葺葺?
1. A Windows application (App.1) copies data to the Windows Clipboard.
2. The contents of the Clipboard are available to Windows App.2 via the Global
Clipoard (Clipboard Server).
3. The OS/2 Clipboard Server is registered as a Windows "Clipboard Viewer".
Data is translated into OS/2 formats via the DPMI Global Clipboard and vice
versa as required.
OS/2 Clipboard Support 3-5
IBM Internal Use Only
Figure Definitions
id File Page References
FIGDEF 3731SU
1-1
Table Definitions
id File Page References
TDEF 3731SU
1-1
Figures
id File Page References
3731WI2 3731WIN
3731DD1 1-5 1-1 3731DDE
2-4 2-1
3731DD2 3731DDE
2-6 2-2
3731CL1 3731CLIP
3-5 3-1
Headings
id File Page References
WIN 3731WIN
1-1 1.0, Microsoft Windows Applications
Processing Options
Runtime values:
Document fileid V2-WIN SCRIPT
Document type USERDOC
Document style IBMXAGD
Profile EDFPRF20 Service Level 0018
SCRIPT/VS Release 3.2.1
Date 91.10.15
Time 11:58:22
Device 3820A
Number of Passes 2
Index YES
SYSVAR G INLINE
SYSVAR X YES
Formatting values used:
Annotation NO
Cross reference listing YES
Cross reference head prefix only NO Dialog LABEL
Duplex YES
DVCF conditions file (none)
DVCF value 1 (none)
DVCF value 2 (none)
DVCF value 3 (none)
DVCF value 4 (none)
DVCF value 5 (none)
DVCF value 6 (none)
DVCF value 7 (none)
DVCF value 8 (none)
DVCF value 9 (none)
Explode NO
Figure list on new page YES
Figure/table number separation YES Folio-by-chapter YES
Head 0 body text Part
IBM Internal Use Only
Head 1 body text Chapter
Hyphenation YES
Justification YES
Language ENGL
Layout OFF
Leader dots YES
Master index (none)
Partial TOC (maximum level) 4
Partial TOC (new page after) INLINE
Print example id's NO
Print cross reference page numbers YES
Process value (none)
Punctuation move characters .,
Read cross-reference file (none)
Running heading/footing rule NONE Show index entries NO
Table of Contents (maximum level) 3
Table list on new page YES
Title page (draft) alignment RIGHT
Write cross-reference file (none)
Imbed Trace
Page 0 3731WIN Page 0 3731SU
Page 0 3731VARS
Page 1-10 3731DDE
Page 2-7 3731CLIP
Page 3-4 3731CL1
�
VMBOOT.DOC
IBM Internal Use Only
1.0 Virtual Machine Boot
IBM Internal Use Only
Draft extract from ITSC Red Book OS/2 Version 2 GG24-3731. Subject to
revision
1.1 VMB Overview
An important goal of OS/2 V2 is the ability to run past, current, and future PC
DOS programs; indeed most DOS applications available today run unchanged in
the MVDM DOS Emulation environment.
However, it should be remembered that the 﨑OS?which runs in this case is
highly optimized for (and specific to) an OS/2 V2 virtual 8086 machine. Because
of this, there are subtle internal differences between DOS Emulation and real
DOS. Unfortunately some DOS programs may be inherently bound to a specific
DOS version, relying on internal DOS structures or features not present in MVDM
DOS Emulation, such as internal DOS tables, LAN redirector hooks, or even
absolute routine addresses or undocumented features.
Another restriction of MVDM DOS Emulation is that only DOS character device
drivers can be loaded. The user may own a block device (often a special disk or
tape drive) for which no OS/2 driver is available.
Virtual Machine Boot allows the user to boot ff-the-shelf?DOS 3.x, 4.0, or 5.0 in
a VDM session, including DOS block device drivers. This gives the user the
greatest possible compatibility with PC DOS.
Another benefit of Virtual Machine Boot is the ability to run DOS of a different
National Language to that of OS/2 V2. This may be useful in a multilingual or
testing environment.
1.2 Virtual Machine Boot Environment
The 80386 processor and VDM component of OS/2 V2 together emulate a 8086
processor, keyboard, display, BIOS and other supporting hardware - a complete
virtual Personal Computer. So it shouldn't really be too surprising that eal?
DOS can run in a Virtual DOS Machine session. Control is passed to the boot
record (the first sector) of the DOS system diskette, which in turn loads and ini-
tializes the rest of the DOS kernel, just as it does when booting on a real PC.
Indeed the VDM environment is so like a real PC system that Virtual Machine
Boot can actually support any 8086 kernel, such as Digital Research DR-DOS and
1
CP/M, Microsoft MS-DOS, or even a PS/2 Reference Diskette . However, since
the purpose of Virtual Machine Boot is to run PC DOS applications, formal IBM
support is announced for IBM DOS 3.x, 4.0, and 5.0 only.
1 Do not attempt to run diagnostics or change the configuration from a VDM; the results are unpredictable.
+ Copyright IBM Corp. 1991 1-1
IBM Internal Use Only
Multiple DOS VDM kernels may be booted and operated concurrently. Each runs
in its own virtual 8086 session; access to hardware and other system resources
is managed by the underlying OS/2 V2 operating system.
1.3 Using Virtual Machine Boot
The booted DOS operating system can be:
1. An actual DOS system diskette
2. An image of a DOS system diskette saved to fixed disk
3. A DOS partition on fixed disk.
A Virtual Machine Boot session is created as a normal Program icon on the
OS/2 desktop. Here is an sample Program notebook page:
+-----------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-----------------------+
Figure 1-1. VMB Program parameters
Program title A suitable description
Path and filename * (actually ignored, but must be valid)
Optional Parameters (blank - ignored)
Working directory (blank - ignored)
The Session type may be DOS Fullscreen or DOS Window as desired.
1.3.1 DOS Startup drive
The difference from a normal DOS item is that the DOS Settings value 﨩ther:
DOS startup drive?is set. This contains the location of the DOS kernel to be
booted.
1-2 VMBOOT
IBM Internal Use Only
+---------------------------------------------------+
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+---------------------------------------------------+
Figure 1-2. DOS Startup drive
Example values for DOS startup drive are:
Startup setting Meaning
a: Boot the diskette in drive A:
c: bootimgdos33.vmb \ \ Boot the specified DOS image file
c: Boot the primary partition of the C: drive
Note:
? You cannot specify a second diskette drive (B:) or fixed disk (D:) as the
startup drive.
? To boot DOS from the C: partition, you must have Boot Manager installed,
and OS/2 V2 must reside in an extended partition on the first fixed disk, or
on another fixed disk. See 1.7, 﨎ooting a DOS partition?on page 1-9.
1.3.2 Virtual Machine Boot and 5?inch drives
You cannot specify 﨎:?or an external diskette drive as the startup drive. There
may be situations where you wish to boot a 5?inch diskette; often the B: drive
on PS/2 systems. One way to do this is by creating an image of the diskette,
then booting this image. (See 1.4, MDISK?on page 1-4.)
If a 5?inch diskette must be booted directly for some reason, this is possible if
drive remapping is supported by the system (such as a PS/2 Model 57, 90 or 95).
Normally A: is Drive 0 (3?inch), and B: is Drive 1 (5?inch, if fitted). To change
this, run et Startup Sequence?from the Reference Diskette, and ensure Drive
1 appears before Drive 0. Then the 5?inch drive will become the A: drive.
Some 5?inch drives (such as the IBM External 1.2MB drive and associated
adapter) require a device-driver, and are accessed as D: or higher. They cannot
be specified as a startup drive, nor can they be readdressed as A:, but can be
the source drive when creating a bootable image file.
Virtual Machine Boot 1-3
IBM Internal Use Only
1.3.3 Other DOS Settings
DOS Settings which control the VDM hardware environment are applicable to the
Virtual Machine Boot session and operate in the same way as for a DOS Emu-
lation window or fullscreen session. Those which modify the virtual DOS environ-
ment are ignored; these are instead determined by the CONFIG.SYS of the
booted DOS kernel. Ignored settings include:
? BREAK
?
DOS Device drivers
? DOS owns UMBs
? DOS SHELL
? DOS High / Low
? LASTDRIVE
? Simulated DOS version
The FCB limit is the lesser of either the booted DOS, or OS/2 V2 CONFIG.SYS
value. The Virtual Machine Boot session will by default have 640 KB of real
memory, mouse support, 2 MB Expanded (EMS) memory, 3 MB DPMI, and 2 MB
XMS memory.
In other respects the VMB session is no different to any other VIO window. It
may be minimized, maximized and switched between windowed and fullscreen
mode, and is subject to the same graphics limitations when windowed. The
session cannot be ended by typing exit at its command prompt. The session can
only be closed from its system icon or the Window List.
1.4 VMDISK
As already described, it is possible to boot from a diskette image which itself
resides on fixed disk. This image is created using the VMDISK utility supplied
with OS/2 V2. The syntax of the VMDISK command is:
vmdisk <source drive> <image filename>
For example:
vmdisk a: c:\bootimg\dos33.vmb
The image file is a complete binary ump?of the diskette, consisting of a short
header record followed by the diskette's boot sector, FAT(s), and all data clus-
ters. Its filesize corresponds to the source diskette capacity regardless of the
amount of space actually used on the source diskette. No compression of the
image is performed. The diskette must be of a normal DOS format (FAT, 512 byte
sectors). It is not possible to create, then boot, an image of a copy-protected
diskette which has a non-DOS format. It may be possible to boot such a diskette
directly in a VDM.
VMDISK can run under either DOS or OS/2, and supports all 3?inch (720KB,
1.44MB and 2.88MB) and 5?inch (360KB and 1.2MB) source diskette formats.
1-4 VMBOOT
IBM Internal Use Only
1.5 Drive letter allocation and access
This is one of the more complex area of Virtual Machine Boot. The following pos-
sible areas of confusion may arise for the user:
? If DOS is booted from an image file, it sees this image file as its A: drive.
This prevents access to the real A: diskette drive. Attempts to the write to the
apparent A: drive will fail.
? A DOS VDM cannot see an HPFS partition on the fixed disk.
? A DOS 3.x VDM cannot see a large (>32MB) FAT partition on the fixed disk,
or FAT partitions beyond HPFS.
?
Even if the booted DOS can otherwise see the fixed disk partition, it is only
given read access. Attempts to write will fail with simulated errors such as
. The 礼eneral failure writing drive C:? user might mistake this for genuine
hardware fault.
? If the booted DOS loads a block device-driver, the allocated drive letter may
be the same as that of a different device outside this VDM.
The results could be somewhat disorienting for the user. To help resolve these
issues, two utilities FSFILTER and FSACCESS are provided with OS/2 V2.
1.5.1 FSFILTER
FSFILTER.SYS is a device driver which manages DOS VDM access to OS/2 disks.
FSFILTER.SYS should be copied from the OS2MDOS directory to the DOS \ \
diskette, and the following statement added to the DOS CONFIG.SYS:
device=a:fsfilter.sys
This gives PC DOS full access to all OS/2 partitions - whatever the filesystem
type or partition size.
This is an important and somewhat surprising point. For example, DOS 3.3 (in a
VDM) has no problem accessing a 300MB HPFS partition, once FSFILTER is
loaded. I/O calls within the DOS virtual machine are passed transparently to
OS/2 V2. DOS itself is unaware of the underlying filesystem. DOS can read, write
and modify files on the fixed disk, and for most configurations the drive letter
mapping within the VMB session will match those of OS/2 V2.
Note
FSFILTER.SYS is loaded via CONFIG.SYS of the booted DOS, not the OS/2 V2
CONFIG.SYS. It should be preceed any statements which load block device=
device drivers.
The FSFILTER device driver occupies approximately 11KB of memory. It can be
loaded high (evicehigh=fsfilter.sys? under DOS 5.0.
Some operating systems may be confused by FSFILTER's actions during their
boot processing. For example the setting of the current drive or COMSPEC may
be invalid, or AUTOEXEC.BAT may not run. This has been noted with DR-DOS
and PC DOS 3.3 (but not 4.0 or 5.0). To avoid this problem specify the path to
COMMAND.COM in the SHELL= statement of CONFIG.SYS (as well as the
Virtual Machine Boot 1-5
IBM Internal Use Only
command processor itself). For example, if you cave copied DOS files to C: DOS,
\
the CONFIG.SYS of a diskette intended for VMB should contain a statement:
shell=c:\dos\command.com c:\dos /p
The first parameter specifies the comand procesor to load. The second param-
eter specifies the reload path (ie the COMSPEC path). This is preferable to a et
comspec= ...?line in AUTOEXEC.BAT.
1.5.1.1 FSFILTER limitations
Even when FSFILTER is loaded, the following restrictions still apply:
? A DOS VMB cannot see HPFS files or directories which have:
?long filenames (9 or more characters)
?invalid FAT characters (eg plus, comma, blank).
?multiple dot separators
? HPFS filenames containing lowercase letters are folded to uppercase.
? PC DOS commands which require low-level disk access will fail. These
include:
?CHKDSK
?SYS
?UNDELETE
?FORMAT
?UNFORMAT
?MIRROR
In such cases OS/2 V2 will simulate a disk error condition. DOS may inter-
pret this as a hardware fault, or report that the command is not supported on
a Network or Assigned drive.
1.5.2 FSACCESS
FSACCESS.EXE is a utility supplied with OS/2 V2 but intended to run in a Virtual
Machine Boot session. It cooperates with FSFILTER to manage drive letters
within the VMB session. This serves three purposes:
1. Drives may be registered for filtering.
2. The drive letter for a device can be changed, giving consistency across ses-
sions.
3. Letters can be removed in order to hide the OS/2 device from the VMB
session.
The syntax of the FSACCESS command is:
FSACCESS 葺葺葺葺葺葺�葺葺葺葺葺葺葺葺葺葺葺葺?葺葺?葺 .
谳�葺??DOSletter 葺葺葺? �
� � ! � �
谳葺葺?DOSletter - DOSletter 葺?
� �
�葺葺葺 DOSletter = OS2drive 葺�
FSACCESS lists the current drive mapping. For example:
1-6 VMBOOT
IBM Internal Use Only
Local C: is mapped to OS/2 C:
Local D: is mapped to OS/2 D:
Local E: is mapped to OS/2 K:
FSACCESS F: registers DOS letter F: for filtering. References to F: will be
sent to OS/2 V2.
FSACCESS !F: deregisters DOS letter F: from filtering.
FSACCESS F:-H: registers DOS letters F: through H: for filtering.
FSACCESS M:=C: registers DOS letter M: and routes requests to OS/2 drive
C:
Parameters can be combined on a single command line, and the colon is
optional.
1.5.3 Practical Considerations
? When booting from an image file, you will probably wish to issue the
command ? fsaccess a: ?in order to access the A: diskette drive.
?This will remove access to the image file, so the booted DOS will be
unable to reload its COMMAND.COM when necessary. You may wish to
copy all the DOS files to a subdirectory on fixed disk, ensuring the PATH
and COMSPEC point there.
An alternative is to access the diskette drive via a different letter. For
example, you can issue the command ? ,?then use G: to fsaccess g=a
access the real A: drive. The image file remains as A:, avoiding PATH
and COMSPEC problems.
?
FSACCESS error messages are contained in the OS/2 file OSO001.MSG,
which is in the OS2SYSTEM subdirectory. \ \ You should ensure that this file
is accessible to the booted DOS via its APPEND search path, otherwise an
FSACCESS error will only report that its message file cannot be found.
? Each block device driver loaded in DOS CONFIG.SYS is allocated the next
free OS/2 letter excluding LAN drives. This can result in a drive letter clash.
An example may illustrate the point. OS/2 drives are:
A: Diskette drive 0
B: Diskette drive 1
C: Fixed disk
D: External Diskette drive
E: Remote LAN drive on a Server
FSFILTER will ensure that a booted DOS sees these drives by the same
letter. The booted DOS has the same access to the external diskette drive
and LAN resources as does OS/2 itself. This is true whether the VMB
session is started before or after user Logon to the network, when remote
drive letters are assigned.
However, a VMB block device driver will also initialize as E:, so LAN drive
access is lost. To remedy this, issue an command. The LAN saccess f=e?
drive is now accessible as F: within the DOS session.
? If a Virtual Machine Boot session hangs for any reason, you can close it from
its system icon or the Window List. Remember that CTRL-ALT-DEL will
reboot OS/2, not the foreground virtual machine session.
Virtual Machine Boot 1-7
IBM Internal Use Only
Hint
Always give disk volumes a meaningful name - either when formatting or
later using the LABEL command. The name will remain constant and help
you identify where you are, even if the assigned drive letter is different some-
times.
1.6 XMS, EMS and MOUSE Support
The booted DOS receives XMS (HIMEM), EMS, DPMI and mouse support services
from its VDM environment (assuming the Virtual DOS Machine has default DOS
Settings). It should not load its own HIMEM, EMS or mouse drivers - indeed they
may cause errors in the VDM.
DOS programs call these services via appropriate API register parameters and a
designated Interrupt:
Mouse INT 33h
XMS INT 2Fh (multiplex)
EMS INT 67h
OS/2 V2 traps these interrupts from the virtual machine and handles the request
accordingly.
This may present a problem for certain programs which can use such services,
but first test for their presence by issuing an OPEN to the associated device-
driver, or check that a valid interrupt handler is pointed to by the Interrupt Vector
Table. When a VMB session is started, these device driver names are not
present, and the interrupt vectors point to null handlers. The application will
therefore assume that these services are not useable.
To resolve this, OS/2 V2 provides three alternative tub?drivers:
? MOUSE.COM
?
HIMEM.SYS
? EMM386.SYS
These stub drivers are very small (and use minimal memory when loaded) but
satisfy programs which depend on drivers with such names being present. They
also set handler addresses in the Interrupt Vector Table.
The user must load these OS/2 files rather than any similarly named files which
may be shipped with DOS or applications, such as:
DOS 4.0 XMAEM.SYS, XMA2EMS.SYS
DOS 5.0 HIMEM.SYS, EMM386.EXE, MOUSE.COM
Other MOUSE.SYS
There are two ways to achieve this. Assuming OS/2 V2 is installed on drive C:
Method 1 Copy the above OS/2 files from C: OS2MDOS to the DOS diskette, \ \
and edit CONFIG.SYS and AUTOEXEC.BAT accordingly to load these
files from the A: drive. VMDISK may then be run to create a bootable
image if desired.
1-8 VMBOOT
IBM Internal Use Only
device=a:fsfilter.sys
device=a:himem.sys
device=a:emm386.sys
Method 2 Edit CONFIG.SYS and AUTOEXEC.BAT to load these files directly from
C:OS2 \ \ MDOS. (FSFILTER must be loaded first if the OS/2 drive would
otherwise be inaccessible to the booted DOS).
device=a:fsfilter.sys
device=c:\os2\mdos\himem.sys
device=c:\os2\mdos\emm386.sys
The first method should be used if you wish to load FSFILTER high using DOS
5.0:
device=a:himem.sys
device=a:emm386.sys
devicehigh=a:fsfilter.sys
The second method has one notable advantage; if and when Corrective Service
is applied to the OS/2 V2 system, and HIMEM, EMM386 or MOUSE are updated,
you won't need to update your DOS diskettes and recreate image files. FSFILTER
itself will have to be updated manually (unless the OS/2 V2 partition is directly
accessible to your DOS and you load FSFILTER from here too).
Note: EMS memory size and frame location are determined by DOS Settings,
not parameters on the EMS386.SYS statement.
1.7 Booting a DOS partition
If you anticipate using Virtual Machine Boot regularly, the most convenient
method may be to do so from a DOS partition on the fixed disk, rather than via
diskettes or diskette images. A partition boot proceeds more quickly and offers
the user a more amiliar?working environment. Also, it is easier to apply DOS
Corrective Service to a disk partition than to diskettes or images.
The configuration requirements are:
1. Boot Manager must be installed
2. DOS must be installed on a primary partition on the first fixed disk
3. OS/2 V2 must be installed on an extended partition on the first fixed disk, or
on another fixed disk.
This will require repartitioning on single drive systems if the disk initially con-
taining DOS alone, or earlier versions of OS/2.
Note: This is not the same as a single partition with the Dual Boot feature.
To boot the DOS partition in a VMB session, enter the DOS Settings Startup
Drive parameter as 﨏:?
Virtual Machine Boot 1-9
IBM Internal Use Only
1.7.1 Configuration files
This particular setup presents one significant problem. The DOS partition is itself
bootable directly via Boot Manager, should the user so choose, and there may a
requirement to boot this DOS partition directly on occasions. The problem is: As
there is only one CONFIG.SYS and one AUTOEXEC.BAT in the C: root directory,
which drivers should be specified - DOS or OS/2 stub drivers?
If the partition is booted via VMB the DOS drivers are inappropriate.
If the partition is booted directly via Boot Manager the OS/2 stub drivers are
inappropriate.
It might appear that the user would have to maintain multiple configuration files
and rename or copy them according to the next desired boot type. This is clearly
rather unsatisfactory. Fortunately there is a solution which avoids this. The key is
to specify both sets of drivers in CONFIG.SYS and AUTOEXEC.BAT.
The following example assumes:
? DOS 5.0 is installed on the C: Primary partition
? OS/2 V2 is installed on the D: Extended partition
CONFIG.SYS on the C: drive contains:
device=c:\fsfilter.sys
device=c:\dos\setver.exe
device=c:\dos\himem.sys
device=c:\dos\emm386.exe noems
device=d:\os2\mdos\himem.sys
device=d:\os2\mdos\emm386.sys
dos=high,umb
... etc ...
When this file is processed under an OS/2 VMB, the DOS HIMEM load fails as it
sees no available Extended memory. EMM386.EXE cannot load as it sees protect-
mode software already running. Then, the OS/2 HIMEM and EMM386 stubs load
as normal.
When this file is processed as part of a native DOS boot, the DOS HIMEM and
EMM386 load as normal, but the OS/2 stubs realize they are not running under
OS/2 and do nothing.
A similar technique works for mouse support in AUTOEXEC.BAT:
@echo off
prompt 減済
set path=c:\dos
lh d:\os2\mdos\mouse
lh c:\dos\mouse
... etc ...
Note that here the OS/2 driver is listed first. When booting DOS native, the OS/2
mouse stub will realize this, and not load. Then the DOS mouse driver loads as
normal.
1-10 VMBOOT
IBM Internal Use Only
When this file is processed under OS/2 VMB, the OS/2 stub loads first. Then, the
DOS mouse driver sees that a mouse driver is already present, so does not
install itself.
Note: Unfortunately this technique cannot be taken too far. For example, you
may need to load IBM LAN Support Program drivers for the Token Ring adapter
(DXMxxMOD.SYS) files in your DOS CONFIG.SYS. If you already have sessions
using the Token Ring adapter (either OS/2 Extended Services or previously
started DOS communications) and then boot the DOS partition, its LAN device
drivers attempt to reinitialize the adapter. This will corrupt existing Token Ring
sessions.
1.8 Virtual Machine Boot Limitations
Virtual Machine Boot does not support:
? VCPI and other non-DPMI DOS extenders
? I/O to disk which bypasses the file system
? Feature adapter sharing without a virtual device driver
? Real-time or timing critical DOS applications
?
Some copy-protection schemes.
1.9 Available Memory
Table 1-1 shows the amount of available base memory for MVDM DOS Emu-
lation, DOS in a VMB session, and native DOS.
Table 1-1. Free Base Memory
Setting VDM DOS Emu- DOS 5.0DOS 4.0 DOS 3.3
lation
DOS low 610 KB 566 KB 588 KB 545 KB
DOS high 633 KB 612 KB - -
With mode728 KB 707 KB 653 KB 670 KB
restriction
(CGA)
Native DOS - 564 KB (low) 545 KB 562 KB
614 KB (high)
Note: Each configuration has HIMEM, EMS and Mouse drivers loaded. Values are approximate.
1.10 Customizing DOS
There is little point in loading the following in a booted DOS:
? Disk cache
? Print spooler
? RAM disk
These are better left to &OS2V2..
Do not configure EMS or XMS if the DOS session doesn't use them, as this can
impact the performance of the rest of the system.
Virtual Machine Boot 1-11
IBM Internal Use Only
1.11 Expanded Memory (EMS) and Upper Memory (UMB)
The following section applies to both VDM DOS Emulation and DOS Virtual
Machine Boot.
Expanded Memory Specification (EMS) is discussed in detail in -- Heading
'3731EMS' unknown --. One requirement of EMS is a page frame in real memory
between 640KB and 1MB (hex addresses X A0000 to X FFFFF). Since IBM ' ' '
'
systems reserve addresses X A0000 to X BFFFF for video, and X E0000 to ' ' ' '
' '
X FFFFF ' ' for BIOS, the EMS Page Frame is normally restricted to addresses
between X C0000 and X E0000 ' ' ' ' . This area can also be used for Upper Memory
Blocks, where DOS device drivers and resident programs can be loaded. This
frees up valuable space below 640KB for conventional DOS programs.
Unfortunately, memory between X C0000 and X E0000 is also needed for ' ' ' '
Option Adapter ROM and RAM. Indeed it can be difficult or even impossible to
configure EMS on a system which has several intelligent adapters installed.
There is really no solution to this problem (sometimes known as AM Cram?
under DOS. However OS/2 V2 provides an elegant alternative.
Normally a VDM inherits a memory map which mirrors the actual system hard-
ware configuration; adapter ROM and RAM addreses set by the PS/2 Reference
Diskette (or adapter switches on non Micro Channel systems) are mapped into
the VDM address space and are not available for EMS or UMBs.
But since the VDM occupies virtual memory this can easily be changed. The
DOS Settings value Other: Include Regions parameter releases adapter
addresses for use as EMS or UMBs. In most cases this can be set to the com-
plete X C0000-X DFFFF range. ' ' ' '
If a VDM uses an adapter directly (usually via DOS device drivers), any adapter
ROM or RAM address must not be specified in Include Regions. Addresses of
adapters used indirectly by the VDM (through OS/2 V2) may be included. For
example, the full X C0000 to X DFFFF ' ' ' ' range may be included on a
SCSI-based
PS/2, even though the SCSI adapter ROM may occupy X D8000 to X DFFFF. '
' ' '
The DOS VDM does not directly access the SCSI adapter so doesn't need SCSI
ROM mapped into its address space. It can still access files on SCSI disks via
the OS/2 V2 filesystem.
Note (** this may change **)
The Include Regions parameter should be entered as shown above, using
5-digit hex addresses (not 4-digit segment addresses, as is often the case).
Also, note that the range is inclusive - you must specify the second address
as (for example) X DFFFF, not X E0000 ' ' ' ' . The parameter is not
validity-
checked when entered. If an invalid parameter is saved, the default (no
include region) is used when the VDM is initialised; no error message is gen-
erated.
In summary, a typical DOS VDM may have a 64KB EMS page frame and 64KB of
UMBs (or 128KB of UMBs) regardless of the hardware adapters installed. Such a
configuration is not possible under PC DOS.
1-12 VMBOOT
IBM Internal Use Only
2.0 Index
A M
Adapter memory 1-12 MOUSE.COM. 1-8
B O
Block device driver 1-7 OSO001.MSG 1-7
Block device drivers 1-1
Boot Manager 1-9
P
PC DOS 1-1
C
COMSPEC 1-6
S
Settings (DOS) 1-4
D Stub drivers 1-8
DOS 1-1
DOS Image 1-4
U
DOS Settings 1-4 UMB 1-12
DOS Startup drive 1-2
Upper Memory 1-12
E
V
EMM386.SYS 1-8 VCPI 1-11
EMS 1-12
EMS. 1-8 Virtual Machine Boot 1-1
VMDISK 1-4
Expanded Memory 1-12
F X
XMS 1-8
FAT 1-5
FCB 1-4
FSACCESS 1-6 Numerics
FSFILTER 1-5 5?inch disks 1-3
H
HIMEM.SYS. 1-8
HPFS 1-5
I
IBM DOS 1-1
Include Regions 1-12
L
LAN 1-1
large partitions 1-5
+ Copyright IBM Corp. 1991 2-1
IBM Internal Use Only
Figure Definitions
id File Page References
FIGDEF 3731SU
1-1
Table Definitions
id File Page References
TDEF 3731SU
1-1
Headings
id File Page References
VMB 3731VMB
VMDISK 1-1 1.0, Virtual Machine Boot 3731VMB
1-4 1.4, VMDISK
1-3
BOOTPRT 3731VMB
1-9 1.7, Booting a DOS partition
1-3
3731EMS ?
? ?
1-12
Footnotes
id File Page References
REFDISK 3731VMB
1-1 1
1-1
Tables
id File Page References
FREEMEM 3731VMB
1-11 1-1
1-11
Processing Options
Runtime values:
Document fileid VMBOOT SCRIPT
Document type USERDOC
Document style IBMXAGD Profile EDFPRF20
Service Level 0018
SCRIPT/VS Release 3.2.1
Date 91.10.15
Time 10:42:52
Device 3820A
Number of Passes 2
Index YES
SYSVAR G INLINE
SYSVAR X YES
Formatting values used:
Annotation NO
Cross reference listing YES Cross reference head prefix only NO
Dialog LABEL
Duplex YES
IBM Internal Use Only
DVCF conditions file (none)
DVCF value 1 (none)
DVCF value 2 (none)
DVCF value 3 (none)
DVCF value 4 (none)
DVCF value 5 (none)
DVCF value 6 (none)
DVCF value 7 (none)
DVCF value 8 (none)
DVCF value 9 (none)
Explode NO
Figure list on new page YES
Figure/table number separation YES
Folio-by-chapter YES
Head 0 body text Part Head 1 body text Chapter
Hyphenation YES
Justification YES
Language ENGL
Layout OFF
Leader dots YES
Master index (none)
Partial TOC (maximum level) 4
Partial TOC (new page after) INLINE
Print example id's NO
Print cross reference page numbers YES
Process value (none)
Punctuation move characters .,
Read cross-reference file (none)
Running heading/footing rule NONE Show index entries NO
Table of Contents (maximum level) 3
Table list on new page YES
Title page (draft) alignment RIGHT
Write cross-reference file (none)
Imbed Trace
Page 0 3731SU Page 0 3731VARS
Page 0 3731VMB
�