IRQ Sharing Argh

I have 2 VIA chipset machines and one Intel chipset.

I do not let Creative near any of my machines any more. Creative issues have
occurred on Intel, VIA, SiS and ALi chipsets. As well as any other oddball
chipsets out there. The issue with Creative is not isolate to a specific
chipset vendor.

I have no problems even though on all 3 machines all PCI devices are hung
off the same IRQ. Then again, and I'll repeat, I do not use Creative sound
cards.

You're still barking up the wrong tree and trying to pass responsibility off
to the wrong party.

I'll repeat the one issue you have yet to accept:

better. Basically you
have a piece of hardware that is known to have issues
with playing well with
other devices.

Only Creative can give you a set of drivers that will play well with other
devices. Or, you can dump the sound card and go with a different one from a
different vendor. Frankly $80US for a Turtle Beach Santa Cruz will more than
assuage the agony you're going through. Or if you can't afford that much,
than a $20 generic sound card will do you wonders. It's your call however.
But the first thing you must realize is that the fault lies with Creative.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/service...on/default.asp


"Chris" wrote in message
...
Well Just Say You have More Power Then The Rest.

VIA Chipsets Are As Crappy As Can Be.



-----Original Message-----
You missed where I stated:

in lies another issue. If the BIOS has assigned an
IRQ to
a given device, it
may not be possible for the OS to change it. This is a

as well as

better. Basically you
have a piece of hardware that is known to have issues
with playing well with
other devices.

Between the two, there's no choice. If a standard HAL
did not allow you to
change the IRQ of the device, then your BIOS is at
fault. See first
reminder.

Of course there is another option. You could drop back
to 9x.

BTW: I don't work for MS. I just help people out as much
as I can. However
MS internal folk do peruse the NGs and some post here
from time to time.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is
insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/service...ileversion/def
ault.asp


"Chris" wrote in message
...
Well As You Mentioned Reinstalling Windows To use
Starndard, I Have Done That, But Nothing Changed, And
As
You Mention, Poor Results... Can You Not Just Make A
Tweak
For The People Who Want to change There settings? They
Shurly know the conciquences Of conflicting Everything.
But Still would alowed To Be Able To Change There
Settings, For Those Who Know How. Just Give Us A Little
credit, were not all computer Illiterate.
-Chris




-----Original Message-----
Not stumped. Just on the east coast and in bed when
you
asked the question
regarding manual IRQ assignments.

Basically it's an issue of complexity of modern
hardware
mixed with
maintaining backward compatibility as much as possible
with older hardware.
In order for things to work the BIOS and the OS
negotiate
how they
communicate not only with each other, but the
individual
devices. And there
in lies another issue. If the BIOS has assigned an
IRQ to
a given device, it
may not be possible for the OS to change it. This is a
highly formalized
process that is, unfortunately, implemented slightly
differently by
different vendors. To add to the complexity, the
devices
and drivers must
adhere to a set of published standards. If any thing
in
that process
belches, burps or hiccups then things break.

I noticed up stream you implied that you attempted to
use
a standard HAL.
For that to work, you must reinstall and force the HAL
selection. AFAIK, if
you reinstall and select a standard HAL you'll have
*some* ability to
manually control resources. But it does require a full
blown reinstall and
there's no guarantees that you'll like the results any
better. Basically you
have a piece of hardware that is known to have issues
with playing well with
other devices.

Personally in your shoes, I'd simply go pick up a
sound
card from a
different vendor. It'll save you a lot of grief.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is
insufficiently advanced.
http://www.dts-l.org

http://support.microsoft.com/service...ileversion/def
a
ult.asp


"CHRIIS" wrote in message
...
Im Not Saying Thats Its Your Products Fault But Why
Did
You Get Rid Of Manual IRQ Changing In THe First
Place,
When Clearly It was a life saver in 98 even though
of
the..err..unstability and ME Edition. heh. But,
Just Why
Get Rid Of IT?


.



.

Haha, Well Whatever WIll Go With My Creative 5.1 Speakers
Shall Work.





-----Original Message-----
I have 2 VIA chipset machines and one Intel chipset.

I do not let Creative near any of my machines any more.
Creative issues have
occurred on Intel, VIA, SiS and ALi chipsets. As well as
any other oddball
chipsets out there. The issue with Creative is not
isolate to a specific
chipset vendor.

I have no problems even though on all 3 machines all PCI
devices are hung
off the same IRQ. Then again, and I'll repeat, I do not
use Creative sound
cards.

You're still barking up the wrong tree and trying to
pass responsibility off
to the wrong party.

I'll repeat the one issue you have yet to accept:

better. Basically you
have a piece of hardware that is known to have
issues
with playing well with
other devices.

Only Creative can give you a set of drivers that will
play well with other
devices. Or, you can dump the sound card and go with a
different one from a
different vendor. Frankly $80US for a Turtle Beach Santa
Cruz will more than
assuage the agony you're going through. Or if you can't
afford that much,
than a $20 generic sound card will do you wonders. It's
your call however.
But the first thing you must realize is that the fault
lies with Creative.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is
insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/service...ileversion/def
ault.asp


"Chris" wrote in message
...
Well Just Say You have More Power Then The Rest.

VIA Chipsets Are As Crappy As Can Be.



-----Original Message-----
You missed where I stated:

in lies another issue. If the BIOS has assigned an
IRQ to
a given device, it
may not be possible for the OS to change it. This
is a

as well as

better. Basically you
have a piece of hardware that is known to have
issues
with playing well with
other devices.

Between the two, there's no choice. If a standard HAL
did not allow you to
change the IRQ of the device, then your BIOS is at
fault. See first
reminder.

Of course there is another option. You could drop back
to 9x.

BTW: I don't work for MS. I just help people out as
much
as I can. However
MS internal folk do peruse the NGs and some post here
from time to time.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is
insufficiently advanced.
http://www.dts-l.org

http://support.microsoft.com/service...ileversion/def
ault.asp


"Chris" wrote in message
...
Well As You Mentioned Reinstalling Windows To use
Starndard, I Have Done That, But Nothing Changed,
And
As
You Mention, Poor Results... Can You Not Just Make A
Tweak
For The People Who Want to change There settings?
They
Shurly know the conciquences Of conflicting
Everything.
But Still would alowed To Be Able To Change There
Settings, For Those Who Know How. Just Give Us A
Little
credit, were not all computer Illiterate.
-Chris




-----Original Message-----
Not stumped. Just on the east coast and in bed when
you
asked the question
regarding manual IRQ assignments.

Basically it's an issue of complexity of modern
hardware
mixed with
maintaining backward compatibility as much as
possible
with older hardware.
In order for things to work the BIOS and the OS
negotiate
how they
communicate not only with each other, but the
individual
devices. And there
in lies another issue. If the BIOS has assigned an
IRQ to
a given device, it
may not be possible for the OS to change it. This
is a
highly formalized
process that is, unfortunately, implemented
slightly
differently by
different vendors. To add to the complexity, the
devices
and drivers must
adhere to a set of published standards. If any
thing
in
that process
belches, burps or hiccups then things break.

I noticed up stream you implied that you attempted
to
use
a standard HAL.
For that to work, you must reinstall and force the
HAL
selection. AFAIK, if
you reinstall and select a standard HAL you'll have
*some* ability to
manually control resources. But it does require a
full
blown reinstall and
there's no guarantees that you'll like the results
any
better. Basically you
have a piece of hardware that is known to have
issues
with playing well with
other devices.

Personally in your shoes, I'd simply go pick up a
sound
card from a
different vendor. It'll save you a lot of grief.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is
insufficiently advanced.
http://www.dts-l.org


http://support.microsoft.com/service...ileversion/def
a
ult.asp


"CHRIIS" wrote in message
...
Im Not Saying Thats Its Your Products Fault But
Why
Did
You Get Rid Of Manual IRQ Changing In THe First
Place,
When Clearly It was a life saver in 98 even
though
of
the..err..unstability and ME Edition. heh. But,
Just Why
Get Rid Of IT?


.



.



.

Turtle Beach Santa Cruz has 5.1 output. The fact that your speakers are
Creative is irrelevant and has no bearing on the sound card.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/service...on/default.asp


"Chris" wrote in message
...
Haha, Well Whatever WIll Go With My Creative 5.1 Speakers
Shall Work.





-----Original Message-----
I have 2 VIA chipset machines and one Intel chipset.

I do not let Creative near any of my machines any more.
Creative issues have
occurred on Intel, VIA, SiS and ALi chipsets. As well as
any other oddball
chipsets out there. The issue with Creative is not
isolate to a specific
chipset vendor.

I have no problems even though on all 3 machines all PCI
devices are hung
off the same IRQ. Then again, and I'll repeat, I do not
use Creative sound
cards.

You're still barking up the wrong tree and trying to
pass responsibility off
to the wrong party.

I'll repeat the one issue you have yet to accept:

better. Basically you
have a piece of hardware that is known to have
issues
with playing well with
other devices.

Only Creative can give you a set of drivers that will
play well with other
devices. Or, you can dump the sound card and go with a
different one from a
different vendor. Frankly $80US for a Turtle Beach Santa
Cruz will more than
assuage the agony you're going through. Or if you can't
afford that much,
than a $20 generic sound card will do you wonders. It's
your call however.
But the first thing you must realize is that the fault
lies with Creative.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is
insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/service...ileversion/def
ault.asp


"Chris" wrote in message
...
Well Just Say You have More Power Then The Rest.

VIA Chipsets Are As Crappy As Can Be.



-----Original Message-----
You missed where I stated:

in lies another issue. If the BIOS has assigned an
IRQ to
a given device, it
may not be possible for the OS to change it. This
is a

as well as

better. Basically you
have a piece of hardware that is known to have
issues
with playing well with
other devices.

Between the two, there's no choice. If a standard HAL
did not allow you to
change the IRQ of the device, then your BIOS is at
fault. See first
reminder.

Of course there is another option. You could drop back
to 9x.

BTW: I don't work for MS. I just help people out as
much
as I can. However
MS internal folk do peruse the NGs and some post here
from time to time.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is
insufficiently advanced.
http://www.dts-l.org

http://support.microsoft.com/service...ileversion/def
ault.asp


"Chris" wrote in message
...
Well As You Mentioned Reinstalling Windows To use
Starndard, I Have Done That, But Nothing Changed,
And
As
You Mention, Poor Results... Can You Not Just Make A
Tweak
For The People Who Want to change There settings?
They
Shurly know the conciquences Of conflicting
Everything.
But Still would alowed To Be Able To Change There
Settings, For Those Who Know How. Just Give Us A
Little
credit, were not all computer Illiterate.
-Chris




-----Original Message-----
Not stumped. Just on the east coast and in bed when
you
asked the question
regarding manual IRQ assignments.

Basically it's an issue of complexity of modern
hardware
mixed with
maintaining backward compatibility as much as
possible
with older hardware.
In order for things to work the BIOS and the OS
negotiate
how they
communicate not only with each other, but the
individual
devices. And there
in lies another issue. If the BIOS has assigned an
IRQ to
a given device, it
may not be possible for the OS to change it. This
is a
highly formalized
process that is, unfortunately, implemented
slightly
differently by
different vendors. To add to the complexity, the
devices
and drivers must
adhere to a set of published standards. If any
thing
in
that process
belches, burps or hiccups then things break.

I noticed up stream you implied that you attempted
to
use
a standard HAL.
For that to work, you must reinstall and force the
HAL
selection. AFAIK, if
you reinstall and select a standard HAL you'll have
*some* ability to
manually control resources. But it does require a
full
blown reinstall and
there's no guarantees that you'll like the results
any
better. Basically you
have a piece of hardware that is known to have
issues
with playing well with
other devices.

Personally in your shoes, I'd simply go pick up a
sound
card from a
different vendor. It'll save you a lot of grief.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is
insufficiently advanced.
http://www.dts-l.org


http://support.microsoft.com/service...ileversion/def
a
ult.asp


"CHRIIS" wrote in message
...
Im Not Saying Thats Its Your Products Fault But
Why
Did
You Get Rid Of Manual IRQ Changing In THe First
Place,
When Clearly It was a life saver in 98 even
though
of
the..err..unstability and ME Edition. heh. But,
Just Why
Get Rid Of IT?


.



.



.

Well I Have Sitting In From Of Me Is Anouther Sound
Card..Purchased At Computer Show And Sale As A Spare,
only 10$ for it..I Believe the Brand Name Is Lsunami but
its scribbled on the box in fancy writing that is
difficult to Read. 6 Channel Pci Sound Card

Diamond DT-688.

THe "Diamond" Rings A Bell, I remember Long Long Ago I
havd A Diamond Sound Card (Legacy) And It Was Hell To
Deal With. I Dunno If Its The Same Kinda Diamond I Have
In My Hand Right Now. The Only Thing In THe Box Is The
Card And Drivers..No Manual, haha. THe Card Is Like...1/4
The Size Of My Creative..It Doesn't Seem Like It Would
Match Up With The Sound Blasters Capabilities...Says That
It Supports XP on the back of the box...Hmm I Dunno If I
Wanna Switch or not cuz.. When I Switch Cards And Such I
Have An Entendicy To Reinstall Windows Fresh Because I
Don't Like Having Like ALl THese Unused Drivers Sitting
Around, lol.

But the card it just..doesn't seem good just by size but
for all i know it could be all packed together tiny in
the chipset on it, lol




-----Original Message-----
Turtle Beach Santa Cruz has 5.1 output. The fact that
your speakers are
Creative is irrelevant and has no bearing on the sound
card.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is
insufficiently advanced.
http://www.dts-l.org
http://support.microsoft.com/service...ileversion/def
ault.asp


"Chris" wrote in message
...
Haha, Well Whatever WIll Go With My Creative 5.1
Speakers
Shall Work.





-----Original Message-----
I have 2 VIA chipset machines and one Intel chipset.

I do not let Creative near any of my machines any
more.
Creative issues have
occurred on Intel, VIA, SiS and ALi chipsets. As well
as
any other oddball
chipsets out there. The issue with Creative is not
isolate to a specific
chipset vendor.

I have no problems even though on all 3 machines all
PCI
devices are hung
off the same IRQ. Then again, and I'll repeat, I do
not
use Creative sound
cards.

You're still barking up the wrong tree and trying to
pass responsibility off
to the wrong party.

I'll repeat the one issue you have yet to accept:

better. Basically you
have a piece of hardware that is known to have
issues
with playing well with
other devices.

Only Creative can give you a set of drivers that will
play well with other
devices. Or, you can dump the sound card and go with a
different one from a
different vendor. Frankly $80US for a Turtle Beach
Santa
Cruz will more than
assuage the agony you're going through. Or if you
can't
afford that much,
than a $20 generic sound card will do you wonders.
It's
your call however.
But the first thing you must realize is that the fault
lies with Creative.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is
insufficiently advanced.
http://www.dts-l.org

http://support.microsoft.com/service...ileversion/def
ault.asp


"Chris" wrote in message
...
Well Just Say You have More Power Then The Rest.

VIA Chipsets Are As Crappy As Can Be.



-----Original Message-----
You missed where I stated:

in lies another issue. If the BIOS has assigned
an
IRQ to
a given device, it
may not be possible for the OS to change it.
This
is a

as well as

better. Basically you
have a piece of hardware that is known to have
issues
with playing well with
other devices.

Between the two, there's no choice. If a standard
HAL
did not allow you to
change the IRQ of the device, then your BIOS is at
fault. See first
reminder.

Of course there is another option. You could drop
back
to 9x.

BTW: I don't work for MS. I just help people out as
much
as I can. However
MS internal folk do peruse the NGs and some post
here
from time to time.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is
insufficiently advanced.
http://www.dts-l.org


http://support.microsoft.com/service...ileversion/def
ault.asp


"Chris" wrote in message
...
Well As You Mentioned Reinstalling Windows To use
Starndard, I Have Done That, But Nothing Changed,
And
As
You Mention, Poor Results... Can You Not Just
Make A
Tweak
For The People Who Want to change There settings?
They
Shurly know the conciquences Of conflicting
Everything.
But Still would alowed To Be Able To Change There
Settings, For Those Who Know How. Just Give Us A
Little
credit, were not all computer Illiterate.
-Chris




-----Original Message-----
Not stumped. Just on the east coast and in bed
when
you
asked the question
regarding manual IRQ assignments.

Basically it's an issue of complexity of modern
hardware
mixed with
maintaining backward compatibility as much as
possible
with older hardware.
In order for things to work the BIOS and the OS
negotiate
how they
communicate not only with each other, but the
individual
devices. And there
in lies another issue. If the BIOS has assigned
an
IRQ to
a given device, it
may not be possible for the OS to change it.
This
is a
highly formalized
process that is, unfortunately, implemented
slightly
differently by
different vendors. To add to the complexity, the
devices
and drivers must
adhere to a set of published standards. If any
thing
in
that process
belches, burps or hiccups then things break.

I noticed up stream you implied that you
attempted
to
use
a standard HAL.
For that to work, you must reinstall and force
the
HAL
selection. AFAIK, if
you reinstall and select a standard HAL you'll
have
*some* ability to
manually control resources. But it does require
a
full
blown reinstall and
there's no guarantees that you'll like the
results
any
better. Basically you
have a piece of hardware that is known to have
issues
with playing well with
other devices.

Personally in your shoes, I'd simply go pick up
a
sound
card from a
different vendor. It'll save you a lot of grief.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is
insufficiently advanced.
http://www.dts-l.org



http://support.microsoft.com/service...ileversion/def
a
ult.asp


"CHRIIS" wrote in message
...
Im Not Saying Thats Its Your Products Fault
But
Why
Did
You Get Rid Of Manual IRQ Changing In THe
First
Place,
When Clearly It was a life saver in 98 even
though
of
the..err..unstability and ME Edition. heh.
But,
Just Why
Get Rid Of IT?


.



.



.



.

I Am Not Using Raid, And I Do Have THe Latest Bios Update.



-----Original Message-----
In article ,
says...
Yes 4 in 1....Darn Them 4in1...Im Assuming Mobo Means
MotherBoard So..I Have An ABIT KT7A 1.3 Its The Only
One
That Will Run My AMD 2100+ XP Chip.

Nothing Works Without the 4in1 its fustrating.

Your problem is not because of ACPI and or IRQ sharing.
This was a well
know problem with the KT7 and KT7A boards way back a
couple of years ago
when they were newer technology. What BIOS version are
you running? Also
if it's a raid board and your running the 1.11 Highpoint
BIOS and
drivers they were well know for causing crackling sound.
You need to be
running a newer v2.x Highpoint BIOS and drivers, and you
need to install
the Raid Performance Patch 'rpp1.02.zip' from here
http://www.viaarena.com/?PageID=66

In the BIOS use these settings for raid and non-raid
boards.
'Enhance Chip Performance' to 'Enabled'
'MD Driving Strength' to 'Hi'
'Delay Transaction' to 'Disabled'
'PCI master Read Caching' to 'Enabled'
'PCI master Bus time-out' to '0'

If you do a goggle search
in 'alt.comp.periphs.mainboard.abit' you will
find tons of posts from 1 1-2 years or so ago covering
this with even
more tips, probably a few hundred posts from me alone.

http://groups.google.com/groups?
q=alt.comp.periphs.mainboard.abit&btnG=Google+Sea rch

Doug
.

In article ,
says...
Yes 4 in 1....Darn Them 4in1...Im Assuming Mobo Means
MotherBoard So..I Have An ABIT KT7A 1.3 Its The Only One
That Will Run My AMD 2100+ XP Chip.

Nothing Works Without the 4in1 its fustrating.

Your problem is not because of ACPI and or IRQ sharing. This was a well
know problem with the KT7 and KT7A boards way back a couple of years ago
when they were newer technology. What BIOS version are you running? Also
if it's a raid board and your running the 1.11 Highpoint BIOS and
drivers they were well know for causing crackling sound. You need to be
running a newer v2.x Highpoint BIOS and drivers, and you need to install
the Raid Performance Patch 'rpp1.02.zip' from here
http://www.viaarena.com/?PageID=66

In the BIOS use these settings for raid and non-raid boards.
'Enhance Chip Performance' to 'Enabled'
'MD Driving Strength' to 'Hi'
'Delay Transaction' to 'Disabled'
'PCI master Read Caching' to 'Enabled'
'PCI master Bus time-out' to '0'

If you do a goggle search in 'alt.comp.periphs.mainboard.abit' you will
find tons of posts from 1 1-2 years or so ago covering this with even
more tips, probably a few hundred posts from me alone.

http://groups.google.com/groups?
q=alt.comp.periphs.mainboard.abit&btnG=Google+Sear ch

Doug

Dougie,
What Will Changing These

'Enhance Chip Performance' to 'Enabled'
'MD Driving Strength' to 'Hi'
'Delay Transaction' to 'Disabled'
'PCI master Read Caching' to 'Enabled'
'PCI master Bus time-out' to '0'

Acomplish? I Do Know For Sure That The First 2 is set
like that, i have to check the rest.





-----Original Message-----
In article ,
says...
Yes 4 in 1....Darn Them 4in1...Im Assuming Mobo Means
MotherBoard So..I Have An ABIT KT7A 1.3 Its The Only
One
That Will Run My AMD 2100+ XP Chip.

Nothing Works Without the 4in1 its fustrating.

Your problem is not because of ACPI and or IRQ sharing.
This was a well
know problem with the KT7 and KT7A boards way back a
couple of years ago
when they were newer technology. What BIOS version are
you running? Also
if it's a raid board and your running the 1.11 Highpoint
BIOS and
drivers they were well know for causing crackling sound.
You need to be
running a newer v2.x Highpoint BIOS and drivers, and you
need to install
the Raid Performance Patch 'rpp1.02.zip' from here
http://www.viaarena.com/?PageID=66

In the BIOS use these settings for raid and non-raid
boards.
'Enhance Chip Performance' to 'Enabled'
'MD Driving Strength' to 'Hi'
'Delay Transaction' to 'Disabled'
'PCI master Read Caching' to 'Enabled'
'PCI master Bus time-out' to '0'

If you do a goggle search
in 'alt.comp.periphs.mainboard.abit' you will
find tons of posts from 1 1-2 years or so ago covering
this with even
more tips, probably a few hundred posts from me alone.

http://groups.google.com/groups?
q=alt.comp.periphs.mainboard.abit&btnG=Google+Sea rch

Doug
.

Ah Yes, I Must Look In The Manual For What THe Different
Selections Do. I Have Not Seen Leaky Caps, But I Have
Seen Pootchy Caps Where they were bulging at the top.
What Would THe Reason Be For Them Blowing Up...?




-----Original Message-----
I was trying to help you 'accomplish' getting rid of
your crackling
sound problem. Isn't that what this thread is about?
Isn't that what
your trying to do? Or do you just want to bitch about
IRQ sharing which
is not the cause of your problem? I also gave you a
goggle link to an
Abit group where you could do some searches on this
problem and find a
wealth of information on the causes and fixes for this
problem from when
it was heavily discussed a couple of years go. Also
check your board for
domed or leaking caps. That board is known to have caps
blow after a
year or so of use. On the KT7A boards the two caps under
the AGP slot
are usually the first to go, followed by the ones around
the memory
strips and the CPU.

Doug


In article ,
says...

Dougie,
What Will Changing These

'Enhance Chip Performance' to 'Enabled'
'MD Driving Strength' to 'Hi'
'Delay Transaction' to 'Disabled'
'PCI master Read Caching' to 'Enabled'
'PCI master Bus time-out' to '0'

Acomplish? I Do Know For Sure That The First 2 is set
like that, i have to check the rest.





-----Original Message-----
In article ,
says...
Yes 4 in 1....Darn Them 4in1...Im Assuming Mobo
Means
MotherBoard So..I Have An ABIT KT7A 1.3 Its The
Only
One
That Will Run My AMD 2100+ XP Chip.

Nothing Works Without the 4in1 its fustrating.

Your problem is not because of ACPI and or IRQ
sharing.
This was a well
know problem with the KT7 and KT7A boards way back a
couple of years ago
when they were newer technology. What BIOS version
are
you running? Also
if it's a raid board and your running the 1.11
Highpoint
BIOS and
drivers they were well know for causing crackling
sound.
You need to be
running a newer v2.x Highpoint BIOS and drivers, and
you
need to install
the Raid Performance Patch 'rpp1.02.zip' from here
http://www.viaarena.com/?PageID=66

In the BIOS use these settings for raid and non-raid
boards.
'Enhance Chip Performance' to 'Enabled'
'MD Driving Strength' to 'Hi'
'Delay Transaction' to 'Disabled'
'PCI master Read Caching' to 'Enabled'
'PCI master Bus time-out' to '0'

If you do a goggle search
in 'alt.comp.periphs.mainboard.abit' you will
find tons of posts from 1 1-2 years or so ago
covering
this with even
more tips, probably a few hundred posts from me alone.

http://groups.google.com/groups?
q=alt.comp.periphs.mainboard.abit&btnG=Google+Sea rch

Doug
.


.

Well what do you know clip "scribbled on the box in fancy writing that =
is difficult to Read." clip reminds me of something. Let me =
think.................



--=20
Just my 2=A2 worth
Jeff
_____in response to_____
"Chris" wrote in message =
...
| Well I Have Sitting In From Of Me Is Anouther Sound=20
| Card..Purchased At Computer Show And Sale As A Spare,=20
| only 10$ for it..I Believe the Brand Name Is Lsunami but=20
| its scribbled on the box in fancy writing that is=20
| difficult to Read. 6 Channel Pci Sound Card
|=20
| Diamond DT-688.=20
|=20
| THe "Diamond" Rings A Bell, I remember Long Long Ago I=20
| havd A Diamond Sound Card (Legacy) And It Was Hell To=20
| Deal With. I Dunno If Its The Same Kinda Diamond I Have=20
| In My Hand Right Now. The Only Thing In THe Box Is The=20
| Card And Drivers..No Manual, haha. THe Card Is Like...1/4=20
| The Size Of My Creative..It Doesn't Seem Like It Would=20
| Match Up With The Sound Blasters Capabilities...Says That=20
| It Supports XP on the back of the box...Hmm I Dunno If I=20
| Wanna Switch or not cuz.. When I Switch Cards And Such I=20
| Have An Entendicy To Reinstall Windows Fresh Because I=20
| Don't Like Having Like ALl THese Unused Drivers Sitting=20
| Around, lol.=20
|=20
| But the card it just..doesn't seem good just by size but=20
| for all i know it could be all packed together tiny in=20
| the chipset on it, lol



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.474 / Virus Database: 272 - Release Date: 4/18/2003

I was trying to help you 'accomplish' getting rid of your crackling
sound problem. Isn't that what this thread is about? Isn't that what
your trying to do? Or do you just want to bitch about IRQ sharing which
is not the cause of your problem? I also gave you a goggle link to an
Abit group where you could do some searches on this problem and find a
wealth of information on the causes and fixes for this problem from when
it was heavily discussed a couple of years go. Also check your board for
domed or leaking caps. That board is known to have caps blow after a
year or so of use. On the KT7A boards the two caps under the AGP slot
are usually the first to go, followed by the ones around the memory
strips and the CPU.

Doug


In article ,
says...

Dougie,
What Will Changing These

'Enhance Chip Performance' to 'Enabled'
'MD Driving Strength' to 'Hi'
'Delay Transaction' to 'Disabled'
'PCI master Read Caching' to 'Enabled'
'PCI master Bus time-out' to '0'

Acomplish? I Do Know For Sure That The First 2 is set
like that, i have to check the rest.





-----Original Message-----
In article ,
says...
Yes 4 in 1....Darn Them 4in1...Im Assuming Mobo Means
MotherBoard So..I Have An ABIT KT7A 1.3 Its The Only
One
That Will Run My AMD 2100+ XP Chip.

Nothing Works Without the 4in1 its fustrating.

Your problem is not because of ACPI and or IRQ sharing.
This was a well
know problem with the KT7 and KT7A boards way back a
couple of years ago
when they were newer technology. What BIOS version are
you running? Also
if it's a raid board and your running the 1.11 Highpoint
BIOS and
drivers they were well know for causing crackling sound.
You need to be
running a newer v2.x Highpoint BIOS and drivers, and you
need to install
the Raid Performance Patch 'rpp1.02.zip' from here
http://www.viaarena.com/?PageID=66

In the BIOS use these settings for raid and non-raid
boards.
'Enhance Chip Performance' to 'Enabled'
'MD Driving Strength' to 'Hi'
'Delay Transaction' to 'Disabled'
'PCI master Read Caching' to 'Enabled'
'PCI master Bus time-out' to '0'

If you do a goggle search
in 'alt.comp.periphs.mainboard.abit' you will
find tons of posts from 1 1-2 years or so ago covering
this with even
more tips, probably a few hundred posts from me alone.

http://groups.google.com/groups?
q=alt.comp.periphs.mainboard.abit&btnG=Google+Sea rch

Doug
.

There were a lot of bad caps sold to manufactures back when those boards
were made. Here is just a few links about the problem.

http://www.overclockers.com/tips00140/
http://www.theinquirer.net/?article=5878

http://www.e-insite.net/electronicnews/index.asp?
layout=article&articleid=CA255062&pubdate=10/28/2002

http://www.ttiinc.com/MarketEye/zogb...s_20021014.asp

If you have caps bulging at the top then they are no good, and there is
really no point in trying to fix this problem. The board is not good
until you have it repaired. You will continue to have problems with it
until it dies. You can get it repaired here
http://home.att.net/~garyheadlee/ but I would just replace the board
with one using newer technology. If you liked the KT7A the Abit KD7
boards are very nice, and Abit is now using some of the best capacitors
on the market, so it is highly unlikely there will be problems with
them.
I am typing this using a KD7 Raid.

Doug


In article ,
says...

Ah Yes, I Must Look In The Manual For What THe Different
Selections Do. I Have Not Seen Leaky Caps, But I Have
Seen Pootchy Caps Where they were bulging at the top.
What Would THe Reason Be For Them Blowing Up...?




-----Original Message-----
I was trying to help you 'accomplish' getting rid of
your crackling
sound problem. Isn't that what this thread is about?
Isn't that what
your trying to do? Or do you just want to bitch about
IRQ sharing which
is not the cause of your problem? I also gave you a
goggle link to an
Abit group where you could do some searches on this
problem and find a
wealth of information on the causes and fixes for this
problem from when
it was heavily discussed a couple of years go. Also
check your board for
domed or leaking caps. That board is known to have caps
blow after a
year or so of use. On the KT7A boards the two caps under
the AGP slot
are usually the first to go, followed by the ones around
the memory
strips and the CPU.

Doug


In article ,
says...

Dougie,
What Will Changing These

'Enhance Chip Performance' to 'Enabled'
'MD Driving Strength' to 'Hi'
'Delay Transaction' to 'Disabled'
'PCI master Read Caching' to 'Enabled'
'PCI master Bus time-out' to '0'

Acomplish? I Do Know For Sure That The First 2 is set
like that, i have to check the rest.





-----Original Message-----
In article ,
says...
Yes 4 in 1....Darn Them 4in1...Im Assuming Mobo
Means
MotherBoard So..I Have An ABIT KT7A 1.3 Its The
Only
One
That Will Run My AMD 2100+ XP Chip.

Nothing Works Without the 4in1 its fustrating.

Your problem is not because of ACPI and or IRQ
sharing.
This was a well
know problem with the KT7 and KT7A boards way back a
couple of years ago
when they were newer technology. What BIOS version
are
you running? Also
if it's a raid board and your running the 1.11
Highpoint
BIOS and
drivers they were well know for causing crackling
sound.
You need to be
running a newer v2.x Highpoint BIOS and drivers, and
you
need to install
the Raid Performance Patch 'rpp1.02.zip' from here
http://www.viaarena.com/?PageID=66

In the BIOS use these settings for raid and non-raid
boards.
'Enhance Chip Performance' to 'Enabled'
'MD Driving Strength' to 'Hi'
'Delay Transaction' to 'Disabled'
'PCI master Read Caching' to 'Enabled'
'PCI master Bus time-out' to '0'

If you do a goggle search
in 'alt.comp.periphs.mainboard.abit' you will
find tons of posts from 1 1-2 years or so ago
covering
this with even
more tips, probably a few hundred posts from me alone.

http://groups.google.com/groups?
q=alt.comp.periphs.mainboard.abit&btnG=Google+Sea rch

Doug
.


.