home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!sun-barr!ames!purdue!news.cs.indiana.edu!lynx.unm.edu!umn.edu!gaia.ucs.orst.edu!flop.ENGR.ORST.EDU!xanth.CS.ORST.EDU!villalj
- From: villalj@xanth.CS.ORST.EDU (John Villalovos)
- Newsgroups: comp.sys.novell
- Subject: Re: Toward a more persistent login.exe
- Date: 21 Jan 1993 05:17:10 GMT
- Organization: Oregon State University
- Lines: 30
- Message-ID: <1jlbkmINNc06@flop.ENGR.ORST.EDU>
- References: <mr.727477099@ogre> <1jiv06INN1tj@flop.ENGR.ORST.EDU> <holbor.44.0@ccmail.orst.edu>
- NNTP-Posting-Host: xanth.cs.orst.edu
-
-
- In article <holbor.44.0@ccmail.orst.edu> holbor@ccmail.orst.edu (Richard Holbo) writes:
- >>The way I do it at my work is set up a batch file called WSLOG.BAT which is
- >>executed by the AUTOEXEC.BAT:
- >>
- >>WSLOG.BAT:
- >>...
- >>:LOOP
- >>LOGIN
- >>IF ERRORLEVEL 1 GOTO LOOP
- >>
- >This does not neccarily (sp) work, with older versions of Login.exe there
- >are no errorlevel's set at all. What I ended up doing was to check for the
- >Existence of Sys:public\map.exe. This will exist for Most everyone unless
- >they arent members of Everyone or you have messed around a LOT with the
- >rights for the group Everyone. Anyway relavant part of batch file is:
- >
-
- I have only done this on NW 2.15 servers and up. Those have all worked with
- the login command returning error levels. But if the person is using a
- version lower then that then they might run into problems as you stated.
- I think they can get an updated set of utilities which should include
- LOGIN.EXE if they are having a problem.
-
- Later,
- --
- John Villalovos
- Certified Netware Engineer
- villalj@xanth.cs.orst.edu
- (503) 753-7883
-