Help Knowledge Base Index
Help Knowledge Base

This is a knowledge base of many problems that exist in Windows.  In addition to the problems are definitions of technical terms and hints to increase your system performance.

Click on any topic below for explanation.

INSTRUCTIONS

Reference Information:

Hardware

This section includes problems with the physical components of your PC including all of the following topics.

MEMORY, CMOS, BIOS, COMMUNICATIONS, KEYBOARD, MOUSE, VIDEO, SOUND, NETWORK CARD, ACCELERATOR CARD, DRIVES

Print

This section deals with problems associated with printing including the following topics.

PRINTERS, DRIVERS, GRAPHICS, NETWORK

Application

The applications used to accomlish your daily tasks are covered here.

SPREADSHEETS, WORD PROCESSORS, GRAPHICS, NETWORK, UTILITIES, ACCESSORIES

System Configuration

Problems with Windows itself and your system are covered in this heading.

SYSTEM FILES, FONTS, WINDOWS, NETWORK, MEMORY MANAGERS

Networks

The problems associated with networking are covered here.

NETWORK OPERATING SYSTEMS, HARDWARE, PRINTING, DRIVES

Performance

Look here for tips on how to increase your system's performance.

HARDWARE, PRINT, APPLICATIONS, SYSTEM, NETWORK


Instructions

Help Instructions

You can find in for in Help by using the index or the Search feature.  To return to the Help Index after you read the instructions below, click the Back button or press the B key.

For complete instructions press F1 while the Help Window is active.

To use the Help Index

Do one of the following:

Click words that are like this.  The mouse pointer [image] will change to a hand like the picture on the right when you are over a clickable area.

Press the TAB key until you highlight the topic you want, and then press the ENTER key.

To return to the previous topic

Click the Back button or press the B key.

To open the Search feature in Help

Click the Search button or press the S key.

To close the Help window

From Help's File menu, choose Exit (ALT, F, X)


Sample

This is an example of a jump topic.  Click the mouse button to continue.


Hardware Problems

This section includes problems with the physical components of your PC, including chips, boards, cards, drives, ports, and anything attached to your ports.  Click on an item below for explanation.

General Information

Motherboard

See

MEMORY

This section covers conventional or ordinary memory, extended memory, and expanded memory.  It also gives a general overview and definitions of these terms.  Problems with memory chip failures and the errors messages that arise are also covered.

CMOS

This is a type of memory chip that can retain its memory when power is turned off because of a battery backup.  CMOS records all the information about the basic system configuration.  This section deals with the problems associated with the corruption of CMOS.

BIOS

BIOS is the basic input/output system of the PC.  Problems with BIOS can result in any of the input and output hardware of the PC, including printers, hard drives, floppy drives, or printers, to malfunction.

COMMUNICATIONS

This section covers modems and the problems associated with these cards.

KEYBOARD

This section covers the keyboard.

MOUSE

This section cover the mouse and its possible conflicts.

VIDEO

This section covers problems with the display of your PC.  This section covers video drivers, mismanaged memory, incorrect configurations, and adapter-monitor mismatches.

SOUND

This section covers problems with the card, the drivers, improper configuration of mics, and other recording settings.

NETWORK CARD

Network Interface Cards can have problems with memory mismanagement and improper drivers.  Check here for tips on installing NICs and for known conflicts.

DRIVES

This section covers drive controllers, CD-ROMS, hard drives, floppy drives, and other drives.  Problems can arise from improper partitioning, drivers, controller-drive conflicts, and controller-memory management conflicts.


Memory Problems

This section has nothing to do with Alzhiemer's disease.  It has to do with the storage area that information can be sent to and taken from by addressing specific locations in any order at any time.  This section specifically deals with the problems associated with Random Access Memory or RAM.  RAM memory chips are referred to by their maximum speed of operation and their storage capacity.  For example, your PC may have 1 Mb (megabyte or 1024 kilobytes) of 70 ns (nanosecond or billionths of a second) RAM.

General

General Information

Possible Problems

Specific Error Messages

~"Divide Overflow Error"

~Error P-CK 1(M) Parity Error

~System Hangs After PARITY CHECK 1 Error

Conflicts with Applications

~"Expanded Memory Error" with Lotus 123 2.x

~Data Query Extract has Missing Data in 123

~Memory Parity NMI Interrupt in WordPerfect


Possible Problems with Memory
Possible Problems with Memory.

VGA Boards

Problems with VGA boards usually arise because they occupy a block of memory that Windows cannot detect.

Network Interface Cards

Problems with Network Interface Cards usually arise because they conflict with memory managers.  Memory managers, like QEMM386, remap the areas assigned to these devices to create larger areas of unused memory, in which the memory managers then load other device drivers and programs.  This can cause problems because some cards' interrupt vectors will still point to the a memory address that is invalid.  If a memory manager has remapped this area the card may not perform properly.

Solution:

The solution to both these problems is to add the Exclude switch to the line that loads your memory manager.  For example, if your memory manager is EMM386 use the following lines:

C:\WINDOWS\EMM386.EXE EXCLUDE memlo-memhi

where memlo and memhi are the addresses of the block you wish to exclude.

This line is in your AUTOEXEC.BAT.  Use a text editor, like Notepad, to edit the file.


Divide Overflow Error
Problem:  "Divide Overflow" error

The "Divide Overflow" error, like the "Packed File Corrupt" error message, is caused by some problem with memory.

Solution:

Running FIXBIOS and TESTMEM.COM can often help pinpoint or fix such a problem.  If these programs do not correct or identify the problem, it is often possible to eliminate this error by increasing the numbers of available files and buffers.


Memory Parity NMI Interrupt
Problem:  "Memory Parity NMI Interrupt" Error with NMI Interrupt Chip.

Error:  "Memory Parity NMI Interrupt."  This message may appear at various times, especially when doing a spell check or running the thesaurus on a WordPerfect document, usually when the document on screen was 20 pages or more.  Sometimes this message will give you the following options (all which seemed to solve the problem temporarily):

1.  Type shut off NMI

2.  Reboot

3.  Press other keys to continue

Solution:

The problem is tied into the NMI interrupt chip.  Thus it was a hardware related problem, rather than a WordPerfect problem.  Replace the bad memory chip.


Error P-CK 1(M) Parity Error
Problem:  Error P-CK 1(M) Parity Error Hardware with Memory.

"P-CK 1(M) error when printing."  This is a parity check error.  A parity error is always a hardware problem.  This particular error indicates which of the memory chips is causing the problem.  The number before the (M) is the number of the chip causing the problem.

Solution:

Replace bad memory chip.


Parity Check 1
Problem:  System Hangs after"PARITY CHECK 1" Error

After displaying the message "PARITY CHECK 1" the system hangs.

Solution:

The PC has special circuitry that continually checks the memory (RAM) for anomalies.  Each time memory is read or written to, a "sanity check" is made. If this check fails, then a failure to properly store the information in memory has occurred.  In this event, the circuitry interrupts the system and displays a "PARITY ERROR" message.

More Information:

Memory chips on a typical PC are arranged in banks of nine.  The first eight chips serve as addressable memory, and the ninth chip holds the parity bits for the previous eight.  In this configuration, there is one parity bit.  In board memory, this parity bit is set for each byte of memory in such a way that the sum of the eight bits plus the parity bit is always odd.  If the system detects an even sum, a "PARITY CHECK 1" error occurs.  In memory on an expansion board, the message "PARITY CHECK 2" is displayed.

Static electricity is a common cause of parity errors.  If a computer comes in contact with a static charge, the charge may "zap" the computer's memory.

In some cases, an atom in the epoxy case will spontaneously decay, shooting out an alpha or beta particle.  If the particle hits a memory cell, it may cause the cell to change state.  The memory chip does not sustain any damage; however, the system will detect the error.

This information applies to Microsoft MS-DOS versions 3.2, 3.21, 3.22, 3.3, 3.3a, 4.0, 4.01, 4.01a, and 5.0.


CMOS Problems

CMOS memory is a battery-backed up RAM that keeps track of the PC's configuration information.  For example, CMOS will store the amount of RAM your system has installed or which types of drives are present.

If the battery fails CMOS will become corrupted.  Restoring CMOS in such a case must begin with replacing the battery.


BIOS Problems

BIOS (Basic Input/Output System) is the first set of code run upon boot up.  Specific addresses, devices, and software interface services are defined.  BIOS is ROM memory that contains instructions that application programs depend on to carry out certain functions.  Sending information out to the second parallel printer port or writing information to the 3.5" floppy are examples of tasks that applications may ask BIOS to do.  BIOS is capable of translating the program's request into commands for the specific devices used in a particular computer.  This frees the program from having to know the different characteristics of every computer manufacturer's parallel port or disk drive.

BIOS and Disk Drive Access

All DOS-based PCs include built-in ROM BIOS code that knows how to read and write individual sectors on a wide variety of hard disk and floppy disk types.  DOS itself allows the BIOS to accomplish these tasks.  This frees DOS from having to know the exact layout of a user's disk drives.  Applications know even less about the disk drives than DOS.  A DOS application simply requests that a file be written, and DOS informs the application that the file was written.

In contrast to DOS, Windows 3.1 can access megabytes of memory while ROM BIOS is restricted to less than 1MB of memory addresses.  This is done to maintain backward compatibility with the large number of DOS applications.  When Windows applications writes a file, Windows switches from protected mode to real mode so the BIOS can handle the request, and then Windows switches back.

Specific Conflicts

~ROM BIOS INTERRUPT

~XT Setup Problem

~Parity Error

~CRTL+P without a printer

~Hard disks with more than 1024 cylinders

~Floppy drives and BIOS


ROM BIOS Interrupt
Problem:   ROM BIOS interrupt problem  -  Date Rollover Problem if No Time Activity

In MS-DOS version 3.2, there is a date rollover problem at midnight that was corrected in MS-DOS versions 3.21 and later.  However, you may be experiencing date rollover problems in time intervals greater than 48 hours. If you are either running an application program or looping in COMMAND.COM.  The date rolls over only once in a time period extending over two midnight hours.  This information applies to Microsoft MS-DOS versions 3.2, 3.21, 3.3, 3.3a, 4.0x, 5.0 and 5.0a.

Explanation:

The problem is not inherent in MS-DOS versions 3.3x software; rather, it stems from the way the system-timer ROM BIOS services are handled.  If the computer is booted and the system date and time are initialized, the timer overflow flag is set to 0 (zero) by the ROM BIOS INT 1Ah system timer services 00h and 01h.  MS-DOS only checks the time when a command or function needs access to the system time, such as when the TIME command is invoked, or when a file modification function needs to set the file modification time.

When the MS-DOS versions 3.3x clock driver checks the system time, it uses these ROM BIOS system-timer clock services.  The format in which the data is returned is the number of counts since the system was powered-on, reset, or since the system-timer services were last activated.  The timer counts are generated 18.2 times per second.  If there have been more than twenty-four hours of counts, an overflow flag is set.  The MS-DOS clock driver uses this overflow flag, along with some date-comparison logic, to see if a midnight event has occurred.  However, if multiple midnight events have occurred since the last ROM BIOS system-timer check, MS-DOS has no way of knowing this, because the overflow flag is a Boolean entity and does not count multiple midnight events.

Thus, if an application is running constantly and never needs to access the ROM BIOS system-timer clock services, when the date is finally polled, MS-DOS will only have known that a single midnight event has taken place and will update the date accordingly.  Looping in COMMAND.COM at the command prompt will also reproduce this behavior.

Solution:

A workaround is to construct the application so that it will use a ROM BIOS system timer clock service at least once in a 24 hour interval.


Leading Edge XT Setup
Problem:   Leading Edge XT Setup Problem with MS-DOS Version 5.0

Leading Edge XT computers are shipped with only Phoenix BIOS and require either version 3.0 or 3.1 of Phoenix BIOS to set up and run correctly with MS-DOS version 5.0.  A BIOS upgrade is available from Leading Edge directly or from a Leading Edge distributor.  Version 3.11 of Phoenix BIOS (currently the latest version) should not be used as an upgrade, however, because it does not work properly with MS-DOS 5.0 on a Leading Edge XT computer.

Solution:

Leading Edge has acknowledged that either version 3.0 or 3.1 of Phoenix BIOS is required on their XT-class computers to work correctly with MS-DOS 5.0. If an earlier version is used, the Microsoft MS-DOS 5 Upgrade will not install.  After SETUP is typed at the command prompt, the cursor appears below the prompt, and the system hangs, requiring a system restart (both a "cold" and a "warm" restart usually work).  A similar effect also occurs when version 3.11 (the latest release) of Phoenix BIOS is used.

Leading Edge is providing a BIOS upgrade for $45.00.  To receive this upgrade, mail Leading Edge at the address below, and include the model number of the computer and a money order for $45.00.  The upgrade is also available through Leading Edge distributors (usually at a higher cost than purchasing directly through Leading Edge.)

If version 3.11 is causing the problem, there is no "downgrade" currently available.  A future release of Phoenix BIOS for the Leading Edge XT might provide compatibility.

Leading Edge Products

Technical Support

117 Flanders Road

Westborough, MA 01581

Leading Edge technical support number: (508) 836-4800

This information applies to MS-DOS version 5.0.


Parity Error
Problem:   Parity Error - Try /NE To Isolate Problem.

When trying to start WordPerfect, a parity error with a question mark (?) for the address occurs.

Solution:

When the using the /NE startup option, WP will run without any problems.  The BIOS doesn't display addresses of parity errors above 1M since memory is mappable to any address above 1M.  Therefore, displaying an address could be more misleading than helpful.     By using /NE WP wouldn't be using expanded memory, and the memory problem wouldn't be an issue.  There are many memory test utilities to help you isolate such failures.


CRTL+P without a Printer
Problem:  CRTL+P typed without printer

If CTRL+P is typed, and there is no printer attached to the system, the system hangs.  Is this a problem with the hardware not being able to tell if the printer is hooked up, or is this a problem with MS-DOS?

Solution:

The system does not actually hang.  If you wait long enough -- it may be 20-30 minutes -- control will eventually be passed to the MS-DOS Interrupt 24H critical error handler.

This is a hardware problem, not a problem with MS-DOS.  The status lines in the IBM (and many compatible) printer adapter are allowed to float, so the printer adapter can't tell if the printer is there or not.  The real problem is in the ROM BIOS.  It takes the ROM BIOS Interrupt 17H too long to time-out-- about one minute.  The MS-DOS Interrupt 24H message is also getting echoed to the printer, putting it back in the same time-out loop, so it takes about one minute per character to print the error message.  This is basically a hardware/ROM BIOS flaw of the ROM BIOS taking too long to time-out.

To resolve this problem, when it has been determined that the printer hasn't been hooked up, the ROM BIOS should time-out immediately.


Hard Disks With More Than 1024 Cylinders
Problem:  Hard disks with more than 1024 cylinders

Systems with hard disks with more than 1024 cylinders will not be able to use the entire drive with a standard ROM BIOS or with a generic MS-DOS packaged product or the Microsoft MS-DOS 5 Upgrade.  This is because the default IBM-PC ROM BIOS can only comprehend disks that have 1024 or fewer cylinders. Microsoft MS-DOS relies on an IBM-compatible ROM BIOS to communicate with the system hardware, and thus cannot understand disks that the ROM BIOS cannot understand.

This information applies to Microsoft MS-DOS versions 2.x, 3.x, 4.x, 5.0, and 5.0a.

Explanation:

The design of the IBM ROM BIOS disk interface did not anticipate disks with more than 1024 cylinders.  The ROM BIOS Interrupt 13H disk interface has a standard register interface in which the cylinder number of a disk is partly contained in two different registers: the 8-bit CH register contains the low-order 8 bits of the cylinder number, and the 8-bit CL register contains the high-order 2 bits of the cylinder number.  When combined, this creates a 10-bit cylinder number, zero based, thus giving the upper limit of 1024 (0 to 1023).

For OEM ROM BIOS extensions, refer to your OEM hardware technical reference manuals.


Floppy Drives and BIOS
Problem:  Determining the number and type of floppy drives from ROM BIOS

MS-DOS determines the number and type of floppy drives on a system using the ROM BIOS services, called interrupts.  The MS-DOS DEBUG utility can be used to "ask" the ROM BIOS for this information directly.  This is helpful in determining why MS-DOS may not be accessing a floppy drive or drives correctly.

It is possible that one version of MS-DOS might access a drive and another version may not.  Some hardware manufacturers modify their MS-DOS to ignore the information returned from the ROM BIOS and rely on vendor-specific information about the drives.

Early versions of Microsoft MS-DOS make assumptions about the existence of one or more floppy drives that might, coincidentally, be correct.  However, in Microsoft MS-DOS versions 4.0 and later, MS-DOS correctly relies on the information reported by the ROM BIOS.

The following procedure uses function 8 of interrupt 13 to determine disk parameters.  The number of sectors per track and tracks is returned, which correlates between the information returned and the parameters MS-DOS uses for the FORMAT utility.  On AT and PS/2 systems, a drive type code is returned as well.

If the BIOS is not returning the correct drive information on an AT or PS/2 machine, it may indicate that the drive type has not been set properly in the CMOS setup.  On any machine, it may indicate that the drive is not properly installed, or that the drive is not supported by the ROM BIOS.  For information about your ROM BIOS and whether you need to upgrade, contact your machine or BIOS manufacturer.

This information applies to MS-DOS versions 3.2, 3.21, 3.3, 3.3a, 4.0, 4.01, 4.01a, and 5.0 and to the PC, PC/XT, PC/AT, and PS/2 BIOS.

Explanation:

To start the DEBUG utility, type "debug" (without the quotation marks) at the command prompt and press ENTER.  If at any time you wish to exit and start over, use the Q[uit] command to exit back to MS-DOS.  It is recommended that DEBUG not be used when other programs are active or in a multitasking environment such as Microsoft Windows.

DEBUG

Displays	Enter	To

a 100	Begin entering commands at address 100 XXXX:0100

int 13	Do an interrupt 13

XXXX:0102

int 20	An interrupt 20 here (insurance)

XXXX:0104

ENTER	Press ENTER here-

rip	Display and modify the IP register IP

XXXX:0100

Begin executing at 100-

rax	Display and modify AX register

AX 0000 :

0800	Function 8 (get drive information)-

rdx	Display and modify DX register DX 0000 :

drive	Enter 0 for first floppy, 1 for second, etc.

p	Process

At this point, DEBUG will execute the command at 0100, interrupt 13.  The ROM BIOS routine will process interrupt 13, function 8, on the drive you specified, and return some information in the registers.  DEBUG will display something like this:

AX=0000  BX=0002  CX=4F0F  DX=0102  SP=FFEE  BP=0000  SI=0000  DI=2115 DS=0E77  ES=F000  SS=0E77  CS=0E77  IP=0102   OV UP EI NG NZ NA PO NC 0E77:0102 CD20          INT     20

The name of each register is displayed, along with its current value.  All values are in hexadecimal.  Note that each X register can also be addressed by its "high" and "low" halves; that is, if CX=4F0F, CH=4F and CL=0F.

The flags register is displayed differently.  The status of the flags register is the series of two-letter codes at the end of the second line. Note the value of the last flag on the second line.  If it is CY (CarrY), the carry flag was set by the BIOS, which means the interrupt failed.  In this case, AX= an error value.  See page 54 of the "IBM ROM BIOS Quick Reference" guide for information about these errors.  If the last flag is NC (no carry), the carry flag was not set, which indicates that the interrupt worked correctly.

On AT and PS/2 systems, the low byte of the BX register (BL) will contain the drive type 01 if 360, 02 if 1.2, 03 if 720, and 04 if 1.44.

The maximum value for the last track on the drive is stored in CH: 27 hexadecimal (39 decimal) if there are 40 tracks maximum, or 4Fh (79d) if there are 80 tracks.  The maximum sector number is stored in CL: 9h (9d), Fh (15d), 12h (18d), or 24h (36d).  Finally, the maximum head number is stored in DH; because floppies have two heads, this is 1. (The ROM BIOS numbers heads and tracks, or cylinders, from 0, and sectors from 1.)

Finally, DL indicates the number of floppy drives.  Note that the value returned in DL (number of drives) is the number of floppy drives attached to the disk controller for the specified drive.  Normally, there is only one controller, and thus DL=the total number of floppies.  However, if floppies A and B are attached to different controllers, then DL=1 will be returned for each.

So, from the previous example (values unrelated to the drive type are indicated by xx):

AX=xxxx  BX=xx02  CX=4F0F  DX=0102  SP=xxxx  BP=xxxx  SI=xxxx  DI=xxxx DS=xxxx  ES=xxxx  SS=xxxx  CS=xxxx  IP=xxxx   xx xx xx xx xx xx xx NC xxxx:xxxx xxxx          xxx     xx

NC, so no error; BL = 02, so 1.2 MB; CH=4F, or 80 tracks; CL=0F, or 15 sectors per track; DX=01, or 2 heads; DL=2, two drives.  All of which indicates that there are two drives on this system, and this particular floppy drive is 1.2 MB.

Reference(s):

"IBM ROM BIOS Quick Reference," Ray Duncan.  Microsoft Press.

"QUE DOS Programmer's Reference," Terry Dettman.  QUE Corporation.


Communications Problems

This section includes any modem hardware installed including FAX modems.

Specific Conflicts

~Diamond Stealth video card and Fax-modem .


Keyboard Problems

Specific Conflicts

~Erratic keyboard behavior

~Keyboard Problems After Upgrading to MS-DOS


Erratic Keyboard Behavior
Problem:  Erratic keyboard behavior

You may encounter erratic keyboard behavior when using the MS-DOS 5.0 HIMEM.SYS driver on certain systems.  Symptoms may include a variety of problems interpreting the state of the SHIFT, CAPS LOCK, NUM LOCK, ALT, and CTRL keys.

If you encounter this kind of problem, setting the /CPUCLOCK: switch to ON may alleviate the problem.  If not, use the HIMEM /machine:xxxx switch to specify an alternative value for the A20 handler.  Switches which have been found to be most likely are 11, 12, and 13 (in that order).  These switches represent progressively longer delays in the switch state of the A20 line compared to the default handler 1.

This information applies to Microsoft MS-DOS version 5.0.

Explanation:

Another workaround is to add line below

c:\dos\keyb us

c:\dos\keyboard.sys

in your AUTOEXEC.BAT file with a text editor like Notepad.  This replaces the ROM BIOS INT 09h keyboard interrupt handler with its own routine.  This may allow handling of the keyboard in a manner that does not conflict with A20 handling.


Mouse Problems

The mouse controls the pointer on the screen.

Specific Conflicts

~Windows 3.0 and Bus Mouse

~Bus Mouse Used Before Serial Mouse

~MOUSE.COM Conflicts with Word 5.0


Hardware Interrupt Conflicts
Problem:  Hardware Interrupt Conflicts

When installing Microsoft Windows version 3.00 on a system with a bus mouse, you may get the following message:

Problem with disk drive C: Please check that the diskette is properly inserted in the disk drive and the door is closed.

A hardware interrupt conflict with the hard disk controller and a bus mouse set to IRQ2 can cause this message.  Many AT and 386 computers use interrupt 2 (IRQ2) to communicate with the hard disk drive.  If your mouse hardware is also on this interrupt, you may have interrupt conflicts.  Some examples of mouse hardware that can cause interrupt conflicts are as follows:

A bus mouse card set for IRQ2 -

A built-in mouse port on the motherboard that is

A video card with a built-in mouse port that is configured for IRQ2 such as the ATI VIP VGA

Solution:

Reassign the mouse to an unused interrupt.  Do this by resetting the jumpers on the bus card, or by using the software setup program for the mouse.  The owner's manual of the hardware causing the problem should list the proper steps to change the IRQ.


Bus Mouse Used Before Serial Mouse
Problem:  Bus mouse used before serial mouse.

On a system with both a Logitech bus mouse and a Microsoft serial mouse connected, the Logitech bus mouse is the functioning pointer.  This is after installing Windows and selecting Microsoft Bus or Serial Mouse from the pointer device section.

Solution:

The Logitech bus mouse uses the same driver as the Microsoft bus mouse. When you make the Microsoft selection, Windows finds the bus mouse and installs it.  The only workaround is to physically remove the bus mouse card from the computer.

The way the mouse driver  works in Windows, is when loaded it searches for the bus card first, then COM2 followed by COM1.  This explains why the Logitech mouse is active after loading Windows.


MOUSE.COM Conflicts with Word 5.0
Problem:  MOUSE.COM Conflicts with Word 5.0

Microsoft has confirmed that a problem exists with the Microsoft MOUSE.COM version 7.00.  You may have difficulty running Word version 5.00 under Microsoft Windows 286 versions 2.x,  Windows 386 versions 2.x, and Windows version 3.00 after loading MOUSE.COM in DOS.

Solution:

Microsoft is researching this problem and will post new information as it becomes available.

A  workaround for this is to Upgrade to MOUSE.COM version 7.04.  Note this file is included with Microsoft Windows version 3.00.  The easiest method of determining the version of the mouse  driver  is to reboot the machine.  The mouse  driver  version is displayed when it is installed.


Video Problems

Problems with the display caused by the video card or monitor are covered in this section.

Symptoms:

Some symptoms of problems with video boards are:

1.  The Setup program freezes during Disk #2 when installing Windows.  This is the point when it would normally switch to graphics mode to complete the installation.

2.  After installing Windows, you cannot start Windows in standard or 386 Enhanced mode.

3.  The display is full of snow or the colors are wrong when Windows is started.  This exists even if they are set correctly in Control Panel.

4.  DOS applications started under Windows abort, or Windows terminates them with a "This application has violated system integrity" message.

Causes:

The most common sources of video adapter is the memory space that these adapters claim.  Video adapters may have 512K, 1MB or more of video memory.  This video memory is in addition to, and separate from, the 640K of conventional memory that all PCs are capable of supporting. It is also separate from a PC's expanded memory and extended memory.  Video memory must be provided with its own address space.  This address space begins exactly where the 640K of conventional RAM ends.

Problems arise because video adapters may occupy a block of memory that Windows cannot detect.  When Windows starts, it examines all the memory locations in the Upper Memory Blocks, looking for holes that it can fill with memory for running Windows applications.  Windows avoids memory locations that appear to be occupied by a device.  If a memory location looks free, however, Windows will claim it.  When this location is later required by a device that was dormant (such as a video card), the conflict will eventually cause the screen to hang or fill with garbage.SEE Possible Problems with Memory.

Specific Conflicts

~Paradise VGA Plus and Sony 1302

~Problem with Tutorial and Combined Drivers

~Mode will not switch on a VGA monitor

~Display Problem on Epson 386SX and 286 Laptops

~Windows Setup conflicts with video hardware

~VGA and EGA Driver Problems with Gradient Fill

~Shadow VGA Card and DOS Graphics Capture

~Running true color at high resolution ruins displayed icons.

~Diamond Stealth video card and Fax-modem .

~Color changes with an 8514/a adapter with VGA passthrough.

~8514/a adapters and VGA monitors.

~Bottom part of screen image is gone.

~Monitor flickers at 1024x768.

~LCD displays on Laptop don't display text

with applications

~Excel 3.0 and Fahrenheit 1280 Orchid

~Using Excel 3.0 with 8514 Video Driver

~Converting 256-Color Paintbrush files to 16-Colors

~Monochrome Display with 123W Multimedia SmartHelp

See Also

General Information on Memory

Possible Problems with Memory


GPF or Systems Errors when you run in 256 colors or more.
Problem:  GPF or Windows Systems Errors when you run in 256 colors or more.

Solution:

Your graphics device driver is probably not the proper one.  Make sure you are running a driver for Windows 3.1.  A driver for Windows 3.0 are unstable when used with Windows 3.1.

Another possibility is that your graphics device doesn't support more than 16 colors in VGA (640 x 480) resolution.  To support VGA resolution a card must have at least 512K of video RAM (VRAM).  This video RAM is not the same as system RAM.  Devices with 256K of VRAM can display 256 colors only in MCGA mode, which only has a resolution of 320 x 200 pixels.

A defective copy of the driver may be installed on your system.  Either reinstall or contact the manufacturer of the board for the latest version of the driver.

If you are using a memory manager SEE Possible Problems with MemoryPRZ_HRD_MEM_GENPROB.

For more information see the README.WRI located in your Windows directory.


LCD displays on Laptop don't display text
Problem:  LCD displays on Laptop don't display text

When using a LapTop computer with an LCD display the text doesn't display on the status bar. Unlike the other problems with wrong fonts being selected, there appears to be no text at all in the status bar, though the boxes are drawn and the goto record works."

Solution:

Apparently this is a color problem. There are three selections in the control panel colors, default color schemes, which are specifically for LCD monitors. Try all 3 and see which one is preferred. One at least should bring back the text.


Monitor flickers at 1024x768
Problem:  Monitor flickers at 1024x768.

Solution:

If your adapter and monitor are working at a vertical refresh rate of 60Hz or lower, there will be noticeable flicker.  This is possibly because your adapter or monitor is only capable of diaplaying at an interlaced 1024x768 resolution.  Check to see if your adapter and monitor can operate at higher vertical rates, preferably noninterlaced, then make the necessary adjustments to either your monitor or card.


Bottom part of the screen image is gone.
Problem:  Bottom part of screen image is gone.

Solution:

Check your video adapter.  You may be using a 640x400 adapter with a 640x480 driver.  Some laptops run only at 640x400.

If this doesn't work then a portion of your video RAM may be bad.  First check to see if the RAM on your video card is seated properly.  Open your system and carefully remove your video card.  Check to see if the video memory chips are socketed or soldered.  If they're socketed, you can try carefully pressing down on the chips to reseat them.  If, as you pushed the chips back in, you felt them pop back into place, chances are good that you have fixed your problem.  If this doesn't work you may have to end the card back for repair.


8514/A adapters and VGA monitors.
Problem:  8514/a adapters and VGA monitors.

8514/a adapters are not compatible with VGA monitors.  When you boot up, you won't see anything.

Solution:

You either need a separate VGA adapter or a VGA piggyback module.  The separate VGA adapter must be connected to the 8514/a card with a VGA pass-through cable.  The VGA piggyback module only works if your board has a connector for it.

If you have already installed either a piggyback module or a passthrough cable, check to make sure that the piggyback module is seated properly and that the passthrough cable is connected correctly.  Next, take a look at the monitor jacks oon your video card(s):  the VGA card should have a terminator and your monitor cable should be attached to your 8514/a card.  Also, check to be sure that the upper memory addresses used by the VGA card and your 8514/a adapter are excluded in both your UMB provider (like EMM386 or QEMM) and the Windows SYSTEM.INI file.

If the system is up and running and then see a blank display when starting a Windowed DOS task, you may need a digital-to-analog convertor (DAC) upgrade for your VGA.


Color changes with an 8514/A Adapter and VGA passthrough.
Problem:  Color changes with an 8514/a adapter with VGA passthrough.

Solution:

The 8514/a board may be sharing its hardware video palette with the VGA card connected by the passthrough cable.  It is possible for a Windows app to change the color of a Windowed DOS app while the Windows app runs in the background, or vice versa.


Stealth video card and FAX-modem on COM4 clash.
Problem:  Diamond Stealth video card and Fax-modem on COM4 clash.

Solution:

S3's chips (the 801, 805, 911, 924, and 928) use the same I/O address as COM4 (2E8).  The same problem crops up with ATI's graphics cards.  Without going into the details, you have two choices.  First, if your graphics card lets you change its I/O mapping, do so (be sure to pick an unused address).  Second, switch your modem to a different COM port.


Running true color at high resolution ruins icons.
Problems:  Running true color at high resolution ruins displayed icons.

Even with plenty of system memory, Windows will have trouble handling true color.  Program Manager stores icons at the same pixel depth as the display device.  Running in true color mode, or 24-bit mode, you will need more icon memory.  The amount of memory allocated for icon storage is limited and in deep color modes you can run out of space if you have more than 16 or 17 icons in a group.

Solutions:

Break your larger program groups into smaller ones, and those wiped out icons will magically return.


Paradise VGA Plus and Sony1302
Problem:  Paradise VGA Plus and Sony 1302 Multisync monitor

It has been reported that the Paradise VGA Plus card with ROM number 62-003060-063 dated WDC '88 has a problem with a Sony 1302 Multisync monitor. Apparently there is a problem with some, primarily older, multisync or multiscan monitors (including the original NEC Multisync monitor) that causes text to be printed beyond the bottom of the screen in graphics mode.

Solution:

According to Western Digital (Paradise), this problem is caused by the lack of automatic vertical page sizing hardware in the monitor.  There is a newer ROM revision that will partially solve this problem, but there is no complete solution in software.

For further information and ROM upgrade, contact Western Digital Corporation at (415) 960-3353.


Problems with Tutorial and Combined Drivers
Problem:  Problem with Tutorial and Combined Drivers.

When attempting to use the Tutorial choosing a combined  driver  (graphs and text together) in the Install Program, the error message "The Tutorial cannot be used with this  driver  set" will result.

Solution:

Any driver  (used in combined mode) that gives resolution greater than 80x25 cannot be used with the Tutorial.  To correct this problem, you should choose separate mode (graphs and text separate).  To date, this problem has been reported with the Symphony 1.2 3.5" version - the drivers for the PS/2's give 80x38 resolution.  Currently, the Hercules 90x38 driver is the only driver  with documentation informing you that they cannot use the Tutorial.


Mode will not switch on VGA monitor
Problem:  Mode will not switch on a VGA monitor

When using a VGA monitor capable of 43 and 50 line mode, the message "Function not supported on this computer" after typing "mode con:lines=50."

Solution:

The Mode command utilizes the ANSI.SYS  device driver  when changing video modes.  Before ANSI.SYS changes to 43 or 50 line mode, it inspects the current video mode.  If ANSI.SYS does not recognize the current video mode as a standard VGA mode, this error message is displayed.

If the video card can be set into a standard VGA mode, the Mode command to change to 43 or 50 line mode will be successful.

ANSI.SYS checks the current video mode before changing to 43 or 50 line mode to prevent possible video conflicts.  If the video card were in a non-standard VGA mode before changing to 43 or 50 line mode, it could leave the video in a unknown state.


Display Problem on Epson 386SX and 286 Laptop
Problem:  Display Problem on Epson 386SX and 286 Laptops

You may experience video display problems when you run Microsoft Windows version 3.0 on your Epson 286 or 386SX laptop.  Windows may appear to extend past the boundaries of the monitor.  This problem usually occurs when you use the built-in LCD display, but may also occur if you are connected to an external EGA or VGA monitor.

Solution:

Epson has a Windows video  device driver , called LTWIN.DRV, that corrects this problem.  This device driver  is available from Epson dealers or the Epson technical support bulletin board at (213) 782-4531.

This  driver  is only for the LT386SX machine.  It is used to correct display problems with Windows 386, Windows 3.0, and OS/2 version 1.1.  The  driver  is available on CompuServe forums for Windows and Epson.  The  driver  file is self-extracting with readme files.

Reference:   Epson, technical support, (800) 922-8911


Setup Conflicts with Video Hardware
Problem:  Setup conflicts with video hardware

On certain machines, Setup can conflict with the video hardware and display a partial, scrambled, or condensed screen.

Solution:

To work around this problem, attempt to print the screen by pressing the SHIFT+PRINT SCREEN keys.  If the printout shows a readable screen, the Setup program can be completed by printing each screen as it appears and following the instructions on the printouts.

Explanation:

On certain machines, it may be necessary to use a key combination other than SHIFT+PRINT SCREEN.  Possible combinations include CONTROL+PRINT SCREEN or PRINT SCREEN by itself.  CAUTION: Other key combinations can toggle printer echoing of the screen output.

This workaround may not work on some machines because of different PRINT SCREEN interrupt handlers or corrupted video memory.

This information applies to MS-DOS version 5.0.


VGA and EGA Driver Problems with Gradient Fill
Problem:  VGA and EGA Driver Problems with Gradient Fill

There is a problem in the EGA and VGA drivers shipped with Windows/286 Version 2.10 that causes a system hang when performing a gradient fill (otherwise known as a fountain fill or radial fill) with certain color combinations.

Solution:

Microsoft has confirmed this to be a problem in Version 2.10.  This problem was corrected in Windows Version 2.11.  The problem has been reported to occur only in Micrografx Designer and Corel Draw, although it could conceivably affect other applications that perform fountain fills, such as Xerox Presents.


Shadow VGA Card and DOS Graphics Capture
Problem:  Shadow VGA Card and DOS Graphics Capture

You cannot copy graphics from DOS applications to the Clipboard when you use the Ground Hog Graphics 1 MB Shadow VGA card with Microsoft Windows version 3.00.  Pressing either ALT+PRINT SCREEN or PRINT SCREEN will NOT copy VGA, EGA, or CGA graphics to the Clipboard.  You can capture text to the Clipboard.  This problem occurs with ALL Ground Hog drivers regardless of the video mode.

Solution:

A workaround is to use the standard Microsoft VGA  driver .  Ground Hog Graphics is researching this limitation and is working on solutions to this problem.  Any questions regarding updates to the drivers should be made to Ground Hog Graphics.


Converting 256-Color Paintbrush Files to 16_Color
Problem:  Converting 256-Color Paintbrush files to 16-Colors

The Microsoft Windows version 3.00 Paintbrush program can display pictures in 16 colors with most video adapters.  Video adapters, such as the IBM 8514/A and Video Seven 256-color  driver , allow Paintbrush to display 256-color pictures.  If Windows is using a 256-color  driver , files will be saved in a 256-color format.  Applications such as Microsoft Word for DOS version 5.00 don't recognize pictures in the 256-color format and will be unable to use pictures in that format.

Solution:

To convert these pictures to a 16-color format, do the following:

1.  Run Windows Setup and install the standard VGA  driver .

2.  Restart Windows and run the Paintbrush application.

3.  Load the 256-color files and then save them in the .PCX format.  This will save 	them in a format Word 5.00 can read.

4.  If necessary, go back to Windows Setup and reinstall the original video  driver  	and restart Windows.

In normal VGA resolution, Paintbrush can display and save files in 16 colors only.  Saving a 256-color file while you have a 16-color  driver  loaded will convert that file to a 16-color format.  Once a 256-color picture is saved in 16-colors, Paintbrush will be unable to convert the picture back to the 256-color format.


Sound Problems

Problems with any sound hardware are addressed in this section.  Problems with recording and playing sound files are also covered here.

Specific Problems...

with Recording or Playing of Sound

~Sound Files play in a loop, stop playing early, or don't play.

~"Format not Supported" error occurs when a sound file is played.

~Digital audio skips at higher sampling rates.

~Can't record anything.

~Recorded or passed-through audio is raspy and distorted.

~Recordings have a lot of noise.

~Trouble running Video for Windows movies

with Sound Hardware

~Windows crashes after replacing old sound card with new one.


Trouble running Video for Windows Movies
Problem:  Trouble running Video for Windows movies.

If your sound card has trouble running Video for Windows movies, then your card's device driver needs to be updated.  Contact the card manufacturer to get an updated driver.


Sound Files play in a loop, stop playing early or don't play.
Problem:  Sound Files play in a loop, stop playing early, or don't play.

Solution:

These symptoms suggest an audio board that is confused.  This could be caused by a number of problems.  The first thing to check is the software that came bundled with your sound card.  Check the settings on audio mixer applet (on the sound board's install disks).

The master volume set by the mixer's sliders should be set at its midpoint or higher, as should the slider controlling your board's digital audio output (usually labeled "wave").  Check to make sure the output is not set to "mute," and that the wave channel is not set to record mode.  If your mixer does not have some of these settings, just check the ones you have.  Test the mixer settings using one of hte sound included with Windows.  Pop up the Media Player or the Sound setting in the Control Panel to play some audio while you adjust the mixer to get the perfect volume.

If the mixer checks out okay, pop up the Drivers setting in Control Panel and check out your driver and software settings.  Both sound board and MCI digital audio drivers must be listed.  The master hardware driver probably has a name like "Wave/MIDI/FM."  Check the board's hardware settings against what Windows displays in the setup dialog box.

If the setting match up but your sound board is still not functioning properly, you probably have a port, DMA or interrupt conflict.  Most boards have a DOS configuration utility that verifies the board's settings.  Some boards are software configurable, meaning the configuration utility can also change the settings.  If, even after a successful test run in the configuration utility, the board is still not functioning properly, you will have to begin using different combinations of IRQs, DMAs and port addresses until you hit the right combination.

When Windows and your board are in commmunication they talk back and forth through the I/O port only.  That means that if you get the port right, but the IRQ or DMA is wrong, there won't be any error messages, but there also won't be any sound.  A symptom of a good port setting and a bad IRQ or DMA is a lockup when you exit Windows, especially when you have selected a Shutdown sound.


."Format not Supported" error occurs when a sound file is played.
Problem: "Format not Supported" error occurs when a sound file is played.

Solution:

This occurs when the sound file was recorded using some method or combindation of settings that your sound card doesn't support.  An 8-bit sound board won't play 16-bit files, and boards that max out a 22kHz won't play 44 kHz files.  Try resampling these files to a sample rate and resolution using Wave for Windows or some other sound editor.

Another possible cause is that the file was recorded by a board that uses hardware data compression.  The sound board vendor may have a new driver that deciphers compressed files in software.  The manufacturer's Tech Support may be able to supply a simple software fix.


Digital audio skips at higher sampling rates.
Problem:  Digital audio skips at higher sampling rates.

At 16-bit, 44kHz, or "CD quality," your system has to move a steady stream of 176,400 bytes per second per bus, which, by itself, is not very taxing.  The problem lies in providing this capacity for an unbroken length of time.

Skipping audio is a symptom of something interfering with your audio data stream.  A DMA channel conflict might be the culprit, but it is more likely thay your system isn't able to keep up with the data rate.

Solution:

To confirm this, record and play a long (60 seconds or more) clip at a lower sampling rate, like 22kHz.  If the this sample doesn't skip, try defragmenting your hard disk with the utility of your choice.  Then, record the clip again at your original (44kHz) sampling rate and play it.  If the sound is still skipping, and if you have a hardware disk cache, try disabling or reducing the size of your disk controller's hardware cache.  A cache might cause imperfect recordings.  Until the cache fills, everything is fine.  The problem occurs when the controller dumps the cache to disk.  Now audio data is still coming in too fast for the controller to juggle.  As a result, some audio data gets lost; most disk controllers won't let you know that there's a problem.

If none of these solutions work, your hardware may be the culprit.  A slow CPU, old hard drive or controller, insufficient memory or sound board may be the cause.


Windows crashes after replacing old sound card with new one.
Problem:  Windows crashes after replacing old sound card with new one.

After upgrading an old sound board with a new card, Windows crashes before the new drivers can be installed.

Solution:

This problems exists because Windows is still referencing the drivers for the old sound adapter, which has been removed.  The best solution is to remove your old drivers before you remove the sound adapter.  The Drivers option under Window's Control Panel allows you to select and remove installed drivers.  Remove the Wave audio driver, an FM synthesis or MIDI dirver, and a mixer driver or an Aux driver.  Don't remove any of hte drivers that begin with [MCI], or the Timer driver.  Now you can safely install the new sound card.

If you've already replaced the sound adapter and now Windows won't start you will have to edit the system configuration information that is stored in the SYSTEM.INI file in the Windows directory.  Before you tinker with the file, make a copy of it (as SYSTEM.BAK or something similar).  Use a text editor to search for the [Drivers] section.  Delete the parameter lines that refer to your old sound card.  The Wave parameter and the MIDI parameter are usually your targets.  A MIDI1 parameter may exist if your card has an external MIDI connector in addition to its built-in synthesizer.  Depending on what sound card you have, there may also be an Aux parameter or a Mixer parameter.


Can't Record
Problem:  Can't record.

Solution:

Open your board's mixer applet and select the "record" button associated witht he Wave, CD Audio or FM synthesizer source.  Make sure the mixer the mixer slider for that input is raised to a reasonable level.  Halfway between the midpoint and full is a good level.

If recording starts and then stops abruptly, you sould check your board and driver settings.  Once again, Windows will think it has a working sound card even if you only have the I/O port address correctly configured.  Check your IRQ and DMA settings.


Recorded or passed-through audio is raspy and distorted.
Problem:  Recorded or passed-through audio is raspy and distorted.

The sound card probably has two external input jacks that are not interchangeable:  mic and line.  The mic input runs through an onboard preamplifier that raises the signal voltage.  If the line output device (a tape recorder, CD player or any other powered audio source) into the mic jack, the signal will be overamplified.  The result is a loud, raspy recording.  The mic input should be used only for microphones.  If you need a second line input, you can use an attenuator to drop a line source down to mic level.


Recordings have a lot of noise.
Problem:  Recordings have a lot of noise.

Solution:

If the recording device has both line and headphone outputs, use the line output to avoid the noise added by the device's headphone amplifier.  If you must record from a headphone jeack, turn the volume up fairly high on th source and clamp the volume down to a usable level with your board's mixer applet.  This will give you a better signal-to-noise ratio.

When you record, make sure you have only the source or sources you want selected for recording activated in the mixer.  If any of the other sources is selected, you may get noise from them even if nothing is playing through them.

Another possibility is a ground problem.  If there is a constant, background hum, check your audio cables and make certain they aren't crossing over any power cords and that they are seated firmly in their sockets.  If there are power cords, move them;  if the plugs are seated correctly, replace the cables (or get your sound card serviced).


Accelerator Card Problems
Accelerator Problems

An accelerator card speeds up the clock speed of the microprocessor of your PC thereby increasing your performance.


Drive Problems

Drives are a means of storing and recalling information.  A variety of different types of drives are available.  Each kind of drive has a different kind of media associated with it.  A drive's mechanism creates the 1s and 0s that record all types of data, from pictures to text.  Reading and writing to your drives is a complicated process that involves the BIOS chip, DOS, and your application software.

All drives need a drive controller card to give the PC access to the drive.

SEE

CD_ROM

  CD-ROMs are optical drives.  This means that data is read by a laser rather than a magnetic head.  Because of their immense storage capacity, CD-ROMs have become the media for multimedia software.  As the access times and data transfer rates of CD-ROMs improve, you can expect even software distribution to one day be done through CDs.

FLOPPY

  Floppy disks are a ubiquitous form of permanent data storage.  They are also the most commonly used form of file transfer, even with the existence of high speed network systems.  This section includes the problems with this media.

HARD DRIVE

  Hard drives are the internal means of permanent data storage on PCs.  Hard drives are the best data storage solution.  They can store large quantites of data, retrieve data quickly, and cost is low on a price-per-megabyte basis.

TAPE

  Tape drives provide a nearly inexhaustible off line storage mechanism, but they are too slow to use for any purpose beyond backup.

NETWORK

  Network file servers are a means of having a centralized storage area for data with quick and easy access for all users of the network.  File servers usually have one or more large capacity hard drives.

CONTROLLERS

  Drive controllers are cards that give the PC access to some types of hard drives.  MFM drives or ST506 drives require a controller cards.


CD-ROM Problems
CD-ROM Drive Problems

CD-ROM stands for Compact Disk Read Only Memory.  These are optical drives meaning they are read by a laser rather than by a magnetic head as in other kinds of drives.  These drives are useful for storing great quantities of information, more than even hard drives.

Specific Problems

Video playback is jerky and/or the sound breaks up.


Video playback is jerky and/or the sound breaks up.
Problem:  Video playback is jerky and/or the sound breaks up.

Solution:

The data rate you chose may be too fast for your CD-ROM.  If your drive has an average data transfer rate of 150 KB per second, but you are using a movie data rate of 300, your CD-ROM will be incapable of reading the frames off the CD fast enough.

When using Video for Windows, VFW will try to play the audio without interruption, but video frames may be dropped.  This causes the jerkiness of the video.  The sound may also break up if Video for Windows can't keep up with the audio.


Floppy Disk Drive Problems

Floppy Disks come in either 3.5" or 5 1/4" size.


Tape Drive Problems

Tape drives are generally used as a backup method for other types of drives.

Specific Conflicts

~Colorado Tape Backup and EMM386


Colorado Tape Backup + EMM386
Problem:  EMM386 Conflicts with Colorado Tape Backup

Colorado Tape Backup Systems FC10 (8-bit) and TC15 (16-bit) internal tape cards may conflict with EMM386.EXE.  Symptoms include intermittent memory conflicts, system hangs when EMM386.EXE attempts to install, and the inability to access upper memory blocks (UMBs).

This information applies to Microsoft MS-DOS version 5.0.

Explanation:

The FC10 and TC15 tape backup cards come with an installation program that automatically assigns an open hardware interrupt (IRQ) and memory address. The selected memory address may conflict with EMM386.EXE.

Solution:

To work around this possible conflict, try one of the following:

- Manually change the address through the tape backup card installation software.

-or-

- Exclude the appropriate memory address on the EMM386.EXE line.  For example:

 device=c:\dos\emm386.exe  x=d000-dfff


Hard Drive Problems

Hard drives are used for storing large quantities of information.  Their capacity is not as great as that of CD-ROMs, but they have much greater capacity than floppies.

Some of the most common drive standards are listed below:

ST506--These drives became the most common interface type among all PC manufacturers during the early years of the industry.  ST506 drives use Modified Frequency Modulation, a digital recording method, and are known as MFM drives.  These drives require a separate controller board.  SEE Drive Controllers.

ESDI--Enhanced Small Device Interface drives upgrade the ST506 standard by allowing a typical data transfer rate of 10 million bits-per-second, compared to the 5 million of the ST506 interface.  The difference is achieved by storing data at twice the density of the ST506 drives.

SCSI--Small Computer System Interface (pronounced scuzzy) use their own expansion bus to communicate with he computer system.  This "bus" is typically a cable, connected to an interface in the PC, to which several different SCSI devices may be attached.  SCSI drives often have higher capacity and better performance than the other types.

IDE--Integrated Drive Electronics drives are a crossbreed between drive controller cards and the drives.  All the controller circuitry necessary for communications with the computer system right on the drive itself.  This requires less circuitry inside the PC so this technology lends itself to smaller PCs and portables.

General Information

~Partitioning Summary

~Using CHKDSK and UNDELETE

Specific Conflicts

~No active partition selected

~Improper Uninstall of Primary Boot Sector

~Nonstandard drives and Windows 386 Enhanced Mode


Nonstandard drives and Windows 386 Enhanced Mode
Problem:  Nonstandard drives and Windows 386 Enhanced Mode

Error messages such as:

Drive C:  Not Ready Error

Cannot Read for Drive C:

Cannot Write to Drive C:

indicate that Windows is having some trouble with a nonstandard drive.

Solution:

Insure the maximum compatibility with drives of all types by setting SYSTEM.INI so Windows is forced to perform all read and write request through the ROM BIOS chip in the computer system instead of handling the hard disk controller itself.  This is done with the following line in SYSTEM.INI:

[386Enh]

VirtualHDIRQ=Off

This statement results in a slow down of disk accesses, but does give better compatibility with nonstandard drives.

If your hard drive still does not work with Windows, there may be some problem with he BIOS and drive in you particular configuration that would prevent it from working reliably with DOS applications as well.


No Active Partition Selected
Problem:  No active partition selected on hard drive

After partitioning the hard drive and installing MS-DOS  the messages "NO ROM BASIC" and "SYSTEM HALTED" are displayed.

Solution:

In addition to partitioning the hard drive you must select an active partition.  This can be done through the Set Active Partition option on the FDISK main menu.  The only MS-DOS partition that can be set active is the primary DOS partition.

Explanation:

When the computer is started, the boot routine polls drive A for a valid boot disk.  If no boot disk is detected, the system will read the boot sector from the first physical hard drive.  The partition table is examined for a partition with a boot indicator.  If no partitions are marked as bootable, the system executes an interrupt 18H, which transfers control to ROM Basic.

Only IBM personal computers have Basic included in ROM; on a compatible, interrupt 18H typically displays the message "NO ROM BASIC," then "SYSTEM HALTED," and the system halts.  Under these conditions, some older COMPAQ DESKPRO computers will display the message:

Non-System disk or disk error replace and strike any key when ready.


Partitioning
Summary:  The following is a summary of MS-DOS partitioning.

This information applies to MS-DOS versions 2.x, 3.x, 4.x, 5.0, and 5.0a.

Explanation:

A hard disk's master boot record (MBR) is located in the first sector of the disk (cylinder 0, side 0, sector 1).  The partition table is located at offset 01BE, containing up to four 16-byte entries.  The fourth byte of each partition table entry is used to mark the partition type.

MS-DOS began supporting hard disks in version 2.0.  In MS-DOS versions 2.x, MS-DOS supports one type 01 partition of up to 32 megabytes (MB) in size, which use a 12-bit file allocation table (FAT).  FDISK creates only one MS-DOS partition per drive.

In MS-DOS 3.0, partitions larger than 15 MB use a 16-bit FAT, which allows a smaller cluster size and thus more efficient disk usage.  As a result, MS-DOS 2.x hard drives larger than 15 MB are incompatible with later versions of MS-DOS.  Again, FDISK creates only one MS-DOS partition per drive.

In version 3.3, MS-DOS introduced support for more than one logical drive per hard disk.  Logical drives are treated as completely separate disks under MS-DOS, even though they may occupy the same physical hard disk.

This was supported by introducing nonbootable MS-DOS partitions known as extended MS-DOS partitions.  FDISK reports these as EXT DOS; other MS-DOS partitions began to be reported as PRI DOS, for primary MS-DOS.  Each primary MS-DOS partition is a logical drive, and extended MS-DOS partitions contain from 1 to 23 logical drives (MS-DOS supports drive letters up to Z).  Logical drives in extended MS-DOS partitions have the same FAT type as a primary MS-DOS partition of the same size.

Only one PRI DOS partition and one EXT DOS partition is allowed per drive. On machines with two physical hard drives, a PRI DOS partition is not required on the second physical disk.  A PRI DOS partition is required on the first physical disk. (MS-DOS would not support more than two physical disks.)

Logical drives larger than 32 MB were introduced in version 4.0.  Full usage of these logical drives requires the MS-DOS program SHARE.EXE to be loaded.

MS-DOS version 5.0 supports the same partitioning strategy as versions 4.x, including FDISK's refusal to create more than one primary MS-DOS partition on a physical disk.  However, because some original equipment manufacturers (OEMs) allow more then one primary MS-DOS partition, MS-DOS 5.0 will support more than one primary MS-DOS partition on a physical disk for compatibility reasons.

MS-DOS 5.0 also supports up to eight physical hard drives.  SHARE.EXE is not required for full large-drive support; this support is included in the MS-DOS kernel.

Note: Many OEMs have changed their MS-DOS to support more than one primary MS-DOS partition, larger type 04 partitions, and/or introduced new partition types.


CHKDSK and UNDELETE Warning
Summary:  CHKDSK and UNDELETE Warning

The Microsoft MS-DOS version 5.0 CHKDSK and UNDELETE commands do not work correctly on logical drives that require 256 sectors to store each copy of the file allocation table (FAT).  Using the MS-DOS version 5.0 CHKDSK command with a /F switch will harm such drives and using UNDELETE will be unpredictable.  Neither command should be used with such drives.

Microsoft has confirmed this to be a problem in MS-DOS version 5.0.  This problem was corrected in MS-DOS version 5.0a.

Explanation:

Drives that require a 256-sector FAT occur when the disk is close to 128 MB, 256 MB, 512 MB, or 1024 MB.  The closeness to these limits increases as the drive size increases.  For example, "close to 128 MB" is within 0.25 MB of 128 MB and "close to 256 MB" is within 0.74 MB of 256 MB.  However, due to the nature of the problems involved, the danger ranges below include a margin for error:

127 MB - 129 MB

254 MB - 258 MB

508 MB - 516 MB

1018 MB - 1030 MB

2035 MB - 2061 MB

Logical drive sizes are determined as reported by FDISK.

If the partition is on the edge of the range AND CHKDSK /F has been used on the drive in the past, all is well.  If the partition is in the range and CHKDSK /F has not been used, you should obtain a copy of MS-DOS 5.0a.  DO NOT use CHKDSK /F as a test.

If the drive is in a state where running CHKDSK /F or UNDELETE would be desirable but the drive is within one of the danger ranges above, or the drive is not within the ranges above but CHKDSK /F or UNDELETE has caused unexplained results, the procedure described below can be used to determine if the drive has a 256-sector FAT.

The following procedure uses the MS-DOS Debug utility to determine how many sectors are used for each FAT.  If the number of sectors per FAT is 256 decimal (100 in hex), then MS-DOS 5.0a is required in order to safely use CHKDSK /F and UNDELETE on that logical drive.  The procedure uses MS-DOS function 440D of interrupt 21 to request information about the default drive. The number of sectors per FAT is returned in hexadecimal.

To start the Debug utility, type "debug" (without the quotation marks) at the command prompt and press ENTER.  If at any time you want to exit and start over, use the Q[uit] command to exit back to MS-DOS.  It is strongly recommended that Debug not be used when other programs are active or in a multitasking environment such as Microsoft Windows.

Debug will begin executing the command at 0100, which is interrupt 21. MS-DOS will process interrupt 21, function 440D on the drive specified and will return either the drive information or an error.  DEBUG will display something similar to:

AX=001D BX=0000 CX=0860 DX=0200 SP=FFEE BP=0000 SI=0000 DI=0000   DS=1D93 ES=1D93 SS=1D93 CS=1D93 IP=0102 NV UP EI PL NZ NA PO NC   1D93:0102 CD20   INT   20

The name of each register (AX, BX, IP, and so on) is displayed along with its current value.  All values are in hexadecimal.

The flags register is displayed differently.  The status of the flags register is the series of two-letter codes at the end of the second line. Note the value of the last flag on the second line.  If it is CY (carry), the carry flag was set by MS-DOS, which means the interrupt failed.  In this case, AX= an error value.  See pages 6 and 7 of the "MS-DOS Functions Quick Reference" (see below) for information about these errors.  If the last flag is NC (no carry), the carry flag was not set, which indicates that the interrupt worked correctly.

If all went well (NC is displayed, not CY) MS-DOS has placed the requested information into memory beginning at offset 0200.  This can be displayed using the command:

d 200

This command displays information similar to:

1D93	:0200	00 05 01 00 E9 00 00 00 02 04 01 00 02 00 02 27

1D93	:0210	F0 F8 3C 00 21 00 08 00 21 00 00 00 00 00 00 00

1D93	:0220	00 00 00 00 00 00 00 00 00 00 00 00 00 32 00 00

2 1D93	:0230	00 00 00 00 00 00 00 00 00 00 00 00 00 33 00 00

3 1D93	:0240	00 00 00 00 00 00 00 00 00 00 00 00 00 34 00 00

4 1D93	:0250	00 00 00 00 00 00 00 00 00 00 00 00 00 35 00 00

5 1D93	:0260	00 00 00 00 00 00 00 00 00 00 00 00 00 36 00 00

6 1D93	:0270	00 00 00 00 00 00 00 00 00 00 00 00 00 37 00 00

7

The display is in three sections; the far left columns show the particular address in memory being displayed, the center section shows the contents of memory in hexadecimal, and the far right section shows the contents of memory displayed as text (nonprintable characters are replaced with ".").  In particular, the first columns on the far left (1D93 in the example above) will vary from machine to machine.  The next five columns (:0200 in the first row above) should not vary, however.

To display the particular piece of information we are seeking (the size of each FAT in sectors), use the command:

d 212

If the two 2-digit values at the beginning of the first line of the Debug display are "00 01", then the number of sectors in each FAT is 0100 hexadecimal, or 256 decimal.  NOTE: THE MS-DOS VERSION 5.0 CHKDSK /F COMMAND WILL HARM THIS DRIVE AND THE UNDELETE COMMMAND WILL BE UNPREDICTABLE. Neither utility should be used.

Thus, if the first line produced by "d 212" is

XXXX:0210    00 01 XX XX XX XX-XX XX XX XX XX XX XX XX xxxxxxxxxxx

then CHKDSK and UNDELETE should not be used (X's represent values insignificant to us).  However, if the first line produced by "d 212" is different, for example:

XXXX:0210    FF 00 XX XX XX XX-XX XX XX XX XX XX XX XX  xxxxxxxxxxx

then the MS-DOS 5.0 CHKDSK /F command and the UNDELETE command will work correctly on the drive.


Improper Uninstall of Primary Boot Sector
Problem:  Improper Uninstall of Primary Boot Sector.

The primary DOS partition on a hard disk has its own boot sector that contains information on the format of the partition and the boot strap code. If the Uninstall program does not complete successfully, this boot sector may not be restored, which can cause an error message (for example, "non-system disk error") to be displayed.  The primary partition's boot sector can be restored from the Uninstall disk using Debug.

Note: The partition boot sector is different from the master boot record.

This information applies to Microsoft MS-DOS version 5.0.

Explanation:

The primary partition boot sector describes the partition format and contains boot strap code.  This sector is the first logical sector on the partition. The old primary partition's boot sector is stored in the PBOOT.DAT file on the Uninstall disk.  DOS interrupt 26H (absolute disk write) can be used to write this information back to the first sector of the boot partition.

Note: Use this procedure with caution and only as a last resort.  In most cases, the SYS command will be adequate.

To write the old primary partition boot sector back to the first sector of the boot partition, do the following:

1.  Place the Uninstall disk #1 into drive A.

2.  Start the Debug program by entering the following at the command prompt:

debug a:\pboot.dat

At the hyphen (the Debug prompt), enter the following commands:

Debug	Command Prompt	to Enter	Comments

w cs:100 2 0 1	Write pboot.dat (at cs:100) to

C;	execute the command at cs:ip

q	Exit Debug

The boot sector on the primary DOS partition is now replaced by the boot sector that was there before the MS-DOS 5 Upgrade was installed.


Drive Controller Problems

Controllers are cards that give PCs access to installed drives.  Most of the drives that require controllers are ST506 type drives.

Specific Conflicts

~Tentime SCSI host adapter with MS-DOS 5.0

~EMM386 Conflicts with Adaptec Controller


Tentime SCSI Host Adapter with MS-DOS 5.0
Problem:  Tentime SCSI host adapter with MS-DOS 5.0

The Tentime SCSI host adapter TNT-4000 series uses a 8K address range in the Upper Memory Area (UMA).  This adapter can be successfully used with Microsoft MS-DOS 5.0.  When using EMM386.EXE to load device drivers high, use the X= switch to exclude the range used by the SCSI host adapter.  It is configurable for its interrupt and I/O address range usage and uses a device driver for its enhanced features.

This information applies to Microsoft MS-DOS version 5.0.

Explanation:

The Tentime SCSI host adapter TNT-4000 series is configurable for several ranges, which are as follows:

Address	Jumpers

14	15	16	17	18	19

C800	O	F	O	O	F	F

D000*	O	O	F	O	F	F

D800	O	F	F	O	F	F

E000	O	O	O	F	F	F

E800	O	F	O	F	F	F

O=On F=Off

* Default

To use EMM386.EXE to load device drivers high, be sure to exclude the range used by the SCSI host adapter.  For example, if the card is jumpered for the default settings, exclude the address range by using the following device line in the CONFIG.SYS file.

DEVICE=C:\DOS\EMM386.EXE NOEMS X=C800-C9FF

Other switches, including RAM, may still be used in conjunction with the X= switch.

The Tentime is also configurable for its interrupt and I/O address range usage.  It can use the following:

Interrupts 	3, 4, 5, 7, 10, 11, 12, 14, 15

I/O address ports 	300, 310, 320, 330, 340, 350, 360, 370, 380, 390, 3A0,

3B0, 3C0

The Tentime adapter also uses a device driver, SSTBIO.SYS, to take advantage of its enhanced features.  This device driver is NOT essential to use the adapter.  SSTBIO.SYS has been successfully loaded high using EMM386.EXE.


EMM386 Conflicts with Adaptec Controller
Problem:  EMM386 Conflicts with Adaptec Controller

An application note is available that includes a driver program to correct an interrupt conflict between the Microsoft MS-DOS 5.0 EMM386.EXE memory manager and certain Adaptec hard drive controllers.

Solution:

If you have an Adaptec controller card and you find that loading EMM386.EXE causes erratic system behavior, loading ADAPTEC.SYS may correct the problem.

This information applies to Microsoft MS-DOS version 5.0.

Explanation:

The application note is titled "ADAPTEC.SYS Driver," PD0455.  To obtain application notes, call Microsoft Product Support Services at (206) 454-2030.


Problems with Other Drives

Includes floptical and drive types not mentioned elsewhere.


Motherboard
The Motherboard

  In this motherboard, the red area is the microprocessor.  The blue area is the place where memory modules are plugged in.  The purple area is the BIOS.


Microprocessor

This is the "brains" of the PC.  This is a 286, 386, or 486 chip, depending upon your PC's configuration.  In the case of the 386 and 486 chips, instructions are processed 32 bits at a time.  A 286 processes 16 bits.  These chips run at different speeds, usually expressed in megahertz (MHz).


BIOS

Basic Input/Output System.  This is a set of code run upon startup.  Here, specific addresses, devices, and software interfaces are defined in ROM.


SIMMs

Single Inline Memory Modules.  These can come in many configurations such as 1 MB x 8.  This means the 8 chips together add up to 1 MB of RAM memory.  This area on the motherboard is where SIMMs are plugged in.  In this way additional RAM can be added at any time.


General Information about PC Memory

The memory of a PC is subdivided in many ways.  The diagram below and the listed topics describe the various divisions.  Click on an area or number in the diagramm or on any topic below for a further explanation.  The colors of the various words match the location in the memory diagramm.

1.Interrupt vectors   2.Flags   3.Conventional or Ordinary Memory     4.High Memory   5.Expanded or Extended Memory


Interrupt Vectors

The first kilobyte, or 1024 bytes, holds interrupt vectors set by both the BIOS and DOS; these may be modified by application programs.  The vectors point to the locations of software routines in other memory addresses to which operations should branch when various hardware components send a special signal called an interrupt.  An interrupt conflict, a major cause of PC problems, is when more than one program uses the same interrupt.


Flags

The next 256 bytes contain BIOS data called flags that are used to indicate the state of various internal system conditions.  A 16-byte keyboard buffer is also in this area.  The keyboard buffer is where keystrokes are stored while the PC unable to process the keystrokes because it is temporarily handling another tasks.


Conventional Memory
Ordinary or Conventional Memory

The next chunk of memory, up to 640K, is ordinary memory or conventional memory.  This is the RAM into which COMMMAND.COM, device drivers, memory-resident programs, and applications software are ordinarily loaded.  Memory managers, such as QEMM386 or HIMEM.SYS allow remapping of memory so that device drivers, memory-resident programs, and part of COMMAND.COM can be loaded into high memory, above the 640K reserved for applications software.  Without memory managers COMMAND.COM suffers the risk of being overwrittern by any application program that needs memory.


High Memory

Above ordinary memory is high memory.  Part of this memory area is reserved for hardware add-ins, like BIOS, and various types of display adapters, network interface cards, or hard-drive controllers.  This area of memory is called upper memory blocks or UMBs because there are six distinct blocks of memory above the 640K line which are used for different purposes by different devices.  UMBs are also known as high memory, upper memory, and adapter segment memory.  This is not the same as the High Memory Area or HMA.  HMA is the first 64K above the UMBs.  This area is the same as the first 64K of extended memory.

The six 64K blocks of memory within the UMB area are typically used by a certain type of adapter or device.  The six blocks of memory are usually refered to by their first memory address.  These addresses are numbered in hexadecimal.  The first 64K is A000 (or A thousand) the second is known as B000, and so on.


Upper Memory Blocks

These blocks are usually allocated in the following ways:

A000:  VGA and EGA graphics adapter RAM chips.  VGA and EGA adapters "swap" parts of their video memory in and out of this 64K area continuously.

B000:  Hercules monochrome graphics RAM takes the first 32K of this area; the second 32K is occupied by CGA graphics RAM, or EGA or VGA text-mode RAM

C000:  The ROM BIOS chips of the VGA adapters occupy this area; some BIOSs take as little as 24K of this area, while some occupy 32K of it.

D000:  A Page Frame of 64K is often placed in this block of memory.  This gives EMS (Expanded Memory Specification) access to DOS applications.  The total available expanded memory is "paged" in and out of this area continuously.

E000:  Some PC manufacturers, like IBM, place an extra ROM BIOS chip here.

F000:  Most DOS applications depend upon the ROM BIOS chip located here.


Extended or Expanded Memory
Expanded or Extended Memory

All memory above 1024 K is called expanded or extended memory.  Extended memory can only be used by Intel's 80286 or later processors.  Under DOS, expanded and extended memory cannot be used to hold program code, but it can be used to hold data.  Windows is not held to these constraints.  Through bank switching, a process in which banks of memory are brought into and out of conventional memory, Windows moves beyond this limitation.


Network Interface Card

The NIC, or LAN adapter, uses  a specialized processor and routines stored in memory to move data to and from the computer's memory over the parallel data bus and to transmit and receive data on the serial network cable.  The NIC buffers data in on-board RAM and rearranges the data to fit network protocol.  At the same time the NIC handles the interface to the computer over the expansion bus connectors and the interface to the cable over the cable connector.

This diagramm illustrates some of the components of an Ethernet NIC.  Click a location on the card or on the following terms for more information.  SEE  Cable Connector, Boot ROM, Transceiver Power Supply, Jumpers, Ethernet Processor, Buffer RAM, Expansion Bus Connectors.


Cable Connector

This connector is the interface between the card and the cable.  Connectors can be of various types and vary with the type of cabling used.  The types are

RJ-45-is used with Unshielded Twisted Pair (UTP) Wire.  Only an expedient level of speed is available and maximum cable length is short.  However, the average cost per node is the least of all the connectors and the media and connector size are small.

BNC-is used with Coaxial Cable.  The speed and throughput are very fast andthe average cost per node is inexpensive.  The maximum cable length is medium as is the media and connector size.

IBM Data Connector-is used only with Token-Ring LAN specifications.  The speed and throughput is very fast.  However, the average cost per node is expensive, the maximum cable length is short, and the media and connector size is large.  Large cable size is a disadvantage because thick cable rapidly fills the space in building wiring ducts.

ST Fiber Optic Connector-is used with Fiber Optic Cable.  The speed and throughput is the fastest possible, the media and connector size is very small, and the maximum cable length is very long.  However, fiber optics has the highest average cost per node.


Boot ROM

A socket exists on some NICs for this special ROM.  This ROM allows a PC to start DOS from a file on a server.  With this arrangement the need for an internal hard drive is eliminated.


Transceiver power supply

The transceiver power supply boosts the low powered digital signals inside a computer to a level powerful enough to travel across the network.


Jumpers

The jumpers are arranged to provide a unique bus address setting for each NIC on the LAN.  This insures that only packets meant for a specific PC will be accepted by the NIC.


Ethernet Processor

This is a specialized processor for moving data to and from the PC's memory over the parallel bus, through the connector, and onto the network.  These processors are manufactured by a number of companies including IBM, Artisoft, and National Semiconductor.  IBM also produces Token-Ring Processors.


Buffer RAM

This RAM is where the NIC buffers data.  The size varies from 8 to 64K of RAM.  Data must be buffered becuase the computer is much faster than the network.  Additionally, the form of the data changes from a wide parallel stream coming in at 8 bits at a time from the PC's bus to a narrow 1 bit at a time serial stream in and out of the network connector.


Expansion Bus Connectors

The expansion bus connectors provide the physical connection between a card and the PC.  Parallel data moves to and from the PC's memory over the expansion bus.


What is a LAN?

A LAN is a Local Area Network.  A LAN is a physical link between several PCs to each other and often to a mainframe or a minicomputer.  This accomplished with a variety of materials like twisted-wire cables, fiber optics, phone lines, and even infrared light and radio signals.

Each network topology - or the network configuration - must perform the same chores.  The most common situation that a network encounters is a message from one PC to another.  The message may be a query for data, the reply to another PC's data request, or an instruction to run a program that's stored on the network.  The data or program that the message asks for may be stored on a PC used by a coworker on the network, or on a file server, a specialized PC.  Similarly, a network may include print servers that everyone on the LAN can use for printing.The network must receive requests for access to it from individual PCs, or nodes, linked to the network, and the network must have a way of handling simultaneous requests for its services.  Once a PC has the services of the network, the network needs a way of sending a message from one PC to another so that it goes only to the node it's intended for and doesn't pop up on some other unsuspecting node.  And the network must do all of this as quickly as possible while spreading its services as evenly as possible among the nodes on the LAN.

SEE ALSO

Why use a LAN?


File Server

A file server is usually a PC with a large hard drive that is not used exclusively by any individual on the network.  Instead, it exists only to serve all the other PCs using the network by providing a common place to store data that can be retrieved as rapidly as possible.


Print Server

A print server is a PC connected to a printer or an intelligent printer that can be connected to a network without an intervening PC.  In this way an expensive resource, like a laser printer, can be shared among many users.


Why use a LAN?

The biggest reason to use a LAN is the ability to share information with others on the LAN.  When individuals work on stand-alone PCs, they work with stand-alone information.  Before PCs, users had dumb terminals which had access to a centralized mainframe or minicomputer.  That computer was a large, mysterious box tended by specialists in lab coats.  In such a system, all the data was stored on the computer and was shared as needed.  Many companies have been moving away from this model and are moving to more decentralized systems.

Other systems work on a client-server model (see picture).  This type of LAN allows the sharing of information and resources, like laser printers or large hard drives, like the centralized systems of the past, but at much less cost.  For example, a mainframe costs in excess of a million dollars to purchase and about $35,000 a month for maintenance.  A client-server LAN costs a fraction of that.

Another model very popular in smaller networks is the peer-to-peer.  In the peer-to-peer model every PC is a file server.  Users not only have access to data on their local drives, but also to data on their co-workers drives.  Any one of the peer workstations can be attached to a printer and can function as the print server for the network.

Reference:  How Computers Work by Ron White.


LAN Topologies

The LAN topology is the configuration of the LAN.  This is the way in which the network handles service requests and conflicts and the means of connecting each of the nodes together.

Three topologies account for most LAN configurations.  They are:

Bus Network

Token-Ring

Star


Bus Network

On a bus network all the nodes are attached to the LAN as branches off a common line.  Each node has a unique address that can be assigned by setting jumpers on the network interface card (NIC).  Before transmitting a message, each node listens to insure that the network is clear.  It then sends a message to another node by giving the message to a transceiver, one of the components of a NIC.

The message is broadcast in both directions, and all the other nodes receive the message.  Each message has the destination node's address, source node's address, error checking packets, and the data itself.  If a node recognizes the destination address as its own, the node accepts the packet and sends out a confirmation message.  If the node does not recognize the packet, the packet is ignored.

If two node simultaneously send messages, a collision occurs.  A collision creates an electrical interference pattern along the bus and is detected by the senders.  The first node to detect a collision jams the network with a special signal.  This warns the other nodes of a collision, and the nodes will stop transmitting.  After waiting a random length of time, the nodes will attempt to transmit again.  This process will repeat until one node successfully transmits a message.

SEE ALSO

NETWORK INTERFACE CARD


Token-Ring Networks
Token Ring Network

In a Token-Ring network all the nodes are connected to the same continuous loop.  The network constantly circulates a token, an all-clear signal, along the circuit.  A node wanting to send a message must wait until the token reaches it.  Once the node gains the token, the node modifies the token to an "in use" form, attaches the message, error checking code, and the destination node's address, and then amplifies the message before transmitting the message through the network.  Each node inspects the token as it passes by to check the destination address.  When the token reaches the destination, that node makes a copy of the message before passing the message along the ring.  When the originating node receives the token it restores the token to the original "all-clear" state.

SEE ALSO

NETWORK INTERFACE CARD


Star Networks
Star Network

In a star configuration, all the nodes are attached to a central station or hub.  The hub contains switches to connect any of the lines to any other line.  When a node sends a message it includes the address of the destination node, the data, and error chencking code.  The connections to each node are regularly checked by the hub.  By taking turns opening and closing the connecitons, the hub prevents collisions between messages.  Only a small portion of one message are passed through the connections at one time.  This prevents one node from monopolizing the network.

SEE ALSO

NETWORK INTERFACE CARD


NOS Data Packaging
Network Operating Systems' Data Packaging

Network Operating Systems package requests in a sequence of steps from the PC to the NIC.  Client Software works with the internal operating system of a computer so it can route requests from application programs and from the keyboard.

The redirector is the part of the client software that captures service requests for the network and routes them out of the PC and across the network for service.  It captures requests it has been programmed to recognize and routes them properly.

Network communications software packages requests from the client computer and sends the requests across the network.  This software conforms to specific protocols for addressing, insuring deliver, and insuring accuracy.  Examples of network communications protocols are Apple's Apple File Protocol (AFP), Artisoft's Network Basic Input Output System (NetBIOS), Microsoft's NetBIOS Extended User Interface (NETBEUI), and Novell's Sequential Packet Exchange (SPX) and Internetwork Packet Exchange (IPX).  Most of these are based on the seven-layer Open Systems Interconnection (OSI) model (see picture).

Driver software works between the network interface card and the network communications software.

For example, to save a file to the NetWare file server, drive F:, a DOS request for drive F: is captured by the NetWare redirector.  The redirector packages the request in an IPX packet and passes it to the Network Interface Card.  The NIC packages the IPX request into an Ethernet frame and passes it to the network.

SEE Internetwork Data Packaging for related information.


OSI

The system is not based on specific hardware or software.  It is based on a scheme implemented upon a certain pattern.  The pattern is composed of seven layers.  Each component of the network exists on a specific layer of the system, and each component can communicate directly only with the layer directly above it and directly below it.  Each layer provides services to the layer above it and can invoke the services of the layer below it.  The seven layers are:

1.  Application Layer

2.  Presentation Layer

3.  Session Layer

4.  Transport Layer

5.  Network Layer

6.  Data-Link Layer

7.  Physical Layer

At the receiving node, the layered process that sent the message is reversed.  A message moves through the seven layers from the bottom up.  At each level headers are removed and the data reconstituted.  The physical layer reconverts the message into bits.  The data-link layer recalculates the checksum, confirms arrival, and logs in the packets.  The network layer recounts incoming packets for security and billing purposes.  The transport layer recalculates the checksum and reassembles the message segments.  The session layer holds the parts of the message until the message is complete and sends it to the next layer.  the presentation layer expands and decrypts the message.  The application lyaer converts the bits into readable characters, and directs the data to the correct application.


Application Layer

The Application Layer converts a message from characters into bits and attaches a header identifying the destination and sender.


Presentation Layer

This layer translates the message into a language that the destination can interpret.  It also compresses and may encrypt the data.  A header identifying the language, compression and encryption schemes is added.


Sessions Layer
Session Layer

This layer keeps the sommunications among all nodes on the network straight.  It sets boundaries for the beginning and end of the message.  Whether the message is sent half-duplex or full-duplex is established here.  Half-duplex communications has each computer taking turns sending and receiving.  Full-duplex communications has both computers sending and receiving simultaneously.  These details are encoded into the sessions header.


Transport Layer

The Transport Layer subdivides the data into segments and creates checksum tests for each segment.  The receiving station can use the checksum to determine if any errors have occured in the transmission.  The transport header identifies each segment's checksum and its position in the message.


Network Layer

This layer selects a route for the message.  It divides the data into packets, then counts them, and adds a header containing the sequence of packets and the address of the receiving computer.


Data-Link Layer

The checksum is confirmed here.  The packets are then addressed and duplicated.  A copy of each packet is maintained here until this layer receives a confirmation from the destination of a successful transfer.


Physical Layer

This layer encodes the packets into the medium that will carry them.


Internetworking

Internetworking-the connecting of LANs-requires the use of specialized equipment.  Network portal devices are devices designed to extend and segment the LAN's high speed cable.  Repeaters, bridges, and routers are examples of portal devices.


Repeater
Repeaters

Repeaters connect two segments of your network cables.  The repeater retimes and regenerates the digital signal on the cable and sends them on their way again.  Repeaters are inexpensive and easy to manage, but they have a limited range, because they cannot extend the LAN cable beyond a few thousand yards.


Bridges

Bridges extend the network and isolate network traffic.  Bridges send packets and frames between various types of media.  Bridges forwared only traffic that is addressed to devices on another cable system to limit the nonessential traffic on linked cable systems.


Router
Routers

A router will read inside the Ethernet or Token-Ring envelope to find the destination for the data packet.  The router will determine the appropriate network destination, discard the outer envelope, and then repackage and retransmit the data.   The destination router will repackage the information into the appropriate form for its LAN segment.  SEE Internetwork Packaging.


Internetwork Data Packaging

Data sent over an interLAN connection requires special handling.  Each type of network portal device uses different techniques to send data.

Bridges

Routers


Bridge - Internetwok Data Packaging
BRIDGES - Internetwork Data Packaging

Bridges examine the address of each packet and send across the interLAN connection only those packets addressed to nodes on the other side.  This reduces the amount of traffic on the expensive connection.  A bridge will read the station address of the Ethernet packet or Token-Ring frame to determine the destination of the message, but it will not look inside the packet or frame to read NetBIOS, IPX, or other protocol address.  The two LANs can use different types of cabling, but they must both use the same topology, for example, both must be Ethernet.


Router - Internetwork Data Packaging
ROUTERS - Internetwork Data Packaging

Routers examine the destination address contained in the network communications protocol (in this case NetWare's IPX) and strip off the Ethernet packet or Token-Ring frame information.  Only the IPX packet and its encapsulated data is sent across the interLAN link.  The destination router repackages the information into the appropriate envelope for its LAN.  Since routers strip off the outer layer of data befor sending the packet they reduce the total number of bits going across the interLAN communications link.  Routers can connect LANs irregardless of the kinds of hardware or network communication protocols the segments use.  Some routers can also repackage the network communications protocol, for example a NetWare IPX packet can be repackaged into an AppleTalk AFP packet.


Print Problems

This section covers printing.

See

PRINTER

This section gives general information about printers.  It also gives information about conflicts with specific printers.

DRIVERS

Drivers are a link between your applications and Windows.  This section gives information about problems with various printer drivers.

GRAPHICS

Problems with printing bitmaps, graphs, and other graphic images are covered here.

NETWORK

Problems associated with outputs to a network print server are covered in this section.


General Information on Printers

The Windows Control Panel is what you will use to install and configure printers; set serial printer ports, baud rate, parity, and other communications setting; delete printer drivers; add or delete soft fonts.

To change the installed printer from an application you generally use the Print Setup command found in the File menu.

Printers differ in their abilities to use fonts, graphics, spacing, alignment, and character formats.  The appearance of your printed document can vary greatly from printer to printer.  The way your document looks depends on which formats you assign and which formats your printer can print. Some differences are listed below:

For some printers, bold and italic are fonts, instead of character formats.  In that case, you need to specify the appropriate bold or italic font when you want to print in bold or italic.

Microspace means microspace justification--an equal amount of space between each word with left and right justified margins.

In some cases, bidirectional printing isn't available on a dot-matrix printer, and it will print in only one direction.  This occurs when a document contains formatting (for example, microspace justification) that the printer can't accommodate while printing backwards.

A printer can print small capital letters only if there is a smaller size available for the font you are using.

If you are using soft (downloadable) fonts, you may run out of printer memory, and then printer output may be garbled or only a part of your document may be printed.

See Also

Printer Ports

Printer Drivers

Printer Interfaces

Printer Cables

Printer Configuration Switches

Handshakes

Fonts


Printer Ports
Ports

LPT1, LPT2, LPT3, COM1, and COM2 are input/output ports.  The computer uses them to connect with printers and other devices.  The parallel ports are LPT1, LPT2, and LPT3.  The serial ports are COM1 or COM2.  Connect a parallel printer to a parallel port and a serial printer to a serial port.  Network printing is generally done over a parallel port.


Printer Interfaces

Printers use various interfaces to connect to the PC.  A printer can use a parallel interface, a serial interface, or either one.  A parallel and Centronics interface are the same thing.  A parallel interface sends multiple bits of information to the printer simultaneously.

Serial, asynchronous, and RS232 interface are all the same thing.  A serial interface sends single bits of information to the printer one at time.


Printer Cables

All parallel cables are the same.  Serial cables usually differ from one another; they are often made for a particular printer.  Bad cables can be the cause of printing problems.  Printers with bad cables may print garbage or garbled characters.


Printer Configuration Switch
Printer Configuration Switches

Many printers have a set of DIP switches that set their configuration.  The printer driver's help file will note if the DIP switches should be changed.  If you have a serial printer, you need to set the correct port, baud rate, word length, parity, handshake and stop bits.  If the baud rate or parity is incorrect, the printer may not print or the output may be garbled.  In the Control Panel, use the Ports command on the Settings menu to set these parameters.


Handshakes
Handshake

With a serial connection the correct handshake or protocol must be used.  The handshake is the hardware and software settings that allow your computer to communicate with a connected printer or other device.  If the handshake is not correct, the printer may print, but it will lose text.  Check your printer manual for the correct settings.


Fonts

A font is a set of characters that share the same typeface, such as Roman or Courier, and the same point size.  A font may also have different type styles such as italic and bold.

Resident Fonts

Resident fonts come with your printer and vary from printer to printer.  For example, after a PostScript printer is set up, the resident fonts will be available for use.

Soft Fonts

Soft fonts are downloadable fonts.  By purchasing soft fonts, you can increase the variety of fonts in your documents.  These font software programs download fonts to your PostScript printer so that you can use additional fonts.

Soft fonts must have a printer font metrics (PFM) file.  The manufacturer will supply the PFM file and may supply a installation program.  If an installation program isn't supplied, then you can install the fonts by modifying your WIN.INI file using a text editor, like Notepad in Windows.


Preparing to Print

There are three steps in preparing to print:

1.  Connect the printer to the computer.

2.  Install the print driver.

3.  Configure the printer.

These steps are outlined below.

1.  Connect the printer

Make sure you have the correct cable for your printer, especially if you are using a serial printer.

Connect your printer to your computer and configure the printer's switches and mode settings according to the printer manufacturer's instructions.

If your printer is connected to a serial port use the Ports command on the Settings menu in the Control Panel to set the port, baud rate, word length, parity, stop bits, and handshake for you printer.

Connecting the printer to a LAN server may require a network administrator.  SEE Network Printing

2.  Installing a Printer Driver

Installing printer drivers is done in Windows.  Installation may require a network administrator if you are installing on a LAN.  SEE Network Printing.  Use Control Panel to install a printer driver.

3.  Configuring your Printer

The printer's connections must be set after you install the printer.  Select the options you want to use as defaults.  To configure the printer, choose Printer from the Settings menu in the Windows Control Panel, and then choose the Configure button.


Using PCL

PCL is a printer command language used by the HP LaserJet printers and some others.  A PCL printer composes a whole page before it prints like a PostScript printer.  PCL printers use resident fonts, font cartridges, or soft fonts.  Cartridge fonts and soft fonts are not included with your printer and must be purchased separately from a font or printer manufacturer.

Drivers

There are two printer drivers for PCL / HP LaserJet printers, HPPCL.DRV and HPPCL5A.DRV.  HPPCL.DRV is for all LaserJet printers except for printers such as the LaserJet III, LaserJet IIID, and LaserJet IIIP, which support HP PCL Level 5 and which require HPPCL5A.DRV.

Graphics

A PCL printer may not print every graphics resolution listed as an option listed in the PCL /HP LaserJet dialog box as a full page.  there may be too much information on a page for your printer's memory to accommodate.  If this happens, try printing at a lower graphics resolution.

Resident and Cartridge Fonts

Resident fonts are built-in fonts.  some printers have as many as 16 built-in fonts.  Each font contains all of the characters that share the same point size, character format (such as italic or bold), family (such as Courier) and orientation (portrait or landscape0.

Cartridges contain one or more fonts.

Your printer manual will have more details on resident and cartridge fonts.

Soft Fonts

Soft fonts are downloadable.  Fonts come with either a printer font metrics (PFM) file or a PFM file is created when the font is installed.  Specific PFM files are customized to a font.  Generic PFM files created during installation may cause a font to appear slightly different from a font printed with a custom PFM.

Two fonts are required to print and display a soft font-a printer font and a screen font.  Screen fonts have the .FON extension.  To see if the screen fonts have been installed, check the SYSTEM subdirectory of your Windows directory for files with the .FON extension.  The Fonts command on the Settings menu in the Control Panel.


Printer Problems

This heading consists of specific printers and their associated print drivers.

General Information

~On Printers

~Printer Drivers

~Printer Ports

~Printer Interfaces

~Printer Cables

~Printer Configuration Switches

~Handshake

~Fonts

~Using PostScript

~Using TrueType

~Using PCL

~ATM - Adobe Type Manager

~Preparing to Print

General Problems with Printers

Specific Printer Problems

Specific Printer Problems with Applications


General Problems with Printers

~Garbled Printing

~Garbage Printing

~Printer does not print

~Only Part of a Page is Printed.

~When Printing to a File, Part of the Document is Lost

~Document Printing is Interrupted on a Network

~Printers not supported by Windows

~Switching from Landscape to Potrait


Specific Problems with Printers

~Curved Characters and the IBM XY749 Plotter

~Windows 3.0 and IBM ProPrinter X24e/XL24e

~Underlines and the Okidata192/193 292/293

~Epson LX 810 Sheet Tear Off Doesn't Work

~Improved HP DeskJet Drivers

~Display Area After Using the HP DraftMaster

~Qume Sprint 11+ Line Feeds And Spacing

~Printing to Legal Size Paper with Canon Printers

~Bitstream 3.0 And Panasonic KXP4450

~Kodak DiconiX 150 and Windows Printer Driver

~Fixing Offset Problems On The Star NX 1000

~QMS PS 2200 Problem Printing 11" X 11"

~TrueType and Blazer Star II Laser

~Some ATM Fonts Print Incorrectly

~Printing with HP PaintJet Driver v1.0

~B and W output from a HP PaintJet /XL

~Print out shows a solid block

~Can't Print from Windows Applications

~Print Jobs take too long or parts of the print job are missing.


Specific Printer Problems with Applications

with Lotus 1-2-3

~Linefeed and Page Advance with Okidata 93 and 1-2-3

~Printing Graphs in 1-2-3 with a Color Printer

~123W Release 4 Plotter Support and Related Printing Issues

~Graph Does Not Print Properly to a Plotter

~Using Internal Scaleable Fonts on a HP LaserJet III

~Memory Setting Not Holding for HP LaserJet III

~Cannot Reset HP LaserJet III Graphic Resolution

with Excel

~Epson FX-80/FX-100 Draft-Printing and Excel

~Printing Excel Charts with Canon LBP 4

~Character Missing When Print Titles Are Set In Excel

with MS Word

~MS Word Printing Selected Text to a File

~A Page Prints but is Incorrectly Formatted in MS Word.

~Printer Advances but doesn't Print in MS Word

~HP II, Vector Fonts, and Landscape Printing in MS Word

~Selection or Pages in the Range Printint in Word

~Word 5.0: Printing with HP DeskJet Downloadable Driver

With AmiPro

~"Error: Printer Busy" Occurs While Printing in Ami Pro

~Printing Files with Graphics Results in a UAE

~"Unable to Print" Message using Generic Text Driver

~"Frame Protocol Error" Printing to Windows Printing System

~Error Messages While Printing

with Freelance Graphics

~"Initialization Error" Printing from Freelance for Windows 1.0

~Some Printer Fonts aren't listed in FLW

~FLW Prints Black & White Only

with Approach

~Internal Error when Printing in Approach

~Print Out is choppy in Approach

~Approach Fields appear in Black

with Accessories

~Printer Setup from Calendar, Cardfile, Notepad

~Incorrect Printing of Saved PIC or Metafile

~Improper Formfeed when Printing Cardfile


Printer Output is Garbled
Problem:  Printer Output is Garbled

A document prints but it is garbled or contains extra characters.

Solution:

Troubleshooting Steps:

1.  Check the baud rate and other parameters you selected with the Ports command in the Control Panel to make sure they match the manufacturer's specifications.

2.  If you are still losing text, change to a lower baud rate than the one you are using now, and try to print again.

3.  Check all the manual switches on your printer against the settings described in your printer manual to make sure the switch settings are correct.

4.  Check to make sure you have the proper cable for your printer.

5.  If you are using a a laser printer that cannot print all the way to the edge of the page, remember to include the figure (usually .25 or .5 inch) in your calculations for page size.

6.  If you are using a NetWare Print Server and using the CAPTURE command check the Q= parameter.  SEE Network Printing and Using the CAPTURE Command


Only Part Of a Page is Printer
Problem:  Only Part of a Page is Printed.

Solution:

Your printer may not have enough memory to print the entire page.  Try printing at a lower resolution.


When Printing to a File, Part of the Document is Lost
Problem:  When Printing to a File, Part of the Document is Lost

In Windows version 3.0, a document that has more than one orientation cannot be printed as a single print job.  For example, if you print a two-page document and one page is formatted as portrait (taller than it is wide), and the other as landscape (wider than it is tall), windows splits the document into two separate print jobs.  When you print to a file, you are therefor prompted twice for the name of the file to which you want to print.  If you type the same filename the second time that you are prompted, the second print job overwrites the first.

Solution:

Give a separate filename to each print job.

If, after printing to a file, you want to use the DOS COPY command to send the file to a printer, you must use the "/B" switch with the command.  For example:

copy /b filename lpt1:


A Document is Interrupted during Network Printing
Problem:  A Document is Interrupted While Printing on a Network

Windows version 3.0 splits a document formatted with more than one orientation into more than one print job.  It is possible, when you are printing on a shared network printer that someone else's document might be printed between different parts of your document.


Printers not supported by Windows
Problem:  Unsupported Printers

Some printers may not be included in the list of printers presented in the Windows Setup program.

Solution:

A generic printer driver, TTY.DRV provides basic support for virtually any printer.  More sophisticated support probably exists as well.

Many printers emulate industry-standard printers such as the Epson FX or Hewlett-Packard LaserJet series.  The printer manual will have details on any emulation.  If it does, the printer driver for the printer it emulates should support the printer.

The printer deal or manufacturer may have a Windows printer driver.

Microsoft uploads new and updated Windows printer drivers to CompuServe.  Check the Microsoft Forum and Knowledge Base.  Microsoft Product Support may also have information.

To use the TTY.DRV printer driver, select Generic/Text Only from the List of Printers in the Setup program or choose Printers from the Control Panel.  Install this printer as you would any other printer.  The TTY.DRV printer driver can direct your printer to print underlines, strikethrough, bold, or to substitute underlining for italic and double underlines.  It cannot print graphics.  For information on installing a printer, see your Windows documentation.


Printer does not print
Problem:  The printer doesn't print.

Solution:

If a printer won't print, the cause is often a simple mechanical problem--the printer may be "offline" or not connected to the computer.

If printing from one application works but printing from another doesn't, check the printer settings by using the Control Panel or the Print Setup command in the trouble application.

Troubleshooting steps:

1.  Make sure the printer is plugged in and turned on.

2.  Make sure that the printer is connected tot he computer and is "on line," as shown on its control panel.

3.  Make sure that the correct printer is selected and the printer settings are correct:

Choose Print Setup or a similar command from within an application to see if the correct printer is selected.  If the printer you are using is not listed, use the Control Panel to install your printer.

If you have a serial printer, check the settings for your serial port by using the Ports command on the Settings menu in the Control Panel to make sure your printer parameters are properly selected.

4.  Look at the Printers dialog box in the Control Panel to make sure the correct port is specified for your printer.

5.  See if you need to change the ribbon, mount a print wheel or cartridge, or add paper.

6.  Make sure that you have the correct cable for your printer and that the printer cable is properly connected.

SEE Preparing to Print


Garbage Printing
Problem:  Garbage Printing

Garbage was printing from WordPerfect for Windows with the WP  driver  of the HP LaserJet III printer selected.  The  same problem exists in other Windows applications, as well as WordPerfect for Windows when using the Windows  driver .  Printing is successful from DOS, however. Switching cables solves printing problems from all Windows applications.

Solution:

Garbage printing is a common symptom of a bad or damaged cable, so check the cable.


Plotting with the IBM XY749 Plotter
Problem:   Plotting curved characters with the IBM XY749 Plotter

A pen intermittently shoots across the page when plotting a curved character. However, sometimes it will plot a graph perfectly.

Solution:

The first  driver  for the IBM XY749 that was released on the Graphics Printer Library disk (GPL 1) was faulty.  The  driver  has been fixed and is on the current GPL I disk.


Underlines with Okidata 192/193 292/293
Problem:  Underlines with Okidata 192/193 292/293

The Okidata 192/193 292/293 (IBM) printers are having problems printing underline with very small left and right margins.  Right now the driver allows you to set your minimum left and right margins at .25".  But that is not correct.

Solution:

To fix the problem for now, either go into PTR and set their minimum margins at .3" or don't use margins smaller than .3".


Epson LX810 Sheet Tear Off Doesn't Work
Problem:  Epson LX 810 Sheet Tear Off Doesn't Work

The Epson LX 810 has a sheet tear off feature that doesn't work with the 7/21/89  driver  (800/810/apex80)

Solution:

Go into the PTR program and delete the codes at "Reset at end of print job".  The codes are [27]"@" and are the only codes there.


Linefeed and Page Advance with Okidata 93
Problem:   Linefeed and Page Advance with Okidata 93.

The Okidata 93  driver  does not issue linefeeds when the menu option (/Worksheet Global Default Printer Auto-LF) is set to No. Pressing Page in 1-2-3 advances the paper one line short of a page.  With long documents, you may receive a "Printer Error".

Solution:

1: Select DOS  device  LPT1

2: Choose Unlisted Complete Capability as a text printer in Install.

See Also

APPLICATIONS

SPREADSHEETS


Improved HP DeskJet Drivers
Problem:  Improved HP DeskJet Drivers

Printer drivers that correct problems on the Hewlett-Packard (HP) DeskJet and DeskJet Plus are available as on the Supplemental Printer Kit for Microsoft Word for MS-DOS version 5.5b.  You can obtain the Supplemental Printer Kit from Microsoft End User Sales at (800) 426-9400.  If you call from outside the United States, contact Microsoft International User Service at (206) 936-8661.

The drivers also can be found in the file DWXHP0 in the Software/Data Library by searching on the word DWXHPO or S12287. DWXHP0 was archived using the PKware file-compression utility.  DWXHP0.EXE and DW0060.EXE are the files that contain the HP DeskJet .PRDs on the Microsoft Download Service (MSDL).

There are three problems with the HP DeskJet drivers currently shipping on the Word Version 5.0 Supplemental Printers disk.  The problems occur only when using soft fonts and the DESKJETX.PRD and corresponding DAT files.  The three problems and their solutions are detailed below.

Related Problems:

1. The Universe 18 and 24-point fonts both print as either 14 or 15 point. If   you download the 30-point Universe font, the 18 and 24-point fonts both   print as 15 point; otherwise, they both print as 14 point.

2. When downloading the Helvetica 8 font, a code that is part of the download   escape sequence prints in the upper left margin of your document. If the   HP DSU download utility is used to download, this code does not appear.

3. The DESKJET3.PRD does not download the ASCII set. The DSU download utility   that comes with the soft fonts allows you to download the 7-bit ASCII set   containing 128 characters, but not the set containing 255 characters. This   saves download time and memory space and allows you to use more fonts.   Although the documentation indicates DESKJET3.PRD allows you to download   the 7-bit ASCII set, it actually sends the entire character set. You can   avoid this by using DSU and specifying only ASCII characters to be   downloaded.

Solutions:

1. Run Makeprd on the appropriate DESKJETX.PRD file. Find the 18 and 24-point   (font sizes 36 and 48, respectively) cPSDs for font 12 (Universe). Change the "t15V" at the end of the begin mod:0 string to "t18V" and "t24V"   (without the quotation marks) for 18 and 24-point, respectively. Run Makeprd and convert the file back.

2. To correct the escape sequence, run DEBUG followed by the name of the   appropriate DESKJETX.DAT file. At the dash prompt, type "E 274" (without   the quotation marks).  The screen displays the number 43 and a colon. Type   63 and press ENTER. At the dash prompt, type "W" to write the new DAT file   and "E" to exit.

3. Use any text editor to load DESKJET3.DAT. Without typing anything else into the file, replace ".DJP" with ".USP", and set confirm to No. Save the new DAT   file. This process ensures that the ASCII fonts are downloaded.


Display Area After Using the HP DraftMaster
Problem:  Display Area After Using the HP DraftMaster.

A drawing created in Freelance Plus 3.0 or 3.01 with the HP DraftMaster listed as the output  device displays far beyond the plot boundaries, if the output  device  is changed from the DraftMaster to another  device such as the HP PaintJet, the drawing .  Freelance is exited and then reloaded, the program retrieves the drawing in question and the drawing is displayed correctly.

Solution:

Whenever a drawing is displayed on the screen in Freelance, the sizing and proportions of the drawing correspond to the installed output  device .  If the output  device  is changed, the screen must be refreshed by exiting and reloading the program so that the display area corresponds to the new  device . With most of the output devices this is not usually necessary because the boundary areas on the devices are very similar.  However, with the HP DraftMaster, the screen needs to be refreshed when the device  is changed because of the DraftMaster's significant boundary difference compared to other printers.


Autorotating Printers
Problem:  Autorotating Printers

When printing two documents in succession, one with portrait orientation and the second in landscape (or vice versa), the second document will print in the wrong orientation.  For example, both may print in portrait, or both may print in landscape.

This is only a problem on autorotating printers.  This does not occur on printers requiring a separate landscape  driver .  Examples of printers affected are the Hewlett-Packard (HP) IIP, IID, and III.  IBM 4019 and PostScript printers are also affected.

Solution:

To work around, When printing a document that has a different orientation from the ones that you have been printing, choose Page Setup and Margins from the Print menu and press the ENTER key without making any changes.  The document will now print in the proper orientation.


Qume Sprint 11+ Line Feeds and Spacing
Problem:  Qume Sprint 11+ Line Feeds And Spacing.

The problem has to do with incorrect line feeds and erratic spacing on machines running faster than eight megahertz.

Solution:

The Sprint 11+ was designed for XT or PC computers.  The faster computers have communication problems with this printer.  For this reason, Qume has an upgrade to the interface module.  The current version is version 2.3, and is available through Qume or a dealer for about $100.00.  If you has an AT or faster computer, they will need the upgrade.  Problems are occurring in all software.  The problem is one of hardware interface.  If you have a computer faster than eight MHz, they need the upgrade.  This problem will show up in 4.2, and in PlanPerfect, or any software from any company.


Printing to Legal Size Paper with Canon Printers
Problem:  Printing to Legal Size Paper with Canon Printers.

It has been reported that printing from Windows versions 2.03, 2.10, and 2.11 onto legal sized paper does not work correctly using the Canon LBP8 Series laser printers.

Solution:

Microsoft is researching this problem and will post new information as it becomes available.


Bitstream 3.0 and Panasonic KXP-4450
Problem:  Bitstream 3.0 And Panasonic KXP-4450.

If you install Bitstream 3.0 using the 4/29/89 .EXE and .ALL files with the Panasonic KXP-4450 printer, there is a problem with marking any landscape fonts with a plus.  The fonts appear in printer control as if they are downloading properly but when you get the actual print job it has not printed in the selected font.

Solution:

If you mark the fonts with an asterisk and initialize the fonts into the printers memory they work fine.  This is only a problem using the 4/29/89 .EXE and .ALL file dates, using the 6/12/89 .EXE and 7/21/89 .ALL file dates works fine.

See Also

SYSTEM CONFIGURATION

FONTS


Kodak DiconiX 150+ Windows Printer Driver
Problem:  Kodak DiconiX 150+ Windows Printer Driver.

Kodak has confirmed a problem with the DiconiX printer driver supplied in the Supplemental Driver Library for Microsoft Windows 3.00.  The printer Setup dialog box in the Control Panel will let you choose a 22-inch paper size in the landscape mode, but the driver will only print up to 17 inches on the first page and print the remaining 5 inches on the second page.  You may also receive the error message "Unable to print to device selected."

Solution:

Kodak is researching this problem and is currently working on a solution. For explanation, contact Kodak Product Support.

Reference:   Kodak Product Support, (800) 344-0006.


Windows 3.0 on IBM ProPrinter X24e/XL24e
Problem:  Windows 3.0 on IBM ProPrinter X24e/XL24e

Printing from Microsoft Windows to the IBM Proprinter X24e and XL24e may produce a white line through the printed characters.  The white line comes in 11/16 inch intervals.

Solution:

To correct this problem, replace the EPROM chip in the printer.  This upgrade is available from IBM.  The updated EPROM chip ID number is 49F5263.  Note: You need to verify that you have the old EPROM.

To verify that an old EPROM is present:

1. Turn off the printer.

2. Make sure that the printer has 8.5-inch or 13-inch paper installed,   depending 	upon whether it's a 4207 or a 4208 (narrow or wide carriage).

3. Press and hold the ProPark button.

4. Turn the printer back on.

5. When the printer starts printing, release the ProPark button.

6. Power the printer off after it has printed one page.

7. Locate the seven-digit alphanumeric part number in the upper-left corner of the 	printout.

8. If it is NOT 49F5263 and the printer exhibits the "White Line" problem,   IBM 	Service can be called to perform the printer update.

Explanation:

This correction will be performed by IBM on-site.  Call IBM service at 1-800-IBM-SERV and state that you need "ECA002" for the IBM 4207 or 4208 printer.  The service will be provided at no charge.  This does NOT apply to the older X24(4207-001) and XL24(4208-001) printers but ONLY to the X24E and XL24E printers, which are also called the 4207-002 and 4208-002.


Fixing Offset Problem On The Star NX 1000
Problem:  Fixing Offset Problem On The Star NX 1000.

The Star NX 1000 which automatically feeds an inch when the paper loads.

Solution:

Here is one way to fix a top offset problem on the Star NX 1000 which automatically feeds an inch when the paper loads.  Create a form with a 0" top offset so the text lines will not print over one another.  Then load the page as usual, reverse micro feed down, shut the printer off and turn it back on.  This will eliminate the extra inch at the top.


QMS PS 2200 Problem printing 11" X 11"
Problem:  QMS PS 2200 Problem printing 11" X 11".

Trouble printing 11" x 11" on QMS PS 2200 when the left margin was printing at 2" and text on the right margin was overlapping leaving about a 3" right margin (margins were set to 1").

Solution:

Changing the paper size to 11" x 17" and adding 6" to the bottom margin solved the problem.  Make sure the sheet feeder for this printer is selected and set the form for whatever bin you  prefer (we used bin 1).  There are sheet feeder codes in the driver to accommodate 11" x 17", Letter, Legal, and a4 paper sizes but not 11" x 11".


Driver Problems

A printer driver is a program that communicates specific information about your system fonts to your printer.

Specific Conflicts

~Kodak DiconiX 150+ Windows Printer Driver

~Improved HP DeskJet Drivers

~Epson LX 810 Sheet Tear Off Doesn't Work

~Plotting with the IBM XY749 Plotter

~TrueType Problem with Blazer Star II Laser

~Screen redraw is slow with ATM

~"ATM fonts and PostScript printer fonts don't match" error

~ATM Fonts aren't available on Plotters

~Screen redraw is slow with ATM

~"ATM fonts and PostScript printer fonts don't match" error

~Some ATM Fonts Print Incorrectly

ATM Fonts aren't available on Plotters

with Applications

~Excel 2.x: Titles with Generic/Text Only Driver


TrueType Problem with Blazer Star II Laser Printer
Problem:   TrueType Problem with Blazer Star II Laser Printer

If you print a file with TrueType fonts from the Microsoft Windows operating system version 3.1 to a Sanyo Blazer Star II laser printer, the printout may be missing characters.

Solution:

To correct this problem, you must upgrade the printer's ROM chips to version 1.3.  To obtain this upgrade, contact Sanyo at (408) 988-6072, and ask for the Blazer parts department.

To determine what ROM version you have, do a self test on the printer.  The test page lists the version.

Explanation:

Steps to Reproduce Problem

1. Start Microsoft Windows Write (WRITE.EXE).

2. Type several lines of text. Change the point size character formatting for the text.

3. From the File menu, choose Print, and choose the OK button.


Printing Graphics Problems

This section covers problems associated with printing graphic outputs.  This includes bitmaps from paint files and graphs from spreadsheets.

Specific Conflicts

~Incomplete printing with downloadable fonts

~Panasonic KXP4450 Timeout Printing Graphics

~Missing text, truncated, blank, no text

~GRAPHICS.COM COLOR8 640 x 480 Mode printing

~Printing 360 dpi Graphics on NEC P5200/P5300

~Graphic Lines do not print


Incomplete Printing with Downloadable Fonts
Problem:  A possible solution for incomplete graph printing on printers that can take downloadable fonts.

Explanation:

If a printer has less memory free in it's internal buffer than a printer driver is designed to anticipate, graphs may not be able to print completely. For instance, if you set up Graph Printer1 to print to an HP LaserJet with 512k of internal RAM and that RAM is not available for the print job being sent by Paradox at print time, the graph may not print properly.  Frequently only part of the graph will print then the paper is ejected by the printer.

A possible cause of this memory depletion in the print buffer is the presence of downloadable fonts.

Solution:

Use either one of the following solutions:

1.  Power down the printer, then power back up.

2.  If the printer has a reset string that will clear the print buffer you could use a quick PAL Miniscript to send that string to the Printer prior to outputting a graph (for example, on an HP Laserjet the following command: Print "\027E"  may clear the print buffer).


Panasonic KXP-4450 Timeout Printing Graphics
Problem:  Panasonic KXP-4450 Timeout Printing Graphics

When printing graphics in High Quality on the Panasonic KX-P445 printer, the printer will generally print approximately 1.5 inches of the graphic before kicking to another page.  This is caused by the "time out" feature on the printer.  WordPerfect will take longer to load the next section of info than the timeout is default for.

Solution:

The fix is to turn off the "time out" or to change the amount of time.  Instructions are in the printer's user manual.


Missingtext, truncated, blank, or no text
Problem:  Missing text, truncated, blank, or no text in 1-2-3

When you create and display a graph, or try to print it, some or all of the text is not displayed or printed.  For example, the title, note, X-axis or Y-axis labels or legend might be missing.  Resetting and recreating the graph does not correct the problem.

Solution:

1. Check the amount of available memory (/ Worksheet Status).  Also check if   the MEM indicator is displayed at the bottom of the screen.  If the amount of available memory is low, part of the graph may not be displayed or printed.

2. When an insufficient number of files is assigned in the CONFIG.SYS file,   no text or only part of the text will be displayed or printed on a graph.  Type out the CONFIG.SYS and check for a FILES=20 statement.  If there is no Files statement, or if the number of files is less than 20, edit the   file to read FILES=20 (or more).  Reboot with the new CONFIG.SYS and try   to display or print the graph.

3. Check the 123 program directory to make sure the Printer Graphics Fonts   are present.  123 uses these fonts to produce the text associated with   graphs; such as, Legends, Titles and the X and Y-Axis labels.  Most of   these files will have either a .LRF or a .LVF extension.  For example, the Swiss Roman Font is AA012LAA.LRF and the Serif Roman Font is COMROM.LVF.

If these font files are either missing or corrupted, 123 may not print any text associated with a graph.  You could either reinstall 123 or   reinflate the font files from the original disks.


GRAPHICS.COM COLOR8 640 x 480 Mode Printing
Problem:  GRAPHICS.COM COLOR8 640 x 480 Mode Printing

When attempting to print a 640 x 480 graphics screen with GRAPHICS.COM and a type COLOR8 using the default GRAPHICS.PRO file  the left one third of the image is missing and the aspect ratio seems to be incorrect.

Solution:

The GRAPHICS.PRO file must be modified to include ROTATE on the PRINTBOX command line for 640 x 480 COLOR8.  After finding the COLOR8 section in the GRAPHICS.PRO file, you will find the following section of commands:

DISPLAYMODE 17,18;; 640x480

SETUP 27,51,14,27,110,1;; aspect ratio = 1:1

GRAPHICS 32,32,32,32,27,76,LOWCOUNT,HIGHCOUNT PRINTBOX STD,2,1

The PRINTBOX command should be changed to read as follows:

PRINTBOX STD,2,1,ROTATE

This change instructs GRAPHICS.COM to print in landscape mode; the full image will now be printed and the aspect ratio will be correct.   Further information about GRAPHICS.PRO is available in the application note PD0246 "GRAPHICS.COM and Graphics Profiles".  This application note can be obtained from Microsoft Product Support Services.


Applications' Problems

This section covers all the various programs you use to accomplish your daily tasks.

General Hints

Hints on Installing New Applications

Hints on Upgrading Applications

There are many kinds of applications.  Examples are given below each category.

See

SPREADSHEETS

Lotus 1-2-3, Microsoft Excel, Borland Quattro Pro

WORD PROCESSING

MS Word, WordPerfect, Lotus AmiPro

DATABASES

Lotus Approach, Borland Paradox

NETWORK

Look here for problems with applications running on networks.

UTILITY

Adobe Type Manager, Disk Compression

ACCESSORIES

Calculator, Notepad, Write

DEVELOPMENT TOOLS

Visual Basic


General Hints on Applications
General Hints

If an application requires an .INI file, make sure that it is intact.  A missing or corrupted .INI file will cause strange behavior in the application.  Most .INI files reside in the c:\Windows directory.

The [boot] section of the SYSTEM.INI file defines the system drivers used by Windows and other applications.  The drivers are defaulted to be in c:\windows\system, but they can be in any directory as long as they are specified in the section.

To insure that an application can be invoke, insure that the application

1. has its proper support components and that the components are accessible.

2. has the proper PIF set up which provides the optimal settings for the application.  This setup can be edited with the PIF Editor in Windows.

3. is associated with its data files.  This association can be set by the File-Associate option in File Manager.


Hints on Installing Applications
Hints on Installing New Applications

Use the following hints to ease later management problems.

1.  Install applications in a separate directory.

2.  The applications drivers are usually installed into the named directory.  Some applications will copy the applications system drivers into the named directory, some will install them into the default directory, namely C:\windows\system

3.  After the installation, take a look at SYSTEM.INI in the Boot section.  Note the change.  The change indicates what are the system drivers installed for the application.

4.  Make sure that the application drivers in the SYSTEM.INI [Boot] are specified with the correct path.  Note that the default path is C:\win\system if no other path is specified.   If the drivers are installed in different directory, make sure that it is reflected in the [Boot] section accordingly.

5.  If the application system drivers are installed in the C:\win\system directory, move them into the application directory.

6.  Make the proper changes in the SYSTEM.INI [Boot] section to reflect the new location of the drivers.


Hints on Upgrading Window's Applications
Hints on Upgrading Windows' Applications

Use the following hints to ease later management problems

1.  Rename the old application directory to something else first.  For example, Appl_OLD.

2.  Install application in a separate directory.

3.  The application drivers are usually installed into the named directory.  some applications will copy the application system drivers into the named directory, some will install them into the default directory, namely c:\win\system.

4. After the installation, take a look at SYSTEM.INI in the [Boot] section.  Note the change.

5.  Make sure that the application drivers in the SYSTEM.INI [Boot] section are specified with the correct path.  Note the default path is C:\windows\system if no other path is specified.  If the drivers are installed in a different directory, make sure that it is reflected in the [Boot] section accordingly.

6.  If the application system drivers are installed in the c:\windows\system directory, move them into the application directory.

7.  Make the proper changes in the SYSTEM.INI [Boot] section to reflect the new location of the drivers.

8.  Try out the new upgraded version of the application.  If it works fine, delete the old, renamed directory.


Spreadsheet Problems

REFERENCE

LOTUS 1-2-3

MICROSOFT EXCEL

OTHER


Problems with Excel

General Information

The Excel .INI File

Necessary Components for Excel to Function Properly

Specific Conflicts

with Hardware

with Printing

with Applications


Specific Conflicts between Excel and Hardware

Click on a topic below:

~Excel 3.0 and Fahrenheit 1280 Orchid Display

~Using Excel 3.0 with 8514 Video Driver

~Excel conflicts with Maynard Hard Disks

~Excel conflicts with Pointing Devices


Specific Conflicts between Excel and Printing

Click on a topic below:

~Character Missing When Print Titles Are Set.

~Epson FX-80/FX-100 Draft-Printing and Excel

~Excel 2.x: Titles with Generic/Text Only Driver

~Excel and TI OmniLaser

~Printing Excel Charts with Canon LBP 4 Driver


Specific Conflicts between Excel and other Applications
Specific Conflicts between Excel and other Application

Click on a topic below:

~A WinWord macro which uses DDExecute to communicate with Excel will cause a UAE.


Necessary Components for MS Excel
Necessary Components for Microsoft Excel

NECESSARY FILES

Excel requires a number of files to function properly.  They are listed below:

Windows subdirectory: [SYSTEM]

COMMDLG.DLL

SHELL.DLL

VER.DLL

SMALLB.FON -or- SMALLE.FON -or- SMALLF.FON  (2)

Windows subdirectory: [MSAPPS\PROOF]

MSSPELL.DLL

MSSP_AM.LEX  (3)

MSSP_BR.LEX  (3)

CUSTOM.DIC  (4)

Excel directory: [C:\EXCEL]

EXCEL.EXE

README.TXT

NETWORK.TXT

XL4.REG

XLCALL.DLL

CNF2INI.EXE

[EXCEL\XLSTART]

PSS.HLP

QEREADME.TXT

[EXCEL\EXCELCBT]

EXCELHLP.HLP	TRANS123.XLM	EXOTIC.FMT

PARTS.FMT	SCHEDULE.FMT	EXCELLES.CBT

SURVEY.XLW	WCOAST.XLW	APERTURE.XLW

BLUESKY.XLW	ELI.XLW	DIVISION.XLW

EXCELCBT.CBT	EXOTIC.WK1	PARTS.WK1

PHOTOS.XLW	SALES.XLW	SALESREP.XLW

SCHEDULE.WK1	TOOLS.XLW	YONDER.XLW

CBTLIB3.DLL	EXPORTS.XLW	XLBASICS.CBT

[EXCEL\QE]

ADDR.DBF	DEPT.DBF	EMP.CSV

EMP.DBF	EMP.DBT	EMP.TXT

EMP.XLS	EMPDEPT.NDX	EMPHIRE.NDX

EMPLNAME.NDX	LOC.DBF	QE.XLA

[LIBRARY]

EXCELINI.TXT

FILEFNS.DLL

FILEFNS.XLA

[LIBRARY\CROSSTAB]

ADDINMGR.XLA

CROSSFNC.XLA

CROSSTAB.XLL

CROSSTMP.XLT

[LIBRARY\CHECKUP]

REPORTS.XLA	SCENARIO.XLA	VIEWS.XLA

ADDINFNS.XLA	ALTSTART.XLA	AUTOSAVE.XLA

FLATFILE.XLA	GLOSSARY.XLA	DEBUG.XLA

CHANGER.XLA	SWITCH.XLA	SWITCHTO.XLA

WHATIF.XLA	AUDIT.XLA	COMPARE.XLA

SUMMARY.XLA	CHECKUP.DLL	CHECKUP.XLM

[LIBRARY\ANALYSIS]

ANALYSF.XLA	ANALYSIS.XLA	ANOVA.XLA

CORRELAT.XLA	ENF.DLL	FIN.DLL

FORECAST.XLA	FOURIER.XLA	REGRESS.XLA

STAT.DLL	TESTS.XLA

[LIBRARY\SLIDES]

SLIDES.XLA

SLIDES.XLT

XLSLIDES.DLL

[LIBRARY\COLOR]

AUTUMN.XLS	BLACKWHT.XLS	BLUERED.XLS

BLUES.XLS	DEFAULT.XLS	DUSK.XLS

PALETTES.XLA	PASTEL.XLS	RAINBOW.XLS

REDS.XLS	SUMMER.XLS	SUNSET.XLS

USER1.XLS	USER2.XLS	WINTER.XLS

YELGREEN.XLS

[LIBRARY\SOLVER]

SOLVER.DLL	SOLVER.XLA	SOLVREP.XLA

[EXAMPLES]

EXCELDE.EXE	TRANS.EXE	TRANSMP.XLM

QE.EXE	QE.HLP

[EXAMPLES/SOLVER]

AMORTIZE.XLS	BILL.XLT	REAKEVN.XLS

COLLEGE.XLS	COLLHELP.XLM	BUDGET.XLS

SALETRAC.XLW	STRUCTM.XLT	EXAMPLE.XLM

SOLVCHRT.XLC	SOLVER1.XLS	SOLVER2.XLS

SOLVER3.XLS	SOLVER4.XLS	SOLVER5.XLS

SOLVER6.XLS	SOLVEREX.XLS

[QE]

DBNMP3.DLL

QEXLA.DLL 	QEDBF.DLL	QEXLS.DLL

QEORA.DLL	ORA6WIN.DLL	QERDB.DLL

SQSAPIW.DLL	QESS.DLL	W3DBLIB.DLL

QETXT.DLL

[Optional Files]

EXCELLIB.CPT	ACCOUNT.CPS	ADDRESS.CPS

ADS.CPS 	AD.CPW 	CARPOOL.CPS

CHART.CPC 	COMMISS.CPS 	COMPARE.CPS

EXPENSES.CPS	FACILITY.CPS	FIRSTQTR.CPS

FORM.CPS 	INCCAT.CPS	INCOME.CPS

KWWHAT.CPM	LISTINGS.CPS 	MACRO.CPM

MACRO9.CPM  	MAILER.CPM	MONTHLY.CPS

MWPRA1.CPW	MWPRAC.CPW	NAMES.CPS

ORDER.CPS 	PAYROLL.CPS	PAYROLLF.CPS

QUARTER.CPS 	RACKCHRT.CPS	RACKS.CPS

RACKS.CPW	RACKSLS.CPS	REGION.CPC

REGION.CPS	REGION.CPW	REGION1.CPS

REGION2.CPS	REGION3.CPS	REGSALES.CPS

SALES.CPS	SAMPLES1.CPS 	SHEET.CPS

SLSPROJ.CPS	SUMMARY.CPS	TAXES.CPM

THIRDQTR.CPS	TUTOR.CPM	TUTOR2.CPM

ZEBRA.CPM

OPTIONAL UTILITY MACROS FILES

AUDIT.CPS 	COMPARE.CPM	CONSOL.CPM

DEBUG.CPM	DBREPORT.CPM 	FORMVIEW.CPM

GOALSEEK.CPM	WHATIF.CPM	CROSSTAB.CPM

In Config.SYS the statement below must exist:

PATH=C:\EXCEL

DEFAULT WIN.INI

A default WIN.INI is set up for Excel.  If things are different, make sure that they are functioning.

[Microsoft Excel]

;  Options is the sum of the following:

;  1=Turns on Scroll Bars, 2=Turns on Formula Bar, 4=Turns on Status Bar

; 16=Cells are referred to as A1, 32=Turns short Menus ON, 64=Excel Accepts DDE requests

;

Options=119

Open=Filename

Font=Tms Rmn,10

Maximized=1

Entermove=0

EMMReserved=128

ExtendedMemory=1

Randomize=0

; The following lines required Excel

Block=

Autodec=0

Menukey=

; The following line requires Excel 2.1 or higher.

Swapsize=128

; The following line requires Excel 2.1 or higher.

NewLook=1


WinWord Macros May Cause Errors in MS Excel
Problem:  A WinWord macro which uses DDExecute to communicate with Excel will cause a UAE.

This is a problem with Windows 3.0.  No work around exists.  Windows 3.1 provides DDEML which has fixed this problem.


Excel Conflicts with Maynard Hard Disk
Problem:  Excel conflicts with Maynard Hard Disk

If you have a Maynard hard disk, it is recommended that you use only version 2.4 or higher of the hard disk software.  An early version of the Maynard hard disk software may contain an error that prevents it from working correctly with Microsoft Excel.

No workarounds exist at this time.


Excel Conflicts with MS Bus Mouse
Problem:  Excel conflicts with Pointing Devices.

A Microsoft Bus Mouse may cause MS Excel not to respond to mouse movements.

Solution:

You may need to change the jumper J4 on the Bus Mouse adapter card.  The jumper is preset with the removable hood covering position 2.  This may cause problems with some video graphics adapters, IBM network adapters, IBM Enhanced Graphics Adapters, or with IBM PC/AT or compatibles (286, 386, or 496).  Generally, you should set the jumper to IRQ5 for the IBM PC AT and IRQ2 for the IBM PC XT.  For information on how to change the jumper, see the Microsoft Mouse User's Guide, pg 14-20.


Excel Conflicts with TI OmniLaser
Problem:  Excel conflicts with TI OmniLaser

Garbled output or messages such as "Can't write to printer" may result when printing to a TI OmniLaser. These problems may result when the printer is connected directly to the computer via its parallel port.

Solution:

Any one of the following workarounds can be used to solve the problem:

1.  Use the printer's serial port instead of the parallel port.

2.  Click retry if the spooler gives you a message that says it can't write tot he printer port.

3.  It is possible to cur the FAULT line (pin 32) on the Centronics parallel cable.  However, doing so will disable printer error feedback to the software.  Also, this should be done at your risk by an experienced technician.


Character Missing in Printout When Print Titles are Set
Problem:   Character Missing in Printout When Print Titles Are Set.

Hewlett-Packard (HP) LaserJet printers may omit a character from an Excel text string if the character's position falls where a vertical Print Title command break falls.  This situation occurs when the Print Titles execution includes columns.  This problem occurs because PCL hardware fonts cannot be clipped (meaning that characters cannot be partially printed).  A character that falls on a vertical Print Title break falls only halfway in the vertical Print Title, so a PCL printer is unable to print the character.

Solution:

Turning gridlines on or off will not affect this problem in any way.  The best workaround is to use one of the Windows' vector fonts: Modern, Roman, or Script.  These fonts will print correctly because they can be clipped.

Steps to Reproduce Problem.  Using an HP LaserJet as your default printer, do the following:

1.  Open a new worksheet.

2.  Enter the word "TITLE" (without the quotation marks) in cell A1.

3.  With cell A1 active, choose Font from the Format menu.  Check the printer Fonts check box.  Choose Courier 12 as the font and choose OK.

4.  Choose Column Width from the Format menu.  Type 3.5 in the Column Width box and choose OK.

5.  Select Row 1 and Column A.  Choose Set Print Titles from the Options menu.

6.  Print the file.

Note that the middle "T" in "TITLE" is missing in the printout.  It will appear in print preview.

Reference(s):    "Microsoft Excel User's Guide."  Version 3.0, pages 533-534.


Epson FX-80/FX-100 Draft Mode Printing with Excel
Problem:   Epson FX-80/FX-100 Draft-Mode Printing Problem with Excel.

When using the Epson FX-80/FX-100 driver while set for Draft Quality in Excel, the data in the print area does not print out, and the column headings appear at the bottom of the page.  To duplicate this problem, do the following:

1.  Select the Draft Quality box under the File Print command.

2.  Set Print Titles for a column (for example, column A).

3.  Set the Print Area to any area immediately adjacent to the print title (for example, B2:E10).

The printout appears to be correct in the print preview, but the data is lost and the column headings dropped to the bottom of the page once the spreadsheet is sent to the printer.

Solution:

No solution exists at this time.


Excel 2.x Print Titles with Generic/Text Only Driver
Problem:   Excel 2.x Print Titles with Generic/Text Only Driver

If a vertical print title is set in Excel when printing with the Generic/Text Only (or TTY) printer driver, the column with the print title in it is printed above the other columns.  Horizontal print titles print properly. This appears to be a problem with the TTY printer driver.

Solution:

Microsoft has confirmed this to be a problem in versions 2.0, 2.01, and 2.1. This problem was corrected with a newer version of the TTY printer driver that was shipped with Windows 3.0.


Using Excel 3.0 with 8514 Video Driver
Problem: Using Excel 3.0 with 8514 Video Driver

There is a problem with pattern redrawing with Microsoft Excel 3.0 when the 8514 video driver is installed in Windows.  The problem occurs when an area of an Excel spreadsheet is formatted in some pattern and then scrolled off the screen using the arrow keys or by using the mouse to click the scroll bar arrows (scrolling the pattern off the screen line by line).  After the pattern has been scrolled off and scrolled back onto the screen, it will no longer be smooth or uniform.  However, if you use the PGUP or PGDN key, or click the scroll bar itself with the mouse, to move the sheet a page at a time, and then use the same procedure to return to the patterned area, the pattern will be restored to its original condition.

Explanation:

Steps to Reproduce Problem

1.  Select any area on a spreadsheet.

2.  From the Format menu, choose Patterns.

3.  Choose the fifth pattern down in the list box.

4.  Choose OK.

5.  Note that the pattern is smooth and uniform.

6.  Hold down your DOWN ARROW key and scroll the patterned area off of the screen.

7.  Hold down your UP ARROW key to scroll the pattern back onto the screen.

The appearance of the pattern will no longer be smooth.

Solution:

Microsoft is researching this problem and will post new information as it becomes available.

Reference:  "Microsoft Excel User's Guide."  Version 3.00, page 27, 206.


Printing Excel Charts with Canon LBP4 Driver
Problem:  Printing Excel Charts with Canon LBP 4 Driver

When you use the Canon LBP-4 printer driver supplied with the Windows 3.0 disks, you may have problems printing Excel charts in the low and medium resolutions. The printout will only contain the tickmark labels for both the value and category axis as well as text. (Both unattached and attached text.)  However, you will be able to print the charts at a high resolution.

Solution:

Microsoft has confirmed this to be a problem with the Canon LBP-4  driver  supplied with Windows 3.0.  This problem was corrected with the Canon LBP-4  driver  in the Supplemental Drivers Library.  On the 5.25-inch disks, this  driver  is found on Disk 2.  On the 3.5-inch disks, this  driver  is found on disk 7.  After installing this  driver , Excel charts should print correctly in all resolutions.


Excel 3.0 Conflict with Fahrenheit 1280 Orchid Display Driver
Problem:  Excel 3.0 Conflict with Fahrenheit 1280 Orchid Display Driver

When using the Fahrenheit 1280 Orchid video display  driver with Microsoft Excel version 3.0 and creating a chart with the Chart tool from the tool bar, the resulting chart will appear empty on the spreadsheet.

Note:  The driver supplied with this card has not been tested to support Excel 3.0.

Reference:  Orchid Technology (415) 683-0300.

Solution:

Changing the display to standard VGA will correct the problem.


Problems with Lotus 1-2-3

General Information on 1-2-3

The Lotus .ini File

Specific Problems

with Hardware

with Printing

with System Configuration


Specific Conflicts between 1-2-3 and Hardware

Click on a topic below:

~Monochrome Display with 123W Multimedia SmartHelp

~Expanded Memory Error  with Lotus 123 2.x

~Data Query Extract has Missing Data


Specific Conflicts in Printing with 1-2-3

Click on a topic below:

~Printing Graphs in 1-2-3 with a Color Printer

~Incorrect Printing of Saved PIC or Metafile

~Line feeds and Page Advance with Okidata 93 and 1-2-3

~Y Axis Title Not Centered

~A Title Prints Only on the First page

~123W Release 4 Plotter Support and Related Printing Issues

~Graph Does Not Print Properly to a Plotter

~Using Internal Scaleable Fonts on a HP LaserJet III

~Memory Setting Not Holding for HP LaserJet III

~Cannot Reset HP LaserJet III Graphic Resolution

~Text on Graphs Is Not Displayed or Printed


Specific Conflicts between 1-2-3 and System Configuration

Click on a topic below:

~Running 1-2-3  Release 3 with MS-DOS 5.0

~Minimum Requirements for 123 for Windows 1.0 and 1.0a

~System Requirements for 123 Release 4 for Windows

~GPF Merging with 123 Release 4 File

~Not Enough Memory to Run 1-2-3 for Windows

~Second Set of Titles Appears in 1-2-3 after Exiting Allways


Expanded Memory Error with Lotus 1-2-3 2.x
Problem:  "Expanded Memory Error" with Lotus 1-2-3 2.x

If you select / Range Erase in an attempt to erase a cell, EDIT [F2] to modify a cell, or simply try to type over information in a cell with new data, 1-2-3 2.x displays the error "Expanded Memory Error".  Expanded memory that meets the Lotus Intel Microsoft (LIM) specifications is loaded on your computer.

The error usually occurs only when certain numbers are entered in the cell, and when UNDO is enabled.

Solution:

On any computer that is configured with expanded memory, there are always exactly four negative integers that cause the problem when they are entered into the worksheet.  The problem integers are the same integers as the four segment addresses of the expanded memory page frames on the computer.  For example, on a system with the page frame starting at E000, the four values would be -8192 (E000), -7168 (E400), -6144 (E800), and -5120 (EC00).

You only receive the expanded memory error when the physical page address that matches the integer does not have a page mapped to it; therefore, you can force the system to use enough memory to map each expanded memory page frame and consequently avoid the error.

The following steps will address a minimum of 64K of expanded memory on the user's PC, which is the size of a page frame, and consequently serve as a workaround for the problem:

1. Select / Worksheet Global Default Other Undo Disable, to disable UNDO.

2. Put the cursor in an unused column in the spreadsheet.

3. Enter  0.1  in the first row (row 1) of the blank column.

4. Select / Copy in the cell that now contains 0.1 .

5. Press ENTER.

6. Highlight the entire blank column.

7. Press ENTER to fill the column with the value .1.

You can now edit or delete the value in the problem cell.  Once you make any desired changes to their spreadsheet, you can select / Range Erase to delete the column of values entered with steps 2-5 listed above.

NOTE: This problem does not occur if the value displayed in a cell is the result of a calculation, even if the value is one of the four problematic integers. Users who continually encounter this problem should use the steps listed above to fill in the page addresses, and  then edit the problem cells and add the +0 to the value in the cell.  This process will convert the integer into a calculated entry and eliminate the error without changing the value of the cell.

The DOS manual has explanation on memory and page frames.


Data Query Extract has Missing Data
Problem:  Data Query Extract has Missing Data

After performing a  /Data Query Extract, some data is missing from the output range.  The correct number of records is extracted, but some of the columns in the output range are left blank.  The problem occurs randomly, and ONLY occurs when expanded memory is used.  This is caused by the fact that the query extract code fails to take necessary precautions when accessing data in expanded memory.

Explanation:

To understand why the problem occurs, here are a few basics of how expanded memory is used with 1-2-3.

Expanded memory is divided into blocks of 16K bytes, called pages.  These pages cannot be accessed directly by 1-2-3.  In order to read from or write to one of these pages, the page must be copied into conventional memory.

Four pages (64K) of conventional memory is set aside to hold copies of expanded memory pages, so that four expanded memory pages can be accessed at any one time.  When an expanded memory page is copied into conventional memory, the conventional memory page it replaces is copied back into expanded memory.  This process is called page mapping, or page swapping.  When 1-2-3 requests the contents of a spreadsheet cell, the page containing the contents of that cell is swapped into conventional memory, if necessary.  The previous contents of that conventional memory page is swapped back into expanded memory.  Since pages are swapped in and out of conventional memory without warning, 1-2-3 must take precautions to make sure that expanded memory data remains in conventional memory until that data is no longer needed.  In order to do this, 1-2-3 can "freeze" one or more of the pages in conventional memory, which prevents those pages from being replaced by new expanded memory pages.

When performing a /Data Query Extract, 1-2-3 must compare the contents of cells as follows:

1. The field names in the Input Range must be compared with the field names   in the Criterion range to determine which columns to use for selecting   records.

2. The field names in the Input Range must be compared with the field names   in the output range to determine which columns to extract to the output   range.

3. The values in the criterion range must be compared with the values in the   input range to determine which records to extract.

During the /Data Query Extract operation, 1-2-3 must compare one cell with one or more other cells.  In no case does 1-2-3 take measures to prevent the contents of the first cell from being removed from conventional memory before the comparison is complete.  For example, suppose that both cells contain data which reside in expanded memory, and that the contents of the two cells are in different expanded memory pages.  When 1-2-3 requests the contents of the first cell, the expanded memory page containing the cell's contents is copied into conventional memory, if necessary.  When the contents of the second cell is then requested, that expanded memory page is swapped into conventional memory, if necessary.  If the second page happens to replace the first one, the contents of the first cell will no longer be accessible.

The reported problems occur during the comparison described in item 2, above. 1-2-3 compares each field name cell in the input range with all field names cells in the output range, looking for matching columns.  At some point, the page containing the current input range field name is being swapped out of conventional memory, causing 1-2-3 to fail to detect a matching field name in the output range.  This results in missing data in the output range columns because 1-2-3 doesn't think those fields exist in the input range.  This problem could occur with any of the comparisons, although it has not been reported.  The nature of the problem is such that it will happen only with large worksheets using more than 64K (four pages) of expanded memory.  The problem is most likely to occur in worksheets which create and delete large amounts of data between /Data Query Extract operations.

Solution:

Unfortunately, there are no real solutions or workarounds.  It might help to save and then retrieve the file immediately before the /Data Query Extract is performed.  This will cause the data to be loaded into expanded memory sequentially.  As long as the input, criterion, and output ranges are close together (preferably in the same columns), saving and then retrieving the worksheet before the extract will increase the chance that all the data is loaded into the same set of expanded memory pages.


Printing Graphs in 1-2-3 with IBM Color Printer
Problem:  Printing Graphs in 1-2-3 with IBM Color Printer

When printing graphs in 1-2-3 Release 1A with the IBM Color printer at the default full and half sizes, the printer advances the paper approximately 3 inches before starting to print.  The graph will then run off the page if the paper has been aligned so that the perforations are level with the print head.

Solution:

The solution is to set the top margin to zero In PrintGraph (i.e. Options Size Manual Top 0).  This advances the paper only 1.25 inches and allows the graph to fit on the page.

To print more than one graph, also set Top-Of-Form on the printer.  This will allow the "page" and "Eject" commands to work correctly.  To set T.O.F. on the printer, do the following:

1.  Turn printer off line (by pressing Ready)

2.  Press Form Mode

3.  Press Initialize

4.  Press Ready ( to turn printer on line)

5.  Press Align and Go in PrintGraph to begin printing.


Y-Axis Title Not Centered
Problem:  Y Axis Title Not Centered.

When printing to a Dot matrix printer the Y Axis label does not Center on the Y Axis though it does preview correctly.  In Portrait Mode the Y Axis Label is too low and when printing in Landscape mode the Y Axis is too High. Postscript and Laser printers print fine though.

Solution:

This appears to be a problem with the Windows Print Drivers and 123W.  The only work around is to go into the graph edit mode, select Chart, Axis, Y, Options, Axis Title, and type in one space.  This leaves room to the left of the graph so text can be manually added to the graph.  After selecting OK two times click on the Draw, Text and type in the text that is desired.  Add this to the worksheet.  Then select Rearrange, Quarter_Turn, this puts the text in a vertical mode.  Now move the text to the left of the Y Axis.  The text will have to be placed higher than center when printing in Portrait mode, or lower than center when printing in Landscape mode.  Upon printing the graph the Text may have to be positioned higher or lower to correctly compensate for the misalignment.


Incorrect Printing of Saved PIC or Metafile
Problem:  Incorrect Printing of Saved PIC or Metafile

A graph which is correctly displayed and printed correctly in 1-2-3 3.0 is saved as a PIC file or a Metafile, the titles are shifted to the left side of the graph when displayed or printed through PrintGraph (PIC) or Freelance (PIC or CGM).

Solution:

1-2-3 estimates the amount of space that will be available for text centering in a PIC or Metafile.  The left justification of titles occurs if the font size and title length selected in 1-2-3 are too large to be centered in these file formats.

To eliminate the problem, reduce the number of characters in the title or choose a smaller text size number under /Graph Options Advanced Text (First or Second or Third).  For example, changing the size from 8 to 7 will result in centered titles.


A Title Prints Only on the First Page
Problem:  A Title Prints Only on the First page

To print a title area, consisting of several rows, only on the first page of a document follow this example.  A two row border should also print on all pages, including the first page.  The first printed page:

OVERSION: CODE: 02 PSEUDO CODE: 123456      TOTAL: $30,000

Client's Name	Amount  	Initiated By	Date Initiated

John Doe	$300	Jane	3/3/89

Ray Doe	$200	Jane	3/3/89

The column headings (Client's Name, etc.) should be printed on every page.

Solution:

A macro must be created which prints the title, does not re-align the page counter, sets the border, and then prints the range.  The following macro (also attached as a .WK1 file) solves this problem.

MACRO	DESCRIPTION

\a  /pp	Brings up printer menu

ohTHIS IS THE HEADER~q	Sets the header

rA1 B4~	Sets the TITLE range to print

ag	Aligns paper, prints TITLE

obrA7.A8~q	Sets the border

rA9.D90	Sets the print range

gpq	prints border/range & advances last page


Text on Graphs Is Not Displayed Or Printed
Problem:  Text on Graphs Is Not Displayed or Printed.

When creating or printing a graph, some or all of the text is not displayed or printed.  For example, the title, note, X-axis or Y-axis labels or legend might be missing.  Resetting and recreating the graph does not correct the problem.

Solution:

1. Check the amount of available memory (/ Worksheet Status).  Also check if   the MEM indicator is displayed at the bottom of the screen.  If the amount   of available memory is low, part of the graph may not be displayed or   printed.

2. When an insufficient number of files is assigned in the CONFIG.SYS file,   no text or only part of the text will be displayed or printed on a graph.  Type out the CONFIG.SYS and check for a FILES=20 statement.  If there is  no Files statement, or if the number of files is less than 20, edit the   file to read 	FILES=20 (or more).  Reboot with the new CONFIG.SYS and try   to display or  print the graph.

3. Check the 123 program directory to make sure the printer Graphics Fonts   are present.  123 uses these fonts to produce the text associated with   graphs; such as, Legends, Titles and the X and Y-Axis labels.  Most of   these files will have either 	a .LRF or a .LVF extension.  For example, the   Swiss Roman Font is AA012LAA.LRF and the Serif Roman Font is COMROM.LVF.

If these font files are either missing or corrupted, 123 may not print any text associated with a graph.  You can then either reinstall 123 or reinflate the font files from the original disks.


Running 1-2-3- Release 3 with MS-DOS 5.0
Problem:  Running 1-2-3  Release 3 with MS-DOS 5.0

Executing Lotus 1-2-3 Release 3 with MS-DOS 5.0 may cause any of the following problems:

-computer lock up when loading

-1-2-3- keyboard lock up

-having to press a key several times to get a response

-beeping when pressing a key

-typing a character and having a different character displayed

The following error message may also be encountered:

UNEXPECTED INTERRUPT

Solution:

Lotus provides a series of SET DOS16M environment commands to be used in the AUTOEXEC.BAT file to resolve these problems.

This information applies to Microsoft MS-DOS version 5.0.

Explanation:

These errors may occur if using a nonstandard technique for switching from protected mode to real mode.

The Lotus series of SET DOS16M commands are specific to certain computer configurations and may eliminate these errors.  These commands, as stated below, can be entered in at the MS-DOS prompt for testing before starting Lotus 1-2-3 Release 3.  Reboot the computer after trying each different command.  After finding the one that works, add it to the AUTOEXEC.BAT file using your favorite text editor or Notepad.

Command	Application

SET DOS16M=10

SET DOS16M=10,750	Use these commands for 80286 machines using

the "fast" method of switching from protected

 	to real mode.

SET DOS16M=9

SET DOS16M=9,750	Use these commands for 80286 machines using the

"standard" method of switching from

protected to real mode.

SET DOS16M=13	Use for AST Research 80286 machines with older

keyboard ROM chips.

SET DOS16M=7	Use for machines with older Phoenix Technologies ROM

chips.

SET DOS16M=6	Use for some AT&T PC 6300 series machine.

SET DOS16M=2	Use for IBM PS/2 80286 machines

SET DOS16M=3	Use for some 80386 computers without VCPI drivers.

If none of the above commands solve the problem, Lotus has a utility, available at no cost, called CHK1-2-3 that will identify the hardware in the system and suggest changes that will help run Release 3.  CHK1-2-3 can be obtained from a local Lotus authorized reseller, a Lotus sales representative, or a Lotus authorized training center.


Problems with Other Spreadsheets

Necessary Files for MS Works to Function Properly

Necessary Files for Quattro Pro to Function Properly

Specific Conflicts

with Always

~Graphs with International Characters, Allways 1.0 Limitation

~Second Set of Titles Appears in 1-2-3 after Exiting Allways

~SCROLL LOCK Problem with Allways

with Symphony

~Backing Up Symphony 2.2

with MS Works

~MS Works: Printing Landscape and Portrait


Necessary files for MS Works
Necessary files for Microsoft Works

The following files are necessary for MS Works to function properly:

MSWORKS.EXE	991200 	03-13-92	6:19p

MSWORKS.HLP	1265064	03-13-92	6:19p

SOLUTION.HLP	24290 	03-13-92	6:19p

SMALLB.FON	17408 	03-13-92	6:19p

SMALLE.FON	21504	03-13-92	6:19p

THESAUR.DLL	11255 	03-13-92 	6:19p

THESAUR.LEX	353587 	03-13-92	6:19p


Necessary Files for Quattro Pro

Quattro Pro for Windows has a number  of files necessary for proper execution.  They are listed below.  Check their sizes and dates as well as their names.

[Program Directory]

ODAPICFG.EXE	34832 	09-15-92

PXENGCFG.EXE	23859	07-10-92

QWUPDATE.EXE	70816	09-15-92

DBD.EXE	94336	09-15-92

QPW.EXE	2732032	09-15-92

DB.DLL	87984	09-15-92

OPTMIZ.DLL	87744	09-15-92

VER.DLL	9008	09-15-92

QPWQBE.DLL	56896	09-15-92

CONF.DLL	34816	09-15-92

PXENGWIN.DLL	241341	07-10-92

QLD.DLL	174080	 	09-15-92

QPSRV.DLL	476560 	09-15-92

QPWVIEW.DLL	176432	09-15-92

CUI.DLL	125954	 	09-15-92

[Windows\System]

TTYWIN.DRV	PXENGWIN.DLL

BWCC.DLL	LD.DLL

OPADI.CFG	ODAPI.DLL

ODAPIQ.DLL

The following files depend on Windows 3.0 or Windows 3.1 installation.  To be sure, copy the files from the Windows\System directory of the installation machine where Quattro Pro is installed.  If Quattro Pro is installed as a networked application and has been registered as a OLE application, the following files have to be at the local machines if the user runs the application locally.  More information is provided in the README.TXT in the program directory.

OLECLI.DLL*	OLEDRV.DLL*

SHELL.DLL*	WINHELP.EXE*

WINHEKP.HLP*

[QPW.ini]

[Quattro Pro for Windows]

SetupVersion=17

Display=None,Yes,Yes,Yes,A..B:A1..B2

International=$,Quattro Pro/Windows,Prefix,Parentheses,"1,234.56 (a1,a2)",MM/DD/YY (MM/DD),HH:MM:SS (HH:MM),Windows Default,English (American),No

Startup=H:\BIN\QPW,QUATTRO.WB1,\0,WB1,Yes,Yes,Yes

Macro=Both,No,Menu Bar

SpeedBar=


Graphs with International Characters  Allways 1.0 limitation
Problem:    Graphs with International Characters,  Allways 1.0 limitation

A graph brought into an Allways screen using /Graph Add is broken up and/or distorted with patches of black over it.

Explanation:

If international characters (i.e the British pound symbol) are in the graph's title, data-label or x-axis of a bar graph, the problem described above will occur.  This is a limitation of Allways 1.0.  Avoid using international characters when creating 1-2-3 PIC files for use with Allways 1.0.

Solution:

The user should call User Service directly at (800) 343-5414 for:

* An upgrade to Allways 1.01, which contains the "No EMM" Expanded Memory Patch and additional printer drivers

* Replacement of damaged disks

* Media swaps (e.g., exchange 3.5" for 5.25")

* Product swaps (e.g., exchange Symphony Allways for 1-2-3 Allways)

* Replacement of Allways manual

(CD/Prompt users can download the "No EMM" patch (AWEMM.COM) and the additional Allways printer drivers from CD/Prompt discs dated October 1989 or later)


MS Works: Problem Printing Both Landscape and Potrait Documents
Problem:   MS Works: Problem Printing Both Landscape and Portrait Documents

When printing two documents in succession, one with portrait orientation and the second in landscape (or vice versa), the second document will print in the wrong orientation.  For example, both may print in portrait, or both may print in landscape.     This is only a problem on autorotating printers.  This does not occur on printers requiring a separate landscape driver.  Examples of printers affected are the Hewlett-Packard (HP) IIP, IID, and III.  IBM 4019 and PostScript printers are also affected.

Solution:

When printing a document that has a different orientation from the ones that you have been printing, choose page Setup and Margins from the Print menu and press the ENTER key without making any changes.  The document will now print in the proper orientation.

Explanation:

In this case, the problem occurs because Works does not initialize the printer correctly.  Although the printer driver is correct, Works is not using it to properly reset the previously set margins on the printer. Entering the page Setup and Margins command and pressing ENTER enables Works to properly reinitialize the printer.

Microsoft is researching this problem and will post new information as it becomes available.


Sizing of Works v1.x, 2.00 Characters Gets Smaller
Problem:  Sizing of Works v1.x , 2.00 Characters Gets Smaller

Works Versions 1.x and 2.00 will print chart text and numbers in smaller sizes as the resolution setting is increased in the Print Settings dialog box if a chart font has not been selected for the text.

Solution:

To avoid this problem, select Chart View (ALT+V C), choose Title Font or Other Font from the Format menu, and choose a font other than the default Screen option.


Second Set of Titles Appears in 1-2-3 after Exiting Allways
Problem:    Second Set of Titles Appears in 1-2-3 after Exiting Allways.

When titles are set in 1-2-3, Allways is invoked and the cursor is moved to a position in the title area, a duplicate set of titles appears when returning to 1-2-3.  The steps to recreate the problem are as follows:

1. In a 1-2-3 spreadsheet, set a horizontal title by selecting /Worksheet   Titles Horizontal.

2. Invoke Allways.

3. Move the cursor to a title area.

4. Quit out of Allways. The title rows appear twice in 1-2-3.

Solution:

Pressing PGDN or PGUP will clear the second set of frozen rows.  If vertical titles (columns) are being used, BIG RIGHT (CTRL-[Right Arrow]), then BIG LEFT (CTRL-[Left Arrow]) will clear the second set of column titles.

This occurs because 1-2-3 does not permit the cursor to move into an area designated as a title, except by using [F5] ([GOTO]).  As documented on page 12-41 of the 1-2-3 2.2 manual, when [F5] is used, 1-2-3 displays a second set of titles immediately below the first set and moves the cell pointer to the specified cell in the second set of titles.  Allways DOES allow cursor movement into areas designated as titles in 1-2-3 so that the area can be formatted. 1-2-3 treats the Allways' entry into the title area as if [F5] had been used within 1-2-3 to enter the title area, i.e. it creates a second set of titles.


Problem Using SCROLL LOCK with Allways
Problem:  Problem Using SCROLL LOCK with Allways

Allways functions differently than 1-2-3 when highlighting a range with the SCROLL LOCK on.  The problem occurs when Allways is used in the text mode.  For example, a user highlights E1..M1 in 1-2-3 and then presses the left arrow a number of times.  The highlighted range decreases column by column, i.e., E1..L1, E1..K1, E1..J1, etc.

In Allways, the user highlights the same range.  Pressing the left or right arrow key has no affect on the range.  It remains fixed at E1..M1.  The up and down arrows seem to function correctly with the SCROLL LOCK on.

Solution:

The user should call User Service directly at (800) 343-5414 for:

* An upgrade to Allways 1.01, which contains the "No EMM" Expanded Memory  	Patch and additional printer drivers

* Media swaps (e.g., exchange 3.5" for 5.25")

* Product swaps (e.g., exchange Symphony Allways for 1-2-3 Allways)

* Replacement of Allways manual


Backing Up Symphony 2.2
Problem:  Backing Up Symphony 2.2

After installing Symphony 2.2 for the first time, the original Symphony disks are copied for backup purposes.  If an attempt is made to subsequently install Symphony 2.2 on another machine using the backup disks, the following error is displayed:

Wrong disk inserted. Please verify that Symphony Disk 2 is inserted in drive A, and press any key to continue.

On page 2-1 of the Symphony 2.2 Getting Started manual that backup copies of the disks can be made; but that the Symphony 2.2 SETUP program must be completed before the disks are copied.  This is because the INIT program must be executed before the Symphony 2.2 Setup disk can be copied.

There are no explicit directions for copying the disks, but you are usually encouraged to use the following DOS command:

COPY A:*.* B:

If this copy command is used, the disk signature files (DISK1, DISK2 etc), which are zero byte files, are not copied to the backup disks.  This is because DOS will not copy a zero byte file.

The SETUP program verifies that the correct disk has been inserted by checking for the existence of these disk signature files.  Since the file is not present on the copied disk, the error message above is displayed.

Solution:

Use the DOS DISKCOPY command to copy the disks for backup purposes.  The correct syntax is:

DISKCOPY A: B:

When the Setup disk is copied the following error will be displayed.

Unrecoverable read error on drive A: side 0 track 39. Target disk may be unusable

The error occurs because the Setup disk is formatted with a bad sector as part of the copy discouragement scheme.  The error can be ignored; the copied disks will be the functional equivalent of the originals.

Alternatively, it is possible to use the backup disks without the disk signature files and manually run the Setup program.  To do this, copy each of the disks and then run the inflate utility to inflate the files.  To inflate the disks, enter the command:

INFLATE -D *.*


Word Processing Problems

SEE

LOTUS AMIPRO

MICROSOFT WORD

WORDPERFECT

OTHER


Problems with AmiPro

General Information

Necessary Files for AmiPro v2.0 to Run Properly

The AmiPro .ini File

The Lotus .ini File

Specific Conflicts

"Unrecoverable Application Error" When Saving a File

GPF when Saving a File

GPF Merging with 123 Release 4 File in AmiPro v3.01

GPFwhen Using AmiPro Help

GPF when running Spell Check

GPF When Pasting

Close-Up May Cause GPF Error Message During Installation

"Error 106: " Message Appears Using ~CALMON.STY

AUTOSTY.SMM Macro Does Not Run

Error Running Grammer Checker

Error Message When Running The Tutorial

AmiPro Shortcut Keys do not work

With Printing

Error Messages While Printing

"Error: Printer Busy" Occurs While Printing in Ami Pro

Printing Files with Graphics Results in a UAE

"Unable to Print" Message using Generic Text Driver

Print Prints a Document Other than the Active Document

Unable to Print Multiple Copies

"Frame Protocol Error" Printing to Windows Printing System

With Networks

"Unable to Locate Compressed File" Message Installing Node


Necessary Files for AmiPro 2.0
Necessary Files for AmiPro v2.0 to Run Properly

AmiPro 2.0 requires a number of executable files to run properly.  These are listed below:

AMIPRO.EXE	1259520	2-17-92

AMIFM.EXE	61984	2-17-92

AMIHYPH.EXE	34848	2-17-92

AMIPRINT.EXE	33584	2-17-92

AMISK.EXE	5408	2-17-92

AMITHES.EXE	49865	2-17-92

AMIDLGED.EXE	53168	2-17-92

AMISPELL.EXE	105303	2-17-92

AMINET.DLL	6210	2-17-92

AMIPROUI.DLL	499376	2-17-92

AMIUICNT.DLL	45184	2-17-92

AMIFONT.DLL	32365	2-17-92

LTSICNO1.DLL	26768	2-17-92

AMIMEM.DLL	11824	2-17-92

AMICHART.DLL	161136	8-13-91

AMIDRAW.DLL	153904	8-21-91

AMIEQN.DLL	692528	2-17-92

AMIMACRO.DLL	165456	2-17-92

AMIICN8.DLL	112992	2-17-92

DRAWMAN.DLL	51405	8-21-91

PXENGWIN.DLL	201431	2-17-92

AMIICNE.DLL	43728	2-17-92

AMICNV.DLL	53488	2-17-92

AMIIMAGE.DLL	95856	2-17-92

AMIPAINT.DLL	32992	2-17-92

AMIQIMP.DLL	4784	2-17-92

AMIWMF.DLL	11792	2-17-92

In AMIPRO.INI the following lines should exist:

[AmiVISD]

AmiOLE=AmiOLE.dll,.ole,.ole,Native,ObjectLink

Windows Metafile=AmiWMF.dll,.wmf,.wmf,CF_METAFILEPICT

Windows Bitmap=AmiPaint.dll,.bmp,.bmp,CF_DIB,CF_BITMAP

AmiImage=AmiImage.dll,.tgf,.tgf

AmiDraw=AmiDraw.dll,.sdw,.sdw

AmiChart=AmiChart.dll,.sdw,.sct

AmiEquation=AmiEqn.dll,.tex,.tex

[AmiPro]

VISDNonImportable=AmiImage.dll,AmiChart.dll,AmiOLE.dll,Aminw.dll

application1=ASCII,T,.*,ASCII.FLT,C:\PACIOLI

application2=Samna Word,T,.*,SAMNA.FLT

application3=TIFF,B,.TIF,TIFF.FLT

application4=PCX,B,.PCX,PCX.FLT

application5=WordPerfect 5.0 & 5.1,T,.*,WP.FLT,E:\ACTWIN\DOCS

application6=WS 2000 ver 1.0,T,.*,WS2000r1.FLT

application7=WS 2000 ver 3.0,T,.*,WS2000r3.FLT

application8=AdvanceWrite,T,.*,SAMNA.FLT

application9=Microsoft Word,T,.*,WORD.FLT,E:\ACTWIN\DOCS

application10=MultiMate,T,.DOC,MM.FLT

application11=DCA/FFT,T,.*,FFT.FLT,E:\TAP

application12=Navy DIF,T,.*,DIF.FLT

application13=WordStar,T,.*,WS50.FLT

application14=Lotus PIC,B,.PIC,PIC.FLT

application15=Windows Write,T,.*,WRITEFLT.FLT

application16=1-2-3,X,.W*,123.FLT

application17=WordPerfect ver 4.2,T,.*,WP42.FLT

application18=DCA/RFT,T,.*,RFT.FLT

application19=PeachText,T,.*,PEACH.FLT

application20=Enable,T,.WPF,ENABLE.FLT

application21=dBase,X,.DBF,DBASE.FLT

application22=DIF,X,.DIF,SSDIF.FLT

application23=Excel,X,.XLS,EXCELFLT.FLT,Biff

application24=SuperCalc,X,.CAL,SCALC.FLT

application25=Rich Text Format,T,.RTF,RTF.FLT,Rich Text Format

application26=Word for Windows,T,.DOC,WWORD.FLT,E:\UNNI

application27=Exec MemoMaker,T,.*,EMM.FLT,C:\BIZPLAN

application28=SmartWare,T,.DOC,SMART.FLT

application29=Manuscript,T,.doc,mscript.flt,E:\TAP

application30=Ami ver 1.0,1,.SAM,0

application31=Excel 3.0,X,.XLS,EXCELFLT.FLT,Biff

application32=Paradox,X,.DB,PARADOX.FLT

application33=E-Mail,T,.*,email.flt

application34=CGM,B,.CGM,cgm.FLT

application35=EPS,E,.EPS,EPS.FLT

application36=HPGL,B,.PLT,HPGL.FLT

application37=1-2-3 rel 3,X,.WK3,123ver30.FLT

application38=<>,?,.SDP,AP.FLT

application39=Freelance,B,.DRW,FLFLT.FLT

application40=DisplayWrite 4,T,.doc,dw4.flt

application41=DrawPerfect,B,.WPG,WPG.FLT

isd1=Image P&rocessing...,AmiImage.dll,Adjust the appearance of gray level scanned images

isd2=&Drawing...,AmiDraw.dll,Create and edit an object-based picture in a selected frame.

isd3=&Charting...,AmiChart.dll,Create and edit a chart in a selected frame.

isd4=&Equations...,AmiEqn.dll,Create or edit scientific and mathematical formulas and equations.

thes4=amithes1.exe


Problems with MS Word

General Information

Necessary files for MS Word for Windows v1.0

Necessary files for MS Word for Windows v2.0

Optimizing MS Word for Windows

Specific Conflicts

with Hardware

with Printing

with Networks


Specific Conflicts between MS Word and Hardware

Click on a topic below:

~MS Word 5.0 Hangs Unpredictably

~Glossary Entries cannot be 10 Point for WinWord v1.0 and 1.1

~Unpredictable behavior in MS Word


Specific Conflicts in Printing with MS Word

Click on a topic below:

~A Page Prints but is Incorrectly Formatted in MS Word.

~Printer Advances but doesn't Print in MS Word.

~Word Printing Pages or Selected Text to a File

~HP II, Vector Fonts, and Landscape Printing in MS Word

~Printing with Selection or Pages in the Range

~Word 5.0: Printing Problem with HP DeskJet Downloadable Driver

~Printing in MS Word with 360 dpi Graphics on NEC P5200/P5300

~NEC ProSpeed 386 and Internal Screen Display


Specific Conflicts with MS Word on Networks

Click on a topic below:

~"There was a problem writing.." Error on Banyan VINES


Optimizing Word for Windows
Hints:  Optimizing Word for Windows Performance

Use the Correct Printer Definition.  Make sure that the fonts used by WinWord are also part of the current printer definition.  The WINWORD.INI file keeps information about the fonts used by WinWord.  This list will not be updated when the printer setup is changed via Windows' Control Panel.  To update the WINWORD.INI, select File-Printer Setup, then select the printer, and click OK.

Turn View Preferences - Pictures to OFF.  This can drastically improve WinWord's screen redraw speed if the document includes bitmaps.

Turn TABLE GRIDLINES to OFF.

Turn View Page - Text Boundaries to OFF

Turn View Page mode to OFF by turning off all View Page choices.

Turn Draft Mode to ON.

Turn OFF Background Pagination in Tools-Options-General.

Check the WIN.INI for the portion of Winword to make sure that no major deviation has been provided.  The portion is described as follow:

[Microsoft Word]

; Set Conversion to No to import nonnative formats as plain text.

Conversion=Yes

; The following lines is set equal to the number of text import filters

CONVNUM=1

; All your installed text import filters will be listed here.

CONV1="Word for DOS" D:\WW\CONV-WRD.DLL ^.DOC

; You can set the default extension to "WRD" or whatever you like.

doc-extension=doc

; Tell Winword the directory containing your document templates

dot-path=c:\winword

; Tell Winword the directory containing  your WINWORD.INI file

ini-path=c:\winword

; Tell Winword teh directory containing LEX-AM.* spelling files

until-path=c:\winword

;  Set Winword's insert-date format

dateformat=MMMM d, yyyy

; Set Winword's insert-time format

timeformat=h:mm am/pm

; Set Newlook to "0" for 2-D instead of 3-D buttons (winword 1.1)

NewLook=1

; Don't use this line unles Winword has not enough RAM to load.]

; EMMLimit=512

[WWFilters]

; All installed graphic filters will be listed here.  Important: labels to left of "=" must not exceed 330 characers total in this section.

Paintbrush PCX=PCXIMP.FLT,PCX

[PCWordConv]

; Set ConverMerge to No to convert chevrons as plain text.

ConvertMerge=Yes

; Set StyleDialog to No to directly format imported DOS Word Files

StyleDiaglog=yes


Necessary Files for MS Word for Windows 1.0
Necessary files for Microsoft Word for Windows 1.0

MS Word has two required executable files.  The first is WINWORD.EXE.  This file should be 1268224 bytes in size and be dated 1-21-91.  The second is CommDlg.dll.  CommDlg.dll should be 89248 bytes long and dated 3-10-92.  If either of these files is missing then Word will not run properly.  To check on these files, use File Manager in Windows and open the WINWORD directory.  In DOS use DIR WINWORD to get a complete list of the files.

MS Word has display requirements.  In the SYSTEM.INI file the [BOOT] section should have display set to VGA.DRV.  Use your favorite text editor, like Notepad in Windows, to open the SYSTEM.INI file and check the value of display.  Change an incorrect value and save the changes.  The changes will become active after rebooting the system.

MS Word requires that Buffers=30 in the CONFIG.SYS file.  MS Word also requires that Files=30.

Use a text editor to verify these values and make any changes necessary.  Save any changes.  These changes will become active after rebooting the system.

SUMMARY

Executables	Size	Date

WINWORD.EXE	1268224	1-21-91

COMMDLG.DLL	89248	3-10-92

Files	Requirements

SYSTEM.INI	[BOOT]

display=vga.drv

CONFIG.SYS	Buffers=30,2

Files=30,2

MORE


Necessary Files for MS Word for Windows 2.0

MS Word has two required executable files.  The first is WINWORD.EXE.  This file should be 1268224 bytes in size and be dated 10-21-91.  The second is CommDlg.dll.  CommDlg.dll should be 89248 bytes long and dated 3-10-92.  If either of these files is missing then Word will not run properly.  To check on these files, use File Manager in Windows and open the WINWORD directory.  In DOS use DIR WINWORD to get a complete list of the files.

MS Word has VGA display requirements.  In the SYSTEM.INI file the [BOOT] section should have display set to VGA.DRV.  Use your favorite text editor, like Notepad in Windows, to open the SYSTEM.INI file and check the value of display.  Change an incorrect value and save the changes.  The changes will become active after rebooting the system.

MS Word requires that Buffers=30 in the CONFIG.SYS file.  MS Word also requires that Files=30.

Use a text editor to verify these values and make any changes necessary.  Save any changes.  These changes will become active after rebooting the system.

SUMMARY

Executables	Size	Date

WINWORD.EXE	1268224	10-21-91

COMMDLG.DLL	89248	3-10-92

Files	Requirements

SYSTEM.INI	[BOOT]

display=vga.drv

CONFIG.SYS	Buffers=30,2

Files=30,2

MORE


Unpredictable Behavior of MS Word
Problem:  Unpredictable behavior in MS Word

MS Word may have problems with ALT+Tab and ALT+Spacebar to format characters.

Solution:

No workarounds exist.  Upgrade to version 5.0a.


Glossary Entries for WinWord
Problem:  Glossary Entries cannot be 10 Point for Winword v1.0 and 1.1

It is not possible to insert a glossary entry of point 10 into a document.  WinWord always changes it to 12 points.

Solution:

The workaround is to leave the Normal style defined as a 10-point font in the Normal template, and use another template, with a different name, to define the new type.


MS Word 5.0 Hangs Unpredictably
Problem:  MS Word 5.0 Hangs Unpredictably

If Word is configured to use 43- or 50-line text mode and the Video Adapter is VGA or EGA then Word may hang unexpectedly.  In Windows Standard mode, Word will run as a full screen and have no problems. However, in Enhanced mode, Word may freeze.

Solution:

To fix, perform the following steps:

ALT + Enter to return Word to full-screen mode

or

Pull down the Control menu, click Settings, then click Full Screen.  Word with DOS full screen will be restored.


Printer Advances But Doesn't Print in Word
Problem:  Printer Advances but doesn't Print in MS Word.

The printer advances, or ejects a page, but doesn't print.

Solution:

Choose the Page Setup command from the Format menu, and then select the Paper Source option to make sure you have selected the correct paper source.  The names of the paper source options in the Page Setup dialog box may differ form the ones that follow, depending on your printer.  Default Tray, Upper Tray, Lower Tray, Envelope, and Manual are used for sheet feeders.  Default Tray is the default paper source for all printers, including dot-matrix and laser printers.  manual is used when you want to feed paper into the printer one sheet at a time.

You can also set the printer's paper source by using the Print Setup command on the File menu.  However, the settings in the Page Setup dialog box override the settings in the Print Setup dialog box, unless the settings in the Page Setup dialog box are for the Default Tray.  In this case, Word uses whatever paper source is set in the Print Setup dialog box as the default paper source.  For example, if both the First Page and Other Pages settings in the Page Setup dialog box are set to Default Tray , and the setting in the Print Setup dialog box is "Upper Tray," then Word uses the printer's upper tray as the paper source.  If the printer has only one tray, Word uses that tray.


Incorrectly Formatted Print in Word
Problem:  A Page Prints but is Incorrectly Formatted in MS Word.

A document prints, but it doesn't look the way you expected.

Solution:

If single underlining, word underlining, double underlining, or strikethrough formatting isn't printed correctly, add the line UNDERLINEMODE=1 to the [Microsoft Word] section of the WIN.INI file.  You can modify this file by choosing Options from the Tools menu, then selecting the WIN.INI category.

With Windows version 3.0, some printers cannot print a document with more than one orientation.  If you have formatted your document with more than one orientation and you have a printer that cannot print the document correctly, Word presents a message that suggests that you change the page size for the section whose orientation differs form the printer's.  for example, if the printer's orientation is portrait, as set in the Print Setup dialog box, and part of the document is formatted as landscape, that part of the document will not print correctly, unless you change its orientation to portrait.

To check your printer when the pages are formatted incorrectly, the margins are incorrect, or the document paginates incorrectly:

Check your formats for accuracy, especially font and point size, in the Character dialog box (Format menu) or in the Font and Point boxes on the ribbon.

Check the Print Setup dialog box (File menu) to make sure the correct printer is selected.

Check the Page Setup dialog box of the Page Setup command (Format menu) to make sure you have selected the correct paper source.

Check your printer switches to see if the proper modes have been set.  for some printers, Word may not be able to override these settings.

Note:

Some laser printers, such as those in the Hewlett-Packard LaserJet family, cannot print closer to the edge of the page than .25 or .50 inch.  Any value you enter in the Page Setup dialog box (Format menu) that is less than this measurement will cause the printer to lose text.  For more information, read the manual that comes with your laser printer.


Word Printing Pages or Selected Text to a File
Problem:   Word Printing Pages or Selected Text to a File

In Word Version 4.00, one of the following two problems can occur when trying to print an interior portion of a document to a file by choosing Selection or Pages in the "range:" field of the Print Options command before executing the Print File command:

1.  The resulting file does not contain the printer initialization sequences from Byte 0 of the PCSD table of the printer driver.

2.  The file contains a corrupted version of the initialization sequence.

This problem is most apparent when printing to a PostScript printer that produces no printout if the initialization sequence is missing or corrupted.

Solution:

Microsoft has confirmed this to be a problem with Word Version 4.00.  This problem was corrected in Word Version 5.00.


HP II, Vector Fonts, and Landscape Printing in MS Word v2.0
Problem:  HP II, Vector Fonts, and Landscape Printing in MS Word v 2.0

Explanation:

On a Hewlett-Packard (HP) LaserJet Series II printer, Microsoft Word for Windows version 2.0 has difficulty printing the following Windows version 3.0 vector fonts: Modern, Roman, and Script (in certain cases).  The printout appears with a blank space where the text should appear.  This problem occurs with both versions 3.3 of the HPPCL.DRV printer driver.

This problem only occurs when ALL of the following conditions exist:

 - You are printing in landscape mode, and

 - You select the Custom Size option in the page Setup dialog box, and

 - You use any size Windows version 3.0 vector font.

Steps to Reproduce Problem

1. From the File menu, choose Print Setup (ALT, F, R). Select the HP LaserJet   II in printer Setup dialog box, and choose the OK button.

2. From the File menu, choose New, and choose the OK button.

3. From the Format menu, choose page Setup (ALT, T, U).

4. Select the Size and Orientation option button. From the Paper Size box,   select Custom Size. Set a paper size of 9.5-inch width and 4.13-inch   height. In the Orientation box, select the Landscape option button.

5. Choose the OK button.

6. From the Format menu, choose Character, select the Courier font, and   choose the OK button. Type one line of text.

7. From the Format menu, choose Character, select the Script font, and choose   the OK button. Type another line of text.

8. From the File menu, choose Print, and choose the OK button.

Solution:

There is only work-around:  If you print in portrait orientation with a custom paper size and vector fonts, no printing problems occur.  You can also print in landscape orientation on standard paper sizes with vector fonts without any problems.  This problem does not occur with the internal Courier font, only with the Windows version 3.0 vector fonts.


Printing with Selection or Pages in the Range
Problem:  Printing with Selection or Pages in the Range

In Word Version 4.00, one of the following two problems can occur when trying to print an interior portion of a document to a file by choosing Selection or Pages in the "range:" field of the Print Options command before executing the Print File command:

1.  The resulting file does not contain the printer initialization sequences from Byte 0 of the PCSD table of the printer driver .

2.  The file contains a corrupted version of the initialization sequence.

This problem is most apparent when printing to a PostScript printer that produces no printout if the initialization sequence is missing or corrupted.

Solution:

Microsoft has confirmed this to be a problem with Word Version 4.00.  This problem was corrected in Word Version 5.00.


NEC ProSpeed 386 and Internal Screen Display
Problem:  NEC ProSpeed 386 and Internal Screen Display

The NEC ProSpeed 386 is supplied with VGA-compatible video and is recognized as such by Word version 5.00.  However, this is correct only when using an external monitor.  The internal screen is capable only of displaying EGA resolution.  When Word is set up, EGA must be explicitly selected as the video type.

Solution:

A problem will occur only when using the video modes specific to VGA (modes 3, 5, 6, and 8).  When using Print Preview with the VGA video  driver , the command menu is pushed off the bottom of the screen.


"There was a problem writing.." Error on Banyan VINES
Problem:  "There was a problem writing.." Error on Banyan VINES

After a user starts Microsoft Word for MS-DOS version 5.5 from the Word program directory on a Banyan VINES network, the following error message may appear when Word tries to save a file to the program directory:

There was a problem writing to a disk or to a device

The message will be displayed if the user has Read-only access to the Word directory.

Solution:

If you receive this error message, save the file to a directory for which you have Modify access.

Explanation:

Read-only access to the Word program directory is the correct access for all users when running Microsoft Word.  In the Banyan VINES environment, Read access is similar to Novell's Read, Open, Search rights.  Modify access is similar to Novell's Read, Open, Search, Create, Delete, Modify, Write rights.


Printing with Word 5.0 and HP DeskJet Downloadable Driver
Problem:  Printing with Word 5.0 and HP DeskJet Downloadable Driver.

There are three problems with the HP DeskJet drivers currently shipping on the Word version 5.0 Supplemental Printers disk.  The problems occur only when using soft fonts and the DESKJETX.PRD and corresponding DAT files.  The three problems and their solutions are detailed below.

Problem 1: The Universe 18 and 24-point fonts both print as either 14 or 15 point. If you download the 30-point Universe font, the 18 and 24-point fonts both print as 15 point; otherwise, they both print as 14 point.

Problem 2. When downloading the Helvetica 8 font, a code that is part of the download escape sequence prints in the upper left margin of your document. If the   HP DSU download utility is used to download, this code does not appear.

Problem 3. The DESKJET3.PRD does not download the ASCII set. The DSU download utility that comes with the soft fonts allows you to download the 7-bit ASCII set containing 128 characters, but not the set containing 255 characters. This saves download time and memory space and allows you to use more fonts.   Although the documentation indicates DESKJET3.PRD allows you to download the 7-bit ASCII set, it actually sends the entire character set. You can avoid this by using DSU and specifying only ASCII characters to be downloaded.

Solution:

Printer drivers that correct problems on the Hewlett-Packard (HP) DeskJet and DeskJet Plus are available as on the Supplemental Printer Kit for Microsoft Word for MS-DOS version 5.5b.  You can obtain the Supplemental printer Kit from Microsoft End User Sales at (800) 426-9400.  If you call from outside the United States, contact Microsoft International User Service at (206) 936-8661.


Printing in MS Word with 360 dpi Graphics on NEC P5200/P5300
Problem:  Printing in MS Word with 360 dpi Graphics on NEC P5200/P5300.

Microsoft Word version 5.0 is unable to achieve satisfactory results when printing 360 dpi graphics with the NEC P5200/P5300 printer.  As a result, Word supports a maximum of only 180 dpi graphics.

Solution:

No solution at this point.


Problems with WordPerfect

General Information

The WordPerfect 6.0 .ini File

Improving WordPerfect Performance

Specific Conflicts

with Hardware

with Printing

with Windows

with Applications


Specific Conflicts between WordPerfect and Windows

Click on a topic below:

~Windows freezes in WordPerfect


Specific Conflicts between WordPerfect and Hardware

Click on a topic below:

~Memory Parity NMI Interrupt in WordPerfect

~Using F10 to save files to Floppy doesn't work in WP.

~Internal stack overflow error in WordPerfect

~Display Pitch Problem Helped by Different Screen Font

~"Device Driver Problem" while using LaserTools' Fonts on the Fly

~Mouse Pointer disappears in Windowed WordPerfect.

~Summagraphics Mouse Conflicts with WordPerfect

~Index Generation HangingPRZ_APP_WP_WPER_IND


Specific Conflicts in WordPerfect with Printing

Click on a topic below:

~Dropped Codes in the Tandy DWP IIB Driver in WordPerfect 5.0

~Line Spacing Problem With R Cartridge On HP Laserjet+

~Fixing an Outdenting Problem

~Print Text On page Overprinting Text In Endnotes

~WordPerfect Double Underline And Shadow Print Only Once

~Printing Bitstream Custom Character Set on WordPerfect

~WordPerfect v5.0 's (6/12/89 Release) Top Margin

~IBM Quietwriter Printers - Horizontal Spacing Problem

~WordPerfect Style For Pleading Causes Problem With Page Numbering

~Endnotes Created In Landscape Problem

~Printing Superscript And Subscript After Italics

~Re-selecting Printer to Clear Margin


Specific Conflicts between WordPerfect and other Applications

Click on a topic below:

Facelift for Windows' Line Draw displays incorrectly in WordPerfect

Close-Up and WordPerfect cause an Application Error


Facelift for Windows' Line Draw displays incorrectly in WordPerfect
Problem:  Facelift for Windows' Line Draw displays incorrectly in WordPerfect.

If you are using FaceLift for Windows, and have selected a Windows printer driver in WordPerfect for Windows, and are using the Line Draw feature in WordPerfect for Windows, characters in the Line Draw dialog box will display incorrectly.  These line draw characters also display incorrectly when you use Draft Mode to edit your document.  This is a display problem only; the characters will print correctly.

Solution:

To correct the display problem,

1  Insert the following line into the WIN.INI file, in the [Typefaces] section, immediately below the "Active=" line:  NoSubstVectFonts=1.

2  Exit Windows.

3  Delete the FaceLift file CACHEDMP.CCH from the Windows directory (if the file exists).

4  Restart Windows.


Close-Up and WordPerfect cause an Application Error
Problem:  Close-Up and WordPerfect cause an Application Error.

If you are using Close-Up with Windows applications and you receive an Application Error when you attempt to start WordPerfect for Windows, you will need an updated keyboard driver for Close-Up.  This driver can be downloaded by modem from the WordPerfect Support Bulletin Board Service.

Solution:

To install the new driver,

1.  Call the Bulletin Board Service at (801) 225-4414.  The system operates at 2400 bps, no parity, 8 data bits, and 1 stop bit.  Follow the prompts for registration on the system.

2.  Download the file CUPKEYBD.DRV.

3.  Copy CUPKEYBD.DRV to your \Windows\System directory.

This file can also be obtained directly from Norton-Lambert.


WordPerfect v5.1 Performance Enhancement
Hint:  WordPerfect v5.1 Performance Enhancement.

In the WordPerfect PIF file, set DETECT IDLE TIME to off, this will speed up performance by 100%.  Use the PIF Editor to change this value.  Click on Advanced to see the Multitasking Box.  Click inside the box next to DETECT IDLE TIME to change the value.  When you are done editing select File-Save to save your changes.


Problem:  WordPerfect 5.2 Displays on Compaq Computers

Print Preview and Reveal codes views may not function properly on Compaq Computers.

Solution:

The QVision 7.23A graphics drivers which ships with some new Compaq Computers may cause display problems in Print Preview and Reveal codes.  Upgrading to the QVision 7.25A graphics may correct many of these problems.  Contact Compaq for more information.


Mouse Pointer Disappears in Windowed WordPerfect
Problem:  Mouse Pointer disappears in Windowed WordPerfect.

This is due to the WP mouse pointer and Windows being out-of-synchronization.

Solution:

1. Press Shift+F1 in WordPerfect.  Press M for Mouse, A for Acceleration Factor, and set the Acceleration Factor to 1.

2. Press Enter 3 times until you are back to the document.

3. Drag the corners of the WordPerfect window so it fills as much of the Windows screen as possible.

4. Move the Windows mouse pointer into the WordPerfect window, move it in turn so it touches the right edge of the window, the left edge, back to the center. and then touching the bottom edge, and finally touch the upper left corner of the window.


Using F10 to Save doesn't work
Problem:  Using F10 to save files to Floppy doesn't work in WordPerfect.

Solution:

To work around this,

1.  Make sure that the floppy is correctly formatted and not write-protected

2.  ALT+F4 key to block the entire document, then press the F10 key to write this "block" to A: or B:

3.  Use F7 (Save and Exit) key to save.


Windows Freezes in WordPerfect
Problem:  Windows freezes in WordPerfect

Solution:

1.  Make sure that WordPerfect version is at least "5.1";

2.  Do a DIR command on the WordPerfect to find out the date of the WP.EXE;

3.  If the date is 11/06/89, request for a upgrade.

4.  When the upgrade comes, start WP with the flag "/32" to force the program to use EMS version 3.2 spec.  For example,

WP / 32

5.  To work around, start WP without Expanded Memory by typing

WP / NE

If problem persists, call WordPerfect at 800-321-4566


WordPerfect Double Underline and Shadow Print Only Once
Problem:  WordPerfect Double Underline And Shadow Print Only Once

The user is printing a multiple page document with a title page that uses double underline and shadow.  He is using the option to have WordPerfect print several copies to the HP LaserJet IIP printer.  The first copy of the title page prints fine, but none of the other copies do.

Solution:

This problem can be eliminated by using the Center code on the title page instead of changing the justification to center.


Internal Stack Overflow Error in WordPerfect
Problem:  Internal stack overflow error in WordPerfect.

WordPerfect has confirmed that the following error message may be displayed on a system running WordPerfect 5.1 with MS-DOS 5.0.

Internal Stack Overflow System Halted

Solution:

To correct this error, set BUFFERS=16 and STACKS=16,128 commands in the CONFIG.SYS file.

This information applies to Microsoft MS-DOS version 5.0.

Explanation:

The following commands must be added to the CONFIG.SYS file to resolve the above error message:

BUFFERS=X   (where X is 16 or more)

STACKS=16,128

The STACKS command needs to occur AFTER the BUFFERS= statement, and BUFFERS needs to be set to at least 16.  The default number for BUFFERS is 15 for machines with at least 640K memory.

The STACKS command supports the dynamic use of data stacks to handle hardware interrupts.  The syntax of the command is:

STACKS=n,s

(where n specifies the number of stacks and s specifies the size [in bytes] of each stack).

The stacks are created within the buffers; therefore, the STACKS command must occur after the BUFFERS statement.

Reference:  WordPerfect technical support: (800) 541-5096


Dropped Codes in the Tandy DWP IIB Driver in WordPerfect 5.0
Problem:  Dropped Codes in the Tandy DWP IIB Driver in WordPerfect 5.0

A user using WordPerfect 5.0 with his Tandy DWP IIB driver from printer 9 (11/23/88) reported problems which seemed to indicate that the printer is not being reset properly at the end of the print job.  After working in 5.0, the printer would not print properly at DOS; it would skip some letters, print some garbage characters, etc. However, when he turned his printer off and back on, it printed correctly.  Entering WordPerfect again and printing and then exiting would cause the same problems as before.  The user could not duplicate the problem with 4.2.

Solution:

Comparing the codes in the 4.2 driver and the 5.0 driver, two codes were being sent to reset the printer at end of print job in 4.2, which are not being sent out in 5.0.

They are <27><25>.  Using PTR to add them to the Reset printer at End of Print Job string solved the problem.

The steps to make this change are:

1.   Enter the PTR program and retrieve the TADWPIIB.PRS file. Press Enter to edit the file.

2.   Press Enter to edit Initialize and Reset

3.   Move to Reset at End of Print Job and press Enter to move to the expression.  The expression is:  [27,22,27,15,27,19].

4.   Add 27,25 to the end of the string so that the string reads:  [27,22,27,15,27,19,27,25].

5.   Exit PTR saving the changes as you do so.  Your user may also want to make this change to the WPRINT9.ALL file in case they ever need to reselect the printer.

See Also

PRINT

PRINTER


Display Pitch Problem
Problem:  Display Pitch Problem

Text on the screen runs beyond the right margin marker before it wraps, which is causes the screen to shift left to right.

Solution:

This is caused by the difference in size/spacing between the selected printer font and the screen font selected to display it.  With a printer font that has a closely matched screen font, so the problem won't be so noticeable.


"Device Driver Problem" while using LaserTools' Fonts on the Fly
Problem:  "Device Driver  Problem," while using LaserTools' Fonts on the Fly.

This error is received while opening, closing, or writing to the output  driver .

Solution:

Use FFINSTAL/A to check for a valid printer port mapping.


Fixing an Outdenting Problem
Problem:  Fixing an Outdenting Problem

What is the preferred method of fixing an outdenting problem?

Solution

It is not generally recommended to use a Reposition for adjustment. The preferred method to fix outdenting, would be to fix the vertical motion by forcing a carriage return with each line feed (Line Feed = [13,10], or fix the printer by changing the dip switches.  Sometimes the method of vertical motion used in the  driver  is not VMI and cannot be set up with a carriage return for every line feed.  If this is the case, and a user simply does not wish to change dip switches, a Reposition could be used.  It should be placed in the relative horizontal motion so that WP will reset the horizontal position for every new line.


Summagraphics Mouse Conflicts with WordPerfect
Problem:  Summagraphics Mouse Conflicts with WordPerfect

A Summagraphics Digitizer 1812 mm 6.13 COM1 version mouse works fine with WordPerfect except when the user enters View Document.  The user can view graphics but no text.

Solution:

With the 03/30/90 release, there were no problems with the 6.13 version Smouse driver .  The 6.2 and 6.1 versions of the mouse driver, however, do not work at all.


Print Text on Page Overprinting Text in Footnotes
Problem:   Print Text On Page Overprinting Text In Endnotes.

The title on an endnote page printed on top of the first lines of an endnote.

Solution:

Entering a hard return  ([HRt]) between the endcode and the text eliminates the overprinting problem.


Printing Bitstream Custom Character Set on WordPerfect
Problem:  Printing Bitstream Custom Character Set on WordPerfect

With the latest releases of WordPerfect and printers (HP Series II) and Bitstream 3.0, custom fonts may not print properly, even though they download to the printer and show up on the font printout. Custom character sets created in Bitstream that do not include any regular characters may cause WordPerfect to default to the nearest font it can find, like Courier Bold.


Line Spacing Problem with R Cartridge on HP LaserJet +
Problem: Line Spacing Problem With R Cartridge On HP Laserjet+.

When printing to an HP Laserjet + with 6-1-89 print dates using the R cartridge, the line spacing will stay the same for 14, 16, 18 point fonts and end up printing on top of each other.

Solution:

In WordPerfect 4.2 you are giving only 2 types of line feeding 6 or 8 lines/inch.  No way of checking for point size and adjusting the line height accordingly exists. This is one reason why 5.0 came out.  A work around is to set his line spacing for 1.5, 2 and 2.5, depending on the point size used to make room for his larger fonts.


Index Generation Hanging
Problem:  Index Generation Hanging - [Index:^^] Was Problem

Generating an index for a very large file the application may hang on pass 7.

Solution:

A code that looks like this: [Index:^^] may cause the problem.  When this code is deleted the index should generate.


WordPerfect v5.0's (6/12/89 Release) Top Margin
Problem:  WordPerfect v5.0 's (6/12/89 Release) Top Margin

In 6/12/89 WordPerfect v 5.0 started printing a little farther down on the page. (Top Margin + 3/4 of the fixed line height.).  This may render older documents useless.

Solution:

To correct this problem, go into Document Initial Codes and set Baseline to YES (Shift-F8, 4,6,5).


IBM Quietwriter Printers - Horizontal Spacing Problem
Problem:   IBM Quietwriter Printers - Horizontal Spacing Problem

The printer prints past the margin.

Solution:

The cartridges are marked incorrectly in WordPerfect.  For 5.0 press Shift-F7, S for Select, 3 For Edit, and 5 for Cartridges and Fonts.  In 5.1, press ShiftF7, S for Select, 3 for Edit and 4 for Cartridges and Fonts.


WordPerfect Style for Pleading Causes Problem with Page Numbering
Problem:   WordPerfect Style For Pleading Causes Problem With Page Numbering.

When using the pleading style in 5.1, the user wants to have page numbering at the bottom center.  With the page numbering code before the pleading style code, several problems occur.  The pleading style includes a top and bottom margin code of 0.667" and 0.833".  This causes the line number 28 to appear immediately under the line number 27 instead of two lines below it.  The last text line appears on line 27 instead of on line 28.  In addition, the page number prints on the same line where the text for line 28 should be.  If the page numbering code appears after the [Style On] code, the spacing of the lines is okay, but the page number still prints in the middle of line 28 with the last text line on line 27.

Solution:

There is a simple work-around that involves setting another T/B Margin code of 0.667" for the top and 0.4" for the bottom after the [Style On] code.  If you would like to make this change permanent, take the following steps:

1-Alt-F8 for Styles menu

2-Highlight Pleading

3-Edit (4)

4-Codes (5)

5-Delete the default T/B Margin setting

6 -Add a new T/B margin (Shift-F8,2,5,.667",.4" [or select 0" to designate minimum bottom margin] )

7-Select (1) for Filename

8-Enter new name [aka. Pleading2]

9-Prompted, "Rename Styles in Document?"  Say No.

10-F7 for previous menu

11-Select (6) for Save

12-Type in default library style file, typically "LIBRARY.STY" (see Setup).

The edited style will now allow the new margin settings to always be available.  The old style [Style: Pleading] will not be lost because WordPerfect will re-create it when WordPerfect encounters it in a document (see page 676 in manual).

The only and correct way to include page numbering with this style would be to decrease the bottom margin.  This style sets up pleading in a header which completely formats the page.  If you place a page numbering code before the style code, it will force line 28 up because WP will not allow the header to extend past the page break.


Endnotes Created In Landscape Problem
Problem:   Endnotes Created In Landscape Problem.

Endnotes created in a landscape font do not print correctly on a portrait endnote page.  The text is compressed to fit on 8.5" rather than 11".  Since endnotes must be printed together at the end, if you have some endnotes landscape and some portrait, no matter what orientation you choose for the endnote page some of the endnotes will not print right.

Solution:

WP is aware of the problem and is currently working on trying to find a solution.  Because a structure change in the program would be needed, it may not be possible to implement this until a future version of WP.  This is an enhancement for a future release of the program.  Until this feature is added to the program, you can work around the wrapping problem by inserting a portrait paper size code just before the endnote code on the landscape page.

Another work around would be to define the endnote code on a dummy portrait page immediately following the landscape page.  You could use a superscript number on the landscape page.  Resetting the page numbering and the automatic endnote numbering might be needed.


Superscript And Subscript Printing Problem After Italics
Problem:   Superscript And Subscript printing Problem After Italics.

Problems printing subscript and superscript in Roman 12 cpi after using the italics feature.

Solution:

No workarounds exist at this time.  This problem was fixed in the next interim release of WP 5.1 following 03/30/90.


Troubleshoot Margin Problem by Re-selecting Printer
Problem:  Troubleshoot Margin Problem By Reselecting printer

You are unable to change the default margins.

Solution:

Try re-selecting the printer.  You don't have to actually go through the process of selecting the printer, just press Shift-F7, S, 3, Enter.  This causes the .SET file to be updated which can clear up the problem.


Problems with Other Word Processors

Specific Conflicts

~Write Problem with Italicized Fonts in Windows 3.00


Utilities Problems
Utility Program Problems

Problems with Adobe Type Manager

~ATM - Adobe Type Manager

~Installation of ATM

~Changes made by ATM

~The ATM.INI File

Specific Conflicts

~Older versions of DMDRVR.BIN (or .SYS) drivers

~Disk Compression Utilities and Windows

~Screen redraw is slow with ATM

~"ATM fonts and PostScript printer fonts don't match" error

~Some ATM Fonts Print Incorrectly

~ATM Fonts aren't available on Plotters


Disk Compression Utilities and Windows
Problem:  Disk Compression Utilities and Windows

Disk Compression TSRs may cause problems with Windows.

Solution:

If a permanent swap files is used, put it in a noncompressed area of the hard disk.  The size of the swap file can be 3 times the size of the RAM.  For example, if Drive D: is the swap space, do not use  any disk compression routine to compress it.  Windows setup does not update any of the system files if C: drive is compressed.

The following are points to keep in mind when using Disk Compression Utilities:

NewSpace 1.07 does not work with Windows

Stacker from Stac Electronics only works with Windows with some restrictions.  Load Stacker last after HIMEM.SYS.

HIMEM.SYS, which Windows uses to manage extended memory, must be located on a non-compressed drive.

Microsoft states that SMARTDrive should not be used to cache a compressed drive.


Problems with Adobe Type Manager

Click on a topic below:

Necessary Files to Run Adobe Type Manager

ATM fonts display differently in Print Preview

ATM fonts are not available for selection in WordPerfect

ATM font names appear twice in the Font list

"ATM fonts and PostScript printer fonts don't match on xxx" Error

Text appears jagged on the screen and/or when printing

ATM fonts display in WordPerfect incorrectly, but print correctly

The ATM fonts do not appear in Windows applications


ATM Font Names appear twice in the Font List.
Problem:  ATM font names appear twice in the Font list.

After installing Adobe Type Manager (versions 1.0 and higher).  ATM font names appear twice in the Font list.

Solution:

Windows applications that use Windows drivers, such as Microsoft Write, will have a font named "Helv" (a Windows bit-mapped font) and another named "Helvetica" (an ATM font).  In WordPerfect for Windows, there will be two fonts with the name "Helvetica."  Helvetica is used as an example, but the problem occurs with Times, Times Bold, Times Italic and possibly other ATM fonts.

To correct this problem, delete the duplicated form of the font under the [Aliases] section of the ATM.INI file.  Once the changes are made to the ATM.INI file, exit Windows, restart Windows, then run WPWin, for example.  Use the Select Printer dialog box to update the printer information.


"ATM Fonts and PostScript printer fonts don't match on xxx" Error
Problem:  "ATM fonts and PostScript printer fonts don't match on xxx" Error

xxx indicates the name of the font.

Solution:

Make sure that the PostScript printer is active in the Windows Control Panel.  Also, if you have changed the port for the PostScript printer since you installed ATM fonts, you may have to install the fonts again from the ATM Control Panel.


Text Appears Jagged on the Screen and/or When Printing
Problem:  Text appears jagged on the screen and/or when printing.

Solution:

Make sure that Windows has been restarted after the initial ATM installation process.

If you are using Windows 3.0, make sure Windows is running in Standard or 386 Enhanced mode.  ATM will not run in Real mode.

Make sure ATM is turned on in the ATM Control Panel.

Make sure the printer is set to the highest possible resolution in the Windows Control Panel.


ATM Fonts Display incorrectly in WordPerfect, but Print Correctly
Problem:  ATM fonts display in WordPerfect incorrectly, but print correctly.

Solution:

You may specify the Windows screen font that is to be used for a specific printer font in WordPerfect 5.2 for Windows.  This is helpful if the screen font displayed in your WPWin document window varies too much in appearance and/or width from the font on the printed page.

NOTE:  These changes will not affect the appearance of your printed document.  These changes will also not affect WordPerfect File Manager or Mail for Windows.

To list the font substitutions you want to make:

1) List the printer fonts you have available by selecting Font from the Font menu in WPWin.  Scroll through the list of fonts, writing down the name of each font that does not display correctly.  Include only the characters up to but not including the first left parenthesis.  For example, Univers (Scalable) would become Univers.  If the font name does not include anything in parentheses, use the full font name, including any size information.

2) Once you have listed all the printer fonts that do not display correctly, you need to choose a screen font for each.  With a Windows printer driver selected, the font list in step one can be used to choose screen fonts.  If you are using a WordPerfect printer driver, select a Windows printer driver by choosing Select Printer from the File menu.  Choose the radio button for Windows, then choose Select.  Include only the characters up to but not including the first left parenthesis.  For example, Arial (TT) (Bold) would become Arial.

To modify the WPC.INI file (or WPC_NET.INI file if WPWin is running on a network):

1) Using Windows Notepad, DOS 5.0 Editor, or any other DOS text editor, open the WPC.INI file located in your Windows directory.

2) Find the section titled [Printer-Screen Font Subst].  There may be some default printer font/screen font pairs listed. Directly beneath the last item under this heading, list each printer font/screen font pair you wish to add in this format:

<printer font>=<screen font>.

Below is an example of what you might enter.  Depending on your installed fonts, your list may differ.

Univers=Arial

Univers Bold=Arial

Courier 10cpi=Courier New

Courier 12cpi=Courier New

3) Save the WPC.INI file, and restart WPWin.

NOTE:  If you are running WPWin on a network, these changes can be made to the WPC_NET.INI file; however, if identical printer font entries are found in a user's WPC.INI file, the screen font entries will override the entries in the WPC_NET.INI.  Any unique printer font entries in the WPC.INI will be used in addition to the list from the WPC_NET.INI.


ATM Fonts do not appear in Windows Applications
Problem:  ATM fonts do not appear in Windows applications.

Solution:

Check to see if the ATM program is active.  To do this, enter the ATM Control Panel in the Main group.  The radio button "On" should be selected.

Check to see if the fonts are installed and appear.on the font list in the ATM Control Panel.  If they do not,appear, it may be necessary to re-install the fonts through Add,in the ATM Control Panel (see your ATM manual for more information).

If you have recently changed the printer port in the Windows Control Panel, it may be necessary to add the fonts again from the ATM Control Panel.

If you are using Windows 3.1, choose the Windows Control Panel, Fonts, then TrueType.  Unmark the option "Show only TrueType fonts in Applications."  Choose OK, then Close the Font window and the Control Panel. Re-enter WPWin, choose Select Printer from the File menu, then choose Update. Once updating is complete, choose Initial Font to see a list of the available ATM fonts.


ATM Font Display Differently in Print Preview in WordPerfect
Problem:  ATM fonts display differently in Print Preview in WordPerfect.

Solution:

WPWin uses the WP.DRS file to display text characters in the Print Preview window.  Thus, third party fonts.will not match the fonts displayed in the Print Preview window unless there is a matching font in  the WP.DRS file.  With the basic WP.DRS file, WordPerfect can display Times Roman, Helvetica, and Courier fonts.  Your ATM fonts will print correctly although they may not look correct in Print Preview.


ATM Fonts are not Available for Selection in WordPerfect
Problem: ATM fonts are not available for selection in WordPerfect.

Solution:

Choose Select Printer from the File menu to make sure you have a Windows printer definition selected. Then, choose Update to update the printer information for WPWin.  Once updating has finished, choose Initial Font.  If the ATM fonts still do not appear in the list, see if the same problem exists in another Windows application.


Files Necessary to Run Adobe Type Manager
Necessary Files to run Adobe Type Manager

In WIN.INI the following lines are necessary:

[PostScript, LPT1]

ATM=Placeholder

[PostScript, LPT2]

ATM=Placeholder

In SYSTEM.INI the following lines are necessary:

atm.system.drv=system.drv

system.drv=atmsys.drv

ATM.INI is also necessary.  This file should have the following lines:]

[Fonts]

Courier,BOLD=c:\psfonts\pfm\cob_____.pfm,c:\psfonts\cob_____.pfb

Courier,BOLDITALIC=c:\psfonts\pfm\cobo____.pfm,c:\psfonts\cobo____.pfb

Courier=c:\psfonts\pfm\com_____.pfm,c:\psfonts\com_____.pfb

Courier,ITALIC=c:\psfonts\pfm\coo_____.pfm,c:\psfonts\coo_____.pfb

GillSans=c:\psfonts\pfm\gn______.pfm,c:\psfonts\gn______.pfb

GillSans,BOLD=c:\psfonts\pfm\gnb_____.pfm,c:\psfonts\gnb_____.pfb

GillSans,BOLDITALIC=c:\psfonts\pfm\gnbi____.pfm,c:\psfonts\gnbi____.pfb

GillSans,ITALIC=c:\psfonts\pfm\gni_____.pfm,c:\psfonts\gni_____.pfb

TimesNewRomanPS,BOLD=c:\psfonts\pfm\mtb_____.pfm,c:\psfonts\mtb_____.pfb

TimesNewRomanPS,BOLDITALIC=c:\psfonts\pfm\mtbi____.pfm,c:\psfonts\mtbi____.pfb

TimesNewRomanPS,ITALIC=c:\psfonts\pfm\mti_____.pfm,c:\psfonts\mti_____.pfb

TimesNewRomanPS=c:\psfonts\pfm\mtr_____.pfm,c:\psfonts\mtr_____.pfb

Symbol=c:\psfonts\pfm\sy______.pfm,c:\psfonts\sy______.pfb

Arial MT=c:\psfonts\pfm\_a______.pfm,c:\psfonts\_a______.pfb

BrushScript,ITALIC=c:\psfonts\pfm\bs______.pfm,c:\psfonts\bs______.pfb

CaslonOpenFace=c:\psfonts\pfm\ca______.pfm,c:\psfonts\ca______.pfb

DomCasual=c:\psfonts\pfm\dc______.pfm,c:\psfonts\dc______.pfb

Frank Goth Cd=c:\psfonts\pfm\fgc_____.pfm,c:\psfonts\fgc_____.pfb

LetterGothic=c:\psfonts\pfm\lg______.pfm,c:\psfonts\lg______.pfb

Shelley Allegro Script,ITALIC=c:\psfonts\pfm\shal____.pfm,c:\psfonts\shal____.pfb

[Setup]

PFM_Dir=c:\psfonts\pfm

PFB_Dir=c:\psfonts

[Settings]

FontCache=128

ATM=Off

BitmapFonts=On

SynonymPSBegin=9

QLCDir=c:\psfonts

ScanBufSize=16

[Mono]

Courier=Yes

LetterGothic=Yes

PrestigeElite=Yes

Orator=Yes

[Aliases]

Helv=Arial MT

Tms Rmn=TimesNewRomanPS

Courier=Courier

Times Roman=Times

[Synonyms]

Helv=Arial MT

Tms Rmn=TimesNewRomanPS

Courier=Courier

Times Roman=Times


Ontrack's DMDRVR.BIN
Problem:   Problem in older versions of DMDRVR.BIN (or .SYS) drivers.

Ontrack's hard disk manager, DMDRVR.BIN, did not properly detect the end of drive marker on older versions of the driver.  Disk Drives using the DMDRVR.BIN or DMDRVR.SYS program (part of ONTRACK Software for the Seagate Drives) should use version 3.3 or later of the driver.  Earlier versions did not detect the end of partition correctly.  This causes conflicts anytime the system (drive) must be accessed.  As the system boots, a banner is displayed showing the ONTRACK version number.  Conflicts with Paradox and Quattro Pro exist.

Solution:

Getting a newer version is the only solution


Database Problems

Click on a database below:

Borland Paradox

Lotus Approach


Problems with Paradox

Specific Conflicts

~Cannot run Paradox in Expanded Mode


Paradox doesn't run in Expanded Mode
Problem:  "Cannot run Paradox in Expanded Mode"

Borland's Paradox database requires a contiguous 64K of Expanded memory to run.

Solution:

If adaptor memory addresses E000 to EFFF is used, Paradox can run by removing the memory manager when running Paradox.


Accessories' Problems

The following Windows' Accessories are covered in this section

CALCULATOR, CARD FILE, CHARACTER MAP, CLOCK, NOTEPAD, RECORDER, MULTIMEDIA PLAYER, OBJECT PACKAGER, PAINTBRUSH, SOUND RECORDER, TERMINAL, WRITE

Specific Problems

~Macro Recorder and Write Problem with TAB in Windows 3.00

~Converting 256-Color Paintbrush files to 16-Colors

with Printing

~Printer Setup from Calendar, Cardfile, Notepad

~Write Problem with Italicized Fonts in Windows 3.00

~Improper Formfeed when Printing Cardfile Cards


Macro Recorder and Write Problem with TAB in Windows 3.00
Problem:   Macro RECORDER and Write Problem with TAB in Windows 3.00

When you create a macro, which uses the TAB key, with Microsoft Windows version 3.00 RECORDer, you may experience problems when you use Write.  For example, when you use Macro RECORDer with Write to make a macro that does the following

TAB TAB Yours very truly, ENTER ENTER TAB TAB John D. Doe

the first two TABS may not work correctly, and ENTER may display as a page break in certain cases.  This is a known problem with Macro RECORDER when you use the macro with Write and TABs.  One workaround is to use SHIFT+TAB instead of a TAB and SHIFT+ENTER instead of ENTER.

Solution:

Microsoft is researching this problem and will post new information as it becomes available.


Printer Setup from Calendar, Cardfile, and Notepad
Problem:  Printer Setup from Calendar, Cardfile, Notepad.

Notepad, Cardfile, and Calendar will not automatically highlight the default printer, which was set up from the Control Panel, as the default printer selection when you select printer Setup from the File menu.  The first printer in the list of printers is selected, rather than the printer most recently set as the default printer.  From Notepad, Cardfile, and Calendar, if no printer is selected under printer Setup, these applications will print to the default printer listed as the Default printer in the Control Panel.

Explanation:

Once a printer has been selected under printer Setup from the File menu, it will remain the active printer until another one is chosen or the work session has ended.  When you go back into the printer Setup menu, you will always see that the first printer on the list is selected again.

Notepad, Cardfile, and Calendar will list all printer devices listed in the WIN.INI file.  As a result, you can select a printer from printer Setup that is not connected to a port or is marked as inactive.  Attempting to print to a printer that is not connected or is marked as inactive will result in the following error message:

Cannot print (filename); ensure the printer is connected and properly set up.  Select a printer that is connected to a port and is marked active.

When choosing printer Setup from the File menu, the printer that will remain selected is the printer that was added last through the Control Panel or Setup.  The order of the printers in Notepad's printer Setup is opposite to the order listed in the WIN.INI file under [printer Ports] (the last printer added is first on the list).

Windows applications such as Word for Windows, Excel, or Terminal select and change the Windows default printer with printer Setup.

Solution:

Microsoft is researching this problem and will post new information as it becomes available.


Write Problem with Italicized Fonts in Windows 3.00
Problem:   Write Problem with Italicized Fonts in Windows 3.00

If you are using italics in the Write program packaged with Microsoft Windows, and the last italicized character is followed by a non-italicized character, the last italic character may appear to be clipped.  This behavior occurs due to the way that Windows handles italic screen fonts.

To reproduce this behavior, do the following:

1.  Load Write.

2.  Select a font, such as Modern (one that can be italicized).

3.  Select Italics.

4.  Type a few words (do not put a space after the last character).

5.  Cancel the Italics selection.

6.  Type another word.

Solution:

Note that the last italicized character is clipped.  This does not affect the printed output.

Microsoft is researching this problem and will post new information as it becomes available.


Improper Formfeed when Printing Cardfile Cards
Problem:  Improper Formfeed when Printing Cardfile Cards

When Cardfile prints cards, it calculates the number of cards per page based on the physical height of the printer page and the print height of the card plus the character print height, using the following formula:

CardsPerPage = PhysHeight / (CardPrintHeight + CharPrintHeight)

After Cardfile has printed this number of cards, it sends a formfeed to the printer using the following function:

 Escape(hDC,NEWFRAME,0,(LPSTR)0,(LPSTR)0)

If you are using 2 1/6-inch by 4-inch continuous-form cards, the formfeed will not terminate on the upper edge of a card.  It will terminate at a location that corresponds to the page height as specified in the printer  driver .  None of the current printer drivers supplied with Windows has a page height that is appropriate for use with the continuous-form cards.


Problems with Development Tools
Development Tools

Necessary Files for Microsoft Visual Basic


Necessary files for Visual Basic

The following files are necessary for Visual Basic:

DECOMP.DLL	README.TXT	SETUP.EXE

SETUP1.EXE	VB.HLP	VB.EXE

VBRUN100.DLL	FARM.WM	CBT.EX

CBTLIB.EXE	VB.LES

In [VB.ini] check the following lines:

[Visual Basic]

ImmediateWindow=320 310 320 170 0

MainWindow=112 288 640 88 1

ToolBox=2 70 0 0 0

ProjectWindow=104 404 220 339 0

ColorPalette=61 383 0 0 0

CustomColors=16777215 16777215 16777215 16777215 16777215 16777215 16777215 16777215 16777215 16777215 16777215 16777215 16777215 16777215 16777215 16777215

SyntaxChecking=1

In [WIN.INI] check the following lines:

[Compatibility]

VB=0x0200

[Extensions]

rm=C:\VB\VB.exe ^.frm

mak=C:\VB\VB.exe ^.mak

bas=C:\VB\VB.exe ^.bas


System Configuration Problems

This section deals with the PC's configuration.

See

SYSTEM FILES

 Examples are AUTOEXEC.BAT, WIN.INI, and CONFIG.SYS

FONTS

  This section deals with the problems of printing and displaying fonts and with specific fonts' problems.

WINDOWS

  Problems associated with Windows Setup, software conflicts, and with hardware conflicts are discussed here.

NETWORK

  Setting up Windows to run on networks presents many problems, since Windows and MS-DOS, which Windows runs on top off, were never intended or designed for this purpose.  However, Windows is the most popular desktop user interface and most network operating systems have at least a "cordial" relationship with Windows.  This section details problems with Windows on the net.

MS-DOS

  This section deals with MS-DOS because Windows can be considered an application that runs on top of DOS.  Since File Manager is nothing more than a graphic interface for DOS, some of DOS's problems become File Manager's problems.

MEMORY MANAGERS

  Memory Managers allow your PC to use RAM more effectively.  However, some of the manager's methods may result in conflicts with hardware or software.  This section explains problems with Memory Managers.  Examples of these products are HIMEM.SYS, QEMM.386, RAMDrive


Problems with System Files

DOS and Windows rely heavily on two key configuration files, CONFIG.SYS and AUTOEXEC.BAT.  These files are the last two files processed during Start-up.  CONFIG.SYS allocates memory for important DOS data structures and installs device drivers.  AUTOEXEC.BAT initializes variables and executes any DOS commands you require each time the system starts up.

WIN.INI is a Windows file that holds all configurable information about Windows.  For instance, the colors used for the background, foreground, menu bars and highlighted text can be edited with the Color Editor in the Control Panel and then saved to WIN.INI to make the changes permanent.  Many applications will modify WIN.INI by adding sections to the file.

Specific Conflicts

~Mysterious Hangs or Failures

~Keyboard Problems After Upgrading to MS-DOS 4.x and Later

~Windowed DOS Applications


WIN.INI Run= Command and Windowed DOS
Problem:  Windowed DOS Applications begun with WIN.INI Run= Command Problem.

When you use the Run= line in the WIN.INI file to start a windowed DOS application followed by a Windows application, the keyboard input goes to the DOS application.  The focus remains on the DOS application in the background and does not switch to the Windows application in the foreground as you would expect.  This only happens in 386 enhanced mode.

The following is a sample WIN.INI run line:

Run=word.pif winword.exe

Microsoft is researching this problem and will post new information as it becomes available.

Solution:

To switch the focus to the Windows application in the foreground, click anywhere in the Windows application with the mouse.  If you do not have a mouse, press ALT+ESC.


Mysterious Hangs or Failures
Problem:  Mysterious Hangs or Failures

Mysterious hangs or failures can occur when a hardware routine does not have enough storage space to perform its job.  To avoid this problem, MS-DOS versions 3.2 and later provide additional storage space for the interrupt-handling code whenever a hardware interrupt occurs.  This is done by changing the current storage area (called a "stack," because it's a place to stack information temporarily) to a new storage area provided by MS-DOS.

By default, nine of these stacks, each 128 bytes in size, are provided.  The number and size of stacks can be increased using the CONFIG.SYS STACKS=n,m command, where n is the number of stacks and m is the size of each stack in bytes.

Changing the current stack takes time.  It was discovered that changing the stack can slow the system enough that some programs, particularly high-speed communications programs, will fail.  To avoid this problem, MS-DOS versions 3.3 and later allow disabling the stack swapping by specifying 0 stacks of 0 bytes in size (STACKS=0,0).

Because the STACKS= command affects hardware- and configuration-dependent code, it can have unpredictable effects.

Solution:

If a "stack overflow" or "exception error 12" (stack exception) error   occurs, increasing the number and size of stacks specified in CONFIG.SYS   may solve the problem (for example, STACKS=18,256).

Note: STACKS= only affects hardware interrupts. If the stack being   overflowed (trying to store too much information) is internal to an   application, this will probably not solve the problem.

If the command STACKS=0,0 is in the CONFIG.SYS file and any instability   occurs (including, but not limited to, printing problems and system   hangs), remove it temporarily and test.

If the command STACKS=n,m is in CONFIG.SYS and problems occur (including,   but not limited to, serial port problems), remove it temporarily and test.   If problems continue and the system is an AT class machine, set   STACKS=0,0; if the system is a PC, PC XT, or PC Convertible, set   STACKS=9,128.

This information applies to Microsoft MS-DOS versions 3.x, 4.x, 5.0, and 5.0a.

Explanation:

Beginning in MS-DOS version 3.2, MS-DOS added code to swap the stack whenever an asynchronous hardware interrupt occurs, before passing control to the original interrupt handler. (Interrupt vectors 02H, 08-0EH, 70H, and 72-77H, corresponding to IRQs 0-15.)  Before MS-DOS 3.2, interrupt handlers received control with the stack set to that of whatever program or device driver was executing when the interrupt occurred.  Thus, if a program stack is nearly full and a hardware interrupt occurs, random and unpredictable behavior will result (typically a system hang).

Beginning in MS-DOS 3.3, the STACKS=0,0 line was added.  This setting disables MS-DOS stack switching (thus returning MS-DOS stack behavior to that of MS-DOS versions 3.1 and earlier).  That is, interrupts are processed using whichever stack happens to be loaded at the time of the interrupt.  Because MS-DOS doesn't manage any stacks, less memory is required when 0,0 is specified.  In addition, less time is required to handle interrupts because no code to swap stacks is executed.  A negative aspect is that the same behavior that motivated support for stack swapping can occur (that is, system hangs and other random behavior as the stack overflows).

If stack switching is enabled, MS-DOS ensures nested interrupts do not get the same stack.  Upon completion of the interrupt processing, the stack is released so that MS-DOS may use it for a future interrupt.

Ranges for n and m in STACKS=n,m:

 - MS-DOS 3.1 and earlier have no support for swapping of stacks

 - MS-DOS 3.2 and later support values in range N=8-64, M=32-512

 - MS-DOS 3.3 added support for 0,0, which is equivalent to behavior in 3.1   and earlier.

Default Values for STACKS

 - MS-DOS versions earlier than 3.2 do not support STACKS; behavior is equivalent to STACKS=0,0 on MS-DOS 3.3 and later.

 - MS-DOS 3.2 always defaults to STACKS=9,128.

 - MS-DOS 3.3 and later use special case codes that check for PC, PC XT, and   PC Convertible. If any of these is detected, STACKS defaults to 0,0.   Otherwise, STACKS defaults to 9,128.

If a system is experiencing random hangs or strange behavior and STACKS=0,0 is in the CONFIG.SYS file, this should be considered a prime suspect and removed.  Conversely, some hardware that requires extremely fast interrupt processing may require STACKS=0,0 to operate properly.  If you are having trouble with a high-speed communications or real-time program, try setting STACKS=0,0.  If you have a program that worked correctly with MS-DOS 3.1 or earlier and you cannot get it to work with MS-DOS 3.2 or later, set STACKS=0,0.

Error Messages:

If stack switching is enabled and MS-DOS runs out of free stacks, the following message will be displayed:

FATAL : Internal Stack Failure, System Halted.

If the above message is displayed, try a higher number for n in STACKS=n,m. If you experience random hangs or other strange behavior, try increasing the m value in STACKS=n,m.

Programming Notes:

If you are hooking interrupts with the MS-DOS get/set interrupt vector services, stack switching will not be done before your interrupt handler gets control.  Any stack switching necessary must be done by your interrupt handler.


Keyboard Problems After Upgrading to MS-DOS 4.x
Problem:  Keyboard Problems After Upgrading to MS-DOS 4.x and Later

MS-DOS versions 4.x and later read information from extended or enhanced (101 and 102 key) keyboards differently than from standard (84 key) keyboards. This allows, for example, MS-DOS to determine which ENTER key is pressed on enhanced keyboards.

Some older terminate-and-stay-resident (TSR) programs that hook into the keyboard interrupt don't recognize there are two ways to read from enhanced keyboards.  It is possible in MS-DOS 4.x and later for TSRs (and other applications) to fail because of this change in how MS-DOS reads from enhanced keyboards.

If you encounter problems using the keyboard after upgrading to MS-DOS 4.x or 5.0, it may be related to this change.  You can force MS-DOS to read from enhanced keyboards like standard keyboards.  If you are not using ANSI.SYS, use the following command in the CONFIG.SYS file:

switches=/k

If you are using ANSI.SYS, load it using the /K switch.  For example:

device=c:\dos\ansi.sys /k

This information applies to MS-DOS versions 4.x and 5.x.

More Information:

The internal MS-DOS CON[sole] device driver is responsible for reading input from the keyboard and displaying character output on the screen.  Whenever possible, MS-DOS operates through the ROM BIOS, and CON is no exception.  CON uses the ROM BIOS Interrupt 16h service to access the keyboard.

In MS-DOS 1.x, 2.x, and 3.x, CON always uses INT 16h function 0h to read characters from the BIOS keyboard buffer and function 1h to check the keyboard status.

In MS-DOS 4.x, 5.0, and 5.0a, MS-DOS uses INT 16h functions 10h and 11h if an enhanced keyboard is present.  Functions 10h and 11h were added to these versions to support enhanced keyboards on ATs and PS/2s.

Enhanced keyboards have two of each of the following keys

 - CTRL - ALT - ENTER - HOME - END - INSERT - PAGE UP - PAGE DOWN

in addition to ARROW keys.  When using INT 16h functions 0h and 1h to read these keys, they both appear the same.  When using INT 16h functions 10h and 11h, it is possible to tell which ENTER or HOME key is pressed.  Functions 10h and 11h also allow MS-DOS to read function keys F11 and F12.

The CONFIG.SYS command SWITCHES=/K causes CON to use functions 0h and 1h when reading from enhanced keyboards.  This is necessary when an application program assumes that MS-DOS will use functions 0h and 1h to read input.

ANSI.SYS is an enhanced console device driver that substitutes itself for the default CON device driver.  When ANSI (or any other substitute console device driver) loads, it overrides the default CON device driver by reporting itself as "CON" (MEM /D reports device names).  Like the default CON driver, ANSI.SYS uses functions 10h and 11h in MS-DOS 4.x and later.  To force ANSI.SYS to read keyboard input using functions 0h and 1h, load ANSI.SYS with the /K switch.

Note: Although ANSI.SYS will use functions 10h and 11h when reading from enhanced keyboards, to remap the extended keys separately from their 84-key counterparts using ANSI escape sequences, you must load ANSI.SYS using the /X switch.


Problems with Fonts

General Information

General Information on Fonts

Using PostScript

Using PCL

Specific Conflicts with Fonts

~Sizing of Works Characters Get Smaller

~Word 5.0: Printing Problem with HP DeskJet Downloadable Driver


Problems with Windows or the OS
Problems with Windows

Components necessary for Windows to run

Specific Conflicts

~Multiple Versions of Windows on the same Fixed Disk

~Windows does not run in 386 Enhanced Mode

~Windows displays garbage in 386 Enhanced Mode

with Installation

~Installing Windows 3.00 into WINDOWS Directory

with Applications and Software Drivers

~VCPI Conflicts with Windows

~Virus Detection Routines will Interfere with Windows Setup or Windows

~Micronics Memory Manager Conflicts with Windows

with Hardware

~Olivetti M-250-E Mouse Conflict with Windows 3.1

with Printing

~Deleting Fonts when more than 40 are Installed


Necessary Components for Windows 3.1 to Function
Components necessary for Windows 3.1 to Function

The following components are required for Windows to run

Display Drivers

Keyboard Drivers

Mouse Drivers

Printer and Plotter Driver

Disk Caching Program

Extended Memory Device Driver

Expanded Memory Manager

Proper Display Drivers

The following is a list of display drivers

ATTDC.CPV	ATTDEB.CPV

CGA.CPV	COMPAQ.CPV

EGAHIBW.CPV	EGAHIRES.CPV

EGALORES.CPV	EGAMONO.CPV

HERCULES.CPV	IBMPS230.CPV

IBMPS250.CPV	STD.LGO

TANDYDSP.CPV	8524.CPV

IBMPS230.CPV	IBMPS250.CPV

TANDYDSP.CPV	WYSE700.CPV

MULTIMOD.CPV	SV400.CPV

Keyboard Drivers

Non-compatible Keyboards must use SETENHKB.COM to function properly.  Compatible Keyboards can use the following drivers:

TANDYKBD.CPV

KBDUS.CP

Printer and Plotter Drivers

These are Printer and Plotter Drivers:

DESKJET.CPV	EPSON24.CPV

EPSON9.CPV	HPPCL.CPV

HPPLOT.CPV	IBMCOLOR.CPV

IBMCRX.CPV	NECCOLOR.CPV

NECP2.CPV	OKI24.CPV

PAINTJET.CPV	PROPRN24.CPV

PROPRINT.CPV	PSCRIPT.CPV

QWIII.CPV	THINKJET.CPV

TOSH24.CPV	TTY.CPV

Mouse Drivers

These are some Mouse drivers:

ATTMOUSE.CPV	IBMMOUE.CPV

MOUSE.CPV	MSMOUSE1.CPV

MSMOUSE2.CPV	NOMOUSE.CPV

LMOUSE.CPV	HPMOUSE.CPV

NOMOUSE.CPV

Disk Caching

These are some examples of disk caching programs:

SMARTDRV.SYS

RAMDRIVE.SYS

Extended Memory Device Driver

A device driver must exist to properly use Extended Memory.  For example,  HIMEM.SYS.

Expanded Memory Managers

When the IBM PS/2 80286 Memory Expansion Board, Intel Above Board, or AST RAMPage board is installed, a Expanded Memory Manager must be used.  These are the necessary memory managers:

PS2EMM.SYS	Use with IBM PS/2 80286 Memory Expansion

EMM.SYS	Use with Intel Above Board or AST RAMPage Board

EMM2.SYS

REMM.SYS


Windows doesn't run in 386 Enhanced Mode
Problem:  Windows does not run in 386 Enhanced Mode

Windows may not run in 386 Enhanced Mode if you are using QEMM386.

Solution:

If you are using QEMM386, remove the QEMM.SYS command and its related statements like LOADHI in Config.sys with a text editor.  Swap HIMEM.SYS with QEMM's old location and reboot system.


Windows Displays Garbage in 386 Enhanced Mode
Problem:  Windows displays garbage in 386 Enhanced Mode

Windows may display garbage in 386 Enhanced Mode if you are using QEMM.

Solution:

If you are using QEMM386, remove the QEMM.SYS command and its related statements like LOADHI in Config.sys with a text editor.  Add HIMEM.SYS in QEMM's old location and reboot system.


VCPI Conflicts with Windows Applications
Problem:  VCPI Conflicts with Windows Applications

Applications using VCPI standard from Phar Lap Software, will have conflicts with Windows.  The applications are

- Lotus 1-2-3 version 3.0

- AutoCad 386

-  FoxBase 386

-  IBM Interleaf Publisher

-  Mathematica 386

-  Oracle Corp's Oracle

-  Paradox 386

-  Smalltalk-80 386

-  Digital Research Concurrent DOS

-  The Software Link's PC-MOS

-  Intelligent Graphics Corp's VM/386


Virus detection routines interfere with Windows
Problem:  Virus Detection Routines will Interfere with Windows Setup or Windows

The following Virus detection routines will interfere with Windows Setup or Windows itself:

ASP Integrity Toolkit 3.7

Data Physician Plus 2.0

Norton Anti-Virus 1.0

Vaccine,

Virex-PC 1.11

Virusafe 4.0

Solution:

Turn them off or get a later version which work well with Windows from disclaimer.


Micronics Memory Manager conflicts with Windows
Problem:  Micronics Memory Manager Conflicts with Windows

The Micronics Memory Manager does not work with Windows.  Make sure that the following drivers are not loaded by CONFIG.SYS.  The drivers names are:

MICEMM4D.EXE,

MICEMM4F.EXE,

MICEMM4G.EXE

MICEMM4*.EXE

Use SmartDrive.sys rather than RAMDrive.sys if possible.

If RAMDrive.sys is used, make sure that it is the latest version.


Olivetti Mouse Conflicts with Windows 3.1
Problem:  Olivetti M-250-E Mouse Conflict with Windows 3.1

The Olivetti M-250_E Mouse is uncontrollable in Windows 3.1.

Solution:

Change SYSTEM.INI with your favorite text editor like Notepad to the following:

[Standard]

FasterModeSwitch=True


Multiple Versions of Windows on the same Fixed Disk
Problem:  Multiple Versions of Windows on the same Fixed Disk

Windows 2.1 and other versions of Windows including run-time Windows have many filenames in common.

Solution:

If you have multiple versions of Windows on your computer, avoid problems by including the path to only one version in your PATH environment variable.   See you DOS manual for information on the PATH variable.


Deleting Fonts when more than 40 are installed
Problem:  Deleting Fonts when more than 40 are Installed

Control Panel can only handle 40 fonts

Solution:

Use a text editor, like Notepad, to modifiy the [fonts] section in WIN.INI.  Save all changes.


Installing Windows 3.00 into Windows Directory
Problem:  Installing Windows 3.00 into WINDOWS Directory.

If you install Microsoft Windows version 3.00 into an existing Windows 286 or Windows 386 directory, you may get the following error message:

Your application has violated system integrity...

This will usually occur when you try to print.  This happens because Windows 2.x printer drivers have not been updated to work with Windows 3.00.

Solution:

Deleting the files from the WINDOWS directory (after saving any files of importance), and reinstalling Windows 3.00 will usually resolve this problem.

Microsoft is researching this problem and will post new information as it becomes available.


Problems with DOS

Specific Conflicts

~Clocks on Amstrad 8086 XTs

~Command-Line Redirection Argument-Parsing Problem

~Tandy 1400 Laptop Clock Problem Under MS-DOS 5.0

~Removing Hidden Files

~Deleting non-DOS partitions

~DOSSWAP.EXE Problem Occurs when Swap Not Allowed

~Incorrectly Executing COPY Command


Clocks on Amstrad 8086 XTs
Problem:  Clocks on Amstrad 8086 XTs

The real-time system clock on the Amstrad 8086 XT class machines does not keep time with MS-DOS 5.0 installed on the system.

Solution:

This problem has been confirmed with Amstrad, and there is no current or proposed workaround for the problem.

This information applies to Microsoft MS-DOS version 5.0.

Explanation:

IBM PCs and PC-XTs do not include a real-time system clock that will retain the correct time and date after repowering the system.  IBM introduced a real-time system clock in the IBM AT.  Microsoft MS-DOS can only access real-time clocks that are compatible with the IBM AT.

The Amstrad company no longer has their own dedicated support division in the United States.  Instead, they have divided service and support responsibilities among three companies.  Issues dealing with out-of- warranty Amstrad products are handled by the Sinotech Corporation, which can be reached by calling (708) 566-0504.  Warranty issues for Amstrad "1000 series" products are handled by the Dictaphone Corporation, at (800) 858-8504. Warranty issues for Amstrad "2000 series" products are handled by the Dow Jones Corporation at (800) 556-0101.

The former Amstrad U.S. service center in Irving, Texas, is no longer in operation; however, you may contact Amstrad at their international headquarters:

Amstrad plc

Brentwood House

169 Kings Rd.

Brentwood, Essex

England  CM 144 EF

Phone:  (011)(44) 277-228-888


Command Line Redirection Argument Parsing Problem
Problem:  Command-Line Redirection Argument-Parsing Problem

Using MS-DOS Versions 3.30 and 3.30a, any MS-DOS filter utility (for this example, "FOO.EXE") and the input and output of this filter "IN" and "OUT", the following command line will be properly interpreted:

FOO <IN >OUT

However, with no spaces between "<IN" and ">OUT", arguments such as the following will result in a "File not found" error:

FOO <IN>OUT

COMMAND.COM tries to redirect input from the file "IN>OUT" into the filter FOO, but it cannot find this file because it does not exist.  Microsoft has confirmed this to be a problem in Versions 3.30 and 3.30a.  This problem was corrected in MS-DOS Version 4.00.

Solution:

The workaround for MS-DOS Version 3.30 is to always use spaces between command-line arguments, as follows:

FOO < IN > OUT

It is always safer to delimit such arguments with spaces because the command-line parsing logic of programs (in this case COMMAND.COM) is must less likely to fail.


Tandy 1400 Laptop Clock Problem Under MS-DOS 5.0
Problem:   Tandy 1400 Laptop Clock Problem Under MS-DOS 5.0

When running Microsoft MS-DOS 5.0 on a Tandy 1400 laptop, the clock will not function properly because of the nonstandard implementation of the clock on the Tandy 1400.  The clock will be reset each time the computer is booted and it won't be incremented while an application is executing.

This information applies to MS-DOS version 5.0.

The Tandy 1400 laptop comes in three models: LT, FD, and HD.  On these models, the clock is a function of the DOS shipped with the computer.  The clock will only function correctly under the original version of DOS shipped with the machine.

Solution:

The following list describes Tandy 1400 laptop models and corresponding DOS versions:

Model	DOS Version

LT	Tandy DOS 3.2003 or 3.2004

FD	Tandy DOS 3.3004

HD	Tandy DOS 3.3004

Tandy technical support: (817) 878-6875


Removing Hidden Files
Problem:  Removing Hidden Files

Solution:

The method described below uses DEBUG to create a small program that will remove the hidden attribute from a file.  This method should be used only as a last resort.

At the DOS prompt, type the following commands:

DEBUG

A 100

mov dx,116	;load the offset to filename into dx

mov ax,4300 	;load get/set file attributes function number into ax

int 21 	;call DOS interrupt 21H to read attribute information

and cx fffd	;strip off only hidden attribute bit

mov dx,116	;load the offset to filename into dx

mov ax,4301	;load get/set file attributes function number into ax

int 21	;call DOS interrupt 21H to write attribute information

int 20	;terminate program

<ENTER>

E 116 'filename' 0

Replace "filename" with the path G and filename of the target file.  Example:

e 116 'C:\DATA\TEST.DAT' 0

When you type the command "G", DEBUG will execute the section of code in memory.  If everything has been entered correctly, the message "Program terminated normally" will be displayed.  After typing "Q" to quit DEBUG, verify that the file is no longer hidden.

Explanation:

The program begins by calling Int 21H function 43H to get the current file attribute.  The attribute byte is returned in register CX, which is then ANDed with hex FFFD to reset bit 1.  The program calls the get/set file attribute function again to write the attribute in register CX to the file.

This information applies to Microsoft MS-DOS versions 3.2, 3.21, 3.3, 3.30a, 4.0, 4.01, 4.01a and 5.0.


Deleting non-DOS Partitions
Problem:  Deleting non-DOS partitions

Solution:

FDISK.EXE from MS-DOS version 5.0 allows a non-DOS partition to be deleted.

The following information applies to Microsoft MS-DOS versions 2.x, 3.x, and 4.x, but not 5.0.

As a security measure, the MS-DOS FDISK.EXE utility will not remove or modify a partition made by another non-DOS operating system (such as XENIX).  If your system contains another operating system in another partition (in addition to MS-DOS), this implies that this operating system understands about disk partitions.  Instead of trying to get the MS-DOS FDISK.EXE utility to work with this other operating system, you should instead rely on the partitioning tools available with the non-DOS operating system.

For safety purposes, the MS-DOS FDISK.EXE utility prevents you from modifying non-DOS partitions; however, it is still possible to accidentally or intentionally modify the partition (or data) of this other operating system by using the ROM BIOS interrupt 13H (Disk I/O), or MS-DOS interrupt 25H/26H (Absolute Disk Read/Write).

If the non-DOS operating system does NOT have the ability to modify its own partition, a program that does the above stated interrupt 13H or interrupt 25H/26H file I/O could be used to modify the partition.  Such a program can be written using the MS-DOS Debug utility.

Another method of removing a non-DOS partition is to perform a low-level format of the disk, thus removing partition information from the disk.


Incorrectly Executing COPY Command
Problem:  Incorrectly Executing COPY Command

When a file of zero length is copied to a currently existing file, the COPY command returns the following message and incorrectly deletes the target file in the process:

0 File(s) copied

Microsoft has confirmed this to be a problem in the Microsoft MS-DOS Packaged Product versions 3.3, 3.30a, 4.0, 4.01, and 5.0.

Solution:

Microsoft is  researching this problem and will post new information as it becomes available.

When a file is to be copied to an existing file, the COPY command deletes the target file and then proceeds to copy the source file onto the target file. However, just before proceeding, COPY checks the length of the target file and, since it is of length zero, the COPY command is aborted.  The net result is that the previously existing target file isn't undeleted and hence is lost.  You can recover the target file by using a third-party utility (such as The Norton Utilities or PC-Tools).

With MS-DOS 5.0, the UNDELETE command can also be used to recover the target file.


DOSSWAP.EXE Problem Occurs When Swap Not Allowed
Problem:   DOSSWAP.EXE Problem Occurs when Swap Not Allowed.

There is a problem in MS-DOS version 5.0 Task Swapper that can cause mysterious failures after a task switch request is not allowed.    A task switch request is prevented whenever you attempt to switch tasks by pressing ALT+TAB or ALT+ESC when task switching could cause a problem for the application.  When the request is prevented, the machine beeps, and the task switch does not occur.

Solution:

Microsoft has confirmed this to be a problem with MS-DOS version 5.0 DOSSWAP.EXE.  This problem was corrected in an application note titled "Replacement DOSSWAP.EXE for MS-DOS 5.0," PD0445.

To obtain application notes, call Microsoft Product Support Services at (206) 454-2030.

If you find that erratic behavior occurs after you are not allowed to perform a task switch, you should obtain the above application note.

Explanation:

A task switch request is disallowed under the following circumstances:

If you are running an application that is MS-DOS Shell Task Switcher aware and you press ALT+TAB to switch, Task Swapper may disallow the call because the application has notified MS-DOS Shell not to swap it.  For example, Novell NetWare never allows task switches while it is servicing any MS-DOS function (INT 21) call over the network.

If you run any application that uses netBIOS asynchronous API (for example, VTP or an SQL application in a session), Task Swapper automatically disallows any switch request to avoid specific conflicts.

In either of the above cases, the value in the CX register will be destroyed. The affect of the CX register being destroyed will vary, depending on what the application was storing there.


Problems with Memory Managers

General Hints

Choosing between RAMDrive and SMARTDrive

Using QEMM

Specific Conflicts

~Error with EMM386.SYS device driver

~HIMEM.SYS and SMARTDrive

~SMARTDrive and Disk Compression Utilities

~SMARTDrive Problem with 20-MHz or Faster 80386 Computers

~SMARTDrive and Expanded Memory Emulators

~386Max and SMARTDrive.

with Windows

~Windows does not run in 386 Enhanced Mode

~Windows displays garbage in 386 Enhanced mode

~Windows Conflict with Micronics Memory Manager

~386Max no longer need device driver.

~Setup and Windows in standard mode crash with 386Max.

~Windows runs slowly with 386Max.

~386Max and Windows' enhanced mode.


386Max and SMARTDrive
Qualitas' 386Max and SMARTDrive.

The disk cache utility that comes with 386Max, QCACHE.EXE, cannot be used with Windows 3.1 SMARTDrive.  If you install 386Max after installing Windows 3.1, 386Max may display an installation message recommending that you install QCACHE.  386Max cannot detect Windows 3.1's SMARTDrive.  Do not install QCACHE.  Use SMARTDrive only.


386Max no longer needs device driver
386Max no longer need device driver.

Microsoft states that the device driver, WINDOWS.LOD, is no longer needed with 386Max version 6.x.

Solution:

Delete the line LOAD=WINDOWS.LOD line out of the 386MAX.PRO file if you have 386Max version 6.x.  This will free up memory.


Setup and Windows in standard mode crashes with 386Max
Setup and Windows in standard mode crash with 386Max.

Solution:

Set 386Max's EXT parameter lower than 64.  If you reduce this to zero, both Setup and Windows in standard mode crash.


Windows runs slowly with 386Max
Problem:  Windows runs slowly with 386Max.

Solution:

Microsoft advises that 386Max's setting for extended memory handles, XMSHNDL, be left blank or set to 4 or above.  A configuration of XMSHNDL=2 or 3 will significantly slow Windows or cause it to fail when loading some components.


386Max and Windows' Enhanced Mode
Problems:  386Max and Windows' enhanced mode.

Avoid limiting the expanded memory swap region with 386Max.

Solution:

Avoid problems with Windows' enhanced mode by using 386Max settings that do not restrict UMBs (above A000).  For example, a setting of EXCLUDE=1800-B800 would be too restrictive, but EXCLUDE=1800-A000 is not.  SEE General Information on Memory.


SMARTDrive and Disk Compression Utilities
Problems:  SMARTDrive and Disk Compression Utilites.

The most popular disk-compression utilities include Stacker, SuperStor and other third-party developers.  Windows 3.1 is not wholly trouble-free with these products.

Solution:

Microsoft states that you should use SMARTDrive to cache only uncompressed drive letters when using Stacker and SuperStor, not the drive letters that represent compressed drives.  These utilities typically show DOS one drive that is uncompressed and one or more that are compressed.

If C: is compressed (label is stac_vol) and D: is uncompressed, you should turn caching off drive C: but not on D: using the following commmand in your AUTOEXEC.BAT:

C:\WINDOWS\SMARTDRV C- D+ 1024 1024

SMARTDrive must be loaded after commands that create the appearance of compressed and decompressed drives.

Windows files must be located on a noncompressed drive.  This includes SWAPFILE.EXE's permanent swap file.  You must configure utilities like Stacker to leave several megabytes for disk space uncompressed. If you rely on a permanent swap file for virtual memory, Microsoft recommends that you make that swap file twice the size of your available extended memory.  For a 2MB system, a 4MB swap file is necessary.

If Stacker's SSWAP driver has been loaded in CONFIG.SYS, it may have substituted different drive letters for its compressed files.  This may mean that Windows Setup cannot automatically modify your CONFIG.SYS and AUTOEXEC.BAT now, since they are in a compressed format.  System files are best kept uncompressed.


SMARTDrive and Expanded Memory Emulators
Problem:  SMARTDrive and Expanded Memory emulators

Expanded memory emulators - sometimes called LIMulators, after the Lotus-Intel-Microsoft Expanded Memory Management Specification - may try to maximize available memory by forcing SMARTDrive into upper memory blocks.  SMARTDrive cannot work under these conditions when Windows is in 386 Enhanced Mode and double-buffering is enabled.

Solution:

Specify that SMARTDrive loads itself into low memory with the switch /L.  For example, your AUTOEXEC.BAT would load SMARTDrive with the following command:

C:\WINDOWS\SMARTDRV /L


Hints for Using QEMM

This section gives warnings regarding QEMM and

Windows Setup

Network Interface Cards

TSRs that require expanded memory

Requisite Files handles in CONFIG.SYS

Windows Setup and QEMM

If you are using QEMM.SYS keep use these hints to avoid setup conflicts with Windows:

*do not use HIMEM.SYS

*do not use DEVICEHIGH : LOADHIGH

*do not use DOS=UMB to claim UMBs (Upper Memory Blocks)

Network Interface Cards and QEMM

QEMM may also cause conflicts with adapters (Network Interface Cards).  To prevent this edit the DEVICE statement that defines QEMM

DEVICE=c:\qemm\QEMM386.SYS EXCLUDE=xxxx-yyyy

where xxxx-yyyy is the memory address of the NIC.  Check the NIC's manual for details.

The EXCLUDE parameter prevents the memory addresses from being used.

TSRs that require expanded memory

TSRs that require expanded memory may also conflict with QEMM.  Check to see if any TSR programs allocate expanded memory for itself by checking the TSR's DEVICE statement.  A "/E" or a "/A" flags the use of expanded memory.  Remove these TSRs one at a time to see if conflicts exist to identify the problem TSR.

File Handles in CONFIG.SYS

Additionally, insure that enough File handles exist in CONFIG.SYS.  The lines should look like this:

FILES=30

BUFFERS=20

Use a text editor like Notepad to check and make any changes necessary.

If all else fails, contact Quarterdeck at (213) 392-9851


Problems with SMARTDrive and RAMDrive
Choosing between SMARTDrive and RAMDrive

In general, SMARTDrive gives better overall performance than RAMDrive.  One exception is output performance for frequently written files.  Another is increasing performance on networks.  SMARTDrive is recommended; however, if you choose to use RAMDrive, a new version of RAMDrive is included with Microsoft Excel.  This version performs significantly better than older versions.  RAMDRIVE.SYS is located on the Microsoft Excel Utilities 1 disk.  If you wish to use RAMDRIVE.SYS in expanded memory, you must use this version of RAMDRIVE.SYS.

For detailed technical information on RAMDrive, see the document titled "Getting the Most from Your Hardware with Microsoft Excel" which is available directly from Microsoft, see the Bonus Kit order form in the Microsoft Excel package.


Error with EMM386.SYS Device Driver
Problem:  Error with EMM386.SYS device driver

The following error message appears after installing EMM386.SYS device driver included with Microsoft MS-DOS version 4.01,:

EMM386 Exception error #13 @ xxxx:xxxxxxxx CODE xxxx

PRESS ENTER TO REBOOT.

Solution:

The error means that the 80386 microprocessor has encountered a general protection violation.  Because the EMM386 driver operates the 80386 chip in virtual real mode, the microprocessor checks for valid memory accesses.  If a program tries to access memory that it is not allowed to access, the 80386 chip generates an exception fault error, which is detected by EMM386.SYS.

The 12 hexadecimal digits following the error (represented by x's above) are the address of the machine language instruction following the instruction that caused the exception error.  This number is given in CS:EIP format, where CS is the code segment, and the EIP is the instruction pointer (relative to the code segment).  This value indicates where in memory the CPU was executing instructions when the exception occurred.  It is sometimes possible to determine from this value what software caused the exception to occur.

This error should not occur on systems that are 100 percent IBM compatible. Due to the hardware intensive nature of the EMM386 device driver, strict IBM hardware compatibility is required.  If this error does occur on your system, the EMM386.SYS device driver needs to be modified by your machine's manufacturer.

The following is a list of Intel 80386 protected mode exception errors and their names:

CODE	MEANING

0	Divide error

1	Debugger interrupt

2	Nonmaskable interrupt

3	Breakpoint

4	Overflow interrupt

5	Array boundary violation

6	Invalid opcode

7	Coprocessor not available

8	Double fault

9	Coprocessor segment overrun

10	Invalid task state segment

11	Segment not present

12	Stack exception

13	General protection violation

14	Page fault

16	Coprocessor error


"0 Bytes Available Contiguous Extended Memory" Reported
Problem:  "0 bytes available contiguous extended memory"

The MEM command reports "0 bytes available contiguous extended memory" when another device driver or program makes a call to extended memory after HIMEM.SYS is loaded in the CONFIG.SYS file.

For example, a CONFIG.SYS file with following lines:

device=c:\himem.sys

device=c:\windows\smartdrv.sys <xxxx> <yyyy>

reports 0 (zero) bytes as available contiguous extended memory with the MEM command (where <xxxx> is the initial cache size and <yyyy> is the minimum cache size).

Explanation:

Available contiguous extended memory is the extended memory available for the interrupt 15h interface.  This memory is not managed by an extended memory manager (HIMEM.SYS in this example).  HIMEM.SYS manages an application's use of extended memory and the high memory area (HMA).  The extended memory manager prevents programs from simultaneously accessing the same memory area.

HIMEM.SYS versions 2.04 and 2.60 have no switch to allocate extended memory to the interrupt 15 interface.

HIMEM.SYS version 2.77, which is shipped with MS-DOS version 5.0, contains an added /INT15=xxxx switch.  This switch allocates a specified amount of extended memory (in kilobytes) for the interrupt 15h interface.  Programs that use extended memory directly and recognize vdisk headers can utilize the memory provided by the /INT15= switch.  For more information, refer to the version 5.0 "MS-DOS User's Guide and Reference."

The programs accessing extended memory using the interrupt 15h call will not get any access to extended memory if HIMEM.SYS is loaded during system startup.  HIMEM.SYS will take control of all the extended memory if no other device drivers are loaded before HIMEM.SYS during system startup.

Solution:

If a program is making an interrupt 15h call to access extended memory, do not load HIMEM.SYS (version 2.04 or 2.60).  Not loading HIMEM.SYS gives access to extended memory through the interrupt 15h call.

This information applies to Microsoft MS-DOS versions 4.0, 4.01, 4.01a, and 5.0.


SMARTDrive Problem with 20 MHz or Faster Computers
Problem:  SMARTDrive Problem with 20-MHz or Faster 80386 Computers.

The following information was formerly available as an application note (appnote), which has now been archived.  This information is not accurate for Windows version 3.0 and 3.00a.  The problem described here was fixed in these later versions of Windows.

The release of the Windows SMARTDrive disk caching utility included with Windows/286 or Windows/386 Version 2.03 does not function correctly on many 20-MHz and 25-MHz 80386 machines.

Machines affected include the 20-MHz IBM PS/2 Model 80-111, the 20-MHz and 25-MHz models of the IBM PS/2 Model 70, the Compaq 386/20, Compaq 386/25, 20and 25-MHz Advanced Logic Research (ALR) 386 machines, the Hewlett-Packard Vectra RS/20, Dell System 310, and others.

Microsoft has confirmed this to be a problem in Version 2.03.  This problem was corrected in Version 2.10.  An updated SMARTDrive is available as an application note from Microsoft Product Support Services by calling (206) 454-2030.


Network Problems

This section deals with networking hardware like Network Interface Cards(NIC)and the software that allows NICs to communicate.  These Network Operating Systems allow the sharing of the network resources like printers and drives.

Although most networks are stable, something will go wrong at some time.  Diagnosing problems can be difficult.  When attempting to diagnose a problem, only change one element at a time.

What is a LAN?

Why use a LAN?

LAN Topologies

RECORDS

NOS

HARDWARE

PRINTING

DRIVES


Problems with Network Operating Systems

Network Operating Systems are number of interrelated programs that work together to give computers and peripherals the ability to accept requests for service across a network and give other computers the ability to correctly use those services.  Servers are computers that share their hard-disk drives, attached preripherals, like printers and CD-ROM drives, and communications devices.  Servers inspect requests for proper authorization, check for conflicts, and then provide the requested service.

For more details SEE:

Packaging Data

Print Servers

File Servers

SEE

for a specific NOS's problems

NOVELL NETWARE

BANYAN VINES

ARTISOFT LANTASTIC

MS WINDOWS FOR WORKGROUPS


Problems with Novell NetWare

Specific Conflicts

~NetWare v3.11 recognizes only the first 16MB of memory.

~"Attempt to allocate memory to read volume definition tables failed" Error.

~NetWare v3.11 runs out of memory when loading NLMs or when an NLM attempts to allocate memory.

~NetWare v3.11 can't load an NLM.

~A NLM won't load from a DOS volume or disk.

~NetWare v3.11 unable to mount volume SYS.

~NetWare v3.11 won't bind a protocol stack to a network board.

~Out of memory errors in NetWare.

with Windows

~Windows hangs when loading with NetWare.

~Windows and NetWare drop connections unpredictably

with Printing

~Using the CAPTURE Command

~Improper Print Job Definitions

~Improperly Printing Laser Printers

~RPRINTER Not Loading Properly at the Workstation

~Warning:-Cannot Create Spool File

~PostScript Jobs Not Printing Properly

~IBM 3816 Page Printer Not Printing Properly

~Cannot Attach to Selected Server

~Printing to a Shared Plotter

~Bad Page Breaks, Font Problems, or Incomplete Print Jobs when Printing from Windows

~Proper Port for Printing Across Network


Windows and NetWare drop connections
Problem:  Windows and NetWare drop connections unpredictably.

Solution:

With NetWare 3.11 make sure that you have Windows 3.1 compatible versions of NetWare's IPX and NETX programs.  To find out the versions type the following lines in at the DOS prompt:

IPX I

NVER

This will give you the IPX version, which should be later than 3.1, and the version of NETX, which should be 3.26 or above.


NetWare recognizes only the first 16MB of Memory
Problem:  NetWare v3.11 recognizes only the first 16MB of memory.

By default NetWare v3.11 recognizes only the first 16MB of server memory.  This is a result of the PC ROM BIOS program which is standard on all Intel-based PCs.

Solution

NetWare v3.11 must be explicitly told to recognize and address memory above 16MB.  The REGISTER MEMORY console command will accomplish this.  On EISA servers s special SET parameter is used.

From the server console:

REGISTER MEMORY start length <RETURN>

start	hexadecimal address of the seventeenth megabyte of memory

length 	amount in hexadecimal of total server memory above 16MB

For an EISA machine use:

SET Auto Register Memory Above 16MB: on <RETURN>

Place either of these commmands in the server's AUTOEXEC.NCF file after the lines that define the server's name and internal IPX number.


Read Volume Definition Tables Failed Error
Problem:  "Attempt to allocate memory to read volume definition tables failed" Error.

Mounting a volume requires more memory than it does to run with a mounted volume.  The mounting process requires extensive consistency checking by NetWare on volume data structures.  As a consequence it is possible to run out of memory when trying to mount a volume.

Solution:

Installing more memory in the server will address the problem.

Another solution is available if you have added name space support to the volume in question.  Use the VREPAIR.NLM to remove one or more supported name spaces.  This will reduce the amout of server memory required to mount the volume, but it will destroy extended attributes for files stored on the volume.


NetWare runs out of memory when loading NLMs.
Problem:  NetWare v3.11 runs out of memory when loading NLMs or when an NLM attempts to allocate memory.

A "unable to allocate short term memory" or "unable to allocate MemoryType" error will result.

Solution:

NetWare v3.11 allocates memory for NLMs on an "as-needed" basis.  This means that no guarantee exists that NetWare can allocate sufficient memory for the NLM to load or run.

If the problem occurs when you are attempting to load an NLM, you can unload at least one other NLM and then try again.  This will free additional alloc memory which may be used to fulfill requests to load a NLM.

A short-term fix is to reduce the minimum number of cache buffers.  This allows NetWare v3.11 to free file cache buffer memory for use by NLMs.  The NetWare console command:

SET minimum file cache buffers:  Numbers

Numbers	the lowest number of file cache buffers the server will allow.

The lowest number is 20.

Another solution is to decrease memory requirements by using VREPAIR to remove volume name space support.  Destroying a NetWare volume and re-creating it with a larger volume block size will also reduce server memory requirements.  These options are both destructive.  Removing name space support will lose extended attributes for files on the volume.  Destroying and re-creating a volume will lose all the data on the volume.

The best solution is to install more server memory.


NetWare Can't Load an NLM
Problem:  NetWare v3.11 can't load an NLM

Aside from insufficient memory, two conditions will cause NetWare to not attempt to load an NLM.  The first is when the NLM isn't found in one of NetWare's volumes or DOS partitions.

The second is when NetWare can't find a loader symbol.  Loader symbols are library functions imported by the NLM.  Without these the NLM can't execute.  Generally, a error like

Loader cannot find public symbol:  symbol

will result.

Solution:

To add paths to NetWare's search path use

SEARCH [add [number] path]

number	number of volume, for example 2

path	path, for example SYS:BIN\NLM

If a SECURE CONSOLE command has been executed before at the server console then a SEARCH can't be executed.

To address the loader symbol problem is to consult the documentation of hte NLM you're attempting to load.  A table of NLMs that the NLM in question relies on for functions to import should exist and load these NLMs before loading the NLM in question.


An NLM won't Load from a DOS Volume or Disk
Problem:  A NLM won't load from a DOS volume or disk.

DOS has been disabled on the server.  REMOVE DOS or SECURE CONSOLE will disable DOS on the server.  If DOS doesn't reside in the server's memory, then NetWare no longer has access to its DOS partition or to DOS floppies.

Solution:

Reboot the server and load the NLM from the DOS partition or floppy.

If the REMOVE DOS or SECURE CONSOLE command is in the server's AUTOEXEC.NCF file, you will have to execute

SERVER -NA

from the DOS prompt.  The -NA parameter causes SERVER.EXE to execute without running its AUTOEXEC.NCF file.


NetWare Unable to Mount Volume SYS.
Problem:  NetWare v3.11 unable to mount volume SYS.

Mounting the SYS volume is the most critical operation NetWare v3.11 performs during initialization.  Initialization consists of "consistency checks" in which the format and contents of all internal data structures are set against a set of pre-defined criteria.  Failure by a data structure to comply results in NetWare not initializing.  Most of the consistency checks occur during the mounting of volumes.

Solution:

Load and run VREPAIR.NLM.  VREPAIR will identify corrupt volume data structures and attempt to repair them.  A copy of VREPAIR on a floppy or the server's DOS partition is a very useful item.  Storing VREPAIR on the SYS volume of the server may be useless if the SYS volume became unmountable.


NetWare won't Bind a Protocol Stack
Problem:  NetWare v3.11 won't bind a protocol stack to a network board.

Solution:

An error in one of the BIND parameters is the most common cause.  The syntax for BIND is

BIND protocol [TO] LANDriver BoardName [Driver Parameter...] [Protocol Parameter] <RETURN>

Protocol	a valid protocol stack

LANDriver	a valid LAN driver or board name

BoardName

A protocol stack other than IPX/SPX requires that the protocol stack be loaded with the LOAD command.  The board name or driver name to which you're binding the stack must also be loaded.

The protocol and driver parameters must be specified.  Typical driver parameters include interrupt numbers, memory addresses, and I/O addresses.  Typical protocol stack parameters include network addresses, domain or zone names, and so on.

A network number that is inconsistent with the configuration of your internet will result in the server reporting routing configuration errors.


Out of Memory Errors in NetWare
Problem:  Out of memory errors in NetWare

A DOS environment memory shortage will result in any of the following error messages:

Could not add "User=John" to the local environment variables.

Could not execute external program "CAPTURE", not enough memory.

There is no room to expand the PATH environment variable with the mapping: "S16:=JUNGLE\SYS:PUBLIC \UTILS"

Solution:

Increase your DOS environment memory space.  Use Notepad to modify the CONFIG.SYS file.  Add the following command:

SHELL=C:COMMAND.COM \P \E:512

The C: is the location of the COMMAND.COM file.  The \P parameter tells DOS to run AUTOEXEC.BAT file on bootup.  The\E parameter sets the environment memory you want to use, in this case 512 bytes.


Windows Hangs When Loading with NetWare
Problem:  Windows hangs when loading with Netware.

This problem could be caused by a number of situations.

Solutions:

Try to load Windows in Real mode with WIN /R, in Standard mode with WIN /S, and 386 Enhanced mode with WIN /3.  If Windows won't load in 386 Enhanced mode but does lad in the other two modes, check the [386Enh] section of the SYSTEM.INI file.  If Windows runs only in Real mode, you probably have problems with you XMS memory manager.  If Windows doesn't load in any mode, something is wrong in you Windows configuration or setup.

Real mode requires 640K, Standard mode requires 1MB, and 386 Enhanced mode requires a 386 or higher CPU and 2MB of memory.  Make sure your workstation has the prerequisite system configuration.

Avoid using IRQ 2 or IRQ 9 for a LAN adapter.  These interrupts are more complex to service than others, and they can cause problems when running Windows in 386 Enhanced mode.  To change the shell's configuration setting to another non-conflicting interrupt run WSGEN.  Use the Novell VPICDA.386 driver instead of Microsoft's VPICD.386 driver if IRQ2 must be used by the NIC.  Change the driver in the [386Enh] section of SYSTEM.INI.  Some video cards also use IRQ 2.

A serial mouse connected to COM1 and a LAN adapter set to IRQ 3 can prevent you from accessing the network.  COM1 users IRQ 4.  This problem usually occurs with Ethernet adapters.  WSGEN can be used to change the NIC's setting to a non-conflicting interrupt.

LAN adapters that use memory addresses in the D000-DFFF range (like the IBM Token-Ring adapter with 16K shared RAM or the SMC Elite16 Combo Ethernet cards) can conflict with Windows' use of this address range for its default EMS page frame.  SEE General Information about Memory, Possible Problems with Memory and  Memory Managers.  Either set the NIC to a different base memory address, or add this statement to your SYSTEM.INI file:

EMMExclude=memlow-memhigh

where memlow=D000 and memhigh=D7FF for the IBM Token Ring adapter

The values for memlow and memhigh will vary with your NIC.  Check the manual for details.

If Windows hangs when loading and you are using the XMSNETx or EMSNETx shell, either switch to the NETx shell or upgrade to Windows 3.0a.


Problems with Banyan Vines

Specific Problems

"There was a problem writing.." Error on Banyan VINES


Problems with MS Windows for Workgroups

Specific Conflicts

Windows for Workgroups and NetWare

Windows for Workgroups and Netware Files


Windows for Workgroups and NetWare
Problem:  Windows for Workgroups and NetWare

This problem relates to WFWG's lack of compatibility with NetWare TCP/IP or with NetWare running over ArcNet.  This applics to WFWG earlier than 3.11.

Solution:

Use the Control Panel Network icon to reach the Networks button in the Network Settings dialog box.  Select Novell NetWare and add it to the system.  Now NetWare will pop up in the "Other Networks in Use" box.  After you restart Windows, the essentials of interoperability between NetWare and WFWG are covered.

If you are using NetWare's Network Basic Input/Output System (netBIOS), you must make sure that your AUTOEXEC.BAT and SYSTEM.INI files are set correctly.  In AUTOEXEC.BAT check for these lines:

NET START	;WFWG network initialized

MSIPX.COM 	;WFWG NetWare IPX transport

NETX.COM /ps=NWserver	;WFWG NetWare shell login

NWserver/username	;WFWG NetWare login to NetWare server

Use any text editor to edit the file.  In SYSTEM.INI check for this lines in the [386Enh] section:

V86MODELANAS=0

And in the [Network] section:

EXCLUDE=0

NetWare's NetBIOS and WFWG should now be completely compatible.  However, if you are using an Open Data-Link Interface (ODI) NetWare driver, you will still have problems.  WFWG is not compatible with these drivers.  You must be running with IPX or Microsoft's IPX equivalents-MSIPX.SYS and MSIPX.COM-to get the two NOSs to talk to each other.


WFWG and NetWare File Server
Problem:  WFWG and NetWare File Server can't be found.

WFWG and NetWare are not functioning together.  The system always has an error message "File server cannot be found.

Solution:

The solution depends on your network architecture.  If you are using a Token Ring LAN, you probably need to delete ROUTE.COM from your AUTOEXEC.BAT.  If the error message still appears, then check your network connections and the hardware.

On an Ethernet network the solution is more complicated.  The PROTOCOL.INI file must have MSIPX as the Adapter.  Open the Control Panel's Network icon.  Pick the Adapters button and select the adapter that's being used by MSIPX, click on Setup, and finally click the Advanced button.  In the "Protocols in Use" box select Novell IPX.  Select the Settings button.  The "Adapter Media Type Value" dialog box should display either Novell/Ethernet or Ethernet_II(DIX).  Whichever of these options is displayed, switch the setting to the other one.


Problems with LANtastic
Problems with LANtastic.

LANtastic is the most popular peer-to-peer NOS.  Although Windows and LANtastic work well together, there are a few conflicts

Specific Conlicts

LANtastic and SMARTDrive

Windows hangs with LANtastic

with Printing

Very Slow Printing on LANtastic


LANtastic and SMARTDrive
Problem:  LANtastic and SMARTDrive

Although LANtastic and Windows work well together, there are a few conflicts.  One of these is disk caching.  LANtastic comes with its own disk cache.  You cannot run this cache with SMARTDrive.

Solution:

Get rid of SMARTDrive.  This will result in an increase in performance.  If, for some strange reason, you are fanatically devoted to SMARTDrive, you can also get rid of the LANtastic cache.  However, it is suggested you get rid of SMARTDrive.


Windows hangs with LANtastic
Problem:  Windows hangs with LANtastic.

Windows hangs at the logo screen and emits a bleeping sound.

Solution:

Redirected local drives in your PATH statement are probably to blame.  You workstation/server system used NET USE to address a local drive as a net drive.  To correct, reboot the system and use a DOS based text editor to open AUTOEXEC.BAT. Make certain that you haven't assigned any local drive letters to network drives.  Save any changes.  The changes will become active upon rebooting the system.


Slow Printing on LANtastic
Problem:  Slow Printing on LANtastic.

Solution:

If your system is being used as a print server, go to DOS and run LANtastic's NET_MGR program.  Go to Shared Resource Management, select the printer resoure and up the Chars/Second Field to 10000.  After that go to Server Startup Parameters and set Printers Tasks to 1, even if more printers are physically attached.  After rebooting, your printer performance should be better.

If you are addressing a remote printer, go to Window's Control Panel and turn off "Use Print Manager."  Print Manager is a print spooler and LANtastic already has one.  (Disabling Print Manager is recommeded on any network.)  Next, turn off "Fast Printing Direct to Port" in the Connect window.  (This is recommended regardless of the NOS you're using with Windows.)  While you're in Connect, insert 900 in the Device Not Selected box, and change the Transmission Retry Timeout to 950.  Finally, set LANtastic to use LPT2  as the network printer port and set Windows and its applications to LPT2.  All kinds of problems may occur when you try to use LANtastic and Windows with LPT1.  Avoid all the headaches by just using LPT2.


Network Hardware Problems

This section cover problems associated with network hardware like Network Interface Cards, bridges, routers and cabling.

Internetworking-Linking LANs

The main purpose of a LAN is to share information.  In a corporation LANs may exist at many sites spread over a local, regional, national, or international area.  To link these LANs the computer industry developed several techniques for extending and linking LANs.

Network traffic generally follows specific paths inside a workgroup.  Traffic between workgroups can travel through many paths, usually through network portal devices called repeaters.  Repeaters pass all data between cable segments.  However, allowing workgroups to communicate without restrictions would consume very expensive resources of a company.  Organizations with busy networks can use network portal devices called bridges that link workgroup LANs while exercising discrimination over the traffic.  Bridges link cable systems but only certain specified traffic pass between those system.

Routers are more complex portal devices than bridges because they have a greater capacity to examine and direct traffic.  Routers are also correspondingly more expensive and require more administration.  Their efficiency at handling LANs linked over a long-distance line overcomes these detractions.  SEE Internetworking  and Internetwork Data Packaging for more information on repeaters, brideges, routers, and their means of communication.

Troubleshooting LAN

Troubleshooting hardware problems begins at the workstation.  The first thing to inspect is the network interface card.  This is ususally the problem if a single workstation fails to operate, but other workstations function normally.  Check the seating of the NIC.  Interrupt conflicts between the NIC and other installed boards may also be possible.  NICs may also have conflicts with memory managers, like QEMM386.  SEE Hints for Using QEMM, General Information on Memory, Possible Problems with Memory, and Memory Managers.

Cable problems are the next thing to inspect.  In the problem above faulty cable may also be to blame.  Unfortunately, cabling problems can be difficult to diagnose.  First, check the seating in the NIC and the wire center port.

The third thing to inspect is the wire closet connections.  The MAU or concentrators should be inspected if one or more workstations do not function.  If the wire center fails, all the workstations connected to the device will fail.  If only one port fails, then the workstation connected to that port will fail.  In either case the entire wire center should be replaced.

SEE ALSO

Network Interface Card

LAN Topologies

Internetworking

Internetwork Data Packaging


 Network Printing Problems

This section covers printers shared on a network.

General Information

~Proper Port for Printing Across Network

~Using the CAPTURE Command

~Printing to a Shared Plotter

Specific Conflicts

with NetWare 3.11

~Partial Pages or garbled printing

~Garbled Printing or printer hangs when using Laser Printers

~RPRINTER Not Loading Properly at the Workstation

~Warning:-Cannot Create Spool File

~PostScript Jobs Not Printing Properly

~IBM 3816 Page Printer Not Printing Properly

~Cannot Attach to Selected Print Server

~Bad Page Breaks, Font Problems, or Incomplete Print Jobs when Printing from Windows

with LANtastic

~Very Slow Printing in LANtastic


Proper Port for Printing Across Network
Problem:  Proper Port for Printing Across Network.

After sending a print job to a network printer and quitting out of the print menu, no print output is generated.

Solution:

To print on a network, it is required that the printer interface be an LPT port.

SEE Ports


Improper Print Job Definitions
Problem:  Improper Print Job Definitions

In NetWare printing a graphic image results in garbled data and partial images printed on each page.  The printer may also hang or be knocked off-line.

Solution:

When a job is printed on a shared network printer using NetWare, print job definition parameters established by the job name specified in the CAPTURE or NPRINT command.  If no job parameter was given, the parameters for a default job are used.

Any job definition used for printing graphics should include these settings

File contents:	Byte Stream

Tabs:	None

Graphic files typically print slowly because the bit-mapped image has to be calculated before it prints.  If a job definition's setting for Enable Timeout and Timeout Count aren't set properly, the print spooler may close the file prematurely and parts of the image print on separate pages.

If the application does not send an end-of-file character after the job, then Enable Timout should be used.  The Timeout Count setting must allocate enough time for the job to complete.  The Timeout Count setting can be established with the CAPTURE command's TI=parameter.


The CAPTURE Command
Problem:  Using the CAPTURE Command

In NetWare incorrect usage of CAPTURE may result in three major problems:

Users may print on an unintended printer.

Partially printed pages

Garbled printing

Solutions:

Printing on an Unintended Printer

The first problem can result from not reconfiguring applications before printing.  If the application they are using is configured for their local printer and the network printer is a different type, users must reconfigure their software before printing.

Partially Printed Pages

The second problem results from modifying the TI= parameter (this governs how long the print spooler waits for more data before closing the print job's queue file) to a value insufficient for the job.

Garbled Printing

The third problem may result from misusing the Q= parameter in the CAPTURE command.  This parameter sends the print job to any queue the user is entitled to and also overrides the queue specified in the job definition.  Problems arise when a print job that the application is configuring to print on a laser printer is sent to a dot matrix printer.  In such a case, garbled printing results.

The problems associated with the CAPTURE commmand can be minimized if the CAPTURE command is issued for the user through a batch file of menu script created by the network administrator.  Problems ususally occur when users without a clear understanding of the CAPTURE command are allowed to issue the command.  Also SEE Garbled Printing


Improperly Printing Laser Printers
Problem:  Improperly Printing Laser Printers

Print job may be garbled or the laser printer may hang when printing in NetWare.

Solution:

The buffer space NetWare uses to contain the control codes for the printer can be exhausted.  The default size of the buffer for initial codes is only 64 bytes.  The size of the buffer for the reset functions is only 16 bytes.  Laser, LED array, and thermal transfer printers require a more complex printer control language to manage all the features available.  Given this, problems can occur even with the proper configurations in PRINTEDEF and PRINTCON.

These buffers can be expanded by adding to the workstations' SHELL.CFG or NET.CFG file these commands:

PRINT HEADER = 	x

PRINT TAIL = 	y

x 	ranges from 64 to 255 bytes

y	ranges from 16 to 64 bytes

Increasing buffer size generally solves problems with downloadable fonts and Postscript printing.


Printing to a Shared Plotter
Problems:  Printing to a Shared Plotter

In a shared environment, output from the application does not go directly to the print device.  Rather, it is placed in a file on the server.  When an application prints to a shared plotter the data is stored on the server.  When the application gets a response from the printing device, the response is not from a plotter, but from a file server.  This is the root of the problem.

Solution:

Most plotters must be directly attached to a workstation that is running the application that requires the potter.  Another solution is to add specialized print server hardware.  With this hardware shared printers can be attached to the hardware without being attached to a workstation.  To print a virtual connection is established between the workstation and the device.  The hardware lets the plotter communicate to the application as if were a locally attached plotter.


RPRINTER Not Loading Properly at the Workstation
Problem:  RPRINTER Not Loading Properly at the Workstation

The error message

Unable to attach to print server SERVERNAME. Error (66)

Unable to complete initialization process.

may occur when running NetWare.

Solution:

The NetWare print server allows shared printers to be attached to workstations on the network.  These remote printers require that the workstation be running the program RPRINTER.  RPRINTER notifies the print server of the remote printer and its print number.  This information was established in the print server set-up done with the PCONSOLE program.  The problem occurs when RPRINTER is run while the print server is performing internal checking immediatelly after the print server is loaded at the file server of a dedicated PC.

This is a timing problem and should resolve itself after a couple of minutes.  Small offices where computers are all turned on at the same time in the morning will frequently be troubled by this problem.

If RPRINTER is loaded via a batch file like AUTOEXEC.BAT a modification to the batch file may prevent the problem.  This modification assumes that PSERVER is loaded and exists.  If loading the print server is discretionary, do not make similar modifications.  The print server and RPRINTER must be loaded successfully to escape the loop.

:P-LOOP

RPRINTER printserver printer#

IF errorlevel 1 GOTO :P-LOOP

ECHO Remote Printer Installed

printserver	name of the print server as defined in PCONSOLE

printer#	printer number (0 to 15) in PCONSOLE


Warning - Cannot Create Spool File
Problem:  Warning-Cannot Create Spool File

Error occurs when someone attempts to print to a shared printer.  This error occurs when free disk space on the file server's SYS: volume drops below 2MB to 3MB or only 20 to 30 directory entries are available on the SYS: volume.

This error is not fatal.  However, it can cause print jobs to print improperly because NetWare does not open disk files for print jobs on the server.

Solution:

If free disk space is less than 2 to 3MB, two options are available.  First, you can remove files from the file server.  If no other volumes are available, more disk space must be added to the file server.  This will require running NETGEN or ELSGEN for NetWare 286 or INSTALL NLM for NetWare v3.11.

If not many free directory entries, then you must reconfigure the file server using NETGEN.  This problem won't occur on NetWare v3.11.


PostScript Jobs Not Printing Properly
Problem:  PostScript Jobs Not Printing Properly

PostScript print jobs fail to print properly or the printer hangs when printing in NetWare.

Solution

Check to see if the proper PostScript printer driver is installed and configured correctly for the printer and application.

The next step is to check that the Print Job Definition's File Contents setting is set to Byte Stream.  If not, NetWare will try to interpret and print control character in the print job, rather than passing them to the printer's ROM for interpretation.

The CAPTURE or NPRINT command must use the NT (No Tabs) and NB (No Banner) parameters.  NT tells the print spooler that the job is a Byte Stream file.  NB is required because the banner is generated by NetWare.

When the buffers NetWare uses for control codes are full, the codes can cause problems.  Change the workstation's SHELL.CFG or NET.CFG file to include the following commands:

PRINT HEADER = 255

PRINT TAIL = 	64


IBM 3816 Page Printer Not Printing Properly
Problem:  IBM 3816 Page Printer Not Printing Properly

With the NetWare print server, print jobs on the IBM 3816 Page Printer may begin to print, stop and appear to hang.

Solution:

The problem is the interface between RPRINTER, the PC and the printer.

The pin outs on the printer cable should first be verified.  Check the following:

PC PIN	PRINTER PIN

2	3

3	2

4	5

5	20

6	4

7	7

8	4

Next, verify the printer, the COM port, and the print server are all configured for the same interface settings.

The DIP switch setting on the printer should have DIP switches 1 to 3, the COM port and the print server configuration all set for the same speed.  DIP switch 6 should be On.  All other switches should be Off.


Cannot Attach to Selected Server
Problem:  Cannot Attach to Selected Server

This error happens because the job definition specifies a file server that is not on the network.

Solution:

The most common causes of this message are found on multiple file server networks.  When print job definitions are created with the PRINTCON program, any file server may be specified as the file server for the job.  If the specified file server is down when a user selects a print job definition, the error occurs.  Either change the file server in the print job definition or make sure the file server is up.

The second cause is that as LANs grow, new file servers may be added and the LAN's configuration adjusted as needed.  One change might involve renaming the file server with the NETGEN or ELSGEN program.  When this server is booted, the name change will take effect.  Any print job definitions containing the old name for the file server must now be changed.  Otherwise the error will result.


Bad Page Breaks, Font Problems, or Incomplete Print Jobs When Printing with NetWare
Problem:  Bad page breaks, font problems, or incomplete print jobs when printing from Windows.

Solution:

When printing to a network printer, disable the Windows' print spooler by using a text editor, like Notepad, to change the spooler statement to NO in the [windows] section of the WIN.INI.  From PRINTCON in NetWare change all the print job configurations to the following:

Suppress Form Feed:	Yes

Autoendcap:	No

Enable Timeout:	No

If you are using CAPTURE to redirect local output to network printers, make sure you include the "NFF NT NA TI=0" options in the CAPTURE command.


Network Drive Problems

 Problems associated with file servers are covered in this section.

Specific Conflicts

with Banyan Vines

"There was a problem writing.." Error on Banyan VINES

with Novell NetWare

~Warning:-Cannot Create Spool File


Performance

This section gives tips on improving your system's performance.

HARDWARE

PRINT

APPLICATIONS

SYSTEM

NETWORK


Increasing Hardware Performance

Increasing Disk Drive Performance


Use FastDisk for Increasing Disk Drive Performance
Suggestion:  Use FastDisk for Increasing Disk Drive Performance.

FastDisk is a disk driver that gives 32-bit disk access.  This can significantly improve disk drive access.  Unfortunately, it may not work with all systems.

Method:

To check to see if your PC is capable of running FastDisk, open SYSTEM.INI with any text editor.  Check the [386Enh] section for the following lines:

[386Enh]

device=*wdctrl

device=*int13

The asterisks in these linesindicate that the device drivers named are internal to the Windows kernael, not located in separate files.  *WDCTRL is what actually speaks to the Western Digital 1003 or ST506 controller.  This controller supports a set of disk drives that includes MFM drives, many IDE and ESDI drives as well.

Windows Setup also writes one more line into SYSTEM.INI if the above two line are present:

[386Enh]

32BitDiskAccess=Off

To change this setting open Windows' Control Panel's 386 Enhanced Dialog box.  Click on the Virtual Memory button.  At the bottom left you'll see the Use 32-Bit Disk Access box.  Click on it to place an X in the box.

Microsoft has built checking routines into WDCrtl to verify that a hard disk controller was truly WD 1003-compatible before really using the disk.  However, this is not a catch-all check.  The worst that could happen is that Windows may hang when you try to start it.  To cure this open SYSTEM.INI with a text editor in DOS and change the line "32BitDiskAccess=on" to "32BitDiskAccess=off" in the [386Enh] section, then restart Windows.


Increasing Printing Performance

General Purpose Printing Speed Solution


General Purpose Printing Speed Solution
Suggestion:   General Purpose Printing Speed Solution

The method below creates a printer redirection before running Windows and lets Windows think it is printing to a DOS disk file instead of to a hardware port.  It is useful to accomplish the following:

1.  Allows printing in virtually any environment that is normally incompatible with Windows direct print methods.  This method should provide a workaround in any situation where printing may be accomplished at the DOS level but not from Windows.

2.  Greatly improves printing speed on networks.

3.  Solves the problem with a print job not appearing until Windows is closed, which occurs on networks under DOS Version 4.01.

This method works with Windows/286 and Windows/386 Versions 2.03, 2.10, and 2.11 and Excel Versions 2.00, 2.01, and 2.10.

Method:

To use this printer redirection method, do the following:

1.  First make a backup safety copy of your WIN.INI file under a different name.

2.  Edit your WIN.INI file as follows:

Old	New

[ports]	[ports]

LPT1	LPT1.PRN (or the port the network printer is accessed by)

3.  Set up any network printer redirection normally used at the DOS level, and then start Windows.

Explanation:

Windows now thinks this port assignment is a DOS disk file rather than an LPT port, so it uses write() to output any printer file directed to this "port."  The network redirector then can send whole strings of characters to the printer instead of one character at a time.  Note: With Win3, connecting to the LPT1.OS2 port accomplishes the same thing.

If you have only LPT1: redirected in the normal manner, Windows treats this as a hardware port and uses INT 17h to print, i.e., the network redirector's hook sends a single byte at a time.  The performance gain appears to be about 50 percent when the change is made.

The same may be done with communications/serial ports.  This workaround appears to improve network communications speed via the serial port for programs such as DynaComm under Windows.  It can be tried with network serial printers, also.

This technique is not guaranteed to work on all network systems and has not been comprehensively tested.  It may not work on Novell networks or other networks that are not 100-percent Microsoft redirector (MS REDIR) compatible.


Increasing Applications Performance
Increasing Application Performance

To Optimize Windows Applications

1.  Install at least 4MB of RAM.  A 4MB RAM machine performs twice as fast as an 2MB PC.

2.  Use Standard Mode for some applications.  Some applications perform 10-20% faster than in Enhanced mode.  Amipro runs much faster in standard mode than in enhanced mode.

3.  Use Disk Caching and RAM Drives.  Install Windows' SMARTDrive or other such utility.  Take heed of any warnings when using these utilities.  SEE Memory Managers.

4.  Avoid background DOS session by proper setting of PIF files for DOS applications.

5.  Close a few Windows.  Since Windows has no means to allocate a certain percentage of process time to each active window, it is important to make sure that no useless Window is claiming the system resources.

6.  Use Draft Mode.  If the Windows' application can switch to "plain-text" mode, which uses fast, "Windows' System Fonts" instead of bitmapped fonts, then use the plain-text mode.

7.  Avoid screen font scalers.  Turn off Adobe Type Manager (ATM) or like programs which generate screen fonts on-the-fly until final layout time.

8.  Maximize the current Window.

General Performance


Increasing System Performance


Increasing Network Performance


Graphic Applications Problems

SEE

Freelance Graphics


Problems with Freelance Graphics

General Information

The Lotus .ini File

Specific Conflicts

"Initialization Error" Printing from Freelance for Windows 1.0

Some Printer Fonts aren't listed in FLW

FLW Prints Black & White Only

DDE Error when using Freelance Graphics


DDE Error when using Freelance Graphics
Problem:  DDE Error when using Freelance Graphics

When running a Windows application, and using the Dynamic Data Exchange command Poke, to insert information from the Windows application into Freelance Graphics for Windows the DDE Poke command is executed, the following Windows error message is displayed on the screen: "Dynamic Data Exchange Time Out Error".

Solution:

Freelance Graphics for Windows does not allow access for the DDE Poke command. This was a design feature for the current version of FLW. A suggestion has been made to include access to the DDE Poke command for future updates of FLW.


Creating DDE links from 1-2-3
Problem:  Creating DDE Links from 1-2-3 for Windows

Various problems exist with creating links from 1-2-3 for Windows.

Solution:

If your DDE links from 1-2-3 are not working correctly check the following:

1. That the 1-2-3 file is saved with a filename.

2. That 1-2-3 directory is in the path statement.

3. If graphs are not pasting correctly check that you have added the graph to the worksheet and then copied to the clipboard.

4. If, when numbers are pasted from another product into 1-2-3, they are pasted as labels check that the highlighted range in the server (source) product does not include a blank space before any of the numbers. A blank space is regarded by 1-2-3 as a label.


Problems with Lotus Approach

General Information

The Lotus .ini File

Specific Problems

Installing Approach on a Peer-to-Peer Network

Requirments for Approach Network Support

Using Paste Link with MS Word or Excel

Internal Error when Printing in Approach

Print Out is choppy in Approach

Approach Fields appear in Black


Installing Approach on a Peer-to-Peer Network
Problem:  Installing Approach on a Peer-to-Peer Network

Installing Approach 2.1 on a Peer to Peer network, such as Lantastic, Novell Lite or Windows for WorkGroups can cause some problems.

Solution:

If you have a dedicated server, the normal procedure for installing using  the /n switch and then performing node installations for each machine needing to use Lotus Approach, is the method to use.  The problem arises when you want to use the server as a node. Use the following procedure:

Server Installation

1. Select File|Run from the Program Manager.

2. Type a:\install /n for a network installation. This copies the installation files to the Approach directory so that other users can perform Node installations. If you don't use the /n switch you won't be able to run Approach from a Node - every node requires it's own copy of the SmartIcons. These must be installed for Lotus Approach to run successfully.

3. Enter your name and company name at the prompt and click OK. Click OK to confirm that your entry is correct. Select FULL INSTALLATION and Click Next.

4. Select a directory to install the Approach files: C:\APPROACH. Click Next.

5. Select a directory to install the Licenser utility: C:\LICENSER. Click Next. This application allows you to setup licenses for the Approach program files, so only the correct number of users can access the program at the same time - depending onthe number of licenses you have purchased.

6. Select a directory for the Licenses to be stored: F:\LOTSHARE. Click Next. After selecting this directory the Lotus Approach installation will begin and all the necessary files will be copied to the server's local drive. The \LOTSHARE directory MUST be installed to the root directory of a network drive, in order for you to be able to run the Approach program from any machine. This means that after completing installation on all nodes you will need to copy the \LOTSHARE directory back to the server, so that all machines see the directory as a subdirectory of a network drive.

7. Once the installation is complete, open the Windows File Manager. (If you're using Lantastic or another Peer to Peer network see your network documentation about sharing the directories.) Select the C:\APPROACH and select the Disk|Share As... command. Give FULL ACCESS to this directory and select to Re-Share on Startup. Click OK. Repeat this step for the C:\LOTSHARE directory. All nodes must have full read/write access to these directories.

8. Run the Licenser Utitlity, from its icon on your desktop, to setup the correct number of licenses for your version of Lotus Approach.

9. If you plan to use the server machine to run Lotus Approach, you must perform a NODE installation at this time. From the Program Manager select File|Run and type C:\APPROACH\INSTALL and click OK.

10. Perform a minimum installation to directory C:\APP21 (or another name, but NOT APPROACH) Once this is complete you should be able to run Lotus Approach successfully from the server machine.

Node Installation

Each machine using Lotus Approach on a network, requires it's own copy of the Lotus SmartIcons. This is required because of the user configurability.

Any node which doesn't have an APPROACH\ICONS directory must perform a Node installation before they can use Approach from the server machine. If you attempt to launch a network installed version of Approach without this directory on your local machine you will be forced to run the Approach node installation. This will copy the icons, examples, and templates to your local machine, unless you perform a minimum installation, when only the icons will be copied. The install will also setup a Lotus Approach icon on your windows desktop.

1. From the machine you want to install to, Select File|Run from Program Manager and type the DRIVE:\PATH\install and click OK. The Node installation will launch and you'll be given the option to perform a minimum, custom or full installation. A full node installation doesn't install and of the Approach program files.

2. Once the installation is complete you should be able to run Approach from the icon created by the install. You'll be running the program from the server, but using your own local set of configurable icons.

To Complete the installation copy the \LOTSHARE directory to the server.


Requirments for Approach Network Support
Problem:  Requirements for Network Support of Approach

Version 2.x should work successfully under most networks types, but has been specifically tested on the following:

1) Novell Netware

2) Netware Lite

3) Microsoft LAN Manager

4) Banyan VINES

5) LANtastic networks

6) Windows for Workgroups

Make sure SHARE is loaded on the server as well as the local machine.  Also, dBASE files must be marked as "Local Databases are Shared".  Paradox files must have a network control path set.

Trying to share the executable of Approach over a Windows for Workgroups network results in the title screen being displayed and then Approach closes.  Sharing of files works correctly; just not sharing of the Approach executable.


Using Paste Link with MS Word or Excel
Problem:  Using Paste Link With Microsoft Word or Excel in Approach

Solution

If the selection for Paste Link is not available with Microsoft Word or Excel, try reinstalling Word or Excel. The Paste Link feature should now be available.

Starting another VEW file or application from an Approach VEW file:

1. Open File Manager and Object Packager.

2. Drag desired VEW file from File Manager into the Object Packager window.

3. Edit|Command line in Object Packager to be the exact path of the VEW file e.g. C:\approach\test.VEW

4. It is also possible to change the icon and the label for the icon, using the button and menu option respectively.

5. Edit/Copy Package, to copy the package to the clipboard.

6. Switch to your Approach VEW file and Edit/Paste Special and select Packaged Object.

7. When you double-click the icon you start the VEW file. However if it is already running you will be informed and then you will have to use the Approach Window menu.

**NOTE -- This is an embedded package; you're working with the COPY of the VEW, not the original VEW file.  Any changes made through the package copy WILL NOT be reflected in the original VEW it was based on. **


Internal Error when Printing in Approach
Problem:  Printing in Approach results in an Internal Error Dialog

Creating a disk file from Approach by adding a Generic/Text Only printer and making that the active printer results in an Internal Error Dialog when trying to print to this printer from Approach.

Solution:

Check to see if Adobe Type Manager is installed.  Some versions of ATM conflict with the Generic/Text only driver.  Upgrade ATM to version 2.5.


Print Out is choppy in Approach
Problem:  Print out is choppy in Approach

The first few lines are OK and the next line is faded or missing.

Solution

Try turning Print Manager off.  If the printer has 1MB or less of memory this can cause memory overflow problems on the printer.

Try sending the print job to a file.  After the print job is sent to the file, use File Manager to select the file which will always by default be located in the subdirectory of where you were working.  Then goto File and then goto Copy and where it says TO: specify the printer port.

Example:    From:  C:\APPROACH\PRINTJOB1 TO:    LPT1

You will get a message that says 'Replace File...' select Yes.  I want to Print to a file:

1) Go to the Control Panel

Printers

Add        (reselect your printer driver)

Install     (while the newly installed driver is highlighted)

Connect (scroll through the Ports until you find FILE, select it)

OK

The option to select 'Print To File' should now be available in Approach.

2) Printing to an ASCII file:

Go to the Control Panel

Printers

Add        (Select Generic/Text Only driver)

Install     (while the newly installed driver is highlighted)

Connect (scroll through the Ports until you fine FILE, select it)

OK

When you want to print to a file in Approach select

File|Print..

Check the Print to File box

Click Setup

Change the selected printer ro Generic / Text Only

Click OK

Click OK to Print and supply a file name.

Approach will print to this file."^


Approach Fields appear in Black
Problem:  Approach Fields appear in black

When printing from Approach to a HP Deskjet, the fields appear all in black or with black lines through them.

Solution

Update the HP Deskjet printer driver to version 3.1 or higher."


Added Printers not seen in Printer Setup for MS Word
Problem:  Added Printers Not Seen in Printer Setup with Microsoft Word for Windows

When more than 15 printers are added through the Control Panel, some  printers are not listed in the Printer Setup dialog box in Microsoft  Word for Windows. Windows can't have more than 16 printers installed  at any one time, and Word for Windows can't display more than 15  printers at any one time. However, it is possible to rearrange the order in which the printers are listed, so a select 15 of the 16 will be listed as available.

Solution:

For Word for Windows to recognize a certain group of printers, edit the WIN.INI file. This behavior occurs because when these printers are installed, they are listed in the WIN.INI in their order of installation. The most recently installed printer is added to the bottom of the list and consequently will not show if it is past number 15 in order.

To rearrange the order in which the printers are listed, follow these steps:

1. Edit the [Devices| section of the WIN.INI using a text editor such as Windows Notepad. The line(s) in regard to the desired printer(s) must be cut and pasted above their current position. Put these lines ahead of the 15th printer, so the last printer you want to access is the 15th listed or less. Save the WIN.INI.

2. Close Windows. After returning to the system prompt, restart Windows and Word for Windows.

3. Word for Windows will now list the printers as they are shown in the WIN.INI. The new arrangement should show the 15 desired printers.

4. If the printer you expect to see is not listed within the first 15 printers, you should rename WINWORD.INI to WINWORD.BAK. Before renaming WINWORD.INI, close Word for Windows. (For archiving purposes, it's best to rename rather than delete an *.INI file.) Word will be forced to create a new WINWORD.INI file and will read the updated information from the WIN.INI file when Word for Windows is restarted.

5. When you restart Word for Windows, you will be prompted for your name. After entering your name, open the File menu, choose Printer Setup, and select a printer from the new list.


Error Saving after Multiple Edits in MS Word
Problem:  Error Saving after Multiple Edits in MS Word

In Microsoft Word for Windows, if you make several text and formatting changes without saving your work and then command Word to perform an action that involves more editing or formatting changes than Word has memory to handle, the following error message displays:

Too many edits; operation will be incomplete. Save your work.

Solution:

Performing a full save on the document -- that is, choosing Save As from the File menu, choosing the Options button and turning off Allow Fast Saves -- helps avoid this error message. A full save eliminates pointers and makes the text contiguous rather than a large, linked list.

The following are other suggestions for working around this error message:

 - Try freeing up as much conventional memory as possible by implementing the memory-saving techniques listed in the "Microsoft Word for Windows User's Reference," Appendix B, under "Low Memory."

- Turn on Autosave in the Utilities Customize dialog box (versions 1.x) for a reminder to save when you have been editing a document for a length of time or have made many changes.

 - Select smaller portions of the document and perform the operation. For example, opening a large document and replacing every "e" with an "x" will probably fail. Instead, select two or three pages of the document and do the same thing.


"Cannot Open Output File.." Error Message in MS Word
Problem:  WinWord Error Message: "Cannot Open Output File. Check to Ensure..."

In Microsoft Word for Windows, if you print to a write-protected file, Word returns the following error message:

Cannot open output file. Check to ensure path and filename are correct.

If a file is flagged read-only, with the Windows 3.0 File Manager's Change Attributes command or with the MS-DOS ATTRIB command, you cannot direct printed output to that file name. Printing to an existing file constitutes an attempt to save changes to the original  file, which is not allowed on read-only files.

Solution:

 Steps to Reproduce Problem

 1. Create and save a document in Word for Windows. Close the document and minimize Word for Windows.

 2. Assign a read-only attribute to the file created in step 1. To do this in the Windows 3.0 File Manager, select the file from the File Manager's Directory Tree. From File menu, choose Change Attributes and select the Read Only check box. Choose the OK button.  To change the file's attributes from the MS-DOS prompt, use the MS-DOS ATTRIB command. At the MS-DOS prompt, type "ATTRIB <filename> +r" (without the quotation marks).

3. Maximize Word for Windows and create a new document (or open an existing document).

4. Print the document to File. In Word for Windows 1.x, from the File menu, choose Printer Setup. Select a printer that is configured to print to the FILE port. Choose the OK button. From the File menu, choose Print and choose the OK button.  In Word for Windows 2.0, from the File menu, choose Print and select the Print to File option. Choose the OK button. Note: You can also follow the same steps as those for version 1.x.

5. When prompted to enter an output file name, type in the name of the read-only file you saved in step 1. Choose the OK button.

6. When the message "Overwrite existing output file?" appears, choose the Yes button.  Word returns the following error message:

Cannot open output File. Check to ensure path is correct.  Word for Windows also creates a temporary file on the same directory where the write-protected file resides.


UAE Occurs When Running Spell Checker in MS Word
Problem:  UAE Occurs When Running Spelling Checker in WinWord Footer

In Microsoft Word for Windows version 2.0, when you run the Spelling command on a document that contains a misspelled word in the header and a misspelled word in the footer, an Unrecoverable Application Error (UAE) occurs when the spelling checker begins to check the footer. The header and footer must BOTH contain misspelled words to generate the UAE.

Microsoft has confirmed this to be a problem in Word for Windows version 2.0. This problem was corrected in Word for Windows version 2.0a.

New or updated Microsoft products can be obtained from Microsoft End User Sales at (800) 426-9400. If you are outside the United States, contact your local Microsoft subsidiary. To locate your subsidiary, call Microsoft International Customer Service at (206) 936-8661.

Solution:

In Word for Windows version 2.0, the spelling checker checks the entire document, including headers, footers, annotations, and footnotes (unless you select a portion of the text before running the spelling checker). If you position the insertion point in the body text and choose Spelling from the Tools menu, the spelling checker checks the document in the following order:

1. Body text

2. Footnote

3. Header

4. Footer

5. Annotations

If you choose the Spelling command when the insertion point is positioned in a header pane, only the header text is checked. This is also true for the footer, footnote, and annotation panes.

To check the spelling of hidden text, you must first display the hidden text. To do this, choose Options from the Tools menu, select the View category, and select the Hidden Text check box.

To avoid receiving an unrecoverable application error when using the spelling checker in a footer, use one of the following methods:

A.  Position the insertion point in the footer, and run the spelling checker. Position the insertion point in the body text, and run the spelling checker on the rest of the document.

B.  Select the entire document (CTRL+Keypad 5) before you run the spelling checker. This ensures that the Spelling command checks only the body text of the document and then displays the following message:

Word finished checking the selection. Do you want to continue checking the remainder of the document?

Choose the No button to avoid checking the footer and receiving a UAE.  You can use the spelling checker on the header and footer separate from the body text using the first method.

C.  Format the footer for no proofing using the following steps:

1. From the View menu, choose Header/Footer.

2. Select Footer, and choose the OK button.

3. Select the contents of the footer. From the Format menu, choose Language.

4. From the Mark Selected Text As box, select the (no proofing) option, and choose the OK button.

This stops the spelling checker from checking the footer.

D.  Note: The following steps assume you are working in normal view. From the View menu, choose Normal to switch views.

1. In a new document, type the word "body text" (without the quotation marks) in the body of a document.

2. From the View menu, choose Header/Footer. From the Header/Footer dialog box, select Header, and choose the OK button. Type the word "hedder" (without the quotation marks) in the header.

3. From the View menu, choose Header/Footer. From the Header/Footer dialog box, select Footer, and choose the OK button. Type the word "footerr" (without the quotation marks) in the footer. From the footer icon bar, choose the Close button.

4. Press CTRL+HOME to move the insertion point to the beginning of the document.

5. From the Tools menu, choose Spelling.

6. The spelling checker indicates that "hedder" is misspelled; choose the Change button. Next, the spelling checker indicates that "footerr" is misspelled, and the following message appears followed by the Cancel and Retry buttons:

RECOVERABLE APPLICATION ERROR. MSWORD failed in MSWORD. Ignoring fault is risky.


Word Printer Driver Version is different from Control Panel
Problem:  WinWord Printer Driver Version is Different from Control Panel

The printer driver version referenced by the Microsoft Word for Windows Print Setup command may differ from the same printer driver referenced in the Windows Control Panel. This occurs if a printer driver for your active printer is located in the Word for Windows  program directory.

This discrepancy can cause problems if the printer driver that Word is using is an older version that is incompatible with the current Windows environment. Symptoms of this problem may include the unavailability of TrueType fonts in Word when you are running Word in the Microsoft Windows operating system version 3.1.

Solution:

To correct this problem, locate the old version of the driver being accessed by Word, and delete it from your hard drive.

If you are installing Word for Windows on a network where some of the workstations are running Windows version 3.0 and some of the workstations are running Windows version 3.1, you should copy the Windows version 3.0 HPPCL5A.* files to the user's Windows \SYSTEM subdirectory before running the Word for Windows Setup program. This problem was corrected in version 2.0b of Word for Windows. During a server installation, Word 2.0b places the HP LaserJet III drivers in a subdirectory called HP_PRINT. This prevents Word from accidentally using the old driver while running under in Windows 3.1.

Note: Versions previous to 2.0b still require that the HPPCL5A.DRV file be renamed or removed. This correction only applies to new setups of Word 2.0b.

When you choose Print Setup from the File menu (Printer Setup in Word for Windows version 1.x), Word looks for the printer driver using the following search order:

1. The directory where Word for Windows is installed.

2. The current working directory. To find the current directory, choose Open from the File menu, and note the directory referenced in the Directories area of the Open dialog box. In Word version 2.0, the DOC-path setting, which is located in the [Microsoft Word 2.0| section  of the WIN.INI file, points to the working directory.

3. The Windows \SYSTEM subdirectory.


Word Screen Shows varying resolutions on Tseng VGA
Problem:  WinWord Screen Shows Varying Resolutions on Tseng VGA

Microsoft Windows operating system version 3.0 and 3.1 using versions prior to 5.4 of Tseng Laboratories video driver with 16 colors along with a a Speed Star Super VGA video card, the Word for Windows ruler may be displayed in VGA mode while the rest  of the screen is displayed in 800x600 resolution.

Solution:

This functionality is caused by the driver. Because Tseng Lab was unable to write a driver that clearly supported 800x600 in 16 colors, they created the driver with a 640x480 aspect ratio, causing the mixed resolution problem.

This problem was corrected in version 5.4 of Tseng Lab's 256 color video driver. To obtain this driver, call Tseng Laboratories technical support at (215) 968-0502.


Word Setup fails with Norton Close-Up installed
Problem:  Word for Windows Setup Failure with Close-Up/Remote Installed

You may be unable to run the Setup program for Microsoft Word for Windows version 2.0 if Close-Up/Remote version 4.0 by Norton-Lambert is also installed on your computer. The keyboard and mouse drivers may need to be updated before you can successfully install Word for Windows version 2.0.

Solution:

The following modifications are made to the SYSTEM.INI file occur when you install Close-Up/Remote version 4.0.

In the [boot| section, the modifications are as follows:

 mouse.drv=cupmouse.drv

 (modified from: mouse.drv=mouse.drv)

 keyboard.drv=cupkeyboard.drv

 (modified from: keyboard.drv=keyboard.drv)

In the [386ENH| section, the following statement is added:

device=cupvirtd.386

To ensure that you have the most recent keyboard and mouse drivers, contact Norton-Lambert technical support at (805) 964-6767. You can download the current drivers by calling (805) 683-2249 and using the transfer file feature. The files are named cupmouse.drv and cupkeyboard.drv.


MS Draw Disk and RAM Error Messages
Problem:  Microsoft Draw Disk and RAM Memory-Related Error Messages

This section contains a summary of Microsoft Draw version 1.0 error messages related to disk or RAM memory issues, the probable causes for each message, and (if available) method(s) of recourse. When you insert or edit a Draw object in Microsoft Word for Windows version 2.0, these error messages are displayed in an error message dialog box within the Microsoft Draw graphic editor.

Error Messages

1. "Sorry, the disk volume is full. Please save to another disk."  This message indicates Word cannot save the palette because the disk is full.

2. "Memory is nearly full. You should exit from Microsoft Draw or some other application now."

b    This message indicates Microsoft Draw detects available (unused) memory is running low; you should exit Draw now. This message may also indicate that the .TMP file specification is incorrect. This messge may also indicate that OLESVR.DLL and OLECLI.DLL may need to be be re-expanded.

If the file dates of OLECLI.DLL and OLESVR.DLL are earlier than 3/10/92, they should be replaced with the files from the Windows 3.1 disks. On the 5.25-inch disk set, OLECLI.DLL is on disk 4, and OLESVR.DLL is on disk 5. On 3.5-inch disks, OLECLI.DLL is on disk 5 and OLESVR.DLL is on disk 4.

Use the following commands to expand the two files off the Windows disks:

OLECLI.DLL

expand (x):olecli.dl_  c:\windows\system\olecli.dll

OLESVR.DLL

expand (x):olesvr.dl_ c:\windows\system\olesvr.dll

 3. "Memory is very full. The previous operation is no longer undoable."  This message indicates Draw detects available memory is running even lower. The program frees memory by releasing the information necessary to Undo the last operation; therefore, the Undo command is unavailable for the last operation.

4. "Sorry, memory is full. Microsoft Draw must quit immediately."  This message indicates memory is so full that Draw cannot continue;  Draw must exit immediately WITHOUT giving you the opportunity to save your drawing.

5. "Sorry, there is insufficient memory or other system resources to run Microsoft Draw."

This message indicates that during program startup, Microsoft Draw detects that there is not enough memory (or other resources) to run.  Draw quits immediately.

6. "Sorry, memory is too full to perform the operation."  This message indicates there is insufficient memory available to perform commands like Copy or Paste, or more complex operations such as updating the drawing to the destination application, disassembling a metafile, or saving the undo state for any operation that modifies the drawing.

7. "Sorry, memory was too full to draw everything; some parts are not Shown."  This message indicates there is insufficient memory (or other system resources) to draw the entire drawing to the screen; parts of the drawing may not display.

8. "Sorry, the Microsoft Draw window may look incorrect owing to insufficient system resources."  This message indicates there are insufficient system resources to draw everything you created.

9. "Sorry, memory is too full to perform the operation and the previous operation is no longer undoable."

This message indicates there is insufficient memory available to save the undo state for the operation you requested, and the previous undo state is already deleted; therefore, the Undo command is unavailable.

10. "If you go on with this operation, you will not be able to undo it owing to insufficient memory."

This message indicates there is insufficient memory available to save the undo state for the operation you requested; you can continue the operation, or you can choose Cancel.

11. "Sorry, memory is too full to cut to the Clipboard; clear the selection instead?"  This message indicates there is insufficient memory available to perform the Cut command; you can clear instead (by choosing the OK button), or you may choose Cancel.

12. "Sorry, the picture in the Clipboard is too large to paste."  This message indicates there is insufficient memory or system resources to paste the picture from the Clipboard.

13. "Sorry <filename> is too big to paste into Microsoft Draw."  This message indicates the named graphics file is too large to paste.

14. "Sorry, unable to import <filename>. Make sure there is enough memory available."  This message indicates the graphics filter ran out of memory while trying to import the named graphics file.


"Word Cannot Save or Create File" Error on NetWare
Problem:  "Word Cannot Save or Create File" Error with NetWare

If you do not have READ, WRITE, CREATE, MODIFY, and DELETE or ERASE rights in the network directory where you are trying to save a file, Microsoft Word for Windows version 2.0 returns the following error message on a Novell network:

Solution:

READ, WRITE, CREATE, and DELETE (or ERASE, for earlier versions of  Novell) are the minimum rights required for saving a file the first  time. READ, WRITE, CREATE, MODIFY, and DELETE are necessary for saving  over a file previously saved to the network drive. You must have MODIFY rights if you are trying to save over a previously saved file.

You can check your rights by going to MS-DOS Shell and typing RIGHTS  at the prompt. If you have the above rights, the response should include the following:

[R WDM C|

The above-mentioned error also occurs if you DO have the correct rights in the appropriate directory, but one or more of the following conditions exist:

1. You do not have rights on the current directory (that is, the directory Word displays above the Directories box in the File Open dialog box). This error occurs when you open or save a file. You must change the current directory in the File Open or File Save As dialog box to a directory in which you have rights.

2. The directory is Search Mapped (for example X:\USERS\USER1).

3. You have gone to Shell and moved to the root of X: (for example, by typing "CD\").

4. You do not have READ, WRITE, and CREATE rights at X:\.

5. You try to save a file to X:TEST.DOC.  This error occurs because Novell Search Drives do not hold their places if you move between directories on the same Search Drive. For  example, when you type "X:" after logging in, you are taken to X:\USERS\USER1 because that is the Search Map that was set up with the login script. However, if you move from the X:\USERS\USER1 to the X:\directory, the Search Map changes to X:\.

In the above example, if you usually type "X:\TEST.DOC" in the File Name box when you save the file, you now receive the "Cannot Open Cannot Create File" error message because Novell is mapping X: to X:\ (where you do not have rights) instead of to X:\USERS\USER1.

Create a Map Root to the directory in which you usually store files.  This prevents Word from changing the current directory to a directory where you do not have rights.  Note: In this case, Novell is behaving similar to MS-DOS. For example, if you move from D:\WINDOWS to the C drive, you can copy a file with the command COPY TEST.DOC D: and it is copied to the D:\WINDOWS directory.


GPF Tool Bar is double-clicked in Word
Problem:  GP Fault or UAE When You Double-Click Tool Bar

Microsoft Word versions 2.0 and 2.0a for Windows will generate either a General Protection (GP) fault in the Microsoft Windows operating system version 3.1 or an Unrecoverable Application Error in Microsoft Windows version 3.0 if you do the following:

1. Start Word for Windows without a default document.

2. Double-click a blank area on the tool bar to activate the Toolbar category of the Options dialog box.

3. Under Category, select View.

4. Choose the OK button without making any changes.

Solution:

To launch Word 2.0 or 2.0a without a default document, select the Word for Windows icon, and add the /n switch to the end of the Command Line b in the Program Item Properties dialog box. For example:

C:\WINWORD\WINWORD.EXE /n

Microsoft has confirmed this to be a problem in Word versions 2.0 and 2.0a for Windows. This problem was corrected in version 2.0b of Word for Windows.


GPF Occurs while Running Spell Checker in Word
Problem: GP Fault Occurs While Running Spelling Checker

In versions 2.0 or 2.0a of Word for Windows, if you are in Whole Page Zoom view and the spelling checker flags an unrecognized word in the footer of a  document that contains a date field, a general protection (GP) fault occurs  or your computer may stop responding (hang).

The date fields that cause this error include CREATEDATE, DATE, PRINTDATE, and TIME.

Solution:

Microsoft has confirmed this to be a problem in Word for Windows versions  2.0 and 2.0a. This problem was corrected in Word for Windows version 2.0b.  To obtain new or updated Microsoft products, call Microsoft Consumer Sales at (800) 426-9400. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Customer Service at (206) 936-8661.

To avoid the GP fault or locking the system under these conditions, do one of the following:

 - Avoid running the spelling checker in Full Page Zoom view.

 -or-

 - Select the entire document before you run the spelling checker. This ensures that the Spelling command checks only the body text of the document and then displays the following message:

Word finished checking the selection. Do you want to continue checking the remainder of the document?

Choose the No button to avoid checking the footer and locking the system. You can use the spelling checker on the header and footer separate from the body text by positioning the insertion point in the header or footer and running the spelling checker.

Steps to Reproduce Problem

1. In Word for Windows, open a new document, from the View menu choose Normal.

2. With the insertion point in the body of the document, from the Insert menu choose Date and Time, select any of the available formats and choose the OK button.

3. Position the insertion point after the field result.

4. From the View menu choose Header/Footer, select Footer, and choose the OK button.

5. Type in a word not recognized by the spelling checker and close out of the footer.

6. On the tool bar, choose the Zoom Whole Page button.

7. From the Tools menu, choose Spelling.

8. Choose the Ignore button each time the Spelling dialog box appears.

Result: After you choose the Ignore button for the unrecognized word in the footer, the program causes a GP fault or your system hangs. You must restart (reboot) your computer if your computer hangs.

Note: This problem usually occurs when you run the spelling checker, as described above. However, the problem also occurs when you do the following:

1. Repeat steps 1-6 above.

2. From the View menu, choose Normal.

3. From the View menu, choose Header/Footer. Select Header or Footer, and choose the OK button.

4. From the View menu, choose Page Layout.


Not Enough Memory to Run 1-2-3 for Windows
Problem:  "Not Enough Memory to Run 123 for Windows"

When attempting to start 123 for Windows, Windows displays the error message: "Not Enough Memory to Run 123 for Windows."  Microsoft Windows 3.0 is running in standard mode.

Solution:

If Windows is being run in standard mode, before 123 for Windows loads, it performs a memory check to verify that a minimum of 1300K of RAM is available.  If less than 1300K is available, then the error message above results.

123/W performs the memory check because approximately it requires 1300K for the program to load completely, and because in standard mode, Windows is not able to use swap files to free up memory when additional RAM is needed.  To verify the amount of available memory, select Help, About Program Manager from the Windows Program Manager.

Typically, on a 2 megabyte (MB) machine the "Not Enough Memory to Run 123 for Windows"  message results .  On a 2 MB 286 machine, with no memory resident programs running, no extraneous device drivers loaded, no other applications running under Windows, and the Adobe Type Manager installed and running, there should be slightly more than 1300K of memory available in Windows.  If less than 1300K is available, memory may be blocked, or reserved by the machine, or the full 2 MB may not truly be available on the machine.

Although this is not recommended, it is possible to alter the minimum amount of RAM for which 123/W checks at startup.  The environment variable 123WSTDMEM controlls the amount of RAM .  For example, entering the following statement:

SET 123WSTDMEM=1200

at the DOS prompt prior to loading Windows, or placing this statement in the AUTOEXEC.BAT file, will cause 123/W to check for only 1200K when it is loaded in standard mode.  This procedure can be used if it is not possible to get 1300K available under Windows due to hardware or environment limitations.

Modifying this setting is not a recommended configuration for running 123/W; it is provided as an interim solution for running the program while additional memory is being purchased for the machine.

NOTE:  This memory check does not take place when Windows is being run in 386 enhanced mode, since this mode provides virtual memory via swapping.


Graph Does Not Print Properly to a Plotter
Problem:  Graph Does Not Print Properly to a Plotter

When printing from either 123 for Windows 1.0 (123W) or Freelance for Windows 1.0 (FLW) to a plotter, the graph does not print properly.  Miscellaneous characters or part of the graph print.

Solution:

This problem occurred in one case when printing to a Hewlett Packard (HP) 7475A plotter from Windows; and the COM port settings in Windows were configured to None.

To print the entire graph without error, verify the baud rate setting and configure the COM port for the Hardware setting in the Windows Control Panel. To do this, follow the steps below:

1. Select the Windows Control Panel from the Main Window in the Windows Program Manager.

2. Select Ports and specify the appropriate COM port (serial port).

3. Select Settings.

4. Select Hardware under Flow Control.

5. Ensure the baud rate setting in Windows matches the baud rate setting on the plotter.

Now the plotter should be able to plot the entire graph without error.

NOTE: The default Flow control setting in Windows Port Settings is none, not hardware. It is not always necessary to change this setting.  Try to only change the flow control setting if experiencing the problem noted above.


Using Internal Scaleable Fonts on a HP LaserJet III
Problem:  Using Internal Scaleable Fonts On An HP LaserJet III

Is it possible to access the internal scaleable fonts, CG Times and Univers, on the HP LaserJet Series III, with 123 for Windows (123W)?

Solution:

The original HP Laserjet III printer driver that shipped with Microsoft Windows 3.0 does not enable this capability.  However, there is an updated printer driver on the 123 for Windows Printer Driver Disk that will access the scaleable fonts.

Once the driver (using the Windows Control Panel) is installed, and the. HP LaserJet III is selected under File Printer Setup in 123W, CG Times and Univers will appear in ALT Style Font Replace.


Memory Setting Not Holding for HP LaserJet III
Problem:  Memory Setting Not Holding For The HP LaserJet III

After installing the HPPCL5A printer driver for the HP LaserJet III, which ships with 123 for Windows, the memory configuration is changed from 1 MB to 2 MB under the File Printer Setup menu in 123 for Windows. When Setup is viewed again, the memory configuration has reverted back to 1 MB.

To reproduce this follow the steps below:

1.    Select File Printer Setup.

2.    Highlight the HP LaserJet III and select Setup.

3.    Change the memory to 2 MB.

4.    Select OK twice.

If the steps 1 and 2 are repeated to view the changes,  the memory has been changed back to 1 MB.

Solution:

In order for the memory change to be permanent, the memory from the Window's Control Panel must be changed.

To do this follow the steps below:

1.    Select the Control Panel from the Windows Program Manager.

2.    Select Printers.

3.    Highlight the HP LaserJet III and select Configure.

4.    Select Setup and change the memory configuration.

5.    Set Page Protection to ON (This is to avoid any memory errors that may occur).

6.    Select OK 3 times.


Cannot Reset HP LaserJet III Graphic Resolution
Problem:  Cannot Reset HP LaserJet III Graphic Resolution

After installing the Windows Driver for the HP LaserJet III, which ships with Windows 3.0,  the graphics resolution is changed from 75 dots per inch (dpi) to 300 dpi from the File Printer Setup menu in 123 for Windows.  When viewing Setup again, the graphics resolution has reverted back to 75 dpi.

To reproduce this follow the steps below:

1.    Select File Printer Setup.

2.    Highlight the HP LaserJet III and select Setup.

3.    Change the graphic resolution to 300 dots per inch.

4.    Select OK twice.

If the steps 1 and 2 are repeated to view the changes,  the graphics resolution has been changed back to 75 dots per inch.

Solution:

This is a problem with Windows HP LaserJet III printer driver.  Install the HP LaserJet III driver  (HPPCL5.DRV version 3.77) that ships with 123 for Windows. The driver is located on the Printer Drivers Disk and  instructions for installing the driver are in the HPREADME.TXT file on the disk.  Once the new driver is installed, exit Windows and then restart.


Minimum Requirements for 123 for Windows 1.0 and 1.0a
Problem:   Minimum Memory Requirements for 123 for Windows 1.0 and 1.0a

The program requires a minimum of  2 MB of memory to run.  This is a minimum requirement; there are other considerations, which vary depending on the particular machine and the mode in which Windows is being run.  To determine the Windows mode select Help, About Program Manager, in the Windows Program Manager.

There are no memory issues regarding running 123 for Windows on a 386 machine with 2 MB in 386 enhanced mode.  In 386 enhanced mode, Windows will swap information to disk to access memory when needed.  This will impact the speed of 123 for Windows; however, this limitation is common to all Windows applications when swap files are used.

Additional memory will improve performance.  123 for Windows requires at least a 1.5 megabyte permanent swap file; this swap file size assumes no other applications are being run concurrently.  For more information on swap files and instructions for creating a permanent swap file, refer to the Microsoft Windows User's Guide, pages 520-529.

386 Machines with 2 MB in Standard Mode:

It is not possible to run 123 for Windows on a 386 machine with 2 MB in standard mode; 2.5 MB of RAM is required.  The additional memory is necessary because 386 machines use more memory for overhead, consequently, that memory is not available for applications.

NOTE:  In standard mode, Windows is not able to use swap files to free up memory when additional RAM is needed.

Some 2 MB 386 machines cannot run Windows in 386 enhanced mode.  This could be due to memory being reserved by the machine (shadow RAM) or by device drivers and TSR's, or due to a hardware incompatibility.

For assistance running Windows in 386 enhanced mode, call Microsoft Customer Support at 206-637-7098 or contact the hardware manufacturer with questions concerning BIOS incompatibilities.

286 Machines with 2 MB in Standard Mode:

Running 123 for Windows on a 286 machine requires that it be run in Standard Mode, therefore no swap files can be used. 123 for Windows will run on a 286 machine with 2 MB of RAM, with the following limitations:

1. The system configuration of the computer must not contain any extra memory resident programs.  There should be no memory blocking device drivers such as SMARTDRV listed in CONFIG.SYS.  The LOAD= and RUN= lines in the WIN.INI file should not be autoloading any software, and there should be no memory intensive bitmap displayed as wallpaper in Windows.  In addition there must be enough free disk space (approximately 3 MB) for Windows to write application temporary files.

A sample AUTOEXEC.BAT file follows:

PROMPT $P$G

PATH=C:\DOS;C:\WINDOWS;

SET TEMP=C:\WINDOWS\TEMP

A sample CONFIG.SYS file follows:

FILES=60

BUFFERS=20

SHELL=C:\DOS\COMMAND.COM /P /E:2048

DEVICE=C:\HIMEM.SYS

   With the configuration above on a 2 MB 286 machine, the amount of free memory under Windows (to check memory status, select Help, About Program Manager in the Program Manager), should be at least 1300K.  123 for Windows verifies that a minimum of 1300K of memory is available before it loads.  If less than 1300K is available, attempting to start 123/W generates the error "Not Enough Memory to Run 123 for Windows."  For more information on this error message, refer to the tech note titled "Not Enough Memory to Run 123 for Windows".

2. The Adobe Type Manager that is included with 123 for Windows must be installed and running.

3. A message box will appear when 123 is loaded indicating that memory is full.  This box appears during any 123 session when memory is extremely low. It is possible to select "OK" when the box appears and continue working. Moderately sized files, in some cases as large as 500K, can be loaded with this configuration.

4. 123 for Windows will run very slowly. It may take several seconds, depending on the CPU and display speeds of the machine, for keystrokes to be reflected on the screen.  Lotus strongly recommends at least 3 MB of RAM for optimal performance.

There are some machines that reserve memory for system use, such as shadow RAM.  Therefore, the entire 2 MB will not be available for program use.  It may be necessary to add additional memory to load 123 for Windows.

Windows applications in general, and specifically 123 for Windows, will have improved performance when additional memory is installed.


Monochrome Display with 123W Multimedia SmartHelp
Problem:  Monochrome Display With 123W Multimedia SmartHelp

Can 123 for Windows 1.1 (123W 1.1) with Multimedia SmartHelp run on a VGA monochrome monitor?

Solution:

123 for Windows with Multimedia SmartHelp was not designed to run on a monochrome monitor.  The product can be installed on a monochrome monitor without any error message, however the display is extremely poor.

For best results install 123W with Multimedia SmartHelp on a computer that uses a VGA Color monitor or higher.


System Requirements for 123 Release 4 for Windows
Problem:  System Requirements For 123 Release 4 for Windows

The system requirements of 123W 4.0 are as follows:

I.    HARDWARE:

1.    A 286, 386, 486 or higher based computer certified for use with Microsoft Windows 3.0 or later.

2.    EGA, VGA, IBM 8514, or higher resolution graphics adapter

3.    Mouse (recommended)

II.    SOFTWARE:

1.    Microsoft Windows 3.0 or later

2.    DOS 3.11 or later

III. MEMORY AND DISK SPACE:

1.    Minimum of 3 Megabytes (MB) of RAM for Windows 3.0.

2.    Minimum of 4 MB of RAM for Windows 3.1.

3.    If using a computer with a 286 processor may require additional memory for ease of use.

4.    7 MB or more of available disk space.


123W Release 4 Plotter Support and Related Printing Issues
Problem:  123W 4.0 Plotter Support And Related Printing Issues

Has Lotus Development Corporation tested and certified plotters as compatible with 123 Release 4 for Windows (123W 4.0)?

Solution:

Lotus has not officially tested or certified plotters as compatible with 123W 4.0.  If printing to a plotter from 123W 4.0 one of the following issues may occur:

No background colors print.

No fill patterns on cells or draw layer objects print.

Y Axis titles on charts print horizontal.

NOTE:  Other print issues not listed above also may exist.


"Initialization Error" Printing from Freelance for Windows 1.0
Problem:  "Initialization Error" Printing from Freelance for Windows 1.0

The error message "The print command cannot be completed because of an initialization error" occurs while doing one of the following:

Situation A: Attempting to print or tries to access the Printer Setup menus while in a Lotus Windows application.

Situation B: Executing the QuickStart tutorial in Freelance for Windows (FLW).

Solution:

There are 4 known reasons why this error message can occur:

1. The ATM font cache is set incorrectly.  The steps to changing the ATM font cache are as follows:

a. From the Program Manager in Windows, start the ATM Control Panel.

b. Select the Up arrow key under Font Cache to change the font cache.  Adobe recommends 96 Kilobytes (96k) for every 1 megabyte of extended memory on the computer.

c. Select Exit to close the ATM Control Panel.

d. Close any other applications in memory and Select File Exit Windows.

e. Restart Windows.

2. The image is too complex for the Windows direct printing.  In Microsoft Windows 3.0, change the port specification to LPT1.OS2 by doing the following:

a. From the Main Group in the Program Manager, select Control Panel.

b. Select Printers.

c. In the Installed Printers box, highlight the printer driver being used and

select Configure.

d. Select LPT1.OS2 from the list of ports and select OK twice.

e. Click on Settings Exit to close the Control Panel.

In Microsoft Windows 3.1, change the port specification to LPT1.OS2, by doing the following:

a. From the Main Group in the Program Manager, select Control Panel.

b. Select Printers.

c. In the Installed Printers box, highlight the printer driver being used and select Connect.

d. Select LPT1.OS2 from the list of ports, select OK and select Close.

e. Click on Settings Exit to close the Control Panel.

3. A printer driver has not been installed in the Windows Control Panel.

4. A printer driver has been installed but is damaged.

5.  There is no default printer chosen in the Control Panel.

Refer to pages 158-160 of the Microsoft Windows 3.0 User's Guide or pages 200-203 of the Microsoft Windows 3.1 User's Guide for instructions on installing a printer driver in the Windows Control Panel.

Explanation:

The "Initialization Error" as well as a "Br Tape Backup" error message can occur while running the FLW tutorial.  Clicking "Begin Demonstration" actually runs the FLW program.  Because FLW was loaded and no printer drivers were installed, an error message box popped up which said "The printer command cannot be completed because of an initialization error". Because the tutorial is running, control of the mouse to click on OK to end the display of the message box is not present.  The presence of this message box disrupts the running of the tutorial and a BR Tape Backup error will appear soon after.

The solution in this case is to install any Windows printer driver before running the tutorial.


FLW Prints Black & White Only
Problem:  FLW Prints Black & White Only for HP DeskJet 500C

Attempting to print a presentation in color from Freelance for Windows 1.0 (FLW 1.0) or Freelance for Windows 2.X (FLW 2.X) to an HP DeskJet 500C printer.  The "Adjust Color Library for Color Printing" choice is grayed out.  Also, when attempting to change the color of an object (by selecting Style Attributes or Text Color, and clicking on the down-arrow next to "Color" to display the palette), the palette shows shades of gray instead colors.

Solution:

When the HP DeskJet 500C driver is installed in the Microsoft Windows Control Panel, the print mode defaults to "Black Only".  The printer will print only in shades of gray with this print mode.  The print mode can be changed so that the printer will print in color.  While in FLW, select File Printer Setup Setup, select "Color/Composite Black" for the print mode, and select OK twice.  The palettes will now display colors and the printer will print in color.


Some Printer Fonts aren't listed in FLW
Problem:  Some Printer Fonts Aren't Listed in FLW

When selecting Text Face in Freelance Graphics for Windows  1.0, the program does not list any internal printer fonts.

Solution:

This issue only occurs when  certain printer drivers are selected in the Microsoft Windows Control Panel. For example, if the Canon LBP-8, the Canon LBP-4, or the Epson FX-850 printers are selected, no internal printer fonts are listed in the Text Face menu.

There is no workaround at this time.


"Unrecoverable Application Error" When Saving a File
Problem:  "Unrecoverable Application Error" When Saving a File

Attempting to save an Untitled to disk with File, Save or File, Save As in Ami Pro results in the error "Unrecoverable Application Error" (UAE).

Solution:

Using the Hercules Graphics Station Card (TIGA) display adapter with Windows 3.X and certain versions of the Windows display driver supplied by Hercules may result in an Unrecoverable Application Error (UAE) when attempting to Save Untitled in Ami Pro.  A temporary workaround to this problem is accomplished by installing the standard VGA display driver supplied by Microsoft for Windows 3.X.  This driver will allow files to be created by the Ami Pro File / Save or File / Save As functions. Lotus WPD has not officially tested and certified the Hercules Graphics Station Card as compatible with Ami Pro.  Contact Hercules Technical Support, 921 Parker Street, Berkeley, CA 94710, 415-540-6000, and request an updated Windows display driver. Hercules Technical Support indicates that the most current version of the driver (1.20 as of April 3, 1991) will resolve the UAE errors with Ami Pro.


"Error: Printer Busy" Occurs While Printing in Ami Pro
Problem:  "ERROR:Printer Busy" Occurs While Printing

During the process of printing in Ami Pro v2.0, the message "ERROR:Printer Busy" appears.  After OK is chosen, the message "Cannot find a printer driver.  Formatting for the screen" appears.

Solution:

The above error may occur when Ami Pro's background printing and flow in background options are enabled while printing to the PowerPak version 1.2 printer driver.  Disabling these Ami Pro options generally eliminates the error.

To disable the Print in Background and Flow in Background options:

1. Load Ami Pro.

2. Choose Tools / User Setup.

3. Choose Options.

4. Remove the X from the Speed Option, Print in background.

5. Remove the X from the Speed Option, Flow in background.

6. Choose OK.

7. Choose OK.

8. Reprint the Ami Pro document to the PowerPak driver.


Printing Files with Graphics Results in a UAE
Problem:  Printing Files With Graphics in Ami Pro 2.0 Results in a UAE

An Unrecoverable Application Error (UAE) termination occurs at some point while printing files containing graphics in Ami Pro v2.0.

Solution:

On rare occasions, an Unrecoverable Application Error (UAE) may occur while printing a file containing one or more graphic images.  There are two possible resolutions.  The first involves deselecting Ami Pro's background printing option (AmiPrint), the second involves removing and reinstalling the printer driver being used.

To turn off Ami Pro 2.0's  Print in Background (AmiPrint) option:

1. Load Ami Pro.

2. Choose Tools / User Setup.

3. Choose Options.

4. Remove the X from the Print in background Speed option.

5. Choose OK.

6. Choose OK.

7. Reprint the file containing the graphic images.

If the UAE still occurs during the process of printing, it may be necessary to remove the printer driver being used and reinstall the driver.

To remove and reiinstall the printer driver being used:

1.  Locate the program disks that were used to install the Windows 3.X program being used.

2.  Exit Ami Pro to the Windows Program Manager.

3.  Run the Windows Control Panel (there is usually an icon for the Control Panel in one of the Program Manager groups).

4.  Choose the Printers option in the Control Panel by selecting the Printers icon.

5.  Under Installed Printers, select the name of the printer being used.

6.  Choose Configure.

7.  Choose Remove.

8.  Choose Yes to confirm removing the printer.

9.  Choose OK.

10.  Close the Control Panel by pressing ALT + F4.

11.  Run the Windows File Manager (there is usually an icon for the File Manager in one of the Program Manager groups).

12.  In the File Manager, access the SYSTEM directory beneath the directory where the Windows program files are located (usually C:\WINDOWS\SYSTEM).

13.  Select the file name of the printer driver that was deleted from the Control Panel in Step 5 and any associated Help file.  NOTE: If the file name of the printer driver file is not known, view the Windows WIN.INI file by running the Windows file SYSEDIT.EXE (normally located in the Windows SYSTEM directory).  This program is a utility for viewing and editing certain Windows and system files.  The names of all Windows printer drivers can be found under the DEVICES section of the WIN.INI file.  An example of this section might look like:

[Devices]

PostScript Printer=PSCRIPT,LPT2:

Canon LBP III=LBP83137,LPT1:

HP LaserJet III=HPPCL5A,COM1:

In this example, the name of the PostScript printer driver is PSCRIPT, the Canon LBP III printer driver name is LBP83137, and the name of the HP LaserJet III printer driver is HPPCL5A.  The actual DOS file name for each printer driver has an extension of .DRV.  For example, the file name for the HP LaserJet III printer drive is HPPCL5A.DRV.  Associated Help files will generally have the same name as the printer driver with an extension of .HLP.  The HP LaserJet III printer driver help file, for example, is named HPPCL5A.HLP.

14.  In the File Manager, choose File, Delete to delete the printer driver file and any associated Help file.

15.  Choose Delete to delete the selected files.  If the File Manager presents another prompt to verify deletion of the files, choose Yes.

16.  Exit the File Manager by pressing ALT + F4, then choose OK.

17.  Run the Control Panel.

18.  Choose the Printers icon.

19.  Choose Add Printer.

20.  Select the name of the printer to install in the List of Printers list box.

21.  Choose Install.

22.  Insert the Windows program disk containing the printer driver into a floppy drive and specify the appropriate drive letter in the Control Panel - Printers dialog box.

23.  Choose OK.

24.  Choose Configure.

25.  Select the desired port name under Ports.

26.  Choose Setup and make any desired Setup changes.

27.  Choose OK.

28.  Choose OK.

29.  If necessary, change the printer's status from inactive to active.  Note:  If there is another printer connected to the same port which is active, it will become inactive when the newly installed printer is made active.

30.  Choose OK.

31.  Close the Control Panel by pressing ALT + F4.

32.  Reload Ami Pro and attempt to print the file containing graphic images again in Ami Pro.

Modified Ami Pro files are available which will address most (if not all) cases where printing files with graphics results in a UAE if Ami Pro's background printing option is enabled.  Contact Lotus Word Processing Division Customer Service at 404-399-5505 and request the modified Ami Pro files that allow printing graphics with the AmiPrint print in background option enabled.

Using these modified files, however, won't guarantee compatibility with all graphics files (even with supported graphic types, there is sometimes unusual formatting).  If you are still not able to print graphics after obtaining the modified program files, contact Lotus WPD technical support at 404-399-5505.


"Unable to Print" Message using Generic Text Driver
Problem:  "Unable to print..." Message Using Generic Text Driver in AmiPro v3.0

The messages "Unable to print this document.  Install the correct printer driver and try again"and  "Cannot find printer driver.  Formatting for the screen" appear when attempting to print in Ami Pro v3.0 using the Windows 3.1 Generic Text printer driver.

Solution:

Ami Pro 3.0 displays the above messages during printing with the Windows 3.1 Generic Text printer driver.  Other Windows applications (including Windows Write and Notepad) issue other messages and cannot print using the Generic Text printer driver.  Disabling Adobe Type Manager will allow you to use the Generic Text printer driver.

To disable Adobe Type Manager:

1. Since you will have to exit Windows to actually disable Adobe Type Manager, complete any necessary work in open applications.

2. In the Windows Program Manager, run the ATM Control Panel (ATMCNTRL.EXE).

3. Select Off under ATM.

4. Choose Exit.

5. Choose Restart Windows if you have completed all current work in applications running in Windows.  Choose Return to current Windows session if you need to continue using Windows.  Note: ATM will not be disabled until you exit and restart Windows.

6. When Windows exits and restarts, ATM will be disabled.


GPF Merging with 123 Release 4 File in AmiPro v3.01
Problem:  General Protection Fault Merging with 123 R4 File in AmiPro v3.01

A Windows General Protection Fault occurs when attempting to insert merge fields from the data file into the standard document or when printing the merge in Ami Pro release 3.01 using  the 123 Release 3 and 4 filter.

Solution:

A temporary solution to this problem is to create an Ami Pro description file to be used with the 123 Release 4 file during merge.

To create a Merge Description File:

1.  In 123, select the first row of the spreadsheet file that will be used in the Ami Pro merge (this row should contain the field names for the merge).

2.  In Ami Pro choose File / New and select the _DEFAULT.STY style sheet.

3.  Choose Edit / Paste to paste the 123 field names from the first row into Ami Pro.

4.  Insert carriage returns (press ENTER) after each field name so that each appears on a separate line.

5.  Press CTRL + HOME to place the insertion point at the beginning of the document.

6.  Insert a new line before the first field name and type on this line:

1-2-3 rel 3 & 4

7.  The text in the document should now look similar to:

1-2-3 rel 3 & 4

fieldname1

fieldname2

fieldname3

..

8.  Choose File / Save and supply a name for the description file.

9.  At step 1 "Select, create or edit a data file" choose "Field names listed in" and specify the name of the description file created in step 8. You are now able to insert the merge fields and print the merge without errors.


"Error 106: " Message Appears Using ~CALMON.STY
Problem:  "Error 106:  " Message Appears Using ~CALMON.STY

Using the ~CALMON.STY style sheet, a message "Error 106: Incorrect parameter used for this function" displays.

 SOLUTION:

An Error 106 message displays when using the ~CALMON.STY monthly calendar style sheet if the Windows separator character in the Control Panel International date settings has been changed to a character other than a forward slash (/).  Changing the date separator back to a forward slash will eliminate the Error 106 message.

To change the date separator character to a forward slash:

1. Run the Windows Control Panel.

2. Select International.

3. Choose CHANGE under "Date Format".

4. Under "Short Date Format" type / for the separator.

5. Choose OK.

6. Choose OK.

7. Press ALT + F4 to close the Control Panel.


AUTOSTY.SMM Macro Does Not Run
Problem:  AUTOSTY.SMM Macro Does Not Run

Style sheets created from automated style sheets which use AUTOSTY.SMM (such as _FAX1.STY), lose the automated feature.

Solution:

Automated style sheets contain power fields that are replaced with text if the "Run macro" option is selected when the style sheet is opened then saved under a new name.  By deselecting the "Run macro" option when opening the style sheet, the power fields are not overwritten and can be saved in a new style sheet.

To Edit and save an automated style sheet under a new name:

1. Load Ami Pro 3.0.

2. Choose File / New.

3. Select an original automated style sheet installed with Ami Pro 3.0.

4. Deselect the "Run macro" option.  There should not be an X in the option box.

5. Choose OK.

6. Make the necessary changes to the style sheet.

7. Choose Style / Save as a Style Sheet.

8. Type a new style sheet name in the "File name" edit box.

9. Select with an X the "With contents" option.

10. Select with an X the "Run macro" option.  Make sure AUTOSTY.SMM is the file name in the edit box to the right of "Run macro".

11. Choose OK.

12. Choose File / New.

13. Select the style sheet name used in Step 8.

14. The "Run macro" and "With contents" options should be selected with an X.

15. Choose OK.

16. The style sheet will open and the AUTOSTY.SMM macro will run.


GPF when Saving a File
Problem: Saving a File May Cause a General Protection Fault

If a file is saved by typing, for example, A:FILENAME and the FILENAME has seven or more characters, a General Protection Fault (in Microsoft Windows 3.1) or Unrecoverable Application Error (in Windows 3.0) may occur.

Solution:

The above errors can be prevented by one of the following:

1) Choose the drive letter in the "Drives" list box instead of typing it as part of the filename, or

2) use a backslash (\) after the drive letter when typing out the filename (for example, C:\FILENAME).


Unable to Print Multiple Copies
Problem:  Unable To Print Multiple Copies

Printing multiple copies of a file to some dot matrix printers and to some HP DeskJet printers only prints one copy in AmiPro v3.0.

Solution:

An Ami Pro 3.01 update is available which will correct this problem.  Using the 3.01 update, multiple copies will print using most printers and Windows printer drivers.  Note: The HP DeskJet color driver version 3.0 from Hewlett Packard will print only one copy unless the Ami Pro print in background feature is enabled, however, the DeskJet version 1.1 printer driver shipped with Windows 3.1 does print multiple copies.  There may be other Windows printer drivers which still require enabling the print in background feature.

The Ami Pro 3.01 update is available electronically from the [Ami Pro - Technotes] library on the LotusWPD CompuServe forum.  Download the files AP3011.EXE, AP3012.EXE, AP3013.EXE, and DOC301.EXE.  The 3.01 update is also available on disk from the Lotus WPD Customer Service Department at 404-399-5505.

A workround is to select the "Print in background" option under Tools / User Setup / Options to print multiple copies to some dot matrix printers (for example Citizen GSX-140, Citizen GSX- 140 Plus, Epson LQ-850, Panasonic KXP-1624) and some HP DeskJets.

How to enable printing in the background

1. Load Ami Pro 3.0.

2. Choose Tools / User Setup / Options.

3. Select with an X the "Print in background" option.

4. Choose OK.

5. Choose OK.

6. Printing multiples will now work properly.


Error Running Grammer Checker
Problem:  Error Running Grammar Checker

"Cannot load the Grammar Checker" message appears when attempting to run the Grammar Checker.

Solution:

This occurs because the Spelling Language Option has been set to British instead of American.  The Grammar Checker is available for the American language option only.  Changing the language option to American will correct the problem.  A second solution is to copy the file, LOTUSAM1.GCS located in the AmiPro program directory, to LOTUSBR1.GCS.  This makes it unnecessary to change the language option to American before running the Grammar Checker, but it may not flag some grammatical errors due to differences in British and American rules of grammar.

If the British language option is to be used for all documents it is possible to delete the LOTUSAM1.GCS file from the AmiPro program directory to conserve disk space.

To change the language option, do the following:

1.  With the document to be Grammar Checked on the screen, choose Tools / Spell Check.

2.  Choose Language Options.

3.  Choose American from the "Language for current document" list box to change to the American language for the current document.  If you want to permanently switch back to the American language, choose American from the "Default language for new document" list box.

4.  Choose OK.

5.  Choose Cancel or OK to Spell Check before running the Grammar Checker.

NOTE:  Any documents that were spell checked with British as the "Language for current document" will use the British spelling dictionary with subsequent spell checks.  To change those documents to the American language dictionary, repeat steps 1-5 above and select American from the "Language for current document" list box.


Error Message When Running The Tutorial
Problem:  Error Message When Running The Tutorial

While the Tutorial is running, the error message "Cannot Find Specified File..X6" displays.

Solution:

To eliminate this error message, the Ami Pro program file AMIVISD.INI should be deleted from the Windows directory.  AMIVISD.INI will automatically be recreated in the Windows directory when Ami Pro is started again.

To delete AMIVISD.INI from the Windows Directory:

1.  Exit Ami Pro if it is loaded.

2.  Start Windows File Manager.

3.  Choose File / Delete.

4.  Type C:\WINDOWS\AMIVISD.INI in the Delete edit box.  If your path to Windows is different, type the correct path.

5.  Choose OK.

6.  Start Ami Pro.  A new AMIVISD.INI will automatically be created.  Run the Tutorial. The error message should not display.


Print Prints a Document Other than the Active Document
Problem:  File / Print Prints a Document Other Than the Active Document

When File / Print is selected, a file will print, however it is not the activefile.

Solution:

The active file has been set up as a Master Document.  The file or files that print when File / Print is selected are files that were included in the Master Document.  (A Master Document is typically used to link separate files that will be printed together.  For example, one might create a Master Document which has no text but "includes" a file for each separate chapter in a book.)  If a file is inadvertently set up to be a Master Document, when File / Print is used, the Master Document closes and files included in the Master Document open and print.  The last file which was included in the master document is left open on the screen.  To eliminate this, the file should not be set up as a Master Document.  By removing all files that have been included in the Master Document, the document is no longer a Master Document and prints properly when File / Print is selected.  Follow the steps given below to change the status of the file from Master Document to an independent file.

To remove included files to change a master document to an independent file:

1.  Start Ami Pro if necessary.

2.  Choose File / Open.

3.  From the "Files" list box, choose the file which has been unintentionally set as a Master Document.

4.  Choose OK.

5.  Choose File / Master Document.

6.  The "Master doc files:" list box will have one or more file names which have been included" in the active file.  Select the first file in the list.

7.  Choose Remove.

8.  Repeat steps 6 and 7 for each file that is listed in the "Master docfiles:" list box until this list box contains no file names.

9.  Choose OK.

10.  Choose File / Save.

The active file is no longer a Master Document.  When File / Print is selected, the active file prints.


General Protection Fault when Using AmiPro Help
Problem:  General Protection Fault when Using Ami Pro Help

A Windows utility program called FREEMEM.EXE is known to cause General Protection Fault messages in GDI.EXE when using Ami Pro Help.

Solution:

If General Protection Faults occur frequently in conjunction with using Ami Pro Help, check the Windows Startup group and the Load= and Run= lines in the WIN.INI Files for the presence of a utility called FREEMEM.EXE.

Remove the icon for FREEMEM.EXE from the Windows Startup group.  Use Windows Notepad or some other text editor to open the WIN.INI file which is located in the Windows directory and delete any reference to FREEMEM.EXE from the Load=and Run= lines.


GPF when running Spell Check
Problem:  Lockup or General Protection Fault Running Spell Check

A lockup or General Protection Fault in AMIPROUI.DLL occurs when Spell Check is in progress.

SOLUTION:

A User Dictionary file is stored in alphabetical order.  If the User Dictionary file is incorrectly sorted a lockup or General Protection Fault may occur when Spell Check is run.  To resolve the problem, re-sort the User Dictionary following the steps below.

First follow the steps for editing the User Dictionary where the User Dictionary file is sorted and re-saved.

To edit the User Dictionary

1.  Start Ami Pro 3.0.

2.  Choose Tools / Spell Check.

3.  Choose Edit Dictionary.

4.  With the insertion point at the upper left-hand corner of the file, hold down the Shift key and the Down Arrow until all the words in the file are selected (shaded).

5.  Choose Tools / Sort.

6.  If needed, type 1 in the Field Level 1 edit box.

7.  Select Alphanumeric under Type.

8.  Select 1st under Word.

9.  Choose OK.

10.  Choose File / Save.

11.  Choose File / Open.

12.  Select the file you want to Spell Check.

13.  Choose OK.

14.  Choose Tools / Spell Check.

15.  Choose OK. You should not lockup or get a GPF.

If the steps above do not resolve the problem, follow these steps to resave the User Dictionary:

1.  Start Ami Pro 3.0.

2.  Choose File / Open.

3.  Choose ASCII from the "List files of type" selection box.

4.  In the File name edit box, type the path to your Ami Pro program files and type LTSUSER1.DIC, for example, type C:\AMIPRO\LTSUSER1.DIC.  (Your drive and directory name might be different.)  LTSUSER1.DIC is the name of the user dictionary file.

5.  Choose OK.

6.  Choose File / Save As.

7.  Choose ASCII Options.

8.  Select CR/LF at paragraph ends only.

9.  Choose OK.

10.  Choose OK.

11.  Choose YES to overwrite LTSUSER1.DIC.

12.  Choose File / Open.

13.  Select the file you want to Spell Check.

14.  Choose OK.

15.  Choose Tools / Spell Check.

16.  Choose OK.  You should not lockup or get a GPF.

If the steps for Editing the User Dictionary and Resaving the User Dictionary do not resolve the problem, follow the steps for Renaming the User Dictionary.   The steps in Renaming the User Dictionary are valid only if you had an earlier version of Ami Pro.

Note:  The User Dictionary in Ami Pro versions prior to 3.0 was named VEAMAB51.LEX.  The User Dictionary file name in Ami Pro 3.0 is LTSUSER1.DIC.  When using the Ami Pro 3.0 Spell Check, if VEAMAB51.LEX exists in the Ami Pro program directory, it is copied to LTSUSER1.DIC, providing LTSUSER1.DIC does not already exist.  A lockup may occur during the Ami Pro 3.0 Spell Check when the renamed VEAMAB51.LEX User Dictionary file is corrupted. Renaming the VEAMAB51.LEX and LTSUSER1.DIC files will cause a new LTSUSER1.DIC file to be created when Spell Check is run.

To rename the User dictionary:

1.  Start Windows File Manager.

2.  Display the directory where your Ami Pro program files are located.   (Usually, this is C:\AMIPRO, however, your directory may be different.)

3.  Select the file VEAMAB51.LEX from File Manager.

4.  Choose File / Rename.

5.  Type VEAMAB51.OLD in the edit box where the insertion point is located.

6.  Choose OK.

7.  Select the file LTSUSER1.DIC from File Manager.

8.  Type LTSUSER1.OLD in the edit box where the insertion point is located.

9.  Choose OK.

10.  Choose File / Exit to close File Manager.

11.  Start Ami Pro 3.0.

12.  Choose File / Open.

13.  Select the file you want to Spell Check.

14.  Choose OK.

15.  Choose Tools / Spell Check.

16.  Choose OK.

17.  Ami Pro will create a new LTSUSER1.DIC file.  You should not lockup or get a GPF.


AmiPro Shortcut Keys do not work
Problem:  Ami Pro Shortcut Keys Do Not Work

When using shortcut keys in Ami Pro 3.0, the shortcut keys do not seem to work.

Solution:

A setting in the Keyboard section under the Windows Control Panel may be causing the problem.  If the "Delay Before First Repeat" option is set to Short, and the shortcut keys are depressed too long, the key sequence will be replayed.  For example, CTRL + E is pressed to Center text.  If the keys remain depressed, CTRL + E (center) is then turned off.

Set the "Delay Before First Repeat" to a longer setting by moving the scroll box to the left about mid-way.  See your Microsoft Windows User's Guide for specific instructions.


"Unable to Locate Compressed File" Message Installing Node
Problem:  "Unable to Locate Compressed File" Message Installing Node

During installation of the Node program, the message "Unable to locate compressed file F:\AMIPRO\NODE\31LINFNT.CMZ" appears.  The node installation terminates after choosing OK to the message.

Solution:

The above problem occurs running the Node program when Ami Pro release 3.01 has been installed from 3.5" media.  The problem does not occur if Ami Pro has been installed from 5.25" media.

There are four methods by which this problem can be resolved.  Performing either of the first three methods will resolve the problem so that the Node program can be installed.  The fourth method (replacement of three disks) is not necessary, but will provide you with a complete set of 3.5" disks which allow proper node installation.  Perform one of the first three methods to get Ami Pro fully installed, then obtain the replacement disks as instructed in method four for future use in the event that you reinstall Ami Pro on your network.

I.  If you have Ami Pro release 3.01 in 5.25" media and your computer is compatible with that media, reinstall Ami Pro from the 5.25" disks and run the Node program at each computer from which Ami Pro is used.

II.  If you do not have Ami Pro release 3.01 on 5.25" media, and want to run the Node program and use Ami Pro immediately, you can force a Node installation by removing three lines from the SCRIPTN.INS file.  Follow the steps in the section below to remove the lines.  One drawback to using Ami Pro after running Node in this manner is that it excludes use of the Ami Pro LotusLineDraw font which translates line drawing in DisplayWrite files.  DisplayWrite files containing line drawing will not import with the line drawing in Ami Pro.  If you import DisplayWrite files containing line drawing, you should perform method three instead.

To Edit the SCRIPTN.INS File

1. At the Windows Program Manager, start Windows Notepad.  Note:  Another ASCII file editor can be used, however, you should not use an ASCII text editor that converts tabs to spaces (the DOS Edit program should not be used because it converts tabs to spaces).  The SCRIPTN.INS file needs tabs at certain locations.

2. In Notepad choose File / Open.

3. Move to the network drive containing the Ami Pro Node subdirectory (usually drive F, but may be a different drive on your network) by selecting the appropriate drive letter in the "Drives" list box.

4. Change to the Ami Pro Node subdirectory (usually \AMIPRO\NODE, but may be different on your network) by selecting the appropriate subdirectory in the "Directories" list box.

5. In the "File Name" edit box type:

SCRIPTN.INS

6. Choose OK.

7. Choose Search / Find.

8. In the "Find What" edit box type:

31linfnt.cmz

9. Choose Find Next.

10. Choose Cancel.

11. The complete line should read

31linfnt.cmz   <WINDOWS>.

12. Press HOME then the UP ARROW to position the insertion point on the line immediately above.  This line should read DECOMP.

13. Press SHIFT + DOWN ARROW four times to highlight the three lines:

DECOMP

31linfnt.cmz   <WINDOWS>

BUILDFONT

14. Press Delete to remove the three lines.

15. Choose File / Exit.

16. Choose Yes to the prompt asking if changes should be saved.

17. Run the Ami Pro Node program at each computer from which Ami Pro is used.

III.  If you have a modem you can immediately obtain two files (31LINFNT.CMZ and SCRIPT.INS) which will allow you to complete the node installation and provide the LotusLineDraw font.  These files can be obtained electronically from the Lotus WPD bulletin board at 404-395-7707 or from the [Ami Pro - Technotes] library on the LotusWPD CompuServe forum.  Download the file 301NOD.EXE from either location.

To Copy The Files 31LINFNT.CMZ and SCRIPT.INS

1. At the Windows Program Manager load File Manager.

2. At the File Manager access the drive containing the file 301NOD.EXE (this will probably be floppy drive A or B).

3. Execute the file 301NOD.EXE by double clicking the file name or selecting the file name and pressing ENTER.

4. Executing the file 301NOD.EXE initiates the process that extracts the two individual files 31LINFNT.CMZ and SCRIPT.INS.

5. In the File Manager copy the file 31LINFNT.CMZ to the Ami Pro program disk 3.

6. In the File Manager copy the file SCRIPT.INS to the Ami Pro program disk 1.

7. Choose File / Exit to close the File Manager.

8. The administrator of the network should repeat the complete installation of Ami Pro including a Node install.

9. Run the Node installation at each computer from which Ami Pro is used.

IV.  Call the Lotus WPD Support Department at 404-399-5505 and request replacement 3.5" program disks 1, 3, and the Bonus Pack for Ami Pro release 3.01.  Discard your original Ami Pro 3.01 program disks 1, 3, and Bonus Pack and replace them with the new disks.  If you used method two above, it is recommended that you reinstall Ami Pro completely and run the node program from each workstation. You will then have the font file LotusLineDraw.  Otherwise, you do not need to use these disks unless you need to reinstall Ami Pro at a later time.


Close-Up May Cause GPF Error Message During Installation
Problem:  Close-Up May Cause Error Message During Installation

A General Protection Fault may occur during the Ami Pro 3.0 installation if Norton-Lambert Close-Up Remote Communication drivers are installed.

Solution:

Close-Up is a remote communications program that loads its own drivers  for the keyboard, mouse and display into the SYSTEM.INI file.  Disabling these drivers in the SYSTEM.INI file before the Ami Pro installation resolves the problem.  This is accomplished by saving the SYSTEM.INI file under a new name and modifying the current SYSTEM.INI file.  The original SYSTEM.INI file can be enabled once the installation is completed.

To disable the Close-Up Drivers:

1. From the Windows Program Manager, start File Manager.

2. Change to the Windows directory (For example, C:\WINDOWS although your directory name may be different).

3. Place insertion point in the file list on the right side of the window.

4. Press the "S" key until SYSTEM.INI is selected.

5. Choose File / Copy.

6. Type "SYSTEM.XXX" in the "To" edit box and choose OK.

7. Double click on the SYSTEM.INI file.  This will start Windows Notepad and displays the SYSTEM.INI file.

8. Choose Search / Find.

9. Type "CPS Commute" (without the quotes) in the "Find What" edit box.

10. Choose Find Next.

11. Choose Cancel.

The following is an example of Close-Up lines in the SYSTEM.INI file (your driver names may be different and the keyboard driver may not be the first driver found in the search):

;CPS Commute has replaced

;"keyboard.drv=keyboard.drv" with "keyboard.drv=commkbd.drv"

keyboard.drv=commkbd.drv

12. With a semicolon, comment out the line loading the Close-Up driver.  See your Windows User's Guide for instructions on commenting out lines from system files.  Using the example above, place a semicolon in front of the third line so that it reads as

;keyboard.drv=commkbd.drv

13. Insert a new line after the Close-Up driver line (using the above example,  place insertion point at the end of the third line and press Enter).

14. Type the original Windows' driver setting on the new line.  This  information can be obtained from the second line in the example above.  The text reading "keyboard.drv=keyboard.drv" (without quotes) is the original Windows' driver setting.  Your setting may be different.

Example of the Close-Up lines in the SYSTEM.INI file after editing:

;CPS Commute has replaced

;"keyboard.drv=keyboard.drv" with "keyboard.drv=commkbd.drv"

;keyboard.drv=commkbd.drv

keyboard.drv=keyboard.drv

15. Repeat steps 8 - 14 to locate and modify the other Close-Up driver settings (which include keyboard, mouse and display drivers).

16. Choose File / Exit.

17. Choose Yes to save changes.

18. Press ALT + F4 to exit File Manager.

19. Press ALT + F4 to exit Windows.

20. Restart Windows.

21. Choose File / Run.

22. Place the Ami Pro Install Disk 1 in a floppy drive.  Type X:\INSTALL, where X is the identification of your floppy drive.  For example, type A:\INSTALL if you install from floppy drive A.  Complete the Ami Pro installation.

23. Once the Ami Pro installation is completed, the drivers for Close-Up can be enabled by renaming the SYSTEM.XXX file from step 6 to SYSTEM.INI.

24. From the Windows Program Manager, start File Manager.

25. Change to the Windows directory (For example, C:\WINDOWS although your  directory name may be different).

26. Place insertion point in the file list on the right side of the window.

27. Press the "S" key until the insertion point in on SYSTEM.INI.

28. Choose File / Rename.

29. Type "SYSTEM.ZZZ" in the "To" edit box and choose OK.  This is a backup of  the SYSTEM.INI file with the Close-Up drivers disabled.

30. Place insertion point on SYSTEM.XXX.

31. Choose File / Rename.

32. Type "SYSTEM.INI" in the "To" edit box and choose OK.  This is original the SYSTEM.INI file with the Close-Up drivers enabled.

33. Press Alt + F4 to exit File Manager.

34. Press Alt + F4 to exit Windows.

35. Restart Windows.


General Protection Fault When Pasting
Problem:  General Protection Fault When Pasting

The error message "General Protection Fault in XXX.FLT" displays when pasting from another application, where XXX is the name of the Ami Pro filter.

Solution:

This problem has been reported with various packages.  One example is "General Protection Fault in EXCELFLT.FLT" when pasting from the IBM Personal Communications 3270 emulation package.

This problem can be resolved by making a selection from the Edit / Paste Special menu rather than using the Edit / Paste function.

To use Edit / Paste Special:

1. Choose Edit / Paste Special.  The Formats list box automatically displays all the formats in which the data is available.

2. Choose one of the options listed.  Try either "Rich Text Format" or "Text" first.  Below is an explanation of each option.  All options listed below do not display for every application.

Windows Metafile - This format scales well but it does not always retain text formatting.

Windows Bitmap and DIB - These formats provide exact representations of a graphic but they do not scale well.

Rich Text Format - A text format that maintains formatting information and attributes such as bold and center. Rich Text Format pastes slowly but it is complete.

Text - A text format that maintains characters but not attributes.

DDE Link - A format that contains DDE link information.

OLE Link - A format that contains OLE link information.

OLE Embed - A format that contains either an icon, a Windows Metafile, or text as a representation of the original data, and the original data in its native format.

3. Choose OK.  Ami Pro embeds or pastes the data in the format you selected.


"Frame Protocol Error" Printing to Windows Printing System
Problem:  "Frame Protocol Error" Printing to Windows Printing System

A message indicating "Frame Protocol Error" followed by a number appears when printing a gray scale TIFF file using the Microsoft Windows Printing System printer driver version number 1.00.00.107.

Solution:

Using the Microsoft Windows Printing System printer driver version 1.00.00.107 (Windows Printing System is a cartridge with a Windows printer driver printing accelerator for HP LaserJet II and III printers) gray scale TIFF files do not print from Ami Pro release 3.0.  A message indicating a "Frame Protocol Error" followed by a number appears on the screen and a blank frame prints.

An Ami Pro update is available with which gray scale TIFF files print using the Windows Printing System Windows driver.  The update is available electronically from the [Ami Pro - Technotes] library on the LotusWPD CompuServe forum.  Download the files AP3011.EXE, AP3012.EXE, AP3013.EXE, and DOC301.EXE.  The 3.01 update is also available on disk from the Lotus WPD Customer Service Department at 404-399-5505.  There may be a nominal shipping and handling charge when obtaining the update on disk from the Customer Service Department.

As a workaround, use the HP PCL Windows printer driver appropriate for your printer.  The gray scale TIFF files will print with the Windows PCL driver, however, the features of the Windows Printing system will not be utilized.


Error Messages While Printing
Problem:  Error Messages While Printing with AmiPro and Font Packages

The error messages "Error Printer Busy" and "Cannot find a printer driver formatting for the screen" may display when printing an Ami Pro document using Atech FastFonts font package or Publisher's PowerPak printer driver.

Solution:

Disabling the Ami Pro "Print in Background" option has been reported to resolve the problem.  Changing to another driver might resolve the problem, however, the FastFonts font will not be accessible.

To disable print in background:

1. Start Ami Pro.

2. Choose Tools / User Setup.

3. Choose Options.

4. Remove the "X" from the "Print in background" option.

5. Choose OK.

6. Choose OK.

7. Print the file.  The error messages will not display.


Can't Print from Windows Applications
Problem:  Can't Print from Windows Applications

Solution:

Any link in the hardware and software chain may be at fault.  Given that the printer is ready to print, troubleshoot with the steps below:

1.  If printing from DOS doesn't work, then Windows won't be able to print either.  From DOS outside of Windows, type

dir > LPT1:

If the printer doesn't respond, then something is wrong in the connnection between the PC and the printer.  Check the cables or try printing from another port.

2.  Turn off Fast Printing Direct to Port option in Control Panel, Printers.  Fast Printing Direct to Port tells Windows to bypass normal DOS interrrupts and send datato the printer directly.  With this option off, printing will be slow.

3.  Reinstall or replace the printer driver.  The next suspect is a faulty or outdated printer driver.  Confirm this by trying another gerneric printer driver such as the HP LaserJet driver, which is supported by almost all laser printers, or an Epson driver, which is supported by almost all dot matrix printers.  If another printer driver works, delete the old driver and reinstall it or contact the manufacturer for an update.


Print Jobs take too long or parts of the print job are missing.
Problem:  Print jobs take too long or parts of the print job are missing.

Solution:

1) Make certain there is a Set Temp=C:\Windows\Temp or equivalent in the autoexec.bat.

2) Make certain the option for Fast Printing Direct To Port is selected.  This can be found under Control Panel-Printers-Connect

3) Set Options to High Priority under Print Manager

4) Make sure there is enough hard disk space available on the drive where the Set Temp= is set to.


Print out shows a solid block
Problem:  Print out shows a solid block rather than the text that should be printed.

Solution:

This is due to an incompatibility in the HP Driver -- HP DeskJet Series v2.0.  If color capabilities are not needed switch to another printer driver. One that works well is the Windows 3.1 HP DeskJet 500 driver.

If color is required, obtain the upgraded HP Driver. Similar problem reports have been noted with two other programs using the v2.0 driver, MS Project and Crystal Service's Quick Reports. Both problems were solved by the v3.1 upgrade of the HP driver.


Graphic Lines do not print
Problem:  Graphic lines created with the line tool do not print, but appear in preview

Solution:

Update the unidrv.dll which is in the \windows\system subdirectory. The problem appears to be in the unidrv.dll dated 3/10/92.


Printer Drivers

Drivers are a link between applications and your printer.  Drivers are included with Windows and have a .DRV extension on their filenames.

A driver contains important information that Windows needs to know about your printer, such as details about printer hardware configuration and the printing interface, descriptions of fonts, definitions of character widths, and control sequences used by the printer to achieve various formats.

Windows Setup probably installed a printer driver for your printer when you installed Windows.  If you want to additional drivers installed, Control Panel.  Each printer must also be configured before you can print.

MORE INFORMATION


More Information on Printer Drivers

Products for the DOS environment each come with their own printer drivers written specifically for the individual application in question. In contrast, all products for the Windows environment are now fully dependant on the common set of printer drivers supplied with or for Windows. These are generally written by Microsoft or the printer manufacturer, and are revised from time to time to correct faults or implement new features. Many applications for Windows are similarly reliant on standard Windows procedures for print related operations such as:

 driver installation

 printer configuration (eg. Portrait/Landscape orientation)

 print job cancelling/suspending/resuming.

One positive aspect of this situation is that all printers supported by Windows are, by default, available for use by any Windows application.  As a consequence of this, however, it is now sometimes difficult to identify the cause of a printing problem - is it the application, Windows, or the printer driver?  In order to understand what is happening, it is important to have at least a basic understanding of some of the Windows utilities that control printing operations.

SEE ALSO

CONTROL PANEL and Printing

PRINT MANAGER and Printing


CONTROL PANEL and Printing

The control panel is where users can personalize their Windows environment and tailor the Windows configuration for their PC. The relevant panel here is the Printer dialogue box.   This is used to install new printers and configure existing ones.  It is also used to locate any available network queues and configurations.

To install a windows printer driver, click on Add Printer. This will move you into an additional dialogue box containing a list of all available printer drivers, and an 'Install' button. After choosing 'Install', Windows will prompt for disks.  Once the driver has been copied across, it will appear in the Installed Printers window. To allocate an interface, highlight and click on the desired printer and select 'Configure'. You will be moved into a small dialogue box where you can specify the printer port, a time-out and the option to setup or remove the printer driver.

NOTE - It is important that when installing a new printer driver that the 'Setup' button is clicked and 'OK' is selected from the dialogue box, even if you do not wish to change any of the settings at that time. This is so that the configuration file WIN.INI file is modified to contain the settings for the new printer and so that Adobe Type Manager (the Windows font enhancer supplied with the Lotus Windows suite products) will function correctly.


PRINT MANAGER and Printing

The main reason to use Print Manager is to see which print jobs are currently printing and which are queued.  It allows you to cancel or suspend print jobs, and view all of the jobs queued to a network printer by highlighting that printer and choosing :

View, Selected Net Queue.

If you experience problems printing from Windows applications try turning the Print Manager off  under the Printers section of the Windows Control Panel to see if direct printing is successful.


Using True Type
True Type

True Type is an outline font technology developed by Microsoft and Apple and is part of Apple's System 7. It is also a part of Windows 3.1.  Conceptually, True Type and Adobe fonts are the same. They perform the same function, are accessed by applications and users in much the same way and offer the same advantages over bitmap fonts. They differ in the formulae and algorithms used to produce the characters, availability of fonts and supported output devices. They can, however, be used together on the same system within the same applications.


Using PostScript

PostScript is a page description language made by Adobe.  Many laser printers and some phototypesetters use PostScript because PostScript document look professionally typeset.  A variety of type styles using either resident or soft fonts (see below) can be produced using PostScript.  Graphics and images from scanners can also be printed.

PostScript printers compose the entire page before printing.  SEE Fonts

You can install fonts by modifying your WIN.INI file using a text editor, like Notepad in Windows.  Follow these instructions:

1.  Move to the section header that identifies the current options for your selected printer.  If you are using the HP LaserJet IV on LPT3, the line would read [PostScript,LPT3].

2.  At the end of the list of printer options, type softfonts=n, where n is the total number of soft fonts you are installing.

3.  On the following line, type softfontn=drive\directory\font-name.pfm where the number n is the number of the font in a series of fonts.  For example,

softfont2=c:\fonts\palantino.pfm

would install the font Palantino.  Each font should have a softfontn= line.

4.  Include the outline file in the softfontn= line by typing a comma and the path of the outline file after the name of the PFM file.  The outline file is probably a PFB or PSO file.

Once installed, a soft font can be used.  A soft font will remain on the printer from its first use by a document till the printer is reset or turned off.

MORE INFORMATION ON ADOBE TYPE MANAGER


ATM - Adobe Type Manager

ATM provides 13 additional screen and printer fonts for all Windows applications. The ATM engine controls the installation and the selection of its options. It is required for adding and deleting Type 1 fonts to and from the Windows environment. The ATM program works with many different printers, including

* Postscript language printers

* The Hewlett-Packard Laserjet family of laser printers

* IBM Laser Printer, Laserprinter E

* IBM Proprinter, Epson, and other dot-matrix printers

* Most other Windows-supported printers (but not plotters)

NOTE: ATM uses Type 1 fonts only. It will not recognize Type 3 or Bitstream fonts.

SEE ALSO

Installation

Changes made to the system by ATM

The ATM.INI File


Installation of ATM

The ATM Installation will begin after the application installation has been completed and should take approx. 3 minutes, overwriting any prior ATM installation. Installation places the ATMCNTRL.EXE file into the WINDOWS directory.  It then places ATM.DLL and ATMSYS.DRV in the SYSTEM subdirectory (directly below the WINDOWS directory). Finally, it creates an ATM.INI file and updates the SYSTEM.INI and WIN.INI files in the WINDOWS directory.

NOTE - The ATM Icon will be automatically placed in the Program Group 'Main'. If you do not have a Group 'Main', the icon will not be added to any Group.


Changes made by ATM

SYSTEM.INI

Prior to ATM installation, the SYSTEM.INI file will contain the statement:-

system.drv=system.drv

After ATM installation, this statement will be modified to read:-

system.drv=atm.drv

atm.system.drv=system.drv

These lines are telling Windows to use ATM fonts, rather than system fonts.

NOTE - During ATM installation, there have been reports that the statement:-386grabber=vga.gr3 has 'slipped' down the SYSTEM.INI file to between the above lines. Adobe acknowledge that this can occur. Users encountering this should manually move the line back to its original position - immediately below the 286grabber statement.  A copy should always be made of any .INI file before attempting to edit the original.

WIN.INI

Prior to ATM installation, the typical Postscript printer driver section of the WIN.INI file will appear as:-

[Postscript,LPT3]

feed1=1

feed15=1

header=0

After ATM installation, this section of the WIN.INI file will be altered to appear as:-

[Postscript,LPT3]

feed1=1

feed15=1

header=1

softfonts=11

softfont1=c:\pclfonts\_a____.pfm,c:\pclfonts\_a____.pfb

softfont2=c:\pclfonts\bdbc___.pfm,c:\pclfonts\bdbc___.pfb

: (similar statements follow counting up to the softfonts number)

softfont11=c:\pclfonts\ptrg___.pfm,c:\pclfonts\ptrg___.pfb

The SOFTFONTS= statement indicates the number of soft fonts installed by ATM. Each soft  font entry indicates the location of the PFM (Postscript Font Metric) file and the PFB

(Postscript Font Binary) file. These statements are determined by the paths indicated during the ATM installation. The same directories should be indicated during the installation of any additional fonts.

NOTE:  The initial installation will cause both the PFM and PFB files to be noted for each font.  If the font is resident on the Postscript printer, the PFB files are not required and this part of the statement should be deleted. If it is not removed, the Printer Binary File is downloaded for the font requested. As each PFB file adds 80K to the printer file, a 123 worksheet with 16 words, using 8 different fonts would become approx. 680K in size and take an hour to print!. The same file might print in about 3 minutes with a PCL device. (ie. HP Laserjet).

The reason why the HP device would print so much faster is that the font is translated to a bit map and then sent to the printer. If the HP has only 512K of memory, Adobe recommends that the printer resident PCL fonts are used.

Prior to ATM installation, a Laserjet section of the WIN.INI would look like this:-

[HPPCL,LPT2]

paper=1

prtresfac=0

duplex=0

Fontsummary=D:\WINDOWS\FSLPT2.PCL

After ATM installation, the WIN.INI would be edited to read like:-

[HPPCL,LPT1]

Fontsummary=C:\WINDOWS\FSLPT1.PCL

softfonts=4

softfont1=c:\pclfonts\hv___10w.pfm,c:\pclfonts\hv___10w.sfp

softfont2=c:\pclfonts\hv___12w.pfm,c:\pclfonts\hv___12w.sfp

softfont1=c:\pclfonts\tir__10w.pfm,c:\pclfonts\tir__10w.sfp

softfont1=c:\pclfonts\tir__12w.pfm,c:\pclfonts\tir__12w.sfp

The SFP files will download soft fonts to the printer when these fonts are requested by any WINDOWS application. If any other WINDOWS font is requested, it will be bitmapped to the printer.

NOTE - If you add Type 1 fonts from third party vendors (ie anyone other than Adobe) to the Adobe Type Manager, the second half of the softfont statement will not be written to the WIN.INI file, and the font will not print on postscript printers. This will have to be manually typed in to the WIN.INI file by the user.


The ATM.INI File
ATM.INI

The ATM.INI is created the first time the user installs ATM. It is modified each time additional fonts are added. Below is the default section of the ATM.INI defining monospaced fonts. ATM will take the spacing defined by the first character in this section and apply it to all characters in that particular font.

[Fonts]

Courier,BOLD=c:\psfonts\pfm\cob____.pfm,c:\psfonts\cob____.pfb

Courier,BOLDITALIC=c:\psfonts\pfm\cobo___.pfm,c:\psfonts\cobo___. pfb

Courier=c:\psfonts\pfm\com____.pfm,c:\psfonts\com____.pfb

Courier,ITALIC=c:\psfonts\pfm\coo___.pfm,c:\psfonts\coo___.pfb

Helvetica=c:\psfonts\pfm\hv____.pfm,c:\psfonts\hv____.pfb

Helvetica,BOLD=c:\psfonts\pfm\hvb____.pfm,c:\psfonts\hvb____.pfb

Helvetica,BOLDITALIC=c:\psfonts\pfm\hvbo____.pfm,c:\psfonts\hvbo_ ___.pfb

Helvetica,ITALIC=c:\psfonts\pfm\hvo____.pfm,c:\psfonts\hvo____.pfb

Symbol=c:\psfonts\pfm\sy____.pfm,c:\psfonts\sy____.pfb

Times,BOLD=c:\psfonts\pfm\tib____.pfm,c:\psfonts\tib____.pfb

Times,BOLDITALIC=c:\psfonts\pfm\tibi____.pfm,c:\psfonts\tibi____.pfb

Times,ITALIC=c:\psfonts\pfm\tii____.pfm,c:\psfonts\tii____.pfb

Times=c:\psfonts\pfm\tir____.pfm,c:\psfonts\tir____.pfb

These are example lines in ATM.INI and do not necessarily represent the fonts, Aliases and Synonyms in all installations of ATM.

Aliases allow you to substitute one font name for another. For example, if you ask for the WINDOWS font HELV you will get the ATM font HELVETICA. So the syntax is Requested Font=Returned Font.

[Aliases]

Helv=Helvetica

Tms Rmn=Times

Roman=Times

Modern=Helvetica

Courier=Courier

Synonyms tell ATM when to substitute fonts declared in the Aliases statement, based upon the point size in the SYNONYMPSBEGIN number. So since SYNONYMPSBEGIN is set at 9, when you ask for HELV, you will only get HELVETICA when you request a point size of 9 or greater.

[Synonyms]

Helv=Helvetica

Tms Rmn=Times

Courier=Courier


Screen redraw is slow with ATM
Problem: Screen redraw is very slow when using the ATM fonts

Solution:

Increase the size of the Font Cache, from within the ATM Control Panel. A good guide ratio for the best performance would be to allocate approximately 96K for each Megabyte of extended memory.


"ATM fonts and PostScript printer fonts don't match" error
Problem:  "ATM fonts and PostScript printer fonts don't match on Helvetica" error appears

Adobe Type Manager fonts have been installed.  Upon entering Ami Pro, the message "ATM fonts and PostScript printer fonts don't match on Helvetica" appears

Solution:

The error "ATM fonts and PostScript printer fonts don't match on Helvetica" is a message that is generated by the Adobe Type Manager (ATM) program.

If a version of ATM containing Helvetica was installed prior to installing the ATM program provided with your Lotus application, modifications should be made to the ATM.INI file.

To Modify the ATM.INI file:

1. At the Windows Program Manager choose File / Run.

2. Type ATM.INI and choose OK.  This runs the Windows editor Notepad and loads the file ATM.INI.

3. Choose Search / Find.

4. Type [Aliases] and choose OK.

5. Press the DOWN arrow to position the insertion point on the line that reads:

Helv=Arial MT

6. Replace Arial MT with Helvetica so that the line reads:

Helv=Helvetica

7. If the ATM Times font has been installed, press the DOWN arrow to position the insertion point on the line that reads:

Tms Rmn=TimesNewRomanPS

If the ATM Times font has not been installed, skip to Step 9.

8. Replace TimesNewRomanPS with Times so that the line reads:

Tms Rmn=Times

9. Choose Search / Find.

10. Type [Synonyms] and choose OK.

11. Repeat Steps 5-8 to make the same chances in the [Synonyms] section.

12. Choose File / Save to save the changes.

13. Press ALT + F4 to close Notepad.

14. Exit Windows completely to the DOS prompt.

15. Load Windows and the Lotus application again.

If the message continues to appear, or if another font is listed, the fonts that are listed in Adobe Type Manager's ATM.INI file do not match the fonts listed in the WIN.INI file section for the selected PostScript printer.  Generally the reason the fonts don't match is because the PostScript printer was not the default printer in Windows at the time the ATM program was installed or the port connection for the PostScript printer has been changed since the ATM program was installed.

The Adobe Type Manager program places the names of ATM fonts in the Windows WIN.INI section for the PostScript printer that is the default Windows printer at the time ATM is installed.  If the Windows default printer at the time ATM is installed is not a PostScript printer, no ATM fonts will be listed in the WIN.INI file for a PostScript printer.  If a PostScript printer is the Windows default printer at the time ATM is installed, the ATM fonts will be listed only for the default PostScript printer connection.  For example, if a PostScript printer connected to the LPT1 port is the default printer when ATM is installed, ATM's fonts will be listed in the PostScript section of the WIN.INI file with the LPT1 connection.  If there are other PostScript sections in the WIN.INI file with other port connections, these sections will not be updated with the ATM font list.  A PostScript printer section in the WIN.INI file can be updated with the ATM font entries by following these steps;

1. Connect the PostScript printer to the desired port through the Printers section of the Control Panel.

a.In Windows run the Control Panel (there is usually an icon for the Control Panel).

b.Choose the printers icon.

c.Choose PostScript printer in the Installed printers list box.

d.Choose Configure.

e.From the Printers Configure dialog box choose the desired port.

f.Choose OK.

g.Choose Active Status.

2. Choose Configure.

3. Choose Setup.

4. Change the orientation to the opposite of the current setting (for example, if the current orientation is portrait, change it to landscape).

5. Choose OK.

6. Choose Setup to change the orientation to the desired setting if the change made in Step 4 is not the desired setting.  NOTE:The reason for changing the orientation is to force creation of a section for the PostScript printer attached to the new port in the Windows WIN.INI file if the section does not exist.  A section for the printer attached to the new port is necessary in order for ATM to add the font lines properly into the WIN.INI file.

7. Choose OK.

8. Choose OK.

9. With a mouse, double click on PostScript printer in the Installed Printers box to 	make it the default printer (without a mouse press ALT + D).

10. Choose OK.

11. Choose ALT + F4 to close the Control Panel.

12. Install the ATM fonts through the ATM Control Panel (there is usually a Windows icon for running ATM). NOTE: If the ATM fonts are not manually downloaded to the PostScript printer, use the ATM disk that is supplied with your application to install the ATM fonts instead of using the ATM Control Panel.  Installing the fonts supplied with the version 1.15 ATM program disk (this is the version that is shipped with the Lotus Windows suite) will place in the WIN.INI file the necessary information for temporarily downloading to the printer the required fonts with each print job. Installing ATM fonts from the ATM Control Panel in Windows will not place the information in the PostScript section of the WIN.INI file for downloading fonts to the printer with each print job.  This provides for the opportunity to manually download the files to the PostScript printer.

13. If the ATM disk is used in Step 12 instead of the ATM Control Panel, the ATM.INI file will need to be modified again if the ATM fonts Helvetica and Times are still installed. Repeat the steps in the section titled To Modify the ATM.INI file.  If the ATM Control Panel was used in Step 12 or if the ATM fonts Helvetica and Times are no longer installed, skip this step.

14. Exit Windows completely to the DOS prompt.

15. Load Windows.

The PostScript printer section in WIN.INI should now match the fonts listed in the ATM.INI file.


Some ATM Fonts Print Incorrectly
Problem:  Some ATM Fonts Print Incorectly

ATM is being used with an HP LaserJet Series II printer.  Sometimes the wrong font is accessed or nothing prints.

Solution:

Some customer reports have been received that ATM (Adobe Type Manager) fonts may print correctly in some Windows applications where other applications printing to the same HP LaserJet printer prints incorrect fonts or no font at all.  This situation is thought to be caused by the printer's section in the Windows WIN.INI file containing incorrect information for graphics resolution. Follow this procedure to write correct printer resolution information into the WIN.INI file:

1.Load the application that is not printing the ATM font correctly.

2.In the application, access printer setup (in Ami Pro choose File / Printer Setup / Setup).

3.For Graphics Resolution, choose a resolution other than the current setting (for example, if the current setting is 300 DPI,chose 75 DPI).

4.Choose OK.

5.Choose Setup again to access the printer's setup dialog box.

6.Change the Graphics Resolution back to the desired resolution.

7.Choose OK.

8.Choose OK if necessary to completely exit printer setup.

9.Issue the print command again.

N.B. Unusual printing problems like the one above sometimes occur with some versions of Windows printer drivers and not others. We recommend that you always obtain the latest Windows driver for the printer you use. After all, it is the driver you will use with all your Windows applications, so it is a very important link in the printing chain.

For example, a lot of copies of Windows 3.0 came with version 3.42 of the Hewlett Packard Laserjet III driver. Recently, version 3.77 has been available, and we also provide a different Laserjet III driver on the Printer drivers disk of 123 for Windows. However we recommend you use the latest Laserjet III driver, version 30.3.86, which is available from Microsoft, Hewlett Packard and bulletin boards such as Compuserve.


ATM Fonts aren't available on Plotters
Problem:  ATM fonts aren't available output device changed to a plotter?

Solution:

It is not possible to plot ATM fonts. Since plotters are vector devices, it is not possible for a plotter to print a bitmap image, the actual format of ATM fonts. The text faces which are available from Windows when a plotter is selected are the Windows GDI vector fonts, Modern, Roman and Script.


B and W output from a HP PaintJet /XL
Problem:  Black and white output from a HP Paintjet/XL color printer

Solution:

HP have recognized this as a problem with the original driver. A new driver is now available called 'HP Paintjet Family Version 1.2.


Printing with HP PaintJet Driver v1.0
Problem:  Printing with HP PaintJet Driver Version 1.0

 The following problems occur when printing from Microsoft Word for Windows version 2.0 using the Hewlett-Packard (HP) PaintJet printer driver version 1.0 that ships with Microsoft Windows version 3.0:

- Text formatted with a screen font does not print.

- Text formatted in color prints as black when using Adobe Type Manager (ATM).

Solution:

The following driver ships with Windows version 3.0:

PAINTJET.DRV  Date 5-1-90  Size 173184  Version 1.00/1.00

This driver works correctly with Word for Windows versions 1.0, 1.1, and 1.1a, but it does not work correctly with version 2.0. Graphics in a version 2.0 document may print, but text does not print, as described above.

To print text properly using version 1.0 of the HP PaintJet printer driver in Word for Windows version 2.0, you must format the text for a printer font. In Word for Windows version 2.0, printer fonts are those fonts that have the small printer icon next to them in the Font list box in the Character dialog box.

Hewlett-Packard has released version 1.2 of the PaintJet printer driver. This driver corrects the "color prints as black" problem and is available from the HP Fulfillment Center at (303) 353-7650.


Microsoft Access.INI
MS ACCESS.INI

This is the INI file for the Microsoft Access Database program 1.0 and 1.1.  Maccess.ini  resides in the user's local windows directory  (c:\windows).  It contains the setup information required for the Access Database to work as well as the interaction with external databases.  Each section describes the needed setup for the features it is supporting.   The following is only served as an example of a MSACCESS.INI.  The user should create the file on his/her own discretion and modify it to fit to his/her program environment.

[Paradox 3.X]

Filter=Paradox (*.db)|*.db|All Files (*.*)|*.*|

Extension=db

OneTablePerFile=Yes

IndexDialog=No

[dBASE III]

Filter=dBASE III (*.dbf)|*.dbf|All Files (*.*)|*.*|

Extension=dbf

OneTablePerFile=Yes

IndexDialog=Yes

IndexFilter=dBASE Index (*.ndx)|*.ndx|All Files (*.*)|*.*|

IndexExtension=ndx

[dBASE IV]

Filter=dBASE IV (*.dbf)|*.dbf|All Files (*.*)|*.*|

Extension=dbf

OneTablePerFile=Yes

IndexDialog=Yes

IndexFilter=dBASE Index (*.ndx;*.mdx)|*.ndx;*.mdx|All Files (*.*)|*.*|

[FoxPro 2.0]

Filter=FoxPro 2.0 (*.dbf)|*.dbf|All Files (*.*)|*.*|

Extension=dbf

OneTablePerFile=Yes

IndexDialog=No

CanAttach=No

[Btrieve]

Filter=Btrieve (file.ddf)|file.ddf|

Extension=ddf

OneTablePerFile=No

IndexDialog=No

[Microsoft Access]

Filter=Microsoft Access (*.mdb)|*.mdb|All Files (*.*)|*.*|

Extension=mdb

OneTablePerFile=No

IndexDialog=No

Maximized=1

Tutorial=0

[Delimited Text]

Filter=Delimited Text (*.txt)|*.txt|All Files (*.*)|*.*|

Extension=txt

OneTablePerFile=Yes

IndexDialog=No

[Fixed Width Text]

Filter=Fixed Width Text (*.txt)|*.txt|All Files (*.*)|*.*|

Extension=txt

OneTablePerFile=Yes

IndexDialog=No

[Microsoft Excel]

Filter=Microsoft Excel (*.xls)|*.xls|All Files (*.*)|*.*|

Extension=xls

OneTablePerFile=Yes

IndexDialog=No

[Lotus WKS]

Filter=Lotus 1-2-3 (*.wks)|*.wks|All Files (*.*)|*.*|

Extension=wks

OneTablePerFile=Yes

IndexDialog=No

[Lotus WK1]

Filter=Lotus 1-2-3 (*.wk1)|*.wk1|All Files (*.*)|*.*|

Extension=wk1

OneTablePerFile=Yes

IndexDialog=No

[Lotus WK3]

Filter=Lotus 1-2-3 (*.wk3)|*.wk3|All Files (*.*)|*.*|

Extension=wk3

OneTablePerFile=Yes

IndexDialog=No

[ISAM]

PageTimeout=300

[Installable ISAMs]

Paradox 3.X=C:\ACCESS\PDXISAM.DLL

FoxPro 2.0=C:\ACCESS\DBSISAM.DLL

dBASE III=C:\ACCESS\DBSISAM.DLL

dBASE IV=C:\ACCESS\DBSISAM.DLL

Btrieve=C:\ACCESS\BTRVISAM.DLL

[Paradox ISAM]

ParadoxUserName=Annie Won

ParadoxNetPath=C:\ACCESS

[dBase ISAM]

CollatingSequence=Ascii

Century=Off

Date=American

Mark=47

Deleted=Off

[Options]

SystemDB=C:\ACCESS\SYSTEM.MDA

UtilityDB=C:\ACCESS\UTILITY.MDA

[Libraries]

[ODBC]

QueryTimeout=15

LoginTimeout=20


Paradox 3.X Links
This section is required for Importing from or Exporting to Paradox 3.X file.


dBase III
This section is required for Importing from or Exporting to dBASE III files.


dBase IV
This section is required for Importing from or Exporting to dBASE IV files.


FoxPro
This section is required for Importing from or Exporting to FoxPro 2.0 files.


Btrieve
This section is required for Importing from or Exporting to Netware Btrieve Database files.


Access
This section is required for Importing from or Exporting to Microsoft Access Database files.


Delimited Text
This section is required for Importing from or Exporting to Delimited Text files


Fixed Width Text
This section is required for Importing from or Exporting to Fixed Width Text files


Excel
This section is required for Importing from or Exporting toMS Excel WorkSheet files


Lotus 123
This section is required for Importing from or Exporting to Lotus 1-2-3 WKS files


Lotus 123
This section is required for Importing from or Exporting to Lotus 1-2-3 WK1 files


Lotus 123
This section is required for Importing from or Exporting to Lotus 1-2-3 WK3 files


ISAM
This section is required to set up the ODBC connectivity parameters for an external Database.


Installable ISAM
This section is required for external Database Server Connection via the Microsoft Open Database Connect (ODBC) Interface. It defines the ODBC drivers for connecting to each of the databases.


Paradox
This entry defines the ODBC driver required to connect to a Paradox DB Server


Fox Pro
This entry defines the ODBC driver required to connect to a Fox Pro 2.0 DB Server


dBase III
This entry defines the ODBC driver required to connect to a dBASE III DB Server


dBase IV
This entry defines the ODBC driver required to connect to a dBASE IV DB Server


Btrieve
This entry defines the ODBC driver required to connect to a Netware Btrieve DB Server


Paradox
This section is required if the Paradox DB Server is on the network and you are connecting to it via the ODBC Interface.


Paradox
Enter the network directory where the Access Server Application is.

CollatingSequence=Ascii


db_isam
This section is required if the dBASE DB Server is called for via the ODBC Interface.


Options
This section is required to enable the System Database as well as the Utility Database to be accessed.


Library
This section is required to enable the use of the Access Wizard set.

C:\ACCESS\wizard.mda=ro


ODBC
This section is required to set up the ODBC connectivity parameters.


Microsoft Excel

This is the .ini file for MS Excel.  A description of each section is given below.

[Microsoft Excel]

Options=87

Options3=32

StickyPtX=539

StickyPtY=431

Maximized=1

Comment=The open=/f lines load custom functions into the Paste Function list.

Basics=1

OPEN=/F C:\EXCEL\LIBRARY\CROSSTAB\CROSSFNC.XLA

OPEN1=C:\EXCEL\LIBRARY\CROSSTAB\CROSSTAB.XLL

OPEN2=/F C:\EXCEL\LIBRARY\REPORTS.XLA

OPEN3=/F C:\EXCEL\LIBRARY\SCENARIO.XLA

OPEN4=/F C:\EXCEL\LIBRARY\SLIDES\SLIDES.XLT

OPEN5=/F C:\EXCEL\LIBRARY\VIEWS.XLA

OPEN6=/F C:\EXCEL\LIBRARY\SOLVER\SOLVER.XLA

OPEN7=/F C:\EXCEL\LIBRARY\ANALYSIS\ANALYSIS.XLA

OPEN8=/F C:\EXCEL\LIBRARY\WHATIF.XLA

[Recent File List]

File1=S:\SALES94\ORDER93\EXCELFIL\ORDER933.XLS

File2=B:\SCHEDULE.XLS

File3=C:\MARKETIN\PC911.XLS

File4=C:\MARKETIN\AMBASS.XLS

[Init Commands]

Comment=This section adds commands to Excel menus.

Syntax=menu_bar_num,menu name,command name,macro,place before command,mac key,status text,help reference

addinmgr=1,Options,Add-&ins...,'C:\EXCEL\LIBRARY\ADDINMGR.XLA'!STUB,13,,Add or

remove Add-Ins,EXCELHLP.HLP!1707

reports=1, File, Print R&eport...,'C:\EXCEL\LIBRARY\REPORTS.XLA'!STUB,---,,Create and print named reports,EXCELHLP.HLP!1731

scenario=1, Formula, Scena&rioManager ..., 'C:\EXCEL\LIBRARY\SCENARIO.XLA'!STUB,,, Create and examine what-if scenarios,EXCELHLP.HLP!1733

views=1, Window, &View...,'C:\EXCEL\LIBRARY\VIEWS.XLA'!STUB,-,,Show or define a named view, EXCELHLP.HLP!1730

solver=1, Formula, Sol&ver...,'C:\EXCEL\LIBRARY\SOLVER\SOLVER.XLA'!STUB,,,Find solution to worksheet model,EXCELHLP.HLP!1830

analysis=1,Options,Ana&lysis

Tools...,'C:\EXCEL\LIBRARY\ANALYSIS\ANALYSIS.XLA'!STUB,,,Select an analytic procedure,EXCELHLP.HLP!1780

Changer=1,Fo&rmula,Change

Na&me...,'C:\EXCEL\LIBRARY\CHANGER.XLA'!mco00.stub,Apply Names...,,Rename name,excelhlp.hlp!1715

Glossary=1,&Edit,&Glossary...,'C:\EXCEL\LIBRARY\GLOSSARY.XLA'!mco00.stub,,,Place text in cell or define new glossary entry,excelhlp.hlp!1712

Whatif=1,Fo&rmula,What &If...,'C:\EXCEL\LIBRARY\WHATIF.XLA'!mco00.stub,Goa&l Seek...,,What If Analysis,excelhlp.hlp!1718

Audit=1,Fo&rmula,&Worksheet Auditor...,'C:\EXCEL\LIBRARY\AUDIT.XLA'!MCO00.STUB,Goa&l Seek...,,Generate audit report, map, trace, or get info on worksheet,excelhlp.hlp!1719

Compare=1,Fo&rmula,Co&mpare...,'C:\EXCEL\LIBRARY\COMPARE.XLA'!MCO00.STUB,Goa&lSeek...,,Compare active worksheet to another,excelhlp.hlp!1720

Palettes=1,Options,C&ustom

Palettes...,'C:\EXCEL\LIBRARY\COLOR\PALETTES.XLA'!mco00.stub,Color Pal&ette...,,Add a custom color palette to document,excelhlp.hlp!1734

Palettes1=2,Chart,C&ustom

Palettes...,'C:\EXCEL\LIBRARY\COLOR\PALETTES.XLA'!mco00.stub,Color Pal&ette...,,Add a custom color palette to document,excelhlp.hlp!1734

[WK? Settings]

Comment=This section controls Lotus file open and save settings.

WYSIWYG_Save=1

Load_Chart_Wnd=1

AFE=2

Monospace=1

Gridlines=0

[Line Print]

Options=2

LeftMarg=4

RightMarg=76

TopMarg=2

BotMarg=2

PgLen=66

Setup=

[Spell Checker]

Speller=Spelling 1033,0

Custom Dict1=C:\WINDOWS\MSAPPS\PROOF\CUSTOM.DIC

Suggest Always=1


The Excel Section
This section is required to enable Excel to load in the Custom functions into the Past Function list.  The Custom functions provides the enhanced functionalities invocable from MS Excel 4.0


Database Management
This entry defines the Database Data Management from Excel.  Replace C:\EXCEL in C:\EXCEL\LIBRARY\CROSSTAB\CROSSFNC.XLA with the proper directory where Excel is installed.


Database Management
This entry defines the Database Data Management from Excel.  Replace C:\EXCEL in C:\EXCEL\LIBRARY\CROSSTAB\CROSSTAB.XLL with the proper directory where Excel is installed.


Database Management
This entry defines the Database Data Management from Excel.  Replace C:\EXCEL in C:\EXCEL\LIBRARY\REPORTS.XLA with the proper directory where Excel is installed.


Scenario Management
This entry defines the Scenario Manager from Excel..  Replace C:\EXCEL in C:\EXCEL\LIBRARY\SCENARIO.XLA with the proper directory where Excel is installed.


Slide Show
This entry defines the Slides Show template from Excel.  Replace C:\EXCEL in C:\EXCEL\LIBRARY\SLIDES.XLT with the proper directory where Excel is installed.


Viewing Tool
This entry defines the Viewing Tool from Excel.  Replace the directory C:\EXCEL in C:\EXCEL\LIBRARY\VIEWS.XLA with the proper directory where Excel is installed.


Solver
This entry defines the Solver Tool from Excel.  Replace the directory C:\EXCEL in C:\EXCEL\LIBRARY\SOLVER\SOLVER.XLA with the proper directory where Excel is installed.


Analysis Tools
This entry defines the Analysis Tool from Excel.  Replace the directory C:\EXCEL in C:\EXCEL\LIBRARY\ANALYSIS\ANALYSIS.XLA with the proper directory where Excel is installed.


What If
This entry defines the WHATIF Tool from Excel.  Replace the directory C:\EXCEL in C:\EXCEL\LIBRARY\WHATIF.XLA with the proper directory where Excel is installed.


Recent Files List
This section is not important and not required.


Initialize Command
This section is required to provide initialization setup for the Enhanced Custom tools for Excel.


Add-Ins
This entry provides the setup to initialize the Add-In function for inclusion of other Customer Tools. Replace the directory C:\EXCEL in 'C:\EXCEL\LIBRARY\ADDINMGR.XLA'!STUB with the proper directory where Excel is installed.


Reporting
This entry provides setup to initialize the Reporting capability for Excel  Replace the directory C:\EXCEL in 'C:\EXCEL\LIBRARY\REPORTS.XLA'!STUB with the proper directory where Excel is installed.


Scenario Manager
This entry provides the setup to initialize the Scenario Manager for Excel.  Replace the directory C:\EXCEL in 'C:\EXCEL\LIBRARY\SCENARIO.XLA'!STUB with the proper directory where Excel is installed.


Viewer
This entry provides the setup to initialize the Viewing Tool for Excel.  Replace the directory C:\EXCEL in 'C:\EXCEL\LIBRARY\VIEWS.XLA'!STUB with the proper directory where Excel is installed.


Solver
This entry provides the setup to initialize the Solver Tools for Excel.. Replace the directory C:\EXCEL in 'C:\EXCEL\LIBRARY\SOLVER\SOLVER.XLA'!STUB with the proper directory where Excel is installed.


Add-In
This entry provides the Add-In ability to include other Customer Tools. Replace the directory C:\EXCEL in C:\EXCEL\LIBRARY\ADDINMGR.XLA'!STUB with the proper directory where Excel is installed.


Audit Tools
This entry provides the setup to initialize the Audit Tools for Excel.  Replace the directory C:\EXCEL in 'C:\EXCEL\LIBRARY\AUDIT.XLA'!MCO00.STUB.stub with the proper directory where Excel is installed.


Compare Tools
This entry provides the setup to initialize the Compare Tools for Excel.  Replace the directory C:\EXCEL in 'C:\EXCEL\LIBRARY\COMPARE.XLA'!MCO00.STUB with the proper directory where Excel is installed.


Color Tools
This entry provides the setup to initialize the Palettes Toolbox for Excel.  Replace the directory C:\EXCEL in 'C:\EXCEL\LIBRARY\COLOR\PALETTES.XLA'!mco00.stub with the proper directory where Excel is installed.


Lotus Import
This section controls Lotus file open and save settings.  It is optional.


Line Print from Lotus
This section controls Lotus macro line printing settings.  It is optional.

Comment=This section controls Lotus macro line printing settings.


Spell Checker
This section provides the setup for the Spell Checker Tools.


Custom Spelling Dictionary
This entry defines where a custom dictionary file is.  Replace the directory with the appropriate directory where a custom dictionary file of type DIC is found.

Ignore Caps=0


LOTUS.INI

This is the Lotus.ini file which is required when you are running any Lotus SmartSuite Application including Amipro, Freelance, Lotus 1-2-3, Approach, CC Mail, Lotus Notes etc.  The following is served as an example of a Lotus.ini in a user installation.  Make sure that all the Path-related entries are correct.

[Hyphenation]

Data Path=C:\AMIPRO

[Thesaurus]

Program Path=C:\AMIPRO

Data Path=C:\AMIPRO

[Grammar Checker]

Program Path=C:\AMIPRO

Data Path=C:\AMIPRO

[Spell Checker]

Program Path=C:\LOTUSAPP\SPELL

Data Path=C:\LOTUSAPP\SPELL

User Path=c:\flw

[Lotus Applications]

AMIPRO=C:\LOTUS\AMIPRO\Amipro.exe

Organize=C:\ORGANIZE\ORGANIZE.EXE

FLW=C:\LOTUS\FLW\FLW.EXE Freelance Graphics

123W=C:\lotus\123r4w\programs\123w.exe Lotus 1-2-3 Release 4

NOTES=C:\NOTES\NOTES.EXE Lotus Notes

CCMAIL=C:\CCMAIL\WMAIL.EXE cc:Mail for Windows

SMARTPIC=C:\SMARTPIC\SMARTPIC.EXE Lotus SmartPics

Net Common Directory=C:\LOTUSAPP

Common Directory=C:\LOTUSAPP

[Ami Pro Update]

SystemDir=1

IsAmiProRunning=0

UpdateVersion=30.114c

[Document File Filters]

Program Path=C:\LOTUSAPP\EXCELFLT\EXCELFLT.FLT

[Icon Palette]

Program Path=C:\LOTUSAPP

[Graphics File Filters]

Program Path=C:\LOTUSAPP\FILTERS\ISGDI9.DLL

[MultiMedia]

Program Path=C:\LOTUSAPP\MULTIMED

Data Path=C:\LOTUSAPP\MULTIMED

Execution Verbs=PLAY

[User Name Service]UserName

Program Path=C:\LOTUSAPP\UNS

AliasUser=A USER

NetUser=USER1

NetSource=NetWare

[DATALENS]DataLens

Program Path=C:\lotusapp\datalens

Data Path=C:\lotusapp\datalens


Hyphenation
This section is required to active the Hyphenation Tool from Amipro.  Substitute C:\AMIPRO with the directory LTSHYPH1.DLL is found.

Program Path=C:\AMIPRO.


Thesaurus
This section is required to active the Thesaurus Tool from Amipro.  Substitute C:\AMIPRO with the directory where AMITHES.EXE can be found.


Grammer
This section is required to active the Thesaurus Tool from Amipro.  Substitute C:\AMIPRO with the directory where LTSGRM1.DLL can be found


Spelling Checker
This section is required to active the Thesaurus Tool from Amipro.  Substitute C:\AMIPRO with the directory where LTSSPL1.DLL can be found


Lotus Application
This section is required when a Lotus SmartSuite is installed.  This provides intergration of the Lotus applications and the interconnectivity among them.  Substitute the Right Hand Side of the = side with the installation directory where the corresponding applications are installed.


AmiPro
This Entry defines the Amipro applicaton.


Orgainzer
This Entry defines the Organize application.


Freelance Graphics
This Entry defines the FreeLance Graphics application


Lotus 123
This Entry defines the Lotus 123R4 application


Notes
This Entry defines the Lotus Notes application


ccMail
This Entry defines the CC Mail for Windows application


SmartPics
This Entry defines the Lotus SmartPics application


Network Directory
This Entry defines the networked directory for the Lotus Shared application.  This is where the support functions such as DataLens, Dialoged, Excelflt, Filters, Multimed, Spell, Uns directories are.


Common Directory
This Entry defines the local directory for the Lotus Shared applications.  This is where the support functions such as DataLens, Dialoged, Excelflt, Filters, Multimed, Spell, Uns directories are.


Document Filters
This Section provides File Conversion Template support.  Substitue C:\LOTUSAPP with the Lotus Shared application directory.


Graphics File Filters
This Section provides Graphics File Conversion Template support. Substitue C:\LOTUSAPP with the Lotus Shared application directory.


Multimedia
This Section provides the MultiMedia Service support.  Substitue C:\LOTUSAPP with the Lotus Shared application directory.


User Name
This Section provides more information for the Network Name Service for the user.


Database Connectivity
This Section provides configuration informaiton for the Database Connectivity support.  Substitute C:\LOTUSAPP with the Lotus Shared application directory.


The WordPerfect .INI file
WPWIN60.INI

This is the .ini file for WordPerfect 6.0.  A description of each section is given below.

[App Server]

WPSP=?c:\wpc\spwin.exe;00000004;Speller

WPTH=?c:\wpc\thwin.exe;00000004;Thesaurus

WPMF=?c:\wpc\mfwin.exe;00000040;WordPerfect Macro Facility

[Settings]

MainDictionaryPath=c:\wpc\

SuppDictionaryPath=c:\wpc\

[PID]

WPWP=wpwpUS.wcd

[WPWP-3rd]

MacroCmd=c:\wpc\wpwcmd.dll

GM5=c:\wpwin\wpwpgm5.dll

SmQuote=c:\wpwin\wpwpsq.dll

ExpressDocs=i:\WPWIN\EXPRESSD\expressd.dll

[Printer-Screen Font Subst]

Univers=Arial

Univers Bold=Arial

Univers Bold Italic=Arial

Univers Italic=Arial

[QuickList]

Documents=c:\tmp

Graphics Files=c:\wpwin\graphics

Macros=c:\wpwin\macros

Style Libraries=c:\wpwin

[Launch-Open]

Ami Pro 1.0=WPWIN

Ami Pro 1.2b=WPWIN

DisplayWrite 5.0=WPWIN

IBM DCA FFT=WPWIN

IBM DCA RFT=WPWIN

MultiMate 4.0=WPWIN

Navy DIF Standard=WPWIN

Rich Text Format (RTF)=WPWIN

MS Word for Windows 1.1=WPWIN

WordStar 2000 1.0=WPWIN

WordStar 2000 2.0=WPWIN

WordStar 2000 3.0=WPWIN

WordStar 2000 3.5=WPWIN

WordStar 4.0=WPWIN

WordStar 5.0=WPWIN

WordStar 5.5=WPWIN

WordStar 6.0=WPWIN

WordPerfect 4.2=WPWIN

WordPerfect 5.0=WPWIN

WordPerfect 5.1/5.2=WPWIN

XyWrite III Plus 3.56=WPWIN

PlanPerfect 3.0=PL

PlanPerfect 5.0=PL

PlanPerfect 5.1=PL

WordPerfect Graphic 1.0=DR

PC Paintbrush Graphic (PCX)=PBRUSH

Windows Bitmap=PBRUSH

Windows Write=WRITE

DEC DX=WPWIN

EBCDIC=WPWIN

OfficeWriter 6.2=WPWIN

MS Word for Windows 1.0=WPWIN

MS Word 5.0=WPWIN

WITA 2.0=WPWIN

[Viewer]

DocFontSize=0000

DocFontWeight=9001

TextTabEvery=0800

[ExpressDocs Defaults]

Default Dir=C:\WPWIN\EXPRESSD\

Macros Dir=C:\WPWIN\MACROS\

Graphics Dir=C:\WPWIN\GRAPHICS\

[QuickFinder]

ExcludeProgramFiles=YES

Display=FL

IndexNumbers=YES

ExtendedChars=exclude

IndexPath=c:\qfindex\


AppServer
This section defines configuration setup for the Application Server Tools such as Speller, Thesaurus, Macro Facility.


Spelling Tool
This entry defines the Speller Application Server Tool.  Replace the c:\wpc with the proper directory where WordPerfect 6.0 is installed.


Thesaurus
This entry defines the Thesaurus Application Server Tool.  Replace the c:\wpc with the proper directory where WordPerfect 6.0 is installed.


Macro
This entry defines the WordPerfect Macro Facility Tool.  Replace the c:\wpc with the proper directory where WordPerfect 6.0 is installed.


Settings
This section defines the settings for the Application Server Tools defined in the [App Server] section.


Main Directory
This entry defines the Main Dictionary directory  Replace c:\wpc with the proper directory where the WordPerfect 6.0 shared applications are.


Supplementary Dictionary
This entry defines the Supplementary Dictionary directory  Replace c:\wpc with the proper directory where the WordPerfect 6.0 shared applications are.


AppServer3
This section defines the third party Application Server Tools such as Macro Command, Grammatik, SmartQuote and Express Doc. It is required if you would like to use those Tools.


Macro Command
This entry defines the Macro Command for Word Perfect 6.0.  Replace c:\wpc with the proper directory where the WordPerfect 6.0 shared directory is.


Grammitik
This entry defines the Grammatik Tool  for Word Perfect 6.0.  Replace c:\wpc with the proper directory where the WordPerfect 6.0 shared directory is.


SmartQuote
This entry defines the Smart Quote Tool for Word Perfect 6.0.  Replace c:\wpc with the proper directory where the WordPerfect 6.0 shared directory is.


ExpressDocs
This entry defines the Express Document Tool for Word Perfect 6.0.  Replace c:\wpc with the proper directory where the WordPerfect 6.0 shared directory is.


Printing
This section defines the font substitution for Printing.  It is not required.


QuickList
This section defines the Quick Find for locating the support data files required by the Application Server Tools.


Graphics Files
This entry defines the graphic directory where the graphic support files are.  Replace c:\wpwin with the proper directory where WordPerfect 6.0 is installed.


Macros
This entry defines the Macro directory where the predefined macros are.  Replace c:\wpwin with the proper directory where WordPerfect 6.0 is installed.


Styles
This entry defines the Style Guides directory where the predefined Styles Templates are.  Replace c:\wpwin with the proper directory where WordPerfect 6.0 is installed.


Importable Documents
This section defines the types of documents importable by WordPerfect 6.0.  It is required if you are working across word processors.


Viewer
This section defines additional configuration data for the Viewing Tool.  It is required if the Viewer Application Server Tool is defined in this .INI file.


Default ExpressDocs
This section defines additional configuration data for the Express Document Tool.  It is required if the Express Doc Application Server Tool is defined in this .INI file.


QuickFinder
This section defines additional configuration data for the Quick Finder Tool.  It is required if the Quick Finder Application Server Tool is defined in this .INI file.


Index Path for QuickFinder
This entry defines the Index directory for the QuickFinder Tool.  Replace c:\qfindex with the proper installation directory for the QuickFinder Tool.


AMIPRO.INI

This .INI file is used for Lotus Amipro 3.0 and above.  It is required for the proper operations for the application.

AmiPro.ini

[AmiVISD]

Windows Bitmap=AmiPaint.dll,.bmp,.bmp,CF_DIB,CF_BITMAP

Windows Metafile=AmiWMF.dll,.wmf,.wmf,CF_METAFILEPICT

AmiImage=Amiimage.dll,.tgf,.tgf

AmiOLE=AmiOLE.dll,.ole,.ole,Native,ObjectLink

AmiDraw=AmiDraw.dll,.sdw,.sdw,AmiDraw,C:\AMIPRO\DRAWSYM

AmiEquation=AmiEqn.dll,.tex,.tex

AmiChart=AmiChart.dll,.sdw,.sct

[AmiPro]

VISDSnapshotSave=Yes

GlossarySize=2

macrodir=c:\amipro\macros

stypath=c:\amipro\styles

Amipro Directory.

docpath=c:\amipro\docs

iconpath=c:\amipro\icons

HPLJClipping=0

isd1=Image P&rocessing...,Amiimage.dll,Adjust the appearance of gray level scanned images

isd2=&Drawing...,AmiDraw.dll,Create and edit an object-based picture in a selected frame.

isd3=&Equations...,AmiEqn.dll,Create or edit scientific and mathematical formulas and equations.

isd4=&Charting...,AmiChart.dll,Create and edit a chart in a selected frame.

thes4=amithes1.exe

application1=TIFF,B,.TIF,TIFF.FLT,C:\WINDOWS\MSAPPS\GRPHFLT

application2=PCX,B,.PCX,PCX.FLT

application3=EPS,E,.EPS,EPS.FLT

application4=HPGL,B,.PLT,HPGL.FLT

application5=DrawPerfect,B,.WPG,WPG.FLT

application6=Freelance,B,.DRW,FLFLT.FLT

application7=CGM,B,.CGM,cgm.FLT

application8=Lotus PIC,B,.PIC,PIC.FLT

application9=AutoCAD,B,.DXF,DXF.FLT

application10=?,?,.SDP,AP.FLT

application11=.BMP,?,.TGF,TIFF2.FLT

application12=.WPG,?,.WMF,WPGEXP.FLT

application13=.WPG,?,.BMP,WPGEXP.FLT

DefOptions=633

defstyle=_DEFAULT.STY

DefOptions2=458

DefImpType=1

CleanOpts=67

TbUnits=1

SpellOpts=2

[Grammar]

Business Writing=1048575,1036174,2178

All Rules=1048575,1048575,1090

Legal Writing=1048567,827391,1154

Technical Writing=1048575,917495,4360

Fiction Writing=993271,1019523,545

Academic Writing=1048567,901119,1090

Formal Writing=1048575,1023999,546

Casual Writing=898551,823168,4356

[Filters]

Samna Word=C:\AMIPRO\Samna.flt,T,.*

WordPerfect 5.x=C:\AMIPRO\wp.flt,T,.*

WS 2000 ver 1.0=C:\AMIPRO\ws2000r1.flt,T,.*

WS 2000 ver 3.0=C:\AMIPRO\ws2000r3.flt,T,.*

AdvanceWrite=C:\AMIPRO\samna.flt,T,.*

Microsoft Word=C:\AMIPRO\word.flt,T,.*

MultiMate=C:\AMIPRO\MM.flt,T,.DO?

DCA/FFT=C:\AMIPRO\FFt.flt,T,.*

Navy DIF=C:\AMIPRO\dif.flt,T,.*

WordStar=C:\AMIPRO\ws50.flt,T,.*

Windows Write=C:\AMIPRO\writeflt.flt,T,.*

1-2-3=C:\AMIPRO\123.flt,X,.W*

WordPerfect ver 4.2=C:\AMIPRO\wp42.flt,T,.*

DCA/RFT=C:\AMIPRO\rft.flt,T,.*

PeachText=C:\AMIPRO\Peach.flt,T,.*

Enable=C:\AMIPRO\Enable.flt,T,.WPF

dBase=C:\AMIPRO\dBase.flt,X,.DBF

DIF=C:\AMIPRO\ssdif.flt,X,.DIF

SuperCalc=C:\AMIPRO\scalc.flt,X,.CAL

Word for Windows 1.x=C:\AMIPRO\wword10.flt,T,.DOC

Word for Windows 2.0=C:\AMIPRO\wword20.flt,T,.DOC

Exec MemoMaker=C:\AMIPRO\emm.flt,T,.*

SmartWare=C:\AMIPRO\smart.flt,T,.DOC

Manuscript=C:\AMIPRO\mscript.flt,T,.doc

Excel 4.0=C:\AMIPRO\excelflt.flt,X,.XLS,Biff4

Excel 3.0=C:\AMIPRO\excelflt.flt,X,.XLS,Biff3

Excel=C:\AMIPRO\excelflt.flt,X,.XLS,Biff

Paradox=C:\AMIPRO\paradox.flt,X,.DB

E-Mail=C:\AMIPRO\email.flt,T,.*

1-2-3 rel 3 & 4=C:\AMIPRO\123ver30.flt,X,.WK*

DisplayWrite 4=C:\AMIPRO\dw4.flt,T,.doc

Office Writer=C:\AMIPRO\ow.flt,T,.wp

Symphony Document=C:\AMIPRO\sym.flt,T,.w*

Professional Write=C:\AMIPRO\pwflt.flt,T,.*

Wang (IWP)=C:\AMIPRO\iwp.flt,T,.DOC

Organizer=C:\AMIPRO\amiorgft.flt,X,.ORG

ASCII=C:\AMIPRO\ascii.flt,T,.*

Rich Text Format=C:\AMIPRO\rtf.flt,T,.RTF,Rich Text Format

[SmartIcons]

Placement=2

IconSize=2

FloatingRect=0,0,0,0


AmiVISD
This section defines the initialization setup for the Amipro Tools to work.  This section is required for all the Tools which are defined in the [id1]...[idn] entries in the [AmiPro] section.


AmiPro Windows Metafile Tool
This entry defines the initialization setup for the Windows Metafile Tool.


AmiPro Bitmap Tool
This entry defines the initialization setup for the Windows Bitmap Tool.


AmiPro OLE
This entry defines the initialization setup for the AmiOLE linkage and object embedding feature.


AmiImage Tool
This entry defines the initialization setup for the AmiImage Tool.


AmiDraw Tool
This entry defines the initialization setup for the AmiDraw Tool.


AmiEquation Tool
This entry defines the initialization setup for the AmiEquation Tool.


Ami Chart Tool
This entry defines the initialization setup for the AmiChart Tool.


AmiPro Section
This section defines all the required Amipro features for them to work.  This section is required.


Macro directory
This entry defines where the macros are.  Replace c:\amipro with the Amipro Directory.


Style Directory
This entry defines where the Style Sheets are.  Replace c:\amipro with the


Document Directory
This entry defines where the user documents are.  Replace c:\amipro with the Amipro Directory.


SmartIcons Directory
This entry defines where the icons are.  Replace c:\amipro with the Amipro Directory.


isd1
This entry is required for Image Processing feature from Amipro which will appear under the Tools button of the application.  Make sure that there is a corresponding entry in the AmiVISD section describing the Amiimage.dll


isd2
This entry is required for the Drawing feature from Amipro which will appear under the Tools button of the application.  Make sure that there is a corresponding entry in the AmiVISD section describing the AmiDraw.dll.


isd3
This entry is required for the Equation Processing feature from Amipro which will appear under the Tools button of the application.  Make sure that there is a corresponding entry in the AmiVISD section describing the AmiEqn.dll


isd4
This entry is required for the Charting feature from Amipro which will appear under the Tools button of the application.  Make sure that there is a corresponding entry in the AmiVISD section describing the AmiChart.dll.


thes4
This entry defines the Executable for the Thesaurus tool


Applications
This set of Entries define different conversion routine to import or export other application files into Amipro.


Grammer Tool
This section defines the Grammatik support for Amipro.  It is required if the Grammatik tool is invoked.


Filters
This section defines the Translation programs required for different file types to be translated.  Substitute all C:\AMIPRO's with the directory path where Amipro is installed.


SmartIcons
This Section defines the Smart Icons setup.  It is not required.