KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q50715: Executing QuickC Under Windows Operating Environment

Article: Q50715
Product(s): See article
Version(s): 2.00 2.01
Operating System(s): MS-DOS
Keyword(s): ENDUSER | S_QUICKASM | mspl13_c
Last Modified: 17-JAN-1990

Question:

When I execute QuickC 2.00 from the Windows environment, the mouse
cursor does not appear on the screen. The cursor does appear when I am
in the Windows environment. Is there a problem with the mouse in
QuickC 2.00 when executing from a Windows program?

Response:

No. The Windows operating environments (Windows 286/386) have an
internal mouse driver available to Windows operating
environment-specific programs. QuickC 2.00 and 2.01 require the mouse
driver supplied with QuickC 2.00 and 2.01 to be loaded.

Since the mouse driver in the Windows environment is internal, only
programs written specifically for the Windows environment can use the
Windows mouse driver. All other DOS applications will have to load a
mouse driver through DOS.

If you have MOUSE.SYS, then in your CONFIG.SYS file, add the
following:

   device=c:\mouse.sys

If you have a MOUSE.COM, then type "mouse" at the DOS prompt or add
the following line to your AUTOEXEC.BAT file:

   mouse

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.