Announcement

Collapse
No announcement yet.

How to get KX133, G400 and W2K working.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • How to get KX133, G400 and W2K working.

    If you already tried everything than just go to http://www7.tomshardware.com/mainboa...508/index.html (I suppose you are smart enough)

    1) Update BIOS (for ASUS K7V get 1005 from http://www.asus.com Downloads)
    2) Install drivers (well... does not matter which ones actualy!
    3) Go to above link and do as they say (Tom that is ;-)
    4) Be happy happy...

    Summary: f#$% VIA! ;-)
    P.S.: Now the only thing I need is different resoluton on my 19' and 15'


    [This message has been edited by Arsa (edited 09 May 2000).]
    Matrox Millenium P750 bios 1.3 - 12, P4 3Ghz HT 800Mhz, Asus P4P800 Deluxe, 1Gb DDR400 Dual Channel, Dual Seagate 80Gb S-ATA on Intel Raid level 0, Toshiba DVD-ROM SD-M1302, external Yamaha CD-RW CRW-F1DX on Firewire, Microsoft Natural Elite keyboard, Microsoft Intellimouse Optical, Viewsonic P90F, Viewsonic PF790

  • #2
    This same file also resolves the "crashing" on startup, experienced with other KX133 chipset boards, after using the "VIA Chipset Indentification Patch". Just reboot to Safe Mode. Copy the new "viaagp.sys" file to your <"X":\WinNT\system32\drivers> folder and the issue fixed.

    Mind you, shortcommings in Matrox's 5.03 drivers still exist. No, OpenGL screensavers will still dont' work. But at least WinCPUID reports AGP 2x, with sideband addressing, is enabled.

    I did find it interesting that "Dr Tom" says Asus was
    shrewd enough to use the little 'dirty' MVP3-8598-trick to make sure that AGP gets enabled in their K7V under Windows2000.
    But I'm still quite irritated that VIA "misreported" the part about KX133 support in Windows 2000! Hopefully they will come out with an improved driver in short order.

    I'm sure that the "Issue" experienced by many of us was nothing more than the fact the original driver was looking for the "8598" chipset. When this wasn't found Win2k refused to load the driver. The driver in this "patch" simply addresses the "8391" device number properly. No other changes have been made! So the issues that remain are most likely a product of this discrepancy.
    <a href="http://www.gaijindesign.com/lawriemalen/jedi" target="_blank"><img src="http://www.gaijindesign.com/lawriemalen/jedi/yoda.jpg" width="285" height="123" border="0"><br>:: how jedi are you? ::</a>

    Comment

    Working...
    X