No, I was actually up during the middle of the night after donating
*** and then crashing for several hours, really had no business
attempting to be coherent on Usenet at that time, and only partially
succeeded. Ordinarily, I'd have properly re-found the date stamp on the
original newsgroup posting before saying that, but I was just too tired.
(That's a poor excuse, I know. I knew I was likely to get it slightly
wrong, but was exhausted and momentarily didn't care. My lazy
guesstimate about the number of months until Microsoft's NT patch was
off, too -- but in the ballpark.)
Now that you mention it.... Hmm, I notice that their earlier
they posted in 1998 doesn't exist, any more. Ah, here:
I found that by googling for Intel's mind-numbing moniker for the
problem, "Invalid Operand with Locked CMPXCHG8B Instruction". Page
claims that NT 3.51 got some sort of hotfix, but they don't actually
name or link that hotfix. NT 4.0 got a fix as part of SP 4.0. Win95
_never_ got any sort of fix, it seems -- just as I was saying in '98.
It's a bit frightening to think that I might personally have been -- for
a while -- the best-informed commentator on this problem other than
Robert Collins (who wasn't saying much). And I was a rank amateur. ;->
Yes, that was quite bogus. Here's the actual vendor statement, from
Intel's inforamtional page:
"Novell's network operating system NetWare/IntranetWare is not
affected by the invalid instruction erratum found in the Pentium
processor. NetWare/IntranetWare requires proper authentication to run
NLM's [sic] and applications on the server. Due to this secure
access, NetWare/IntranetWare is not susceptible to NLM's [sic] or
applications that would use the invalid opcode. For further
information, please contact Novell at 1-801-861-5533 or www.novell.com."
Senior Marketing Manager
Cheers, "Due to circumstances beyond our control, we regret to
Rick Moen inform you that circumstances are beyond our control."
XXXX@XXXXX.COM --Paul Benoit