home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.novell
- Path: sparky!uunet!pmafire!mica.inel.gov!ux1!fcom.cc.utah.edu!gateway.univel.com!ns.novell.com!novell.com!klewis
- From: klewis@novell.com (Kimo Lewis)
- Subject: Re: More rprinter.exe
- Message-ID: <klewis.19.0@novell.com>
- Sender: usenet@Novell.COM (Usenet News)
- Nntp-Posting-Host: klewis.nsd.provo.novell.com
- Organization: Novell, Inc.
- References: <727245689snx@seswho.chi.il.us> <1jkc2lINNfa9@uxa.ecn.bgu.edu>
- Date: Wed, 20 Jan 1993 22:35:56 GMT
- Lines: 56
-
- In article <1jkc2lINNfa9@uxa.ecn.bgu.edu> mftjs@uxa.ecn.bgu.edu (T. Jerry Scott) writes:
- >From: mftjs@uxa.ecn.bgu.edu (T. Jerry Scott)
- >Subject: Re: More rprinter.exe
- >Date: 20 Jan 1993 14:18:29 -0600
- >In article <727245689snx@seswho.chi.il.us> slice@seswho.chi.il.us (Steve Steiner) writes:
- >>I have an interesting problem with rprinter. When I try to have it start
- >>via the users login script, the workstation is left with about 128k of base
- >>memory. But when rprinter is started from the autoexec.bat of the workstation
- >>the problem goes away. Am i not to load rprinter from the login script, or
- >>am I just missing something? We're runnig Novell 3.11 on a 486DX2-66 and the
- >>workstations are 286SX-25 with 2mb of memory. Not sure what version of
- >>rprinter.exe.
- >>Steve Steiner slice@seswho.chi.il.us
- >
- >There is an article in the latest InfoWorld on these problems. Briefly,
- >when you load rprinter inside the system login script, you must load
- >that tsr inside of the ram left with login.exe loaded. Thus, you lose
- >about 100 or more K of ram that way. Another solution is to put
- >rprinter.exe in the login directory, and flag it as sharable. Then,your
- >autoexec.bat file does something like
- >
- > ipx >nul
- > net5 >nul
- > f:
- > rprinter pserver printer#
- > login
- >
- >This works and now you have not lost the ram, only taking out about 5K
- >for rprinter. I have done the above for diskless workstations.
- >
- >Hope this helps.
- >
- >Thanks for your Message. Keep in Touch.
- >=====================================================================
- >Thomas J. Scott (aka Dr. J.) Phone: 309-298-1452
- >Western Illinois University mftjs@uxa.ecn.bgu.edu
-
-
- You may also simply exit the login script to a bat file and within
- that bat file, call rprinter.exe. Let me give you an example.
-
- LOGIN SCRIPT
- map s1:=sys:public
- #capture
- exit "print.bat"
-
- PRINT.BAT (found in public)
- rprinter pserver 0
-
- The syntax for rprinter.exe is "rprinter printServerName printerNumber".
- If you use this method in the system login script, the user's login scripts
- won't be executed.
-
- Kimo Lewis
- Klewis@Novell.com
-
-