Problem printing on 2000 server

  • Thread starter Thread starter Ignacio Machin \( .NET/ C# MVP \)
  • Start date Start date
I

Ignacio Machin \( .NET/ C# MVP \)

Hello,

I have problem printing on a windows 2K server, it has a shared Okidata
impact printer dedicated to print invoices from W98 workstations, as soon as
one of these machines send a print work the printing consume around 70% of
the processor memory which greatly degrade all other applications. I see in
the Task Manager that a process named System consumes almost all the CPU.

Is there any way I can lower the priority of the printer or there is any
other way to improve the printing speed?

Thanks in advance.

Ignacio Machin.
 
--------------------
From: "Ignacio Machin \( .NET/ C# MVP \)" <ignacio.machin AT
dot.state.fl.us>
Subject: Problem printing on 2000 server
Date: Mon, 19 Apr 2004 09:45:26 -0400

Hello,

I have problem printing on a windows 2K server, it has a shared Okidata
impact printer dedicated to print invoices from W98 workstations, as soon as
one of these machines send a print work the printing consume around 70% of
the processor memory which greatly degrade all other applications. I see in
the Task Manager that a process named System consumes almost all the CPU.

Is there any way I can lower the priority of the printer or there is any
other way to improve the printing speed?

Thanks in advance.

Ignacio Machin.
----------------------

70% CPU should be considered unacceptable behavior in you situation. The
first thing I would suspect would be a driver issue. Check to see if your
particular model of Okidata printer has a driver that is included with
Windows 2000, as opposed to using the vendor-supplied drivers.
--
~~~ JASON HALL ~~~
Performance Support Specialist,
Microsoft Enterprise Platforms Support
~~ This posting is provided "AS IS" with no warranties, and confers no
rights. Use of included script samples are subject to the terms specified
at http://www.microsoft.com/info/cpyright.htm
~~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
Back
Top