Avoiding blue screen
A recurring blue screen can occur when different combinations of drivers are used. For example, it occurs when an HP traditional PCL driver (versions 4.3.2.38 to 4.3.2.50) is installed on the server, and when an earlier HP traditional PCL driver (version 4.3.2.38 or earlier) or Microsoft Unidriver is installed on the client. Because the architecture of these drivers is different, the settings cannot be accurately reported when the driver on the server attempts to read the configuration on the client. The driver enters an infinite loop and eventually causes a blue screen on the server. To resolve this situation, make sure that the drivers on the server and client are the same type (either HP or Microsoft
Unidriver) and the same version.
An intermittent blue screen also occurs when an HP traditional PCL driver (version 4.3.2.38 or earlier) reads beyond an array boundary. Depending on the allocation of system memory and the load of the server, the few bytes read beyond the buffer may be an invalid page and a Stop 0x50 error results.
Finally, an intermittent blue screen on a Windows NT 4.0 terminal server occurs when the server runs out of memory as the driver is executing. To remedy this situation, install the most recent drivers.
Preserving settings during autocreation
Client driver settings might be lost during autocreation. This is a limitation of Citrix MetaFrame. Driver settings such as tray configuration and print task quick sets are not read during autocreation. Paper size and orientation are the only client settings that are read during autocreation. The remaining settings are determined by the default settings of the driver installed on the server.
However, if Feature Release 1/Service Pack 1 is installed on the MetaFrame XP server, a user can go into the
Properties of the autocreated printer driver and manually configure it for features such as optional trays, setting the tray configuration, installing the duplexing unit, and hard disk settings. The settings are saved to the user's profile when the user logs out. The next time the user logs in, the user profile restores the printer settings. This feature is available only in MetaFrame XP Feature Release 1/Service Pack 1.
Installing drivers
Whether the printers are connected to a remote client or print server on a network, or whether they are connected directly to the terminal server over a parallel port, a driver must be installed on the terminal server. The remote client performs no application rendering; this is all performed at the terminal server. A driver can be installed on the terminal server in one of two ways:
• a driver is installed directly on the terminal server. An administrator installs the driver directly on the terminal server, and the driver becomes available to all of the terminal server clients.
• a driver is installed to the terminal server by using Point and Print from a client. Such a driver is available only to the the client, even though it is installed on the terminal server.
284
HP printers in terminal-server and cluster-server environments (Internal) Software Technical Reference ENWW
