Last night I was relaxing watching TV and my printer activated and printed out
a two page order from BrickLink.
The order had been filled, and completed 10 days ago.
The computer had been off and on, as had the printer several times since the
initial order.
How is it that something stays in memory for so long and then just presents itself
to the world, or at least my part of the world?
Last night I was relaxing watching TV and my printer activated and printed out
a two page order from BrickLink.
The order had been filled, and completed 10 days ago.
The computer had been off and on, as had the printer several times since the
initial order.
How is it that something stays in memory for so long and then just presents itself
to the world, or at least my part of the world?
Printing jobs are sent into a queue (= saved somewhere on your disk) before being
sent to the printer. If the printer doesn’t answer or is interrupted or if the
queue is interrupted or there’s a glitch and it doesn’t know the job was printed
or it forgot it was, it’ll try again later.
It may not try again immediately when the printer is available, something else
may trigger it.
When you add features like:
— multiple printers,
— multiple users / machines,
— pausing,
— auto-retry, etc.,
you also add potentialities for glitches.
Thank you, since I'm not very tech savvy, I will go with the second option,
Gremlins.
In Off Topic, SylvainLS writes:
In Off Topic, bricks2you writes:
Last night I was relaxing watching TV and my printer activated and printed out
a two page order from BrickLink.
The order had been filled, and completed 10 days ago.
The computer had been off and on, as had the printer several times since the
initial order.
How is it that something stays in memory for so long and then just presents itself
to the world, or at least my part of the world?
Printing jobs are sent into a queue (= saved somewhere on your disk) before being
sent to the printer. If the printer doesn’t answer or is interrupted or if the
queue is interrupted or there’s a glitch and it doesn’t know the job was printed
or it forgot it was, it’ll try again later.
It may not try again immediately when the printer is available, something else
may trigger it.
When you add features like:
— multiple printers,
— multiple users / machines,
— pausing,
— auto-retry, etc.,
you also add potentialities for glitches.
USA, Pennsylvania
France, Nouvelle-Aquitaine