Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!elroy.jpl.nasa.gov!decwrl!shelby!lindy!news
From: LC.YRS@forsythe.stanford.edu (Richard Stanton)
Newsgroups: comp.sys.ibm.pc
Subject: Re: 4DOS file concatenation problem -- WARNING!
Message-ID: <8705@lindy.Stanford.EDU>
Date: 28 Mar 90 01:04:54 GMT
Sender: news@lindy.Stanford.EDU (News Service)
Distribution: usa
Lines: 27

In article <2143@darkstar.ucsc.edu>,
mee@ucscb.UCSC.EDU (Kevin Kahl) writes:
>It seems that 4DOS version 3.0 has a new bug.  I wrote a device driver that
>is in two parts.  These are the commands that I used (in a batch file under
>4DOS v2.2) to concatenate the to files into one:
>
>        copy /b password.bin+password.txt password.sys
>
>The resulting file does not include everything!  "password.bin" is 859 bytes
>in length.  "password.txt" is 4000 bytes.  The resulting "password.sys" is
>only 4083 bytes, though.  Under 4DOS 2.2, the resulting length was 4859 (as
>it should be).  Upon further investigation, I found that the 84th byte in
>"password.bin" is a EOF character, but the "/b" directive should have
>caused 4DOS to ignore this.
>
I don't know if this solves the problem, but if you look at the 4DOS
help for the COPY command, it shows /A and /B being used AFTER at
least one file name. According to the description, these affect the
preceding filename and any succeeding filenames until the next /A or
/B flag. What happens if you try

copy password.bin+ /B password.txt password.sys

I agree that this is rather clumsy looking, even if it works.

Richard Stanton
pstanton@gsb-what.stanford.edu