home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!walter!att-out!pacbell.com!ames!olivea!spool.mu.edu!caen!batcomputer!lynx@msc.cornell.edu!tommy
- From: tommy@lynx.msc.cornell.edu.UUCP (Mike Thompson,332,54714,2734927)
- Newsgroups: comp.os.os2.misc
- Subject: Re: The SP, Diamond SpeedStar (ET4000), and Higher Resolutions
- Message-ID: <1992Nov17.160236.22331@msc.cornell.edu>
- Date: 17 Nov 92 16:02:36 GMT
- References: <8Bu9TB2w165w@student.business.uwo.ca>
- Sender: news@msc.cornell.edu
- Organization: Cornell-Materials-Science-Center
- Lines: 58
- Originator: tommy@snoopy.msc.cornell.edu
-
- From article <8Bu9TB2w165w@student.business.uwo.ca>, by pkedrosk@student.business.uwo.ca (Paul S. Kedrosky):
-
- > I've seen more stuff on this topic than i care to think about but I'm
- > about to add a little more.
- >
- > All of the solutions that I have seen to the problem of getting OS/2
- > (post SP) to work non-interlaced in 800x600 or 1024x768 haven't worked
- > for me. If you're reading this you probably know the prescription I'm
- > talking about: full screen dos session, svga off, vmode, svga on, run
- > dspinstl, reboot, etc etc. I may be missing steps but this is
- > essentially the jist of it. I have found a work around that gets
- > Diamond Speed Star Et400-based cards into the the two top resolutions
- > without the screen going kerblooey.
-
- And I will add more. There seems to be a lot of misinformation about
- the SVGA problem with Diamond SpeedStar.
-
- My configuration is a Gateway 2000 with a Diamond SpeedStar. To get
- 1024x768 running, I
-
- 1. Run Selective Install (not dspinstl)
- 2. After it finishes, DO NOT REBOOT IMMEDIATELY AS REQUESTED.
- 3. Open a DOS Full Screen Session.
- 4. run VMODE MONITOR
- 5. run SVGA ON
- 6. Exit Dos Full Screen and reboot.
-
- The problem is not a bug in SVGA, but a limit of the Diamond SpeedStar;
- it cannot autodetect the monitor type.
-
- When dspinstl (from selective install) does the automatic SVGA ON, the
- board does not know what type of monitor is attached. (why it forgets
- is beyond me, but it does). Consequently, SVGA properly copies the
- register information into the SVGADATA.PMI for an incorrect monitor.
- When the high resolution drivers initialize the board, they do so with
- this incorrect configuration.
-
- Switching to the FULL screen session and running VMODE, SVGA ON AFTER
- the install rewrites the SVGADATA.PMI with the correct register info.
- Now, the system can correctly configure itself and run. All of the
- tricks of making multiple SVGADATA.PMI files and copying over the one
- written by dspinstl do the same thing.
-
- Important notes:
- 1. RUN Selective Install, not dpsinstl
- 2. Ignore the instructions from IBM about starting a DOS session,
- I've heard of no one finding that successful.
- 3. Run the Full Screen DOS "VMODE MONITOR" and "SVGA ON" AFTER
- running Selective Install but before rebooting, not BEFORE.
-
- -----------------
- ____ ___ ___ ___ Michael O. Thompson
- / / / / / / / / / \ / Materials Science & Engineering
- / /__/ / / / / / / / 329 Bard Hall -- Cornell University
- Ithaca, NY 14853
- tommy@msc.cornell.edu Ph: (607) 255-4714
-
- OS/2: For the few, the proud, the devoted!
-