Xref: utzoo comp.sys.ibm.pc:46161 comp.sys.zenith:178
Path: utzoo!attcan!uunet!snorkelwacker!usc!srhqla!demott!kdq
From: kdq@demott.COM (Kevin D. Quitt)
Newsgroups: comp.sys.ibm.pc,comp.sys.zenith
Subject: Re: Why differences between PRINT and COPY?
Keywords: PRINT, COPY, binary files
Message-ID: <64@demott.COM>
Date: 10 Mar 90 18:10:37 GMT
References: <6182@blake.acs.washington.edu>
Reply-To: kdq@demott.COM (Kevin D. Quitt)
Followup-To: comp.sys.ibm.pc
Distribution: na
Organization: DeMott Electronics Co., Van Nuys CA
Lines: 20


    The real reason is that DOS is basically hosed.  All systems have
some EOF character for input from keyboards and/or serial lines.  DOS
thinks this is such a good idea, it uses the EOF on output too! (not to
disk).

    It's not that PRINT or COPY explicity check for EOF - when they send
the EOF, DOS closes the channel for them.  If you specify /B to COPY, it
uses IOCTL to make the channel a raw output channel. 

kdq
-- 

Kevin D. Quitt                          Manager, Software Development
DeMott Electronics Co.                  VOICE (818) 988-4975
14707 Keswick St.                       FAX   (818) 997-1190
Van Nuys, CA  91405-1266                MODEM (818) 997-4496 Telebit PEP last
34 12 N  118 27 W                       srhqla!demott!kdq   kdq@demott.com

        "Next time, Jack, write a God-damned memo!" - Jack Ryan