RE: ACPI Machines and IRQ 9

I never said that VIA chipsets were bad. I only said that they operate
differently from Intel chipsets, and that most BIOS code is cut and
pasted from Intel’s examples, which means that the BIOS tends to be more
broken on a VIA machine than on an Intel machine.

The Intel i815 is a fine chipset, but it has bugs just as all other
hardware does. (All software has bugs too. I don’t mean to
discriminate.) I’ve personally added five or six hacks to Windows XP to
make it run, which is about average for an Intel chipset. In general, I
don’t add as many hacks for non-Intel chipsets. But that’s just because
the design cycles for the other guys is shorter, and they don’t send me
machines with their chips in time to do anything about the problems.

All the desktop chipsets shipping today, with the exception of one from
VIA and one from SiS, have an I/O APIC. But not all motherboard makers
enable the feature.

I disagree with your notion of hack-job PC’s being as reliable as a Dell
or an HP. I spend a huge amount of my time debugging problems with
specific motherboards. And it really boils down to finding the
cross-product of bugs that create nasty hardware interactions and then
avoiding them. When Dell, HP, Compaq or IBM build a machine, they
choose a chipset and a few different component suppliers. Then they
test the machine extensively, shaking out the incompatibilities before
they settle on a final configuration. This process gets a much higher
quality product into the end-user’s hands. (Incidentally, this is ten
times as true with SMP machines. None of the raw motherboard makers
builds one that I would consider reliable.) Part of the problem with
building your own machine is just that you can’t personally afford to
test each peripheral in isolation, chosing the ones that don’t have bad
interactions.

I once debugged a machine that had a bad interaction between the SuperIO
chip and the CD-ROM drive. When the CD would put data on the IDE bus,
it would cause a signal to be asserted that would cause all bytes in the
top lane of the X-Bus to appear as all 1’s. If that occurred while the
OS was doing a 16-bit read to the X-Bus, then data returned would be bad
in the upper byte. The problem went away if you changed to a different
brand of CD-ROM drive, or if you used a different SuperIO chip.

In another example, you can’t get stand-by to work on a 440BX-based
machine unless you exclude one of the three supported types of RAM.
Using one of the other two types requires a massive BIOS hack to make it
work. But if you apply the hack with the wrong RAM type (and software
couldn’t tell the difference) then the machine will hang. When I told
ASUS about the problem, they couldn’t do anything about it because their
customers install the RAM themselves. When Intel told the large
companies about it, they were all able to successfully patch their
BIOSes.

My point is that the people who design the commodity motherboards don’t
control the peripherals that will be matched with them. So they can’t
guarantee that the machine, when viewed as a whole, will actually work.
The big guys can.

  • Jake Oshins

-----Original Message-----
Subject: RE: ACPI Machines and IRQ 9 [was: Communicating with the NT
developers]
From: “Maxim S. Shatskih”
Date: Mon, 31 Dec 2001 14:56:33 +0300
X-Message-Number: 19

>This is a stupid story. And I’m embarrassed to tell you the truth.
But
>here it is.

Really an interesting story, Jake. Thanks for it!

>But if your machine has a VIA chipset, or if it has a BIOS that we know
>to be broken, then we fall back to the Win2K-style stacking behavior.

So, VIA is this bad. Will know this now.

>The unfortunate truth is that you guys on this list mostly build your
>own machines, rather than buying them from reputable manufacturers,

Yes, twice as cheap, and the same performance and reliability. All
depends on parts vendor, mainly motherboard vendor.
As about the brand names like Dell or HP - they are known to be not 100%
compatible with the usual PC, for instance, Dell required a
PCI card to be Dell-certified.

>which means that you guys own the machines with broken BIOSes and VIA
>chipsets.

Lots of motherboards on the market (and thus self-assembled machines)
use Intel chipsets like i815 or such.
Is i815 bad?

>One notable addendum is that any machine with an APIC interrupt
>controller, and thus more than 16 IRQs, will spread interrupts out,
even
>in Win2K.

And what chipsets will provide APIC on non-SMP machine?

Max


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

I don’t have anything to add from a technical standpoint, but something
interesting did occur to me as I’ve followed this thread. It’s too bad
the ACPI IRQ stacking behavior gravitates toward IRQ 9 — if only it
were two interrupts higher, we could dub the phenomenon “Oshins’ 11”!

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jake Oshins
Sent: Tuesday, January 01, 2002 2:34 AM
To: NT Developers Interest List
Subject: [ntdev] RE: ACPI Machines and IRQ 9

I never said that VIA chipsets were bad. I only said that they operate
differently from Intel chipsets, and that most BIOS code is cut and
pasted from Intel’s examples, which means that the BIOS tends to be more
broken on a VIA machine than on an Intel machine.

The Intel i815 is a fine chipset, but it has bugs just as all other
hardware does. (All software has bugs too. I don’t mean to
discriminate.) I’ve personally added five or six hacks to Windows XP to
make it run, which is about average for an Intel chipset. In general, I
don’t add as many hacks for non-Intel chipsets. But that’s just because
the design cycles for the other guys is shorter, and they don’t send me
machines with their chips in time to do anything about the problems.

All the desktop chipsets shipping today, with the exception of one from
VIA and one from SiS, have an I/O APIC. But not all motherboard makers
enable the feature.

I disagree with your notion of hack-job PC’s being as reliable as a Dell
or an HP. I spend a huge amount of my time debugging problems with
specific motherboards. And it really boils down to finding the
cross-product of bugs that create nasty hardware interactions and then
avoiding them. When Dell, HP, Compaq or IBM build a machine, they
choose a chipset and a few different component suppliers. Then they
test the machine extensively, shaking out the incompatibilities before
they settle on a final configuration. This process gets a much higher
quality product into the end-user’s hands. (Incidentally, this is ten
times as true with SMP machines. None of the raw motherboard makers
builds one that I would consider reliable.) Part of the problem with
building your own machine is just that you can’t personally afford to
test each peripheral in isolation, chosing the ones that don’t have bad
interactions.

I once debugged a machine that had a bad interaction between the SuperIO
chip and the CD-ROM drive. When the CD would put data on the IDE bus,
it would cause a signal to be asserted that would cause all bytes in the
top lane of the X-Bus to appear as all 1’s. If that occurred while the
OS was doing a 16-bit read to the X-Bus, then data returned would be bad
in the upper byte. The problem went away if you changed to a different
brand of CD-ROM drive, or if you used a different SuperIO chip.

In another example, you can’t get stand-by to work on a 440BX-based
machine unless you exclude one of the three supported types of RAM.
Using one of the other two types requires a massive BIOS hack to make it
work. But if you apply the hack with the wrong RAM type (and software
couldn’t tell the difference) then the machine will hang. When I told
ASUS about the problem, they couldn’t do anything about it because their
customers install the RAM themselves. When Intel told the large
companies about it, they were all able to successfully patch their
BIOSes.

My point is that the people who design the commodity motherboards don’t
control the peripherals that will be matched with them. So they can’t
guarantee that the machine, when viewed as a whole, will actually work.
The big guys can.

  • Jake Oshins

-----Original Message-----
Subject: RE: ACPI Machines and IRQ 9 [was: Communicating with the NT
developers]
From: “Maxim S. Shatskih”
Date: Mon, 31 Dec 2001 14:56:33 +0300
X-Message-Number: 19

>This is a stupid story. And I’m embarrassed to tell you the truth.
But
>here it is.

Really an interesting story, Jake. Thanks for it!

>But if your machine has a VIA chipset, or if it has a BIOS that we know
>to be broken, then we fall back to the Win2K-style stacking behavior.

So, VIA is this bad. Will know this now.

>The unfortunate truth is that you guys on this list mostly build your
>own machines, rather than buying them from reputable manufacturers,

Yes, twice as cheap, and the same performance and reliability. All
depends on parts vendor, mainly motherboard vendor.
As about the brand names like Dell or HP - they are known to be not 100%
compatible with the usual PC, for instance, Dell required a
PCI card to be Dell-certified.

>which means that you guys own the machines with broken BIOSes and VIA
>chipsets.

Lots of motherboards on the market (and thus self-assembled machines)
use Intel chipsets like i815 or such.
Is i815 bad?

>One notable addendum is that any machine with an APIC interrupt
>controller, and thus more than 16 IRQs, will spread interrupts out,
even
>in Win2K.

And what chipsets will provide APIC on non-SMP machine?

Max


You are currently subscribed to ntdev as: xxxxx@owen-t.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

>pasted from Intel’s examples, which means that the BIOS tends to be more

broken on a VIA machine than on an Intel machine.

Thanks, I understand.

discriminate.) I’ve personally added five or six hacks to Windows XP to
make it run, which is about average for an Intel chipset.

BTW - I saw the following on i815:

  • standby/hibernate works fine in w2k.
  • but they have problems on XP, on the same machine with the same mobo.

The only explanation I have is that either i815 or Asus’s BIOS are buggy, w2k has hacks to work the bugs around, while XP has not.

builds one that I would consider reliable.) Part of the problem with
building your own machine is just that you can’t personally afford to
test each peripheral in isolation, chosing the ones that don’t have bad
interactions.

Yes, a known issue, you can sometimes end with slightly incompatible set of peripherals.
In combination with ACPI IRQ thing in w2k, this can turn out very bad :slight_smile:

In another example, you can’t get stand-by to work on a 440BX-based
machine unless you exclude one of the three supported types of RAM.

Wow!
And after this, some people are speaking on BX as the “best chipset ever made” :-(.
BTW, Jake, can you name these 3 types of RAM and what one will not allow standby on BX?

My point is that the people who design the commodity motherboards don’t
control the peripherals that will be matched with them. So they can’t
guarantee that the machine, when viewed as a whole, will actually work.

Yes, with the “dark side” of having to purchase memory from Dell only, not just on the market.
Any stories on “brand-name incompatibilities” are usually about somebody who tried to install some off-the-shelf hardware to the
Dell (or such) machine.

Max


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Sorry, what is it?
I’m not a native English speaker, so what does “somebody’s 11” mean?

Max

----- Original Message -----
From: “Owen T. Cunningham”
To: “NT Developers Interest List”
Sent: Tuesday, January 01, 2002 9:06 PM
Subject: [ntdev] RE: ACPI Machines and IRQ 9

> I don’t have anything to add from a technical standpoint, but something
> interesting did occur to me as I’ve followed this thread. It’s too bad
> the ACPI IRQ stacking behavior gravitates toward IRQ 9 — if only it
> were two interrupts higher, we could dub the phenomenon “Oshins’ 11”!
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Jake Oshins
> Sent: Tuesday, January 01, 2002 2:34 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: ACPI Machines and IRQ 9
>
>
> I never said that VIA chipsets were bad. I only said that they operate
> differently from Intel chipsets, and that most BIOS code is cut and
> pasted from Intel’s examples, which means that the BIOS tends to be more
> broken on a VIA machine than on an Intel machine.
>
> The Intel i815 is a fine chipset, but it has bugs just as all other
> hardware does. (All software has bugs too. I don’t mean to
> discriminate.) I’ve personally added five or six hacks to Windows XP to
> make it run, which is about average for an Intel chipset. In general, I
> don’t add as many hacks for non-Intel chipsets. But that’s just because
> the design cycles for the other guys is shorter, and they don’t send me
> machines with their chips in time to do anything about the problems.
>
> All the desktop chipsets shipping today, with the exception of one from
> VIA and one from SiS, have an I/O APIC. But not all motherboard makers
> enable the feature.
>
> I disagree with your notion of hack-job PC’s being as reliable as a Dell
> or an HP. I spend a huge amount of my time debugging problems with
> specific motherboards. And it really boils down to finding the
> cross-product of bugs that create nasty hardware interactions and then
> avoiding them. When Dell, HP, Compaq or IBM build a machine, they
> choose a chipset and a few different component suppliers. Then they
> test the machine extensively, shaking out the incompatibilities before
> they settle on a final configuration. This process gets a much higher
> quality product into the end-user’s hands. (Incidentally, this is ten
> times as true with SMP machines. None of the raw motherboard makers
> builds one that I would consider reliable.) Part of the problem with
> building your own machine is just that you can’t personally afford to
> test each peripheral in isolation, chosing the ones that don’t have bad
> interactions.
>
> I once debugged a machine that had a bad interaction between the SuperIO
> chip and the CD-ROM drive. When the CD would put data on the IDE bus,
> it would cause a signal to be asserted that would cause all bytes in the
> top lane of the X-Bus to appear as all 1’s. If that occurred while the
> OS was doing a 16-bit read to the X-Bus, then data returned would be bad
> in the upper byte. The problem went away if you changed to a different
> brand of CD-ROM drive, or if you used a different SuperIO chip.
>
> In another example, you can’t get stand-by to work on a 440BX-based
> machine unless you exclude one of the three supported types of RAM.
> Using one of the other two types requires a massive BIOS hack to make it
> work. But if you apply the hack with the wrong RAM type (and software
> couldn’t tell the difference) then the machine will hang. When I told
> ASUS about the problem, they couldn’t do anything about it because their
> customers install the RAM themselves. When Intel told the large
> companies about it, they were all able to successfully patch their
> BIOSes.
>
> My point is that the people who design the commodity motherboards don’t
> control the peripherals that will be matched with them. So they can’t
> guarantee that the machine, when viewed as a whole, will actually work.
> The big guys can.
>
> - Jake Oshins
>
> -----Original Message-----
> Subject: RE: ACPI Machines and IRQ 9 [was: Communicating with the NT
> developers]
> From: “Maxim S. Shatskih”
> Date: Mon, 31 Dec 2001 14:56:33 +0300
> X-Message-Number: 19
>
> >This is a stupid story. And I’m embarrassed to tell you the truth.
> But
> >here it is.
>
> Really an interesting story, Jake. Thanks for it!
>
> >But if your machine has a VIA chipset, or if it has a BIOS that we know
> >to be broken, then we fall back to the Win2K-style stacking behavior.
>
> So, VIA is this bad. Will know this now.
>
> >The unfortunate truth is that you guys on this list mostly build your
> >own machines, rather than buying them from reputable manufacturers,
>
> Yes, twice as cheap, and the same performance and reliability. All
> depends on parts vendor, mainly motherboard vendor.
> As about the brand names like Dell or HP - they are known to be not 100%
> compatible with the usual PC, for instance, Dell required a
> PCI card to be Dell-certified.
>
> >which means that you guys own the machines with broken BIOSes and VIA
> >chipsets.
>
> Lots of motherboards on the market (and thus self-assembled machines)
> use Intel chipsets like i815 or such.
> Is i815 bad?
>
> >One notable addendum is that any machine with an APIC interrupt
> >controller, and thus more than 16 IRQs, will spread interrupts out,
> even
> >in Win2K.
>
> And what chipsets will provide APIC on non-SMP machine?
>
> Max
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@owen-t.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Sorry Max, you’re correct that this joke will make sense only to
American moviegoers.

There is a film that was just released (actually a remake of an earlier
Frank Sinatra movie of the same name) starring George Clooney and Brad
Pitt. The name is “Ocean’s Eleven” — George Clooney’s character is
named Danny Ocean and the title is meant to refer to his gang of 11
thieves that he assembles to rob a bunch of casinos in Las Vegas.

Now that I think about it, this joke could turn out to completely suck
if Oshins is pronounced differently from Oceans…

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Tuesday, January 01, 2002 1:17 PM
To: NT Developers Interest List
Subject: [ntdev] RE: ACPI Machines and IRQ 9

Sorry, what is it?
I’m not a native English speaker, so what does “somebody’s 11” mean?

Max

----- Original Message -----
From: “Owen T. Cunningham”
To: “NT Developers Interest List”
Sent: Tuesday, January 01, 2002 9:06 PM
Subject: [ntdev] RE: ACPI Machines and IRQ 9

> I don’t have anything to add from a technical standpoint, but
something
> interesting did occur to me as I’ve followed this thread. It’s too bad
> the ACPI IRQ stacking behavior gravitates toward IRQ 9 — if only it
> were two interrupts higher, we could dub the phenomenon “Oshins’ 11”!
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Jake Oshins
> Sent: Tuesday, January 01, 2002 2:34 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: ACPI Machines and IRQ 9
>
>
> I never said that VIA chipsets were bad. I only said that they
operate
> differently from Intel chipsets, and that most BIOS code is cut and
> pasted from Intel’s examples, which means that the BIOS tends to be
more
> broken on a VIA machine than on an Intel machine.
>
> The Intel i815 is a fine chipset, but it has bugs just as all other
> hardware does. (All software has bugs too. I don’t mean to
> discriminate.) I’ve personally added five or six hacks to Windows XP
to
> make it run, which is about average for an Intel chipset. In general,
I
> don’t add as many hacks for non-Intel chipsets. But that’s just
because
> the design cycles for the other guys is shorter, and they don’t send
me
> machines with their chips in time to do anything about the problems.
>
> All the desktop chipsets shipping today, with the exception of one
from
> VIA and one from SiS, have an I/O APIC. But not all motherboard
makers
> enable the feature.
>
> I disagree with your notion of hack-job PC’s being as reliable as a
Dell
> or an HP. I spend a huge amount of my time debugging problems with
> specific motherboards. And it really boils down to finding the
> cross-product of bugs that create nasty hardware interactions and then
> avoiding them. When Dell, HP, Compaq or IBM build a machine, they
> choose a chipset and a few different component suppliers. Then they
> test the machine extensively, shaking out the incompatibilities before
> they settle on a final configuration. This process gets a much higher
> quality product into the end-user’s hands. (Incidentally, this is ten
> times as true with SMP machines. None of the raw motherboard makers
> builds one that I would consider reliable.) Part of the problem with
> building your own machine is just that you can’t personally afford to
> test each peripheral in isolation, chosing the ones that don’t have
bad
> interactions.
>
> I once debugged a machine that had a bad interaction between the
SuperIO
> chip and the CD-ROM drive. When the CD would put data on the IDE bus,
> it would cause a signal to be asserted that would cause all bytes in
the
> top lane of the X-Bus to appear as all 1’s. If that occurred while
the
> OS was doing a 16-bit read to the X-Bus, then data returned would be
bad
> in the upper byte. The problem went away if you changed to a
different
> brand of CD-ROM drive, or if you used a different SuperIO chip.
>
> In another example, you can’t get stand-by to work on a 440BX-based
> machine unless you exclude one of the three supported types of RAM.
> Using one of the other two types requires a massive BIOS hack to make
it
> work. But if you apply the hack with the wrong RAM type (and software
> couldn’t tell the difference) then the machine will hang. When I told
> ASUS about the problem, they couldn’t do anything about it because
their
> customers install the RAM themselves. When Intel told the large
> companies about it, they were all able to successfully patch their
> BIOSes.
>
> My point is that the people who design the commodity motherboards
don’t
> control the peripherals that will be matched with them. So they can’t
> guarantee that the machine, when viewed as a whole, will actually
work.
> The big guys can.
>
> - Jake Oshins
>
> -----Original Message-----
> Subject: RE: ACPI Machines and IRQ 9 [was: Communicating with the NT
> developers]
> From: “Maxim S. Shatskih”
> Date: Mon, 31 Dec 2001 14:56:33 +0300
> X-Message-Number: 19
>
> >This is a stupid story. And I’m embarrassed to tell you the truth.
> But
> >here it is.
>
> Really an interesting story, Jake. Thanks for it!
>
> >But if your machine has a VIA chipset, or if it has a BIOS that we
know
> >to be broken, then we fall back to the Win2K-style stacking behavior.
>
> So, VIA is this bad. Will know this now.
>
> >The unfortunate truth is that you guys on this list mostly build your
> >own machines, rather than buying them from reputable manufacturers,
>
> Yes, twice as cheap, and the same performance and reliability. All
> depends on parts vendor, mainly motherboard vendor.
> As about the brand names like Dell or HP - they are known to be not
100%
> compatible with the usual PC, for instance, Dell required a
> PCI card to be Dell-certified.
>
> >which means that you guys own the machines with broken BIOSes and VIA
> >chipsets.
>
> Lots of motherboards on the market (and thus self-assembled machines)
> use Intel chipsets like i815 or such.
> Is i815 bad?
>
> >One notable addendum is that any machine with an APIC interrupt
> >controller, and thus more than 16 IRQs, will spread interrupts out,
> even
> >in Win2K.
>
> And what chipsets will provide APIC on non-SMP machine?
>
> Max
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@owen-t.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to ntdev as: xxxxx@owen-t.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

:slight_smile:

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Tuesday, January 01, 2002 10:17 AM
To: NT Developers Interest List
Subject: [ntdev] RE: ACPI Machines and IRQ 9

Sorry, what is it?
I’m not a native English speaker, so what does “somebody’s 11” mean?

Max

----- Original Message -----
From: “Owen T. Cunningham”
To: “NT Developers Interest List”
Sent: Tuesday, January 01, 2002 9:06 PM
Subject: [ntdev] RE: ACPI Machines and IRQ 9

> I don’t have anything to add from a technical standpoint, but
> something interesting did occur to me as I’ve followed this thread.
> It’s too bad the ACPI IRQ stacking behavior gravitates toward IRQ 9
> — if only it were two interrupts higher, we could dub the phenomenon

> “Oshins’ 11”!
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Jake Oshins
> Sent: Tuesday, January 01, 2002 2:34 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: ACPI Machines and IRQ 9
>
>
> I never said that VIA chipsets were bad. I only said that they
> operate differently from Intel chipsets, and that most BIOS code is
> cut and pasted from Intel’s examples, which means that the BIOS tends
> to be more broken on a VIA machine than on an Intel machine.
>
> The Intel i815 is a fine chipset, but it has bugs just as all other
> hardware does. (All software has bugs too. I don’t mean to
> discriminate.) I’ve personally added five or six hacks to Windows XP
> to make it run, which is about average for an Intel chipset. In
> general, I don’t add as many hacks for non-Intel chipsets. But that’s

> just because the design cycles for the other guys is shorter, and they

> don’t send me machines with their chips in time to do anything about
> the problems.
>
> All the desktop chipsets shipping today, with the exception of one
> from VIA and one from SiS, have an I/O APIC. But not all motherboard
> makers enable the feature.
>
> I disagree with your notion of hack-job PC’s being as reliable as a
> Dell or an HP. I spend a huge amount of my time debugging problems
> with specific motherboards. And it really boils down to finding the
> cross-product of bugs that create nasty hardware interactions and then

> avoiding them. When Dell, HP, Compaq or IBM build a machine, they
> choose a chipset and a few different component suppliers. Then they
> test the machine extensively, shaking out the incompatibilities before

> they settle on a final configuration. This process gets a much higher

> quality product into the end-user’s hands. (Incidentally, this is ten

> times as true with SMP machines. None of the raw motherboard makers
> builds one that I would consider reliable.) Part of the problem with
> building your own machine is just that you can’t personally afford to
> test each peripheral in isolation, chosing the ones that don’t have
> bad interactions.
>
> I once debugged a machine that had a bad interaction between the
> SuperIO chip and the CD-ROM drive. When the CD would put data on the
> IDE bus, it would cause a signal to be asserted that would cause all
> bytes in the top lane of the X-Bus to appear as all 1’s. If that
> occurred while the OS was doing a 16-bit read to the X-Bus, then data
> returned would be bad in the upper byte. The problem went away if you

> changed to a different brand of CD-ROM drive, or if you used a
> different SuperIO chip.
>
> In another example, you can’t get stand-by to work on a 440BX-based
> machine unless you exclude one of the three supported types of RAM.
> Using one of the other two types requires a massive BIOS hack to make
> it work. But if you apply the hack with the wrong RAM type (and
> software couldn’t tell the difference) then the machine will hang.
> When I told ASUS about the problem, they couldn’t do anything about it

> because their customers install the RAM themselves. When Intel told
> the large companies about it, they were all able to successfully patch

> their BIOSes.
>
> My point is that the people who design the commodity motherboards
> don’t control the peripherals that will be matched with them. So they

> can’t guarantee that the machine, when viewed as a whole, will
> actually work. The big guys can.
>
> - Jake Oshins
>
> -----Original Message-----
> Subject: RE: ACPI Machines and IRQ 9 [was: Communicating with the NT
> developers]
> From: “Maxim S. Shatskih”
> Date: Mon, 31 Dec 2001 14:56:33 +0300
> X-Message-Number: 19
>
> >This is a stupid story. And I’m embarrassed to tell you the truth.
> But
> >here it is.
>
> Really an interesting story, Jake. Thanks for it!
>
> >But if your machine has a VIA chipset, or if it has a BIOS that we
> >know to be broken, then we fall back to the Win2K-style stacking
> >behavior.
>
> So, VIA is this bad. Will know this now.
>
> >The unfortunate truth is that you guys on this list mostly build your

> >own machines, rather than buying them from reputable manufacturers,
>
> Yes, twice as cheap, and the same performance and reliability. All
> depends on parts vendor, mainly motherboard vendor. As about the brand

> names like Dell or HP - they are known to be not 100% compatible with
> the usual PC, for instance, Dell required a PCI card to be
> Dell-certified.
>
> >which means that you guys own the machines with broken BIOSes and VIA

> >chipsets.
>
> Lots of motherboards on the market (and thus self-assembled machines)
> use Intel chipsets like i815 or such. Is i815 bad?
>
> >One notable addendum is that any machine with an APIC interrupt
> >controller, and thus more than 16 IRQs, will spread interrupts out,
> even
> >in Win2K.
>
> And what chipsets will provide APIC on non-SMP machine?
>
> Max
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@owen-t.com To
> unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com To
> unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to ntdev as: xxxxx@storagecraft.com To
unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

At 21.16 01/01/2002 +0300, you wrote:
[“Oshin’s Eleven”]

I’m not a native English speaker, so what does “somebody’s 11” mean?

It’s a (funny :slight_smile: pun on “Ocean’s Eleven” (a movie’s title)


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

“Oshins” and “oceans” are, in fact, homophones. That’s the last that
I’m going to say on this thread. I’ve already expressed my opinions and
I don’t want to stoke the flames.

  • Jake

-----Original Message-----
Subject: RE: ACPI Machines and IRQ 9
From: “Owen T. Cunningham”
Date: Tue, 1 Jan 2002 13:49:25 -0500
X-Message-Number: 12

Sorry Max, you’re correct that this joke will make sense only to
American moviegoers.

There is a film that was just released (actually a remake of an earlier
Frank Sinatra movie of the same name) starring George Clooney and Brad
Pitt. The name is “Ocean’s Eleven” — George Clooney’s character is
named Danny Ocean and the title is meant to refer to his gang of 11
thieves that he assembles to rob a bunch of casinos in Las Vegas.

Now that I think about it, this joke could turn out to completely suck
if Oshins is pronounced differently from Oceans…


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Sheesshhhh … If that is a homophone that what is a last name of Little
appended to a 300# 10 toed biped?

Gary G. Little
Broadband Storage, Inc.
xxxxx@broadstor.com
xxxxx@inland.net
(949) 7372731

-----Original Message-----
From: Jake Oshins [mailto:xxxxx@windows.microsoft.com]
Sent: Wednesday, January 02, 2002 5:20 AM
To: NT Developers Interest List
Subject: [ntdev] RE: ACPI Machines and IRQ 9

“Oshins” and “oceans” are, in fact, homophones. That’s the last that
I’m going to say on this thread. I’ve already expressed my opinions and
I don’t want to stoke the flames.

  • Jake

-----Original Message-----
Subject: RE: ACPI Machines and IRQ 9
From: “Owen T. Cunningham”
Date: Tue, 1 Jan 2002 13:49:25 -0500
X-Message-Number: 12

Sorry Max, you’re correct that this joke will make sense only to
American moviegoers.

There is a film that was just released (actually a remake of an earlier
Frank Sinatra movie of the same name) starring George Clooney and Brad
Pitt. The name is “Ocean’s Eleven” — George Clooney’s character is
named Danny Ocean and the title is meant to refer to his gang of 11
thieves that he assembles to rob a bunch of casinos in Las Vegas.

Now that I think about it, this joke could turn out to completely suck
if Oshins is pronounced differently from Oceans…


You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

On Wed, 2 Jan 2002, Gary Little wrote:

Sheesshhhh … If that is a homophone that what is a last name of Little
appended to a 300# 10 toed biped?
Inaccurate.


Peter xxxxx@inkvine.fluff.org
http://www.inkvine.fluff.org/~peter/

logic kicks ass:
(1) Horses have an even number of legs.
(2) They have two legs in back and fore legs in front.
(3) This makes a total of six legs, which certainly is an odd number of
legs for a horse.
(4) But the only number that is both odd and even is infinity.
(5) Therefore, horses must have an infinite number of legs.


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com