OSPRWARP - OS/2 WARP PRINT INFORMATION 02/01/96 ======================================================================= OS/2 Warp Print Information ======================================================================= Please Read Entire Document for Full Explanation of Procedures -------------------------------------------------------------- DESCRIPTION Frequently asked questions related to printing in OS/2 Warp. RESOLUTION Note: Make sure you have a backup of any file you intend to change. Question 1 ---------- I installed OS/2 Warp and now I can't print. I could print under OS/2 2.1 and OS/2 2.11. What do you recommend? Try adding /IRQ to the CONFIG.SYS statement, BASEDEV=PRINT0x.SYS. For the correct syntax, refer to the OS/2 Command Reference under "PRINT01" or "PRINT02." Using /IRQ directs the parallel-port device driver to use the interrupt method to print instead of polling, which is the default in OS/2 Warp. After adding this change to the CONFIG.SYS file, you must restart the system for the changes to take effect. Question 2 ---------- I installed OS/2 Warp and now I need to install a Windows printer driver. How do I do this? If you need to add a Windows printer driver after installing OS/2 Warp 3.0, you must install the driver from the Windows Control Panel. To install the Windows driver when creating a printer object from the OS/2 side: 1. Create a new printer by dragging a printer template from the Templates folder. 2. Install the OS/2 driver, if not already installed. 3. Press the Create push button. 4. You are asked if you wish to install an equivalent WIN-OS/2 printer configuration. Select YES. You are then prompted to insert the proper diskette. Note: If there is NOT an equivalent Windows driver, you are not prompted to install an equivalent driver. Only the printer drivers that are shipped with Windows 3.1 are included in OS/2 Warp. The drivers are not updated, and new printer models are not included. New Windows printer drivers must be obtained from either Microsoft or the printer manufacturer. Question 3 ---------- Does OS/2 Warp support automatic parallel-port printer-sharing boxes? Contact your hardware vendor to see if the box has been tested with OS/2 Warp. You might be able to use this device with OS/2 Warp if you are using the polling method of printing. DOS uses this method and supports the automatic sharing boxes. The OS/2 parallel-port device driver does not support these devices in OS/2 2.x releases. You can, however, test the box with polling on OS/2 Warp. To make sure polling is being used, type RMVIEW /IRQ and press Enter at a command prompt. IRQ7 should NOT be associated with the parallel port. Question 4 ---------- What is RMVIEW in OS/2 Warp? RMVIEW is a utility program included in OS/2 Warp to help resolve IRQ conflicts. To use RMVIEW: 1. Open an OS/2 Window or Full Screen session. 2. Type RMVIEW and press Enter. RMVIEW HELP provides the switches tat are available; for example: * RMVIEW /IO * RMVIEW /IRQ If you have /IRQ in the CONFIG.SYS file (using the interrupt-driven methodology), RMVIEW /IRQ displays IRQ Level = 7. If you do not have /IRQ and are using the default (or polling), there is no reference to IRQ7. If you have a DMA-enabled system and install OS/2 Warp, the default is the interrupt-driven printing protocol, and /IRQ is not in the CONFIG.SYS file. Question 5 ---------- When do you use the OS/2 Warp Omni driver? Support for the DeskJet, Epson, and PaintJet drivers has been merged into one driver called the Omni driver. The DeskJet, PaintJet, and Epson drivers also are provided on the printer diskettes. It is preferable to use the Omni driver when printing to the DeskJet, PaintJet, or Epson printers. The only time the other drivers should be used is when the system is attached to a network and printing to a 2.1 server that is currently using the 2.1 drivers. In this case the Epson, PaintJet, and DeskJet drivers should be installed on the workstation. If the DeskJet, PaintJet, or Epson driver is desired, it can be installed by selecting Other OS/2 printer driver and typing in the path where the driver is located in the printer Install window. Question 6 ---------- Why does the Pulse mini-application indicate my system is being fully utilized by printing in OS/2 Warp? When running the Pulse mini-application in OS/2 Warp and printing at the same time, Pulse could show that the system is nearly 100% utilized. This is due to polling, the default configuration for the parallel port when no /IRQ switch is in the BASEDEV=PRINT0x.SYS statement of the CONFIG.SYS file. When not many applications are running on the system, polling occurs continuously during printing. This causes Pulse to sense that the system is being fully used by printing; however, the system is functioning normally. As other programs are started, they begin to get time slices on the system. They run normally due to the system's preemptive multitasking ability with task scheduling. Therefore, multiple applications can function properly while printing, even though Pulse indicates 100% utilization. Question 7 ---------- I am printing to a Lexmark 4029 printer under OS/2 Warp with the IBMPCL5 driver. Printing from the command line works, but PM printing appears corrupt. I did not have a problem under OS/2 2.1. Why do I have the problem now? The 4029 printer comes with PCL3 support. The IBMPCL5 driver sends PCL5 data and can be used only with a 4029 that has the additional hardware to upgrade to PCL5 emulation. This hardware consists of a "daughter card" that plugs into the main circuit board to give PCL5, just as it does in the PostScript option. If you are not using an application that requires PCL5, try using another driver. Question 8 ---------- Can I install an OS/2 Warp driver on an OS/2 2.11 system? Because of changes to the printer device drivers and diskette formats in OS/2 Warp, problems could occur if these drivers are not correctly installed in any OS/2 2.11 system. Several of the printer drivers have been upgraded to 32 bits, and before installing them, you should delete their 16-bit counterparts. The diskette format for the drivers on OS/2 Warp has been changed to 1.88 MB. Before installing these 32-bit drivers in an OS/2 2.11 system, you must copy the drivers to a 1.44 MB diskette and delete their 16-bit counterparts. The drivers are: * IBMNULL driver (IBMNULL.DR_) * LASERJET driver (LASERJET.DR_) * OMNI driver (OMNI.DR_) * PLOTTER driver (PLOTTERS.DR_) * IBMPCL3 driver (IBMPCL3.DR_) * IBMPCL5 driver (IBMPCL5.DR_) * IBM42XX driver (IBM42XX.DR_) * IBM4019 driver (IBM4019.DR_) On the OS/2 Warp system: Copy the driver.DR_ and driver.EA_ files from the OS/2 Warp diskettes to a formatted 1.44 MB diskette. On the target OS/2 2.11 system: 1. Delete any jobs in the queue associated with the LASERJET driver. 2. Open the printer-object Settings notebook and select the IBMNULL printer driver as the default (or any other driver that is not in the family of the driver you want to install; that is, LASERJET). Close the Settings notebook. Do this for all printer objects that selected this family printer driver as the default. 3. Shut down and then restart the system. Shutdown must be done to ensure the appropriate driver changes are saved. 4. When the system restarts, open the printer-object Settings notebook and go to the Printer Driver page. Delete all drivers of that family type. 5. Select Yes when prompted, "Do you want to delete the files associated with this printer driver from your fixed disk?" 6. Click mouse button 2 on the default printer driver and select Install. 7. The Install New Printer Driver window appears. Select Other OS/2 Printer Driver, using A:\ as the default directory. 8. Insert the 1.44 MB diskette that contains the OS/2 Warp driver.DR_ and driver.EA_ files in drive A and select Refresh. Available drivers are displayed. 9. Select the appropriate printer driver; then select the Install push button. 10. Select the driver as default and close the printer object's Settings notebook. The object should be available for use. Notes: * If the OMNI driver has been installed in an OS/2 2.11 system and high color support is desired, unpack the LASERJET.DR_ file from OS/2 Warp Printer Driver Diskette 1 and copy RE32.DLL to the same directory as the OMNI driver (see the OS/2 Warp Command Reference for information about UNPACK). * The 16-bit versions of the PaintJet, DeskJet, and Epson drivers are included on the OS/2 Warp Printer Driver diskettes. If these updated versions must be used, copy the driver.DR_ and driver.EA_ files from the OS/2 Warp 1.88 MB diskette to a 1.44 MB formatted diskette and install as normal in the OS/2 2.11 system. When you open the Printer Install window, select Other OS/2 Printer Driver, as described in "Question 5." Question 9 ---------- Is there a user option to switch between polling and the interrupt-driven printing protocol in OS/2 Warp? Currently, the polling protocol is the default on all parallel ports, except for Micro Channel parallel ports that have DMA enabled. If you want to go back to the interrupt-driven printing protocol, you must edit the CONFIG.SYS file and add /IRQ after the statement, BASEDEV=PRINT0x.SYS. Currently, there are no plans to provide a user option via the print object or some other methodology (other than on startup) to switch between the two printing protocols. There is no API that the spooler can use to switch between polling and interrupt-driven. Question 10 ----------- There is no error reported, but the installation process seems to lock up when I try to install an OS/2 driver from OS/2 Warp Printer Diskette 3. What is the problem? There is no OS/2 printer driver on Printer Diskette 3 for OS/2 Warp. All drivers are Windows drivers. Select Cancel, insert the diskette containing the OS/2 driver, and retry the operation. ______________________________________________________________________ IBM disclaims all warranties, whether express or implied, including without limitation, warranties of fitness and merchantability with respect to the information in this document. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright (c) 1994, 1996 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.