corrupted sound heard

Hi everybody,

I'm using WIN98SE 64MB RAM On a VIA motherboard

last time i got my computer upgraded, they removed my sound card and they told me to use the one who's burned on the motherboard instead.

Well, at the first few days after the upgrade, it all sounded okay.
But after that, I started hearing some noises and ticks when i heard music and even system sound.

I downloaded & installed the latest version of the motherboard audio drivers but it didn't changed it even a bit!

maybe the reason for all that is that I just don't have a sound card? maybe the motherboard doesn't allocate enough memory for the audio PCI bridge?

How could I fix this problem?

 

last time i got my computer upgraded, they removed my sound card and they told me to use the one who's burned on the motherboard instead

#1 right off the bat. That should heve been YOUR CHOICE not theirs. If it were me I would be on their butts ( big time ) and have the sound card back.

Also I had the same problems with onboard audio and was told by the shop Tech where I bought my motherboard to disable it and use a plug in card.

Followed those instructions and have not had a problem with audio since.

BillyBob

 

At the very least you should have had the sound card in a anti static bag in your hand when walking out the door. Why would they need to keep it?

 

Don't worry guys...

First of all, thanks for your concern.

Don't worry about my sound card, i kept it and gave it to my friend.

So, should I get a new card and disable the on-board audio?

And another thing, may you tell me what is the reason for all the hissing and ticking?

Thanx.

 

re: hissing and ticking - soundcards can be a major pain in the arse when setting up a machine. Usually, the culprit is the DOS emulation driver and or an IRQ conflict. Sometimes, moving the card to another slot will cure the problem but I've seen instances whereby an upgraded bios flash is necessary. (guess that provides little relief for onboard sound though, huh?)

In your specific case, my suggestion would be to check for driver updates and look for IRQ conflicts.