🚀 go-pugleaf

In article <baird2.257.000D5D8F@lincoln.ac.nz>, baird2@lincoln.ac.nz says...
>
>In article <5c8005$65c@eve.enteract.com> pschuman@interserv.com (Phil Schum
>an) writes:
>>From: pschuman@interserv.com (Phil Schuman)
>>Subject: Re: NDS tree name displayed wrong
>>Date: 23 Jan 1997 15:27:01 GMT
>
>>In article <5c6q4u$l3f@nnrp1.news.primenet.com>, hbae@primenet.com says...
>>>
>>>pschuman@interserv.com (Phil Schuman) writes:
>>>>we have a Novell 4.1 IPX system with a tree name of:  SYMONS_CORP
>>>>at least, this is what is displayed on the DSMERGE screen.
>>>>       which is the only place I can think of to see the name,
>>>>       as NWADMIN does not show it...
>>>>however - 
>>>>when I bring up NWPOPUP on a WIN3.1 client,
>>>>the 'tree' has a name of 'SYMONS CORP' - - no underscore
>>>>I'll have to check and see what WIN95 shows...
>>>>any ideas on who is right - ??
>>>
>>>Both.  "_" and spaces are equivalent.  "_" are used as fillers.  I don't
>>>like spaces so I don't use them.  Down the road... you'll run into
>>>problems somewhere!
>>>
>>>
>>interesting - 
>>here is the added piece that confused me - when using the NWPOPUP
>>in Win 3.1x to get logged in 
>>(again, I have not looked at the Win95 stations)
>
>>        one of the trees = SYMONS_CORP  displayed as  SYMONS CORP
>
>>                  server = SYMONS_PROD  displayed as  SYMONS_PROD
>
>>so - the tree is NOT displaying the 'underscore' but the server is ???
>
>According to Hughes and Thomas in "Netware 4.1 networks", a tree name may
>comprise A-Z (uppercase only) 0-9, '-' and '_', and it cannot start or end 
>in
>an underscore or contain more than one adjacent underscore. So the actual
>tree name will be SYMONS_CORP, but for whatever reason NWPOPUP is
>replacing '_' with a space. Both spaces and underscores may be used in NDS
>object names, but if you create an object in bindery mode with an underscor
>e
>in the name, the object appears in NDS with a space instead.
>
>John

checked on a WIN95 machine - 
and suprise - the SYMONS_CORP tree name is ok !! (no space)
so, it's NWUSER that is displaying the tree name incorrectly... (with space)
nice - huh - 
Phil -