>> It certainly makes sense - but I never encountered this situation. Thanks for the clarification.
>You're quite welcome. Other pecularities you might encounter with DOS apps -- sometimes the printout doesn't occur until you exit the program (the exiting of the program triggers the end of the print job).
>Speaking of network printing... I recall once while I was at university when somehow the printer device was accidentally changed to be writable by any user (normally it's read-only for any user except for the print spooler daemon). Students started writing directly to the printer device (to bypass the print quota imposed when you enqueued printouts normally). Whenever more than one student started writing to the printer, the printout that resulted was all the data interleaved together.

Perfect. They finally learned why the spooler was introduced, and the learned it the best way :).