The printer had been working fine using a USB to parallel converter and the
MS driver. However a week or so ago it stopped doing so. The symptoms are
that if a test page is sent, it can be seen in the queue as printing, and the
print light flashes for while. Then the message in the print queue changes to
say error or error sent to printer, but nothing gets printed. If the machine
is left it sometimes but not always prints a few hours later.

Changing to a different USB port enables a test page to be printed, but the
job is still shown in the queue and eventually changes to the error status. A
second test page doesn't get printed, and the system then behaves as above.

Any Ideas?



Thanks

What Vista OS are you using?




"julian" wrote:

> The printer had been working fine using a USB to parallel converter and the
> MS driver. However a week or so ago it stopped doing so. The symptoms are
> that if a test page is sent, it can be seen in the queue as printing, and the
> print light flashes for while. Then the message in the print queue changes to
> say error or error sent to printer, but nothing gets printed. If the machine
> is left it sometimes but not always prints a few hours later.
>
> Changing to a different USB port enables a test page to be printed, but the
> job is still shown in the queue and eventually changes to the error status. A
> second test page doesn't get printed, and the system then behaves as above.
>
> Any Ideas?
>
> Thanks

Hi

Vista Home

Julian

"frogstomp" wrote:

> What Vista OS are you using?
>
>
>
>
> "julian" wrote:
>
> > The printer had been working fine using a USB to parallel converter and the
> > MS driver. However a week or so ago it stopped doing so. The symptoms are
> > that if a test page is sent, it can be seen in the queue as printing, and the
> > print light flashes for while. Then the message in the print queue changes to
> > say error or error sent to printer, but nothing gets printed. If the machine
> > is left it sometimes but not always prints a few hours later.
> >
> > Changing to a different USB port enables a test page to be printed, but the
> > job is still shown in the queue and eventually changes to the error status. A
> > second test page doesn't get printed, and the system then behaves as above.
> >
> > Any Ideas?
> >
> > Thanks

Having a similar problem with a LaserJet 6L connected through a USB to
parallel adapter. Machine is a Toshiba laptop running Vista Business.
Printer worked fine first time I installed the adapter and then the printer.
Both recognized, and drivers installed. Printing fine.
On re-boot, system creates a new printer with COPY1 appended to the name,
and a new virtual USB port to print through. However it doesn't get set as
the default printer. Print jobs now queue in the original printer, with an
error condition.
If I delete the COPY1 printer, then go into the original printer's
Properties -> Ports, and change the port selected to the other (just
created) USB virtual port, the print jobs then print.
This happens every time the machine is re-booted. If I don't fix it (as
above) and re-boot again, a COPY2 version of the printer is created and a
3rd USB virtual port.

Any help would be much appreciated.

Bob


"julian" <julian@discussions.microsoft.com> wrote in message
news:0414EAD8-1196-4D17-8494-9A24645381E1@microsoft.com...
> Hi
>
> Vista Home
>
> Julian
>
> "frogstomp" wrote:
>
>> What Vista OS are you using?
>>
>>
>>
>>
>> "julian" wrote:
>>
>> > The printer had been working fine using a USB to parallel converter and
>> > the
>> > MS driver. However a week or so ago it stopped doing so. The symptoms
>> > are
>> > that if a test page is sent, it can be seen in the queue as printing,
>> > and the
>> > print light flashes for while. Then the message in the print queue
>> > changes to
>> > say error or error sent to printer, but nothing gets printed. If the
>> > machine
>> > is left it sometimes but not always prints a few hours later.
>> >
>> > Changing to a different USB port enables a test page to be printed, but
>> > the
>> > job is still shown in the queue and eventually changes to the error
>> > status. A
>> > second test page doesn't get printed, and the system then behaves as
>> > above.
>> >
>> > Any Ideas?
>> >
>> > Thanks