Xref: utzoo bit.listserv.novell:10941 comp.sys.novell:1684
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!comp.vuw.ac.nz!actrix!tornado!sideways!ileader
From: ileader@sideways.gen.nz (Ian Leader)
Newsgroups: bit.listserv.novell,comp.sys.novell
Subject: Re: SetTrustee() function bug.
Message-ID: <4cHP33w164w@sideways.gen.nz>
Date: 28 May 91 12:20:38 GMT
References: <1991May24.135502.31039@kuhub.cc.ukans.edu>
Organization: Sideways Bulletin Board, Lower Hutt, New Zealand.
Lines: 32

mcginnis@kuhub.cc.ukans.edu writes:

> I have posted this twice before but I haven't figured out a
> solution and I haven't received a single reply.  The problem
> is the SetTrustee() function of the NetWare C Interface doesn't
> always work.
> 
> When I use it to set file trustee assignments on the W: drive 
> it won't usually work.  It will always work on low drive letters
> like F: or H:.  In fact, it always seems to work on drive U:.
> I did see it work once on drive W:.
> 
> It's not a problem with file security or anything because the
> tests were done on the same files in the same directories... just
> used different drive letters to map to them.
> 

I'm not familiar with the details of the API function calls, but one 
thought that occurs with relation to it only working on 'low' drive 
letters is that the 'low' drive letters are usually mapped to logical 
drives, whereas the higher ones correspond to search mappings.  
Have you tried doing a striaght MAP X:=<pathname> to overwrite a search 
mapping and see if it still fails?  Just a thought - flame me if you 
wish! :-)

                            - Ian Leader  (ileader@sideways.gen.nz)
                            - Avalon Television Centre
                            - Lower Hutt
                            - New Zealand

**These views MUST be my own because my company wouldn't be interested in
**having views on these things, anyway.