Hi Willi,
if PRINT is what I think it is, then:
This PRINT here only takes /1 /2 /3 as "/D:lpt1" etc equivalent options or a filename to print a file. Please use the free PRINTQ tool for "print file", "print /t" (clear queue incl current job), "print /c" (clear queue) and "print /p file" (add file to queue).
I would assume that the /1 /2 /3 or /D:lptX tell it which printer port to use and loads PRINT as a resident tool in the background. Later, "PRINTQ /P file.txt" adds a file to the queue and "PRINTQ /T" or "PRINTQ /C" remove things from the queue BEFORE they got printed. Things automatically vanish from the queue as soon as they have reached the printer. Or maybe it is PRINT instead of PRINTQ, you have to test. Either way, printer ports have pins for feedback from the printer, allowing it to tell your computer that the printer is busy and cannot receive data at the moment. So having a resident printer queue tool means that your apps can send content to the queue quickly and you can soon continue working with the app, while in the BACKGROUND, the queue tool keeps pumping queued data to your printer as fast as the printer wants to receive it, until the queue is empty again :-) If you have no printer connected, then nothing will say that it is ready to receive more data and your queue will just float around in RAM without ever getting printed to paper. Regards, Eric _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
