building new rig for first time, having trouble

DukeGamma

Junior Member
Feb 11, 2002
16
0
0
the m/b im using is an ASUS A7V266-E VIA KT266A Socket A RAID 3DDR 5PCI Audio ATX
i installed windows xp home and everything seemed fine until i tried to set up my video audio and nic
i disabled the onboard audio and lan however i still have problems.
i have 2 unknown audio controllers and the network card i have is showing up as Net 1394 and i cant get the drivers installed for it. also there is a unknown video controller which i cant get to install.

i had the motherboard set for jumperfree so i did all the setting changes in the bios, thats not the problem.

email me dukegamma@gamercenter.com

all help is extremely appreciated.
 

DaiShan

Diamond Member
Jul 5, 2001
9,617
1
0
have you upgraded to the latest Via 4 in 1's? Also which video card are you using? if it is geforce based, do you have the latest dets for xp? Also I can see why you disabled audio, if you want to use your own card, but why the onboard LAN? Also could we get a complete run down of what is in your system?
 

mee987

Senior member
Jan 23, 2002
773
0
0
net 1394 = firewire (not sure exactly how that relates to your problem)

please tell what video, sound, and network cards you have in the system
 

DukeGamma

Junior Member
Feb 11, 2002
16
0
0
video is an inno3d geforce 3 ti500
soundcard is a creative audigy
nic is a linksys network everywhere 10/100 (NC100 v2)

for some reason under network adapters xp is listing the 1394

i installed the 4in1s that came with the m/b, i'll see if i have newest ones
 

DaiShan

Diamond Member
Jul 5, 2001
9,617
1
0
yah go grab the 4.37's, and grab the latest dets if you haven't, also grab xp sound drivers for your audigy
 

Woohah

Member
Feb 19, 2002
29
0
0
If the audigy is anything like the live series, then windows won't have a damn clue what it is when you first install. Remove the "phantom sound card" hardware and when they're redetected by windows point them to specific drivers, either on CD or file.

This is the only way to get stuff to work in Win98 upon install if it's not detected correctly, and I'm guessing it's similar in XP.

Bottom line: If windows doesn't know what it is, you have to tell it what it is. :)