 |
|
|
|
QL 1000
Series
Chapter 8 - Loading Application Software
This chapter explains how to create or modify batch files to make each QL Series processor run application software when it boots up. For information on the QL Series boot image files, their boot sequence, or modifying the boot image file, see the "Technical Reference Manual - Modifying QL Image Files".
QL series processors boot from an image file in the \LOGIN subdirectory on the file server. The last function of the image files boot sequence instructs each processor to execute one of the following two batch files:
QLUSER.BAT - The default batch file for all QL Series processors. If the QL processors do not find a node specific batch file, they will execute this default batch file.
QLUSRxxx.BAT - (Where xxx is the QL Node number). If the QL processor finds a batch file with its node number in the filename, it will execute this node specific batch file. No other processor will execute this batch file since each QL processor will have a different node number.
The following explains the functions of the two batch files, and how to use them for loading application software on the QL processors.
This is the default batch file. Each processor will execute this file unless it finds a node specific batch file. The file must be in the \LOGIN subdirectory. It reads as follows:
ECHO OFF Turns off batch file display SET COMSPEC=Y:COMMAND.COM Sets COMSPEC PROMPT $P$G Sets the DOS prompt QLRCV Loads the QL remote connect program LOGIN Executes the NetWare LOGIN command
NOTE: Loading QLRCV on the processor provides QLVision support for the node.
This node-specific batch file can be used to execute an application program on one QL processor. Each batch file has a processor's node number as part of its filename. This gives each processor a unique batch file, to give your network maximum flexibility. The batch files must reside in the \LOGIN subdirectory of your file server. You can create the batch file with any ASCII editor (such as EDLIN).
Creating Node-Specific Batch Files
1. Create a batch file QLUSRxxx.BAT, where xxx is the processor's node number (for example, QLUSR290.BAT).
2. Add to the batch file any command you wish to execute. There are two methods of loading application software, mostly dependent on the version of NetWare. Read both methods below to determine which one will work best for your configuration.
Method A. NetWare 286, (or 3.10 with FXOPEN patch) - You can put your application program in a subdirectory below \LOGIN. This will allow you to load the application program without logging in as a user. This works well with most communications programs that we have tested, but if it does not work, or your application program seems to have problems finding its files, you must use method B instead.
Method B. NetWare 386 3.11 or 3.10 without FXOPEN patch - You must create a temporary user file that you can use to log in, change to the proper subdirectory, and execute the application program. You then can change back to \LOGIN, execute LOGOUT, clear the screen, and execute the Novell LOGIN command. With this configuration, users calling in will be in the \LOGIN subdirectory with the Novell LOGIN command showing on their screen.
The following sample batch files will give you an idea on how to create custom batch files for each processor to load different communication programs. The batch files will be shown in both methods described above.
About the Sample Batch Files
Some samples shown use command line options for the application program. The ones shown are for test purposes only, and must be set up for your particular application.
The DOS PATH command has been added to some batch files to insure that the application program can find its configuration or data files if necessary.
The %1 variable is the DOS variable LOADHIGH.COM carried over from the image file, and is used to load programs into upper memory. This variable only appears if you have the Memory Manager software installed. Not all application programs will load into upper memory. The ones that have been tested are shown with the %1 variable on the command line in the batch file. The file LOADHIGH.COM must be in the application subdirectory.
Sample 1 (QLUSR001.BAT) - To Load Co/Session 5.02 (Method A)
ECHO OFF Turns the batch file display off SET COMSPEC=Y:COMMAND.COM Sets COMSPEC PATH F:\LOGIN\;F:\LOGIN\SESSION Sets DOS Path PROMPT $P$G Sets DOS prompt QLRCV Loads the QL utility CD \LOGIN\SESSION Changes to the proper subdirectory %1 SAPPLICA Loads Co/Session (SAPPLICA.EXE) CD.. Changes back to \LOGIN CLS Clears the screen LOGIN Executes the NetWare LOGIN command
Sample 2 (QLUSR126.BAT) - To Load PCAnywhere IV LAN (Method B)
ECHO OFF Turns the batch file
display off
SET COMSPEC=Y:COMMAND.COM Sets COMSPEC
PROMPT $P$G Sets DOS prompt
QLRCV Loads the QL utility
LOGIN TEMPUSER Logs in a temporary user
with minimum
necessary rights to
|COM|PC4LAN
CD \COMM\PCA4LAN Changes to the proper
subdirectory
%1 AWLOVL1.EXE -I=JEG -O=H -M=W Loads PCAnywhere IV
CD \LOGIN Changes back to \LOGIN
LOGOUT Logs out the temporary
user
CLS Clears the screen
LOGIN Executes the NetWare
LOGIN command
These sample batch files are provided to assist you in getting your application program to work. If you have problems, please read the section on "Testing Your Application Software", and refer to the "Troubleshooting" chapter in the "Technical Reference Manual". For detailed instructions on using asynchronous software on the QL products, see the "Remote Communications Chapter" in the "Technical Reference Manual".
If you have problems running your application program on the QL processor, here are a few things you should check.
1. Does the application program run on a regular workstation?
Run the application program on a regular network workstation to make sure it is configured correctly. If you are running a communications program, connect the modem to the workstation's COM port to ensure the modem and cable configurations are correct. Once you get everything to work on the regular workstation, switch everything back to the QL board and retest.
2. Does your program require special drivers, or CONFIG.SYS settings?
See the Section on "Modifying Boot Image Files" in the "Technical Reference Manual" for information on adding device drivers or changing the CONFIG.SYS file in the boot image file.
3. Does your application program require more File Handles for Novell?
Regular workstations and QL Series boards running under NetWare default to 40 File Handles. To increase this number, you need to create a SHELL.CFG file for the image file. If using a database program, we suggest increasing the number to 60. See the Section on "Modifying Boot Image Files" in the "Technical Reference Manual" for information on adding a SHELL.CFG file to the image file.
4. Does the program work on your regular workstations, but not on the QL processors?
Check the version of Novell shell file (NETX.COM) on the workstation that the application works on. If it is a different version than the one the QL processor is using, change the NETX.COM file for the QL image file to the version that works on your regular workstation.
5. If you can't tell where the program fails . . .
Change the QL processors batch file back to the default (QLUSER.BAT), and reset the board with QLRESET. Use QLVISION to determine when the processor goes ACTIVE. Then use the QLCONN program to take over control of the QL workstation. Log on to the QL workstation and manually go through the steps required to load your application program. You now will be able to see any error messages that appear.
6. Do You Have Problems with LOGIN, LOGIN scripts, NetWare Menus, etc.?
Most of the problems that show up on the QL Series processors and Novell's programs are related to different versions of program files and the NetWare shell file (NETX.COM) or IPX.COM. For example: There are six or seven versions of NetWare's LOGIN.EXE file. Some of these versions will cause a workstation to lose mapping information, some versions affect rights. Most of the problems can be corrected by simply updating the file, or changing the version of shell files.
7. Are you using the QL Memory Manager?
The Memory manager program uses the memory area between 640K and 1MB of memory. Some application programs may also try to use this memory area, and will not work with the Memory Manager program enabled. Try a different video option for the Memory Manager, or disable it to get your application program to work. See the section on "Memory Configurations and Software" in the" Technical Reference Manua"l for more information.
If your application program requires changes to the CONFIG.SYS file, the addition of device drivers, or a SHELL.CFG file, see the "Modifying Image Files" chapter in the "Technical Reference Manual" for more information.
This document, and all Web contents, Copyright © 1997
by Cubix Corp., Carson City, NV, USA.