#VIPER PCI+ 3DS
11 messages in this thread
to : SYSOP, ANYONE WHO MIGHT KNOW
RE: VIPER PCI ON GATEWAY 2000 P-60 WITH NEC 4D MONITOR
PROBLEM: I CANNOT GET MY VIPER TO DRIVE MY MONITOR FOR 3D-STUDIO r3
THE MONITOR EITHER GOES MILKY, OR THERE IS A WHITE FRECKLED
HORIZONTAL BAND IN THE CENTER. IN THE CENTER BANDING CONDITION I AM FAIRLY
CERTAIN THAT IT DOES NOT ENTER THE PROGRAM. IS THERE A WAY TO TEST THE MONITOR
/CARD TO CHECK WHAT IS WRONG.
I AM RUNNING THE NEW 3D-STUDIO DRIVERS, I HAVE TRIED RUNNING THE CARD
IN VESA MODE, AS A P9000, AS A VIBRANT VESA(CARD SET TO VESA), COMBINATIONS OF
VGA. NOTHING IS WORKING. I CANNOT FIND THE 3.02G DRIVERS THAT GATEWAY
MENTIONED IN OUR COMMUNICATION, IT IS NOT POSTED ON THERE BOARD ON CSERVE.
PER GATEWAYS INSTRUCTIONS NEC 4D IS AT 32/72(640×480,16 MILL) ,
72(800×600 16 MILL), 60(1024×768,65K)
COPY TO : VIPER, ADESK, GATEWAY
<< RE: VIPER PCI ON GATEWAY 2000 P-60 WITH NEC 4D MONITOR >>
Hi Warren,
<< THE MONITOR EITHER GOES MILKY, OR THERE IS A WHITE FRECKLED HORIZONTAL BAND
IN THE CENTER. >>
Does this happen when running the video tests while configuring the viper in
"3ds vibcfg" test: YES?
You also mention VESA. Have you tried Vesa Compatibles?
jonas[adesk]
Although I have the same setup as Warren, at least I can get it to work under
the ADI drivers (it identifies my card as a Diamond Viper) and as a VIBRANT
VESA. However, VIBRANT Diamond Viper P9000 does not seem to work. It complain
about not finding some P9000.INI file. What is P9000 anyway? I found no
reference to it in my documentation for my Diamond Viper. The ADI drivers seem
ok, but require a VESA mode driver loaded for the Materials editor. Am I batty,
or can't the Materials editor go 640x480x16m?
Chad, you really need to read up on the Viper's installation instructions. When
the drivers are properly set up, the needed files exist and the machine's DOS
environment will allow them to be found at the proper times.
The Vibrant drivers should work flawlessly with your card and 3DS at all
resolutions and bit-depths it supports.
If you still have problems after getting everything set up like the book, give
me a shout.
-Alan
Trust me, I've been there. I've re-installed the drives. There are no
P9000*.INI files, just VIPER.INI. The VIPERPATH variable is set, and set
correctly. Vibrant complains. I know something is wrong, but beats me what.
Anybody have this P9000 file a can copy?
Which PCI Viper are you using, Chad? The 32-bit, 2MB version, or the 64-bit,
4MB version (Viper Pro SE)?
Which version of the Vibrant drivers are you using?
-Alan
32bit 2MB version. I got the updated Vibrant drivers. Problem solved.
Chad, try downloading the file VIB3DS.ZIP from the library here. I had the
same problems with the Viper PCI, but was able to operate it with the updated
drivers from VIB3DS. Be sure to read the following note, though.
Cheryl
Update to the Vibrant Graphics drivers which shipped with Autodesk 3D Studio
R3. Specifically, this consist of vib3ds.vlm and vibrant.res. Numerous changes.
Caution: This software has not been tested by Autodesk. Use at your own risk.
Autodesk disclaims any responsibility for supporting users running 3DS R3 with
this new set of drivers.
Note: The 1.0.4 version of this product is NOT supported by Vibrant Graphics.
We are only supporting users of version 1.0.5.
[download time at 2400 baud: 18 min]
Oh wow! Thanks, will let you know!
Oh yeah! That was it! Works great now!
Yeah; I don't know what I would have done if someone else here hadn't told me
about the new Vibrant drivers. Glad I could help.