Hi there. Attached to this mail is my replacement for the pbm to gif converter that is in the pbm package. I wrote it because the pbm to gif converter in the pbm package manages to use an incredible 10MB or more (!) in converting a 500K raw file created with g3topbm to gif. That reduces my system to a quivering heap of thrashing harddisks for 20 minutes or so, which makes that program next to useless. (I tried to use it to automatically convert incoming faxes to gif. But that made my system unable to answer calls while incoming faxes was converted.) So I wrote a converter which is much faster. The main reason it's faster is that it works on the stream directly, not using much more than around 20K of ram. It's designed as a filter to deal with P4 pbm's as g3topbm writes them. So you say "g3topbm file.pbm | pbm2gif >file.gif". It uses no external code or libs and is compact. It's my first C program, took 3 very long days to write and I'm still cross-eyed from debugging by trying to count bits in the bitstream... :) Anyway, I would really be honoured if you would include this in your *wonderfull* mgetty package. I think there is some need for it since the standard pbmtogif program is so poor in handeling large resultion monochrome pics and since pbm is such an obscure format for mac, dos-pc and amiga owners. I'm running a Linux system but I think the code is portable. It may break when the order of the bytes in an int changes. I'm not sure about that. The program checks if it's input is pbm data, but it will happily write bogus gif-data given erroneous pbm data. I'm waving all rights to the source, you can just include it under the "free-but-not-sell" license you are using. -=- Sys-adm, Redleaf - E-mail and USEnet News -=-