home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Professional
/
OS2PRO194.ISO
/
os2
/
editor
/
sedt
/
install.how
< prev
next >
Wrap
Text File
|
1994-01-31
|
2KB
|
49 lines
It is strongly advisable to install Sedt in its own subdirectory.
This makes organization of the files and future updates much
easier. To create a subdirectory under OS/2 use the MD command.
For example
MD C:\SEDT
will create a directory calles SEDT on drive C.
Next copy all files from the installation floppy to the
subdirectory with the COPY command. For example
COPY A:*.* C:\SEDT
Now check that SEDT will run by making the directory containing
all the files you current working directory. For example
C:
CD \SEDT
SEDT
Sedt should fire up and be ready to accept commands.
The next step is to make Sedt runnable from any directory. The
simplest way to do this is to include the directory containing
Sedt in your PATH statement in CONFIG.SYS. See your OS/2 manual
for instructions.
You can speed up initialization if you create the logical name
SEDT which should contain the directory with the Sedt files.
This is done with the SET command in CONFIG.SYS. For example
SET SEDT=C:\SEDT
In a file server environment you may wish to separate the files
into public, sharable files and user-specific files for
customization and data files. The environment variable SEDT
should point at the public directory, which may be read only.
The logical name PSEDT should point at the users private
directory, to which there must be write access. Here the user
can create a private SEDT.CNF file, rulers will be saved here,
and any other data file created by Sedt will reside here.
Once you have Sedt up and running, you will probably want
to start customizing it for your preference. By creating a file
called SEDT.CNF as instructed in SEDTMAN.EDT, section 2.3.1, you
can increase performance dramatically and also make it behave the
way you prefer.