RE: flexfax: Hylafax future

[Robert Colquhoun <rjc@trump.net.au>]

Hello
The way i was thinking of doing it is:

Use whfc's transport part to connect to the server
Write some code around pscript.dll & pscrptui.dll - the basic windows
postscript driver that the laserwriter and HP laserjets use.

ie from Word you would print to Hylafax printer which would convert the
document to postscript using pscript.dll and prompt for the number then use
whfc's code to connect to the fax server and also for the queue/status
information

The problems that come up straight away are:
	definition of pscript.dll(apparently the DDK includes the source code)
	limitations on pscript.dll(can i get it to do what i want)
	queue/status might be more than a little difficult
If i cannot get that to work the g3 driver sounds like a good idea - the
server will need to do less processing of the incoming fax

Theres a fair bit of work in the above (mild understatement)

Gary there's no chance at getting the source code for the g3 driver is there?

Robert

At 11:28 16/09/97 +0800, Gary Ng (Winclient) wrote:
>
>> 2) A good windows client - i like hfaxd but i was thinking a proper
>> network
>> printer driver, to write the code you also need to be subscribed to
>> MSDN
>> for the Microsoft DDK, i will ask my boss( this  costs A$1000 p.a.)
>> 
>I can contribute a printer driver for hylafax (binary only). This is in
>a sense a
>printer driver that can produce 1D g3 stream. If someone can write the
>transport
>part (to pickup the stream, convert it to whatever format hylafax needed
>and
>deliver that to the server), there will be a print-to-fax driver for
>hylafax. It is available
>in 3.1, 95, NT 3.51 and NT 4.0.
>