#Upload problems
9 messages in this thread
Dear Sysop:
I seem to be having serious amounts of difficulty uploading to your data
libraries, DL11 to be exact. To answer your first question, yes I have
successfully upload several files to Compuserve with no problems, with the same
software, and when your system was under even greater load. Also before and
after my numerous tries I have successfully uploaded to a local BBS. I'm using
xmodem with crc-16 error detection, at 300 baud. What happens is that your
system sends me a capital c which starts me sending, so far so good. After I
send the first block there is no response from your system, I can tell by
watching my modem lights. Your system is supposed to send me an ack or nack
character after I send the full block. After 30 seconds of nothing my xmodem
aborts and I have no choice but to hang up, because the system doesn't realize
that there is a problem. I really don't like to hangup on your system, but it
won't let me regain control.
Ed
Ed,
I'm not sure what's going on, there is no difference in the software
for DL 11 vs any other DL….in fact, the DL # is the equivalent to a
subdirectory on your drive….there's nothing special about any specific DL so
if you can upload to one DL, you can upload to any of them with the exception
of if we run out of room in a DL…but in that case, you get the "full message"
before you even start the upload.
Since you say you've uploaded ok in the past, I'll presume you haven't
changed any of that…and the settings were correct to start off with.
Are you by any chance using AHOST? If so, when it locks, try hitting
the Left-Amiga-N key, see if there is a system requester behind the screen
(which is where they pop up with AHOST).
Also, you shouldn't see the capital C (it's the CRC handshake
character)so it may be you are telling your terminal program to start the
upload too late…althou I doubt it since it does send the first block anyway.
Lastly, try uploading a short file (any file) to any of the DL's, see
if that goes ok. In the description, and keywords, just use TEST UPLOAD, that
way, we won't make the file public…at least that may narrow the trouble down
to a specific file that won't upload or a general problem.
Don
Don,
Thanks for getting back to me. I went ahead and tried DL11 again with no luck,
and then I tried DL1, and still no luck. The reason I see the capital c is
because it takes a little while to get set up so I miss the first one, which
cause it to display to my screen. I usually make it by the second capital c.
Your system sends three capital c before giving up on crc, and going to 8 bit
checksum. At that point my xmodem routine sends the block of data. While this
is happening I look at the receive and transmit lights on my modem, and I can
see the transmit light flickering as the xmodem routine sends the characters.
At no time do I ever see the receive light flicker for the response character
from your system. In the past when I have done this, I can easily see the
response character from your system. So it's not a matter of my program
locking up it's a matter of it never sees an ack or nack response, and
therefore it keeps on waiting, until it times out after 30 seconds and aborts.
It's as if your system is locking up. Also I have no problems uploading to one
of the local BBS, and I haven't modified my terminal since the last five
uploads that I did to DL11, which were printer drivers. Those uploads were
perfect, a little slow but perfect. Maybe I'm wrong but it sure sounds like
something is not right with your system. Thanks.
Ed
Ed,
If something is wrong on this end, I sure can't duplicate it using CRC
xmodem.
Ed,
Uploads work fine…we've had a few from other members and I tried a
short one…no problem at all using Xmodem.
Did you try to upload a different file? The particular file you are
trying upload may have a unique sequence of characters in it that is causing
either your modem or your terminal program to quit sending early. If CIS
doesn't receive the full block (including header and checksum)…it will wait
for up to 1 minute before it errors out.
I know you've said you have uploaded this file to other BBS's with no
problem…but I'd really like to see what happens if you try to upload any
other file using Xmodem…again, just note in the description that it's a TEST
UPLOAD and we'll not make the file public, we'll just erase it.
Don
Don,
Thanks for your patients. I have found the problem, and it's not me and it's
not CIS. Normally I access CIS through the local Tymnet node, so just out of
desperation I made a long distance call to El Paso Texas and used the CIS node
there. The upload worked just fine, and I did try using Tymnet right before I
tried the CIS node and still had no luck, so it appears to be a problem with
Tymnet. Now I didn't have any problems talking to CIS through the Tymnet node,
so this brings up a real big question in my mind. When I'm doing an xmodem
transfer, is the transfer between me and CIS or between me and the node. I was
always under the impression that it was between me and CIS. After having this
problem it sounds like it's between me and the node. If it is between me and
CIS then it should have worked, because I wasn't having trouble talking to CIS,
and CIS wasn't having any troubles talking to me through the Tymnet node. I
never saw any strange or missing characters. It sounds like it's between me and
the node, and the node's xmodem routine is messed up. Thanks for your help.
While I'm on the subject of Tymnet, do the daytime rates being gone forever
also apply to Tymnet or is that strictly CIS?. Also when the charges are
suspended during uploads does that also apply to Tymnet or is that strictly
CIS?
Ed
Ed,
The Xmodem part of the transfer is between your terminal program and CIS. A
node knows nothing about it the protocol, and simply passes data between you
and the host. One possible source of the problem could be that for whatever
reason (hardware problem in the node?) the node may be passing only 7 bits.
This would explain being able to talk to CIS (all ASCII characters are 7 bits),
yet it would hose up a protocol transfer, which needs 8 bits.
I'm not sure, but I think that local communication charges are always in
place. They are an expense inurred by CIS and are merely passed on to you. If I
am wromng about this, Steve or Don will undoubtedly jump in with a correction.
Regards, Larry.
Ed,
As Larry stated, the transfer is between you and CIS, Tymnet is merely
another connection in the circuit. There are methods for setting Tymnet for 7
or 8 bit service…but I haven't used it in a few years and that could easily
have changed. Leave a message to FEEDBACK about your difficulites. Make sure
you are quite specific about the problem and your use of Tymnet.
The only charges that CIS has any control over are their own charges,
they have no control over Tymnet charges. When CIS changes it's rates, or
gives free uploads, that means free of CIS charges…but any other connect
charges (such as Tymnet) still apply.
Don