Actually Rune the source code now come with Redmon so using that as a base to understand how to write a port monitor is the best solution I think. But are you saying that its best to work with the WDK SDK? also RedMon redirects the job to a program, that program is GhostScript in this circumstance, it also means I need to edit the RedMon Port Monitor to redirect the output to a server, effectively uploading the job. Either that or maybe play about with GhostScript to save to a default location then trigger an application to do the upload for me. RegardsSam > Date: Wed, 7 Apr 2010 11:13:36 +0200 > Subject: [WinPrnDev] Re: Creating a Printer Driver > From: jjflash@xxxxxxxxx > To: winprndev@xxxxxxxxxxxxx > > On Wed, Apr 7, 2010 at 11:04 AM, Sam Elamin <hussam_88@xxxxxxxxxxx> wrote: > > After rereading your email its clear to me that either I have to learn how > > to write me own RedMon port to work with my own GhostScript program to > > produce a PDF of any jobs printed to it (convert to PDF on Client Side) > > OR > > Print to postscript and write my own Port monitor to upload the PostScript > > (The spool file i believe ) File up to the server and do the conversion > > The common theme seems to be that you need control of the port monitor. > > RedMon, last time I checked (two years ago), did not come with a > 64-bit version, and there was no source AFAICT. > > I think that if you write a decent port monitor that gets the print > job dispatched to where you want it, you've covered 80-90% of the > functionality needed. > > The SDK comes with a couple of port monitors that you can dissect and adapt. > > -- > Rune > --- > Questions? First check the UndocPrint pages at > http://www.undocprint.org/winspool > > To unsubscribe, visit the List Server page at > //www.freelists.org/list/winprndev _________________________________________________________________ http://clk.atdmt.com/UKM/go/195013117/direct/01/ We want to hear all your funny, exciting and crazy Hotmail stories. Tell us now