home *** CD-ROM | disk | FTP | other *** search
- READNET.TXT
-
- DOCUMENTATION FOR THE NODE SETUP PROGRAM, NODE.EXE
-
- ==================================================
-
- The Node Setup program, node.exe, was designed to setup nodes
- that will be running shared Ami Pro 2.0 from a network. No
- other system administration is required to setup nodes to run
- Ami Pro. NOTE: Ami Pro 2.0 should be installed on the network
- prior to running NODE.EXE.
-
-
- STEPS TO SET UP AMI PRO 2.0 ON A NETWORK:
-
- =========================================
-
- 1. Follow the instructions in the Installation Guide for
- installing Ami Pro 2.0 on a network.
-
- 2. Create a Node directory on the network server.
-
- 3. Copy the following Node files from disk 4 to the Node
- directory on your hard drive. (The node setup cannot be run
- from a floppy disk.)
-
- NODE.EXE
- SCRIPTN.INS
- NODEINFO.INS
- COMPRESS.DLL
- INI.CMZ
- IMAGEINI.CMZ
- EQNINI.CMZ
- READNET.TXT
-
- 4. From within Windows, run the Node Setup program, NODE.EXE, as
- the system administrator. During the Node Setup you will be
- asked for directory names into which files will copied, and you
- will be asked to insert a disk from the original Ami Pro install set.
-
- 5. Run NODE.EXE on each workstation to set them up to run Ami Pro
- from the network.
-
-
- USING NODE.EXE TO PERFORM SYSTEM ADMINISTRATION:
-
- =================================================
-
- When the network administrator runs NODE.EXE, the file
- NETADMIN.INI is created in the Ami Pro directory on the
- network. When NODE.EXE is run from individual workstations,
- it looks for this file. NETADMIN.INI contains the
- following lines:
-
- [AmiPro]
- LocalDirs=[TRUE|FALSE]
- macrodir=[full path of the AMIPRO\MACROS directory on the network]
- stypath=[full path of the AMIPRO\STYLES directory on the network]
- docpath=[full path of the AMIPRO\DOCS directory on the network]
-
- If LocalDirs is set to TRUE, node users are allowed to have
- local directories for their Ami Pro macros, documents, and style
- sheets.
-
- NOTE: When individual nodes are installed, all the files in
- the macros, styles, and docs directories will be copied to the
- directories specified by the user. If, for example, the docs
- directory has grown to several hundred files, they will all be
- copied to the users docs directory during the node install.
- Therefore, it might be advisable to create a set of "master"
- directories that contain only the original files and will not
- have files added to them.
-
- If LocalDirs is set to FALSE, node users are not allowed to have these
- local directories and must use the macros, documents, and style
- sheets that are on the network.
-
- If the file NETADMIN.INI does not exist, the Node Setup program
- will create it for the system administrator. NODE.EXE will bring up
- dialog boxes that prompt the system administrator for information that
- will be placed in the NETADMIN.INI file. Therefore, the first time
- NODE.EXE is run, it should be run by the system administrator of the
- network so that it contains accurate information. Furthermore, it must
- be run by a user with write permission in the shared Ami Pro
- directory on the network (usually the system administrator). An
- alternative method is to create NETADMIN.INI manually, and then
- edit the file to contain the above information.
-
-
- USING NODE.EXE TO SET UP INDIVIDUAL NODES:
-
- ==========================================
-
- Once NETADMIN.INI exists, NODE.EXE can be used to set up
- individual nodes (workstations) on the network for Ami Pro. The
- program should be run on each node that wishes to run Ami Pro
- from the network. Certain files needed by Ami Pro will be
- placed on the user's local machine, and icons for Ami Pro and
- Ami Pro's Dialog Editor will be put in the group Lotus
- Applications under the Program Manager (if that is the main
- shell used on that node).
-
- Technical Information: NODE.EXE copies several .INI files to the
- user's Windows directory (amipro.ini, apib.ini, amiimage.ini, amieqn.ini).
- Then it puts the Microsoft OLE libraries in the user's Windows
- directory if they're not already there. Next, if local directories are
- allowed, it copies the contents of the document, macro, and style
- directories to the user's local directories. Finally, it adds icons
- to the Program Manager and makes an entry in the [Extensions] section
- of the win.ini.
-