Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - TBC-Or1on

#1
Very insightful, thank you. It says 2100, would having a late produced version be any more valuable than an early one?
#2
Just curious, a good amount of people have seemed intrigued by the stickers on the fans. I must say that I've seen a whole lot of Aavid logos, but does it change the significance at all? Thanks.


#3
Interesting. Thank you all for your time. If ABIT were to add the features in the next release that will be good.
#4
I'm sorry for not posting anything. I've been ill.
#5
QuoteOriginally posted by bloodworm

Hmmmmm. you really need to get that primary video disabled on the motherboard somehow.  what video BIOS are you running on the V5? 1.11?  I think there is a later version for the PCI?
I'm using 1.11. I don't know how to change them.
#6
QuoteOriginally posted by Nightbird

QuoteSECONDARY DEVICE -- NO ROM ALLOWED.
The card is setup like a second adapter.
A second monitor ?
The Voodoo5 5500 is my primary right now.



#7
There is something I feel I should mention though. In the Adapter tab for the Voodoo5 5500 PCI it says Bios Information: SECONDARY DEVICE -- NO ROM ALLOWED.
#8
I tried the dual display thing. As of right now the card is working. I cannot remove the Banshee. When I do remove the Banshee the computer hangs on the Voodoo5 copyright. Either way I guess I cannot complain, it's working. I have the Banshee and onboard video disabled in Device Manager. I have the latest Amigamerlin drivers installed. Thank you all for the help.
#9
QuoteOriginally posted by bloodworm

classic problem.  the onboard video needs to be disabled OR you run the monitor from the onboard, get into the video setup in windows, and make the voodoo card the PRIMARY video and the onboard the SECONDARY video.  then just "turn off" the onboard video in windows.  you will need to load one of the XP capable drivers from this here site before you will be able to set your primary and secondary things properly though.......  use the onboard video to load the drivers so you can see what's going on, eventually you will get to the point that the V5 is the only one active in windows.  keep trying, it will work.
Thank you for your reply. Could you elaborate more? By the way, when I have the power hooked up to the Voodoo5 it'll hang on copyright.
The only way I've been able to get into Windows with the card actually running was when the Banshee was also in. When I disable the onboard video from device manager I still can't use the card. I've been looking for how to completely disable it.
#10
I have the latest BIOS release for my motherboard. I'm kind of at my wit's end here. Completely stumped.
#11
Either way, when I plugged my monitor into the Voodoo5 it wouldn't work. I do not know what to do now. I'm going to check if there's a bios update for my motherboard. I put the Voodoo5 in one of my older systems and it worked. I'm trying to reject the notion that the Voodoo5 is not going to work with this motherboard.
#12
No, I couldn't get it to work so I put both in lol. The Banshee has been out of my system for awhile.
#13
Also, the Banshee works. I tried it before what I did above.
#14
Okay now this is confusing. Out of frustration I put both cards in. With the Banshee in the Voodoo5 would not display. So, I had the monitor hooked up to the Banshee. Everything went fine until I got to the user accounts screen in Windows. The Banshee quit displaying so, I plugged the monitor into the onboard video. Here's what's in Device Manager.

#15
QuoteOriginally posted by SuperFurryFurryThing

I have seen a Voodoo 5500 AGP hang showing the copyright message. but it was down to me having changed the mouse and keyboard (long story invoving a KVM switch). I would check unrelated things to see everything is ok. It might be worth re-installing the banshee to make sure that the machine still boots with the banshee. If it doesn't work with the banshee back in then you have a wierd problem that is not related to the 5500. This might sound a bit strange but this approach fixed my hanging at the BIOS problem with my 5500, it proved to be unrelated to the 5500.

SFFT
This is a good idea. I will try this shortly.