Notes about Mouse Support
 About mouse support.
──────────────────────────────────────────────────────────────────────────────

 We are aware of some problems with getting a mouse to work in large screen
 text modes. This problem will arise with any program that you run in a large
 text mode, such as 132 columns by 43 rows etc. The following should help you
 to resolve any problems that you might have with getting MrDebug to run with
 a mouse in a large text mode.

 By default, we have set the Use Mouse option to off - so that you are not
 greeted with garbage on the screen - the sign of a mouse driver limitation.

 Mouse drivers that have VESA compatibility modules, such as Logitech seem to
 work just fine in large text screen modes - as long as you have a VESA
 compliant video card and the VESA mouse extensions loaded.

 You will know whether your mouse driver does not work properly in large text
 modes by the annoying garbage that you get on the screen when you move the
 mouse, after enabling it.

 Our tests lead us to conclude that any video mode greater than 40 Decimal,
 28 Hex, will cause this problem to surface, in text mode.

 Please Note - these problems have not been experienced under an OS/2 DOS
 session.

 Should you still have problems getting the mouse to work with MrDebug and
 your screen becomes garbled when you move the mouse try the following:

 1. Refer to your video card hardware documentation for a text video mode for
    a large text screen number in hexadecimal, for example, the Cirrus Logic
    CL542X has support for 132 text columns by 43 text rows, which is mode 54
    in hexadecimal.

 2. Create a text file that contains the following text:

        n test.com      
        a 100           
        MOV ax, 00<n>   
        INT 10          
        MOV ax, 40      
        MOV es, ax      
        MOV di, 0049    
        MOV al, 3       
        STOSB           
        INT 20          
                        
        rcx             
        12              
        w               
        q               


    where <n> on the third line is the video mode that you wish to use, in
    the case of the Cirrus Logic 542X is 54 ie. MOV ax, 0054    

 Please note that although the above is not case sensitive, the placement of
 the blank line is very important - so don't remove it.

 3. Save the file as HELPMRD.DEB

 4. At a DOS Prompt type:

        DEBUG < HELPMRD.DEB

 This will create a small TEST.COM program that you may run before MrDebug to
 set the video mode and mouse up for use with MrDebug. In most cases this
 will cure the problem of garbage on the screen - if only we could do this
 for our code!

 Phew....glad that's outta the way - what trouble we had there...