Apex Language Processor(ALP)

INSTALLATION OF ALP

Installation on DOS

Installation on Novell Netware

Installation on Unix

Installation on DOS

To install ALP insert floppy # 1 in the floppy drive and type (assuming the drive is A ):

A: INSTALL

Press the Enter key to initiate installation. Specify the complete path of the directory where ALP is to be installed.

TOP   

ALP on Novell Netware server

To install ALP3.0 (Net) on the server follow the following steps:

a) Connect the ALP Netware dongle to the parallel port of the server. Connect printer cable or other dongles, if any, after that and tighten the ALP dongle screws.

b) Login as Supervisor/ADMIN

c) Insert ALP floppy no.1 in the floppy drive.

d) If the server is a 386/486/pentium-based PC, copy the HASPSERV.NLM from the Disk #1 to the Netware SYS:\SYSTEM directory.

e) If the server is a 286 based PC, copy the HASPSERV.VAP from the disk #1 to the netware SYS:\SYSTEM directory.

f) In the netware console prompt ‘:’ load the HASPSERV.NLM or VAP (for 286 PC s) as shown below.

          : load HASPSERV

This has to be done whenever server is switched off and on. So best way is to add following line into the Netware’s AUTOEXEC.NCF file. This can be done by running the INSTALL.NLM program from the console. Type ‘load instll’ at the netware console. A menu will appear. Select ‘system options’ and from the next menu select ‘Edit Autoexec.ncf file ‘ .Add the ‘load HASPSERV’ command to it and exit. Also make sure that ‘CLIB’ is loaded before the haspserv.

g) Now to install ALP, run INSTALL.EXE from the Disk #1 of ALP. Give the destination path as per choice on the server and load all the three floppies.

h) Make sure that 64Kb of expanded memory is available on the workstation because ALP needs 64Kb of expanded memory. (See ALP manual APPENDIX ‘Expanded Memory Support’)

i) Add ALP directory path into system login script and give the rights of ALP directory to all the ALP users.

j) Logout as Supervisor. Login as a user and type SETALP to set all the default values . Save settings and exit from SETALP. Now type ALPHN (opening ALP with Hindi spellchecker) or ALPGJ (For Gujarati spellchecker) or ALPMR (For Marathi spellchecker) to open the ALP.

 TOP

Installation on Unix

ALP for UNIX requires some settings in UNIX as well as in Terminal. ALP version 3.0 needs GIST Terminal firmware version 7.7 or higher. ALP for Unixware will work on UNIXWARE version 2.0x. ALP for SVR4 will work on UNIXWARE version 1.0/1.1.

ALP disks will come on packaged format.

a) To install the ALP login as root and give the following command:

pkgadd -d/dev/rdsk/fd0 or pkgadd -d /dev/dsk/fd0
fd0 is for floppy drive A, fd1 is for floppy drive B.
or
Instead fd0/fd1 you can mention the device full name.

(Ex. Floppy drive device names like fd096ds15 for 1.2mb disk and fd1135ds18 for 1.44mb disk)

After giving  the  above  command system  will prompt you some questions about installation.  Then it will copy the ALP, SETALP and GISTDIAGS files into /usr/bin/alp , Samples  files  into /usr/bin/alp/samples/  sub  directory  and Keyboard  files  to /usr/bin/alp/kbd/ subdirectory.  The  DONGLE (Hardware lock)  driver  files  Driver.o  will  be  copied  into /etc/conf/pack.d/don/ directory. Then it will relink the kernel.

During installation if ALP is facing any problems, then it will create an error file /tmp/alp.err and abort the installation. To analyze the problem, cat that file.

For SCO UNIX release 5 or XENIX use SCOADMIN to install  the  ALP.

For older version of SCO UNIX use custom command.

ALP requires 8 bit mode. Both GIST Terminal and UNIXtty driver should be in 8bit mode. In GIST Terminal 7 bit mode should be off and  in Terminal communication parameters Char size should be  8. Check the UNIX parameters settings through stty command.  Give stty-a command. It will show the terminal settings. If cs7 is present then change cs7 to cs8. For more options give man stty.

1) ALP is not able to install in SVR4 UNIX and it will  display error message  "Symbol  references error  Post  Script  install failed".Some  Unix releases may not have Space.c file. After  loading the ALP, Check the /etc/conf/pack.d/don/ directory before relinking  the kernel. Driver.o file will be there. Create a file  with the name of Space.c with the following entry int dondevflagi

Save the file and give the following command.

/etc/conf/bin/idbuild -K

The above command will rebuild the Kernel.

Note : Before relinking the kernel make a copy of /stand/unix.

2) Link Kit not found

Check  the /etc/conf/bin/idbuild. This command is  required  to rebuild the kernel. If it is not there please reinstall the  Link kit.

3) Printing from ALP

For  taking  printouts from ALP, GIST Terminal  local  printing should  be enabled. The procedure is given in the  Terminal  manual. Printer driver, printer splmode, 8 or 7  bit mode (depend  upon software  package)  and  Numscript settings  should  be  selected properly.

In  SETALP  printer Device/name should be mentioned. Then only printing from ALP is possible.

LOCAL PRINTING:

After installing ALP give the following command.

usr/lib/lpadmin -p gist -v/dev/tty1a

                                      enable gist

                                      accept gist

Run SETALP, in option3 mention the printer device is /dev/tty1a. By giving  the above lpadmin command it will create a Printer device. Enable command will enable the printer device. By giving Accept command, printer will be able to accept print requests from users.

Here tty1a is the GIST terminal where printer was connected. In this setup while printing is on you cannot use the terminal. When printing is on, at the same time if terminal wants to be accessed use Background printing.

BACKGROUND PRINTING:

For background printing GIST terminal Auxillary port has to  be connected to one of the system serial port. Make that tty entry respawn in /etc/inittab. Give the following command.

/usr/lib/lpadmin -p gist -v/dev/tty2a

                                      enable gist

                                      accept gist

Here tty2a is the one which was connected to Auxillary port  of GIST Terminal. In SETALP mention the printer device/name is tty2a. In this setup you can use the terminal while printing is ON. The printer data will be redirected from Console to Auxillary port of GIST Terminal to Printer. But if 2 or more  persons give  the printing in same time it will result Garbage  printing. To avoid this problem give printer device / name is Gist in SETALP. Note that even if number of printers is more than onle, ALP can use only one printer.

PRINTING FROM GIST CARD INSTALLED IN SERVER:

For  printing from GIST card the GIST card Device  driver  for UNIX has to be installed in console. GIST card will be  installed as a g_tty.Give the following command.

/usr/lib/lpadmin -p gist -v/dev/g prn

                                      enable gist

                                     accept gist

Run SETALP, in option3 mention the printer device / name is Gist. Connect the printer cable to parallel port of GIST Card.

Note :  Before Installing ALP make a copy  of  /stand/unix  for safety purpose. With ALP version 3.00 GISTDIAGS software will  be bundled. Run the GISTDIAGS in GIST Terminal. It will test the Settings of Terminal, Console and hardware lock of ALP and it will generate a gisttest.log file. Cat that file. If any problems was found then it will be mentioned in that file. If any problems are found send the report file to CDAC. The GIST Terminal firmware version should be 7.7 or higher. Otherwise the  terminal may give problem in ALP and GISTDIAGS.

If background printing is giving any problem, then check the entry of the auxillary port of the GIST terminal (where printer was connected) in /etc/inittab. Check the cable connection in between GIST Terminal Auxillary port and console. Check the printer cable. Give the printing command from command prompt to check whether the data is going to lp spooler. Check the lp spooler with lpstat command for print requests. If any print requests are found but still it is not printing then go to SYSADMIN check the printer configuration. Enable printer schedule.

4) Insufficient memory to run Spell checker             

The  memory available is not enough to run Spell Caster.  Increase the max process size in /etc/conf/cf.d/stune, rebuild the UNIX kernel and reboot.