#Access1.3a
18 messages in this thread
Keith, I just trued tried several times to download using QB with Access1.3a
with no success. After the prompts come from CIS nothing happens. I assume
you aren't responing to CIS's DLE B, or whatever. Using 1.29 right after
these failed attempts (hangs), it worked flawlessly. Seems like you
introduced a QB bug while fixing an Xmodem bug. 🙂
GreG
You stick in the + in the phone directory entry?
Did you read the docs about the new method for doing QB protocol? There is
nothing wrong with the QB protocol in 1.3A. I have downloaded several files
from CIS using QB in 1.3A with no problems.
Art Lewis
Art, yes I have. I am stumped. I used 1.30 with the '+' in the name of the
phone book directory. When I tried the same phone config, '+' and all, QB
was not enabled. I had to manually turn in on. Go figure? I did jump the
gun in my message, I have DL'd using QB with 1.3A succesfully. Sorry for any
confusion my message may have led to.
GreG
Greg-
Did you leave a space between the name and the +? If you did "COMPUSERVE+"
it might not work. (Just an idea).
Art
Art, mine is CIS+ and it works just fine. Marlene
Art, yes. My entry was "Compuserve +". It worked in 1.30, but 1.3A needs it
to be "Compuserve+". All is working now.
GreG
Ah, (oops)… I see that you _did_ read the docs, sorry! 🙂 I haven't had
any problems with it, and can't think of what it might be… hmmm…
lesse'… ok, (I'll have to look but..) the
B+ _might_ only get set correctly if you use the "auto-dial" feature (where
is
that source code <madly flipping through disks> ). Lemme' know if you have
further problems.
Keith
Keith, I seemed to ave solved the problem by putting no spaces between the
service name and the '+'. Before, for 1.30 I had it as 'Compuserve +', and
it worked. Now it seems that 1.3A needs it to be 'Compuserve+'.
GreG
GreG,
Really? hmmm… I thought I had it so that it would work either way…
anyway, I'm glad it's working for you now, thanks.
Keith
Mine is set to Compuserve +2400 and works – kinda. Just to confuse the
issue, either bell is fine with me (or even no bell).
Ok, well… that kinda' keeps it at a tie but adds a new entry/choice "no
bell at all" hmmm… actually I was considering doing an "AAAOOOOOGGGAA"
horn.
decisions, decisions… Keith
Keith,
Why not stick with DisplayBeep() and supply SetBeep and a few sound files
with it?
-larry
Love the AAAOOOOOGGGAAHHH!! sound. (you forgot the H's at the end)
I'd like a fart please. <snicker>
Karl
<ahem> well go right ahead. 🙂
GreG,
I see that a few people beat me to the answer to your B+ problems… But
I
can't resist… "READ THE DOCS!" <grin>
Keith