Hello all, I ama sking this question here, because I know, that on this isdn-list there are a lot of people who have hylafax running on their isdn-line, and maybe someone can help me: Suse 7.3 hylafax 4.1-34 ghostscript 6.51-159 Win XP-clients, running WHFC, using Apple Laserwriter 16/600 driver I know that this problem could exist, because it takes (too) long to convert ps to tiff, hence the possibility to enlarge PostScriptTimeout in hylafax-config files. I already did that, enlarging it from 300 to 1200 secs. When I print a report from an Access-application to fax, larger than 1 page, it times out, giving "Job time limit exceeded" message. It seems to me, that gs is looping, because the gs process is still there, driving the cpu up to 100%. When I print a 10+page document from Word, gs converts so fast, that I can hardly see the PID in ps -ax, and fax is sent with no problem. Therefore my conclusion is, that there must be something wrong in the job printed, like hylafax states: <<quote>> Your facsimile job to xxxx xxxxxxxx was not sent because document conversion to facsimile failed. The output from the converter program was: %%[ ProductName: GNU Ghostscript ]%% [Job time limit exceeded] Check any PostScript documents for non-standard fonts and invalid constructs. <<unquote>> My question: does any of you faxwizards know how I can determine what is exactly going wrong in gs-conversion, and how can I find the invalid construct?? TIA Leen (PS: sorry I write in English, it is way better then my German, but if you want to use German, no problem, I can read and understand it enough..)