2. Port Your DOS, UNIX and VMS Applications

Converting to 32-bit

Because this version of Vermont Views runs as a native 32-bit GUI application, some features of Vermont Views Plus are no longer supported and must be either removed or rewritten. This section describes the necessary changes.

If you are not using the MemEx extensions to create a 32-bit extended program under DOS, you will need to make sure that your application is 32-bit compliant and takes into account the differences in the size of data types when in 32-bit mode. Pay particular attention to the use of the data type integer, which is 32 bits under Win32.

MemEx

Vermont Views for Windows runs as a 32-bit application with a flat memory model. It is no longer necessary to use a DOS extender to obtain extended memory support.

GraphEx

Vermont Views for Windows runs as a native GUI application. Additional work is no longer required to display Vermont Views forms and menus in graphics mode. Because of the change in operating systems, however, the code you wrote to display any graphical information will need to be rewritten using native Windows API functions, or another third-party graphics library.

In addition, the GraphEx functions listed in Table 5-1 are not functional in Vermont Views for Windows and are ignored.

Table 5-1: GraphEx Functions Ignored in Vermont Views for Windows

  • csr_enable()
  • vid_hibg()
  • vs_vertq()
  • sw_vidpage()
  • vid_int()
  • wn_gset()
  • vid_adapter()
  • vid_setmode()
  • wn_gunset()
  • vid_cgabdr()
  • vid_usemode()
  • wn_reset()
  • vid_ega()
  • vid_vga50()
  • wn_zap()
  • vid_getmode()
  • vs_horzq()
  

Mouse Functions

Because the mouse is an integrated part of the environment, it is neither necessary nor recommended that you use the functions that deal specifically with the mouse:

mou_hide()

mou_show()

Home Contents Previous Next