Click to See Complete Forum and Search --> : SB Live + Celeron + 3dfx = No Go ?
You have a resource problem! Could be IRQ, DMA or I/O not sharing.
I have definitely seen this happen before. Ive cured it a few times by removing one device at a time until I isolate the problem, then I will manipulate the resources for that device.
I have had to remove devices for good before also to fix this kind of thing.
BBA
jmatrix
07-10-1999, 11:29 PM
This happened to me just yesterday...I needed to rearrange my PCI cards to make room for a fan that I wanted to attache to my Voodoo 3 AGP heatsink. I needed to drop each card down one slot to make room for the fan which is on the bottom side of the Voodoo 3. Lo and behold, on re-boot everything seemed fine until I went to play an mp3 and realized I had no sound coming through my CLSB AWE 64 ISA card. Devise manager showed no conflicts in resources, but did reassign the sound card to irq 9 instead of irq 5. Knowing how finicky CL Sound Blasters products are I fooled around with the resources, specifically DMA and I/O, until I got the sound to work. This has happened to me with other computers also. Luckily, there is usually a work-around for this Sound Blaster problem: either forcing resource changes and/or deleting each card in the devise manager and then re-installing one at a time starting with the Video Card and then the Sound Card. A lot of trial and error.
[This message has been edited by jmatrix (edited 07-10-99).]
sabine urfer
07-11-1999, 12:35 AM
I recently installed a SB Live! value into my abit BH6, Celeron 300@450, Voodoo Banshee PCI, Win95B comp.
Now most of the time, the right channel is almost mute, and the soundquality is bad.
If it will work or not, decides on boot time. If I go back to 300 MHz, it will be OK most of the time, but still not always. I checked a different machine, also with 100 MHz Celeron, but with a Voodoo 3 3000 AGP card, same effect. I checked a different SB Live, also the same.
So far, I found out, that it works better, when both cards are in the top 2 pci-slots. I checked every IRQ, DMA and Address, there are no problems visible. There is no difference in resources, between the "OK GO" and the "NO GO" states of my machine.
Has anybody had the same problems? How did you solve them?
philipg
07-11-1999, 12:49 AM
Here's something to look into. When I installed the logitech Quickcam I lost my sound because of a shared DMA channel but there were no conflicts showing anywhere in the system. Just no sound.
I ended up redirecting my sound DMA to a different channel and everything is fine now.
Goto your device manager and check each devices resources for a shared setting and change whatever devices setting you are able to. Note: There won't be a visual conflict
kec95
07-11-1999, 02:59 AM
On thing I did notice when using Abit mobos is, When you first install the OS, Set the PNP OS in the bios to NO. This will prevent ALOT of IRQ problems.
I also set "assign IRQ for VGA" to disabled as well as "assign IRQ for USB" to disabled.
I never had a problem since.
All my cards work fine regardless of what slot there in. and my USB videp camera works great also.
Abit also recommends using PCI slots 1 and 2 first for cards that require IRQ's. I read that on there web page's FAQ section.
Just my experiences.
Kenny C
kec95
07-11-1999, 03:24 PM
Ever consider trying to run WIN98 instead??
Im not saying WIN95 in incapable, but WIN98 is a little smarter and maybe a little more DIRECT X friendly.
Just a suggestion.
Kenny C
sabine urfer
07-11-1999, 04:19 PM
Maybe I can find someone sponsoring me a Win98?!
Anyway, as I understand, Win98 is also NOT coming with DirectX6.1? Maybe I lend out my machine for some Win98 testing http://www.sysopt.com/forum/smile.gif.
sabine urfer
07-12-1999, 12:43 AM
Oh dear, I'm becoming too old for this. No, not troubleshooting hardware, the horrors after realising, that the load bang I just heard was my 'puter hitting the concrete after hopping out of the chair, I placed it in to make room on the workbench. Luckily, except for some nasty dents on the case and two missing keys on my keyboard, anything else cold just be shoved back to the "standard" positions and is working well.
But back to the point. I tried to move around the cards a bit more, that didn't help. I tried to manually set some IRQs differently, the problem still stayed with me.
I reinstalled windows from scratch, the problem seems to start, after installing Directx 6.1.
I double checked again every resource for double use, found none.
I don't have to reboot the comp, it's enough, to do a windows restart to provoke the sometimes go sometimes nogo effect.
What I found out so far, is that Win NT4 is not having this problem. Everything is working smooth there (if you have NOT installed servpack4, otherwise it's a complete FREEZE there, but that's a different story...).
NT4 is using the exact same IRQs and I/O ports as Win95.
A visit to the sblive.com site didn't help either.
Any further hints? I'm profoundly stuck.
[This message has been edited by sabine urfer (edited 07-11-99).]
Petec
07-19-1999, 10:53 PM
.... win98 Second Edition come with Diretx6.1
Keep playin with the PCI slots.
My Ultra66 pci card and SBlive had the same problem untill I found the Right Combination
SysOpt.com
Copyright Internet.com Inc. All Rights Reserved.