This method is from the days of DOS and is not driver-aware. You are blindly submitting a document into a print queue. Along with what David said, you may also encounter print issues between ASCII and Binary file types. The COPY command does however have a /b (binary mode) switch.
-- Espi On Tue, Sep 3, 2013 at 12:32 PM, Michael Leone <[email protected]> wrote: > I got asked a question from one of my developers, and I am unsure of > the answers. > > Suppose you add a printer to your workstation (by doing START, > \\server\printername, apparently). > You then send a print job to that printer from a command prompt by > doing "COPY filename \\server\printername". > > Does the print job use the printer driver you just installed? (I think not) > The job *does* seem to get into the print spool queue of the server, > because jobs come out, and they seem properly formatted (that's the > server using the print driver, I think) > > Don't ask me why they send print jobs that way. The guy I was speaking > to didn't know either. But I'm trying to understand what is happening > when they do it this way. > > Anybody shed any light on what the sequence and process is when you > send a print job to a printer by using COPY in a command prompt? (as > opposed to using API calls, I guess) > > Thanks > > >
