Jump to content
Compatible Support Forums

PieterPan

Members
  • Content count

    3
  • Joined

  • Last visited

    Never

Everything posted by PieterPan

  1. I'm getting really desperate now. I spent 1 whole day trying to get windows 2000 to recognize my TNT and actually USE it. But everytime I get the error in the device manager "This device cannot start. (Code 10)" I have the 2195 build. I downloaded the latest bios for the motherboard, NJ V1.22 (www.bp6.com), I tried the new and the old bios for my Viper V550 TNT, all to no avail. I have tried pretty much every driver that is available for the TNT: The MS driver that comes with windows (Viper V550), The MS NVidia driver (NVidia RIVA TNT), and the 69, 75 and 76 driver from the internet from NVidia (NVIDIA RIVA TNT). NONE OF THESE BLOODY WORK I always get the 640*480*16 colors or the 800*600*16 colors at 60 hz. This is very depressing. Now here comes the juicy bit: I have a dual celeron with the Abit BP6 motherboard. I have tried MPS Multiprocessor PC and the MPS Uniprocessor PC. NEITHER work. The video card works flawlessly on BeOS and on Win98. I have read that a lot of people have problems with the TNT drivers, but that is usually for games. (like OpenGL and Direct3d) I really hope someone else can help me out here, Thanks in advance for anything. Pieter
  2. PieterPan

    DESPAIR: Viper 550 TNT on BP6 motherboard

    I had been looking around the forum, but I guess I didn't go back far enough to find it. I am new to this place, so I missed out on a lot of messages For those of you interested in BeOS, visit the following sites: www.benews.com Nice newssite www.beoscentral.com another newssite www.begroovy.com New newssite, very nice www.bebits.com VERY nice site where people publish their programs www.thebesite.com Newssite www.begamer.com beGames And ofcourse www.be.com, the makers of BeOS. Check out fttp://free.be.com for the soontobereleased beos 5.0
  3. PieterPan

    DESPAIR: Viper 550 TNT on BP6 motherboard

    I fixed it... If anyone is having the same trouble as I was, go to the bios and enable "assign IRQ for VGA". I had disabled it for BeOS a while ago. It's a miracle I though of it. Wow.
×