Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!mms00786
From: mms00786@uxa.cso.uiuc.edu
Newsgroups: comp.sys.ibm.pc
Subject: Re: File concatenation using Microsoft
Message-ID: <46500106@uxa.cso.uiuc.edu>
Date: 11 Jun 90 13:29:00 GMT
References: <4891@druco.ATT.COM>
Lines: 15
Nf-ID: #R:druco.ATT.COM:4891:uxa.cso.uiuc.edu:46500106:000:799
Nf-From: uxa.cso.uiuc.edu!mms00786    Jun 11 08:29:00 1990


If you don't mind machine dependent code, what do you think of the following:
   Find the entry for file A in the dir area. The entry, I believe, consists
   of the name + some junk + number of the first allocated cluster. Then, the
   byte corresponding to that cluster in the dir area has the number of the
   next cluster and so on, just like a linked list. So if you can traverse
   the entire linked list for file A, then make its last cluster byte point
   to the first cluster byte of file B, you will have concatenated the two.
   You will have to take care and delete file B, or else someone will run
   chkdsk and ... wamoose. This should be much faster, and I think you might
   be able to pull it off using bios calls, so at least your code should run
   on all PC's (sure...)

Milan
.