Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!news.funet.fi!tukki.jyu.fi!jyu.fi!otto From: otto@tukki.jyu.fi (Otto J. Makela) Newsgroups: comp.os.msdos.programmer Subject: Re: minor problem with COPY command Message-ID: Date: 13 Dec 90 17:55:49 GMT References: <31600012@hpcvra.cv.hp.com.CV.HP.COM> Sender: news@tukki.jyu.fi (News articles) Organization: Turing Police, Criminal AI section Lines: 14 In-Reply-To: everett@hpcvra.cv.hp.com.CV.HP.COM's message of 13 Dec 90 00:12:38 GMT In article <31600012@hpcvra.cv.hp.com.CV.HP.COM> everett@hpcvra.cv.hp.com.CV.HP.COM (Everett Kaser) writes: [description of problem, which boils down to the fact that JUNK.* are treated as ASCII, not binary in the command COPY JUNK.* TEMPFILE] This is a "feature" (n., bug or a quirk which has been documented). It stems from the exceedingly weird method of concatenating files which is supported by COPY (and alas, XCOPY), where you combine several files into the target file by specifying several filenames OR wildcard pattern(s) separated by pluses (+). -- /* * * Otto J. Makela * * * * * * * * * * * * * * * * * * */ /* Phone: +358 41 613 847, BBS: +358 41 211 562 (CCITT, Bell 24/12/300) */ /* Mail: Kauppakatu 1 B 18, SF-40100 Jyvaskyla, Finland, EUROPE */ /* * * Computers Rule 01001111 01001011 * * * * * * * * * * * * * * * * */