Kenneth J. Harris
February 22nd 04, 10:02 PM
I recall that when I set up a small home network with one 98 computer
and one xp computer(printer connected to it), I was told to make sure
the drivers for the printer were installed on the 98 computer as well as
on the xp computer, but if both computers were xp the drivers only had
to be on the one with the printer. My 98 did have the drivers on it and
did print through the network so maybe that's the solution.
Ken
Marlene wrote:
> I have a printer connected to my XP machine. I have a Win 98 system connected to the
> network, and am trying to print to the printer on the XP machine.
>
> The print job shows up in the queue on the XP machine, status states it is printing,
> but NEVER prints. If I try to cancel the job, it never goes away(reboot is only way
> I can clear the queue for that printer). This has happened with both Brother and HP
> printers on my system, and both USB and Parallel connections, so it seems to be on the OS side.
>
> I've seen once knowledge base article that 'looked' like it could be the solution(322303), but
> not the case.
>
> Anyone have any ideas?
> Marlene
>
>
and one xp computer(printer connected to it), I was told to make sure
the drivers for the printer were installed on the 98 computer as well as
on the xp computer, but if both computers were xp the drivers only had
to be on the one with the printer. My 98 did have the drivers on it and
did print through the network so maybe that's the solution.
Ken
Marlene wrote:
> I have a printer connected to my XP machine. I have a Win 98 system connected to the
> network, and am trying to print to the printer on the XP machine.
>
> The print job shows up in the queue on the XP machine, status states it is printing,
> but NEVER prints. If I try to cancel the job, it never goes away(reboot is only way
> I can clear the queue for that printer). This has happened with both Brother and HP
> printers on my system, and both USB and Parallel connections, so it seems to be on the OS side.
>
> I've seen once knowledge base article that 'looked' like it could be the solution(322303), but
> not the case.
>
> Anyone have any ideas?
> Marlene
>
>