Warp2Search.net » News » July 2005 » Creative Sound Blaster Live! 24-bit & Audigy: MediaSource Go & Utilities
Creative Sound Blaster Live! 24-bit & Audigy: MediaSource Go & Utilities
Posted by: Newsfactory on: 07/29/2005 05:59 PM [ Print | 11 comment(s) ] · 3736 views
Just got word from our bro's over at Station-Drivers.com, that they have Creative's Mediasource Go! Which was snagged from a Sound Blaster Live! 24-bit driver CD and also works on the Audigy Series.
Mediasource Go version 2.20.06 MediaSource CD-Rom Burner Component 3.10.12 Creative Music Blind Plugin 1.00.12 MediaSource Detector 2.10.08 Creative Device Control 1.20.08 EAX_CONSOLE 2.10.13 Creative Restore Defaults 2.10.04 SFBANK_Manager 3.10.18 SPEAKER_SETTINGS 1.60.12 Surround Mixer 3.60.16 WAVESTUDIO 6.20.11
Creative Sound Blaster Live! 24-bit & Audigy: MediaSource Go & Utilities
Mediasource Go version 2.20.06 MediaSource CD-Rom Burner Component 3.10.12 Creative Music Blind Plugin 1.00.12 MediaSource Detector 2.10.08 Creative Device Control 1.20.08 EAX_CONSOLE 2.10.13 Creative Restore Defaults 2.10.04 SFBANK_Manager 3.10.18 SPEAKER_SETTINGS 1.60.12 Surround Mixer 3.60.16 WAVESTUDIO 6.20.11
Creative Sound Blaster Live! 24-bit & Audigy: MediaSource Go & Utilities
« ForceWare 77.77 for Windows XP 64-bit · Creative Sound Blaster Live! 24-bit & Audigy: MediaSource Go & Utilities
· DirectX 9.0 SDK August 2005 Update Realeased »
Comment
|
vacantmind Unregistered |
#61804 Posted on: 07/29/2005 10:53 PM
Creative sucks.. get a different soundcard if you have a creative card. Worst sound products... EVER. |
Comment
|
ewwhww01 Unregistered |
#61806 Posted on: 07/29/2005 11:42 PM
Please stop posting your anti-Creative stuff here. I wish I could kill file you like I can on newsgroups. |
Comment
|
ChrisW Unregistered |
#61807 Posted on: 07/30/2005 02:42 AM
Can someone please report this ***** jerk to the mods ? I'm looking for PM details of the owners, or mods, to PM them about this shit. Listen to me VacantBRAIN, take your ***** sad pathetic anti-creative shit, and fuckoff somewhere else you complete ***** jerk. It really shows just how old you are, and your stupid mentality. Prick !! |
Comment
|
Valagard Unregistered |
#61808 Posted on: 07/30/2005 03:01 AM
This worked perfectly with my Audigy LS, now I have new sound options in my control panel I diden't have before. Thanks W2Search |
Comment
|
Faust Unregistered |
#61809 Posted on: 07/30/2005 04:19 AM
I believe 99.9% of any hardware problems lay between the chair and the keyboard. I'm surprised vacantmind can even post anywhere. |
Comment
|
Astro Unregistered |
#61810 Posted on: 07/30/2005 05:05 AM
I bet this kid will be the first to buy an X-Fi.. |
Comment
|
derfie Unregistered |
#61812 Posted on: 07/30/2005 05:36 AM
The idiot always says the same thing. Just goes to show you how vacant his mind really is. |
Comment
|
ocyl Unregistered |
#61813 Posted on: 07/30/2005 06:05 AM
Or it can be that Creative's drivers really do suck bad ;O (not saying either way, just chatting along) |
Comment
|
x243x Unregistered |
#61814 Posted on: 07/30/2005 12:55 PM
Creative cards like the original SoundBlaster Live! and other PCI SoundBlaster series cards did have problems with many chipsets around 1999-2002. At the time, VIA was a very popular chipset maker, and comprised the majority of AMD motherboards as well as some Intel boards. The problem was that the Creative cards would output scratchy, crackly sound and sometimes even corrupt harddrive data. This was due to latency problems with the PCI bus. Sometimes the problem only happened on boards that issued the Stop/Halt Thread command to the processor for thermal throttling. The problem was Creative's and not VIA's. This problem happened even on non-VIA chipsets, but more rarely. For instance, I can replicate the problem on a PIII ALi chipset based board (the TUA266) and it will cause problems with keyboard/mouse detection and harddrive transfer speed. To this day I can still plug in my old Live! or Soundblaster 16 into my old VIA KT133 board that I have lying around and get crackly sound. There were some fixes and patches posted for the problem, but they never came from Creative. Geoge Breese comes to mind. Today, Creative cards don't really have the same compatibility issues that plagued them years ago, but there are still some. More than likely though, the problems now come down to a defective soundcard or motherboard and not an inherent manufacturing flaw. |
Comment
|
MB Unregistered Posts: 26 Joined: 2004-05-21 |
#61827 Posted on: 08/01/2005 12:47 PM
Get your facts straight. These problems were only mainboard problems since they also occured with other soundcards like Turtlebeach and Teac. Those problems never or extremely rarely happened with other than VIA mainboards. It was the time when there were still LOTS of other good soundcard makers out there and they all had problems with VIA chipsets. This was also the time when onboard sound got popular. I wonder why.... Youre talking about the KT133 chipset. Go check the internet and you will see that this was one of the worst made chipsets ever made by VIA and had various problems. No wonder VIA always made a new version of their chipsets at that time (133a, 266a, etc) Do you remember the horrible PCI transfer speed problems of pre-(and including)KT266A chipsets? And because those patches never came from creative, but were instead patches that fucked with the mainboards it proved again it was ONLY VIAs fault. And yes, I had those mainboards aswell. and all went well when I switched to a different chipset brand (ALi, Intel, AMD). Though there was no real alternative to VIA at that time if you had an AMD CPU, I took older (but still available) AMD chipsets and they proved to be very mature and stable. But because of their age not the fastest anymore. |
Comment
|
Mertsch Senior Member Posts: 2708 Joined: 2002-08-22 |
#61828 Posted on: 08/01/2005 02:56 PM
very true ! I was so happy switching to nForce after the VIA suckage the KT133A worked very well and still does work well but what was between KT133A and KT800 sucked very very much ... and yes I had those problems, too |
