Print Spooling vs suspend
in [Windows XP]
|
From: MRCS on 4 Jul 2010 06:44 Struggled with this problem for days, and it never would have occurred to me it was a print problem if I hadn't stumbled across it thru System Information. In my case there was no CPU activity. What may have been the glitch was that I changed the default printer after the incomplete pending print job, not knowing I had one. Jeff Barnett wrote: Jose wrote:As I stated in my original message, the sleep/suspend mode was 04-Feb-10 Jose wrote: As I stated in my original message, the sleep/suspend mode was S3; hibernate is S4. S3 is also called suspend to RAM. As I understand MS rules for initiating S2/S3/S4, the CPU cannot be more than x% busy for a user specified period or no state transfer will occur. (Of course you can give one of the various suspend/hibernate now commands and it will force transition.) So in part the ability to sleep will depend on the relative sizes of x%, the user-specified period, the spooler time-between-checks, the amount of resources necessary to poll the printer, and several other things. What I managed to discover was that a printer missing/not responding state can block state transition. The only time you probably would care about this tidbit of trivia is if your computer was failing to enter sleep automatically. -- Jeff Barnett Previous Posts In This Thread: On Thursday, February 04, 2010 3:51 PM Jeff Barnett wrote: Print Spooling vs suspend A few days ago we took one of our printers off the network and to a repair shop. Later we noticed that one of our computers no longer dropped to sleep (S3 mode). I have spent a few days trying to figure out why and repair the problem. The computer owner suddenly recalled trying to print something after the printer was removed from the network so the print job was in the spool. The print job was deleted and the computer went to sleep! I am sending this note for two reasons: 1) In case someone else out there is tracking down a sleep problem - it is tricky since the printer icon can disappear from the task bar removing hints about the source of the problem 2) To ask a question based on my memory: MEMORY = (I think that MS required software to work and play well with sleep modes in order to be XP certified.) QUESTION = (If memory is correct would not the XP spooler fail to be XP certified if someone other than MS wrote it?) Tongue firmly in cheek on 2 above. -- Jeff Barnett On Thursday, February 04, 2010 4:10 PM Pegasus [MVP] wrote: I suspect that it is by design that pending print requests should prevent aPC I suspect that it is by design that pending print requests should prevent a PC from going into a sleep state. It is likely that many printers are unable to cope with an extended interruption in the flow of print data. What would you say if you had a network printer that refused to accept any more print jobs because the PC that has just sent half of a print job has been put to sleep? You would probably slam Microsoft for not having thought this through properly. I think you can take your tongue out of your cheek. On Thursday, February 04, 2010 4:24 PM Jeff Barnett wrote: Pegasus [MVP] wrote:Note that the job had never reached the printer because it Pegasus [MVP] wrote: Note that the job had never reached the printer because it was OFF the network (and at the repair shop). Therefore, the spooler kept trying to send the job and not even a byte (or a packet depending on how the net error was reported) of the print stream arrived. The point is that after N tries, where N was certainly not a small number after two days, there is reason to believe that 1) the time between tries should have been backed off and/or 2) a mechanism should have been used that did not disturb the count-down-to-sleep timer. I am still of the opinion, given that my memory is correct, that MS would not have certified this behavior for another organization. And my tongue is still in my cheek. -- Jeff Barnett On Thursday, February 04, 2010 6:59 PM Jose wrote: Do you mean Stand By mode (or Hibernate)? Do you mean Stand By mode (or Hibernate)? Why do not you try it again and see. I unhooked my wireless printer and printed a file. It ended up where all good print jobs go: C:\Windows\system32\spool\PRINTERS As a matter of fact, I printed several things using various programs. I adjusted my Power Options System standby setting (I could not find any sleep option) from Never to 2 minutes, OK'd my way out, double clicked the clock so I could watch the time and in 2 minutes, the system entered Stand By. I already know Hibernate works when there are pending jobs in the spool folder since I choose to use Hibernate instead of Stand By. I did not get any print icon either so there was nothing to disappear since it never appeared. I clicked the mouse to bring the system around, plugged my printer back in, and was shortly presented a print preview of my document since that is how I have my system set up (print preview) and the printer icon showed up until all my print jobs were dispatched. The files printed fine. I am not saying you do not have a problem, but if you can try it and verify that would be good information to know. I cannot recreate any situation where a pending print job inhibits Stand By or Hibernate. If you can think of another way for me to test it, I will do it. On Thursday, February 04, 2010 7:02 PM Jose wrote: eerI also just tried it with a USB wired printer and it works the sameway as e er I also just tried it with a USB wired printer and it works the same way as my wireless printer - as expected. I would not think MS would care how the printer was connected and apparently is does not in my situation. On Thursday, February 04, 2010 10:39 PM Jeff Barnett wrote: Jose wrote:As I stated in my original message, the sleep/suspend mode was Jose wrote: As I stated in my original message, the sleep/suspend mode was S3; hibernate is S4. S3 is also called suspend to RAM. As I understand MS rules for initiating S2/S3/S4, the CPU cannot be more than x% busy for a user specified period or no state transfer will occur. (Of course you can give one of the various suspend/hibernate now commands and it will force transition.) So in part the ability to sleep will depend on the relative sizes of x%, the user-specified period, the spooler time-between-checks, the amount of resources necessary to poll the printer, and several other things. What I managed to discover was that a printer missing/not responding state can block state transition. The only time you probably would care about this tidbit of trivia is if your computer was failing to enter sleep automatically. -- Jeff Barnett On Friday, February 05, 2010 7:15 AM Jose wrote: tngtherbeolerestRelative sizes, unspecified period - X%, spooler t ng the r be oler e st Relative sizes, unspecified period - X%, spooler time-between-checks (what is the spooler time between checks), several other things... does not sound like very good science since none of the variables mentioned include a method to tie a specific value to one of the terms. What are the several other things. Where are you getting these MS rules for initiating S2/S3/S4? What method was used to discover that a printer missing/not responding state can block state transition and how would I recreate that state? On Friday, February 05, 2010 1:45 PM Jeff Barnett wrote: Jose wrote: Jose wrote: Submitted via EggHeadCafe - Software Developer Portal of Choice Producer/Consumer Queue and BlockingCollection in C# 4.0 http://www.eggheadcafe.com/tutorials/aspnet/7d10d73c-321c-446e-8b6d-b81ee8d9b314/producerconsumer-queue-and-blockingcollection-in-c-40.aspx
|
Pages: 1 Prev: export/import users grant between pcs Next: SM Bus Controller has no driver |