Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!munnari.oz.au!bruce!monu0.cc.monash.edu.au!vaxc.cc.monash.edu.au!steved
From: steved@vaxc.cc.monash.edu.au
Newsgroups: comp.sys.novell
Subject: Re: Login Script Gods, Ahoy
Message-ID: <1991May3.091948.86655@vaxc.cc.monash.edu.au>
Date: 2 May 91 23:19:47 GMT
References: <1991Apr30.201944.39@maytag.waterloo.edu>
Organization: Computer Centre, Monash University, Australia
Lines: 20

In article <1991Apr30.201944.39@maytag.waterloo.edu>, ckirie@csg.uwaterloo.ca (Chris Irie) writes:
>
> A question for anyone who has hacked around with Novell login scripts...
> The SUPER REFERENCE book says that loading TSRs in a login script
> using the EXIT command is a no-no. It seems that running them using
> the "#" command is also kind of iffy.
>
> Is there some way to load TSRs from a login script that _does_ work?
>

Any TSR loaded during the execution on a login script must load into memory
beyond the end of the LOGIN.EXE image in memory. When LOGIN.EXE completes
you will have a sizable gap in low memory.

A method I have found that does work is to use the script EXIT "COMMAND"
type command. I am told the keyboard buffer is stuffed with the COMMAND
as LOGIN.EXE terminates, so you have to keep it short. Mine connects with
a batch file that does TSR-like things.

SteveD.