Subject: | |
From: | |
Reply To: | |
Date: | Tue, 23 Jun 1998 18:18:54 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
I have a different configuration, but just installed a Viper 330 AGP in my
system, so this may help. First check your Motherboard documentation or Web
Site for instructions on using AGP. Then, you must load the USB supplement
found on Win95 ver. 2.1 or higher CD ROM--apparently it contains files needed
for AGP to properly communicate with the O/S. I also had to load DirectX ver.
5. After doing all of that, then I downloaded the latest Viper Drivers from
www.diamondmm.com (specifically for AGP) and it works like a charm. Also, the
Nvdia Chip likes to use an IRQ, check your bios setup to see if you've enabled
VGQ IRQ or something like that for your board. Hope this helps.
Dan Shaughnessy
Miguel Morillo wrote:
> Just installed an OEM Diamond Viper 330 AGP card on an AOpen AX6L
> motherboard, Pentium-II 233MHz with 96 mb of SDRAM and to my surprise in
> Win 95B and games like Total Annihilation, the tint of the screen is either
> blue or yellow. Using the bundled InControl Tools just adjust the colors of
> blue and yellow but NO red. I tried three monitors on this card with the
> same result.
>
> Device Manager shows this even before installing the drivers for the card:
>
> At the Device Manager, there appears to be a resource conflict:
>
> Conflicting Device List
>
> Memory Range D8000000 - D8FFFFFF used by: Intel 8223LX Pentium(r) II
> Processor to AGP controller
>
> Memory Range A8000000 - A8FFFFFF used by: Intel 8223LX Pentium(r) II
> Processor to AGP controller
>
> Changing the conflicting addresses above would result in the system hanging.
>
> Operating System & Version -> Windows 95B
> Motherboard make and model ->AOPen AX6L
> Processor type and speed -> Pentium II 233 mhz
> Monitor make and model -> Viewsonic 6FS
> Video driver version ->4.10.01.0126
> Video bios version ->1.50
> Other peripherals and add-on cards -> Diamond Sonic 64 PCI
>
> Thanks in advance!
>
> Miguel Morillo
> [log in to unmask]
|
|
|