From: "Sammy Mitchell" 
>we just got our 10 license user copy of tse-pro. Is it possible to run
>it off the lan or do I need to install it on 10 PC's individually?
>Do I need to have just certain files on the indiv. PC but the
>main executeable can be accessed from the LAN?
Note that I am assuming you are familiar with what "Save Current Settings"
and with what "burning-in a new configuration and/or .ui file" does.  If
not, please let me know, and I'll explain it.
You can run 2.5 from the LAN, with a few limitations.  There are basically
two different ways to do it:
I.) If your users do not want to save any state information (history, the
ability to restore the previous session, etc), or change any of the default
settings, you can simply install TSE Pro on a LAN drive, tell the users to
put that directory in their path, and away they go.  Make sure that TSE Pro
is installed in a read-only directory.
You could even allow them a little configurability, by setting the editors
TSEPath variable to something like "c:\macros", or perhaps modify the tse.ui
to get TSEPath from an environment variable.  In either case, users can
place macros in "c:\macros" (or whatever it is called), including a tsestart
macro, which gets called at startup, to customize their individual versions.
Savvy users will even be able to set the editors LoadDir variable in their
tsestart macro, to achieve exactly the same results that the process below
achieves.  They would do something like this in their tsestart macro, before
doing much if anything else:
    Set(TSEPath, GetEnvStr("TSELOADDIR") + ';' + LoadDir())
    Set(LoadDir, GetEnvStr("TSELOADDIR"))
Where TSELOADDIR is an environment variable, in this example, it would be
"c:\macros".  If they want, they could just hard code it instead of using an
environment variable:
    Set(TSEPath, "c:\macros" + ';' + LoadDir())
    Set(LoadDir, "c:\macros\")
In either case, whatever is assigned to the editors LoadDir variable *MUST*
end in a backslash, or some state/info files will not be placed in the
proper place.
II.) If however, your users want to be able to save state information and/or
to have custom configurations, you will have to either have them create the
tsestart macro mentioned above, or do the following:
a) make sure that the users do not have WRITE or CREATE access to the TSE
Pro directory on the LAN.
b) You will also need to modify the tse.ui as follows:
In the WhenLoaded procedure, add the following statements just after the
variable declarations:
    Set(TSEPath, GetEnvStr("TSELOADDIR") + ';' + LoadDir())
    Set(LoadDir, GetEnvStr("TSELOADDIR"))
c) Each user will need a private writable directory, on a local or remote
drive.  The name is immaterial, but for this example, lets call it "mytse".
In this directory, they should copy all the *.dat files that come with TSE
Pro.  These files can be found in the tse\mac directory and possibly in the
tse directory.  They should also copy the user.lex from the tse\spell
directory.
Any macros the user creates, should go in this directory.
d) Each user will need to set a TSELOADDIR environment variable to the full
path of the directory created in step 3.  So, "TSELOADDIR=c:\mytse\", for
instance.  The code I gave you (plus many of the macros shipped with TSE
Pro) depend on the internal LoadDir ending with a backslash, so make sure
that whatever you set TSELOADDIR to, it ends in a "\".  Alternatively, you
could change the code I gave you above to force the trailing slash.  The
choice is up to you - I choose the lazy way out - but if one of your users
forgets, then you've got a problem!
NOTE:  If you can come up with a convention where all users will put there
TSE Pro relevant files in (for example) "c:\macros", then there is no need
for them to set the environment variable, and you could just hard code the
TSEPath and LoadDir editor variables using "c:\macros", as follows:
    Set(TSEPath, "c:\macros" + ';' + LoadDir())
    Set(LoadDir, "c:\macros\")
Limitations:
------------
1) The "Save Current Settings" command will no longer work.  This command
(in the DOS version) writes the settings back to the TSE Pro executable.
Obviously, you would not want this to happen if e.exe is shareable.
In order for users to be able to have custom settings, they can do one of
two things:
a) Place a tsestart macro in the "mytse" directory, and put any necessary
customizations in that macro.
b) Or, you could create a macro and add it to the autoload list.
To simulate the "Save Current Settings" command, users can instead use the
"Write Settings to Ascii File" under the "Full Configuration" menu.  Once
that file is saved, they can load the file into the editor, and run the
attached macro (fixcfg) to convert that file into a loadable macro.  Then
they can either add the created macro the autoload list, or call it from the
tsestart macro, or just rename it tsestart.mac.
2) Users will not be able to have their own personal .ui's.  But, this is
pretty easy to circumvent by using a tsestart macro, and/or the autoload
macros.  However, certain things, like the mainmenu, can only be set in the
users .ui file, so each user will have whichever menu system (TSE Pro, TSE
Jr, WordPerfect, or custom) the network administrator deems best.
3) The user should not attempt to change the TSEPath editor variable, since
its use is crucial to this working correctly.
4) Certain settings (those marked with '*' in Full Configuration) can only
be set at startup, via options being "burned-in" to the editor.  The user
will not have the ability to change these settings from whatever the Network
Administrator has set them at.  Fortunately, it is only a small number of
options, hopefully, none that your users need set differently than the
defaults you choose!
I hope this info proves useful; the fixcfg macro is attached, just in case
you need it.
Sammy Mitchell
SemWare corp.
---
---------------