Re: How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using
From: Dick Kistler (dickkist_at_Remove-hotmail.com)
Date: 08/01/04
- Next message: cindy: "windows error message"
- Previous message: S.Low: "POP3 Problem"
- Next in thread: N. Miller: "Re: How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using"
- Maybe reply: N. Miller: "Re: How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using"
- Maybe reply: N. Miller: "Re: How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using"
- Maybe reply: N. Miller: "Re: How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 31 Jul 2004 20:17:06 -0400
"Phillip Windell" <@.> wrote in message
news:ebH0jKmdEHA.384@TK2MSFTNGP10.phx.gbl...
> "Dick Kistler" <dickkist@Remove-hotmail.com> wrote in message
> news:%238vgKdcdEHA.1184@TK2MSFTNGP11.phx.gbl...
> > Nah, there is a place for a non-routable protocol in instances where
> > internet access
> > is not wanted or needed. For instance, in a network that is dedicated to
> > a particular job, and where internet connectivity is not wanted.
>
> I agree. There are situations such as what you describe where NetBEUI is
> "handy". But to be honest, it doesn't matter much to me what they do with
> it. I can take it or leave it. Believe it or not I liked DOS, I thought it
> was just fine for what it was designed to do, and even today it works just
> fine on older equipment that only requires a simple OS like that. MS
dropped
> support for DOS a long time ago yet there is no shortage of it if someone
> wants a copy of it for something.
Yes, there are still lots of DOS(or maybe Windows for Workgroups 3.11)
machines
doing lots of good work out there. The rest of the world does not throw out
things so quickly when they work, as the electronics/computer industry does.
I once worked in the Chemical Industry where, when you install a control
system
you are talking about a 20-30 year lifetime. And have worked in plants with
50
year old control systems.
One thing that I have noticed about DOS and Windows 3.11 is that they run
real fast
on 200 MHz machines, too. And it can do lots of stuff-remember we were
running
the world using it 10 years ago. We would have been pleased as punch with
MSDOS
at 200 MHz.
And IBM is still selling it.
But you have to remember that MSDOS in say, 1994 had been about the same
OS for quite a long time-maybe 13 years. Windows XP is still very young.
And clearly Microsoft can do whatever they want to with NetBEUI, even if it
were
some kind of standard. Once upon a time Windows had many protocols
available,
but only two are left: TCP/IP and NWLink. Maybe I can get NWLink to work.
But not so far.
***
- Next message: cindy: "windows error message"
- Previous message: S.Low: "POP3 Problem"
- Next in thread: N. Miller: "Re: How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using"
- Maybe reply: N. Miller: "Re: How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using"
- Maybe reply: N. Miller: "Re: How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using"
- Maybe reply: N. Miller: "Re: How to tell which protocol (NetBUI or TCP/IP) each Network Neighborhood connection is using"
- Messages sorted by: [ date ] [ thread ]