Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!isgate!krafla!einari
From: einari@rhi.hi.is (Einar Indridason)
Newsgroups: comp.os.msdos.programmer
Subject: Re: minor problem with COPY command
Message-ID: <2546@krafla.rhi.hi.is>
Date: 15 Dec 90 23:17:08 GMT
References: <31600012@hpcvra.cv.hp.com.CV.HP.COM> <valley.661107643@gsbsun> <10758@jpl-devvax.JPL.NASA.GOV>
Reply-To: einari@rhi.hi.is (Einar Indridason)
Organization: University of Iceland (RHI)
Lines: 21

In article <10758@jpl-devvax.JPL.NASA.GOV> brad@huey.Jpl.Nasa.GOV writes:
>In article <valley.661107643@gsbsun>, valley@uchicago (Doug Dougherty) writes:
>There was a blurb in the back of a recent PC Magazine about this.  The problem is
>that COPY is running in ASCII mode in this case.  Normally copy runs in binary mode,
>but when it sees something like
>	COPY JUNK.* TEMPFILE
>it assumes (due to the *) that you are trying to append multiple text files (e.g.,
>JUNK.TXT, JUNK.DOC, etc.) into a single output file and switches to ASCII mode.
>I believe that what you have to do in this case is explicitly specify the /B
>switch to get it to run in binary mode:
>	COPY /B JUNK.* TEMPFILE

Has anyone patched command.com to *stay* in binary mode *all* the time?

(Solution:  Get *NIX :-)

--
Internet:    einari@rhi.hi.is        |   "Just give me my command line and drag
UUCP:    ..!mcsun!isgate!rhi!einari  |   the GUIs to the waste basket!!!!"

General Surgeons warning:  Masking the 8th bit can seriously damage your brain!!