| | 752 | <p><br><a name="3_2"></a> |
| | 753 | <h3>3.2. Why does nothing happen when I try to open the driver/job properties in my desktop printer object?</h3> |
| | 754 | |
| | 755 | <p>This problem happens if the desktop is unable to load the driver information for some reason. This can be caused by a number of things; the most common reasons are listed below. |
| | 756 | <dl> |
| | 757 | <dt><i><tt>AUXPRINT.PAK</tt> is missing or out of date</i> |
| | 758 | <dd>Whenever you import a PPD file using PIN, its information gets added to the file AUXPRINT.PAK, which resides in the same directory as the print driver (ECUPS.DRV). When you then install the imported model's driver, this file is supposed to get copied to the correct directory (<tt><i>?</i>:\OS2\DLL\ECUPS</tt>) automatically. Unfortunately, this does not always happen (due to an apparent bug somewhere). As a result, the WPS cannot locate the imported information for the new model. |
| | 759 | <p>To fix this, manually copy the updated AUXPRINT.PAK over from the directory where PIN output the imported files. |
| | 760 | <dt><i>The driver's extended attributes are corrupt</i> |
| | 761 | <dd>The extended attributes on the driver file (ECUPS.DRV / ECUPS-HP.DRV, etc.) are vital to its operation. If they become lost or corrupted, this problem can appear. |
| | 762 | <p>If this happens, you will probably have to replace the file with a fresh copy from the original install package, then re-import any PPDs which you previously imported. |
| | 763 | <dt><i>The driver entry is missing from OS2.INI</i> |
| | 764 | <dd>The desktop keeps information about installed printer drivers in the desktop "user INI" file (OS2.INI), under the application name <tt>PM_DEVICE_DRIVERS</tt>. If the entry for the ECUPS.DRV (or any other) print driver gets lost somehow, all ECUPS printers will become unusable. This has been observed to happen sometimes when using the PRNDRV utility from the Keller Group to delete printers, queues, or devices. |
| | 765 | <p>The fix in this case is to open an INI editor (such as the built-in "registry editor" REGEDIT2.EXE) and make sure that the application <tt>PM_DEVICE_DRIVERS</tt> contains the key <tt>ECUPS</tt> (no extension), whose value is the fully-qualified filename of ECUPS.PDR. This should become effective immediately. (If the problem occurs with a different driver, such as PSCRIPT or ECUPS-HP, substitute the appropriate driver name in both the key name and the value.) |
