Scott Parks wrote in a message to Mike Bilow:
 SP> .. it will prompt
 SP> you for a login, map just that one drive .. and then run. 
 MB> That should not be possible: the system login script should
 MB> always execute for the user, no matter how they log in.  One
 MB> possibility is that you are running on NW 4 with NDS active,
 MB> and the login normally proceeds as NDS but the special login
 MB> proceeds as Bindery emulation.  
 SP> It's Netware 3.11 and if you don't check "run logon scripts"
 SP> _or_ just bypass the login screen .... you end up with only
 SP> your local drives in "my computer".  With this program ...
 SP> it gives a WIN  login (client I'm using now) and then runs. 
 SP> If you then look at  "my computer", only one additional
 SP> drive is mapped.
Maybe this is some oddball NW 3.11 issue.  I have almost no experience 
running Windows 95 clients on NW 3.11, as all but one server accessed by 
Windows 95 clients are on either NW 3.12 or NW 4.11 now.  The exception is, 
believe it or not, our own test server, which is a 386DX-20 that has been 
around forever.  I don't recall ever testing the Novell client against this 
server, either.
I did have to implement a huge number of required fixes and patches on the NW 
3.11 server to support Windows 95 clients of any type, all of which are 
basically the same as you would need to support OS/2 clients on NW 3.11 -- 
fast file open handling, long file name support, and so forth.
 SP> Like I said ... never seen it before!
Neither have I.
 
-- Mike
--- 
---------------