SB Live! Demon VANQUISHED ! ! !

Before I get into the details, I just want to say that I could kiss Jari Korhonen, wherever he may be. (OK, I know he lives in Finland, and I have his e-mail address, but a little <b>good</b> publicity never hurt anyone!) <b>THANK YOU JARI!!!</b>

A while back I stated that I was having a problem with my SB Live!, and that it had seemingly gone away, and then came back again. When I was cleaning off my desk the other day, I remembered why the problem had come back . . . I had recently purchased a Hercules 3D Prophet II MX. How did this come to me? I found the sheet I had printed out from the Herc site re: sound cards making "crackling" noises with the Prophet. (See link below...)

<A HREF="" target="_new"></A>

I had done that in October, and tried the suggestions, making sure that the IRQ 5 in the BIOS was set to Legacy ISA, but that did not work (read more below). I failed to return to the site to click on the link inside the article that takes you to the GE Force FAQ re: sound crackling. So, on New Year's Eve I went there, and last night I finally tried the suggestions found therein. I have some questions about some of the tweaks, but I will save them for the end and get to the good stuff now.

The Tenth Bullet was my saving grace, the Lawgiver which gave my SB Live! Demon the Double Whammy (alright . . . ending this corn-o-rama). I have the EPOX Apollo MB with the Via MVP3 chipset, so I followed the link given which contained a tiny 35KB program to put in the Start Up folder which sets the CPU-to-Bridge Latency to 0. I rebooted and started up Serious Sam and perfecto! No crackling, shimmering, or any other form the Demon had taken in the past. I was sooooo stoked that I blew myself up listening to the beautiful boom sounds that the rocket makes when hitting a wall about 5 feet in front of you, rather than the "Oops! I hit a baseball through the paranoid neighbor's window which is covered with tinfoil!" sound which I have been getting for the longest time.

The FAQ states that this fix is specifically for the VIA MVP3 MBs, but there is also info about VIA KX133 MBs. If you have one or the other, I <b>highly</b> recommend checking this out. Oh, for other MBs, it has a link for TweakBIOS program which may also work.

OK, questions for you BIOS gurus and other IRQ nuts (the following were all done prior to the Latency Timer setting I mentioned above):
In the PCI/PnP IRQ section, the following IRQs were set to Legacy ISA: 3, 4, 7, 14, & 15. PCI/ISA PnP had the rest, IRQs 5, 9, 10, 11, 12, and all the DMAs. I had switched IRQ 5 to Legacy ISA, but nothing changed. I am going to leave it switched, but what about the rest?
<b>Question 1</b>: Should I set my IRQs in this section differently, or leave them the f@#k alone?

In Windows 98, my SB16 Emulation is IRQ 5, the Live! is IRQ 9, and my Prophet is IRQ 11, which is shared with my 56K "blazing fast!" modem.
<b>Question 2</b>: Should I switch the modem to another IRQ, or leave it the f@#k alone? Are the other IRQs kosher, since they are not sharing?

Another suggestion in the FAQ was disabling the PCI Delayed Transaction in the BIOS. I did it, but nothing changed.
<b>Question 3</b>: Should I re-enable the PCI Delayed Transaction option?

Well, that's all for now . . . if I think of anything else, I will add it later. I hope this helps out some of you, and I appreciate all of the help I have received and the engaging discussions I have read in the past.


<i> Thoughts are thinking; Thunk from knowing
<b> nwod </b> gniog em peek reverof sthguohT </i>
1 answer Last reply
More about live demon vanquished
  1. OK, here's a little more info, straight from the readme file:


    <i>This program sets chipset CPU-to-PCI Bridge (PCI bus#0, function#0 and device#0) latency timer to 0 clks (according VIA's documents there is still fixed granularity of 8 clks in MVP3 chipset).
    Setting latency timer to 0 might fix graphics card caused sound crackling.

    Supported OS's and chipset's:
    This program work's only in Windows9x. Only VIA MVP3 chipset tested by the author. Program runs and sets PCI bus#0, function#0 and device#0 offset D to 0 all chipset's that support PCI configuration mechanism #1.

    Q: Are you going to make Windows 2000 version?
    A: No, But Tibor Schütz has made NT4/W2000 version.</i>
    <A HREF="" target="_new"></A> (German)
    <A HREF="" target="_new"></A> (English)

    <i>Q: 0 clks doesn't work, can you send me latency.exe with different value?
    A: You can get different latency timer value by little hex-editing, instructions:
    Get a hex-editor and change byte in offset 413H to desired latency value.</i>


    If anyone can post what setting the "chipset CPU-to-PCI Bridge latency timer to 0 clocks" actually does, please do. Also, if anyone can explain what the individual timers are (i.e., PCI bus, function, and device), please do.

    Hope this info helps some, and hope some can help with the info. :wink:


    <i> Thoughts are thinking; Thunk from knowing
    <b> nwod </b> gniog em peek reverof sthguohT </i>
Ask a new question

Read More

Sound Cards Components