Q: I am following the NetWare for SAA instructions exactly but I keep getting Btrieve errors. Why?
A: The AUTOEXEC examples in the instructions contain a btrieve line with a part that can easily be read as:
-1=20
In fact, the l is not a number, it is a lower case L. The line should read:
-l=20
Q: Why do I get the error message "LC:Unload from console of service NACS"
when trying to use a Digiboard in my NACS version 3?
A: The Digiboard AIODGXI driver is case sensitive. The NODE=0 statement in AUTOEXEC.NCF must be in lower case. For example:
LOAD AIODGXI port=0200 mem=D0000 node=0
Q: Can I use DOS 5 with Access Server?
A: You can if you have upgraded to version 1.22. But do not use the memory management feature of DOS 5 with Access Server. The amount of RAM available per virtual DOS session will be significantly less than with DOS 3.3.
Q: I think I am following the Asynch Router addressing instructions, but the router acts as though the addressing is incorrect. Why?
A: Early versions of the Asynch Bridge/Router required the address on both sides to be the same. However, starting with Asynch Router 1.2 the addresses must be Different.
DR DOS Top Issues
Q: What are the requirments for the HIINSTALL, HIDEVICE, and HILOAD commands?
A:1. For these commands to be effective, your computer hardware must support upper memory through a DR DOS memory manager (HIDOS.SYS or EMM386.SYS). If a DR DOS 6.0 memory manager is not present, the device or executable is loaded into conventional memory.
2. These commands do not work with third-party memory managers. See the Optimization and Configuration Tips manual for more details. A brief description of these commands follows.
HIINSTALL: HIINSTALL loads specified TSRs into upper memory. If there is insufficient upper memory for the specified TSR, it is loaded into conventional memory. Although it is very similar to the HILOAD command (see below), HIINSTALL must be used in the config.sys or dconfig.sys file. Use HIINSTALL when you want to load a TSR permanently at boot time for best memory allocation. As with HILOAD, HIINSTALL loads the executable into upper memory only if enough Upper Memory Blocks (UMB's) are available.
HILOAD: HILOAD loads specified TSRs and network drivers into upper memory. HILOAD is similar to the HIINSTALL command (which must be loaded using the config.sys file), but it can be executed from the command line or from the autoexec.bat or other batch file. Before using HILOAD, you must enable upper memory with the MEMMAX +U command. This command loads the executable if enough UMBs are available. An example of the HILOAD command in a batch file follows:
MEMMAX +U
HILOAD LSL
HILOAD NE2000
HILOAD IPX
HILOAD NETX
MEMMAX -U
HIDEVICE: HIDEVICE loads specified device drivers into upper memory if UMBs are available. HIDEVICE must be loaded via the config.sys file. An example of HIDEVICE follows:
HIDEVICE=C:\DRDOS\ANSI.SYS
Q. What is MEMMAX, and how is it used?
A. The MEMMAX.EXE command selectively enables and disables those memory areas provided by DR DOS 6.0 that might conflict with some applications.
For example, MEMMAX -L and +L respectively disable and enables the first 64 Kbytes of conventional memory. This region is termed "low memory."
Usually the operating system resides in low memory; however, by using the DR DOS 6.0 MemoryMAX features, you can free up most of this area for running applications.
Some applications were written using packing utilities that become confused when loaded into this low memory. If this happens, the following message appears:
!Packed file is corrupt.
To correct this situation, use the MEMMAX -L command to disable low memory before running the application. After exiting the application, use MEMMAX +L to enable the low memory once again.
Q. What can I expect when I use SSTOR on my bootable hard drive?
A. The SuperStor program (and device driver) compress data for more efficient storage on hard disks. Data is automatically compressed when you write to the drive and decompressed when you read from the drive. You can increase the capacity of your hard disk considerably, depending on the type of files stored on the disk.
The following are some typical compression ratios achieved by SuperStor:
Executable program files 1.4:1 to 2:1
Word processing files 2:1 to 4:1
Video image file 2:1 to 8:1
The overall compression ratio of the files determines the total amount of disk space you can expect to obtain using SSTOR.
You may also notice a new drive letter when you use SSTOR. When the SSTOR utility compresses your first bootable hard disk, it automatically sets aside a small portion of the disk as uncompressed disk space and assigns it the next available drive letter. This space is used at boot time to load the SSTOR driver and the operating system. Applications cannot understand the compressed data in the compressed drive without a driver acting as a compression translator. See the DR DOS 6.0 Users Guide P. 471 for additional information.
Q. Can I use the HIDEVICE command to load the SuperStor drivers sstordrv.sys and devswap.com into upper memory?
A. The SuperStor drivers are designed to detect whether upper memory blocks are available and they load as much into upper memory as possible. The HIDEVICE statement is not necessary and should not be used on sstordrv.sys and devswap.com.
Load these drivers with the usual DEVICE command.
Likewise, if you use a third party memory manager such as a QEMM or 386MAX in place of the DRDOS memory manager, use the usual DEVICE statement Do not use the third party manager's equivalent of HIDEVICE to force all of the driver into upper memory.
Note that in order for the SuperStor drivers to detect and use available upper memory, you must load the memory manager before the SuperStor drivers.
For more information, see Faxback document #1202, "Hiloading SuperStor."
Q. I used SuperStore on my c: drive, and now my original d: drive has become e:. How can I get my original drive sequence back?
A. This situation may occur if a third party-disk partitioning scheme such as Disk Manager or Speedstor was used to partition the disk. To restore the original drive letter assignments, you must load the partitioning driver before the SuperStor driver. Do this by moving the line that loads the partitioning driver before the SSTORDRV.SYS driver in either the CONFIG.SYS file or the DCONFIG.SYS file (usually found on D: drive). You must also copy the partitioning driver to the same drive in which it is loaded.
TOP ISSUES NETWARE FOR MACINTOSH
Q: Can DOS workstations print to AppleTalk printers?
A: NetWare for Macintosh includes printer definition files for the LaserWriter and the ImageWriter. After you set up the VAP or NLM so that Macintoshes can print, you need only to run PRINTDEF to import the needed printer definition file (PDF) and define a form. Then run PRINTCON to define a job. Use CAPTURE and NPRINT, along with the DOS application's printer drivers, to send jobs to the queue.
A common problem with DOS workstations printing to the Macintosh queues is that print jobs do not print after being submitted to the queue. This happens if a text job, such as a screen print, is sent to a queue through a PostScript job. If you want to print a non-PostScript job, be sure to configure and use APLASER2.PDF for Apple LaserWriter printers, or PSTSCRPT.PDF for third-party PostScript printers. These files convert a text file into PostScript so the LaserWriter can print it. They are posted to CompuServe's NetWire and are shipped with v3.01 and v3.011 NetWare for Macintosh. Configuration through PRINTCON and PRINTDEF is documented in NetWare for Macintosh Installation and Maintenance.
Other oversights that will result in a failure to print include these:
- Not using a print header = 255 command in the SHELL.CFG file on the DOS workstation.
- Setting a printer to "reinitialize" mode in a PRINTCON job configuration.
- Attempting to print under Windows without the XMS shell.
Q: How do I set up printing so my Macintoshes can print to network printers?
A: With versions of NetWare for Macintosh below v3.01, all printers (either true Apple LaserWriters or LaserWriter-compatible printers) need to be connected to an AppleTalk network. The AppleTalk network on which the printer resides does not need to be connected directly to the file server, but it must be accessible to the file server via AppleTalk. There are also third-party solutions available for connecting LaserWriter printers to a dedicated AppleTalk device, that is connected to Ethernet.
With NetWare for Macintosh v3.01 and above, ATPS (AppleTalk Print Services) queues can be serviced by PostScript printers attached via serial or parallel cables to the NetWare v3.11 file server or NetWare DOS client. You must configure the ATPS.CFG file to set up a queue that will be handled by a print server other than ATPS. The syntax in the configuration file should be similar to this:
-o <name of the print queue> -wb -l -f <font file>
This syntax also works for PostScript printers that are attached to Ethernet but don't use the AppleTalk protocol, such as the HPIIIsi. The print server that handles this queue is configured in PCONSOLE. Look to the NetWare for Macintosh and Print Server documentation for more detailed information.
Q: When I try to print from PageMaker v4.2, it results in the following error messages:
ATPS: loading printer (<printer name>) with new Laser Prep
ATPS: can't open dictionary (SYS:SYSTEM|ATPS|ald20955.PRS)
ATPS: printer (<printer name>) returned bad dictionary status
What is the problem?
A: ATPS parses out the Aldus Prep dictionary version and revision number incorrectly, so it names the Aldus Prep dictionary incorrectly when it saves it to the SYS:SYSTEM\ATPS subdirectory. This results in ATPS not being able to use the file when it is time to print a PageMaker v4.2 print job. To correct this, you must rename the Aldus Prep file located in the SYS:SYSTEM\ATPS subdirectory. Look for a file named "ALD00.PRS " or "AL00.PRS" and rename it to "ALD20955.PRS".
Q: I seem to be having a compatibility problem with system inits and extensions and DataClub. My Macintosh crashes, and I get erratic behavior from the system. What could be the problem?
A: DataClub works fine with most common software, although there are some known init conflicts. Below are a few of the common ones. DataClub v2.0 Release Notes include a complete list of compatibility considerations.
SAM Intercept - The v2.x series of SAM needs to be loaded after the DataClub extension. If you do not have an extension loading utility (for example, InitPicker), then rename SAM Intercept to !SAM Intercept. Also, the v2.x series should set the SAM protection to Basic. DataClub and SAM v3.0 are compatible provided SAM loads before the DataClub extension file.
Note that under System 7 it is not sufficient to drag the SAM Intercept file into the System Folder. This can lead to SAM loading after all the extensions, leaving your system less protected. Under System 7, you must place the SAM Intercept file in the Extensions Folder and create an alias in the Control Panels Folder.
RasterOps Extensions - DataClub is not compatible with the RasterOps Extensions. These are optional when using the RasterOps screen and should be disabled.
Now Utilities - DataClub shows erratic behavior with the Now Utilities Startup Manager. Uncheck the "Show invisible folders" in the Control Panel.
