Reviews:
 ·Verizon Online DSL
 ·Verizon FiOS
| Do Via chipsets have comp issues with Audigy? Do via chipsets have compatibility issues with Audigy soundcards? I'm having trouble with my KT333 mainboard, and my Audigy soundcard it seems. I thought I read somewhere that people are having trouble with this combination... but I'm not sure.
btw Codezero... your more than welcome to blast Via here. 
--
Who cares about ET? Use your spare CPU cycles for a real cause, Join Team Discovery today! |
|
 ARPremium,ExMod 2001-04
join:2000-09-21
Toronto, ON | No problems with my Audigy Mp3+ and Abit Kx7-333.
--
What? Me worry? |
|
| reply to z28kindaguy
I had no problem running this setup asus a7v333 and audigy. My company was using this setup for over a year with no problems. I know there was a few problems at the start. Some blamed via some blamed creative. I blamed creative as there driver support was crap  . You should take a look in the creative forums as I have found it to be very helpful in the past. |
|
 CylonRedPremium,MVM
join:2000-07-06
Bloom County | reply to z28kindaguy
Some people have problems with Creative sound cards and VIA chipsets and others have had the exact same problems with Intel chipsets. You might have problems - you might not. The problem is Creative's problem and they fail to correct it for both chipsets.
I personally refuse to buy any Creative products for this reason among others....
--
Brian
CylonRed in the AOLL
"Just on the border of your waking mind........" |
|
 MarkPremium
join:2001-11-15
Mesa, AZ
kudos:1 | reply to z28kindaguy
My feelings exactly Cyclone, there is a nice alternative available too, the turtle beach.  |
|
|
|
Reviews:
·Verizon Online DSL
·Verizon FiOS
| said by Mark:
My feelings exactly Cyclone, there is a nice alternative available too, the turtle beach.
Looks like I'm buying another one... I'm having no trouble with the one that's in my secondary system.
--
Who cares about ET? Use your spare CPU cycles for a real cause, Join Team Discovery today! |
|
 C0deZer0Oc'D To Rhythm And PolicePremium
join:2001-10-03
Davenport, FL | reply to z28kindaguy
Audigy + VIA chipset = registry meltdown
Though I did manage to get the Audigy to work when I installed the latest chipset drivers before installing the Audigy, I still had overall hell keeping the machine up and running with that combination.
Switching to an nForce board fixed that problem of course
Though I guess it depends more on the generation of the chipset and chipset driver version more than anything. I Just know damned well that I won't be getting another VIA-based anything as long as I can help it 
P.S. I'm biased against VIA, but my experience w/ the KT266 chipset and a faulty Epox board is enough to make me stick to my guns
--
Free SAT review: VIA is to chipsets as AOL is to ISPs. |
|
| reply to z28kindaguy
the via+audigy thing is in the past...via has grown out of THAT incompatibility. |
|
Reviews:
·Verizon Online DSL
·Verizon FiOS
| reply to C0deZer0
I guess I can troubleshoot all of this by sticking in a cheapy crystal audio sound card before I pluck down some cash on another TB. This just sucks... I'm also thinking I have just a bad mobo, because this Audigy was working in my Abit KG-7 Raid.. (which has AMD northbridge.)
--
Who cares about ET? Use your spare CPU cycles for a real cause, Join Team Discovery today! |
|
| reply to z28kindaguy
I have an Abit KR7A-133RAID board with the VIA KT266A chipset. I have a Creative Audigy Platinum board running without any problems. What I would suggest is that you install the sound card first, if you're building a new system, and then install the latest drivers. Of course, that is after the video card otherwise what's the point!!
I love this board and the sound out of my 5.1 speakers is fantastic. I have a Santa Cruz sound card in my other machine and prefer the sound quality from the Creative board.
--
I Am Strong, I Am Invincible, I Am Woman. I Am Tired.LadyHawk57 |
|
 mmI Did It My WayPremium
join:2001-04-07
Matawan, NJ | reply to z28kindaguy
No issues with the KT266, KT333 or KT400 chipsets and my Audigies. I had lots of issues with the KT133a chipset (Not only Audigy issues). |
|
 chmodPremium
join:2000-12-12
Lockport, IL | reply to z28kindaguy
I ran a live! gamer on my old kt133 board without a hitch for a few years now it resides in my 850e p4 rig still running great. |
|
 dbmavenThere's no shortagePremium,Mod
join:1999-10-26
Sty in Sky
kudos:2
 ·VOIPo
 ·Optimum Online
Host:
Filesharing Software
No, I Will Not Fix..
Road Runner
Bright House Netwo..
Computer Hardware ..
| reply to C0deZer0
said by C0deZer0:
Audigy + VIA chipset = registry meltdown
You always make it sound like anything to do with VIA doesn't work with anything else. Be more specific and state what board and what chipset you had a problem with.
Just like gquiring, I've built plenty of VIA/SB (LIVE!, LIVE! 5.1, and Audigy) systems and have never had a single installation, driver, or stability issue. Of couse, I was smart and/or lucky enough to have avoided the KT133/133A chipset, which was widely known to have issues.
I don't mind (actually, I appreciate) your experience(s). What I don't like are the generalities.
If you wouldn't mind, PLEASE be more specific.
--
"Q: When will it be done? A: When pigs fly! " |
|
CylonRedPremium,MVM
join:2000-07-06
Bloom County | said by dbmaven:
said by C0deZer0:
Audigy + VIA chipset = registry meltdown
You always make it sound like anything to do with VIA doesn't work with anything else.
I really do think he thinks that....
--
Brian
CylonRed in the AOLL
"Just on the border of your waking mind........" |
|
Reviews:
·Verizon Online DSL
·Verizon FiOS
| said by CylonRed:
I really do think he thinks that....
Yeah.. Codezero has issues with via... but its cool.. sometimes funny.
--
Who cares about ET? Use your spare CPU cycles for a real cause, Join Team Discovery today! |
|
C0deZer0Oc'D To Rhythm And PolicePremium
join:2001-10-03
Davenport, FL | reply to z28kindaguy
Well, I was hoping that I wouldn't have to repeat myself, but here goes.
In my experiences, VIA has shown that it is a company that shows complete and utter disregard for its users. Not only do they make some extremely horrid, unstable chipsets, but they can't even support their own stuff or keep up to date the drivers they put out.
First, long, drawn-out and overly painful example: Epox 8KHA (VIA KT266 chipset).
This is the board that will live in infamy for me, and nearly scared me away completely from ever building my own computer, it was so bad.
First day I got it, and finally was able to set it all up, it wouldn't recognize the processor correctly, so it wouldn't finish POST.
The BIOS updating was also a nightmare on that machine compared to every other motherboard I've worked with. It apparently didn't like it the first time, and it in the end needed to be flashed three times in order for the processor to be recognized correctly, and for the thing to work.
Secondly, the overall stability of the thing to begin with was terrible. Its IRQ assignments were all farked, and even with freeing up about 5 by disabling most (if not all) of my legacy ports, there was IRQ sharing galore. It wouldn't even run the memory at stock. I had to scale it down to using PC1600/DDR200 spec in order to get it to let me finish POST and move on to booting the OS.
Finally, when I could get into the OS Setup and actually booting up into it, my problems were far from over. First, i was told that I shouldn't need to install the 4-in-1 drivers, because "XP Pro has them built in." WRONG. Tried to install Audigy without the 4-in-1's, and I get this lovely message showing up on my screen only a mere two reboots later: said by system w/o 4-in-1 drivers:
Registry Hive:
/Software/**
is either corrupt or missing,
or its backup or alternate.
This is where the real fun began, for I could never have the machine up and running more than a week, all because of all the millions of other conflicts.
The 4-in-1 drivers installation was a horrid routine, and would hang constantly. The only thing they ever did was keep that registry meltdown from happening when I installed my Audigy. It caused many other conflicts beyond that.
•Instability running games•still couldn't run memory even @ stock•Conflicts With Roxio's GoBack (this was the first and only time I've ever seen GoBack complain about anything
The list went on. Epox's support was absolutely non-existent, and I had tried everything recommended to me in the MS help forum and here, and still no luck. I couldn't even find a single driver revision at the time that would let the Ti200 work right on that motherboard. Then it had to go let my system overheat when running Jedi Knight II demo.
In its glorious finale, the board decided to kill itself, and take the hard drive with it (60GB WD Caviar HDD, bought @ Circuit City). Needless to say, after the long problems I had with both WD and this board, I was sure I wouldn't be giving either anymore business. The HDD was returned, so I could get my $$$ back and get a fresh new Maxtor. The only thing left of the motherboard is the northbridge fan.
Second, now very glaring annoyance: VIA VT6202 USB2.0 chip
I was glad to finally have a working board when I got my NV7-133R. At first, I was very weary to see the "VIA" chip on there, being there to handle USB2.0. But then I thought to myself, "Surely, they could at least make a proper chip for one function, right?"
Big mistake. Driver that came with the cd doesn't work. Had to go online to find a working one for it. Its last revision was almost 2 years old.
Went to VIA's many different sites for any sort of updated driver, but alas, VIA in its infinite wisdom decided to drop support and quit making anymore updated drivers for their own chip. Nice move there.
Even now, I still can't use the USB2.0 ports right, because the only thing that can work with them right now is my HP Printer.
I plug in my Logitech Gamepad on them, and it prompts a reinstall of the drivers everytime. Also, the apps and such that I would put it to use with don't recognize it when it's on those ports. It's fine on the 1.1 ports, but not these.
I plug in my Intel PC-cam on the USB2.0 ports... I get a hard lockup (requiring a power-off), and at worst cases, a BSOD.
VIA is the most worthless company I've seen. Their driver support is horrid, their chips are absolute garbage and even their newest crap still has compatibility problems out the yin-yang.
If I have to choose between VIA and Intel for my next machine, I'm buying a Mac. I love AMD for their CPU's, but I refuse to put another VIA product in my machines again.
Does this explain my POV for you?
--
Free SAT review: VIA is to chipsets as AOL is to ISPs. |
|
ARPremium,ExMod 2001-04
join:2000-09-21
Toronto, ON | said by C0deZer0:
in my machines again.
Does this explain my POV for you?
Sure. But when you make general statements like "Audigy + VIA chipset = registry meltdown ", that is not spelt out as a PoV, it is mentioned as a fact which is misleading to someone who has no knowledge of the issue.
Nitpicky, probably.
--
What? Me worry? |
|
| reply to z28kindaguy
never had a prob with via chipset code...guess im extremely lucky...eveyone pray for me as i stick the sb live 5.1 in my tk333
--
U R B stupid! Yes you r is stupid! |
|
CylonRedPremium,MVM
join:2000-07-06
Bloom County | reply to C0deZer0
said by C0deZer0:
Well, I was hoping that I wouldn't have to repeat myself, but here goes.
Nope - you did not have to repeat yourself - but it does show people that you really have problems with the company that made the motherboard - not VIA....
--
Brian
CylonRed in the AOLL
"Just on the border of your waking mind........" |
|
 MajinKenshinToo Much Talking, More Fighting
join:2002-04-10
UK | reply to z28kindaguy
I've got to defend CodeZero again on this one
I have previously posted this link in another thread, and i do believe that it is once again warranted for this discussion:
»www.matrox.com/video/support/rtx···sets.cfm
Have a look at the unsupported chipsets, oh look, all VIA chipsets are incompatible, all the way up to the KT400(i'm sure their newer P4 chipsets still have the same problem and Matrox couldn't be bothered to list them).
For any PCI device that needs any amount of bandwidth, the VIA chipsets are deemed.....useless, unless anyone can prove otherwise, I'd appreciate it if a website could actually run some latency/bandwidth tests on everyones chipsets, that would kill this discussion completely.
There is no way in hell that I'd buy a motherboard that had any kind of VIA chipset on it.
--
If you think things can't get worse it's probably only because you lack sufficient imagination. |
|
