IBM Q&A on 1.2.

 Q1. Please describe the key enhancements to Standard Edition.

A1. Key enhancements to Standard Edition include the Dialog Manager available in OS/2 Programming Tools and Information V 1.2 which is designed to      operate with both Editions, as well as Presentation Manager enhancements. The Dialog Manager is a tool that controls the interactions between a      dialog application and a user. Also included in Standard Edition are:

Desktop Manager/File Manager: An enhanced user interface for adding, starting, and manipulating programs and files.

High Performance File System: An optional replacement for the File Allocation Table (FAT) based file system which can handle files and partitions up to 2 gigabytes in size. The HPFS is designed to provide improved performance over the FAT based file system. Compatibility between files created by both file systems is maintained for OS/2 programs and programs running in OS/2's compatibility mode.

Online Programming Technical Reference: An "electronic book" available in the OS/2 Programming Tools and Information V 1.2.

Online Command Reference: An "electronic book" that describes OS/2 command usage and syntax.

Dual Boot Utility: Allows both OS/2 and DOS to load from the same fixed disk drive.

Generic Printer Control Language Device Driver: Included with Version 1.2 to support printers compatible with the HP* Laserjet* and Laserjet II* series.

Windowable System Editor: An editor is provided which is written to the Presentation Manager interface. This allows it to share the display with other Presentation Manager programs.

DOS Compatibility Improvements: IBM DOS 4.0 support for greater than 25 lines mode display and support for additional video modes of PS/2 displays are now available in DOS compatibility mode.

Q2. IBM recently admitted that OS/2 wouldn't be complete until Version 1.2 was available. However, there appear to be many elements which are still needed to complete OS/2. Is this gradual release to market intentional?

A2. OS/2 Standard Edition 1.2 is a completely functional operating system and all planned function is available in it. We are always striving to      improve our products, respond to new customer requirements, and meet the needs of changing technology. As such, the product will continue to      evolve.

Q3. Have you done anything to make OS/2 easier to use?

A3. We have implemented a Desktop Manager in Version 1.2 to further enhance usability of the graphical user interface to the operating system functions such as adding applications, starting applications, associating files to applications, and switching between applications. We have also included an Online Command Reference which provides the user with an      "electronic book" that describes OS/2 command usage and syntax.

Q4. Why has IBM waited until now to provide the dual boot feature on OS/2 when it has been available from Microsoft in the past?

A4. IBM has chosen to offer this feature at this time because the solution implemented needed to be consistent with the strategic plans and immediate functional content of IBM OS/2.

Q5. Will there be a separate Device Support Supplement diskette as there was in 1.1? What will it contain? When will it be available? How do I get it?

A5. All device drivers delivered with Version 1.1 either with the product or      with its Device Support Supplement will be packaged and shipped with the Version 1.2 base operating system. IBM Operating System/2 Standard Edition Version 1.2 does not have a Device Support Supplement diskette as      did Version 1.1. This includes the "Null" device driver delivered with the Device Support Supplement for use by applications that choose not to      use the advanced facilities provided by the Presentation Manager.

Q6. Specifically, what device drivers will be included with OS/2 Standard Edition Version 1.2? What printers will the drivers support?

A6. IBM OS/2 Standard Edition Version 1.2 will include a generic Printer Control Language device driver that supports printers compatible with the HP* Laserjet* and Laserjet II* series. A PostScript (R) driver is also included which will allow applications to output PostScript to the IBM Personal Page Printer II and to other printers with PostScript capabilities. Also included is an Epson device driver that supports devices compatible with Epson FX8O and LQ1500 series of wire matrix printers. Finally, Version 1.2 has the capability to separately install device drivers if needed.

Q7. When will the Printer Control Language device drivers for printers compatible with the HP* Laserjet* and HP Laserjet II* printer series be      available?

A7. The Printer Control Language device driver will be available in January, 1990.

Q8. How do I get the Printer Control Language device driver?

A8. Details on ordering the Printer Conrol language device driver will be      available at a later date.

Q9. Does the Post Script device driver contained in IBM OS/2 Standard Edition Version 1.2 support any other printers besides the IBM Personal Page Printer II?

A9. The Post Script device driver in IBM OS/2 Standard Edition Version 1.2 is      code that was delivered by Microsoft was part of the Joint Development Agreement between IBM and Microsoft. Microsoft has indicated that the device driver should support other similar devices that can accept this type of data stream.

Q10. Why isn't Procedures Language announced in Extended Edition available in      Standard Edition?

A10. Our current plan is to ship it only with EE since EE is the OS/2 SAA Platform Product.

However, we are evaluating market requirements for including it with SE.

Q11. Why is there an UPDATE in November, just two months after product GA?

A11. There are always functions IBM believes are beneficial to customers that are not available at the time of our planned release. These functions will be available to licensees via an UPDATE package available November 30, 1989.

Q12. What is contained in the November UPDATE?

A12. The File System will be enhanced to preserve the case of the filename when the file is created or renamed. Utilities will be enhanced to allow for a space and other special characters to be imbedded with quoted filenames.

Q13. How do I get the November UPDATE?

A13. Contained in the product package will be the appropriate registration card. To receive the UPDATE, the customer need only complete and mail the card.

Q14. Will long filenames and/or case preservation of filenames cause any incompatibilities or any programs not to run?

A14. File naming conventions and enhancements added to the HPFS have been implemented in a very open fashion. Users will be able to continue to      use file naming conventions used by the FAT file system. Case preservation simply returns a filename in the same case as it was entered. Filenames are not case sensitive in any other way. When moving files from the HPFS to FAT file systems, the names used for the FAT file system files may have to be changed to conform to FAT rules. No change will be required to go the other way. Usability testing as well as      customer requirements have demanded more flexibility in file naming.

Q15. Does OS/2 Version 1.2 Presentation Manager provide WYSIWYG plotter support?

A15. Generally speaking, OS/2 1.2 provides WYSIWYG. However, plotter reverse clipping is not supported. This means that pictures with overlaying areas and lines will draw all overlays, not just the top overlay. OS/2 1.2 Presentation Manager also does not support image plotting.

Q16. Why are there no COBOL or FORTRAN bindings for the Interactive Presentation Facility API?

A16. IBM has, as its first priority, decided to concentrate an offering COBOL and FORTRAN bindings to those parts of the Presentation Manager that have already been announced as part of the SAA Presentation Interface.

Q17. What are the benefits of Version 1.2 to software developers? End users?

A17. Software developers will benefit from the programmer productivity improvements of the Dialog Manager. COBOL and FORTRAN bindings will allow programmers who use those languages to write to the Dialog Manager interfaces as well as the interfaces of Presentation Manager. New Presentation Manager programming examples are useful to programmers moving to Presentation Manager. Programmers will also benefit from the Online Technical Reference included in the OS/2 Programming Tools and Information Kit.

These and other valuable tools for the developer are found in the new OS/2 Programming Tools and Information V1.2 offering.

End users will benefit from performance improvements of the High Performance File System and the usability enhancements that come with the Desktop Manager/File Manager and productivity of the Windowable System Editor.

Both programmers and end users will benefit from the new Online Command Reference and "electronic book" that describes OS/2 command usage and syntax.

Q18. Are DOS files created by standalone DOS compatible with the High Performance File Systems (HPFS)?

A18. Compatibility is only maintained within OS/2 and between OS/2 and DOS compatibility mode of OS/2. Files created by HPFS cannot be accessed from standalone DOS 3.3 or DOS 4.0. Files created by standalone DOS 3.3 or 4.0 cannot be accessed by the HPFS on OS/2, either. Files created by      standalone DOS are accessed by the FAT-based file system on OS/2.

Q19. Can you give me some performance comparisons between the FAT-based file system and the High Performance File System?

A19. The High Performance File System is designed to provide extremely fast access to very large disk volumes. The HPFS' performance over the FAT file system is especially evident under the following conditions (for any      I/O):

o  Very busy disk (lots of small files being updated) o  Large number of subdirectory levels o  Very large files o  Large hardfile partitions.

The High Performance File System has multiple levels of caching and uses intelligent write-behind logic--this allows it to find/open files much faster than the FAT file system. The Higher Performance File System is      less performance sensitive as file sizes and/or directories get very large.

Actual performance data has not been assembled at this time.

Q20. Is DOS 4.0 fully supported in DOS compatibility mode?

A20. No. Only as stated above. The DOS shell and EMS specifically are not supported.

Q21. Please describe the key enhancements to the Presentation Manager.

A21. Key enhancements to the presentation Manager in Version 1.2 are:

Cut and Paste Improvements: Text may now be cut or copied from text only screens and subsequently pasted into windows of Presentation Manager applications programmed to accept such text.

Font Sizes: When using the 8514/A display adapter, new font sizes are available for programs that emulate terminals so that appropriate font sizes for the terminal may be used.

Picture File Utilities: Utilities are now available to print and display metafiles and convert picture files to metafiles.

COBOL/FORTRAN Bindings: Applications may be written in COBOL or FORTRAN and can use the Presentation Manager.

Q22. I recently received a copy of the new SAA/CUA Advanced Interface Design Guide. Why are the figures in that book visually different from those in      OS/2 Standard Edition 1.2?

A22. Changes to the visual appearance of the OS/2 interface were made after the publication of the SAA/CUA Advanced Interface Design Guide. We      believe that these changes represent a significant enhancement to the appearance of the OS/2 interface. The OS/2 programming interfaces support these visual enhancements and should be used when developing applications. As CUA evolves, these visual enhancements will be      incorporated in the figures.

Q23. Have the memory requirements for OS/2 Standard Edition 1.2 changed from the 1.1 version?

A23. Minimum storage requirements have remained the same: 2Mb, 2.5 Mb when configured for both OS/2 and DOS applications.

Q24. Will Version 1.2 participate in the memory promotion?

A24. Yes, the promotion applies to OS/2 Version 1.2.

Q25. What are the RAM and DASD requirements of Standard Edition Version 1.2?

A25. RAM: OS/2 Standard Edition V1.2 requires a minimum of 2 Mb of memory for running OS/2 applications or a minimum of 2.5 Mb of memory for running OS/2 and DOS applications. The actual amount of memory required is a      function of the working set requirements of the operating system and the application. There are scenarios that require significantly greater amounts of memory and DASD storage. Under OS/2 Standard Editon 1.2 maximum memory available to DOS applications has increased by      approximately 30K.

DASD: The minimum size hardfile on supported systems is 20 Mb.  IBM publishes planning information for memory and DASD in a guide--IBM Operating System/2 Information and Planning Guide (G360-2650). You should consult it for your specific requirements.

Q26. What is a Dialog (as referred to in Dialog Manager)?

A26. A dialog is a sequence of interactions between an application and a user. A dialog application is the set of elements that support the work performed by a user. The Dialog Manager is a tool that controls the interactions between a dialog application and a user.

Q27. Would you explain a little about the Dialog Manager and how it relates to      the Presentation Manager? When and by whom should each be used? Are there any benefits to using one over the other?

A27. The Dialog Manager is a development facility with which a developer can efficiently implement application dialogs that take advantage of      Presentation Manager functions, including the capability of being windowed. The Dialog Manager invokes the Presentation Manager to perform presentation services. It is more limited than the Presentation Manager because it does not provide for the use of graphic primitives available in the Presentation Manager.

As Dialog Manager is a programmer productivity aid, it may be used if the application is primarily text based, ISPF structured or structured in      COBOL or FORTRAN, and is not planned for conversion to graphical data presentation.

If the application will require graphical data presentation or multifont text or will require context sensitive user interaction, or will be      written in "C", Presentation Manager should be used.

Dialog Manager provides the capability to directly invoke Presentation Manager via user controls so if the application requires Presentation Manager primitives, you may still be able to take advantage of the productivity features of OS/2.

Q28. Can the Dialog Manager runtime facilities be redistributed? Without charge?

A28. There are no charges associated with redistributing the Dialog Manager runtime facilities. The Dialog Manager runtime facilities may be      redistributed with Dialog Manager applications developed within the redistributor's company. If, however, the Dialog Manager runtime facilities are to be marketed outside the redistributor's company, IBM will require a redistribution agreement without fee.

Q29. What are the "significant elements of the interface" in the OS/2 Dialog Manager?

A29. The OS/2 Dialog Manager provides the necessary functions to implement CUA compliant applications. The Dialog Tag Language for programmable workstations and the supporting set of the runtime services are provided to handle display of panels and messages. The elements (verbs) are: DMOPEN/DMCLOSE, DISPLAY, ADDPOP/REMPOP, and VCOPY/VDEFINE/VDELETE/VREPLACE/VRESET. The OS/2 Dialog Tag Language Guide and Reference and OS/2 Dialog Manager Guide and Reference will describe the facilities and verbs provided.

Q30. Will the Microsoft "developer's tool kit" contain the Dialog Manager that is in IBM OS/2?

A30. Under the Joint Development Agreement, IBM has made the Dialog Manager available to Microsoft. Microsoft should provide the definitive answer to this question.

Q31. If I write an application using the IBM OS/2 Dialog Manager, will my      application run on Microsoft OS/2?

A31. The IBM OS/2 Dialog Manager is an enabling tool written to the standard OS/2 APIs. These APIs are preserved between IBM OS/2 and Microsoft OS/2. As such, any program written to these APIs will run on either operating system.

Q32. What is the relationship of the new Presentation Manager enhancements to      the current lawsuit between Apple and Microsoft?

A32. We are not a party to the lawsuit. We take necessary steps to ensure we      do not infringe on anyone else's intellectual property. This is true for all of our products, not just OS/2. We have not changed our plans as a      result of the lawsuit.

Q33. Will OS/2 1.2 be serviced in the same way as 1.1?

A33. Yes.

Q34. Is OS/2's default end user interface, as implemented with Presentation Manager, fully CUA compliant?

A34. The default end user interface is CUA compliant. If there are any differences from current CUA Advanced Interface Design Guidelines, they will be documented in product documentation.

Q35. In light of Microsoft's alliance with DCA on a communication server, are you still doing joint development work with MS on SE?

A35. Absolutely.

Q36. What is your relationship with Microsoft?

A36. We consider Microsoft an outstanding business partner.

Q37. Will Microsoft announce Standard Editon 1.2?

A37. Microsoft will have to answer that question.

Q38. Are their any architectural limits enforced in 1.2 that were not enforced in 1.0/1.1?

A38. Not specifically, however, OS/2 Release 1.2 does use slightly more stack space that may cause problems for applications that did not observe the recommended stack size of 4K bytes.

Q39. Why were ISV's told to ensure they are using at least a 4K stack?

A39. The recommended minimum stack available when making a call to an OS/2 function is 4K bytes. This size is necessary to accommodate current and future needs of applications. Some of the OS/2 functions are implemented such that they use the stack of the application.

Q40. How many applications are currently available for OS/2?

A40. There are currently over 600 applications available. �

