home *** CD-ROM | disk | FTP | other *** search
Text File | 1990-07-20 | 45.1 KB | 1,230 lines |
- *****************************************
-
- READNET.TXT - Amí Professional ver. 1.2
-
- *****************************************
-
- Amí Professional can be installed on networks that are
- compatible with Microsoft Windows. If you are currently working
- with Microsoft Windows on your network, you should have no
- problems installing and running Amí Professional. If you don't
- have Microsoft Windows, you can install Amí Professional using
- the SAE Run-Time version of Windows provided with your software.
- Microsoft indicates that Windows is compatible with any 100%
- Microsoft networks redirector-based network shells. To determine
- whether your network software is compatible with the Microsoft
- networks redirector-based network shell, contact your network
- software manufacturer.
-
- This guide assumes that you are familiar with the network
- operating system and DOS. It contains detailed information about
- installing Amí Professional on Novell and 3COM networks;
- however, similar procedures can be followed to install on other
- Windows compatible networks.
-
- If you are using a Novell network and full Windows/286 or
- Windows/386, version 2.11, you may need an updated KERNEL.EXE
- file to correct erratic performance. Errors may vary from
- problems loading Amí Professional or other Windows applications
- to problems saving files and system lock-ups. The new version of
- KERNEL.EXE (for Windows/286 version 2.11) is included on the Amí
- Professional SAE Setup, Build, & Displays 1 disk. Copy this file
- from the SAE diskette to your Windows Setup, Build, & Displays 1
- diskette, then reinstall Windows so the updated file will be
- recognized. If you have any questions or problems performing
- this operation, call Microsoft Technical Support at
- (206)-454-2030.
-
- Before continuing with this guide, make sure you are familiar
- with:
-
- The "Getting Started" section in the User's Guide
-
- The "Networks" section in the Reference Manual
-
- Regardless of the network you are working with, make sure to
- read the following sections in this guide:
-
- The "Network Support in Amí Professional" section
-
- The "Network Installation Issues" section
-
- -----------------------------------
-
- Network Support in Amí Professional
-
- -----------------------------------
-
- Amí Professional has been designed to take advantage of the
- sharing capabilities offered by a Local Area Network. There are
- three features of particular interest:
-
- A. File Locking
-
- B. User Dictionaries
-
- C. Style Sheets
-
- A. File Locking:
-
- Amí Professional provides file locking to protect against the
- possibility of simultaneous data update attempts in a network
- environment. When a user opens a document, the original file is
- flagged READ-ONLY and can only be modified by the original user.
- Another user can open the file in READ-ONLY mode, but changes
- can only be made if the user saves them with a different file
- name. File locking provides a safe way of sharing documents
- across the network.
-
- If Amí professional is terminated abnormally, as in the case of
- a power failure, some files may be left in a read-only mode. You
- can change them back to read-write using Amí Professional's File
- Management function.
-
- B. User Dictionaries:
-
- Amí Professional allows each user to maintain his own user
- dictionary file(s). Each network user can choose between having
- a customized user dictionary file or sharing a user dictionary
- file with other users in the network. For more information on
- installing the user dictionary, refer to the "User Dictionary
- File" section elsewhere in this guide.
-
- C. Style Sheets:
-
- Amí Professional provides Style Sheets that can be personalized
- to each individual user's needs. Style Sheets can also be placed
- in a shared directory where users can access them but not modify
- them.
-
- ---------------------------
-
- Network Installation Issues
-
- ---------------------------
-
- The following issues must be addressed when installing Amí
- Professional on a Local Area Network:
-
- A. Minimum System Requirements
-
- B. File Security
-
- C. File Placement
-
- D. Hardware Configurations
-
- E. User Dictionary File
-
- F. TEMP Environment Variable
-
- G. Printing
-
- A. Minimum System Requirements:
-
- Amí Professional requires 3.5 MB of free disk space on the
- server to store its program files, style sheets and sample
- files. (Note: disk space requirements vary depending on the
- number of options installed. You will need approximately 4.3 MB
- if you install all options.) All workstations must have a
- minimum of an 80286 processor, 640K of RAM memory, and a
- Hercules, CGA, EGA or VGA graphics display. A mouse is highly
- recommended but is not required.
-
- B. File Security:
-
- File attributes and user rights may vary depending on your local
- area network operating system. Amí Professional can be installed
- in a directory with just READ/OPEN/SEARCH rights. The user,
- however, must have full rights to the directory containing his
- documents, style sheets and user dictionary files.
-
- C. File Placement:
-
- Amí Professional installs into its own directory, usually
- \AMIPRO, on the network server. However, each user should have a
- private directory to hold his personal WIN.INI file, style sheet
- files, user dictionary file(s), and documents. (Note: This
- private directory on the server will be referred to as a home
- directory.)
-
- When the installation is complete, the network Supervisor may
- decide to make the \AMIPRO directory READ ONLY. If this is done,
- all users will share the user dictionary, and the style sheet,
- macro, draw and sample document files automatically provided by
- Amí Professional during the installation. Only the Supervisor
- (or a user with sufficient rights to the \AMIPRO directory) will
- be able to edit these files. If users need to be able to make
- changes to these files, copy the files contained in the
- \AMIPRO\STYLES, \AMIPRO\DOCS, \AMIPRO\DRAW, and AMIPRO\MACROS
- directories into similar subdirectories within each user's home
- directory. For more information about the user dictionary, refer
- to the "User Dictionary File" section.
-
- D. Hardware Configurations:
-
- Depending on the hardware configurations of the workstations
- attached to the network, certain Windows files may need to be
- copied to a different location on the server, and appropriate
- CONFIG.SYS files may need to be copied to each workstation's
- bootup disk.
-
- Workstation hardware configurations vary in the following ways:
-
- * the type of computer
-
- * the type of graphics display adapter
-
- * the type of mouse
-
- * the amount of RAM Memory (Expanded/Extended)
-
- If all the workstations have the same hardware configuration,
- most of the Windows files can be shared by all the users.
- However, each user must have his own copy of the WIN.INI file
- (usually stored in his home directory), and the WIN.INI file
- located in the \WINDOWS or \AMIPRO directory must be removed.
-
- If the workstations have different hardware configurations,
- there must be a set of Windows program files for each
- configuration. You will need to install Windows (or SAE Windows)
- for each configuration. After each installation, you should copy
- the WIN*.* files located in the \WINDOWS or \AMIPRO directory to
- a different directory named for the particular configuration.
-
- For example, you are installing full Windows and Amí
- Professional, and all the workstations are identical except that
- some workstations have Hercules display adapters and some
- workstations have VGA display adapters. Install Windows twice.
- The first time, specify Hercules display. When the Windows
- installation is complete, copy the \WINDOWS\WIN*.* files to a
- directory called \WINMONO. Install Windows again, and specify
- VGA display. Then copy the new \WINDOWS\WIN*.* files to a
- directory called \WINVGA. Now delete the \WINDOWS\WIN*.* files.
- The other Windows files must remain in the \WINDOWS directory.
-
- If any workstations have extended or expanded memory, you should
- install Windows from one of those stations and specify that
- additional memory during the installation. Windows will update
- the workstation's CONFIG.SYS file with two lines:
-
- device=himem.sys
-
- device=smartdrv.sys NNN
-
- (where NNN is the number of kilobytes allocated for the disk
- cache)
-
- Copy this CONFIG.SYS file to the root directory of the drive or
- disk used to boot any workstation with additional memory. You
- may need to modify the NNN value to accommodate different memory
- configurations on the workstations.
-
- Note: Each workstation's CONFIG.SYS file should also contain, as
- a minimum, a files=20 statement.
-
- Remember: If you have workstations with varying display
- adapters, mice, and memory configurations, you will need to
- install for every possible combination and create separate
- directories to hold each set of WIN*.* files.
-
- E. User Dictionary File:
-
- Each user can have his own personal copy of a user dictionary
- file if a line specifying the path for that file (for example,
- userdictionary=m:\users\beverly) is added to the [AmiPro]
- section of his WIN.INI file. Amí Professional will automatically
- create the user dictionary file, VEAMAB51.LEX, in the directory
- specified in this path the first time the user dictionary file
- is accessed.
-
- Note: Do not modify the dictionary= line in the user's WIN.INI
- file. Amí Professional uses this information to find the main
- dictionary file.
-
- In order for the user to be able to add words and edit the user
- dictionary file, the directory specified for the user dictionary
- must exist and the user must have all rights to it.
-
- As an alternative, the network Supervisor may decide to maintain
- a shared user dictionary file in the \AMIPRO directory and grant
- READ ONLY rights to it. If this is done, all users will share
- the user dictionary but only the Supervisor (or a user with
- sufficient rights to the \AMIPRO directory) will be able to add
- words and edit the user dictionary file.
-
- F. TEMP Environment Variable:
-
- Amí Professional and Windows use temporary files to maintain
- information. These temporary files are created in the root
- directory of the current logged drive, where the user may not
- have rights to create and write files, unless a TEMP environment
- variable is specified in the user's AUTOEXEC.BAT file.
-
- For example, the following line typed in a user's AUTOEXEC.BAT
- file will cause the temporary files to be created and maintained
- in the C:\TEMPDIR directory.
-
- SET TEMP=C:\TEMPDIR
-
- Before running Amí Professional, SET the TEMP environment
- variable for each user to either a network drive or a local
- drive. Setting the TEMP environment variable to a local hard
- disk drive, if available, will improve speed by reducing network
- traffic. However, on Novell networks, setting the TEMP
- environment variable to a local drive may cause problems with
- saving files that contain imported graphics, drawings, or
- charts. If you experience problems saving files that contain
- the above items, set the TEMP environment variable to a network
- drive.
-
- The TEMP environment variable cannot be set to a removable media
- drive (a floppy disk drive or Bernoulli box). Each user must
- have full rights to the directory that will hold his TEMP files.
- Since each workstation maintains its own environment, the TEMP
- environment variable must be SET on each workstation running Amí
- Professional.
-
- G. Printing:
-
- Network printing is normally achieved by re-routing a local port
- to a network printer spooler. Make sure that you re-route or
- link the local port to the correct network spooler before
- running Amí Professional. Otherwise, the print job will be sent
- to the local printer port.
-
- Since most networks have their own spooling systems, you should
- disable the spooler provided by Windows by specifying spooler=no
- in each user's WIN.INI file. Having two spoolers may create
- conflicts and even slow down the printing process.
-
- -----------------------------------------------------------
-
- Installing Windows and Amí Professional on a Novell Network
-
- -----------------------------------------------------------
-
- This section is divided into four parts, each containing
- information about installing or printing.
-
- A. Installing Amí Professional if Microsoft Windows is already
- installed on a Novell Network
-
- B. Installing Microsoft Windows and Amí Professional on a
- Novell Network
-
- C. Installing Amí Professional with SAE Microsoft Windows on a
- Novell Network
-
- D. Printing on a Novell Network
-
- A. Installing Amí Professional if Microsoft Windows is already
- installed on a Novell Network:
-
- 1. Login as the network Supervisor.
-
- 2. Make sure there is a copy of the WIN.INI file in the \WINDOWS
- directory. During installation, Amí Professional will open the
- \WINDOWS\WIN.INI file and copy necessary information to an
- [AmiPro] section.
-
- 3. Insert the Amí Professional Program Disk 1 into the floppy
- disk drive you want to use for the installation. (Note: You will
- use only the disks labeled Program Disks.)
-
- 4. Make the floppy disk drive containing Program Disk 1 the
- current drive by typing the drive letter followed by a colon and
- pressing RETURN.
-
- 5. Type INSTALL and press RETURN.
-
- 6. Follow the instructions on the screen.
-
- Note: The installation program uses C:\WINDOWS as the default
- directory for Microsoft Windows. If Microsoft Windows is
- installed in a different directory (for example,
- F:\APPS\WINDOWS), make sure you specify the correct drive letter
- and directory name when asked to do so.
-
- 7. After Amí Professional has been installed, rename or delete
- the \WINDOWS\WIN.INI file, and add the [AmiPro] information
- contained in the \AMIPRO\AMINI.TXT file to each user's WIN.INI
- file. The first section of text should be copied into the AMIPRO
- section of the WIN.INI, and the second section should be copied
- into the AMIVISD section of the WIN.INI. If there is no AMIVISD
- section, one should be created.
-
- 8. If necessary, modify each user's login script so that it
- includes search paths to both the \WINDOWS directory and the
- directory containing his WIN.INI file (usually his home
- directory).
-
- 9. Make sure that all users have a minimum of READ, OPEN and
- SEARCH rights to the \AMIPRO and \WINDOWS directories. Users
- should also have all rights to their home directories. You can
- create a User Group to assign the trustee rights; consult
- Novell's Reference Manuals for information about creating User
- Groups.
-
- Notes:
-
- You can create an Amí Professional STYLES directory in each
- user's home directory and copy the style sheet files from the
- \AMIPRO\STYLES directory into it. This will provide customized
- style sheets for each user. Change the Style Sheet Path option
- under Edit/Defaults/Paths to the correct STYLES directory for
- each user.
-
- In order to provide each user with a personal copy of the user
- dictionary, the [AmiPro] section in his WIN.INI file must
- contain a line indicating the location of the user dictionary
- file (for example, userdictionary=m:\users\beverly), and the
- user must have all rights to the assigned directory. For more
- information on installing the user dictionary, refer to the
- "User Dictionary File" section found elsewhere in this guide.
-
- When the installation is complete, you should have the
- following new files and directories on the network:
-
- An \AMIPRO directory that contains all the Amí Professional
- files, including an \AMIPRO\STYLES directory with the Amí
- Professional style sheets and an \AMIPRO\DOCS directory with
- some sample documents, and AMIPRO\DRAW directory with the
- symbols files (clip art), and an \AMIPRO\MACROS directory with
- the macros.
-
- B. Installing Microsoft Windows and Amí Professional on a Novell
- Network:
-
- 1. Login as the network Supervisor and install Windows on the
- server following Microsoft's instructions.
-
- 2. Create a home directory on the server for each user who will
- be sharing Windows and Amí Professional.
-
- 3. If all the workstations attached to the Novell Network have
- the same hardware configuration (the same type of computer,
- display adapter, mouse, and memory configuration), most of the
- Windows files can be shared by all the users. However, each user
- must have his own copy of the WIN.INI file (usually stored in
- his home directory).
-
- 4. If the workstations attached to the Novell Network have
- different hardware configurations (different type of computer,
- display adapter, mouse, or memory configuration), there must be
- a full set of Windows program files for each configuration.
-
- Install Windows on the server for one type of hardware
- configuration.
-
- 5. Create a new directory on the server for the hardware
- configuration you just installed. For example,
-
- F:\WINMONO for stations with Hercules display adapters
-
- F:\WINVGA for stations with VGA display adapters
-
- 6. Copy the \WINDOWS\WIN*.* files to the hardware configuration
- directory. For example, if you installed Windows for stations
- with Hercules display adapters under F:\WINDOWS and you created
- a directory called F:\WINMONO for this hardware configuration,
- then you would use the following copy command:
-
- COPY F:\WINDOWS\WIN*.* F:\WINMONO
-
- The following files should be copied:
-
- WIN.COM
-
- WIN.INI
-
- WIN200.BIN
-
- WIN200.OVL
-
- WINOLDAP.GRB
-
- WINOLDAP.MOD
-
- These files contain all the necessary information for the
- particular hardware configuration you installed.
-
- 7. Repeat steps 4, 5, and 6 for each remaining hardware
- configuration. For each installation, specify the same network
- directory name for Windows.
-
- Note: If any workstations have extended or expanded memory, you
- should install Windows from one of those stations and specify
- that additional memory is available during the installation.
- Windows will update the workstation's config.sys file with two
- lines:
-
- device=himem.sys
-
- device=smartdrv.sys NNN
-
- (where NNN is the number of bytes allocated for the disk cache)
-
- Copy this config.sys file to the root directory of the drive or
- disk used to boot any workstation with additional memory. You
- may need to modify the NNN value to accommodate different memory
- configurations on the workstations.
-
- Note: Each workstation's config.sys file should also contain, as
- a minimum, a files=20 statement.
-
- Remember: If you have workstations with varying display
- adapters, mice, and memory configurations, you will need to
- install for every possible combination and create separate
- directories to hold each set of WIN*.* files.
-
- 8. Install Amí Professional as described in steps 2-6 of
- "Installing Amí Professional if Microsoft Windows is already
- installed on the network" in part A of this section.
-
- 9. For each user, copy the WIN.INI file that matches the user's
- hardware configuration from the appropriate hardware
- configuration directory to his home directory.
-
- 10. After Amí Professional has been installed, delete the
- \WINDOWS\WIN*.* files, and rename or remove the WIN.INI file in
- each of the hardware configuration directories. Add the
- information contained in the \AMIPRO\AMINI.TXT file to each
- user's WIN.INI file.
-
- 11. Modify each user's login script so that it includes search
- paths for these directories in this order:
-
- S1 - Search path to the \DOS directory
-
- S2 - Search path to the hardware configuration directory that
- contains the WIN*.* files for the station's configuration
-
- S3 - Search path to the \WINDOWS directory
-
- S4 - Search path to the user's home directory
-
- S5 - Search path to the \AMIPRO directory
-
- 12. Make sure that all users have a minimum of READ, OPEN and
- SEARCH rights to the \AMIPRO, \WINDOWS and hardware
- configuration directories. Users should also have full rights to
- their home directories. You can create a User Group to assign
- the trustee rights; consult Novell's Manuals for information
- about creating User Groups.
-
- Notes:
-
- You can create an Amí Professional STYLES directory in each
- user's home directory and copy the style sheet files from the
- \AMIPRO\STYLES directory into it. This will provide customized
- style sheets for each user. Change the Style Sheet Path option
- under Edit/Defaults/Paths to the correct STYLES directory for
- each user.
-
- In order to provide each user with a personal copy of the user
- dictionary, the [AmiPro] section in his WIN.INI file must
- contain a line indicating the location of the user dictionary
- file (for example, userdictionary=m:\users\beverly), and the
- user must have all rights to the assigned directory. For more
- information on installing the user dictionary, refer to the
- "User Dictionary File" section found elsewhere in this guide.
-
- When the installation is complete, you should have the
- following new files and directories on the network:
-
- A \WINDOWS directory that contains all the Windows files
- except the WIN*.* files
-
- An \AMIPRO directory that contains all the Amí Professional
- files, including an \AMIPRO\STYLES directory with the Amí
- Professional style sheets and an \AMIPRO\DOCS directory with
- some sample documents and macros.
-
- One hardware configuration directory for each type of
- installed hardware configuration. These directories should
- contain all the WIN*.* files except the WIN.INI file.
-
- A home directory for each user that contains a WIN.INI file.
- (A user dictionary file and a STYLES sub-directory in each
- user's home directory are optional.)
-
- C. Installing Amí Professional with SAE Microsoft Windows on a
- Novell Network:
-
- 1. Login as the network Supervisor and completely install SAE
- Windows and Amí Professional. To install SAE Windows and Amí
- Professional on the server, follow the instructions found in the
- Amí Professional User's Guide, "Installing Amí Professional with
- SAE Microsoft Windows."
-
- 2. Create a home directory on the server for each user who will
- be sharing Windows and Amí Professional.
-
- 3. If all the workstations attached to the Novell Network have
- the same hardware configuration (the same type of computer,
- display adapter, mouse, and memory configuration), most of the
- Windows files can be shared by all the users. However, each user
- must have his own copy of the WIN.INI file (usually stored in
- his home directory).
-
- 4. If the workstations attached to the Novell Network have
- different hardware configurations (different type of computer,
- display adapter, mouse, or memory configuration), there must be
- a full set of Windows program files for each configuration.
-
- Install SAE Windows on the server for one type of hardware
- configuration.
-
- 5. Create a new directory on the server for the hardware
- configuration you just installed. For example,
-
- F:\SAEMONO for stations with Hercules display adapters
-
- F:\SAEVGA for stations with VGA display adapters
-
- 6. Copy the \AMIPRO\WIN*.* files to the hardware configuration
- directory. For example, if you installed Amí Professional for
- stations with Hercules display adapters under F:\AMIPRO and you
- created a directory called F:\SAEMONO for this hardware
- configuration, then you would use the following copy command:
-
- COPY F:\AMIPRO\WIN*.* F:\SAEMONO
-
- The following files should be copied:
-
- WIN.INI
-
- WIN200.BIN
-
- WIN200.OVL
-
- These files contain all the necessary information for the
- particular hardware configuration you installed.
-
- 7. Repeat steps 4, 5 and 6 for each remaining hardware
- configuration. For each installation, specify the same network
- directory name for Amí Professional.
-
- Note: If any workstations have extended or expanded memory, you
- should install Windows from one of those stations and specify
- that additional memory is available during the installation.
- Windows will update the workstation's config.sys file with two
- lines:
-
- device=himem.sys
-
- device=smartdrv.sys NNN
-
- (where NNN is the number of bytes allocated for the disk cache)
-
- Copy this config.sys file to the root directory of the drive or
- disk used to boot any workstation with additional memory. You
- may need to modify the NNN value to accommodate different memory
- configurations on the workstations.
-
- Note: Each workstation's config.sys file should also contain, as
- a minimum, a files=20 statement.
-
- Remember: If you have workstations with varying display
- adapters, mice, and memory configurations, you will need to
- install for every possible combination and create separate
- directories to hold each set of WIN*.* files.
-
- 8. For each user, copy the WIN.INI file that matches the user's
- hardware configuration from the appropriate hardware
- configuration directory to his home directory.
-
- 9. Delete the \AMIPRO\WIN*.* files, and rename or remove the
- WIN.INI file in each of the hardware configuration directories.
- Add the information contained in the \AMIPRO\AMINI.TXT file to
- each user's WIN.INI file.
-
- For each user, copy the WINDOWS\WIN.INI file to the user's home
- directory.
-
- 10. Modify each user's login script so that it includes search
- paths for these directories in this order:
-
- S1 - Search path to the \DOS directory
-
- S2 - Search path to the hardware configuration directory that
- contains the WIN*.* files for the station's configuration
-
- S3 - Search path to the \AMIPRO directory
-
- S4 - Search path to the user's home directory
-
- 11. Make sure that all users have a minimum of READ, OPEN and
- SEARCH rights to the \AMIPRO and hardware configuration
- directories. Users should also have all rights to their home
- directories. You can create a User Group to assign the trustee
- rights; consult Novell's Reference Manuals for information about
- creating User Groups.
-
- Notes:
-
- You can create an Amí Professional \STYLES directory in each
- user's home directory and copy the style sheet files from the
- \AMIPRO\STYLES directory into it. This will provide customized
- style sheets for each user. Change the Style Sheet Path option
- under Edit/Defaults/Paths to the correct STYLES directory for
- each user.
-
- In order to provide each user with a personal copy of the user
- dictionary file, the [AmiPro] section in his WIN.INI file must
- contain a line indicating the location of the user dictionary
- file (for example, userdictionary=m:\users\beverly), and the
- user must have all rights to the assigned directory. For more
- information on installing the user dictionary, refer to the
- "User Dictionary File" section found elsewhere in this guide.
-
- When the installation is complete, you should have the
- following new files and directories on the network:
-
- An \AMIPRO directory that contains all the Amí Professional
- files, including an \AMIPRO\STYLES directory with the Amí
- Professional Style Sheets and an \AMIPRO\DOCS directory with
- some sample documents and macros.
-
- One hardware configuration directory for each type of
- installed hardware configuration. These directories should
- contain all the WIN*.* files except the WIN.INI file.
-
- A home directory for each user that contains a WIN.INI file.
- (A user dictionary file and a STYLES sub-directory in each
- user's home directory are optional.)
-
- D. Printing on a Novell Network:
-
- To be able to print to a Novell NetWare network printer, the
- NetWare spooler must be enabled prior to loading Windows or Amí
- Professional. For NetWare networks versions 2.0a and below, the
- spooler command is SPOOL; for NetWare networks versions 2.1 and
- above, the spooler command is CAPTURE. Examples of NetWare
- spooler commands where the printer spooler is 0, no banner page
- is desired (/nb), no form feed is performed (nff), no tab
- expansion is desired (nt), and a time out of 45 seconds is
- desired (ti=45) are:
-
- NetWare 2.0a or below:
-
- SPOOL p0 /nb/nff/nt/ti=45
-
- (re-routes local lpt1: to network p0 printer)
-
- NetWare 2.1 or above:
-
- CAPTURE p0 /nb/nff/nt/ti=45
-
- (re-routes local lpt1: to network p0 printer)
-
- These options may vary, but the most important parameter is the
- time out period (ti=). For most printing applications, a
- time-out of 45 seconds (/ti=45) should work fine. When printing
- to postscript printers, or printing documents with large graphic
- files, you may need to increase the time out period to 60
- seconds or more. Refer to your NetWare manual for more
- information about printing under Novell NetWare.
-
- ----------------------------------------------------------
-
- Installing Windows and Amí Professional on a 3COM Network
-
- ----------------------------------------------------------
-
- This section is divided into four parts, each containing
- information about installing or printing.
-
- A. Installing Microsoft Windows on a 3COM Network
-
- B. Installing Amí Professional on a 3COM Network
-
- C. Installing Amí Professional with SAE Microsoft Windows on a
- 3COM Network
-
- D. Printing on a 3COM Network
-
- A. Installing Microsoft Windows on a 3COM Network:
-
- 1. Login in as the 3COM Server User.
-
- 2. Using the 3F command, link to a Network Drive.
-
- 3F Link [Network Drive]: \\Samna\Apps1
-
- 3. Change the current drive to the [Network Drive].
-
- 4. Create a directory on the [Network Drive] called \WINDOWS.
-
- MKDIR [Network Drive]:\WINDOWS
-
- 5. Create a sub-directory under the WINDOWS directory called
- \PIF.
-
- MKDIR [Network Drive]:\WINDOWS\PIF
-
- Note: The Windows installation program may not automatically
- create the necessary sub-directories. Therefore, you must create
- the required directories in advance.
-
- 6. Install Windows on the server following Microsoft's
- instructions. When asked for the DRIVE and DIRECTORY where
- WINDOWS should be installed, type:
-
- [Network Drive]:\WINDOWS
-
- 7. Create a home directory on the server for each user who will
- be sharing Windows and Amí Professional.
-
- 8. If all the workstations attached to the 3COM Network have the
- same hardware configuration (the same type of computer, display
- adapter, mouse, and memory configuration), most of the Windows
- files can be shared by all the users. However, each user must
- have his own copy of the WIN.INI file (usually stored in his
- home directory).
-
- For each user, copy the [Network Drive]:\WINDOWS\WIN.INI file to
- the user's home directory. Skip to step 15.
-
- 9. If the workstations attached to the 3COM Network have
- different hardware configurations (different type of computer,
- display adapter, mouse, or memory configuration), there must be
- a full set of Windows program files for each configuration.
-
- Install Windows on the server for one type of hardware
- configuration, following the directions in step 6.
-
- 10. Create a new directory on the server for the hardware
- configuration you just installed. For example,
-
- MKDIR [Network Drive]:\WINVGA for stations with VGA display
- adapters
-
- 11. Copy the [Network Drive]:\WINDOWS\WIN*.* files to the
- hardware configuration directory. For example, if you installed
- Windows for stations with VGA display adapters and you created a
- directory called [Network Drive]:\WINVGA for this hardware
- configuration, you would use the following copy command:
-
- copy [Network Drive]:\WINDOWS\WIN*.* [Network Drive]:\WINVGA
-
- The following files should be copied:
-
- WIN.COM
-
- WIN.INI
-
- WIN200.BIN
-
- WIN200.OVL
-
- WINOLDAP.GRB
-
- WINOLDAP.MOD
-
- These files contain all the necessary information for the
- particular hardware configuration you installed.
-
- 12. Repeat steps 9, 10 and 11 for each remaining hardware
- configuration. For each installation, specify the same network
- directory name for Windows.
-
- Note: If any workstations have extended or expanded memory, you
- should install Windows from one of those stations and specify
- that additional memory is available during the installation.
- Windows will update the workstation's config.sys file with two
- lines:
-
- device=himem.sys
-
- device=smartdrv.sys NNN
-
- (where NNN is the number of bytes allocated for the disk cache)
-
- Copy this config.sys file to the root directory of the drive or
- disk used to boot any workstation with additional memory. You
- may need to modify the NNN value to accommodate different memory
- configurations on the workstations.
-
- Note: Each workstation's config.sys file should also contain, as
- a minimum, a files=20 statement.
-
- Remember: If you have workstations with varying display
- adapters, mice, and memory configurations, you will need to
- install for every possible combination and create separate
- directories to hold each set of WIN*.* files.
-
- 13. For each user, copy the WIN.INI file that matches the user's
- hardware configuration from the appropriate hardware
- configuration directory to his home directory.
-
- 14. Rename or remove the WIN.INI file in each of the hardware
- configuration directories.
-
- 15. Each workstation must have search paths for these
- directories:
-
- [Network Drive]:\WINDOWS
-
- the hardware configuration directory that contains the WIN*.*
- files for the station's configuration
-
- the user's home directory
-
- 16. Each workstation must have a minimum of READ, OPEN, and
- SEARCH rights to the [Network Drive]:\WINDOWS and hardware
- configuration directories. Users should also have full rights to
- their home directories.
-
- 17. Windows and Amí Professional use temporary files to maintain
- information. These temporary files are created in the root
- directory of the current drive, where the user may not have
- rights to create and write files, unless a TEMP environment
- variable is specified in the workstation's autoexec.bat file or
- in the user's logon batch file.
-
- To create a directory to maintain the temporary files, type:
-
- MKDIR [Network Drive]:\TEMPDIR
-
- Then type the following line in each workstation's autoexec.bat
- file or in each user's logon batch file to cause the temporary
- files to be created and maintained in the [Network
- Drive]:\TEMPDIR:
-
- SET TEMP=[Network Drive]:\TEMPDIR
-
- The TEMP environment variable cannot be set to a removable media
- drive (a floppy disk drive or Bernoulli box). Each user must
- have full rights to the directory that will hold his TEMP files.
- Since each workstation maintains its own environment, the TEMP
- environment variable must be SET on each workstation running Amí
- Professional.
-
- B. Installing Amí Professional on a 3COM Network:
-
- 1. Login in as the 3COM Server User.
-
- 2. Using the "3F" command, link to a Network Drive.
-
- 3F Link [Network Drive]: \\Samna\Apps1
-
- 3. Change the current drive to the [Network Drive].
-
- 4. Create a directory on the [Network Drive] called \AMIPRO.
-
- MKDIR [Network Drive]:\AMIPRO
-
- 5. Create a sub-directory under the AMIPRO directory called
- \STYLES.
-
- MKDIR [Network Drive]:\AMIPRO\STYLES
-
- 6. Create a sub-directory under the AMIPRO directory called
- \DOCS.
-
- MKDIR [Network Drive]:\AMIPRO\DOCS
-
- Note: The installation program may not automatically create the
- necessary sub-directories. Therefore, you must create the
- required directories in advance.
-
- 7. Make sure there is a copy of the WIN.INI file in the [Network
- Drive]:\WINDOWS directory. During installation, Amí Professional
- will open the [Network Drive]:\WINDOWS\WIN.INI file and copy
- necessary information to an [AmiPro] section.
-
- 8. Insert the Amí Professional Program Disk 1 into the floppy
- disk drive you want to use for the installation.
-
- 9. Make the floppy disk drive containing Program Disk 1 the
- current drive by typing the drive letter followed by a colon and
- pressing RETURN.
-
- 10. Type INSTALL and press RETURN.
-
- 11. When asked for the DRIVE and DIRECTORY where Amí
- Professional should be installed, type:
-
- [Network Drive]:\AMIPRO
-
- When asked for the DRIVE and DIRECTORY where Windows is
- installed, type:
-
- [Network Drive]:\WINDOWS
-
- 12. Follow the instructions on the screen.
-
- 13. After Amí Professional has been installed, rename or delete
- the [Network Drive]:WINDOWS\WIN.INI file, and add the [AmiPro]
- information contained in the \AMIPRO\AMINI.TXT file to each
- user's WIN.INI file.
-
- 14. Make sure that all users have a minimum of READ, OPEN and
- SEARCH rights to the [Network Drive]:\AMIPRO and [Network
- Drive]:\WINDOWS directories. Users should also have all rights
- to their home directories.
-
- Notes:
-
- You can create an Amí Professional STYLES directory in each
- user's home directory and copy the style sheet files from the
- [Network Drive]:\AMIPRO\STYLES directory into it. This will
- provide customized style sheets for each user. Change the Style
- Sheet Path option under Edit/Defaults/Paths to the correct
- STYLES directory for each user.
-
- In order to provide each user with a personal copy of the user
- dictionary, the [AmiPro] section in his WIN.INI file must
- contain a line indicating the location of the user dictionary
- file (for example, userdictionary=m:\users\beverly), and the
- user must have all rights to the assigned directory. For more
- information on installing the user dictionary, refer to the
- "User Dictionary File" section found elsewhere in this guide.
-
- When the installation is complete, you should have the
- following new files and directories on the network:
-
- A [Network Drive]:\AMIPRO directory that contains all the Amí
- Professional files, including a [Network Drive]:\AMIPRO\STYLES
- directory with the Amí Professional style sheets and a [Network
- Drive]:\AMIPRO\DOCS directory with some sample documents, a
- [Network Drive]:\AMIPRO\DRAW directory with symbols files (clip
- art), and a [Network Drive]:\AMIPRO\MACROS directory with
- several macros.
-
- C. Installing Amí Professional with SAE Microsoft Windows on a
- 3COM Network:
-
- 1. Login in as the 3COM Server User.
-
- 2. Using the "3F" command, link to a Network Drive.
-
- 3F Link [Network Drive]: \\Samna\Apps1
-
- 3. Change the current drive to the [Network Drive].
-
- 4. Create a directory on the [Network Drive] called \AMIPRO.
-
- MKDIR [Network Drive]:\AMIPRO
-
- 5. Create a sub-directory under the AMIPRO directory called
- \STYLES.
-
- MKDIR [Network Drive]:\AMIPRO\STYLES
-
- 6. Create a sub-directory under the AMIPRO directory called
- \DOCS.
-
- MKDIR [Network Drive]:\AMIPRO\DOCS
-
- Note: The installation program may not automatically create the
- necessary sub-directories. Therefore, you must create the
- required directories in advance.
-
- 7. Install SAE Windows and Amí Professional on the server
- following the instructions found in the Amí Professional User's
- Guide, "Installing Amí Professional with SAE Microsoft Windows."
-
- When asked for the DRIVE and DIRECTORY where Amí Professional
- should be installed, type:
-
- [Network Drive]:\AMIPRO
-
- 8. Create a home directory on the server for each user who will
- be sharing Amí Professional.
-
- 9. If all the workstations attached to the 3COM network have the
- same hardware configuration (the same type of computer, display
- adapter, mouse, and memory configuration), most of the Windows
- files can be shared by all the users. However, each user must
- have his own copy of the WIN.INI file (usually stored in his
- home directory).
-
- For each user, copy the [Network Drive]:\AMIPRO\WIN.INI file to
- the user's home directory. Then rename or remove the [Network
- Drive]:\AMIPRO\WIN.INI file. Skip to step 16.
-
- 10. If the workstations attached to the 3COM Network have
- different hardware configurations (different type of computer,
- display adapter, mouse, or memory configuration), there must be
- a full set of Windows program files for each configuration.
-
- Install SAE Windows on the server for one type of hardware
- configuration, following the directions in step 7.
-
- 11. Create a new directory on the server for the hardware
- configuration you just installed. For example,
-
- MKDIR [Network Drive]:\SAEVGA for stations with VGA display
- adapters
-
- 12. Copy the [Network Drive]:\AMIPRO\WIN*.* files to the
- hardware configuration directory. For example, if you installed
- Windows for stations with VGA display adapters and you created a
- directory called [Network Drive]:\SAEVGA for this hardware
- configuration, you would use the following copy command:
-
- copy [Network Drive]:\AMIPRO\WIN*.* [Network Drive]:\SAEVGA
-
- The following files should be copied:
-
- WIN.INI
-
- WIN200.BIN
-
- WIN200.OVL
-
- These files contain all the necessary information for the
- particular hardware configuration you installed.
-
- 13. Repeat steps 10, 11 and 12 for each remaining hardware
- configuration. For each installation, specify the same network
- directory name for Windows.
-
- Note: If any workstations have extended or expanded memory, you
- should install Windows from one of those stations and specify
- that additional memory is available during the installation.
- Windows will update the workstation's config.sys file with two
- lines:
-
- device=himem.sys
-
- device=smartdrv.sys NNN
-
- (where NNN is the number of bytes allocated for the disk cache)
-
- Copy this config.sys file to the root directory of the drive or
- disk used to boot any workstation with additional memory. You
- may need to modify the NNN value to accommodate different memory
- configurations on the workstations.
-
- Note: Each workstation's config.sys file should also contain, as
- a minimum, a files=20 statement.
-
- Remember: If you have workstations with varying display
- adapters, mice, and memory configurations, you will need to
- install for every possible combination and create separate
- directories to hold each set of WIN*.* files.
-
- 14. For each user, copy the WIN.INI file that matches the user's
- hardware configuration from the appropriate hardware
- configuration directory to his home directory.
-
- 15. After Amí Professional has been installed, rename or delete
- the [Network Drive]:\AMIPRO\WIN*.* file, and the WIN.INI file in
- each of the hardware configuration directories. Add the [AmiPro]
- information contained in the \AMIPRO\AMINI.TXT file to each
- user's WIN.INI file.
-
- 16. Each workstation must have search paths for these
- directories:
-
- [Network Drive]:\AMIPRO
-
- the hardware configuration directory that contains the WIN*.*
- files for the station's configuration
-
- the user's home directory
-
- 17. Each workstation must have a minimum of READ, OPEN, and
- SEARCH rights to the [Network Drive]:\AMIPRO and hardware
- configuration directories. Users should also have full rights to
- their home directories.
-
- 18. Windows and Amí Professional use temporary files to maintain
- information. These temporary files are created in the root
- directory of the current drive, where the user may not have
- rights to create and write files, unless a TEMP environment
- variable is specified in the workstation's autoexec.bat file or
- in the user's logon batch file.
-
- To create a directory to maintain the temporary files, type:
-
- MKDIR [Network Drive]:\TEMPDIR
-
- Then type the following line in each workstation's autoexec.bat
- file or in each user's logon batch file to cause the temporary
- files to be created and maintained in the [Network
- Drive]:\TEMPDIR:
-
- SET TEMP=[Network Drive]:\TEMPDIR
-
- The TEMP environment variable cannot be set to a removable media
- drive (a floppy disk drive or Bernoulli box). Each user must
- have full rights to the directory that will hold his TEMP files.
- Since each workstation maintains its own environment, the TEMP
- environment variable must be SET on each workstation running Amí
- Professional.
-
- Notes:
-
- You can create an Amí Professional STYLES directory in each
- user's home directory and copy the style sheet files from the
- [Network Drive]:\AMIPRO\STYLES directory into it. This will
- provide customized style sheets for each user. Change the Style
- Sheet Path option under Edit/Defaults/Paths to the correct
- STYLES directory for each user.
-
- In order to provide each user with a personal copy of the user
- dictionary, the [AmiPro] section in his WIN.INI file must
- contain a line indicating the location of the user dictionary
- file (for example, userdictionary=m:\users\beverly), and the
- user must have all rights to the assigned directory. For more
- information on installing the user dictionary, refer to the
- "User Dictionary File" section found elsewhere in this guide.
-
- When the installation is complete, you should have the
- following new files and directories on the network:
-
- A [Network Drive]:\AMIPRO directory that contains all the Amí
- Professional files, including a [Network Drive]:\AMIPRO\STYLES
- directory with the Amí Professional style sheets and a [Network
- Drive]:\AMIPRO\DOCS directory with some sample documents and
- macros.
-
- One hardware configuration directory for each type of
- installed hardware configuration. These directories should
- contain all the WIN*.* files except the WIN.INI file.
-
- A home directory for each user that contains a WIN.INI file.
- (A user dictionary file and a STYLES sub-directory in each
- user's home directory are optional.)
-
- D. Printing on a 3COM Network:
-
- 1. Login as the 3COM Server User.
-
- 2. To make a network printer available to the users, the printer
- must be shared using the 3P SHARE command:
-
- 3P SHARE [ShareName]=[PhysicalPort]
-
- (where [ShareName] is the name you want to assign to the network
- printer and [PhysicalPort] is the port on the server where the
- printer is connected, for example, lpt1, com1, etc.)
-
- Consult the 3COM PC Server Manual for information about Printer
- Sharing.
-
- 3. Once the server port is shared and the printer has been
- assigned a ShareName, users can re-route their workstation's
- local port to the network printer by linking to the ShareName.
-
- 3P LINK [ShareName] [PortName]
-
- (where [ShareName] is the name assigned to the network printer
- and [PortName] is a physical port on the workstation, for
- example, lpt1, com1, etc.)
-
- Note: If the workstation has a local printer, make sure that the
- [PortName] linked to the network printer is different than the
- one used for the local printer. Consult the 3COM PC Server
- Manual for information about Printer Sharing.
-
- Note: Print jobs sent to a port that has been linked to a
- network printer assigned a ShareName will print on the network
- printer even if a local printer is connected to that port.
-
-