![]() |
> > So if I use the client to send a 20 page MSWord document to the > > server, the server performs a transformation to tiff/fax format. Would > > you say the conversion would take 2-3 minutes? 5-10 minutes? more? > > with the 233 mhz machine? (I also presume that if the conversion > > process is preempted by a incoming fax, the outgoing service will > > resume and successfully complete after the incoming fax is received?). > Years ago I ran HylaFAX on a P-75 (yes, 75 MHz) laptop for a customer. > It was a bit slow, but faxing went fine, and I would be very surprised > if a 20-page document would have taken more than 2-3 minutes to prepare > before sending. Yep. I'd be primarily concerned about RAM. If the document contains complex figures like 3D pie charts with a color gradient or just lots of photo like images then ghostscript can get pretty big. If you go into swapping like crazy, especially on a really low end machine, you'll have problems. In this case it'll work until a user attempts to send something ridiculous; maybe you can use ulimits or something to just have the renderer konk out if it gets larger then a certain size... but hardware is cheap. I suppose it also depends on how intelligent/responsible your users are. Mine include people whose job title starts with a "C" and have less than four letters - they usually don't have any idea what they are doing. :) ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*