Path: utzoo!utgpu!watserv1!watmath!att!linac!uwm.edu!rpi!julius.cs.uiuc.edu!apple!agate!ucbvax!CSG.UWATERLOO.CA!kevin From: kevin@CSG.UWATERLOO.CA (Kevin Kreutzweiser) Newsgroups: comp.binaries.ibm.pc.d Subject: BOOTDMOD.ZIP disk boot record utility uploaded to SIMTEL20 Message-ID: <1472.w8sdz@WSMR-SIMTEL20.ARMY.MIL> Date: 26 Nov 90 02:35:08 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 41 I have uploaded to SIMTEL20: pd1: BOOTDMOD.ZIP Modifies disk BOOT record and cluster size Brief information from documentation: Summary: ======= Allows modification of following disk(ette) parameters: - sectors per cluster - number of root directory entries Purpose ======= BOOTDMOD is meant to optimize disk space for special situations. Examples ======== FORMAT does not allow a free choice of clustersize and number of root-directory entries, while there are situations where other than the default value is desirable, for example: - A large number of relatively small files might cause waste of a considerable amount of disk space. An example of this is a bulletin board program OPUS: every message is a DOS file, of which there may be thousands present. If average messagesize is 1 KB, while the clustersize will generally be 2 KB (4 sectors of 512 bytes), then half of the diskspace will be unused. With BOOTDMOD a 1 KB cluster (2 sectors) can be created, or even a 1 sector cluster, resulting in much better disk utilisation. - When a strict directory structure is maintained, and with very few root-directory entries, the non-used directory entries might be freed for data-storage. In these cases BOOTDMOD may be applied after FORMAT to modify a disk or diskette to obtain a better utilisation. -- Internet: kevin@csg.uwaterloo.ca Fidonet: SYSOP, 1:221/172 (The Atlantis Automotive Bulletin Board) Gateway: Kevin.Kreutzweiser@f172.n221.z1.fidonet.org Data: (519) 748-9081 | Kitchener, Ontario, Canada