Buchan Milne wrote:

This isn't required. Being a little creative, I put together a slick
(and simple) way to do this.



Sure, but your's doens't make it any easier (in terms of distributing it).



Not sure what you mean, unless you are refering to the licensing (see next comment).


I am using WHFC (Windows HylaFAX client). This accepts postscript
input, and talks directly to the HylaFAX server. Using the Generic
(Windows) Postscript driver (downloaded from Adobe's website).



Which is proprietary software BTW ...



WHFC is GPL. From their website (http://www.uli-eckhardt.de/whfc/):


WHFC is a client for the network fax server HylaFAX 4.0/4.1 <http://www.hylafax.org> under Windows 95/98 and Windows NT/2000. It's now available under the GNU Public license.

However, (and I haven't looked), although its free to download, I doubt the Adobe postscript driver is GPL (or other acceptable public) license.

Install & configure WHFC first, then install the Generic Postscript
driver. You need to set the port in the postscript driver to use WHFC
port - and after that, like magic anything you print from windows (using
the postscript driver), goes to WHFC and is sent as a fax.



If you could set up cover pages and stuff, this could be quite cool, and
we could compete with win2k3 (which has a complete fax service solution).



You can setup the cover pages (I just haven't gotten that far yet). I have been working the connection side of things first (make sure I can receive & send faxes from windows).


Now, would WHFC warrant being packaged with MDK (as an addon / utility
maybe) extending HylaFAX services to Windows client desktops? Hmm,
Interesting issue - packaging windows utilities that interact with an
MDK server... Where do you draw the line?



Exactly the issue at hand, but remember it can really only be done for
totally free software.



Yea, I know. WHFC fits that classification (GPL) so now if someone could dig-up a GPL windows (postscript) print driver, it could all be packaged as a fax solution. (But what would you call it? As its not Linux software, how would it fit into the distro? Any ideas?)



Thanks,


S



Reply via email to