Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

27.10 *still* doesn't work...

0 views
Skip to first unread message

Richard West

unread,
Jan 25, 2002, 6:26:41 AM1/25/02
to

Gainward GF3 card + SGI 1600SW flat-panel monitor via DVI + 27.10 drivers =
black screen.

Just like 23.xx!

Still using 22.80, as it's the only drivers that give me a display which
isn't one of:

a) shifted right by 8 pixels
b) black

Come on Nvidia. Get your act together! I *know* you know about this bug!
You've had is right in the past, now you've un-got it right. Please re-get
it right!

Grrrrrr.

Hans Bergengren

unread,
Jan 25, 2002, 8:26:05 AM1/25/02
to

"Richard West" <rgw...@ntlworld.com> wrote:

> Still using 22.80

Where can these be downloaded? I've been doing some looking around for them,
but not found a pure reference set.

Thanks!


Bye!
/HB.

Richard West

unread,
Jan 25, 2002, 9:42:17 AM1/25/02
to

They be got from here...

http://www.3dchipset.com/drivers/beta/nvidia/series2xx.shtml

Apparentl they are "beta".

"Hans Bergengren" <sp...@spam.com> wrote in message
news:N1d48.10527$n4.19...@newsc.telia.net...

John Russell

unread,
Jan 25, 2002, 10:01:12 AM1/25/02
to
I'm very concerned that the so called Unified Driver Approach is breaking
down. I've reported about problems with the 23.xx drivers for windows98se
but the impression I'm getting is that both Nvidia, and most people who use
this NG, are only bothered about Windows XP.

"Richard West" <rgw...@ntlworld.com> wrote in message
news:Phb48.22298$ka7.3...@news6-win.server.ntlworld.com...

Richard West

unread,
Jan 25, 2002, 10:06:55 AM1/25/02
to

Well I'm using XP. I've managed to solve my problem by fiddling with the
scaling options. Helluva hullballo though.

Adapter scaling is still broken though (as it has been for a while)...


"John Russell" <john_e_...@hotmail.com> wrote in message
news:3c5172c7$1...@mk-nntp-1.news.uk.worldonline.com...

me

unread,
Jan 25, 2002, 11:31:05 AM1/25/02
to
Don't say "Come on Nvidia, Get your act together!
It's your fault! You just don't know what you are doing!
 

Richard West

unread,
Jan 25, 2002, 11:45:09 AM1/25/02
to

Too true.

"me" <m...@here.org> wrote in message
news:dLf48.119$S4.1...@paloalto-snr2.gtei.net...

John Russell

unread,
Jan 25, 2002, 11:54:15 AM1/25/02
to
Some people need you to post a CV containing how many graphics cards you'd
swapped , and how drivers you've successfully installed before they take any
problem report seriously!

"me" <m...@here.org> wrote in message
news:dLf48.119$S4.1...@paloalto-snr2.gtei.net...

me

unread,
Jan 25, 2002, 12:08:20 PM1/25/02
to
Hehe, I've probably done about 70,000 driver installs for Nvidia cards in South Africa alone
as an american citizen, and through our companie's software, we did it all at once without any
bluescreens or hitches. On the other hand, the computers were all from the same IBM computer family
so it makes it easy. On the other hand, I probably do about 20,000 nvidia driver installs at tradeshows
all around the world every year. As far as graphics cards I've swapped, what do you mean? Like how many
graphics cards I've changed in a year from one to another. I'd say about 20,000 a year, like i have drivers,
at the same tradeshows. I'm not exactly a slouch when it comes to working with Nvidia cards. I'm also a registered
Nvidia developer and develop Virtual Reality 3D engines with Nvidia as my root. On the other hand, I use my own custom
OS which is simply a rip of the latest Linux kernel and the have my own X type server made completely from OpenGL calls.
It really rocks for OpenGL because the whole thing is all about OpenGL from the kernel up. I even have Sound extensions
in OpenGL calls for all recent Intel Mainboards. That way I can use the sound technology built into intel mainboards which
isn't shabby by the way. You'd be suprised what those little Analog devices multichannel ADAC chips do, even for 3D.
Beats the hell out of Soundblaster cards, except for wavetable as I have no wavetable for music. I'm not playing music,
I'm making VR programs for the development of applications.

Bob Austin

unread,
Jan 25, 2002, 1:13:47 PM1/25/02
to
20000 Video card changes a year eh!! That's 55 video card changes every
single day of 365 days per year! Bullshit or what!!!

Bob


me

unread,
Jan 25, 2002, 12:01:06 PM1/25/02
to
I hate being honest because it hurts me to be blunt as it hurts and pisses off others, but
my God, I can see that there is a mess on your hands and it has to do with that flat panel.
Also, since you were polite instead of was mean to me, then I'll tell you that there, in the .inf
file, is a list of resolutions and refresh rates. Find the resolution and refresh rate table for
your video card and then notice that the 8 and 16bit color refresh rates are higher than the 32bit
refresh rates. For your video card table, make the 32bit color refresh rate match up to your 8 and 16
bit refresh rates in that table by simply copying all the resolution and refresh rates from your 16bit table
starting at 1600x900 resolution to the highest resolution.
Then delete from your 32bit table for your video card, the resolution and refresh settings from 1600x900
and then past your 16bit resolution and refresh settings to that 32bit settings hole that you made.
Then, change all the 16's in that 32bit color list to 32's and then uninstall and reinstall your drivers.
That should solve your problem.

Hans Bergengren

unread,
Jan 25, 2002, 3:15:40 PM1/25/02
to

"Richard West" <rgw...@ntlworld.com> wrote:

> They be got from here...
> http://www.3dchipset.com/drivers/beta/nvidia/series2xx.shtml

Thank You!

> Apparentl they are "beta".

Yeah, I know. But I feel that can be said about many of Nvidia's drivers
wether leaked or official. ;-)


Bye!
/HB.

Vincent Poy

unread,
Jan 25, 2002, 5:32:51 PM1/25/02
to
"Richard West" <rgw...@ntlworld.com> wrote in message news:<Phb48.22298$ka7.3...@news6-win.server.ntlworld.com>...

Yeah, I have the PNY GeForce3 Ti500 and have the same problem as
reported before. 23.xx and 27.xx has the problem where 1280x1024 60hz
is the highest resolution that will work but 1600x1024 60hz gives a
1280x960 60hz signal when I checked by pressing the button on the
Multi-Link Adapter. 21.88 is the last stable driver for me since
22.xx does work but full screen command prompt in XP will give me a
BSOD but 21.88 doesn't have the problem.

Cheers,
Vince

Vincent Poy

unread,
Jan 25, 2002, 5:58:03 PM1/25/02
to
I'm going to try your theory and do a comparison. All I know is that
the drivers worked fine up to 22.80 but I'm at 21.88 due to 22.xx
giving me a BSOD when I do a full screen command prompt in WinXP
Professional. I do know that 1600x1280 works fine on my Dell Inspiron
8000 notebook and for others with the Inspiron 8100 as well with the
GeForce2Go modified inf file. But people had problems with 23.xx even
at 1600x1280 LCD's so it's not just a issue with the GeForce3 Ti500
and the SGI 1600SW 17.3" 1600x1024 LCD which both Richard and I have.
I have tested 23.xx and 27.xx and 1280x1024 is the highest the drivers
will work. If we put it at 1600x1024 60Hz, the card seems to be
sending a signal at 1280x960 60hz which is what is causing the problem
but anyways, just for comparison. The GeForce3 Ti500 is listed as a
ID 202 so from the .inf files, we do the comparison of your theory:

[22.80]
HKR,, NV20_2_Modes, %REG_SZ_APPEND%, "8 1600 1024
60 70 72 75 85 100 0"
[27.10]
HKR,, NV20_2_Modes, %REG_SZ_APPEND%, "8 1600 1024
60 70 72 75 85 100 0"

[22.80]
HKR,, NV20_2_Modes, %REG_SZ_APPEND%, "16 1600 1024
60 70 72 75 85 100 0"
[27.10]
HKR,, NV20_2_Modes, %REG_SZ_APPEND%, "16 1600 1024
60 70 72 75 85 100 0"

[22.80]
HKR,, NV20_2_Modes, %REG_SZ_APPEND%, "32 1600 1024
60 70 72 75 85
[27.10]
HKR,, NV20_2_Modes, %REG_SZ_APPEND%, "32 1600 1024
60 70 72 75 85

From what I see, they are identical so it's not a problem with the
.inf file
since it's a problem with the drivers not being able to send the
correct signal out the DVI interface like it did in the older drivers.
There used to be a problem with this resolution which SGI prompted
Hercules to get NVidia to fix in 12.40 and above.

Cheers,
Vince


"me" <m...@here.org> wrote in message news:<mbg48.139$S4.2...@paloalto-snr2.gtei.net>...

> --

Dave

unread,
Jan 25, 2002, 9:58:27 PM1/25/02
to
He pulls this same shit in the ATI newsgroup. People generally don't take
him seriously there either. You'd think with all this experience he'd have
learned to stop posting in HTML, too...

"Bob Austin" <bob.a...@ntlworld.com> wrote in message
news:ueh48.16555$4i5.2...@news11-gui.server.ntli.net...

Richard West

unread,
Jan 26, 2002, 3:21:23 AM1/26/02
to

"Vincent Poy" <vi...@WURLDLINK.NET> wrote in message
news:e758f5f2.02012...@posting.google.com...

>
> Yeah, I have the PNY GeForce3 Ti500 and have the same problem as
> reported before. 23.xx and 27.xx has the problem where 1280x1024 60hz
> is the highest resolution that will work but 1600x1024 60hz gives a
> 1280x960 60hz signal when I checked by pressing the button on the
> Multi-Link Adapter. 21.88 is the last stable driver for me since
> 22.xx does work but full screen command prompt in XP will give me a
> BSOD but 21.88 doesn't have the problem.
>

Ahh, glad to know I'm not alone (sort of!). Well I sort of got it to work
like this...

1. Change resolution to something low (eg. 640x480)
2. Upgrade the drivers
3. Change the resolution up to 1280x1024.
4. Change the DFP Options (Display Properties -> Settings -> Advanced ->
Device Selection -> Device Adjustments) to use "Centred Output" rather than
"display adapter scaling" or "monitor scaling".
5. Change to 1600x1024.

And bingo, it works! The problem is that Windows seems to forget this little
bit of tweaking across a re-boot.
When you boot up again youget the black screen once more (unless you F8 and
boot into VGA mode). I'm trawling the registry to see if I can't get this
change to stick permanently.

Richard.

Richard West

unread,
Jan 26, 2002, 5:45:05 AM1/26/02
to

Well, I've been fiddling about some more and I've found a few things:

1) There's a registry key called 'flatpanelmode0' which changes whenever I
alter the DFP scaling mode, though I can't see any logic to the values it
takes. It also seems to change across reboots.

2) I tried removing all reference to the 1280x960 mode (which the card
outputs in lieu of 1600x1024) in the INF file and re-installing the drivers.
Although I now can't select 1280x960 as a display mode, if I select
1600x1024 that's still what I'm getting (according to the MLA).

Blah.

"Richard West" <rgw...@ntlworld.com> wrote in message

news:5Gt48.27499$ka7.4...@news6-win.server.ntlworld.com...

ZOD

unread,
Jan 26, 2002, 11:14:37 AM1/26/02
to
> I have tested 23.xx and 27.xx and 1280x1024 is the highest the drivers
> will work. If we put it at 1600x1024 60Hz, the card seems to be

I read somewhere about a hardware issue with this on some early GF3's with
DVI.....TI models should not have it though.


Richard West

unread,
Jan 26, 2002, 12:26:42 PM1/26/02
to

I can't see how this is a hardware problem. By messing about I can get
1600x1024 to display, I just can't get the "fiddling" to stick across a
reboot.

"ZOD" <Z...@ZOD.com> wrote in message
news:NBA48.17197$ag5.1...@newsread2.prod.itd.earthlink.net...

ZOD

unread,
Jan 26, 2002, 1:20:49 PM1/26/02
to
> I can't see how this is a hardware problem. By messing about I can get
> 1600x1024 to display, I just can't get the "fiddling" to stick across a
> reboot.

Yeah..not sure either. WHy don't you send me a panel to test with...hehe

Vincent Poy

unread,
Jan 26, 2002, 4:19:23 PM1/26/02
to
"ZOD" <Z...@ZOD.com> wrote in message news:<NBA48.17197$ag5.1...@newsread2.prod.itd.earthlink.net>...

I doubt it's a hardware problem since besides the 1600x1024 60hz
resolution, there is a special timing mode needed. Silicon Graphics
Inc (SGI) was testing this on a Hercules card and Hercules reported
the problem to Nvidia and Nvidia added the fix to 12.40 drivers. I
used to be using a Matrox G400Max DualHead until 3 months ago so I
never actually had the experience portion but I know people before
12.40 had problems where they had to use powerstrip to fix. Not sure
what they did though. Ah, I found it from:
http://www.sgi.com/peripherals/displays/multilink/nvidia_faq.html

At this time, all cards based on the GeForce3 cards have a problem
where the display is shifted several pixels to the right, and the
screen "wraps" around to the other edge. This problem has been
reported to NVIDIA, and will hopefully be fixed in a future driver.
Other users have reported a workaround using Powerstrip 3.0 by setting
"Sync Width" to 232 under the "Horizontal Geometry" section in
"Advanced Timing Options".

They haven't updated that page in ages but basically the SGI 1600SW is
a OpenLDI interfaced monitor and both Richard and I have this
Multi-Link Adapter which converts VGA, DFP, DVI interfaced video cards
to be able to talk to the display. I think the special timing mode is
because this monitor is at a 16:9 ratio or superwide as they call it
so just 1600x1024 60hz won't work without the special timing mode.
Ofcourse it seems that I remember other people who had DVI LCD
display's had the same symptoms with regular LCD panels in 23.xx too
so maybe they broke something in DVI support. Ofcourse, the 15" LCD's
1600x1280 on notebooks such as the GeForce2Go on the Dell Inspiron
8000/8100 which I am also user doesn't have the problem with
23.10/23.11/27.10 modified drivers.

Cheers,
Vince

Vincent Poy

unread,
Jan 26, 2002, 4:21:15 PM1/26/02
to
Yep, since drivers 12.40-22.80 don't have the problem and only
beginning with 23.xx did the problems exist and even people with
non-SGI DVI LCD's had the same problem. I remember we discussed the
problem with 23.10/23.11 and you proved I wasn't alone.

Cheers,
Vince


"Richard West" <rgw...@ntlworld.com> wrote in message news:<wFB48.18952$4i5.3...@news11-gui.server.ntli.net>...

Vincent Poy

unread,
Jan 26, 2002, 4:35:38 PM1/26/02
to
"Richard West" <rgw...@ntlworld.com> wrote in message news:<5Gt48.27499$ka7.4...@news6-win.server.ntlworld.com>...

I haven't tried the DFP options thing on 23.xx or 27.xx yet but by
default, it's on display adapter scaling. When I moved it to centred
Output, it seems like the screen is slightly smaller in size. When I
tried monitor scaling, the entire screen turned white and I can't see
anything so I hard resetted.

Cheers,
Vince

Vincent Poy

unread,
Jan 26, 2002, 4:37:24 PM1/26/02
to
I wonder if on 2 below, what really happened is that the drivers does
support the 1600x1024 60hz but what they messed up on is the special
timing mode needed for the SGI to do the SuperWide special timing
mode.

Cheers,
Vince


"Richard West" <rgw...@ntlworld.com> wrote in message news:<VMv48.27636$ka7.4...@news6-win.server.ntlworld.com>...

akula

unread,
Feb 14, 2002, 1:23:52 PM2/14/02
to
I just installed the new 27.42 drivers from here:
http://www.guru3d.com/files/pafiledb.php?PHPSESSID=&action=viewfile&fid=317&id=10

Not only do they work with the 1600sw on my gf3, they allow for
monitor scaling. All resolutions below 1600x1024 now look much better
than they did with adapter scaling.

vi...@WURLDLINK.NET (Vincent Poy) wrote in message news:<e758f5f2.02012...@posting.google.com>...

Vincent Poy

unread,
Feb 15, 2002, 12:10:33 AM2/15/02
to
Cool.... Richard emailed me this morning and said 27.42 worked for
him. So I grabbed the newer revision of 27.42 from guru3d.com and
then loaded it, on my PNY Verto GeForce3 Ti500, it defaulted to
Monitor scaling while Richard said it did Center on his. 27.42 fixed
both the problem where it didn't work for the 1600SW since 23.10 and
also the full screen command prompt (windowed command prompt worked
fine) on all versions after 21.88. So NVidia actually did a good job
with this one. I guess since we have a 1600SW, we don't need the
modified inf for the refresh rate hack since we can only do 60hz.

Cheers,
Vince


t_ka...@coloradocollege.edu (akula) wrote in message news:<dd686d8f.02021...@posting.google.com>...

Matthew Farra

unread,
Feb 18, 2002, 3:32:37 PM2/18/02
to
vi...@WURLDLINK.NET (Vincent Poy) wrote in message news:<e758f5f2.02021...@posting.google.com>...

> Cool.... Richard emailed me this morning and said 27.42 worked for
> him. So I grabbed the newer revision of 27.42 from guru3d.com and
> then loaded it, on my PNY Verto GeForce3 Ti500, it defaulted to
> Monitor scaling while Richard said it did Center on his. 27.42 fixed
> both the problem where it didn't work for the 1600SW since 23.10 and
> also the full screen command prompt (windowed command prompt worked
> fine) on all versions after 21.88. So NVidia actually did a good job
> with this one. I guess since we have a 1600SW, we don't need the
> modified inf for the refresh rate hack since we can only do 60hz.
>
> Cheers,
> Vince

Tried those newer 27.42 drivers from guru3d.com on my VisionTek XTasy
6964 (GeForce3 Ti-500). I have the same problem with these drivers as
I do with anything newer than 21.83. My 1600SW shows the initial
booting screen, the white-background Windows 2000 is starting up
screen, and then goes blank. The 1600SW and MultiLink LEDs turn
yellow (indicating no signal). If I press the menu button on the
MultiLink, it reports no signal detected. If I attach a standard VGA
CRT, the CRT works fine.

Anyone have any suggestions? I'm frustrated that I'm stuck with
drivers this old and have been unable to take advantage of the newer
drivers.

-Matt Farra
farr...@pilot.msu.edu

Vincent Poy

unread,
Feb 20, 2002, 5:08:29 AM2/20/02
to
farr...@pilot.msu.edu (Matthew Farra) wrote in message news:<fdb369fb.02021...@posting.google.com>...

Hmm, did you uninstall the drivers with Add/Remove software in Control
Panel before you installed the new version?

Cheers,
Vince

Simon

unread,
Feb 23, 2002, 3:31:48 PM2/23/02
to
vi...@WURLDLINK.NET (Vincent Poy) wrote in message news:<e758f5f2.02022...@posting.google.com>...

Greetings,

I'm also using a VisionTek 6964 and was restricted to just using
the 21.83 drivers under Win2K. After reading the posts here about
the success folks are having with 27.42 I gave it another try but
with still no luck.

I think the VisionTek was one of the first Ti500 so I thought I'd
look elseware and so started to check out things like the boards
bios. It was something like 3.16.00xx which was old(ish) so I
decided to update it to something more current. I'm happy to report
that with bios 3.20.00.18X25 I'm now using the new drivers. I'll
use the new configuration for a few days to see how it goes. Hope
this help and I'll post an update in a few days to give any
feedback.

Simon.

PS. Current system is a VisionTek 6964 Ti500 driving an apple cinema
display (via a Gefen DVI to ADC adapter).

Vincent Poy

unread,
Feb 26, 2002, 1:46:31 AM2/26/02
to
st...@speakeasy.net (Simon) wrote in message news:<e158bf5a.02022...@posting.google.com>...

I'm using 27.51 now and the BIOS on my PNY Verto GeForce 3 Ti500 from
guru3d.com is 3.20.00.20.02 Nvidia Reference GF3 Ti500 Bios. The
Visiontek seemed to have shipped with a even earlier bios than the PNY
which was at 3.20.00.19.xx before I did the upgrade. 27.42 does
generate BSOD's under WinXP from time to time like many reported with
27.42 in general. Give 27.51's a try. How do you like the Apple
Cinema? Is that the 22"? and how much and where can one get the
Gefen DVI to ADC adapter? Thanks.

Cheers,
Vince

Simon

unread,
Feb 26, 2002, 3:48:26 PM2/26/02
to

Vince,

I've not had any BSOD under Win2K yet but thanks for the tip
about the 27.51 under WinXP. Played a few games and continued
my development without problems so I'm happy.

The Apple Cinema is the 22" display. I like it and looks nice
too also saving a lot of desk space (secondary concern LOL).
The DVI to ADC adapter can be found at www.gefen.com and
I've had no problem with the device. Cost $199 last time I
checked. Yeah I know it's a luxury but nice combo with the PC.

Simon.

Vincent Poy

unread,
Feb 27, 2002, 5:04:24 PM2/27/02
to

Simon,

I think the BSOD is only a WinXP issue and not a Win2k issue. There
is another issue with WinXP where when the machine is idle for a
certain period of time, the defrag starts to run and then the system
will eventually run out of resources and the only way out is to
shutdown or reboot. I'm not sure how to even turn it off since the
Release Candidates and the Beta's didn't have the problem.

Cheers,
Vince

Vincent Poy

unread,
Feb 27, 2002, 5:06:53 PM2/27/02
to

Also Simon,

The Apple Cinema Display actually is pretty cool and is actually just
a larger version of the SGI 1600SW since both of the screens are made
by the commercial side of Mitsubishi. The DVI to ADC Adapter isn't
that much of a luxury since it's still way cheaper than the SGI
Multilink we paid for. Ofcourse, thanks to your link, I found the DVI
switcher box!

Cheers,
Vince

Simon

unread,
Feb 28, 2002, 3:10:19 AM2/28/02
to
vi...@WURLDLINK.NET (Vincent Poy) wrote in message news:<e758f5f2.0202...@posting.google.com>...

Vince,

LOL. Let me know what happens :).

Simon.

Simon

unread,
Mar 5, 2002, 11:16:34 PM3/5/02
to

Vince,

I said I'd give some feedback after a period and here it is.

Used the drivers with the bios update for now over a week and
all things seem stable. No glitches and things running smoothly.
Thanks to this thread I was able to sort this out, greatly
appreciated.

Luck.
Simon.

Vincent Poy

unread,
Mar 6, 2002, 6:01:17 AM3/6/02
to
In article <e158bf5a.02030...@posting.google.com>,

Cool Simon... Now let's see who can actually get the 27.70's
working with a GeForce3 Ti500 even with a modified inf under 2k/XP
since even with the modded inf, XP reports no drivers can be found
even when it lists and let's you choose the device.


Cheers,
Vince - vi...@WURLDLINK.NET - Vice President ________ __ ____
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ]
WurldLink Corporation / / / / | / | __] ]
San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____]
Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin

0 new messages