Category : File Managers
Archive   : TM18A.ZIP
Filename : NETWORK.DOC

 
Output of file : NETWORK.DOC contained in archive : TM18A.ZIP





Turbo Menu v1.8a/1.8g 1 Feb. 1990 (Network Information Manual)
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ
E A G L E W a r e 1987,1988,1989,1990
ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

ððððððððððððððððððððððððððððððððððððððððððððððððððððððððððððððððððð

EagleWare Software Engineering
c/o Rick Prince
P.O. Box 30416
Yukon Station
Jacksonville, FL 32230


TURBO MENU NETWORK INFO GUIDE

Version 1.8a/1.8g
February 01, 1990


Turbo Menu has been used and tested under the Novell and DECnet
Networking environments.

This document is being provided for information purposes only and
assumes the networking user/installer has previous network experience
in the use of network software and networks in general. In order to use
Turbo Menu in a networking environment all that is required is that you
install Turbo Menu's main executable file (TM.EXE) on a public
drive/disk and have the disk/drive path in the in the users start-up
batch file for accessing the network (STNET.BAT for example). Place all
of the other files that are packaged with Turbo Menu (TMCONFIG.DAT &
TMCOLOR.DAT for example) in a subdirectory of there own (C:\MENU) on
each users system that wants/has access to Turbo Menu over the network.
Placing the path of this subdirectory also in the users start-up batch
file (either AUTOEXEC.BAT or STNET.BAT for example). Use the file M.BAT
to call-up Turbo Menu, making sure that M.BAT goes to the subdirectory
on each individual system wanting access to Turbo Menu. Assuming the
subdirectory C:\MENU (user's harddrive) and R:\TURBO_M (network
harddrive) exists the following is an example of file/program
placement:



USER HARDDRIVE
C:\(ROOT)ÄÄÄÄÂ BATCH
à DECNET
à DOS33
à EWORDÄÄÄÄÄÄÄÄÄÄ ESE
³ À TEMP
à FASTBACK
À MENUÄÄÄÄÄ[*FILES*]
TMCOLOR.DAT
TMCONFIG.DAT
M.BAT
EAGLETL.EXE

NETWORK HARDDRIVE
R:\(ROOT)ÄÄÄÄÂ DECNET
à DOSX
à MGR
à PCAPPÄÄÄÄÄÄÄÄÄÄ HG
³ Ã LOTUS
³ Ã TURBO_MÄÄÄÄÄ[*FILES*]
³ ³ TM.EXE
³ À ZIPWARE
À GRAPHICS

Examples:
With the previous file placement example in mind then note the following:

Path
Data to add to the User's PATH (Path=C:\MENU;R:\TURBO_M;)

Example M.BAT: (Used to call up Turbo Menu)
ECHO OFF
C:
CD\MENU
TM %1 %2
TMGO

1) ECHO OFF =====> Turn echo off
2) C: =====> Drive location of TM.EXE support files (ie: TMCOLOR.DAT)
3) CD\MENU =====> Home directory of TM.EXE support files (ie: TMCONFIG.DAT)
4) TM %1 %2 =====> Command to call-up Turbo Menu. Searches the PATH to find
where TM.EXE is (ie:TM.EXE on R:\PCAPP\TURBO_M) and pass
any command line parameters to TM.EXE if applicable.
(See TM.DOC for command line parameter info)
5) TMGO =====> Batch file created by TM.EXE. This file will be created
and placed into C:\MENU

Example TMGO.BAT (Batch file that is dynamically created by TM.EXE)
ECHO OFF
CLS
R:
CD R:\PCAPP\XTREE
ECHO * [ Loading Xtree Pro ] *
XTPRO.EXE
C:
CD C:\MENU
CLS
ECHO * [ Returning to Turbo Menu ] *
M 2 1

1) ECHO OFF ====> Turn echo off
2) CLS ====> Clear the users screen
3) R: ====> Log on to R:\ drive
4) CD R:\PCAPP\XTREE => Change to subdirectory R:\PCAPP\XTREE
5) ECHO * [ Loading Xtree Pro ] * => Echo to the user what is being
loaded into memory
6) XTPRO.EXE ===> Program name to run (load)
7) C: ====> Log back on to C:\ drive
8) CD C:\MENU ==> Change to subdirectory C:\MENU
9) CLS ====> Clear the users screen again
10) ECHO * [ Returning to Turbo Menu ] * => Echo to the user that we are
returning to Turbo Menu
11) M 2 1 ====> Call up M.BAT again and pass the numbers "2 1" to
TM.EXE

Program execution:

Ú> M.BAT <ÄÄÄÄÄÄÄÄÄÄÄ¿ ÚÄÄÄ> TMGO.BAT
³ 4 1 3 2 ºººººººº
³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄ> TM.EXE ºººººººº
³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ> TMGO.BAT <ÄÄÄÄÄÄÄ¿
³ 7 5 ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ ³ ³
³ ³
³ 6
ÀÄÄÄÄÄÄÄÄ> FILENAME.EXE


1) M.BAT has control and loads TM.EXE
2) TM.EXE creates and/or modifies TMGO.BAT
3) TM.EXE ends and M.BAT takes control again
4) M.BAT continues on, it loads and turns control over to TMGO.BAT
5) TMGO.BAT now has control and runs FILENAME.EXE
6) FILENAME.EXE ends and TMGO.BAT takes control again
7) TMGO.BAT continues on and turns control over to M.BAT
and the loop continues.

And thats all there is to it, runs like a champ and lasts a long time.

Rick Prince
EagleWare, Software Engineering
Jacksonville, Fl