decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Even on a "secure" network it wasn't trustworthy. | 402 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Even on a "secure" network it wasn't trustworthy.
Authored by: jesse on Thursday, May 17 2012 @ 07:20 AM EDT
simple retransmissions of packets could cause it to crash.

And a simple divide by 0 caused an entire network to fail.

C2 on a network requires it to work properly... and it didn't.

Which was why it required the network to be disconnected for any C2 level
operation.

That was the MS lie.

I tried to get the NSA manual for NT - couldn't be done (and I was a contractor
to the Navy at the time). Did it exist? yes, sort of. but as far as I know it
was never released.

[ Reply to This | Parent | # ]

NetBEUI != TCP/IP
Authored by: artp on Thursday, May 17 2012 @ 09:30 AM EDT
I usually reserve the word "lies" for intentional untruths.
When you ignore several people who have personal experience
with the truth [before I replied], then I would call that a
lie.

The Internet is TCP/IP. Windows was not, and to some extent,
is still not today. When they added TCP/IP, it was bolted
on, not integrated into the OS.

Wikipedia states:

"Consequently, even today, Microsoft file and printer
sharing over Ethernet continues to be called NetBEUI, with
the name NetBIOS commonly used only in reference to file and
printer sharing over TCP/IP. In truth, the former is the
NetBIOS Frames protocol (NBF), and the latter is NetBIOS
over TCP/IP (NBT)."

Stick to the facts, not your opinions. And bring some
references to back them up. It's OK to be wrong, especially
if you can admit it. But trolling for Microsoft isn't going
to get you anywhere in a forum where the goal is to uncover
the facts.

The problem with misrepresenting the facts here is that
there are a number of people here who actually designed and
implemented basic computer technology. I never fail to get a
thrill reading some of the reports of history that appear
here. I am just a hack. I didn't design anything, although I
wanted to. I just had the privilege of being there to help
implement new technology in a production environment.

---
Userfriendly on WGA server outage:
When you're chained to an oar you don't think you should go down when the galley
sinks ?

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )