CompuServe Thread

#access!, cis-b

6 messages in this thread
#114651From: Bob AdamsMar 19, 1988 8:57 PM
The "quick cis-b" protocol downloading ain't so quick. Trying to download a 100K file using access 1.29 at 2400 baud, the first 50K or so zipped along at 16K/min. Then things slowed down to 2K/min (25secs per 1024 block — at 2400 baud!!!) What's happening? ALso, is there an abort command to kill the dowload? Bob Adams 75275,1102
#114652From: KEITH YOUNGMar 19, 1988 9:07 PM
Bob, Hmmm… interesting, I don't know of any reason that would cause things to slow down except for maybe line noise causing blocks to be reX$Nre-sent. (soory, a burst of line noise there <grrrr>) You can hit the ESC key to abort, but CIS does not always come back to the prompt and let you do anything else. (appears to be an inherent bug in the protocol ). Keith
#114659From: Bill EastburnMar 19, 1988 9:36 PM
The system will slow down as it becomes more loaded. Usually, this is noticable between about 9PM and midnight eastern time. Just too many people for CompuServe's aging hosts. <grin>
#114700From: KEITH YOUNGMar 20, 1988 1:18 AM
Ah… thanks Bill… that would explain it. 🙂 Keith
#114654From: Doug WingerMar 19, 1988 9:16 PM
Bob, I believe (and Keith will tell you for certain) that Access! buffers the download into ram for the first 64K block. Even that shouldn't create times like you're seeing! I think perhaps you got a lot of retries due to noise on your line. When the line is clear, QB is the zippiest protocol you can use here! Doug
#114792From: Bob AdamsMar 20, 1988 3:03 PM
If the problem were line noise, shouldn't access show an increasing NAK count for certain blocks? While the data rates are decreasing during my download, I access! isn't displaying an increasing NAK count. Bob Adams