1. AS59099V2_0.zip Driver
2. tctomsc.txt File Contents

tctomsc.txt Driver File Contents (AS59099V2_0.zip)

==============================
Porting DevUtil from TC to MSC
=========================1.1==

****************************** Inportment **********************************
This documents contains information about how to port the AXIOM DAS DEVICE
UTILITY from Turbo C 2.0 to Microsoft C 7.0. We believe that you are already 
familiar with the Microsoft C environment, and are familiar with making a C
library and managing a project with both Microsoft C linker and compiler.
If you are not, please refer to your programming language user's guide and 
language reference.
****************************************************************************


I. INTRODUCTION
II. WHAT'S THE DIFFERENCE?
III. WHAT TO DO AND WHAT HAVE DONE?



I. INTRODUCTION
---------------
   AXIOM DAS DEVICE UTILITY (DevUtil) is build up with the Borland Turbo C 2.0 
   (TC) compiler. Though the compiled binary files are not compatible with the
   Microsoft C compiler, the source code is full compatible with both compilers,
   which means you can make up your own binary object code with either TC or
   MSC compiler.
   
   As mentioned in the readme file of DevUtil, 'README.TXT', there are two parts
   of DevUtil that implement this utility 
     
      AXDDU - Source code of AXIOM DAS Device Utility(DevUtil).
      AXDDR - Source code of AXIOM DAS Device Driver.
      
   You can use the compiled binary files for either TC or MSC located under the
   different sub-directories, '\TC', or 'MSC'. Otherwise, with souce code 
   provided, it is easy to re-compile the binary code with either TC or MSC by 
   yourself.
   
    
      
II. WHAT'S THE DIFFERENCE?
--------------------------
   Since the utility is optimized for best use with TC compiler, there are lots
   of converting works done by simulating some TC functions with MSC compiler.
   They are 

   void textcolor(int);
   void textbackground(int);
   void textattr(int);
   void clrscr(void);
   void clreol(void);
   int bioskey(int);
   void gotoxy(int,int);
   int wherex(void);
   int wherey(void);
   void sleep(unsigned seconds);
   void delay(unsigned millisecinds);
   int gettext(int,int,int,int,char*);
   int puttext(int,int,int,int,char*);
   void window(int,int,int,int);

   These functions are not available in MSC but are called by DevUtil with TC. 
   Thus, to provided such function calls for DevUtil, the simulating functions
   are implemented in 'TC2MSC_x.OBJ', which could be found under directory 
   '..\AXDDR\MISC\MSC'. Include the necessary object files when needed.
   

III. WHAT TO DO AND WHAT HAVE DONE?
-----------------------------------
   For users who only want to call the device driver(AXDDR), the pre-compiled
   binary files will be ready to use, and can be found under the sub-directory 
   '\MSC'.
   
   If you want to build the device utility(DevUtil) by yourself with MSC, a lot 
   of work should be done manually.
   
   1. For AXDDR- The driver library, 'AXDDRM_L.LIB', for DevUtil is available 
      for MSC, or you may want to re-build with MSC 'LIB' command by your own
      self.
      
   2. For AXDDU- The devutil utility kernel library, 'AXDDUM_L.LIB', will be
      found under the sub-directory, '\MSC'. And the additional associated 
      include file, 'TCTOMSC.H', will also be found in the same working 
      directory as 'DRV.C', '\AXDDU'. Use the DOS command prompt batch file, 
      'playmsc.bat', to compile and link the project files.
      
   3. Don't forget to add the object files, 'MISC*.OBJ', and 'TC2MSC*.OBJ',
      into the AXDDR library, if you decided to make your own library.