Of course they do, and when you actively participate in that
as well it's a bit too late to come back and point at the
opposing view.
It's never too late to criticize someone for not making sense - like
you're doing now. There's no logical conflict with continuing to
argue/explaing something for the duration of flawed attempts at
counter-arguments, and at the same criticizing the very same argument
style which, esp several post in, frequently floods a thread with crap
& defensiveness instead of insight, just like this (now) silly thread.
There's no reason why an internet "debate" can't or shouldn't have
mostly valid arguments with little repetition and of varying
persuasiveness.
Then what would you prefer, that arguments go on flawed?
Nope. You're again proving my point. Unable to develop more
convincing arguments or tolerate criticism, you're still just
generating text, getting defensive, and making no sense.
I"m well aware that you think you're right when you get into
arguments, but who doesn't have same belief in same
situations?
If you put something out there and it turns out to be wrong, then suck
it up and move on. If its being challenged and you can make it more
convincing then do so. Believing your right no matter what and
getting mad instead of more clear/convincing is just plain stupid,
delusional & a waste of bandwidth. Just because you haven't
challenged me very successfully in the past doesn't mean I can never
acknowledge when I'm wrong or missing details. It happens- you're
just not there.
You really should pay more attention to my posts then, I
certainly did mention routablity previously.
Mention? Indeed little more.
and? So? Advanced NetBIOS over IPX or TCP/IP takes advantage of the
routability of these communication devices and is routable. You've
been talking down any impact from protocol combinations and talking up
the benefits of NETBUI. That you "mentioned" routability doesn't
really impeach that observation - or at least it doesn't do it very
well.
I feel WinXP has made it pretty clear that MS sought to
dumb-down networking and make it easier for the new users.
Which is easier for (those users), multiple protocols where
they have to pick things or just having TCPIP do it all by
default?
The interface for configuring networking has been pretty standard or
at least closely related to/since the Win 95,NT days. Nothing's been
dummed down, really. It's only that some backwards-compatibility for
an EOL protocol is limited/problematic. It's not like 2000 came by
default with NETBIOS and no TCP-IP by default.