Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- CA-Clipper/ExoSpace 1.0g - <b>compatibility note</b> http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
 Compatibility Note
------------------------------------------------------------------------------

     The protected-mode DOS extender technology on which CA-Clipper/ExoSpace
     relies is supplied by Rational Systems, Inc., a leader in protected-mode
     technology.  Many commercial applications that run in protected mode
     rely on this Rational Systems technology, including applications from
     Lotus, IBM, Quarterdeck, Borland, Symantec, and Watcom.  Such
     applications should successfully coexist with CA-Clipper/ExoSpace
     applications.

     However, when running other protected-mode applications alongside
     CA-Clipper/ExoSpace applications, it is possible that the first
     CA-Clipper/ExoSpace application which starts up may reserve all
     available extended memory, unless it is running under a DPMI host, a
     VCPI host, or an XMS manager.

     Without a memory manager, if you try to start up a protected-mode
     application that was not built with CA-Clipper/ExoSpace after your
     CA-Clipper/ExoSpace program, the non-CA-Clipper/ExoSpace application
     will not find any extended memory available.

     There are several ways to avoid this problem:

     .  Use a memory manager whose protocol both programs adhere to.

        CA-Clipper/ExoSpace follows the DPMI, VCPI, and XMS protocol.  If the
        other program also follows one of these protocols, the memory manager
        will ensure that the programs properly share memory.

     .  Start the non-CA-Clipper/ExoSpace application first.

        If the non-CA-Clipper/ExoSpace, protected-mode application reserves
        only the memory that it needs, the CA-Clipper/ExoSpace program uses
        extended memory that the first does not reserve.

     .  Use the DOS16M environment variable to limit the amount of
        memory that the CA-Clipper/ExoSpace application can use.

        For example, to limit the CA-Clipper/ExoSpace application to 1 MB,
        use this setting:

        SET DOS16M= :1M

     .  Use the DOS16M environment variable to set the range of memory
        that CA-Clipper/ExoSpace uses.

        If you can specify a range of memory for the non-CA-Clipper/ExoSpace
        application, you may be able to establish a private range for each
        application, so that they do not conflict.  The DOS16M environment
        variable allows you to specify a range for the CA-Clipper/ExoSpace
        application.

        For example, if you can make your non-CA-Clipper/ExoSpace application
        utilize addresses from 1 MB to 2 MB, you can specify the memory from
        2 MB to 3 MB for CA-Clipper/ExoSpace.  To specify this range of
        memory, use one of these settings in your DOS16M environment
        variable:

        SET DOS16M= @2M - 3M
        SET DOS16M= :1 @2M

        If setting a range in the DOS16M environment variable does not solve
        the problem, remove the setting.


Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson