TERM2.0 and quickb
13 messages in this thread
HAS anyone gotten them TERM 2.0 program to work with quickb protocol? -dan
Daniel,
I use term / quick B all the time. What kind of problem are you
having?
Gary, Could you tell me step by step what you do to set up quickb
downloads? Does term2.0 start the download automatically or do you have to
tell it to start the download? etc. thx much!! -dan
Daniel,
Check the following :
Transfer menu – xprquickb.library is selected
Transfer options – auto-activate transfers is "checked"
As far as setting up a download I locate the file I want, type DOW
filename, Compuserve prompts for the filename I want to use, I type in the
name I want the file to have on my system and press return. The file
transfer status box comes up and the file transfers automatically to my
computer. Works every time.
gary, I have tried all that I found it that the download status window will
only come up automatically if I run 8 N 1 settings before transfer. However
the system yesterday kept timing out CIS give me an error at one point ?to
many Nak? I did get the xprquickb library to work with Ncomm however, but
looks like TERM2.0 presently has more features that I like. Are you running
TERM2.0? or a later version? Regards,dan
Gary, just tried it again even using the 68000 still no go just sits there
getting timeout errors is the author on cis? looks like a program with
great promise if I could just get it to work What serial settings are you
using? What equipment are you running it on? -dan
Daniel,
I am running TERM 1.9C on an Amiga 1000 with Rejuvenator, WorkBench
2.04, 1 meg CHIP / 2 meg FAST RAM. My serial settings are 2400 baud 8/n/1 ,
strip 7th bit, xon/xoff full duplex. I don't think the author is on CSERVE,
I believe he is European. One thing to try is to check the protocol options
for quick-b, maybe there is a problem in that area. Its worth working on
TERM, its great when properly configured. One other idea – are your
settings on CSERVE set to use quick-b? You may want to take a look at them
again. Good luck!
I tried it two nights ago and got a locked up system for my troubles. I
hate it when that happens. ZModem works very well. Those are the only two
protocols I've tried with Term 2.0. Term is a neat telecomm program
though.
Now if only JRComm 2.0 will be as good. Jack finally updated his
bulletins on the progress of the upgrade. He estimates several more weeks
(In Sha Allah!){God willing!} before it's ready for beta testing. I hate
it when upgrades all are due out about the same time, especially if they
cost me money!
Rodger
– via Whap!
Have you had any experince in writing script/command files for Term 2.0??
Since I connect to most BBSs through PC Pursuit, I like to automate things
as much as possible. I have not been able to get Term 2.0 to send the host
computer a string containing a space character. The script is an Arexx
file, so I tried double quotes ("), single quotes ('), and a combination of
both. So far, all I've gotten sent to the host are the characters upto the
space char. Any help would be appreciated.
Versia
Sorry,
I've only just started using TERM 2.0! I haven't even printed the
manual yet!
Rodger
– via Whap!
Is Term 2.0 available on CServe? I have been using Term 1.9g. Are there
any significant improvements?
Bill
– via Whap!
Bill,
I'm not sure if Term 2.0 is available here on CServe. I downloaded
it from The Portal. There are two archive files, Term20_International_1.zom
and Term20_International_2.zom. T2-1 contains the program and docs, while
T2-2 contains the source code. The ".zom" extention indicates these files
are compressed in the "ZOOM" format, I believe this format was created by
the author of Term 2.0 (although I could be wrong), therefore you will also
need the "Zoom???.lzh" (I can't remebmer the exact name of the file) to
decompress the files. I have never used "Term" before, so I am unable to
discuss any improvements, but if you've had any experinence writing "Term"
script files, please let me know.
Versia
I had problems with Term and QuickB too… but now I set my profile to NONE
for parity and come into the net at 8N1 instead of 7E1… works well… I
think the problem is in the XPR which is only an alpha version… Its when
the protocol tries to change speeds from 7e1 to 8n1 automatically…