From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0714_01C31325.E2010060
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   How changes in machines are communicated depends on how you have your =
network configured.  If you don't have WINS running then you are relying =
entirely on broadcasts and individual machines or browser masters =
listening to these and keeping their own lists.  If you want this to be =
fast, have the WINS service running.

   New shares on a specific machine are enumerated whenever you ask for =
them.  If they don't show up immediately then there is something funny =
going on with the sharing machine.

Rich

  "Frank Haber"  wrote in message =
news:3eb6d6c5$1{at}w3.nls.net...
  I mean that XP is slow in recognizing *any* change in available =
machines on
  the peer LAN. The Snap! is quite fast.  George gave me a patch for a
  RemoteComputer\NameSpace hex key that sped up my 2000 machines =
dramatically.
  I haven't tried it on XP - I'm chicken.

  NETBEUI is active on all machines here, and needs to be: there are a =
couple
  of NETBEUI-only WFWG machines we actually use sometimes.  I've not =
tried the
  Win2000 NETBEUI on XP, which a couple of people have recommended I =
try.

  And I don't think SMB is hot except when the  Samba on the Snap! is at =
work,
  no?  There are seldom any Linux machines with active human and console =
on
  this net.  The XP machine is fast enough opening folders and copying =
files
  to/from any machine.  It's just slow recognizing new shares, and =
*very* slow
  recognizing new, or just-powered-on but previously known machines.  =
All
  machine, volume and share names are LanMan-ish, <9chars USASCII
  alphanumeric, caps only - and unique.


------=_NextPart_000_0714_01C31325.E2010060
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   How
changes in machines =
are=20
communicated depends on how you have your network configured.  If
= you don't=20
have WINS running then you are relying entirely on broadcasts and = individual=20
machines or browser masters listening to these and keeping their own=20
lists.  If you want this to be fast, have the WINS service=20
running.
 
   New
shares on a specific =
machine are=20
enumerated whenever you ask for them.  If they don't show up =
immediately=20
then there is something funny going on with the sharing =
machine.
 
Rich
 

  "Frank Haber" <frhaber{at}N0SPMrcn.com>">mailto:frhaber{at}N0SPMrcn.com">frhaber{at}N0SPMrcn.com>
=
wrote in=20
  message news:3eb6d6c5$1{at}w3.nls.net...I=20
  mean that XP is slow in recognizing *any* change in available machines =

  onthe peer LAN. The Snap! is quite fast.  George gave me a =
patch for=20
  aRemoteComputer\NameSpace hex key that sped up my 2000 machines=20
  dramatically.I haven't tried it on XP - I'm =
chicken.NETBEUI is=20
  active on all machines here, and needs to be: there are a coupleof =

  NETBEUI-only WFWG machines we actually use sometimes.  I've not =
tried=20
  theWin2000 NETBEUI on XP, which a couple of people have =
recommended I=20
  try.And I don't think SMB is hot except when
the  Samba =
on the=20
  Snap! is at work,no?  There are seldom any Linux machines =
with active=20
  human and console onthis net.  The XP machine is fast enough =
opening=20
  folders and copying filesto/from any machine.  It's just slow =

  recognizing new shares, and *very* slowrecognizing new, or =
just-powered-on=20
  but previously known machines.  Allmachine, volume and share =
names=20
  are LanMan-ish, <9chars USASCIIalphanumeric, caps only - and=20
  unique.

------=_NextPart_000_0714_01C31325.E2010060--

--- BBBS/NT v4.01 Flag-4