printing is sluggish - please help

A

Adam

Host OS: Ubuntu 10.04 LTS
Guest OS: Windows XP Pro SP3 (via VirtualBox)

My laptop prints to a printer connected to
a Win98SE desktop on a home network.
The print dialog is very sluggish to open (from the guest OS).
What is the likely cause of this problem? And, how can it be fixed?
 
T

The Wizard of Oz

Host OS: Ubuntu 10.04 LTS
Guest OS: Windows XP Pro SP3 (via VirtualBox)

My laptop prints to a printer connected to
a Win98SE desktop on a home network.
The print dialog is very sluggish to open (from the guest OS).
What is the likely cause of this problem? And, how can it be fixed?
Presuming this is a new set up rather than one which suddenly became
slow...

Look at the process. The XP has to create the document and send it to
the network. VirtualBox accepts it and sends it to Ubuntu. Ubuntu
accepts it and sends it to the network. The router says "I know where
this goes" and sends it to your 98 machine which contacts the physical
printer and prints it.

Each step of the process adds its own delay and bottleneck. The two
biggest would be VirtualBox and your LAN (presuming you aren't using
gigabit). In addition, XP is not printing a TEXT document. If there are
any fonts, colour, or formatting there is a conversion to a graphic
format. Since you are running in a virtual machine the corresponding
time to convert the information to graphics will go up.

As to the print dialogue box... Remember you are running in a virtual
machine. Knock the speed of the computer down by at least half. XP
(particularly SP3) is the slowest of the three OSs you have. It's not
exactly rapid to begin with. Some printer drivers query the printer for
ink/toner levels and other information. From my observation, CUPS (the
Linux end of things) usually doesn't bother. So XP could be expecting
information and not be getting it.

The only thing I can suggest is to make sure your XP has enough RAM to
play with. As to what is enough... Your guess is as good as mine.

Later
Mike
 
A

Adam

Thanks, my response is inline.


The Wizard of Oz said:
Presuming this is a new set up rather than one which suddenly became
slow...

The latter case is more fitting since it didn't used to be like this.
What could have messed things up? My guess is that
installing the "HP LaserJet 4100 PCL 5e" drivers from
the CD may have messed things up. I'm trying to find
instructions on how to properly reinstall the drivers for similar setup.

Look at the process. The XP has to create the document and send it to
the network. VirtualBox accepts it and sends it to Ubuntu. Ubuntu
accepts it and sends it to the network. The router says "I know where
this goes" and sends it to your 98 machine which contacts the physical
printer and prints it.

Each step of the process adds its own delay and bottleneck. The two
biggest would be VirtualBox and your LAN (presuming you aren't using
gigabit). In addition, XP is not printing a TEXT document. If there are
any fonts, colour, or formatting there is a conversion to a graphic
format. Since you are running in a virtual machine the corresponding
time to convert the information to graphics will go up.

It hasn't even gotten to the printing part yet. The delay is in waiting for
the dialog box to open so I can select OK to print.
 
P

Patok

Adam said:
The latter case is more fitting since it didn't used to be like this.
What could have messed things up? My guess is that
installing the "HP LaserJet 4100 PCL 5e" drivers from
the CD may have messed things up. I'm trying to find
instructions on how to properly reinstall the drivers for similar setup.

Check the System event log of the XP. Do you see, after the LPDSVC startup
information, an error message? The Service Control Manager saying that some
service depends on the Parallel arbitrator group and no member of this group
started? If yes, it means that the driver you installed thinks that your
computer has a parallel port, which it doesn't. Is that the case?
 
P

Paul

Adam said:
Host OS: Ubuntu 10.04 LTS
Guest OS: Windows XP Pro SP3 (via VirtualBox)

My laptop prints to a printer connected to
a Win98SE desktop on a home network.
The print dialog is very sluggish to open (from the guest OS).
What is the likely cause of this problem? And, how can it be fixed?

The protocols involved in files shares and printing, are
pretty complicated. The length of this article, and the
lack of details, show how many versions there are, and
the need to map from one scheme to another, in a
heterogeneous network.

http://en.wikipedia.org/wiki/Server_Message_Block

In my small experience using virtual machines (more than one on
the same PC), I find that the "discovery" phase, sucks. I've had
cases where one VM, simply refuses to find a share on a second VM,
necessitating shutting both down and rebooting them.

So if I was approaching the problem, I'd look for a solution that
avoided discovery as much as possible. I've found for shares, that
if I use an IP address for the share machine, I get there a lot faster.

This page details setting up a printer having an IP address.
I don't know if this will solve your problem, but it might
help avoid discovery.

http://uis.georgetown.edu/software/documentation/winxp/winxp.network.printer.html

To make that work in the future, you're probably going to need some
usage of static IP addresses. Perhaps the Win98 machine can be
changed from DHCP over to static, then once the static IP address
is known, then set up printer details in WinXP ?

Just a guess,
Paul
 
A

Adam

Patok said:
Check the System event log of the XP. Do you see, after the LPDSVC startup
information, an error message? The Service Control Manager saying that some
service depends on the Parallel arbitrator group and no member of this group
started? If yes, it means that the driver you installed thinks that your
computer has a parallel port, which it doesn't. Is that the case?

Thanks, in Event Viewer (eventvwr.msc), since the system started up a week ago,
I don't see any event types from Service Control Manager other than
"Information". No errors or warnings from Service Control Manager.
 
A

Adam

Paul said:
The protocols involved in files shares and printing, are
pretty complicated. The length of this article, and the
lack of details, show how many versions there are, and
the need to map from one scheme to another, in a
heterogeneous network.

http://en.wikipedia.org/wiki/Server_Message_Block

In my small experience using virtual machines (more than one on
the same PC), I find that the "discovery" phase, sucks. I've had
cases where one VM, simply refuses to find a share on a second VM,
necessitating shutting both down and rebooting them.

So if I was approaching the problem, I'd look for a solution that
avoided discovery as much as possible. I've found for shares, that
if I use an IP address for the share machine, I get there a lot faster.

This page details setting up a printer having an IP address.
I don't know if this will solve your problem, but it might
help avoid discovery.

http://uis.georgetown.edu/software/documentation/winxp/winxp.network.printer.htm
l

To make that work in the future, you're probably going to need some
usage of static IP addresses. Perhaps the Win98 machine can be
changed from DHCP over to static, then once the static IP address
is known, then set up printer details in WinXP ?

Just a guess,
Paul

Thanks (Guru Paul), I'll have to look into
giving the Win98SE desktop a static IP address as soon as possible.
 
P

Patok

Adam said:
Thanks, in Event Viewer (eventvwr.msc), since the system started up a week ago,
I don't see any event types from Service Control Manager other than
"Information". No errors or warnings from Service Control Manager.

Just to clarify - if this was the case, it would happen only once - at boot
time. Right after the LPDSVC started. Afterwards there would be no other error
messages, no matter how long the system stayed on.
It was a nice try. :) I had the same symptoms you do - about a 30 second
delay from clicking the "print" button until the dialog appeared - and that was
the reason in my case. Sorry I couldn't help.
 
A

Adam

Patok said:
Just to clarify - if this was the case, it would happen only once - at boot
time. Right after the LPDSVC started. Afterwards there would be no other error
messages, no matter how long the system stayed on.
It was a nice try. :) I had the same symptoms you do - about a 30 second
delay from clicking the "print" button until the dialog appeared - and that was
the reason in my case. Sorry I couldn't help.

Thanks for trying.
 
D

David H. Lipman

From: "Adam said:
Host OS: Ubuntu 10.04 LTS
Guest OS: Windows XP Pro SP3 (via VirtualBox)

My laptop prints to a printer connected to
a Win98SE desktop on a home network.
The print dialog is very sluggish to open (from the guest OS).
What is the likely cause of this problem? And, how can it be fixed?

After reviewing this thread...

I suggest putting the printer on a Print Server and printing directly to it via TCP/IP and
not via Win9x Print Share.
 
A

Adam

David H. Lipman said:
After reviewing this thread...

I suggest putting the printer on a Print Server and printing directly to it via TCP/IP and
not via Win9x Print Share.

Thanks, I'll have to look into the best way to
setup a Print Server for my case as well.
Things like ... what type of system, OS, etc.
Sounds like fun. :)
 
D

David H. Lipman

From: "Adam said:
Thanks, I'll have to look into the best way to
setup a Print Server for my case as well.
Things like ... what type of system, OS, etc.
Sounds like fun. :)

A Print Server is a standalone appliance that connects directly to the printer (parallel
or USB) and via Ethernet, Bluetooth or WiFi to your network. There is no OS to speak of.

Once the IP address is set on the Print Server appliance, you point any OS to print to its
IP address. Usually a good Print Server can use; DLC, Appletalk, TCP/IP and IPX/SPX
protocols.
 
A

Adam

David H. Lipman said:
A Print Server is a standalone appliance that connects directly to the printer (parallel
or USB) and via Ethernet, Bluetooth or WiFi to your network. There is no OS to speak of.

Once the IP address is set on the Print Server appliance, you point any OS to print to its
IP address. Usually a good Print Server can use; DLC, Appletalk, TCP/IP and IPX/SPX
protocols.

Thanks (Guru Dave), I found some good info here ...

How to set up a print server:
http://www.theblog.ca/print-server-how-to

Looks like Option #3 best suits my case since
my router (Linksys BEFSR41) does not have a built-in print server, I think.
Will give it a try as soon as I get a chance.
 
D

David H. Lipman

From: "Adam said:
Thanks (Guru Dave), I found some good info here ...

How to set up a print server:
http://www.theblog.ca/print-server-how-to

Looks like Option #3 best suits my case since
my router (Linksys BEFSR41) does not have a built-in print server, I think.
Will give it a try as soon as I get a chance.

That is not a good source.

Here is a Wiki on HP JetDirect devices...
http://en.wikipedia.org/wiki/JetDirect

http://www.amazon.com/D-Link-DP-300U-100TX-2-Parallel-Server/dp/B00008UA9I

http://www.amazon.com/Jetdirect-300X-1PAR-Print-Server/dp/B000EVOPHY

CSCO wireless to USB
http://homestore.cisco.com/en-us/pr...VproductId53934612VVcatId552009VVviewprod.htm

Here is a Linksys with an Ethernet switch and print server
http://www.amazon.com/Cisco-Linksys-PSUS4-PrintServer-Port-Switch/dp/B0000DF2LT

Linksys Wireless to USB
http://www.amazon.com/Cisco-Linksys-WPS54GU2-Wireless-G-Print-Server/dp/B0000E658Q
 
A

Adam

David H. Lipman said:
The router is not detecting "what" it right now?

Sorry, this is my first attempt at setting up a print server so
putting the pieces together is not smooth sailing.

The "it" refers to the print server (JetDirect).

According to ... http://www.theblog.ca/print-server-how-to

"First, you will need to find the IP address of the printer...
If you are using a network-capable printer (option #3), log in to
your router and find the printer in the “DHCP” or “Client list” or similar page.
If your router has a “static IP” feature,
where you can assign fixed internal IP addresses to MAC addresses,
be sure to use that so that the printer always has the same IP address."

Turns out the router is not detecting the print server because
JetDirect is not even showing up in the Printer Configuration Page when
performing Step 5 according to ...

http://ec1.images-amazon.com/media/i3d/01/A/man-migrate/MANUAL000039870.pdf

So, JetDirect is not operating properly.
 
D

David H. Lipman

From: "Adam said:
Sorry, this is my first attempt at setting up a print server so
putting the pieces together is not smooth sailing.

The "it" refers to the print server (JetDirect).

According to ... http://www.theblog.ca/print-server-how-to

"First, you will need to find the IP address of the printer...
If you are using a network-capable printer (option #3), log in to
your router and find the printer in the “DHCP” or “Client list” or similar page.
If your router has a “static IP” feature,
where you can assign fixed internal IP addresses to MAC addresses,
be sure to use that so that the printer always has the same IP address."

Turns out the router is not detecting the print server because
JetDirect is not even showing up in the Printer Configuration Page when
performing Step 5 according to ...

http://ec1.images-amazon.com/media/i3d/01/A/man-migrate/MANUAL000039870.pdf

So, JetDirect is not operating properly.

What model HP JetDirect ?

The objective is to hold down the reset button for ~30 secs. while the JetDirect is
connected to the network. This will cause the JetDirect to forget any settings and to
subsequently initiate a DHCP call. Once it has an IP address you can go into the Router's
DHCP table and determine the IP address which was assigned. Then you can Telnet or HTTP
into the IP address and statically set the IP to to one you want and set anything else you
prefer. Once completed you can then setup clients to print to it.
 
A

Adam

David H. Lipman said:
What model HP JetDirect ?

The objective is to hold down the reset button for ~30 secs. while the JetDirect is
connected to the network. This will cause the JetDirect to forget any settings and to
subsequently initiate a DHCP call. Once it has an IP address you can go into the Router's
DHCP table and determine the IP address which was assigned. Then you can Telnet or HTTP
into the IP address and statically set the IP to one you want and set anything else you
prefer. Once completed you can then setup clients to print to it.

Thanks, the Configuration Page that came with the printer says
it's an HP JetDirect J6057A. But, I have not been able to
print a Configuration Page showing the JetDirect card.
Even after a cold reset power on, both EIO 1 & 2 are "Empty".
 
D

David H. Lipman

From: "Adam said:
Thanks, the Configuration Page that came with the printer says
it's an HP JetDirect J6057A. But, I have not been able to
print a Configuration Page showing the JetDirect card.
Even after a cold reset power on, both EIO 1 & 2 are "Empty".

OK. The directions I gave you more or less is for an External JetDirect.

You have an EIO card, 615N

So when you go to the printers LCD control panel to configure EIO, you can't manually set
the TCP/IP information. That's indicative of a bad EIO card.

Please check again by entering the LCD control panel and try find the EIO sub-menu. When
you go through the menu it should be listed.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top