>>>You're right, under normal circumstances with a fairly up-to-date computer there should be no appreciable difference in print speeds between the two drivers.
>>>
>>>Who was the author of the LJ4 driver? If it was HP, do you get the same results using the W2K LJ4 driver?
>>
>>These are both from W2K.
>>
>>>
>>>Is the LJ4 directly attached to the W2K computer or is it a network printer? If it's local, is it shared with other users?
>>
>>It is on the network via a JetDirect card
>>
>>>
>>>If it's directly attached by a parallel interface, is the port standard parallel, EPP, ECP, or EPP+ECP? The LJ4 driver may be bi-directional and you may see slow or intermittent performance if it's standard, or if the computer's EPP or ECP modes are not properly implemented.
>>>
>>>Also, if the driver is bi-directional problems may be encountered if the parallel cable is substandard. Ideally it should be IEEE1284 (if memory serves).
>>>
>>>If it's a network printer a bi-directional LJ4 driver may run into problems depending on print server/queue settings.
>>
>>Do you have any ideas on which settings might be more problematic?
>
>Do users:
>
>- print to the JetDirect card directly, or
>- print to a server (i.e. computer) queue, which in turn feeds jobs to the JetDirect card?
>
>In most environments option #2 is preferred because the JetDirect has a limited amount of RAM to buffer print jobs; if that fills up it reports "busy" and print jobs seem to finish slowly.

We are running the reports on a W2K Server box. This box prints directly to the JetDirect card as the properties for the printer indicate the port the printer is on and this port references the IP address of the JetDirect card. I don't know if there is a better way to do this. I haven't ever seen any "busy" messages when we look at the print queue.

>
>In Advanced...Print Processor you could try setting data type to EMF rather than the default RAW, this may reduce total data volume sent to the print server/printer.

I tried this but no change.

>If there is any bidirectional support in the driver, turn it off.

I tried this as well but no change.