by @Macarlo
Team OS/2 Registered
Screenshots by registered Embellish

READ ALSO
What is the Best Corel Draw for OS/2 Warp?

 Hi All.
Have you any problem with WinOS2 after the FixPak13 install? I'm running just fine WinOS2 on my Warp Client 4.5 and his performance has increased with this Fix. Before FP13, using FP12, some applications was using 30 per cent of CPU (Pentium 200) resources; now, these applications are running with 15/20 per cent of CPU usage. I'm running seamless.

Click here to see Fractal Design running on Warp 4.5 (100KB)

Click here to see Opera Browser working on @Macarlo's Warp 4.5

Comment on this article
by Arjen Meijer

My observation is that FP13 enforces the device drivers rules more strictly than ever.
For example FP13 breaks some device drivers, like eicon diva PCMCIA drivers version 6.01. Version 6.03 works fine.
The WinOS2 problem is most likely due to incorrect sound drivers. The 100% CPU usage is likely to be a incorrect processing of the exit
list of ...the sound drivers.
Mwave drivers are a example of corrupted drivers in FixPack 13. REM out the drivers and OS/2 works fine. With the drivers, OS/2 is a disaster.
My two cents.

Photo above shows WordPerfect 6.0 running Artistic Text on @Macarlo's Warp 4.5

 I received dozens of e-mails from scared OS/2 users reporting "serious troubleshooting"during WinOS2 applications use on Warp Client 4.5 (Warp 4.0 + FP13). Some of these users are Matrox customers. After the FixPak13 install, said these users, WinOS2 can't run in seamless mode, only in full screen mode; and after the WinOS2 use, with this Windows emulation closed, these users reported that have received a colored full screen trap notice "made by IBM", reporting a device driver problem.
Easy, men! This problem in reality is not serious and you can solve it following these steps:
1)Jump Matrox web site (http://matrox.com) and sucks os2_231.zip (1.06MB), the zip file that contains Matrox OS/2 PM Display Driver Version 2.31.100 for the Matrox G400 MGA Millennium/Mystique MGA-G100/MGA-G200 (released at 26-Aug-1999);
2)Unzip the compressed file into a /temp directory and save the zip file in a secure place for future use;
3)Boot you machine and at the Blue Screen Options (Recovery Choices) press F3 in order to reset the primary video driver to VGA;
4)Jump to the /temp directory where you was unzipped the file, search for /os2_231 subdirectory, click install.cmd and follows the instructions. That is all. Reboot you PC and the problem is solved.
5)Now you can works fine on Warp 4.5 using all applications you have installed on your WinOS2, like me.
Note that OS/2 Warp have hundreds applications for all purposes and that you, in reality, don't need to use WinOS2. I'm using OS/2 since the firsts versions because when I decided join to the eremite's life as a monk of Saint Benedict Order I needed a decent environment in order to write, illustrate, format and print colored books about Theology and Esoterism.

Photo above shows Aldus Page Maker 5.0 running on @Macarlo's Warp 4.5

During some years I made these books in Latin and Portuguese language in order to make my bread. At this old time Aldus was innovated desktop publishing with his first version of Page Maker, a release that runs just on OS/2 Presentation Manager as a native application! OS/2 was created at 1987 by Microsoft and IBM, but Bill Gates decided increase his Windows project and at May 22, 1990 released Windows 3.0. Gates obtained his first billion dollars with Windows and Aldus discarded new Page Maker releases for OS/2. IBM added Windows emulation on OS/2, creating WinOS2, and I joined it in order to follow making my books. When Warp 3.0 was released, I decided discard WinOS2 graphics applications and replaced Adobe Photoshop and Corel Draw by Embellish. With the Warp 4.0 arrival I migrated from the paper to the web and no more used WinOS2. But I have a nice tab with WinOS2 applications in my Object Desktop Professional Launchpad, as you can see in the screenshots here, all made by Embellish registered in BMT Micro, Inc. Actually my principal web site have above 4,000,000 html pages and above 3,000,000 images and I works on OS/2 Warp 4.5 using Boxer text editor by David Hammel and Netscape 4.61 by Mike Kaply and his team, both embedded on Larsen Commander by Leif-Erik Larsen. Originally I used HomePagePublisher by Jean-Bernard Clerin but now I'm using the most recent HTML code, with advanced Forms and all templates was created by Namo Web Editor on Windows NT environment. At this time the only WinOS2 that I need everyday is the dictionary DIC (Brazilian-English/English-Brazilian) that runs just fine on my OS/2 Warp 4.5 in seamless mode, as a native OS/2 applications, with absolutely insignificant CPU usage!!!

 Photo above shows DIC dictionary running seamless on @Macarlo's Warp 4.5

Product Description

This OS/2 PM driver for the Matrox G400, MGA Millenium, MGA Mystique, MGA-G100 and MGA-G200 video accellerator chips supports 8-bit (256 colors), 16-bit (64K colors), and 24- and 32-bit (16M colors) display modes under OS/2 2.11 and later, in resolutions ranging from 640 x 480 to 2048 x 1536.

Driver Installation

To install the software, follow the procedure below:

   1. If you have previously configured OS/2 for another graphics card, then
      you should uninstall the drivers for that card.  Be sure that OS/2 will
      start up in VGA mode before installing the Matrox Drivers.

   2. Using the Command Prompts folder of OS/2, open an OS/2 Window or Full
      Screen session.

   3. Insert the driver disk in a floppy drive (if you are installing from
      the floppy disk) or insert the CD-ROM in its drive bay.

   4. Make the CD-ROM or floppy disk the active drive and type:

      "SRCPATH\INSTALL",

      where SRCPATH is the path which contains the Matrox OS/2 drivers.

      Examples:

      A:\INSTALL     (if installing from a diskette with OS/2 only)
      A:\OS2\INSTALL (if installing from diskette with OS/2 and NT)
      D:\OS2\INSTALL (if installing from a CD-ROM)

      Note: if you install this driver to a Warp System, you may run

      \INSTALL /U       for all but Japanese OS/2
        or
      \INSTALL /UJ      for Japanese OS/2 (DBCS driver disk only)

      and everything will be installed without any further input from the
      user (primary, secondary selection, driver selection, and source
      disk/path selection).

   5. You will see a dialog box in which you can select the Primary Display.
      Choose "Matrox G400, Millennium/Mystique/MGA-G100/MGA-G200 Series".  You
      may have to change the source drive if you are not installing from drive
      A.

   6. The installation program will then proceed with the installation.  When
      it is complete, you will have to shut down your system in order for the
      MGA driver to take effect.

If you haven't previously installed a high-resolution driver, OS/2 will restart
in Matrox default resolution (640x480x256).  If you know which resolutions your
monitor is capable of displaying, you may wish to configure the driver for your
monitor and/or a different resolution before shutting down.  To do this, use
the MGA Settings notebook, as explained in the next section.  However, if you
do this before shutting down, some resolutions shown by the MGA Settings
notebook may be invalid, and, if you select one of those, OS/2 will restart in
a different, valid resolution instead.

Note:  If you are using Selective Install in OS/2 Warp, the Matrox G400,
MGA Millennium/Mystique/MGA-G100/MGA-G200 driver shows up as "Other."

Driver Configuration

To change the driver monitor configuration or mode (resolution or pixel depth),
use the following procedure:

   1. Double-click on the MGA Settings icon on the desktop.

   2. Select the Monitor tab and either select Use Display Data Channel (if
      available) or choose your monitor from the list provided.

   3. Select the Resolution tab and choose the resolution/pixel depth.

You will need to reboot the system to see the change take effect.

Uninstalling the Driver

The Matrox UNINSTAL command file makes use of the OS/2 DSPINSTL.EXE program
to switch the display driver from MGA mode back to VGA mode, as shown in the
following procedure:

   1. Open an OS/2 Text Window (or Full Screen) session.

   2. Enter:  CD \MGA\OS2

      UNINSTAL
      or
      UNINSTAL CLEAN (to also delete the Matrox files from your hard disk)

   3. Once the MGA driver has been uninstalled, the DSPINSTL utility will
      launch.  Select Primary Display, then choose the driver you require (for
      example, VGA).

You will need to reboot the system to see the change take effect.

Note:  With Warp, there are two additional ways to switch the driver from MGA
mode to VGA mode:

  1. You can access a menu by pressing Alt+F1 when the OS/2 logo appears
     in the upper left corner of the screen during the bootup process.
     This menu will allow you to change the driver to VGA by selecting
     the appropriate option.

  2. You can also change the driver to VGA by running the following program
     in an OS/2 window or full screen session:

              SETVGA

Driver Reinstallation

To reinstall the same level Matrox driver as was previously installed, run
DSPINSTL.  Select the primary display as in installation step 6 above.  Change
the source drive to \MGA\OS2 (on your boot drive), and then press the Install
button.  When DSPINSTL finishes, shut down and reboot.

Monitor Customization using Matrox's MGA Settings Notebook

The OS/2 Matrox G400/Millennium/Mystique/MGA-G100/MGA-G200 driver supports
VESA DDC-2B compliant monitors.

If your monitor is not detected as DDC compliant, the driver will take the
"Unknown Monitor" hardcoded timings, which assume that you have a monitor
supporting all resolutions available on your board at a 60Hz refresh rate
(non-interlaced).

If you have a monitor that is capable of refresh rates higher than 60Hz, you
should change the monitor setting on the Monitor page of the notebook.  If your
monitor is not listed, try to choose a similar monitor or one of the standard
monitors.  MGA Settings then creates a file called MGA.INF, which contains the
appropriate video parameters for your monitor.  The MGA.INF file is read by the
MGA display driver when OS/2 boots.

The MGA settings notebook is located in the System Setup folder, described
below.

You must shut down OS/2 and reboot your computer for the changes to take
effect.

Note:  The timing information in MGA.INF overrides the timing info returned by
DDC compliant monitors.  If you are using a DDC compliant monitor, and you do
not wish to override the monitor's timing info, then check the "Use Data
Display Channel (DDC)" box.

Driver configuration using the MGA settings notebook

Advanced configuration of the MGA driver can be performed through the MGA
settings notebook, located in the System Setup folder and shadowed on the
desktop.

Fonts page:

   You may change font settings for the current resolution, and they will be
   remembered if you switch resolutions.  You may change font resolution and
   the system font using the Fonts page.  To change the default AVIO font, open
   an OS/2 or DOS Window, select Font Size from the system menu, select the
   desired font, and click the Save button.  Your selection will be stored when
   you exit the MGA settings notebook.  Note that this is not supported with
   the DBCS driver.

   Font resolution affects the sizes of your OS/2 fonts.  The system font is
   the default font and also affects window sizes.  On Warp 4, the WarpSans
   font is used for window titles and menus.  On previous OS/2 versions, the
   window titles and menus use the default font.  If you want to change this,
   you may drag any font from the Font Palette to any window title or menu bar
   while holding the Alt key.

   Note that the default values for the fonts are:

                System Font           Font res  AVIO Font
    640x480     10.System Proportional   96        8x14
    800x600     10.System Proportional   96        8x14
   1024x768     10.System Proportional  120       12x22
   1152x864     12.System Proportional  120       12x22
     or higher

Advanced page:

1. Grayscale driver switch

   Owners of the Millennium PowerDoc Edition may enable the grayscale driver
   switch, which defines whether 8 bits per pixel should be in 256 colors or
   256 gray shades.

2. DIVE switch

   Due to an OS/2 problem in 32 bpp, the Warp Digital Video player image
   may be shifted to the left.  24 bpp may trap under certain conditions.

   The MGA Settings notebook has a switch to ensure DIVE is always enabled in
   24 and 32bpp.  Note that when the box is not checked, DIVE will still be
   used in some cases where no problems were found to occur with OS/2 Warp 3
   with FixPak 17 installed.

3. EnDIVE switch

   If you wish to enable/disable EnDIVE support, use the EnDIVE switch.

For all changes you make with the MGA setttings notebook, except for hot key
changes, you must reboot your computer to see the changes take effect.

Driver configuration using MGACONF.CMD

1. Cursor Vsync

   The cursor may exhibit some "noise" when an application changes the color
   palette.  This switch forces to wait for a Vsync before changing the
   palette.  The drawback is a loss of speed when changing the palette.  Some
   animated application requires fast changing palette.  This switch applies
   only to 8 bpp.  The problem occurs only on the Millennium card.

   mgaconf v 0      (off)
   mgaconf v 1      (on)

   Default is 1.

2. Color cursor

   mgaconf c [0/1/2],

   where 0 will enable the software cursor (multicolor cursor)
         1 will disable the software cursor (you will have 2 or fewer colors
           in the cursor)
         2 will disable the software cursor if the cursor has fewer than 4
           colors

   Default is 0.

File description

Assume: <S> -> Source path
        <D> -> Destination drive (OS/2 system drive).
        <W> -> WinOS/2 or Windows path (\os2\mdos\winos2 or \windows)

<S>\INSTALL.CMD     --> stay where it is.
<S>\FIXAUTO.CMD     --> <D>:\MGA\OS2
<S>\UNINSTAL.CMD    --> <D>:\MGA\OS2
<S>\MGAX64.OS2      --> <D>:\MGA\OS2\SYSLEVEL.MGA
   (pack file)          <D>:\MGA\OS2\MGAX64S.DSP
                        <D>:\OS2\DLL\PMGAX64.DLL
                        <D>:\OS2\DLL\BMGAX64.DLL
                        <D>:\MGA\OS2\KMGAX64.SYS
                        <D>:\OS2\MDOS\VMGAX64.SYS
                        <D>:\MGA\OS2\MGASET.EXE
                        <D>:\MGA\OS2\MGASET.DLL
                        <D>:\MGA\OS2\MGASET.HLP
                        <D>:\MGA\OS2\MGAHK.EXE
                        <D>:\MGA\OS2\MGA.MON
                        <D>:\MGA\OS2\MGACONF.CMD
                        <D>:\MGA\OS2\MGAOBJ.CMD
<S>\MGAX64W.OS2     --> <W>:\SMGAX64.DRV
   (pack file)          <W>:\MGAX64.DLL
<S>\MGAX64.DSP      --> stay where it is.
<S>\VVGA.SYS        --> <D>:\MGA\OS2 and <D>:\OS2\MDOS
<S>\SCREEN01.SYS    --> <D>:\MGA\OS2 and <D>:\OS2
<S>\MGAX64.DSC      --> <D>:\OS2\INSTALL
<S>\README.OS2      --> <D>:\MGA\OS2

MGAX64.DSP      installation support file for "dspinstl" (for first install)
MGAX64S.DSP     installation support file for "dspinstl" (for re-install)
MGAX64.DSC      installation support file
MGAX64.DLL      initialization library for Win-OS/2 fullscreen
BMGAX64.DLL     Base Video Handle (sets VGA for OS/2 fullscreen)
PMGAX64.DLL     32bit PM driver (8, 16 and 32bpp)
KMGAX64.SYS     low-level initialization for 32bit PM driver
SMGAX64.DRV     Win-OS/2 Fullscreen and Seamless driver
VMGAX64.SYS     Virtual MGA driver (for DOS sessions)
VVGA.SYS        Modified IBM VGA virtual driver.
SCREEN01.SYS    Modified IBM system device driver.
README.OS2      Readme file
INSTALL.CMD     first time installation
MGASET.EXE      MGA Settings notebook
MGASET.DLL      MGA Settings notebook text strings
MGASET.HLP      MGA Settings notebook help
MGAHK.EXE       hot key trapping applet
MGACONF.CMD     Configuration utility for PM driver
FIXAUTO.CMD     inserts "SET MGA=x:\MGA\OS2" in autoexec.bat (Win-OS/2)
UNINSTAL.CMD    uninstalls driver (and optionally removes all Matrox G400,
                Millennium/Mystique/MGA-G100/MGA-G200 files from hard drive)
MGA.MON         MGA Monitor data file for MGA settings notebook
SETUP.EXE       Monitor program to create MGA.INF out of MGA.MON
SYSLEVEL.MGA    driver Version info
                (use OS/2 command syslevel.exe to obtain the driver Version)
MGAOBJ.CMD      MGA object installation

Known bugs and limitations

The following bugs and limitations are present in this release of the
driver:

· When using the DSPINSTL program to reconfigure your MGA driver, the program
  states that VGA is the current driver.  This is because the DSPINSTL program
  included with OS/2 does not correctly identify the Matrox G400,
  Matrox Millennium/Mystique/MGA-G100/MGA-G200.

· The MGA PowerDesk Windows drivers should NOT be used in a Win-OS/2 full
  screen session.  The results will be highly unpredictable.  If the MGA
  windows driver features are absolutely needed, then a dual-boot configuration
  must be used.  When booting from DOS, the PowerDesk Windows driver features
  are fully supported.

· The driver does not work with Mayo Clinic Family Health Book (Windows app.)
  in seamless Windows at 16bpp (64K colors).  If you need to run this
  application, please run it in Win-OS/2 fullscreen instead or change the
  colors to 256 or 16M.

· It is necessary to shut down all Win-OS/2 sessions prior to installing the
  driver.  Make sure the "Fast load" option in Win-OS/2 Setup (in the System
  Setup folder) is not checked, and close Win-OS/2 Setup prior to install.
  Otherwise, required Win-OS/2 files will not be copied, and install will fail.

· Using the large OS/2 system font on OS/2 2.11 causes some text in the MGA
  settings notebook to be cut off.  This is due to an OS/2 bug in the font
  spacing.

· Selecting a scalable font as the OS/2 system font on OS/2 2.11 and Warp 3
  without a FixPak does not work correctly.  A system proportional font is used
  instead.  You can obtain a list of scalable fonts by opening the Font
  Palette, pressing the Edit Font button, and pressing the Delete button.
  In the Delete Font window, any font with file extension OFM is a scalable
  font.  Warp 3 FixPak 17 is known to fix this problem.

· Using MGA Settings to select the OS/2 system font is not supported with the
  DBCS driver.

· When using higher than 1280x1024 resolution, if you use MGA Settings to
  change the monitor setting to a monitor which does not support the current
  resolution, you must shut down the system prior to switching to a full screen
  session.  Otherwise, the system will hang when switching back to the desktop.

@Macarlo, Inc.
@Macarlo's Shareware & Web
OS/2
Java Lobby Member
Java Site Accredited

[TOP] [HOME] [INDEX]