Oemsetup.inf Driver File Contents (CyrixMGMxNT-3_1-95.zip)

; Microsoft Windows 3.1 Device Development Kit (DDK)
; Sample OEMSETUP.INF File for Windows 3.1
; Copyright 1992 Microsoft Corporation
; ---------------------------------------------------------------
;
; This file demonstrates what a display driver installation diskette would
; look like for all of the display drivers included with Windows 3.1.
; The diskette would contain this OEMSETUP.INF file and all of the files
; referenced by it, e.g. DRV, 2GR, 3GR, 386, FON, LGO, RLE, etc.
;
; The OEMSETUP.INF file should be kept on the driver installation diskette.
; If you write a driver installation program, this must not copy any files 
; to the Windows directory or System directory.  Windows Setup is the 
; "gate-keeper" of the contents of the these directories!  It knows how to 
; resolve naming and version conflicts.  Only Windows 3.1 Setup should be
; used to install Windows display drivers.
;
; Also, do not modify or replace the SETUP.INF file in the Windows 3.0 or
; 3.1 System directory.  This is very important!  Windows 3.1 Setup will 
; copy and rename the OEMSETUP.INF file to the System directory.  The 
; display selections in the OEMSETUP.INF file will then be included in
; the Windows Setup display list the next time it is run to change the
; display type.
;
; All files on the driver installation disk (except for OEMSETUP.INF)
; can be compressed using the COMPRESS.EXE utility in the Windows 3.1
; Software Development Kit (SDK).  Both versions of Setup, 3.0 and 3.1,
; can expand files compressed using COMPRESS.EXE.
;
; See Chapter 14 of the DDK Device Driver Adaptation Guide for detailed 
; information about the OEMSETUP.INF file and complete information about
; creating driver installation diskettes.  Also, Microsoft Developer Support
; is qualified and ready to assist with the creation of driver diskettes,
; you are encouraged to contact them via your accounts if you have any
; questions or problems.
;
; When you have completed your OEM driver disk, test it rigorously.
; Be sure to test Windows 3.1 Custom Installation, MS-DOS and Windows
; maintenance modes for switching drivers, and the "keep current driver"
; vs. "install new driver" features.
;
; If you use this file to create your own OEMSETUP.INF file, please do
; not ship these comments, and remove any driver listings and sections 
; that are not necessary for your product.


; VERSION INFO
; ---------------------------------------------------------------
; This tells Setup that this is a 3.1 compatible OEM driver disk.
; Setup will not attempt to translate VDD and logo file name requests
; to their new equivalents on Windows 3.1 diskettes.

[data]
    Version   = "3.1"   


; DRIVER DISKS
; ---------------------------------------------------------------
; Here is the list of disks that Setup can prompt for.  Note that the 
; Windows Setup disks are not referenced!  All necessary files must be on 
; your  driver disk, even those that are equivalent to 3.1 files, such as 
; fonts and logos.
;
; You should include the brand and model name, if possible, in the
; disk name.  Be specific, it is important that users not confuse your
; disks with Windows disks.  Windows Setup prompts the user to "insert
; the:", so your disk name should be of the following form:

[disks]
    a =., "Cyrix Gx86 Windows 3.1 Driver Disk", diska


; DISPLAY TYPES
; ---------------------------------------------------------------
; Specify the complete list of display types, colors, and resolutions
; available in this section.  Some tips...
; 
; Profile:              This must be a unique identifier.
;
; Description:          No more than 47 characters!  Include all necessary info.
;                       This description string should change slightly in new versions
;                       of your driver disk.  Include a version id, and keep the rest 
;                       of the string the same, e.g. "ACME Z-1000 v1.1 640x480, 256 colors".
;
; VDD:                  Don't reference *vddvga!  This file uses "vddvga.386" instead,
;                       which can be built using the DDK source files.
;
; Work section: This is new to 3.1, and optional.  See below for details.

[display]
;profile = driver,         Description of driver,                           resolution,    286 grabber,    logo code,       VDD,            386grabber,   ega.sys,   logo data,    optional work section
;
gx31a    = a:gx31.drv,     "MediaGX, 640x400 256 colors",                            "100,96,96",   a:vgacolor.2gr, a:vgalogo.lgo,   a:gxvdd.386,    a:vga.3gr,,              a:vgalogo.rle, gx31a     
gx31b    = a:gx31.drv,     "MediaGX, 640x480 256 colors",                            "100,96,96",   a:vgacolor.2gr, a:vgalogo.lgo,   a:gxvdd.386,    a:vga.3gr,,              a:vgalogo.rle, gx31b     
gx31c    = a:gx31.drv,     "MediaGX, 800x600 256 colors",                            "100,96,96",   a:vgacolor.2gr, a:vgalogo.lgo,   a:gxvdd.386,    a:vga.3gr,,              a:vgalogo.rle, gx31c     
gx31d    = a:gx31.drv,     "MediaGX, 1024x768 256 colors",                           "100,96,96",   a:vgacolor.2gr, a:vgalogo.lgo,   a:gxvdd.386,    a:vga.3gr,,              a:vgalogo.rle, gx31d     
gx31hca  = a:gx31hc.drv,   "MediaGX, 640x400 64K colors",                            "100,96,96",   a:vgacolor.2gr, a:vgalogo.lgo,   a:gxvdd.386,    a:vga.3gr,,              a:vgalogo.rle, gx31hca     
gx31hcb  = a:gx31hc.drv,   "MediaGX, 640x480 64K colors",                            "100,96,96",   a:vgacolor.2gr, a:vgalogo.lgo,   a:gxvdd.386,    a:vga.3gr,,              a:vgalogo.rle, gx31hcb     
gx31hcc  = a:gx31hc.drv,   "MediaGX, 800x600 64K colors",                            "100,96,96",   a:vgacolor.2gr, a:vgalogo.lgo,   a:gxvdd.386,    a:vga.3gr,,              a:vgalogo.rle, gx31hcc     
gx31hcd  = a:gx31hc.drv,   "MediaGX, 1024x768 64K colors",                           "100,96,96",   a:vgacolor.2gr, a:vgalogo.lgo,   a:gxvdd.386,    a:vga.3gr,,              a:vgalogo.rle, gx31hcd     


; OPTIONAL WORK SECTIONS
; ---------------------------------------------------------------
; Optional sections listed in field 9 of the display section are interpreted as follows:
;
; File, Destination, .ini file, Section, LHS, RHS
;
; Where:    a:File      = Optional file to be copied; may be left null.
;           Destination = 0: for windows root or 0:system for \system subdir.
;           .ini file   = Optional; any .ini file to be modified or created.
;           Section     = Section of .ini file to be modified.
;           OldLine     = Optional old line to be removed from the ini file.
;           NewLine     = New text line to be written with the .ini file.
;
; There is no standard syntax for display drivers to determine user options.
; Note that the 8514 driver uses "dpi=" from the [8514.drv] section, and
; TIGA uses "tigafont=" in a [tiga.drv] section.  However, Setup now writes
; the font resolution (e.g. "100,96,96") to the "aspect=" line of the 
; [boot.description] section of SYSTEM.INI.  This can be used by all drivers 
; to determine the correct screen resource size to use, instead of inventing
; your own flag name and values.
;
; In addition to supporting different font resolutions, the Video Seven driver
; demonstrates multiple screen resolutions in a single driver.  The "WidthXHeight"
; line of the [v7vga.drv] section tells the driver what mode to run.


[gx31a]
,,system.ini,gx31.drv,"Xres=","Xres=640"
,,system.ini,gx31.drv,"Yres=","Yres=400"

[gx31b]
,,system.ini,gx31.drv,"Xres=","Xres=640"
,,system.ini,gx31.drv,"Yres=","Yres=480"

[gx31c]
,,system.ini,gx31.drv,"Xres=","Xres=800"
,,system.ini,gx31.drv,"Yres=","Yres=600"

[gx31d]
,,system.ini,gx31.drv,"Xres=","Xres=1024"
,,system.ini,gx31.drv,"Yres=","Yres=768"

[gx31hca]
,,system.ini,gx31.drv,"Xres=","Xres=640"
,,system.ini,gx31.drv,"Yres=","Yres=400"

[gx31hcb]
,,system.ini,gx31.drv,"Xres=","Xres=640"
,,system.ini,gx31.drv,"Yres=","Yres=480"

[gx31hcc]
,,system.ini,gx31.drv,"Xres=","Xres=800"
,,system.ini,gx31.drv,"Yres=","Yres=600"

[gx31hcd]
,,system.ini,gx31.drv,"Xres=","Xres=1024"
,,system.ini,gx31.drv,"Yres=","Yres=768"


; 386 GRABBER FONTS
; ---------------------------------------------------------------
; Setup will copy these fonts, sometimes called "old app fonts",
; depending on the 386 grabber being used.  If you use your own
; 386 grabber, then you should be sure to specify a section with
; your grabber name.  You only need sections that correspond to 
; 386 grabber names in the [display] section.

[VGA.3gr]
a:CGA40WOA.FON,a:CGA40850.FON
a:CGA80WOA.FON,a:CGA80850.FON
a:EGA40WOA.FON,a:EGA40850.FON
a:EGA80WOA.FON,a:EGA80850.FON


; SYSTEM FONTS
; ---------------------------------------------------------------
; Fonts are installed according to the resolution of the display type selected.
; Your OEMSETUP.INF file must have these sections, with all font resolution lines 
; appropriate for the listings in the [display] section.  Note that the HELVx.FON
; from Windows 3.0 is now SSERIFx.FON; TMSRx.FON is now SERIFx.FON.

[sysfonts]
a:egasys.fon,"EGA (640x350) resolution System Font", "133,96,72"
a:vgasys.fon,"VGA (640x480) resolution System Font", "100,96,96"
a:8514sys.fon,"8514/a (1024x768) resolution System Font", "100,120,120"
a:egasys.fon,"AT&T (640x400) resolution System Font", "120,96,80"

[fixedfonts]
a:egafix.fon,"EGA (640x350) resolution Fixed System Font", "133,96,72"
a:vgafix.fon,"VGA (640x480) resolution Fixed System Font", "100,96,96"
a:8514fix.fon,"8514/a (1024x768) resolution Fixed System Font",  "100,120,120"
a:egafix.fon,"AT&T (640x400) resolution Fixed System Font", "120,96,80"

[oemfonts]
a:egaoem.fon,"EGA (640x350) resolution Terminal Font (USA/Europe)", "133,96,72",1
a:vgaoem.fon,"VGA (640x480) resolution Terminal Font (USA/Europe)", "100,96,96",1
a:8514oem.fon,"8514/a (1024x768) resolution Terminal Font (USA/Europe)", "100,120,120",1
a:egaoem.fon,"AT&T (640x400) resolution Terminal Font (USA/Europe)","120,96,80",1

[fonts]
   a:SSERIFB.FON, "MS Sans Serif 8,10,12,14,18,24 (EGA res)", "133,96,72"
   a:SSERIFE.FON, "MS Sans Serif 8,10,12,14,18,24 (VGA res)", "100,96,96"
   a:SSERIFF.FON, "MS Sans Serif 8,10,12,14,18,24 (8514/a res)", "100,120,120"

   a:COURB.FON, "Courier 8,10,12,15 (EGA res)", "133,96,72"
   a:COURE.FON, "Courier 10,12,15 (VGA res)", "100,96,96"
   a:COURF.FON, "Courier 10,12,15 (8514/a res)", "100,120,120"

   a:SERIFB.FON, "MS Serif 8,10,12,14,18,24 (EGA res)", "133,96,72"
   a:SERIFE.FON, "MS Serif 8,10,12,14,18,24 (VGA res)", "100,96,96"
   a:SERIFF.FON, "MS Serif 8,10,12,14,18,24 (8514/a res)", "100,120,120"

   a:ARIALB.FON, "Arial 8,10 (EGA res)", "133,96,72"
   a:TIMESB.FON, "Times New Roman 8,10 (EGA res)", "133,96,72"

   a:SYMBOLB.FON, "Symbol 8,10,12,14,18,24 (EGA res)", "133,96,72"
   a:SYMBOLE.FON, "Symbol 8,10,12,14,18,24 (VGA res)", "100,96,96"
   a:SYMBOLF.FON, "Symbol 8,10,12,14,18,24 (8514/a res)", "100,120,120"

   a:SMALLB.FON, "Small Fonts (EGA res)", "133,96,72"
   a:SMALLE.FON, "Small Fonts (VGA res)", "100,96,96"
   a:SMALLF.FON, "Small Fonts (8514/a res)", "100,120,120"

   a:ROMAN.FON, "Roman (Plotter)",   "CONTINUOUSSCALING"
   a:SCRIPT.FON, "Script (Plotter)", "CONTINUOUSSCALING"
   a:MODERN.FON, "Modern (Plotter)", "CONTINUOUSSCALING"

Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web1, load: 0.77