Документ взят из кэша поисковой машины. Адрес оригинального документа : http://crydee.sai.msu.ru/ftproot/pub/misc/doc/winos2-mga Дата изменения: Fri Apr 5 10:17:20 1996 Дата индексирования: Sun Apr 10 04:33:50 2016 Кодировка: Поисковые слова: annular solar eclipse

From ns.itep.ru!Radio-MSU.net!dscomsa.desy.de!news.belwue.de!fu-berlin.de!news.mathworks.com!newsfeed.internetmci.com!in2.uu.net!news.sprintlink.net!news.xnet.com!doj Fri Apr 5 10:17:21 1996
Path: ns.itep.ru!Radio-MSU.net!dscomsa.desy.de!news.belwue.de!fu-berlin.de!news.mathworks.com!newsfeed.internetmci.com!in2.uu.net!news.sprintlink.net!news.xnet.com!doj
From: doj@flood.xnet.com (David James)
Newsgroups: comp.os.os2.setup.video
Subject: Solved - setting Matrox WinOS2 FS resolution
Date: 2 Apr 1996 03:22:45 GMT
Organization: XNet - A Full Service Internet Provider - (708) 983-6064
Lines: 35
Message-ID: <4jq6i5$hki@flood.xnet.com>
NNTP-Posting-Host: cyclone.xnet.com
X-Newsreader: TIN [version 1.2 PL2]


After weeks of "challenging" frustration, I finally figured out how
to make my Matrox Millennium do what I needed: to run WinOS2 Full-
screen sessions run at lower resolutions & color depth (640x480x256)
than my OS/2 desktop. Some of my WinOS2 apps, (particularly my 4-year
old's games) wouldn't run in any better than VGA.

Thanks to a reply from my original post, here's what I did:
1. copied the original DOS-Windows drivers to my WinOS2/system dir:
mgax64.drv and mgax64.dll
2. hacked WinoS2 system.ini, changing
"display.drv=smgax64.drv" to "display=mgax64.drv".

HOWEVER.. it took me two weeks to get it working reliably!! One boot
partition (my test parition) worked, but not the other. There, full
screen WinOS2 sessions would be corrupted, with vertical lines cutting
into the whole screen, making it almost unreadable. To figure out the
difference, I kept cycling through
a) backing up test OS2 boot partition
b) going a little further through the install (e.g., app migration)
c) testing WinOS2 fullscreen resolution
until it broke #c, helping me identify the difference & cause. Eventually
I thought it was DOS Driver for Internet connection, then that I was using
IRQ 9 for modem, but then it eventually STILL broke without those set.

Ya know what the problem was? SYSTEM CLOCK (???!!!).
I have it set for digital display. When I make it too small,
WinOS2 fullscreen display goes to pot. When I enlarge it a bit,
WinOS2 fullscreen display gets fixed.

Its the nuttiest thing, but at least I can make it work now.
Any theories on WHY??? Just curious.

Dave James doj@xnet.com