BUG IN INSTALL OF MATROX MILLENIUM OS/2 DRIVER 2.13.053 At a suggestion from this forum, we recently upgraded our Matrox Millenium driver from Version 2.03.038. Before this video driver upgrade, I had reset video to VGA. I did the upgrade by following the instructions which came (unzipped) with the newly downloaded V2.13.053 driver, basically just running INSTALL.CMD (also unzipped from the download). Immediately after the driver install/reboot, two problems were obvious: 1) The MGA Settings icon on my Desktop had transformed to a blank white icon. 2) I was unable to open ANY WIN-OS2 session, seeing a error related to DISPLAY.DRV. The first problem was easy to fix. I just opened the PROPERTIES of the MGA Settings icon and pointed it at D:\MGA\OS2\MGASET.EXE (where the MGA subdir is on my D: drive) for Path and File Name settings. The second problem was MUCH tougher to figure out, and is the reason for this posting. Hopefully this will keep others from pulling out their hair as I did while trying to sort this out. It seems the original Matrox driver install routine (from INSTALL.CMD on the CD that came w/the Millenium board, which had installed my V.2.03.038 driver) setup the WIN-OS2 SYSTEM.INI to look for a Seamless Windows driver called SMGAS64.DRV. This is what I saw in this SYSTEM.INI file (booting from floppy to be able to open and view the INI file) under the DISPLAY.DRV setting. The new Matrox driver installed the Seamless Windows driver as SMGAX64.DRV (note the different 5th character in the filename!!!), but never changed the SYSTEM.INI setting. Once I realized this, I finally sorted everything out by just copying the new SMGAX64.DRV driver to an identical file in the same subdir (D:\OS2\MDOS\WINOS2\SYSTEM, where D: is my OS/2 boot drive) with the old SMGAS64.DRV filename. FWIW, before coming upon this solution, I had done the following: * Reset to VGA and tried to reinstall using the new INSTALL.CMD 3 times. * Actually re-downloaded the new driver from Matrox's ftp site, to make sure there was no corruption in the file. * Reset to VGA and tried to reinstall using the re-downloaded driver files 2 times. None of the above asterisked attempts made any difference. Symptoms were STILL exactly the same (both #1 and #2 above) each time I tried to reinstall the new driver. I am 1000% convinced that there is a problem with the new INSTALL.CMD which causes this. I am posting this in this forum, and also in an E-mail to Matrox, hoping that it will help others who see the same problem. Best of luck, and feel free to direct any questions on the procedure above to me. John C. Fusi CSi: 72010,3723 Internet: RueDog@ibm.net JCF Research Associates, Inc. FAX Transmission From: John C. Fusi, C.E.O. Date: 22 September 1997 To: Time: 16:52 hrs EDT Company: FAX #: 97/ Phone: (908) 647-9600 FAX: (908) 647-1146 320 Essex Street, Suite 5, Stirling, NJ 07980 USA