Subj : Re: drive mapping problems To : Leonard Erickson From : Darren Gibbs Date : Thu Jun 08 2000 12:29 pm LE> Login does the following on it's own (no such commands in the login LE> scripts) LE> Search 1 gets mapped to SYS:PUBLIC LE> Search 2 gets mapped to SYS:PUBLIC\\\ That's the default login script runing. I assume you use user login scripts without applying a system {or container, or profile} login script? LE> And I map several other drives in a batch file after login. LE> The problem is that often, S1 or S2 wind up mapped to the *root* LE> directory. Ditto for the other search drives I add later in the batch LE> file. This *never* happens from the command line, only at login or LE> from batch files. LE> The error message is "Directory XXXX is not locatable". Huh? Sounds like some form of rights issue - are you certain the users concerned have R & F rights to these directories? LE> Also, frequently, mapped drives (even non-search drives) map LE> correctly, but you can't *change* the directory. LE> The Win95 systems have an additional wrinkle. When I open a second DOS LE> window, the search drives aren't mapped as search drives. And trying LE> to change mappings in one DOS window will clobber the mappings in LE> another window. LE> Obviously *something* is wrong. But what? What client revision are you running? Some of the W95 clients are absolute _dogs_, and have loads of bugs. Have you updated to the latest one? DaZZa --- GoldED/2 3.00.Beta5+ * Origin: WOW BBS - Coming Soon! Netware for the Nintendo! (3:712/888) .