>>>>>I have a client who is getting get an error 125 - 'Printer not ready' once every two or three weeks. This system is being used all day, every day. After restarting the system, everything works again.
>>>>>
>>>>>I didn't know I could get this error under Windows!
>>>>>
>>>>>Any ideas?
>>>>>
>>>>>Thanks,
>>>>>Shane
>>>>I have the same problem in win 3.11, the spooler
>>>>from printer manager hangs up when it gets to
>>>>36 jobs aprox. The only solution I could find was to
>>>>install win95
>>>
>>>
>>>I have also run into this problem -- but the max number of print jobs I could get out was 32. You have to exit Windows to reset. As Claudio alluded to, you have to upgrade to win95 to solve this problem.
>>>
>>>Best of luck!
>>>
>>>Valerie
>>
>>the print routine in fpw2.6 is infamous for 'losing' memory. we had a situation where one of our clients could print 50-60 invoices at a time before this happened. the original design had a loop around the report form to printer command (bad design). we replaced it with a report form to printer for [range of invoice numbers]. this took only one report command but would print until they finished (or hit a paper jam).
>
>Are you using '2.6a', because I believe this was one of the fixes that
>they made for 2.6, if not you can download for free the patch for
>2.6a, I used to have that problem sometimes and I haven't have it after
>I patched to 2.6a.
>HTH
>=Good.Luck()
>luisg@netrunner.net

probably, but batching the jobs instead of printing individually met our needs. there were several other reasons we had to do that...