CompuServe Thread

The number of blocks depends on the protocol you are using and the size of the file. To get the size of the file in bytes, look at the first line when you BRO on that file. It will contain a filename, a file type (usually "binary"), a date (which is when it was uploaded), a big number and a small number. The big number is the size of the file in bytes. (The small number is the number of times it was downloaded. You may not always see that one…) Now, once you have that number, you need to know how many bytes there are in a block for your protocol. For Compuserve B+ or Quick B protocols, which are the recommended ones to use, the block size is 1024 bytes. For XMODEM, to give another example, the block size is 128 bytes. (I do NOT recommend using XMODEM… <grin>) Divide block size into file size and there you'll have the number of blocks. –>Steve Bennett

Mark, If you mean storage blocks on your target disk, you'll come close enough by figuring 2 disk blocks per 1000 bytes of download file. On my hard disk, the file STITCH.LZH (57388 bytes) takes 115 blocks. On an 880K floppy, the same file takes 119 blocks. Hope this helps. 8) David

Mark, When you see the name of a program, it will be something like this: 11BARD.ARC/binary 21-Sep-87 107648 126 ^ name of the program to download ^ type – binary, ascii, or some others ^ date the program was uploaded to CIS ^length of the program in bytes ^ # of downloads Hope this helps. ……Betty