Welcome. to the MAS 90 for Windows Online Installation Guide. How to Use This Guide. Contents. Index. Modules

Transcription

1 Welcome to the MA 90 for Windows Online Installation Guide How to Use his Guide Contents Index Modules

2 How to Use his Guide Go to the How to Use his Guide page (this page). EN Go to the Contents. Go to the previous page. Go to the next page. Go back to the previous link. Go to the Index....ext on page... Go to the Modules page. Indicates a jump to a topic. Bookmarks appear in the overview window to the left of the document window when the View Bookmarks and Page option is selected from the View menu in Acrobat Reader. hese bookmarks are similar to a table of contents. For information about MA 90, refer to About MA 90 on page 3. Note: he MA 90 Installation Guides and User Manuals CD-ROM is best viewed using Acrobat Reader 4.0, which can be installed from the CD-ROM. For best printing results, print to a Postcript printer.

3 About MA 90 Information in this document is furnished only under a Customer License Agreement or non-disclosure agreement, and may be used or copied only in accordance with the terms of such agreement. he software described in this document is protected by copyright, and may not be copied on any medium except as specifically authorized in the license or non-disclosure agreement. his document is also protected by copyright, and may not be reproduced or transmitted, in whole or in part, by any means, including photocopying, facsimile transmission, or reduction to any electronic medium or machine readable form, without the express written consent of age oftware, Inc. Copyright 1999 age oftware, Inc. All rights reserved. MA 90, ClientCare, and the ClientCare logo are registered trademarks of age oftware, Inc. age is a trademark of age oftware, Inc. Other product names used in this document are trademarks or registered trademarks of their respective owners.

4 4 Chapter 1 Introduction 8 he age Ideal 8 How to Use his Manual 9 Graphic Conventions 10 Installing MA Installation and Conversion Checklist 11 Printer Configuration Checklist 15 Workstation etup Checklist 16 Contents Chapter 2 Getting tarted 17 Overview of ystem tartup 17 Installing in the Windows Environment 17 Installation of ystem etup 19 Installation Options 20 Agreeing to the erms of the License 21 electing a Destination Directory 22 etup Options 23 Confirmation and Installation 24 Installing Crystal Reports 25 Installing the Microsoft Web Publishing Wizard 27 etup Complete 28 CD-ROM Installation of Crystal Reports 29 CD-ROM Installation of Microsoft Data Access Pack 30 Workstation etup Program 32 Disk pace Requirements 32 Running the Workstation etup Program 33 MA 90 Workstation Identification and ession racking 36 Assigning a Workstation ID 36 Overriding the FID0 Value 37 tarting MA 90 for the First ime 39 MA 90 tartup 39 MA 90 for Windows Installation Guide

5 5 Chapter 3 Data Conversion 41 Conversion Overview 41 Conversion Flowchart 42 ystem File Conversion from MA 90 Level 1.x or 2.x 43 Unconverted Data Files from MA 90 Level 1.x or 2.x 45 FIG.BBX File Conversion 46 Converting the FIG.BBX/FIGW.BBX Files 46 Conditional Printers 47 ample Conversion 48 Application Data File Conversion 50 Converting Application Data Files 51 Input Fields 51 pecific Company 53 All Companies 53 Proceeding with the Conversion 54 Conversion Processing 54 Conversion Completion 55 Application Upgrade Conversion 55 Chapter 4 Installing Onto a ingle User ystem 56 Windows etup Procedures 56 Windows etup Procedures 57 Windows N 4.0 Workstation 57 ystem Requirements 57 Printer etup 58 Chapter 5 Installing Onto a Novell NetWare 3.12/3.20 Network 59 etup and Configuration 59 NetWare Rights 59 Configuring Captured Printers in Device Configurator 60 Configuring Local Printers in Device Configurator 61 Defining Local Printers for a Workstation 61 roubleshooting 62 Novell NetWare Networks 62 MA 90 for Windows Installation Guide

6 6 Checklists 63 Determining Hard Disk pace 63 Windows 95/98 Workstations 64 Chapter 6 Installing Onto a Novell NetWare 4 or 5 Network 66 etup and Configuration 66 Novell NetWare 4.1x 66 Novell NetWare Windows 95/98 Workstations 68 Chapter 7 Installing Onto a Windows N erver 4.0 Network 70 ystem Requirements 70 Minimum erver Configuration 70 Minimum Workstation Requirements 71 etup Procedures 72 Networking Procedures 72 Windows 95/98 72 etting Up Networking 73 Logging Onto a Domain 74 Printer etup 75 Printing Procedures 75 Drive Mappings 76 Checklists 76 Windows 95/98 Workstations (Workstation Checklist) 77 Windows N Workstation 4.0 (Workstation Checklist) 78 Chapter 8 Installing Onto a Windows 95/98 Peer-to-Peer Network 80 ystem Requirements 80 etup Procedures 80 Networking Procedures 80 Establishing Network Connections 81 MA 90 Workstation etup 82 Printing Procedures 83 Changing Printer ettings 84 Checklists 84 Windows 95/98 (erver Checklist) 85 Windows 95/98 (Workstation Checklist) 86 MA 90 for Windows Installation Guide

7 7 Chapter 9 Installing Onto a Windows N Workstation 4.0 Peer-to-Peer Network 87 ystem Requirements 87 Drive Mappings 88 Checklists 88 Windows N 4.0 Workstation (erver Checklist) 88 Windows N 4.0 Workstations (Workstation Checklist) 90 MA 90 for Windows Installation Guide

8 Introduction Chapter 1 he age Ideal Chapter 8 1 At age oftware, Inc., we make it our mission to provide market-leading accounting, distribution, and manufacturing software systems to small and mid-sized businesses. With customer satisfaction as a top priority, we are committed to providing reliable, highly evolved business applications today, as well as smooth, cost-effective upgrade paths to the new technologies and operating systems of tomorrow. EN As part of he age Group plc, we are the largest supplier of mainstream PC accounting software in the world. More than one million companies worldwide have already learned that the age name is synonymous with peace of mind. he knowledge that you can rely on your age software enables you to focus on your other vital business operations. We will continue with our commitment to you, and enhance our product offerings to meet the changing needs of business and industry now, and well into the next century. MA 90 for Windows Installation Guide

9 9 Chapter 1 Introduction How to Use his Manual his manual provides the information necessary for installing MA 90. his manual also contains information and troubleshooting tips on the configuration of the various operating systems and environments in which the MA 90 software is supported. It is designed to function as a self-teaching guide. he instructions contain detailed technical information on the configuration of operating systems and environments. Chapters 4 through 9 each represent a specific type of operating system platform onto which you might install the MA 90 software. Read Chapters 1 through 3 and the applicable chapter covering the platform on which you plan to install the MA 90 software thoroughly prior to beginning the installation process. EN For example, if you are installing MA 90 onto a Novell NetWare 4.11 erver, read the following chapters before you begin the installation. Chapter 1 Introduction Chapter 2 Getting tarted Chapter 3 Data Conversion Chapter 6 Installing Onto a Novell NetWare 4 or 5 Network MA 90 for Windows Installation Guide

10 10 Chapter 1 Introduction Graphic Conventions he following icons are used throughout this manual to flag different types of information. EN 5 2 : he Note icon is followed by a brief note with additional information about an option. he ip icon is followed by a brief tip that suggests a different method for applying a technique or procedure. he Warning icon is followed by a brief warning with important information to be aware of to avoid costly mistakes. Installing MA 90 Before beginning the installation, test and validate all the hardware and network configurations using this manual and the Operating ystem/platform Compatibility Matrix, which can be found on the age oftware Web site. Also review the current support library for any pertinent information, particularly the "Hot Pre-Installation Issues" page on the age oftware Web site. If you are upgrading from a previous level of MA 90 software (Level 1.x or 2.x), read Chapter 3, Data Conversion, to determine whether to perform an in-place or parallel upgrade. age oftware recommends that you perform a parallel upgrade. In the event that there is data corruption in the previous data files, performing a parallel upgrade makes it easier and safer to recover and repair the data. his also allows previous and new MA 90 programs to run simultaneously for verification. A good, verified backup of the system is still required for either upgrade method. MA 90 for Windows Installation Guide

11 11 Chapter 1 Introduction For specific support on your hardware or operating system, contact the vendor from whom you purchased that product. Use the following checklists for step-by-step instruction for all operating system configurations on which the MA 90 software is supported, to ensure that the network is configured properly prior to beginning the installation. For more information, refer to the applicable chapter representing the specific type of installation to be performed and Chapter 3, Data Conversion. EN For specific support on operating system commands such as UP, consult your operating system manuals or contact the vendor from whom you purchased that product. Installation and Conversion Checklist 1 Make sure that the CD-ROM is for the current levels for all the modules that you plan to install. For a listing of the current levels, refer to the age oftware Web site. 2 Make sure the packing list is available. he packing list contains serial number and unlocking key information that is required to activate the interpreter for the correct number of users and to register the modules. If you do not enter the unlocking key and perform system activation, you are only able to run in single-user mode. If you do not enter the unlocking keys for the modules, you are only able to access the module 40 times before you are locked out. 3 If you are upgrading from a previous level of MA 90 software (Level 1.x or 2.x), read Chapter 3, Data Conversion, to determine whether to perform an in-place or parallel upgrade. age oftware recommends that you perform a parallel upgrade. A parallel upgrade makes it easier and safer to recover and repair data, in the event of data corruption. An in-place upgrade is irreversible. Make sure a backup of the MA 90 system and data files is available should the need arise to retrieve this data. If you are upgrading from a previous level of MA 90 software (Level 3.x), an in-place upgrade must be performed. 4 Make sure that all data entry files have been updated and are empty prior to upgrading. Any data in the data entry files during the upgrade will be lost. Print all customized form definitions and the ystem Activity Log. Default forms may be erased in the upgrade process. MA 90 for Windows Installation Guide

12 12 Chapter 1 Introduction 5 If you are performing a parallel upgrade and you want to be able to access the prior version of MA 90, rename the MA90.BA file in the root directory of the drive to which MA 90 is being installed. Installing MA 90 overwrites the existing MA90.BA file. o run the previous version of MA 90 software, execute the renamed batch file. 6 Check permissions on the root directory of the drive to which you are installing. he MA 90 installation requires write access to the root directory so that it can write to the MA90.BA file. he root directory and the directory hierarchy where MA 90 is installed should have all available permissions set. he user installing MA 90 must have the highest-level user account for that particular operating system (for example, supervisor, admin., or root). EN Before installing MA 90, review the chapters pertaining to the operating system being installed. If you receive an Error 61 or Error 17 when starting the MA 90 system from the DO prompt, there is a possibility that the Level 2 MA90.BA file is being executed. 7 Install the software. MA 90 is installed using EUP.E if you are installing to a network. If you are installing ystem etup over a previous installation of MA 90, a dialog box appears indicating that a previous installation of MA 90 has been detected. Choose the O button only if you intend to perform an in-place upgrade. If you intend to perform a parallel upgrade, choose the Cancel button and enter a new path to which you want to install MA 90. A parallel upgrade can be used when upgrading from MA 90 Level 1.x or 2.x. 8 tart MA 90 by double-clicking the shortcut or program item. 9 If you install over an existing installation of MA 90 Level 1.x or 2.x, the in-place upgrade process begins. You are asked to confirm that a verified backup exists and you have the option to exit. After this process starts, it cannot be reversed. If you are upgrading from a previous version of Level 3, the ystem File Conversion process (Post Installation Merge) will begin automatically. You will not receive any prompts until the process is completed. MA 90 for Windows Installation Guide

13 13 Chapter 1 Introduction EN :Warning his is the only time that you are prompted to convert system files and start a parallel upgrade. Choose the Yes button on the dialog box to begin the conversion process. A parallel upgrade is only for MA 90 Level 1.x or 2.x data files. Printers are only converted if you chose to convert system files, or if you are performing an in-place upgrade. 10 If you did not install over an existing installation of MA 90 (parallel upgrade), when you start MA 90, a dialog box appears prompting you to convert system files. ystem files include the Forms file, List Mode Master files, ystem Control file, ecurity file, Report Master Definition file, Payroll ax able files, PostMaster Definition file, and the ime and Billing formats. All reports generated in Report Master, Import Master, and PostMaster in previous levels of MA 90 must be recompiled before they can be used. If you do not have a previous level of MA 90 (Level 1.x or 2.x) installed or do not want to convert system files from a previous level, choose the No button in the Do you want to convert MA 90 ystem files from another directory? dialog box. If there is an existing installation of MA 90 Level 1.x or 2.x software that needs to be converted, choose the Yes button. You will then be prompted for a directory from which to convert. Enter the path to the directory from which you want to convert. Include the drive letter and the full path, which should end with \MA After system files are converted, the post-installation merge begins. his process can take anywhere from a few minutes to an hour, based on the number of modules installed and the hardware configuration. If this is a new installation, you are ready to use MA 90 software and can proceed to Printer Configuration Checklist on page If upgrading from a prior level of MA 90 Level 1.x or 2.x, the FIG.BBX and/or FIGW.BBX files are converted. hese files contained printer and other device-related information associated with the device configurator; FIG.BBX contained the device configurator information for DO installations and FIGW.BBX contained the device configuration information for Windows installations of MA 90 Level 2.x. If either FIG.BBX or FIGW.BBX exists, it is converted to MA90.INI. If both files exist, the FIGW.BBX is converted to MA90.INI and FIG.BBX is converted to MA90D.INI. o retain and utilize the device configurator information that was in FIG.BBX, you must reenter the relevant information from MA90D.INI to MA90.INI using Library Master Device Configurator. MA 90 for Windows Installation Guide

14 14 Chapter 1 Introduction 13 If you are installing over a previous in-place version of MA 90 Level 1.x or 2.x, the program now begins converting module data files from the BB x format to the ProvideX format. If you performed a parallel upgrade of MA 90, refer to Application Data File Conversion on page 50. EN General Ledger must be converted first for each company. 14 If this is an upgrade from an existing installation that has company codes defined, select the first company code on the list. Access each module that has data files set up for this company. If the file format of any files for that module has changed from the previous level, a prompt appears for a secondary file format conversion to Level 3.x format. his occurs in addition to the database conversion in step 12. Choose the Yes button to allow the conversion process to proceed. elect the next module and repeat the process. When you have selected all the modules for the company, change to the next company and repeat the process. 15 he data files are now set up and ready for processing. You are now able to access data files using the maintenance programs. Proceed to Printer Configuration Checklist on this page before attempting to process data. If you have Report Master, Import Master, PostMaster, or ime and Billing customized billing formats or List Mode Master files, proceed to the next step. You must press HIF to type a tilde (~). 16 Recompile your Report Master, Import Master, PostMaster, or ime and Billing customized billing formats by accessing the respective maintenance program. elect each report and recompile it by typing a tilde (~) at the maintenance menu. Repeat this process for each report. MA 90 for Windows Installation Guide

15 15 Chapter 1 Introduction Printer conversion only converts the LP device and any device starting with "P." Other devices are ignored. Printer Configuration Checklist Before you can print from MA 90, your printers must be properly configured, either in the Windows Print Manager or using Library Master Device Configurator. A DO printer refers to a printer that has been configured using Library Master Device Configurator, including devices with device names of LPx, *WEV*, and *WINPR*. A Windows printer refers to a printer that is configured through Windows Print Manager. If a previous version of MA 90 software was installed, all printers configured there are converted to DO printers in MA 90. For more information, refer to Device Configurator in your Library Master manual. 1 tart MA 90. elect Device Configurator from the Library Master Utilities menu. EN 2 During the conversion process (from MA 90 Level 1.x or 2.x), the FIGW.BBX and FIG.BBX files were converted to MA90.INI and MA90D.INI, respectively. If only the FIG.BBX file exists, it is converted to MA90.INI. Only the MA90.INI file is used by MA 90. Printers defined in FIGW.BBX but not in FIG.BBX, or vice-versa, must be re-created in Library Master Device Configurator after MA 90 starts. If there are more printers defined in FIG.BBX than in FIGW.BBX, rename the MA90D.INI file to MA90.INI. 3 In Library Master Device Configurator, bring up each printer listed. his creates the link file for this printer. For information on setting up additional printers, refer to your Library Master manual. Add any necessary printers that do not currently appear in the printer list. MA 90 for Windows Installation Guide

16 16 Chapter 1 Introduction Workstation etup Checklist Before any workstation other than the one from which you installed can run MA 90, the Workstation etup program, EUP.E, must be executed from each individual workstation. EN You must run WEUP from each workstation every time you install a new system setup. he workstation must be able to see the MA90 directory. Do not share this directory; instead, share the drive or parent directory above MA90. 1 On the individual workstations, run the EUP.E program. he EUP.E program is located in the F:\MA90\WEUP\ directory (where F: represents the drive on which MA 90 is installed). From Windows Explorer, select this directory and double-click the EUP.E program. 2 Make sure your computer name is unique. No other computer accessing MA 90 can have the same computer name. You do not need to set the PVXFID0 value in your AUOEC.BA file. MA 90 for Windows Installation Guide

17 Getting tarted Chapter 2 Overview of ystem tartup Chapter 17 2 Before you can install MA 90 ystem etup, Library Master, or any of the MA 90 modules, your hardware must be properly configured, and the appropriate operating system software must be fully installed and operational. In addition, you should also calculate the total disk storage requirements for each module to be installed. If you are installing over an existing installation of MA 90 EVOLUION/2, refer to Converting EVOLUION/2 Data Files in your Library Master manual for additional requirements and procedures. EN Installing in the Windows Environment MA 90 is a 32 bit application. Windows 3.1x workstations must be upgraded in order to run MA 90. For information on compatibility, refer to the Operating ystem/platform Compatibility Matrix on the age oftware Web site. he following installation procedures address the Windows N and Windows 95/98 environments. Windows N and Windows 95/98 workstations require an Intel Pentium or better class microprocessor running at 166 MHz or faster. Different operating systems require different minimum hardware requirements. MA 90 performs well on the base recommended hardware configurations specified for each operating system. For more information on the specific operating system requirements, refer to the applicable chapter in this guide. After you have verified the compatibility of your hardware and operating system software, you must verify the available hard disk storage space before proceeding with the installation process. o do this, calculate the total disk storage requirements for each module to be installed. his calculation ensures that your hard disk contains adequate space to accommodate your processing requirements. ystem etup and Library Master require approximately 25 Mb of hard disk space. Each module occupies approximately 10 to 15 Mb of hard disk space. MA 90 for Windows Installation Guide

18 18 Chapter 2 Getting tarted If you choose not to install Crystal Reports, you will not be able to create new reports or modify existing reports and forms. he installation and setup process consists of the following steps. 1 Install MA 90 ystem etup, Library Master, and any other MA 90 modules. For more information, refer to Installation of ystem etup on page Install Crystal Reports (this is optional). 3 tart MA 90 and enter today's date as the "accounting date." For more information, refer to ystem tartup in your Library Master manual. 4 et up your company. For more information, refer to Company etup in your Library Master manual. EN 5 et up the application files for your company. For more information, refer to Module etup in your Library Master manual. Be sure to read this and all module user manuals completely before setting up MA 90 software. Each module has an options setup window that allows you to customize MA 90 software for your specific needs. aking the time to understand all the options available before you install and set up your modules allows you to use your accounting software to its fullest potential. After completing these procedures, your system is ready for normal processing activities. hese routine activities are described in detail in the menu chapters of each MA 90 user manual. MA 90 for Windows Installation Guide

19 EN 19 Chapter 2 Getting tarted Installation of ystem etup o begin the installation process, start Windows; if you are installing MA 90 to a server, map a drive letter to that server. Close all other programs before beginning the installation process. Place the MA 90 CD-ROM in the CD-ROM drive of the workstation from which you are installing MA 90. If Autorun is enabled on the workstation, the MA 90 Autorun window appears; otherwise, select Run from the tart menu, and type D:\AUORUN.E, where D:\ is the CD-ROM drive. Choose the Install MA 90 button to begin the installation process. he MA 90 etup program can take a few seconds to launch. Follow the instructions on the window to proceed with the installation. MA 90 for Windows Installation Guide

20 20 Chapter 2 Getting tarted Installation Options here are six options available on the Autorun window for installing MA 90 components. Install MA 90: Choose this option to install the MA 90 etup program. his option is required. Read MA 90 Release Notes: Choose this option to read the release notes for MA 90. EN For information on installing the MA 90 Web Engine, refer to your internet.acess Installation Guide. Install MA 90 Web Engine: Choose this option to install the MA 90 Web Engine. his option requires the internet.access module and Windows N 4.0 with ervice Pack 5 or higher. Run Workstation etup: Choose this option to install the Workstation etup program to local workstations. his option is required for all workstations. Install Crystal Reports for MA 90: Choose this option to install Crystal Reports to the workstation or server. his option is optional. Install Microsoft Data Access it: Choose this option to install Microsoft's ODBC drivers. his option is optional. MA 90 for Windows Installation Guide

21 EN 21 Chapter 2 Getting tarted Agreeing to the erms of the License After choosing the Install MA 90 button to begin the installation process, the following dialog box appears. Choose the Yes button to accept the terms of the license agreement. You must accept the agreement to continue with the installation. Choose the No button to stop the installation process. MA 90 for Windows Installation Guide

22 EN 22 Chapter 2 Getting tarted electing a Destination Directory he MA 90 etup program first requires you to specify where to install MA 90. Do not nest a destination directory in directories named MA90 or OA. Do not use WIN in any part of a destination directory name. he destination directory cannot include subdirectories with long file names. When the MA 90 etup program is ready for the destination directory, a dialog box similar to the following appears. Choose the Browse button to view a listing of all drives and directories available on the server. You are prompted to create the path if the path you enter does not exist. Choose the Yes button to proceed or the No button to select a new path. MA 90 for Windows Installation Guide

23 EN 23 Chapter 2 Getting tarted etup Options he MA 90 etup program displays the following dialog box, which lists all the modules available on the CD-ROM. If you do not have enough disk space, a warning appears after you choose the Next button. :Warning Do not integrate your existing modules with nonregistered modules unless you plan to purchase those modules. elect the check box next to the modules you want to install. Choose the elect All button to select all the modules, including demonstration data. Choose the Clear All button to clear all the check boxes. Choose the Next button to proceed. You are able to install modules that you have not purchased; however, you are required to purchase and unlock these modules after 40 free accesses. MA 90 for Windows Installation Guide

24 EN 24 Chapter 2 Getting tarted Confirmation and Installation After all the parameters have been entered and options selected, the MA 90 etup program provides a summary of your responses and prompts you for confirmation before beginning the installation. Before files start copying to your system, the MA 90 etup program verifies that no other programs are running that may be using programs the MA 90 etup program will be installing. If you receive a message (after choosing the Next button in the Confirmation dialog box) stating that etup is unable to copy programs because they are currently in use, close all programs and select the Continue option, then choose the Next button. o exit the MA 90 etup program, select the Exit option and choose the Next button. MA 90 for Windows Installation Guide

25 EN 25 Chapter 2 Getting tarted Choose the Next button to begin the installation, or choose the Back button to change your options. he Installation program begins copying files and establishes a program group and icon in the tart menu to run MA 90. Installing Crystal Reports When the etup program finishes copying files and creating any necessary program groups or icons, you are asked whether to install either Crystal Reports or Crystal Reports Workstation files. It is only necessary to install Crystal Reports if you will be modifying graphical forms or creating new Crystal Reports forms. Crystal Reports is not required for viewing or printing graphical forms, or for using any other MA 90 features. MA 90 for Windows Installation Guide

26 EN 26 Chapter 2 Getting tarted Crystal Reports can be installed to the local workstation or to a network server. If you are installing to a server, select the Custom option on the Installation Options dialog box, then select Workstation etup on the Custom Installation Options dialog box. his will create the Client 32 subdirectory under the CRW directory. EUP.E can be run from this directory to run Crystal Reports Workstation etup. Choose either the Launch Crystal Reports setup program or the Launch Crystal Reports Workstation setup program option, and then choose the Next button. he appropriate setup program is launched. If you choose to launch the Crystal Reports Workstation etup program, you must indicate the path containing your LAN or shared installation of Crystal Reports. he Crystal Reports etup program installs a full version of Crystal Reports to the destination drive specified. he Crystal Reports Workstation etup program is used to install the Crystal Reports workstation components to the local workstation from a shared Crystal Reports installation. At the completion of the Crystal Reports or Crystal Reports Workstation installation (or if you chose not to install either), control returns to the MA 90 etup program. You are prompted whether to copy the Crystal Reports setup files to a place on your network. his enables other users to install Crystal Reports from the network. If you choose the Yes button, the etup program copies the setup files to the following directory. MA90\WEUP\DAA\CRWOA MA 90 for Windows Installation Guide

27 27 Chapter 2 Getting tarted Installing the Microsoft Web Publishing Wizard If you choose to install the internet.access module, the etup program displays the following dialog box. EN he Microsoft Web Publishing Wizard is used when you choose Publish Files to Web from the internet.access etup menu. Only workstations that have installed the Microsoft Web Publishing Wizard will be able to successfully publish internet.access images to a Web site. he option to install the Microsoft Web Publishing Wizard is also provided at the end of the Workstation etup Installation process. o install the Microsoft Web Publishing Wizard, choose the Yes button. o skip installation of the Microsoft Web Publishing Wizard, choose the No button. For more information on publishing internet.access images to a Web site, refer to your internet.access manual. MA 90 for Windows Installation Guide

28 28 Chapter 2 Getting tarted :Warning etup installs ODBC if it does not already exist on your system. Make sure all components of ODBC are installed and configured properly. etup Complete When the etup Complete dialog box appears, you have the option of viewing a README file containing important information about MA 90. After you close the README file, if system files that MA 90 uses were in use during installation, the MA 90 etup program will display a dialog box similar to the following. EN :Warning You must restart Windows before restarting MA 90 or errors may occur. If this dialog box appears, you must restart your computer for MA 90 to function properly. You may want to choose the second option, "No, I will restart my computer later." to shut down all other programs yourself and then restart your computer. MA 90 for Windows Installation Guide

29 EN 29 Chapter 2 Getting tarted CD-ROM Installation of Crystal Reports Crystal Reports can be installed from the CD-ROM without performing the MA 90 installation. Place the MA 90 CD-ROM in the CD-ROM drive of the workstation from which you are installing. If Autorun is enabled on the workstation, the MA 90 Autorun window appears; otherwise, select Run from the tart menu, and type D:\AUORUN.E, where D:\ is the CD-ROM drive. Choose the Install Crystal Reports for MA 90 button on the MA 90 Autorun window to begin the installation. It takes the Crystal Reports etup program a few seconds to launch. After choosing the Next button in the Welcome dialog box, the following dialog box appears. Choose the Crystal Reports etup, the Crystal Reports Workstation etup, or the Crystal Reports etup files button to begin the Crystal Reports setup appropriate for your reporting needs. For more information, refer to Installing Crystal Reports on page 25. MA 90 for Windows Installation Guide

30 30 Chapter 2 Getting tarted CD-ROM Installation of Microsoft Data Access Pack he Microsoft Data Access Pack (which is required to view or print MA 90 graphical forms) is usually installed with ystem etup or Workstation etup, but can be installed from the CD-ROM without performing the MA 90 installation. Place the MA 90 CD-ROM in the CD-ROM drive of the workstation from which you are installing. If Autorun is enabled on the workstation, the MA 90 Autorun window appears; otherwise, select Run from the tart menu, and type D:\AUORUN.E, where D:\ is the CD-ROM drive. Choose the Install Microsoft Data Access it button to begin the installation of the Microsoft Data Access Pack. EN he Data Access Pack may not be able to install programs that are open and possibly using some of the components that the Data Access Pack will overwrite. Close all external programs before running the Data Access Pack installation. When the Data Access Pack etup program starts, the following dialog box appears. his dialog box appears if you already have some components of the Data Access Pack installed. Choose the Add/Remove button, then choose the directory to which you will install the Data Access Pack. MA 90 for Windows Installation Guide

31 31 Chapter 2 Getting tarted If the Data Access Pack has never been installed, the following dialog box appears. EN Choose the Complete/Custom Install button. he following dialog box appears. elect the Data Access Drivers check box and choose the Continue button. he Data Access Pack copies files to your system. When complete, the Data Access Pack etup program informs you that it has successfully completed the installation and exits. MA 90 for Windows Installation Guide

32 32 Chapter 2 Getting tarted Workstation etup Program age oftware does not support running MA 90 through a shared network installation of Windows. he Workstation etup program is used specifically for Windows workstations attached to a Novell or Windows network. his program must be run in order to use MA 90 software on any workstation. he workstation from which the MA 90 software was originally installed does not need to run this utility. he Workstation etup program copies all the necessary Dynamic Link Libraries and programs to the WOW\YEM directory and also sets up the initialization files for this particular workstation. Disk pace Requirements EN he drive on which Windows is installed must have at least 2 Mb of free disk space available. If Custom Office is installed on the server, this drive will require an additional 10 Mb for system OCXs and DLLs. he drive on which the MA 90 software will be installed must have approximately 10 Mb of free disk space. If Crystal Reports is installed on the local workstation, the hard drive on which Crystal Reports is installed will require approximately 30 Mb. he hard drive on which Windows is installed will require approximately 10 Mb for system files. MA 90 for Windows Installation Guide

33 EN 33 Chapter 2 Getting tarted :Warning he Workstation etup program will not run properly if it is not executed from a drive letter. A physical drive letter does not exist if you run the Workstation etup program through Network Neighborhood in Windows 95/98. Running the Workstation etup Program he Workstation etup program can be run from the CD-ROM or from an installation of MA 90. Close all other programs before beginning the installation process. o begin the installation process from the CD-ROM, map a drive letter to the server on which MA 90 is installed. Place the MA 90 CD-ROM in the CD-ROM drive of your workstation. Run the Workstation etup program after every software upgrade. If Autorun is enabled on the workstation, the MA 90 Autorun window appears; otherwise, select Run from the tart menu, and type D:\AUORUN.E, where D:\ is the CD-ROM drive. Choose the Run Workstation etup button to begin the installation. It takes the Workstation etup program a few seconds to launch. MA 90 for Windows Installation Guide

34 EN 34 Chapter 2 Getting tarted o run Workstation etup from your installation of MA 90, use Windows File Manager or Explorer to attach to the drive on which the MA 90 software is installed and select the MA90\WEUP directory. Double-click the EUP.E file to run the Workstation etup program. It takes the Workstation etup program a few seconds to launch. After choosing the Next button, if you are running Workstation etup from the CD-ROM, the following dialog box appears, which allows you to enter the path to your MA 90 installation (this path is used only to create the MA 90 icon, not for copying files from the MA 90 installation). MA 90 for Windows Installation Guide

35 35 Chapter 2 Getting tarted he following Confirmation dialog box appears. EN :Warning etup installs ODBC if it does not already exist on your system. Make sure all components of ODBC are installed and configured properly. Choose the Next button to begin the installation. After the Workstation etup program has copied the necessary files to your workstation and has created a program group and icon in the tart menu to run MA 90, you are given the option to install either Crystal Reports or Crystal Reports Workstation files. For more information, refer to Installing Crystal Reports on page 25. At the completion of the Crystal Reports or Crystal Reports Workstation installation (or if you chose not to install either), control returns to the MA 90 etup program. If etup detects the internet.access module in the path to your MA 90 installation, you will now be given the opportunity to install the Microsoft Web Publishing Wizard. For more information, refer to Installing the Microsoft Web Publishing Wizard on page 27. MA 90 for Windows Installation Guide

36 36 Chapter 2 Getting tarted MA 90 Workstation Identification and ession racking Every MA 90 session initiated requires a unique identifier (created by setting the PVXFID0 environment variable) distinguishing each session from every other session running on the server. Additionally, the MA 90 Launcher launches a separate session of MA 90 for each module executed. When MA 90 Level 3 and MA 90 for Windows were first introduced, a new session tracking algorithm was developed to allow significantly more users and more sessions per user by compressing the FID(0) value without major changes to the data structure itself. A base PVXFID0 value for each individual workstation was still required but session tracking was handled by MA 90. Assigning a Workstation ID EN MA 90 sets the workstation ID automatically, when possible, by using the machine name of the workstation. If a machine name is not available, MA 90 requires a PVXFID0 value to be set in the environment. It is very important that all workstations have unique computer names. Most networks force users to have unique machine names; however, some older systems may allow duplicates. he following algorithm is used to assign a PVXFID0 value (in the order shown below). he FID0MAP.INI file is located in the MA90\HOME directory. If the workstation's computer name is located in this file, the value associated with this machine is used as the PVXFID0. MA 90 for Windows Installation Guide

37 37 Chapter 2 Getting tarted If the user's machine is not located in this file and if an existing PVXFID0 value is found in the environment, the existing PVXFID0 is written into the FID0MAP.INI file and is used in the future when MA 90 is started up if the PVXFID0 value is not already assigned to another machine. If the PVXFID0 is already assigned, MA 90 automatically assigns the next highest PVXFID0 value to this workstation. Note that 0 is a reserved PVXFID0 value. If 0 is set in the environment, a different PVXFID0 value is assigned to this workstation. If the value is not located in this file and a PVXFID0 value is not found in the environment, MA 90 assigns the next highest PVXFID0 value, starting with 101, automatically. Note that PVXFID0 values cannot exceed 400. EN If a machine name cannot be determined by MA 90 (in the case of some environments), the PVXFID0 value in the user's environment is used. If the PVXFID0 value is not found, MA 90 will not be able to start. Users can modify the FID0MAP.INI file to customize their PVXFID0 values for their machine. Note that if the user's machine name changes, their PVXFID0 value changes as well. he automatic assignment of PVXFID0 values starts at 101; values from 0 to 100 are reserved for users who have to assign their PVXFID0 values manually. Overriding the FID0 Value In some cases, it may be necessary to override the FID0 value assigned by MA 90. o override the FID0 value, assign an environment variable called MA90FID that has a value between 0 and 99. his is the FID0 value that will be used by MA 90 when the user accesses the system. Assigning a value above 99 will be ignored and the FID assignment from the MA 90 program will take precedence. When overriding the FID0 value, make sure that there are no duplications of FID0 values between different users. MA 90 for Windows Installation Guide

38 38 Chapter 2 Getting tarted If you are unfamiliar with DO batch files, consult your system administrator before editing this file. o add an environment variable in the Windows operating system, edit the AUOEC.BA file using Notepad or any other nonformatting text editor. Add the following command line to the AUOEC.BA file. E MA90FID=xx In this command line, xx represents a numerical value between 0 and 99. ave the file. You must restart Windows before the changes will take affect. o add an environment variable in the Windows N operating system: 1 Right-click the My Computer icon and select Properties. EN 2 elect the Environment tab on the ystem Properties window and add MA90FID as a new user variable with a value of xx (where xx represents a numerical value between 0 and 99). 3 Choose the et button to apply the changes; you do not need to restart Windows N. 4 Choose the O button to exit the ystem Properties window. MA 90 for Windows Installation Guide

39 39 Chapter 2 Getting tarted tarting MA 90 for the First ime After ystem etup, Library Master, and all MA 90 modules have been installed, you are ready to start the MA 90 software. If you have installed MA 90, a program group is created (or a tart menu item under the Programs submenu is added). Double-click the MA 90 for Windows icon in this program group to start MA 90. MA 90 tartup EN :Warning his is the only time you are given this option. ystem files include ecurity, Customized Forms, and Report Master reports. For more information, refer to the Converting EVOLUION/2 Data Files Appendix in your Library Master manual. If you installed MA 90 to a new directory, the following dialog box appears. ystem data files include the Forms file, List Mode Master files, ystem Control file, ecurity file, Report Master Definition file, Data Import Definition file, Payroll ax able files, PostMaster Definition file, and the ime and Billing billing formats. If you are a first-time user of MA 90 software, choose the No button to begin the final phase of the installation. If you have MA 90 EVOLUION/2 installed on your system and you want to convert your data files from this directory, choose the Yes button. You are then prompted for the location of the MA 90 EVOLUION/2 files. After the system files are converted, the system begins merging the installation files with your system files. his process can take anywhere from a few minutes to an hour, depending on the number of modules and the speed of the machine on which you are installing. For more information on setting up your MA 90 accounting software, refer to your Library Master manual. MA 90 for Windows Installation Guide

40 EN 40 Chapter 2 Getting tarted If you performed a system level conversion, either by installing over an existing MA 90 EVOLUION/2 installation, or by choosing the Yes button on the Data Conversion dialog box, the system begins the data conversion routine. For more information, refer to the Converting EVOLUION/2 Data Files Appendix in your Library Master manual. MA 90 for Windows Installation Guide

41 Chapter 3 Data Conversion Chapter 3 he data conversion process is divided into a number of small sections, each covering one specific area of conversion. his chapter discusses all four phases of the conversion process. Understanding the various phases of conversion is important in pinpointing any specific problems that may occur during this process. Conversion Overview ystem File Conversion FIG.BBX File Conversion Application Data File Conversion Application Upgrade Conversion 41 EN Database file conversion is a two-phase process, depending on how MA 90 is installed on a system. If MA 90 is installed directly over MA 90 Level 1.x or 2.x (commonly referred to as an in-place upgrade), the conversion program runs automatically when MA 90 is first started. he only interaction with the user is to confirm that data conversion should take place. If you are upgrading from a previous version of Level 3, the ystem File Conversion process (Post Installation Merge) will begin automatically. You will not receive any prompts until the process is completed. If MA 90 is installed to a separate location (parallel upgrade), the MA90 program detects, on startup, that no system files exist for this system and prompts the user to convert system and application data files from another location. A parallel upgrade can be used when upgrading from MA 90 Level 1.x or 2.x. After MA 90 has started, the user does not have the option to convert system files again unless system files in the OA directory are deleted and Library Master is reinstalled. In addition, after MA 90 has started, it is not possible to run certain phases of the system-level conversion process again because the configuration files are modified for the new level. MA 90 for Windows Installation Guide

42 42 Chapter 3 Data Conversion Conversion Flowchart he following flowchart is a graphical representation of the conversion process discussed in detail in the following sections. tart Parallel Upgrade Is Y0CL a BBx file? No Installation Files? No Yes Yes EN In-Place Upgrade Copy FIG.BBX and FIGW.BBX Convert ystem Files Yes No Create Conversion emporary Directories pecify Path for Conversion Finish (tart MA 90) tart Application Data Conversion (UPCV1) et Parallel Installation Flag Run FIG.BBX Conversion (YPCV3) Copy ystem Files to be Converted Y0CL.OA Y0EC.OA RM0RP.OA DI0RP.OA Run Post-installaion Merge (INALL.LIB) Payroll ax ables Convert Files and Copy to Destination Y0FRM.OA Y0LM1, Y0LM2 Y0LM3, Y0LMB ime & Billing Billing Formats PostMaster Configuration Files Create New RM0L.OA and DI0L.DOA Extract Y0CL Records to be Retained Parallel Upgrade? No Delete Existing Y0*.OA Files Delete RM0L.OA and DI0L.OA Yes MA 90 for Windows Installation Guide

43 43 Chapter 3 Data Conversion ystem File Conversion from MA 90 Level 1.x or 2.x When starting MA 90 for the first time, the MA90 program runs the system file conversion program to convert system files. If you are upgrading from MA 90 Level 1.x or 2.x, only the following system files are converted. Y0CL.OA: Only the company and alternate directory records are converted. erminal control records and other data are not converted. Y0EC.OA: If the previous version of MA 90 has had menus modified, verify the security file because some menu items may have shifted. he security file does not need to be re-created for MA 90. Y0FRM.OA: he customized forms codes are retained. EN 2ip Report Master, Import Master, and PostMaster report definitions are maintained but must be recompiled. No reports will appear in the Print election routine until these reports are regenerated, even if the original.rm,.di, or.pm file is still in the corresponding directory. Y0LM1.OA, Y0LM2.OA, Y0LM3.OA, and Y0LMB.OA: he four main List Mode Master files are retained and converted. RM0RP.OA: he Report Master Maintenance file is retained and converted. Files must be created on this system to be converted. he *.RM files copied from another system are not converted and cannot be recompiled. DI0RP.OA: he Import Master Maintenance file is retained and converted. Files must be created on this system to be converted. he *.DI files copied from another system are not converted and cannot be recompiled. PM0RP.OA, PM0L.OA, PM0MDE.OA, PM0VAL.OA, and PM0CFG.OA: he PostMaster configuration files are retained and converted. All reports must be recompiled before use. PRU.OA, PRV.OA, PRW.OA, PRX.OA, and PR_09.OA: Payroll ax ables are converted so that customized changes in tax tables do not have to be reentered. ax able conversion occurs before the installation routines run; therefore, if you have installed new ax ables and have not flagged your existing modified ax ables not to update, the converted ax ables are subsequently modified with the new ax able Update information. MA 90 for Windows Installation Guide

44 44 Chapter 3 Data Conversion B6.OA and BU.OA: he ime and Billing billing formats are converted from a previous installation of ime and Billing. he billing formats must be recompiled before they can be used. After these system files are converted, the normal post-installation merge process takes place. his process regenerates the menu system for the Launcher. he post-installation merge also regenerates all other system data files normally created during installation. All other files in the OA directory with a.oa extension are removed if performing an in-place upgrade. his prevents users from receiving errors when starting MA 90 with BB x data files still in the OA directory. hese remaining files are re-created and repopulated by the post-installation merge process. EN When the post-installation merge completes, the configuration conversion program (YPCV3) is run, converting the FIG.BBX or FIGW.BBX files into the MA90.INI file. For more information, refer to FIG.BBX File Conversion on page 46. he FIG.BBX file is no longer required for basic operation. MA 90 for Windows Installation Guide

45 45 Chapter 3 Data Conversion Unconverted Data Files from MA 90 Level 1.x or 2.x he following data files or portions of data files are not converted during the system-level conversion process. Many of these files are re-created during the installation process. o limit the amount of data being converted at a system level (and to reduce the potential exposure to error), these files are re-created instead of being converted. Most of these files should be modified only by experienced users by editing the file directly, or by Master Developers using the Master Developer Utilities programs. Y0BAR.OA: he Bar Code masterfile is re-created on installation. EN Y0DC.OA: he Data Dictionary is not converted. his large file is re-created as each module is installed; however, neither run-time nor linked fields created in either Report Master or Import Master (Level 2) nor any manual data dictionary changes made by Master Developers are retained. Y0DEF.OA: he Deferred Print file is cleared, along with all deferred print reports remaining in the MA90\HOME directory. Level 1 and 2 deferred print files are not compatible with Level 3 deferred print files. Y0EOP.OA: he End of Period file is not converted and is re-created with each new module. If end-of-period customization was designed by a Master Developer, these changes must be reimplemented. Y0ERR.OA: he Error Log is not converted. his file is reinitialized during the initial startup routine and only records events from the time MA 90 was installed. Y0FIL.OA: he File/Record Format information is re-created from "scratch" during installation. Master Developer modified programs that changed the data structure must be converted and reinstalled on the system. Y0MNU.OA: he OA Menu ystem file is not converted. It is re-created during the installation process as all new modules are installed. Customized menu changes must be added again, if desired. Report Master reports added to the menu must be recompiled before running in MA 90. MA 90 for Windows Installation Guide

46 46 Chapter 3 Data Conversion Y01.OA and Y02.OA: ask menus have been enhanced in MA 90, rendering the existing task menus incompatible with new task menu file structures. FIG.BBX File Conversion During MA 90 conversion, prior to the Application Data File Conversion, the FIG.BBX file is converted to MA90.INI. Extraneous lines are removed and other changes are made to prepare the MA90.INI as the source file for both the revised device configurator and the character-based printer selection. EN After installing ystem etup, if an MA90.INI file does not exist, the MA90.MP file is renamed MA90.INI. he MA90.MP file can be found in the..\home directory. Converting the FIG.BBX/FIGW.BBX Files he FIG.BBX file conversion converts both FIG.BBX and FIGW.BBX files, if they exist. If either the FIG.BBX or FIGW.BBX file exists, it is converted to MA90.INI. If both files exist, the FIGW.BBX file is converted to MA90.INI and the FIG.BBX file is converted to MA90D.INI. he contents of the two files cannot be merged. If there is information in one file, but not in the other, the missing information must be added back using Library Master Device Configurator after MA 90 finishes the conversion process. If there are more DO printers set up in the FIG.BBX than the FIGW.BBX, rename the MA90D.INI file to MA90.INI. MA 90 for Windows Installation Guide

47 47 Chapter 3 Data Conversion Conditional Printers Local printers defined within an "IF xx ENDIF" clause in the FIG.BBX file are stored in unique configuration files, based on the workstation ID. For example, printer information conditional to workstation 222 is stored in MA90222.INI. During conversion, workstation identifiers used with conditional printers are assigned new FID values in cardinal order automatically, beginning at "101." As each "IF xx" clause is processed, the conversion program assigns the next available FID and uses this number for naming the respective "MA90xxx.INI" file. he mappings between the original workstation identifiers and the new number are written to the "..\HOME\CNVLOG.X" file. EN For example, assuming the following three conditional printer definitions exist in FIG.BBX, they are assigned the new FID values shown below. Before 9 A1 24 After MA 90 for Windows Installation Guide

48 48 Chapter 3 Data Conversion ample Conversion he following FIG.BBX file was converted into the MA90.INI file shown on page 49. FIG.BBX fcbs=128 cibs=128 aliases=49 stblen=4096 EN prefix../oa/../home/ novell_locks alias LP LP1 "HP Laser eries III" cp= 1B E363648,cpcols=133,cr,ff=1B266C3048,ptoff= 1B45,pton=1B266C32411B266C F C B C,sp=1B266B3053,spcols=80 alias PD1 "../HOME/PD1.X" "Deferred Print File",cpcols=255,lock=../HOME/PD1.LC,spcols=255 alias PD2 "../HOME/PD2.X" "Deferred Print File" cpcols=255,lock=../home/pd2.lc,spcols=255 alias PD3 "../HOME/PD3.X" "Deferred Print File" cpcols=255,lock=../home/pd3.lc,spcols=255 alias PF1 "../HOME/PF1.X" "Print File 1" cpcols=255,lock=../home/pf1.lc,spcols=255 MA 90 for Windows Installation Guide

49 49 Chapter 3 Data Conversion MA90.INI [info] Level=3 Build=hu-07Mar96-10: WM EN [device LP] Id=HP Laser eries III PhysName=LP1 Cp=1B E Cpcols=133 Cr=rue Ff=1B266C3048 Ptoff=1B45 Pton= 1B266C32411B266C F C B C p=1b266b3053 pcols=80 [device PD] Id=Deferred Printing PhysName= Prtype= Pglines= [device PF] Id=File Output PhysName= Prtype= Pglines= MA 90 for Windows Installation Guide

50 50 Chapter 3 Data Conversion he changes include: he "[info]" comment block was added to the beginning of the file. he fcbs, cibs, aliases, stblen, prefix, and novell_locks options were skipped. he alias labels became data block keys. For example, "alias LP" became "[device LP]". "Id=" and "PhysName=" were added to the physical device name and comment. he mode names were proper cased. For example, "lock=" became "Lock=". EN he printer LP Boolean "Cr" label had a value of "=rue" added to it. All entries must follow a "name=value" format. "PD1" was saved as "PD" and all other such devices were skipped. "PF1" was saved as "PF". Application Data File Conversion he Application Data File Conversion program (UPCV1) converts Level 2 BB x data files into ProvideX data files used by MA 90 programs. here are two modes of operation for this program: stand-alone and interactive. tand-alone, in-place data conversion is invoked automatically during installation of the software. In this mode, all BB x data files for all companies found in the current directory are overwritten by the new ProvideX files. he only operator interaction occurs if there is inadequate disk space to continue the conversion and on completion of the program. MA 90 for Windows Installation Guide

51 51 Chapter 3 Data Conversion MA 90 data files from previous versions of MA 90 should not be moved under the \MA90 directory to which MA 90 was installed. Converting Application Data Files he Data Conversion program can be run by selecting Convert Evolution/2 Data Files from the Library Master Repair menu. In this mode, the operator specifies the company to convert and the source directory in which the BB x data files reside. he files are converted from their original location into the current MA 90 directory. Do not copy or install a previous version of MA 90 data files under the MA90\ hierarchy created after installing MA 90. he Convert Evolution/2 Data Files option, when run from the Library Master Repair menu, may encounter errors if all the files are not synchronized with each other. Input Fields EN When the data conversion process begins, the window shown below appears. If the conversion process is proceeding through a first-time installation, the program attempts to convert all company codes automatically. If an in-place, or automatic upgrade is being performed, a warning confirmation message appears; otherwise, the procedure begins when the total amount of disk space available has been confirmed. MA 90 for Windows Installation Guide

52 52 Chapter 3 Data Conversion he conversion program (UPCV1) can be run at any time using Convert Evolution/2 Files from the Library Master Repair menu. When running this utility by itself, the user must enter the company code to convert or select all companies. he conversion program converts an entire company at a time; individual data files for each module cannot be converted. EN MA 90 data conversion is performed on all data for a given company. o maintain integrity between applications, it is not possible to convert a specific module. Company Code: Enter a valid company code or enter an asterisk to indicate that all companies are to be converted. Choose the Lookup button to list all defined companies. When running automatically during a first-time installation, the company code is set to "*", indicating that all companies are to be converted. ource Directory: Enter the directory in which the Level 2 data resides. By default, the current directory appears. After the user selects the directory, the program scans for BB x files and displays the results on the window. In stand-alone mode, the directory is set to the current MA 90 directory and cannot be changed. he conversion program converts data located in alternate directories; however, the placement of the converted data files depends on the type of conversion, according to the following guidelines. If you are converting data in place, resulting data is located in the existing alternate directory. Existing data is overwritten. If you are converting data from another source directory (parallel upgrade), resulting data is placed under the MA90 directory. Existing data files remain to allow parallel data processing. MA 90 for Windows Installation Guide

53 EN 53 Chapter 3 Data Conversion pecific Company he source directory is scanned for valid BB x files. Applications associated with the specified company appear, along with the number of bytes used in the source files for each module. he total number of bytes used in the source files for this company appear at the otal Bytes field. All Companies If all companies are specified, the company codes found to contain BB x data files are listed, with the number of bytes for applications within each company. MA 90 for Windows Installation Guide

54 EN 54 Chapter 3 Data Conversion Proceeding with the Conversion After the scan for EVOLUION/2 data files has concluded, choose the Cancel button to abort the conversion program and exit to the MA 90 menu system. Choose the Proceed button on the Convert Evolution/2 Data Files window to continue processing. A confirmation dialog box appears if you are going to perform a conversion that will destroy existing data files (an in-place or automatic upgrade). his dialog box does not appear if a parallel upgrade is performed. :Warning It is important to thoroughly back up the EVOLUION/2 data files. Performing an out-of-place or parallel upgrade does not overwrite the original EVOLUION/2 data files; therefore, the files remain secure. It is only when performing an in-place upgrade, where the original files are replaced with new MA 90 files, that a backup becomes essential so that the system can be restored, if necessary. he conversion program then checks for available disk space. When converting data in place, processing is suspended at this dialog box until a valid response from the operator is entered. Conversion Processing As each module is converted, a conversion progress bar appears. If the conversion program determines that enough free disk space is not available for converting the application files, the following message appears. he conversion process is interrupted and control returns to the MA 90 menu system. MA 90 for Windows Installation Guide

55 55 Chapter 3 Data Conversion Conversion Completion After all modules are converted, control returns to the Convert Evolution/2 Data Files window. Choose the Cancel button to exit to the MA 90 menu system. he conversion log file called CNVLOG.X, found in the MA90\HOME directory, can be used to determine the type and severity of any errors that occurred in the conversion program. If the conversion log file is large, error lines can be singled out by searching for the string "**". Application Upgrade Conversion EN he final step of the conversion process is to upgrade the application data files to current MA 90 standards. he data conversion process converts the data files from the BB x format to the ProvideX format. his final conversion is responsible for converting the data file structure so that it can be used by the current MA 90 modules. he conversion takes place automatically when the module is first accessed with older data files. he structure of the data files is appropriately modified. It is very important to enter and exit out of every module to ensure that the conversion process is run on all the data files for a given company. For example, if Accounts Payable has been converted, but General Ledger has not been accessed since the data conversion, errors will occur when posting the Daily ransaction Register because the file structures are incompatible. When upgrading from Level 2 data files, the conversion is almost exclusively limited to changing the version record ("v" record in the parameters file); however, depending on what specific level of modules the data is upgrading from, and to, additional conversions may be necessary. he most significant conversion for MA 90 data files is the conversion of the General Ledger Detail file. Note that when starting General Ledger for the first time in MA 90, this conversion process can take some time, depending on the size of the GL5 file. When upgrading from Level 1 data files, more conversion steps are required to bring the data files "up to date" with current MA 90 data structures. his often takes a significant amount of time to convert, based on the size of the data files. he older the structure of the data files, the more steps that are required to perform the conversion. his is handled automatically when the module is first accessed. MA 90 for Windows Installation Guide

56 Installing Onto a ingle User ystem Chapter 4 For information on compatibility, refer to the Operating ystem/platform Compatibility Matrix on the age oftware Web site. Windows 95 Chapter his chapter specifically covers stand-alone (single-user) installations. Minimum system requirements and sample configuration files accompany each platform. As new operating systems and drivers are released, the information in this manual is subject to change. his chapter covers the following operating systems. Windows 95 Windows 98 Windows N 4.0 Workstation 56 4 EN :Warning Older, non-intel Pentium processors may not be registered through Windows as Pentium processors. MA 90 may not be compatible in this environment. he following operating configurations are required for running MA 90 on a Windows 95 system. An Intel Pentium or better class processor running at 166 MHz or faster A minimum of 32 Mb RAM etup Procedures Follow the installation procedures for Windows 95 from either the CD-ROM or 3½" floppy distribution media. Installation of Windows 95 can also be performed from the network. he Windows 95 Installation wizard walks you through the installation; a "ypical" installation is recommended. MA 90 for Windows Installation Guide

57 57 Chapter 4 Installing Onto a ingle User ystem Windows 98 he following operating configurations are required for running MA 90 on a Windows 98 system. An Intel Pentium or better class processor running at 166 MHz or faster A minimum of 32 Mb RAM etup Procedures Follow the installation procedures for Windows 98 from either the CD-ROM or 3½" floppy distribution media. Installation of Windows 98 can also be performed from the network. he Windows 98 Installation wizard walks you through the installation; a "ypical" installation is recommended. EN Windows N 4.0 Workstation his section discusses the use of Windows N 4.0 as a single-user workstation. he About Program Manager or About Windows N dialog box should display information regarding the build of Windows N currently installed, as well as the service packs for the operating system. It is important to keep the operating system on the latest service packs available. In the case of Windows N 4.0, five service packs have been released to date. Installing the latest service pack installs all previous service packs. o obtain information on the latest service packs available for Windows N, refer to the Operating ystem/platform Compatibility Matrix on the age oftware Web site. ystem Requirements age oftware has tested Windows N under the Intel x86 platform only with the following configurations. MA 90 software has not been tested and is therefore not supported running on an N erver with a MIP R4000, Digital Alpha AXP, or PowerPC processor. MA 90 for Windows Installation Guide

58 58 Chapter 4 Installing Onto a ingle User ystem he following operating configurations are required for running MA 90 on Windows N. An Intel Pentium or better class processor running at 166 MHz or faster A minimum of 64 Mb RAM A VGA or higher resolution color video display monitor capable of 640 x 480 resolution (uper VGA configuration is recommended) Printer etup EN If everything is set up correctly, you should be able to print to the printer from any Windows application, such as Notepad or WordPad. Do not run MA 90 until you are sure that you can print to at least one Windows printer set up in Print Manager. Workstations using N cannot print directly to physical devices set up in Library Master Device Configurator (for example, device name of LPx). MA 90 for Windows Installation Guide

59 Chapter Installing Onto a Novell NetWare 3.12/3.20 Network Chapter 5Chapter 3 his chapter discusses the use of Novell NetWare as a server and the various configurations required by the server and workstations in order for MA 90 to operate properly in this environment. For specific workstation setups, refer to the appropriate section in this chapter for the operating system under which the workstation is running. For information on compatibility, refer to the Operating ystem/platform Compatibility Matrix on the age oftware Web site. etup and Configuration 59 5 EN :Warning Failure to exit MA 90 software through the normal procedures may result in data loss or corruption. Always remember to exit the MA 90 software completely before turning off or rebooting your workstation. imilarly, shutting down NetWare while anyone is working in MA 90 is likely to result in data corruption. For this reason, it is recommended that you provide your NetWare server and any critical workstations with Novell-approved uninterruptible power supplies. If you are running a disk caching program (such as MARDRV or uper PC wik) you may want to disable the cache while using NetWare; there have been sporadic reports of conflict between MARDRV and the NetWare shell programs (LL/mlid/IPXODI/VLM). NetWare Rights MA 90 users need full rights (for example, read, write, create, erase, modify, and file scan) to all MA 90 data directories. Grant each user account full rights to all data directories with MA 90 data files that the user should be able to use. Module data directories are named with the module code and the company code of the data in that directory (for example, PRABC has the Payroll data for company code ABC). All MA 90 users should also have full rights to the MA90\OA and MA90\HOME directories. MA 90 for Windows Installation Guide

60 60 Chapter 5 Installing Onto a Novell NetWare 3.12/3.20 Network Additionally, full rights must be granted to users for the following combinations. Payroll users need full rights in the MA90\PR (program) directory to maintain the ax ables (which are the same for all company codes). Anyone authorized to use Report Master needs full rights to the MA90\RM directory to maintain reports (which are the same for all company codes). he same applies to Import Master (MA90\DI) and PostMaster (MA90\PM). ime and Billing users need full rights in the MA90\B directory to maintain billing formats (which are the same for all company codes). EN Configuring Captured Printers in Device Configurator his section covers captured printer configurations using Library Master Device Configurator. Library Master Device Configurator is provided as a convenience for users upgrading from DO versions of MA 90 to the Windows version of MA 90. It is recommended that you print to printers defined through Windows instead of using Library Master Device Configurator. Printers that are already defined through Windows will automatically appear on the printer selection list. Captured printing refers to the redirection of print output from a workstation to a virtual network printer that is shared between several workstations. All printer configurations assume that the printer is already captured at the workstation. here is nothing in Library Master Device Configurator that performs any part of a NetWare capture. Before you attempt to configure printers in MA 90 software, you should have a list of the printers that are captured on your workstation. One way to determine the queue names captured on this workstation is to use the command CAPURE HOW at the M-DO prompt (on any drive) any time after logging into NetWare. If you receive a Bad Command or File Name error when running the CAPURE HOW command, make sure that you have a search path to the PUBLIC directory on the Y volume of your server. If you have no captured printers, your network administrator must capture the printers outside of MA 90. E and ECOFF, previously used in Library Master Device Configurator, are no longer supported in Windows. MA 90 for Windows Installation Guide

61 61 Chapter 5 Installing Onto a Novell NetWare 3.12/3.20 Network Configuring Local Printers in Device Configurator his section covers local printer configurations using Library Master Device Configurator. Library Master Device Configurator is provided as a convenience for users upgrading from DO versions of MA 90 to the Windows version of MA 90. You should print to printers defined through Windows instead of using Library Master Device Configurator. Printers that are already defined through Windows will automatically appear on the printer selection list. In a network environment, you can have a mix of different types of printers attached to various workstations. Each of these printers may require a different configuration for such features as compressed printing and the number of lines per page. Defining Local Printers for a Workstation EN Local printing refers to the attachment of a printer to a workstation printer port and printing directly to that port. he available parallel or serial ports are accessed directly by MA 90 software by specifying the name of the printer port to which the printer will be connected. MA 90 software allows you to configure local printers in such a way that a given workstation displays its own local printers in the Printer election window. A workstation does not display the local printers attached to any other workstation. o define local printers for a workstation: 1 elect Device Configurator from the Library Master Utilities menu. 2 Choose the Local Printers button, and enter the workstation ID for the workstation that has a local printer. his should be the same identifier shown on the ystem Information dialog box for the workstation (select Run from the File menu and type *INFO). his workstation ID is added to the third line of the display while defining local printers. For more information, refer to Device Configurator in your Library Master manual. 3 Define the printer devices that are local to the workstation. MA 90 for Windows Installation Guide

62 62 Chapter 5 Installing Onto a Novell NetWare 3.12/3.20 Network roubleshooting Because the MA 90 software uses high-level techniques to access computer resources, most problems with computer hardware can be quickly diagnosed and resolved. Whenever an error occurs, take the time to write the message exactly and what you did just before the error message appeared. If possible, choose the Info button on the error message dialog box; this produces more information about the error that helps your authorized MA 90 Reseller or oftware Consultant isolate the cause of the problem and provide the correct solution as quickly as possible. For more information, refer to the troubleshooting templates on the age oftware Web site. Novell NetWare Networks EN For specific support on operating system configuration, consult the vendor from whom you purchased that product. o obtain a list of required NetWare patches for each version of NetWare, refer to the Operating ystem/platform Compatibility Matrix on the age oftware Web site and the PALI.HM document on the Novell Internet Web site. o determine the level of NetWare, type the following command at the DO prompt. NVER Each server you are logged onto displays the user license and the current version of NetWare that is running. An example of the output from the NVER command is shown below. NEWARE VERION UILIY, VERION 3.75 NetBIO Protocol pecification: V-2.0 IPX Version: 3.10 PX Version: 3.10 LAN Driver: NDI 3.1 DRIVER V0.00 hell: V3.26 Rev. A DO: MDO V7.00 on IBM_PC Fileerver: IYONE Novell NetWare v3.12 (100 user) (8/12/93) Fileerver: MIHOHI Novell NetWare v3.12 (50 user) (8/12/93) MA 90 for Windows Installation Guide

63 63 Chapter 5 Installing Onto a Novell NetWare 3.12/3.20 Network Checklists If you receive a Bad Command or File Name error message, change to the drive mapping for the server's Y volume and then change it to the PUBLIC directory. he current versions of NetWare 3 supported by MA 90 are 3.12 and If the Monitor program shows an older version of NetWare, the operating system may need to be upgraded. Version 3.11 of NetWare is supported only when the latest NetWare 3.11 patches are applied. hese patches are available on both Novell's Compuerve and Internet sites. Prior versions of NetWare 3 are no longer supported. When installing MA 90 to a NetWare 3 server, proceed to the appropriate checklist on the following pages for the specific type of workstation attaching to the server. EN :Warning Allow for as much disk space as possible. If disk space requirements are not met, the upgrade will encounter problems that may require restoring files from a backup. Parallel upgrades may require more hard disk space if your hard drive is partitioned for 16 or 32 sectors. Determining Hard Disk pace Before installing to the server, make sure that there is adequate hard disk space available for the application. If you are upgrading an existing MA 90 installation and want to convert data files, determine which conversion method to use. Open a DO prompt and change to the MA90 directory. ype DIR *.OA / to view the total amount of bytes currently occupied by MA 90 files and the total amount of bytes free on the hard drive. If alternate directories are used, the information obtained from the DIR command will not be accurate. If an in-place upgrade is performed, multiply the total amount of bytes currently occupied by MA 90 files by 1½ to determine approximately how much space is necessary for the data conversion. his space is primarily required for temporary files during conversion; however, MA 90 for Windows files are slightly larger than Level 2 files. If a parallel upgrade is performed, multiply the total amount of bytes currently occupied by MA 90 files by 2½ to determine approximately how much space is necessary for the data conversion. Because new copies of the data files are created for each module and company code, additional space is required temporarily to perform the conversion. Additionally, MA 90 for Windows files are slightly larger than Level 2 files. MA 90 for Windows Installation Guide

64 64 Chapter 5 Installing Onto a Novell NetWare 3.12/3.20 Network Verify that the name of the Windows directory has not changed to something other than WOW during installation. Windows 95/98 Workstations Use the following checklist for Windows 95/98 workstations that will be running MA Make sure that Windows is installed on the local hard drive. Running a shared version of Windows on a network drive is not supported. If there is no WOW directory off the root of the local drive, it is possible that Windows is running from a server. A Windows utility program such as Norton Utilities, or WinProbe shows you where Windows is running from. EN For specific support on printers and operating system configuration, consult the vendor from whom you purchased that product. :Warning he path specified for MA 90 operation should not be assigned as a EARCH drive. 2 Verify the minimum system requirements for a Windows workstation. he system must be running on an Intel Pentium or better class processor running at 166 MHz or faster and have at least 32 Mb of RAM installed. Install additional memory or upgrade the processor, if necessary. 3 Check the hard disk space. here must be enough hard disk space available to copy the required workstation system files, which require at least 10 Mb. If Custom Office is installed, another 10 Mb is required for a total requirement of 20 Mb. 4 Verify that the current Microsoft Client for NetWare Networks or Novell's IntranetWare Client for Windows 95/98 is installed and that the Novell Client 32 drivers are installed; the Client 32 drivers must be version For more information, refer to the Operating ystem/platform Compatibility Matrix on the age oftware Web site. 5 Verify that the network is accessible from this workstation. Restart Windows 95/98. After logging onto the server, all workstations should have mapped network drives that have access to the directory where MA 90 software is or will be installed. he drive mapping for the MA 90 software on each machine must be mapped on the same path. For example, one computer cannot have MA 90 mapped on the X:\APP\MA90 directory while a second computer has MA 90 mapped on the X:\MA90 directory. MA 90 for Windows Installation Guide

65 EN 65 Chapter 5 Installing Onto a Novell NetWare 3.12/3.20 Network 6 Make sure that the workstation can print to a network printer from Windows 95/98, either using Notepad, Word, or any other Windows program. 7 et or validate the EMP variable in the AUOEC.BA file. his environment variable must point to a valid temporary directory and is used by Windows for temporary files. MA 90 may not function properly if this variable is not set. 8 Restart the system before running MA 90. MA 90 for Windows Installation Guide

66 Chapter 6 Installing Onto a Novell NetWare 4 or 5 Network Chapter 6 his chapter describes the setup and configuration for a Novell NetWare 4 or 5 network. etup and Configuration 66 For information on compatibility, refer to the Operating ystem/platform Compatibility Matrix on the age oftware Web site. Before installing to the server, make sure that there is adequate hard disk space available for the application. If you are upgrading an existing MA 90 installation and you want to convert data files, determine which conversion method to use, then open a DO prompt and change to the MA90 directory. ype DIR *.OA / to obtain the total amount of bytes currently occupied by MA 90 files and the total amount of bytes free on this particular hard drive. If alternate directories are used, the information obtained from the DIR command will not be accurate. EN :Warning Allow for as much disk space as possible. If disk space requirements are not met, the upgrade will encounter problems that may require restoring files from a backup. If an in-place upgrade is performed, multiply the total amount of bytes currently occupied by MA 90 files by 1½ to determine approximately how much space is necessary for the data conversion. his space is primarily required for temporary files during conversion; however, MA 90 for Windows files are slightly larger than Level 2 files. If a parallel upgrade is performed, multiply the total amount of bytes currently occupied by MA 90 files by 2½ to determine approximately how much space is necessary for the data conversion. Because new copies of the data files are created for each module and company code, additional space is required temporarily to perform the conversion. Additionally, MA 90 for Windows files are slightly larger than Level 2 files. E and ECOFF, previously used in Library Master Device Configurator, are no longer supported in Windows. MA 90 prints directly to the Windows default printer; printer resources must be configured in the Print Manager. Novell NetWare 4.1x NetWare 4.10, 4.11, and 4.20 are currently the only supported versions of NetWare 4 on which MA 90 operates. MA 90 is not supported under NetWare 4.0, 4.01, or For a workstation to connect to the NetWare 4 server, the appropriate clients, drivers, and protocols must be installed. MA 90 for Windows Installation Guide

67 67 Chapter 6 Installing Onto a Novell NetWare 4 or 5 Network Novell NetWare 5.0 Make sure to adhere to the following guidelines when installing to a NetWare 5.0 server. NetWare 5.0 is only supported with MA 90 Level 3.31 or higher. It is not supported on Level 3 (character-interoperable) versions of MA 90. MA 90 is only supported on Windows 95/98 workstations. Windows N clients (Workstation or erver) are not supported. Novell Client version 3.10 for Windows 95/98 must be used. NetWare Operating ystem upport Pack 2 for NetWare erver (NW5P2A.E) must be installed. EN If using Novell torage ervices (N), install the N2AA.E patch after installing upport Pack 2. Workstations must be running either the Microsoft Client for NetWare Networks or the Novell Client version 3.10 for Windows 95/98. If the Novell client is being used, make sure it is Version For additional information about these patches, consult your system administrator and Novell's Web site. In addition, check the MA 90 Operating ystem Platform Compatibility Matrix on the age oftware Web site for the most up-to-date information on this operating system. MA 90 for Windows Installation Guide

68 68 Chapter 6 Installing Onto a Novell NetWare 4 or 5 Network Verify that the name of the Windows directory has not changed to something other than WOW during installation. Windows 95/98 Workstations Use the following checklist for Windows 95/98 workstations that will be running MA 90 on a NetWare 4.10, 4.11, 4.20, or 5 server. 1 Make sure that Windows is installed on the local hard drive. Running a shared version of Windows on a network drive is not supported. If the WIN.COM file in the WOW directory off the root of the local drive does not exist, it is possible that Windows is running from a server. A Windows utility program, such as Norton Utilities or WinProbe, shows you where Windows is running from. EN For specific support on operating system configuration, consult the vendor from whom you purchased that product. :Warning he drive specified for MA 90 operation should not be assigned as a EARCH drive. 2 Verify the minimum system requirements for the Windows 95/98 workstation. he system must be running on an Intel Pentium or better class processor running at 166 MHz or faster and have at least 32 Mb of RAM installed. Install additional memory or upgrade the processor if necessary. 3 Check the hard disk space. here must be enough hard disk space available to copy the required workstation system files, which require at least 10 Mb. If Custom Office is installed, another 10 Mb is required for a total requirement of 20 Mb. 4 Verify that the current Microsoft Client for NetWare Networks or Novell's IntranetWare Client for Windows 95/98 is installed and that the Novell Client 32 drivers are installed; the Client 32 drivers must be version 2.50 or For the most current information, refer to the Operating ystem/platform Compatibility Matrix on the age oftware Web site. 5 Verify that the network is accessible from this workstation. Restart Windows 95/98. After logging onto the server, all workstations should have mapped network drives that have access to the directory on which the MA 90 software is or will be installed. he drive mapping for the MA 90 software on each machine must be mapped on the same path. For example, one computer cannot have MA 90 mapped on the X:\APP\MA90 directory while a second computer has MA 90 mapped on the X:\MA90 directory. MA 90 for Windows Installation Guide

69 EN 69 Chapter 6 Installing Onto a Novell NetWare 4 or 5 Network 6 Make sure that the workstation can print to a network printer from Windows 95/98, either using Notepad, Word, or any other Windows program. 7 et or validate the EMP variable in the AUOEC.BA file. his environment variable must point to a valid temporary directory and is used by Windows for temporary files. MA 90 may not function properly if this variable is not set. 8 Restart the system before running MA 90. MA 90 for Windows Installation Guide

70 Chapter 7 Installing Onto a Windows N erver 4.0 Network Chapter 7 his chapter describes the setup and configuration of the Windows N 4.0 erver and supported workstation environments specifically for MA 90. ystem Requirements 70 EN For information on compatibility, refer to the Operating ystem/platform Compatibility Matrix on the age oftware Web site. For specific support on Windows N 4.0 configuration, consult the vendor from whom you purchased the networking software. MA 90 requires a Windows N 4.0 erver with the following system requirements. Additional memory or hard disk space may be required based on the number of users that will be accessing MA 90 and the other applications being run on the Windows N 4.0 network. Minimum erver Configuration he Windows N 4.0 erver requires the following system requirements to run MA 90. An Intel Pentium or better class processor running 166 MHz or faster is required. AGE OFWARE only supports Windows N 4.0 running under the Intel x86 platform. MIP R4000, Digital Alpha AXP, and Power PC processors have not been tested and are not supported. A minimum of 64 Mb RAM plus 4 to 6 Mb per user on the server is required. Additional memory may be required based on the number of users and applications running on the network. A VGA or higher resolution color video display monitor is required. Approximately 100 Mb of free disk space on a single partition for MA 90 application program files is required. his number varies greatly based on the number of applications installed. ystem etup and Library Master require approximately 25 Mb of hard disk space. Each module occupies approximately 10 to 15 Mb of hard disk space. MA 90 for Windows Installation Guide

71 71 Chapter 7 Installing Onto a Windows N erver 4.0 Network Minimum Workstation Requirements MA 90 is currently supported running on a Windows N 4.0 erver with Windows 95/98 workstations or Windows N 4.0 Workstation. he following system requirements are needed to run MA 90 from the Windows 95/98 workstation. An Intel Pentium or better class processor running at 166 MHz or faster A minimum of 32 Mb RAM for Windows 95/98; a minimum of 64 Mb RAM is recommended for Windows N A VGA or higher resolution video display monitor capable of 640 x 480 resolution (uper VGA configuration is recommended) EN Approximately 10 to 20 Mb of hard disk space on the workstations for MA 90 system files MA 90 for Windows Installation Guide

72 72 Chapter 7 Installing Onto a Windows N erver 4.0 Network etup Procedures Follow the instructions for setting up the Windows N 4.0 erver from the Windows N erver Installation Guide. MA 90 is supported only on an N erver with an Intel Pentium-class processor running at 166 MHz or faster and a minimum of 64 Mb of RAM. Be sure to read the Installation Guide completely before proceeding with the installation of a Windows N erver. If you need help installing Windows N 4.0, contact your local Microsoft expert or Microsoft's Product upport via Internet, Compuerve, or directly by phone. EN For specific support on your hardware or operating system, contact the vendor from whom you purchased that product. During installation you will be prompted for a domain name, which will be the domain of which this N erver is a member, or for which it is a domain controller. he Windows 95/98 workstations that connect to the N erver to run MA 90 will use this domain as well. After installing the Windows N 4.0 erver, apply the latest service pack for Windows N 4.0. For the most current information, refer to the Operating ystem/platform Compatibility Matrix on the AGE OFWARE Web site. Networking Procedures he following section describes how to attach to a Windows N erver from a Windows 95/98 workstation. Windows 95/98 wo components are required for setting up a workstation with Windows 95/98 to allow it to communicate with a Windows N network. he first component is the actual setup of the networking protocols that allow the computer to communicate with the N erver. he second component is specifying the domain to which the Windows 95/98 workstation will connect. MA 90 for Windows Installation Guide

73 73 Chapter 7 Installing Onto a Windows N erver 4.0 Network etting Up Networking :Warning Do not install the IPX/PX protocol; it causes errors and data corruption. Networking components are divided into clients, adapters, protocols, and services. Clients provide the necessary redirectors for the specific network. his allows the computer to connect and access shared network resources. Adapters are the drivers for the network interface card (NIC) currently installed in the workstation. his driver may need to be obtained by the NIC manufacturer if it is not provided by Microsoft with Windows 95/98. Protocols are rules and/or conventions used by computers to send information across a network. Windows 95/98 includes NetBEUI (used for Microsoft Windows networks), IPX/PX (used primarily for Novell networks), and CP/IP. ervices are processes that perform specific functions on a network and usually provide some application programming interface (API) for other programs to call. EN Clients, adapters, protocols, and services can be established on a Windows 95/98 workstation through the Network program in the Control Panel. A dialog box similar to the following appears. MA 90 for Windows Installation Guide

74 EN 74 Chapter 7 Installing Onto a Windows N erver 4.0 Network o connect to a Microsoft Windows N erver, Microsoft's Client for Microsoft Networks must also be loaded. For more information on connecting Windows 95/98 workstations to a Windows N 4.0 erver, refer to your Windows 95 or Windows 98 User's Guide or the network operating system documentation. Logging Onto a Domain After Microsoft's Client for Microsoft Networks is loaded, highlight this client on the Network window and choose the Properties button. he following dialog box appears. elect the Log on to Windows N domain check box to enable the Windows 95/98 workstation to log into a Windows N domain. Enter the domain name of the N erver at the Windows N domain field. After choosing the O button, restart the Windows 95/98 workstation. After Windows 95/98 restarts, log onto the Windows N domain. Before installing the MA 90 software, create a share point on the N erver and make sure that the user name that will be used to install the software has full privileges for the share point. For more information regarding creating users and creating share points, refer to your Microsoft Windows N User's Guide. MA 90 for Windows Installation Guide

75 EN 75 Chapter 7 Installing Onto a Windows N erver 4.0 Network Printer etup Before attempting to print in MA 90, a printer must be set up in the Windows environment. o set up a new printer in Windows 95/98, select ettings from the tart menu, then select Printers. Double-click the Add Printer icon and follow the instructions in the Add Printer Wizard. Printing Procedures he properties tabs are different for each type of printer driver; however, they should all have a Details tab. On completion of the Add Printer Wizard, a new printer item appears in the Printers folder with the name of the newly created printer. If it is necessary to change the settings on this printer, right-click the Printer icon and select the Properties menu item. he properties of the printer item appears. elect the Details tab to change the port to capture or change the location of the printer itself.. hese properties can be changed as many times as necessary. Other tab options do not affect the way MA 90 prints to this printer. Choose the O button when you are finished editing the printer's properties. MA 90 for Windows Installation Guide

76 76 Chapter 7 Installing Onto a Windows N erver 4.0 Network MA 90 usually prints to the default Windows printer unless directed to do otherwise. You can set a printer to be your default Windows printer by right-clicking the printer in the Printers list box and selecting et As Default. If everything has been set up correctly, you should be able to print to the printer from any Windows application, such as Notepad or WordPad. Drive Mappings EN Checklists o access MA 90 from a workstation, the workstation must establish a drive mapping to the N erver's shared resource (the root of the network drive or a subdirectory thereof). It is important that this drive path mapping be identical for each workstation. Although the drive letters do not need to be the same, the path to the MA 90 programs must be the same. For example, if a user has drive : mapped to \\AUMI\ROO\ACC (where AUMI is the name of the N erver, ROO is the shared resource, and ACC is a directory off of ROO) and installs MA 90 from this system, all other workstations must see MA 90 from the same "false root." Another user cannot access MA 90 with a drive mapping of \\AUMI\ROO. All users should access MA 90 from the same drive letter and path mappings. Use the following checklists as a guide to ensure the most relevant portions of the N erver that directly affect MA 90 are configured properly. If you are unfamiliar with Windows N erver, consult a hardware engineer or consultant trained in Windows N. AGE OFWARE cannot offer the level of support required to specifically set up a Windows N network for each individual client because individual server requirements vary greatly. MA 90 for Windows Installation Guide

77 77 Chapter 7 Installing Onto a Windows N erver 4.0 Network Verify that the name of the Windows directory has not changed to something other than WOW during installation. Windows 95/98 Workstations (Workstation Checklist) Use the following checklist for a Windows 95/98 workstation connected to a Windows N erver network. 1 Verify that the workstation running Windows 95/98 has an Intel Pentium or better class processor running at 166 MHz or faster and has at least 32 Mb of RAM installed. 2 Make sure that Windows is installed on the local hard drive. Running a shared version of Windows on a network drive is not supported. If the WIN.COM file in the WOW directory off of the root of the local drive does not exist, it is possible that Windows is running from a server. A Windows utility program, such as Norton Utilities or WinProbe, verifies whether Windows is running from a server. EN For specific support on printers and operating system configuration, consult the vendor from whom you purchased that product. 3 Check the hard disk space. here must be enough hard disk space available to copy the required workstation system files, which require at least 10 Mb. If Custom Office is installed, another 10 Mb is required for a total requirement of 20 Mb. 4 Verify that the network is accessible from this workstation. After logging onto the server, all workstations should have mapped network drives that have access to the directory where MA 90 software is or will be installed. he drive mapping for the MA 90 software on each machine must be mapped on the same path. For example, one computer cannot have MA 90 mapped on the X:\APP\MA90 directory while a second computer has MA 90 mapped on the X:\MA90 directory. 5 Make sure that the workstation can print to a Windows printer, either using Notepad, Word, or any other Windows program. 6 et or validate the EMP variable in the AUOEC.BA file. his environment variable must point to a valid temporary directory and is used by Windows for temporary files. MA 90 may not function properly if this variable is not set. 7 Reboot the system before starting MA 90. MA 90 for Windows Installation Guide

78 78 Chapter 7 Installing Onto a Windows N erver 4.0 Network Windows N Workstation 4.0 (Workstation Checklist) Use the following checklist for a Windows N Workstation connected to a Windows N erver network. 1 Verify that the workstation running Windows N Workstation has at least 64 Mb of RAM installed. 2 Make sure that the latest service pack for N is installed on the workstation. It is very important to install service packs to both N Workstations and ervers. For more information, refer to the Operating ystem/platform Compatibility Matrix on the AGE OFWARE Web site. EN Verify that the name of the Windows directory has not changed to something other than WINN during installation. For specific support on printers and operating system configuration, consult the vendor from whom you purchased that product. 3 Make sure that Windows is installed on the local hard drive. Running a shared version of Windows on a network drive is not supported. If the WIN.COM file in the WINN directory off the root of the local drive does not exist, it is possible that Windows is running from a server. A Windows utility program, such as Norton Utilities or WinProbe, verifies whether Windows is running from a server. 4 elect Network from the Control Panel, which displays the Network window. On the Identification page, verify that the Computer name and the Workgroup fields are correct. For more information on domain configurations, refer to the Windows N erver User's Guide or online documentation. 5 Check the hard disk space. here must be enough hard disk space available to copy the required workstation system files, which require at least 10 Mb. If Custom Office is installed, another 10 Mb is required for a total requirement of 20 Mb. 6 Verify that the network is accessible from the workstation. After logging onto the server, all workstations should have mapped network drives that have access to the directory where MA 90 software is or will be installed. he drive mapping for the MA 90 software on each machine must be mapped on the same path. For example, one computer cannot have MA 90 mapped on the X:\APP\MA90 directory while a second computer has MA 90 mapped on the X:\MA90 directory. MA 90 for Windows Installation Guide

79 EN 79 Chapter 7 Installing Onto a Windows N erver 4.0 Network 7 Make sure that the workstation can print to a Windows printer, either using Notepad, Word, or any other Windows program. 8 et or validate the EMP variable. his environment variable must point to a valid temporary directory and is used by Windows for temporary files. MA 90 may not function properly if this variable is not set. 9 Reboot the system before starting MA 90. MA 90 for Windows Installation Guide

80 80 Chapter Installing Onto a Windows 95/98 Peer-to-Peer Network Chapter 8Chapter 3 his chapter discusses the use of Windows 95/98 as a peer-to-peer 8 workstation. ystem Requirements EN For information on compatibility, refer to the Operating ystem/platform Compatibility Matrix on the age oftware Web site. etup Procedures he following operating configurations are required for running MA 90 on a Windows 95/98 system. An Intel Pentium or better class processor running at 166 MHz or faster At least 64 Mb RAM All computers running MA 90 in the peer-to-peer network must be running the same operating system. Hybrid configurations of Windows 95, Windows 98, or Windows N are not supported. Follow the installation procedures for Windows 95/98 from either the CD-ROM or 3½" floppy distribution media. Installation of Windows 95/98 can also be performed from the network. he Windows 95/98 Installation Wizard will walk you through the installation; a "ypical" installation is recommended. Networking Procedures his section describes how to connect Windows 95/98 to a network. he procedure is identical for Windows (Windows 95/98 or Windows N) and Novell NetWare networks. If you are not attaching Windows 95/98 to a network, proceed to Printing Procedures on page 83. MA 90 for Windows Installation Guide

81 EN 81 Chapter 8 Installing Onto a Windows 95/98 Peer-to-Peer Network Establishing Network Connections Establish your network protocol using the Network program in the Control Panel. A window similar to the following appears. Networking components are divided into clients, adapters, protocols, and services. Clients provide the necessary redirectors for the specific network. his allows the computer to connect and access shared network resources. Adapters are the drivers for the network interface card (NIC) currently installed in the computer. his driver may need to be obtained from the NIC manufacturer if it is not provided by Microsoft with Windows 95/98. Protocols are rules and/or conventions used by computers to send information across a network. Windows 95/98 includes NetBEUI (used for Windows networks), IPX/PX (used primarily for Novell networks), and CP/IP. ervices are processes that perform specific functions on a network and usually provide some Application Programming Interface for other programs to call. MA 90 for Windows Installation Guide

82 EN 82 Chapter 8 Installing Onto a Windows 95/98 Peer-to-Peer Network For more information on connecting Windows 95/98 workstations to a network server, refer to your Windows 95 or Windows 98 User's Guide or the network operating system documentation. Each workstation must recognize the network drive on which the MA 90 software is loaded as the same drive letter; however, Windows 95/98 allows users to connect to a network volume without mapping a drive letter to that volume. MA 90 software cannot run from this kind of "virtual" drive that has no mapping assignment. Use the Network Neighborhood or Explorer in Windows 95/98 to set up the mappings on each workstation. Map a network drive through Explorer or Network Neighborhood by right-clicking the volume name and selecting Map Network Drive. A dialog box similar to the following appears. elect a drive letter to which to map this drive and select the Reconnect at logon check box to connect this volume to this drive letter every time you log in. Choose the O button. his procedure must be used for any network configuration. MA 90 Workstation etup For individual Windows workstations to use MA 90, you must install the appropriate DLLs and libraries in each system's WOW\YEM directory. his is accomplished by running the Workstation etup utility. For more information, refer to Running the Workstation etup Program on page 33. MA 90 for Windows Installation Guide

83 EN 83 Chapter 8 Installing Onto a Windows 95/98 Peer-to-Peer Network Printing Procedures Network printers are mapped through Windows 95/98 if the appropriate network client is installed using the Network program in the Control Panel. o add a new printer, select the ettings/printers option from the tart menu, and then double-click the Add Printer option. Follow the instructions from the Add Printer Wizard as directed. After selecting the printer's queue, the wizard asks for the printer drivers, which may have to be obtained from the printer manufacturer if they are not included with Windows 95/98. he wizard also requires a name for the printer that will be used throughout all Windows 95/98 applications when printing. MA 90 for Windows Installation Guide

84 EN 84 Chapter 8 Installing Onto a Windows 95/98 Peer-to-Peer Network Changing Printer ettings After completing the Add Printer Wizard, a new printer item appears in the Printers folder with the name of the newly created printer. If it is necessary to change the settings on this printer, right-click the Printer icon and select the Properties option. he properties of the printer item appear. elect the Details tab to change the port being captured or the location of the printer itself. A sample of this window is shown below. Checklists A maximum of five workstations (including the server) can access MA 90 simultaneously via a Windows 95 network. hese properties can be changed as many times as necessary. Choose the O button when you are finished editing the printer's properties. he About Windows 95 or About Windows 98 dialog box displays information about Windows 95/98 and the relevant service packs that have been installed on the system. At this time, there is one service pack available for Windows 95. Although recommended, the service pack is not required to run MA 90. For the most current information, refer to the Operating ystem/platform Compatibility Matrix on the age oftware Web site. MA 90 for Windows Installation Guide

85 85 Chapter 8 Installing Onto a Windows 95/98 Peer-to-Peer Network Windows 95/98 (erver Checklist) Use the following checklist for the server of a Windows 95/98 network. 1 A server running Windows 95/98 requires an Intel Pentium or better class processor running at 166 MHz or faster and have at least 64 Mb of RAM available. 2 Make sure there is enough hard disk space to accommodate MA 90 and all data files. If this is a first-time installation, plan for an average of 10 to 15 Mb of disk space per module. EN :Warning Allow for as much disk space as possible. If disk space requirements are not met, the upgrade will encounter problems that may require restoring files from a backup. For specific support on operating system commands such as UP, consult your operating system manuals or contact the vendor from whom you purchased that product. 3 If you are upgrading an existing MA 90 Level 1.x or 2.x installation and want to convert data files, determine which conversion method to use. Open a DO prompt and change to the MA90 directory. ype DIR *.OA / to obtain the total amount of bytes currently occupied by MA 90 files and the total amount of bytes free on this particular hard drive. If alternate directories are used, the information obtained from the DIR command will not be accurate. If an in-place upgrade is performed, multiply the total amount of bytes currently occupied by MA 90 files by 1½ to determine approximately how much space is necessary for the data conversion. his space is primarily required for temporary files during conversion; however, MA 90 for Windows files are slightly larger than Level 2 files. If a parallel upgrade is performed, multiply the total amount of bytes currently occupied by MA 90 files by 2½ to determine approximately how much space is necessary for the data conversion. Because new copies of the data files are created for each module and company code, additional space is required temporarily to perform the conversion. 4 Make a backup of the server, especially if you are upgrading the software and data files. Verify this backup before installing. 5 Enable sharing on the root of the drive where MA 90 is going to be installed. his can be accomplished in My Computer by right-clicking the root of the drive and selecting the haring option. Make sure that the share access type is set to Full Control. MA 90 for Windows Installation Guide

86 86 Chapter 8 Installing Onto a Windows 95/98 Peer-to-Peer Network Windows 95/98 (Workstation Checklist) Use the following checklist for a client workstation of a Windows 95/98 network. All clients of a Windows 95/98 network should also be running Windows 95/98. 1 A workstation running Windows 95/98 requires an Intel Pentium or better class processor running at 166 MHz or faster and have at least 32 Mb of RAM available. EN Verify that the name of the Windows directory has not changed to something other than WOW during installation. For specific support on printers and operating system configuration, consult the vendor from whom you purchased that product. 2 Make sure that Windows is installed on the local hard drive. Running a shared version of Windows on a network drive is not supported. If the WIN.COM file in the WOW directory off of the root of the local drive does not exist, it is possible that Windows is running from a server. A Windows utility program, such as Norton Utilities or WinProbe, verifies whether Windows is running from a server. 3 Check the hard disk space. here must be enough hard disk space available to copy the required workstation system files, which require at least 10 Mb. If Custom Office is installed, another 10 Mb is required for a total requirement of 20 Mb. 4 Verify that the network is accessible from this workstation. After logging onto the server, all workstations should have mapped network drives that have access to the directory where MA 90 software is or will be installed. he drive mapping for the MA 90 software on each machine must be mapped on the same path. For example, one computer cannot have MA 90 mapped on the X:\APP\MA90 directory while a second computer has MA 90 mapped on the X:\MA90 directory. 5 Make sure that the workstation can print to a Windows printer, either using Notepad, Word, or any other Windows program. 6 et or validate the EMP variable in the AUOEC.BA file. his environment variable must point to a valid temporary directory and is used by Windows for temporary files. MA 90 may not function properly if this variable is not set. 7 Reboot the system before starting MA 90. MA 90 for Windows Installation Guide

87 Chapter 9 Installing Onto a Windows N Workstation 4.0 Peer-to-Peer Network Chapter 9 his chapter describes the setup and configuration of the Windows N 4.0 Workstation Peer-to-Peer network. ystem Requirements 87 EN For information on compatibility, refer to the Operating ystem/platform Compatibility Matrix on the age oftware Web site. he Windows N 4.0 Workstation requires the following system requirements to run MA 90. An Intel Pentium or better class processor running 166 MHz or faster is required. age oftware only supports Windows N 4.0 running under the Intel x86 platform. MIP R4000, Digital Alpha AXP, and Power PC processors have not been tested and are not supported. A minimum of 64 Mb RAM on the server is required. Additional memory may be required based on the number of users and applications being run on the network. A VGA or higher resolution color video display monitor is required. Approximately 100 Mb of free disk space on a single partition for MA 90 application program files is required. his number varies greatly based on the number of applications being installed. ystem etup and Library Master require approximately 25 Mb of hard disk space. Each module occupies approximately 10 to 15 Mb of hard disk space. MA 90 for Windows Installation Guide

88 88 Chapter 9 Installing Onto a Windows N Workstation 4.0 Peer-to-Peer Network Drive Mappings o access MA 90 from a workstation, the workstation must establish a drive mapping to the N erver's shared resource (the root of the network drive or a subdirectory thereof). It is important that this drive path mapping be identical for each workstation. Although the drive letters do not need to be the same, the path to the MA 90 programs must be the same. For example, if a user has drive : mapped to \\AUMI\ROO\ACC (where AUMI is the name of the N erver, ROO is the shared resource, and ACC is a directory off of ROO) and installs MA 90 from this system, all other workstations must see MA 90 from the same "false root." Another user cannot access MA 90 with a drive mapping of \\AUMI\ROO. All users should access MA 90 from the same drive letter and path mappings. Checklists EN Use the following checklists as a guide to ensure that the most relevant portions of the N erver that directly affect MA 90 are configured properly. If you are unfamiliar with Windows N erver, consult a hardware engineer or consultant trained in Windows N. age oftware cannot offer the level of support required to specifically set up a Windows N network for each individual client because everyone's individual server requirements vary greatly based on their business. Windows N 4.0 Workstation (erver Checklist) Use the following checklist for the Windows N erver. 1 Check the hardware. Make sure the N erver is installed on an Intel Pentium-class server or higher running at 166 MHz or faster. A minimum of 64 Mb of RAM is also required. Adding additional memory improves performance and may be required for larger installations running additional, network-intensive software. :Warning his is the most important item to check on an N installation. 2 Verify that the latest service pack that has been tested by age oftware is installed on the N erver. For more information, refer to the Operating ystem/platform Compatibility Matrix on the age oftware Web site. MA 90 for Windows Installation Guide

89 89 Chapter 9 Installing Onto a Windows N Workstation 4.0 Peer-to-Peer Network 3 Make sure that there is enough hard disk space to accommodate MA 90 and all data files. If this is a first-time installation, plan on an average of 10 to 15 Mb of disk space per module. EN :Warning Allow for as much disk space as possible. If disk space requirements are not met, the upgrade will encounter problems that may require restoring files from a backup. Parallel upgrades may require more hard disk space if your hard drive is partitioned for 16 or 32 sectors. For specific support on operating system commands such as UP, consult your operating system manuals or contact the vendor from whom you purchased that product. 4 If you are upgrading an existing MA 90 Level 1.x or 2.x installation and want to convert data files, determine which conversion method to use. Open a DO prompt and change to the MA90 directory. ype DIR *.OA / to obtain the total amount of bytes currently occupied by MA 90 files and the total amount of bytes free on this particular hard drive. If alternate directories are used, the information obtained from the DIR command is not accurate. If an in-place upgrade is performed, multiply the total amount of bytes currently occupied by MA 90 files by 1½ to determine approximately how much space is necessary for the data conversion. his space is primarily required for temporary files during conversion; however, MA 90 for Windows files are slightly larger than Level 2 files. If a parallel upgrade is performed, multiply the total amount of bytes currently occupied by MA 90 files by 2½ to determine approximately how much space is necessary for the data conversion. Because new copies of the data files are created for each module and company code, additional space is required temporarily to perform the conversion. 5 Make a backup of the server, especially if you are upgrading the software and converting data files. Verify this backup before installing. MA 90 for Windows Installation Guide

90 90 Chapter 9 Installing Onto a Windows N Workstation 4.0 Peer-to-Peer Network Verify that the name of the Windows directory has not changed to something other than WINN during installation. Windows N 4.0 Workstations (Workstation Checklist) Use the following checklist for a Windows N 4.0 workstation connected to a Windows N erver network. 1 Verify that the workstation has an Intel Pentium-class processor or higher running at 166 MHz or faster and at least 64 Mb of RAM available. 2 Make sure that Windows is installed on the local hard drive. Running a shared version of Windows on a network drive is not supported. If the WIN.COM file in the WINN directory off of the root of the local drive does not exist, it is possible that Windows is running from a server. A Windows utility program, such as Norton Utilities or WinProbe, verifies whether Windows is running from a server. EN For specific support on printers and operating system configuration, consult the vendor from whom you purchased that product. 3 Check the hard disk space. here must be enough hard disk space available to copy the required workstation system files, which require at least 10 Mb. If Custom Office is installed, another 10 Mb is required for a total requirement of 20 Mb. 4 Verify that the network is accessible from this workstation. After logging onto the server, all workstations should have mapped network drives that have access to the directory where MA 90 software is or will be installed. he drive mapping for the MA 90 software on each machine must be mapped on the same path. For example, one computer cannot have MA 90 mapped on the X:\APP\MA90 directory while a second computer has MA 90 mapped on the X:\MA90 directory. 5 Make sure that the workstation can print to a Windows printer, either using Notepad, Word, or any other Windows program. 6 et or validate the EMP variable. his environment variable must point to a valid temporary directory and is used by Windows for temporary files. MA 90 may not function properly if this variable is not set. 7 Reboot the system before starting MA 90. MA 90 for Windows Installation Guide

91 91 Index EN Index A adapters, defined 73 application data files conversion complete 55 processing 54 converting 51 in-place upgrade 54 input fields 51 overview 50 window sample 51 application upgrade conversion, overview 55 C CD installation confirmation 24 destination directory 22 setup options 23 ystem etup 19 checklists conversion 11 installation 11 printer configuration 15 workstation setup 16 conditional printers, FIG.BBX conversion 47 FIG.BBX file conversion overview 46 sample FIG.BBX 48 MA90.INI 49 conversion, checklist 11 Crystal Reports, installing 25 D Data Access Pack, etup program 30 data conversion application data files 50 upgrade 55 FIG.BBX file 44, 46 flowchart 42 overview 41 parallel 41 system file 43 data file conversion, in-place 41 destination directory, CD installation 22 F FID0 value, overriding 37 FID0MAP.INI, location 36 G graphic conventions 10 H how to use this manual 9 I installing checklist 11 Crystal Reports 25 from CD 19 MA Novell NetWare 4.1x 66 onto Novell NetWare Windows 95/98 Peer-to-Peer 80 single-user systems 56 Web Publishing Wizard 27 A B C D E F G H I J L M N O P Q R U V W X Y Z MA 90 for Windows Installation Guide

92 92 EN L local printers configuring for Novell NetWare defining 61 M MA 90 installing 10 starting 39 Microsoft Web Publishing Wizard 27 N Novell NetWare 3.12 checklists overview 63 Windows 95/98 64 configuration 59 configuring local printers 61 spooled printers 60, 61 determining NetWare level 62 hard disk space 63 required patches 62 rights 59 setup 59 troubleshooting 62 Novell NetWare 4.1x checklists, Windows 95/98 68 overview 66 O ODBC Workstation etup 36 P printer configuration checklist 15 printing procedures Windows 95/98 Peer-to-Peer 83 Windows N 4.0 network 75 protocols, defined 73 PVXFID0 algorithm 36 services, defined 73 session tracking 36 single-user installations 56 spooled printers, configuring for Novell NetWare , 61 system file conversion customized forms 43 Import Master Maintenance file 43 List Mode Master files 43 Payroll ax ables 43 PostMaster 43 Report Master Maintenance file 43 Y0CL.OA 43 Y0EC.OA 43 ime and Billing billing formats 44 unconverted data files 45 ystem etup CD installation 19 ystem tartup, overview 17 U unconverted data files Bar Code masterfile 45 data dictionary 45 Deferred Print file 45 End of Period file 45 error log 45 File/Record format 45 OA menu system 45 ask menus 46 W Web Publishing Wizard 27 Windows 95 operating requirements 56, 57 setup procedures 56, 57 single-user installation 56, 57 A B C D E F G H I J L M N O P Q R U V W X Y Z MA 90 for Windows Installation Guide

93 93 EN Windows 95/98 Peer-to-Peer checklists server 85 workstation 86 installing 80 MA 90 workstation setup 82 network connections, establishing 81 procedures networking 80 printing 83 setup 80 system requirements 80 Windows 98 operating requirements 56, 57 setup procedures 56, 57 single-user installation 56, 57 Windows N 4.0 Network checklists Windows 95 workstations 77 Windows N 4.0 workstation 78 drive mappings 76 networking with Windows printer setup 75 requirements system 70 workstation 71 server configuration 70 setup procedures 72 Windows N 4.0 Peer-to-Peer checklists server 88 workstation 90 drive mappings 88 requirements system 87 time zone synchronization 88 Windows N 4.0 Workstation printer setup 58 requirements system 57 single-user installation 57 workstation ID assigning 36 overview 36 Workstation etup Program location 33 overview 32 running 33 workstation setup, checklist 16 A B C D E F G H I J L M N O P Q R U V W X Y Z MA 90 for Windows Installation Guide