CompuServe Thread

#Term 4.3

3 messages in this thread
#192376From: Carson TylerApr 13, 1995 1:48 PM
Robert, PMFJI 2 — Caught this thread and wanted to see if maybe you or some of the other learned bretheren could maybe help me with a slightly different problem I'm having with Term4.3. Simply put, I can't get the upload or download to trigger most of the time. I can dial and log onto a BBS just fine. But then, when I get to the point either to U/L or D/L, the Binary requester pops up, I select the file, click it, and nothing happens. The Transfer window opens, but the transfer doesn't trigger, and no data is displayed. The only way out is to re-boot, since the top menu is locked out in this condition and none of the Stop Transfer buttons will work. For info, I have an A2000 030, always select Zmodem, have 8N1, RTS/CTS on, and ANSI VT-220. I also use a Supra V.32bis 14.4. There's a host of other settings possible, as you know, and I can't remember what they all are at the moment. Suffice it to say that just about everything is set to default configuration. Zmodem is selected on the master settings menu as my default transfer lib. My phonebook settings are also individually set. The main thing is that everything was working fine until the transfer problem sprang up one day. I have sent EMAIL to Olsen Barthel, but sadly, his reply was somewhat less than helpful. I know that the program is not receiving or sending the transfer trigger, what I want to know is why or why not. If it's a simple setting thing, I would think that's fixable. Olsen said I ought to try changing my TTY settings, but I haven't a clue how you go about doing that or what I ought to change. It must be something local in the computer that's cropped up someplace, either within the program itself or something that's gone awry with my OS. The last few things I've done to the computer were adding a MegaChip and a DKB 2632 w/ 8 megs RAM, which required altering the WB:startup sequence slightly. Any helpful ideas for a fix would be *very* welcome. CST
#192469From: Joachim SondermannApr 14, 1995 6:14 AM
It might be not related – but there could be a file "zmodem" in ENVARC: (and ENV: also) with some settings you did for ZModem previously. I had trouble due to that fact before. You could try to delete those files and set your parameters anew. Joachim Sondermann-Bieker on Amiga AutoPilot 1.80 from Cologne, Germany
#192533From: Carson TylerApr 14, 1995 8:19 PM
Joachim, You're right, there was a file called "zmodem" burried in both RAM:ENV and in SYS:ENV-ARCHIVE. I deleted them both, and will let you know what happens next time I try to UL or DL something. Thanks! C.Tyler