gtp@houem.UUCP (11/02/83)
I am looking for a cpm program that will change the "user" entry in the cpm file directory. What I want to do is be able to set up a work area (maybe user 0 or user 15) and be able to have files moved in and out of the work area without the overhead of physically copying them. I am not so concerned with copying one or two files, but am thinking in terms of entire user areas. I.e. change all files in user 3 to the chosen work area. Looking at the fcb block it seems that I should only have to change the first byte. Any information would be helpful. Also looking for any other disk utilities that might be useful. Thanks
SHahn@SUMEX-AIM.ARPA (11/10/83)
From: Sam Hahn <SHahn@SUMEX-AIM.ARPA> Re: fcb modification program. There's a public domain program (I forget whether it's in CP/MUG or SIG/M) called MAKEUSER that modifies the user number of selected files. As implemented, it does NOT look at user numbers of files before user-number- modification, but the source is (I think) included on the disk, so it should be an easy enough mod to include a filter on the input filespecs. The reason I'm unclear is that I don't have the original disk close at hand, since I just modified it, and keep only the .COM around nearby. Someone may be able to pick up on this reference before I get around to finding it myself. -- sam hahn [shahn@sumex-aim] -------
MMOON.ES@PARC-MAXC.ARPA (11/11/83)
DUPUSR2.ASM OR DUPUSR21.ASM are floating around on various RCP/Ms & will do what you want with a little extra effort. This program creates a *duplicate* directory entry in a comand-line specified user area. One must then go back and delete the file in the original user area if access to it from that user is not desired. This second delete must be followed by a <ctrl>-C to force a fresh read of the allocation vectors into memory. The sectors where the program or data reside have not, of course, been physically nulled by the erasure, but by marking them as deleted in *any* user area which has a directory entry for the particular file, you have caused an update of the in-memory allocation vector which will cause those sector bits in the bit mapped to toggle, thus marking these sectors as free to be written into, which they are not. The <ctrl>-C thus avoids a potential overwrite problem by renewing the allocation vector. I have been using DUPUSR21 for several months to very good effect under ZCPR2, using it also to move files into different user areas as well as making duplicate entries for the same file. The program documents the above mentioned side effect in the commented code. Also, it will accept wildcard file designations so an entire directory could be moved in this manner. Enjoy. MMoon.es