soundblaster audigy1 gamer not detecting

i got a new mobo and my motherboard refuses to detect when i install drivers, it shows up in Other Devices with a question mark next to it in device manager. i have disabled my onboard sound and it still doesn't work. help?

gtfo winfag

>>2

Maybe investigate the question mark. Or lurk Creative forums.

If you decide to investigate the question mark, start here: http://en.wikipedia.org/wiki/Question_mark

you guys are no help D:

>>6
you think /g/ was being helpful and kind when they said to come here? You realize we troll harder than /b/tards in here right?

>>7
VIP Quality ;)

>>6
I'm >>4 and I was being serious.

>>9
I am going to stop trolling for a few minutes. This only happens like once a week so listen up

You can really have some good times with your computer. You seriously should learn to fix it yourself. Nobody cares about how it runs but you. If you take it to some jackhole and tell him to fix it, it's not going to get done right. Even if you have a father/brother/boyfriend/whatever that you LIVE with who is a Lunix tard and fixes computers for a living, he can't fix it like you can. Even if you're mediocre at best dealing with hardware. Only you use it enough to make a true diagnosis of your computer's health.

Start troubleshooting. Rule everything you can out, then make an educated guess about the source. You know where all the components came from (or have at least a good guess). You know that hard disk failure is probably not the culprit because it's new. Did you install Windows from scratch on it, or did you use some utility to move it from your old disk (like MaxBlast/dd/etc.)? Can you consistantly get your disk to register in the BIOS? Can you make it consistantly fail? If either is true, you found the cause. Try replacing the IDE cable. If that fixes it, you found the cause. Try removing one stick of RAM and see if the problem happens still. If so, take it out and try the other. If still, try one stick in the other DDR channel or another slot. If that still doesn't fix it, you ruled out a RAM error too. Remove all PCI cards but the graphics. Remove all other disk drives. If this doesn't fix it, you've ruled out the possibility of a power drought (not enough power from the power supply causes brownouts that show this kind of behaviour).

Try anything else reasonable you can think of. If all else fails, you have a bad IDE channel on the motherboard. In that case, you need a new motherboard.

its on a fresh copy of winxp with sp2, i disabled the on board and now it shows up as detected but i still don't have sound. i've tried every pci slot on the board and its all the same

Then your computer PHAILS

now that the drivers are recognized you need to tell windows to use them.  Double click the speaker >> properties >> Mixer Device >> SB Au whatever.

I've actually never had to do this since most Creative products make themselves defaults at install, but there can be a first for everything.

>>10

hey are you still around? Could you tell me what compelled you to copy pasta that? (I wrote it). Am I a retard? Are you doing it because it needs to be told to practically everyone who posts a support thread here?

I'd like to hear from you with questions/comments/feedback!

ps >>1 eat a dick and gtfo

>>14
I am going to stop trolling for a few minutes. This only happens like once a week so listen up

You can really have some good times with your computer. You seriously should learn to fix it yourself. Nobody cares about how it runs but you. If you take it to some jackhole and tell him to fix it, it's not going to get done right. Even if you have a father/brother/boyfriend/whatever that you LIVE with who is a Lunix tard and fixes computers for a living, he can't fix it like you can. Even if you're mediocre at best dealing with hardware. Only you use it enough to make a true diagnosis of your computer's health.

Start troubleshooting. Rule everything you can out, then make an educated guess about the source. You know where all the components came from (or have at least a good guess). You know that hard disk failure is probably not the culprit because it's new. Did you install Windows from scratch on it, or did you use some utility to move it from your old disk (like MaxBlast/dd/etc.)? Can you consistantly get your disk to register in the BIOS? Can you make it consistantly fail? If either is true, you found the cause. Try replacing the IDE cable. If that fixes it, you found the cause. Try removing one stick of RAM and see if the problem happens still. If so, take it out and try the other. If still, try one stick in the other DDR channel or another slot. If that still doesn't fix it, you ruled out a RAM error too. Remove all PCI cards but the graphics. Remove all other disk drives. If this doesn't fix it, you've ruled out the possibility of a power drought (not enough power from the power supply causes brownouts that show this kind of behaviour).

Try anything else reasonable you can think of. If all else fails, you have a bad IDE channel on the motherboard. In that case, you need a new motherboard.

>>14
And for the reason:
 - The first paragraph is gold
 - It's tl;dr
 - It's general enough to apply to every post in /comp/

>>15
hey are you still around? Could you tell me what compelled you to copy pasta that? (I wrote it). Am I a retard? Are you doing it because it needs to be told to practically everyone who posts a support thread here?

I'd like to hear from you with questions/comments/feedback!

>>17
I am going to stop trolling for a few minutes. This only happens like once a week so listen up

You can really have some good times with your computer. You seriously should learn to fix it yourself. Nobody cares about how it runs but you. If you take it to some jackhole and tell him to fix it, it's not going to get done right. Even if you have a father/brother/boyfriend/whatever that you LIVE with who is a Lunix tard and fixes computers for a living, he can't fix it like you can. Even if you're mediocre at best dealing with hardware. Only you use it enough to make a true diagnosis of your computer's health.

Start troubleshooting. Rule everything you can out, then make an educated guess about the source. You know where all the components came from (or have at least a good guess). You know that hard disk failure is probably not the culprit because it's new. Did you install Windows from scratch on it, or did you use some utility to move it from your old disk (like MaxBlast/dd/etc.)? Can you consistantly get your disk to register in the BIOS? Can you make it consistantly fail? If either is true, you found the cause. Try replacing the IDE cable. If that fixes it, you found the cause. Try removing one stick of RAM and see if the problem happens still. If so, take it out and try the other. If still, try one stick in the other DDR channel or another slot. If that still doesn't fix it, you ruled out a RAM error too. Remove all PCI cards but the graphics. Remove all other disk drives. If this doesn't fix it, you've ruled out the possibility of a power drought (not enough power from the power supply causes brownouts that show this kind of behaviour).

Try anything else reasonable you can think of. If all else fails, you have a bad IDE channel on the motherboard. In that case, you need a new motherboard.