#Vibrant Drivers
5 messages in this thread
Do you know where I can get current Vibrant drivers for supporting Diamond
Viper P9000 cards? (Diamond says I need the current driver and they don't have
them. I just bought the cards last week.)
–Noah
Noah,
<< latest drivers >>
The latest Vibrant drivers can be found in "VIB3DS.zip" in the "What's new"
section of the libs.
jonas[adesk]
Thanks, Jonas. I got some dated 4/8/94 already from Vibrants BBS, and still
can't get it to work. I'll try the one's here, also, I guess.
–Noah
I could not get the drivers from CompuServe to work properly, so I called
Vibrant and talked to John in Technical Support. He had me download them from
Vibrant's BBS (512-918-3411) and they worked just fine. The instructions are
to download the file named VIBCFG.ZIP, unzip it and copy the unzipped files
into the main 3D Studio directory (C:\3DS3 for mine). I then ran "3DS VIBCFG"
and selected the Diamond Viper P9000 chip and all resolutions work fine (I hope
I am right about the filenames and commands.)
I will tell you that I have one small anomaly and I called Vibrant to report it
on 5/5 but they have not called me back yet. When I run Windows or a graphics
package called RIO by AT&T and then exit them and try to run 3D Studio, the 3D
Studio screen comes up kind of garbled. It also leaves mouse trails (its very
strange.) I found out that if I select, with the mouse, several of the
programs like KEYFRAMMER and other, it will eventually clean the screen
problems up when it changes screens between the internal programs. After it's
cleared up, it never comes back as long as I stay in 3D Studio.
Hope some of this info helps. Drop me a note if you have any other problems.
Kenny-
Thank you for your reply. I think I downloaded the same file (it was
VIB3DS.ZIP) from Vibrant. These files were dated 2/28/94. There was a more
recent version called 1D124102.ZIPwith files dated 4/8/94, which I used. I got
different errors and could only get the VESA drivers to work, which perform
goofily (very slow response). I guess the next thing for me to try is to go
back to the 2/28 version, which I'm assuming is the one you used.
Do you know if your driver is specifically for the PCI version of the Viper?
Are all Viper's PCI cards? I'll ask Diamond when I can get hold of someone
there.
BTW, we use RIO , too, and we had some of those same trails, but in RIO using
the TARGA driver, I believe. It seems as though maybe we got the same thing
persisting in 3DS, but I wouldn't swear to it. It was a while ago and before
any of these Viper problems.
–Noah