Has anyone been able to send a multiple paged fax with graphics from windows 95 using winflex????
> Has anyone been able to send a multiple paged fax with graphics from windows 95 > using winflex???? > I can fax fine through windoze 3.11 but for windows 95 I can only send a one > page fax (with text only). Otherwise, when I try to fax it it will fax it > but on the receiving end instead of your postscript file printing it says > > This job requires morm memory than is available in thi printer. > try one or more of the following, and then print again: > In the postscript dialog box, click optimize for portability > In the device oprions dialog box , make sure the Available printer mem is > accurate. > reduce the number of fonts in the documnet > print the document in parts... I haven't run into this myself yet, but I would guess this item from gnu.ghostsript.bug is relevant: |From: ghost@aladdin.COM (L. Peter Deutsch) |Newsgroups: gnu.ghostscript.bug |Subject: Re: Not enough virtual memory? |Date: 3 Sep 1995 21:09:14 -0400 |Message-ID:|References: <42ddf5$k00@vixen.cso.uiuc.edu> | |> Looking at the Postscript code (generated by Word 6 for Windows), the |> Postscript seems to be querying the Postscript device for the amount |> of memory it has and then printing the message if there is not |> enough. | |This is a not uncommon "feature" of bad PostScript code put out by |applications that don't understand PostScript printing. | |The easiest way to work around it is to patch a definition of vmstatus into |gs_init.ps so that it always returns some huge amount of unused memory. For |example: | | /vmstatus { vmstatus 2000000 add } bind odef | |Of course, if you are trying to preview or print on a small MS-DOS PC, it |may legitimately run out of memory. Les Mikesell les@mcs.com
On Mon, 19 Aug 1996, Adrian Sherriff wrote: > > I have tried to use winflex under windows 95 but I am having trouble > getting a print. > > All I seem to get is that my printer does not have enough memory. > > Can you advise which is the printer driver to use I seem to remember > something about either QMS or HP. > > I would be gratefull if you could offer any advice 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. #!/bin/sh sed '/^\/VM?/,/ VM?/d' $1 > outp Good Luck Alex