HylaFAX The world's
most advanced open source fax server
ghostscript and win95 (fwd)
Date: Thu, 03 Apr 1997 10:01:19 -0800
>From: Fred <email@example.com>
Subject: ghostscript and win95
This seems to be a pretty well covered topic in the Mailing list
archives - but I would like ask one more question about ghostscript and
The FAQ Q163 refers to the following fix for being able to use
Ghostscript 2.6x and Win95 postscipt print drivers to solve the 'memory
>"I think that this has nothing to do with winflex nor Hylafax. I had a
> similar problem and that was caused by Ghostscript 2.6x and Win95 > Postscript output in general. I upgraded to Ghostscript 4.01 and the > problem was gone.
> An alternative is to run following script on you PS output to > remove the error code from the PS file. This worked for me for GS 2.6x > files and Win95.
> sed '/^\/VM?/,/ VM?/d' $1 > outp "
I upgrade to GS 4.01 and found that it does fix this bug - however I
noticed a great increase in system resource demand for converting the
postscript files to tiff files - (it seems to take much longer to
preform the same task that Gs 2.6x).
I would therefore like to stick with Gs 2.6x and apply the above
My question is: Can I insert this sed command into one of the sendfax
script files to automatically ammend the postscript files comming from a
Winflex client? If this can be automated - where and in which script
would I place the command. (Not being well versed in Sed - I have
attempted to do this but failed)
Has anyone automated a good fix for this problem?