Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- Proclip2 Library - Norton Guide http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]

                      - Cautions, Warnings & Compatibility -
     ------------------------------------------------------------------------

                          - Environment Compatibility -

     Some of the functions contained in PROCLIP2 assume they are operating in
     an IBM (or 100% compatible) system utilizing DOS 2.xx or greater, OS/2
     in "real" mode or Microsoft Windows.  What this means is that they will
     access the ROM BIOS or perform DMA (direct memory access) from time to
     time to perform specific functions or obtain information regarding the
     current system environment.  As long as you are using an IBM (or 100%
     compatible) with the proper version of DOS you should experience no
     difficulties.

                            - Monitor Compatibility -

     PROCLIP2 is intelligent enough to determine the current monitor type and
     treat it accordingly.  This includes Monochrome, Color Graphics (CGA),
     Enhanced Graphics (EGA) and Video Graphics (VGA) monitors in either
     native or emulated modes.  Those functions which offer DMA video buffer
     updating should be tested on the system prior to releasing it for use.
     These functions are again assuming they are operating in an IBM-type
     environment and so they "know" where the video buffer currently resides.
     DMA updating is useful when operating in personal computers which have a
     clock speed slower than 8MHz.  If one of the screen functions appears to
     be operating sluggishly try attempting the DMA update request specified
     in the function.

                             - Memory Compatibility -

     Some functions within PROCLIP2 require a temporary allocation of memory
     from the system.  If this allocation is not possible the function will
     refuse to function.  The typical allocation request is less than 1Kb
     (1024 bytes) so no real conflict should exist.  Once memory has been
     allocated and used by PROCLIP2 it will be returned to the system memory
     pool for use by other programs or DOS.  PROCLIP2 will not attempt to
     allocate any memory outside of the standard 640Kb limit.


                      - System / BIOS dependent functions -

     Some functions are dependent upon system level functions or internal
     BIOS interrupt vectors.  These functions, when active, have the ability
     to "hang" the computer if a serious error occurs in the system.
     PROCLIP2 will intercept DOS level critical errors before DOS is made
     aware of them and make every effort to restore any interrupt vectors or
     system functions to their previous state before passing the error to DOS
     for handling.  This feature of PROCLIP2 is unique to PROCLIP2 as it
     requires no additional coding or intervention on your part.  When a
     function is activated which depends on interrupt or system vectors (eg.
     CLOCK) it will automatically create the "hook" into the DOS critical
     error handler.  Should a critical error occur all PROCLIP2 functions
     which are using interrupt or system vectors will be deactivated by
     PROCLIP2.



.

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