home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!ogicse!news.u.washington.edu!tad
- From: tad@wrq.com (Tad Marshall)
- Newsgroups: comp.os.ms-windows.programmer.win32
- Subject: Re: Problems with LINK386 and ET4000
- Message-ID: <1992Sep14.042506.19747@u.washington.edu>
- Date: 14 Sep 92 04:25:06 GMT
- Article-I.D.: u.1992Sep14.042506.19747
- References: <1992Sep13.220316.23236@cs.mcgill.ca>
- Sender: news@u.washington.edu (USENET News System)
- Organization: Walker Richer & Quinn, Inc., Seattle, WA
- Lines: 22
-
- In article <1992Sep13.220316.23236@cs.mcgill.ca> storm@uriel (Marc WANDSCHNEIDER) writes:
- >
- >Got the NT PreRelease SDK, and have been fiddling with it to try and see
- >how things are.
- > ...
- >Following the instructions given there just caused my screen to garble
- >stuff up big time though -- as if the frequency was all hosed. I am curently
- >using my SpeedStar with my AAMAZING monitor in High-Res (60Hz) without
- >troubles.
-
- On my Windows 3.1 system, I am using a Diamond SpeedStar with a Gateway 2000
- "1024NI" monitor which maxes out at 60Hz when displaying 1024x768. In order
- to make it work, I need to run a program called VMODE.COM before starting
- Windows, otherwise it is like you say, unable to sync up with the video
- signal. I suspect that the SpeedStar defaults to a frequency higher than
- 60Hz if you don't run VMODE. This is mostly bad news for NT, since I'm not
- sure that there is any way to get VMODE (a DOS program) to run before NT, and
- NT is unlikely to let a DOS program hammer the video mode. The only
- sure-fire solution, I suspect, is a new monitor, one which can handle the
- (70Hz?) refresh rate the SpeedStar is using. Or wait for a tunable driver.
-
- Tad Marshall
-