On 19 Jan 98 10:50pm, Mike Bilow wrote to Scott Parks:
 MB> 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.
 MB> Maybe this is some oddball NW 3.11 issue.  I have almost no
 MB> experience running Windows 95 clients on NW 3.11, as all but
 MB> one server accessed by Windows 95 clients are on either NW 3.12
 MB> or NW 4.11 now.  The exception is, believe it or not, our own
 MB> test server, which is a 386DX-20 that has been around forever.
 MB> I don't recall ever testing the Novell client against this
 MB> server, either.
 MB> I did have to implement a huge number of required fixes and
 MB> patches on the NW 3.11 server to support Windows 95 clients of
 MB> any type, all of which are basically the same as you would need
 MB> to support OS/2 clients on NW 3.11 -- fast file open handling,
 MB> long file name support, and so forth.
 SP> Like I said ... never seen it before!
 MB> Neither have I.
I would think this this is the customary scenario as seen by any client
running from a workstation for a connection to a Netware server.  The
client (be it NETX, VLM, CLIENT32) would do an ATTACH to the server,
providing a single drive letter (F:) for the purpose of running the
LOGIN CLU.  This one drive letter and directory (LOGIN) are the only
items accessable on the server until properly logged in and/or
authenticated.
BTW, there are no required patches or fixes to NW3.11 to support
Windows95 clients.  All the patches are to fix or enhance CLU's and the
OS itself from its original shipped coding.  None of them are specific
to Windows95 or OS/2.  There are some .DLLs that need changing in the
OS/2 Netware Requester v2.12 itself if you wish to use it with NW3.11
(must go back to older versions that shipped with Requester v2.11) since
those were modified for 3.12 and 4.x.
Also, long filename support is not required unless you're planning on
using it.
I've been running my 3.11 server for quite a number of years and
currently have NT4 Workstation, NT4 Server, OS/2 Warp 4, Windows95 and
WFW tied into it quite nicely without having to go through any special
steps concerning support.  I only insured that the Minimum OS Updates as
published by Novell have been applied to the server.
I know I'm going to have to upgrade soon.  I just hate having to do so.
This server's been so stable for so long! :)
George
... British boobs are the best in the world.
--- Via Silver Xpress V4.4P [Reg]
---------------