CompuServe Thread

#486 in a 386sx bb

5 messages in this thread
#72267From: John G. AtaOct 3, 1992 1:52 PM
This simply is NOT true as stated: The 2.04 version of addbuffers does NOT have those two failings. It does not allocate buffers in chip memory and it allows you to delete the buffers once they are allocated. Please refer the the 2.04 documentation for a complete description. Maybe there are other reasons to run BlitzDisk, but for 2.04 users, it isn't for the reasons you've stated. John G. Ata Sterling, VA
#72344From: Steven D. KapplinOct 3, 1992 11:25 PM
John, I'll refresh my acquaintance with the new docs, and if I was wrong, I stand corrected.
#72345From: Steven D. KapplinOct 3, 1992 11:32 PM
John, Well, you are definitely right about not using CHIP. But I cannot tell how you get rid of assigned buffers. The command template doesn't have a parameter for removing the buffers and resetting buffers for a given drive to 0 doesn't return any memory to the free pool. Perhaps this is undocumented. It isn't in my 2.04 docs. The template is just <drive> nbuffs.
#72414From: Craig GlaserOct 4, 1992 3:09 PM
Simply Specify a negative number of buffers, and that number will be removed. I.E. ADDBUFFERS DH1: -10 will remove 10 buffers from DH1: (This is only under 2.04+ of course.) Craig Glaser
#72434From: Steven D. KapplinOct 4, 1992 8:05 PM
Craig, Thank you for clearing that up.