Hello :)
I was trying to upload a QWK *.rep packet and the BBS
disconnected me after the transfer. Not sure what the
problem is; could be archive decompression, tossing, or protocol/connection related.
When you have time could you inspect your log for
further details ? I would be interested in what's causing the problem.
I'm currently using Bluewave/386 as my OLR.
I can upload and toss Bluewave *.rep packets fine to my
own BBS (Maximus/DOS v3.01) via mTelnet's Zmodem.
But I get the same disconnection problem on COMM Port
OS/2 (Bob Juge's BBS) after uploading a QWK *.rep
packet. So not sure if it's an OS/2 issue as I don't
know of any other DOS Maximus BBS's to call.
Here's the screen output on my end:
Maximus supports any .QWK format reader.
Press "?" for more information.
READER (59 mins):
Tag area Download new msgs Upload replies
Protocol default
Archiver default Restrict date Main menu
Goodbye (log off)
?help
Select: u
Please begin uploading TOPHAT2.REP now.
Mode: Zmodem
Begin sending now, or hit <Ctrl-X> several times to cancel.
0100000027fed4
The BBS has ended for unknown reasons.
Please wait while an attempt is made to record this bad news...
Thank you.
Connection Closed to tophat.darktech.org/23 @ 1:28 pm
Thanks !
Thank you.
Connection Closed to tophat.darktech.org/23 @ 1:28 pm
Thanks !
Interesting.....
Based on what I am seeing, I am guessing that the
upload completes, and then something "breaks" trying to
unpack the uploaded .rep packet. My guess is the
archive method you are using is too new for what I run
on the BBS.... What are you using to compress the
file? What version of the program? What flags are you
using?
It probably works on your BBS setup because you have
matching compression and decompression routines.....
It probably works on your BBS setup because you have
matching compression and decompression routines.....
I was going to scrutinise your Compress.Cfg for clues
but I don't think it's compression related because it
appears that any upload / file transfer whatsoever from
me to your BBS is breaking.
I've attempted some test uploads: "lanius.zip" and
"bitsbaud.mec" which both failed. I think lanius.zip
was created with WinZip 8.0, and bitsbaud.mec is just a
flat MECCA file -- the aim was to test if your upload
process would yield different results between
compressed and uncompressed file uploads (which it
didn't).
Are you currently able to upload files via that Zmodem
protocol to your own BBS ? and is it the Maximus
internal Zmodem ? -- the Maximus internal Zmodem is
what I use for my BBS and uploads with mTelnet work
fine.
I'm using pkzip to upload *.REP packets to Vertrauen
(Rob Swindell's BBS ( telnet://vert.synchro.net))
successfully. He's runnin his stuff on W2k+3 ...
So I don't know what the problem is. I can only suspect
it's OS/2. I seem to be having lots of probs with
uploading stuff to OS/2, albeit thus far observed only
from Bob Juge's and your BBS.
Anyway, I've provided below some details with what I've
attempted to do for each of your available compression options.
I'm using PkPak from 1988 and PkZip (1993) so I don't
think they're too "new" for your ARC 5.xx and Info-zip.
+-----------------+
| Your ARC Option |
+-----------------+
CMD: "C:\tmp\pkpak -a tophat2.rep *.msg"
Version: PKPAK FAST! Archive Create/Update
Utility Version 3.61
08-02-88 Copyright (c) 1986-1988 PKWARE Inc.
All Rights Reserved.
PKPAK/h for help
+----------------------+
| Your Info-zip Option |
+----------------------+
CMD: "C:\tmp\pkzip tophat2.rep *.msg"
Version: PKZIP (R) FAST! Create/Update Utility
Version 2.04g 02-01-93
Copr. 1989-1993 PKWARE Inc. All Rights
Reserved. Shareware Version
PKZIP Reg. U.S. Pat. and Tm. Off. Patent No. 5,051,745
+-----------------+
| Your LHA Option |
+-----------------+
CMD: "C:\tmp\lha a tophat2.rep *.msg"
Version: LHA version 2.13
Copyright (c) Haruyasu Yoshizaki, 1988-91
=== <<< A High-Performance File-Compression Program >>>
======== 07/20/91 ===
If you've got time perhaps you can try uploading files to yourself using mTelnet or other client with Zmodem.
Apart from that, I think we've reached the end of the line with this.
Based on your additional comments, that is probably where the problem is.
I was also thinking modem not telnet session. How are
you opening the telnet session? Are you using 8 bit
clear protocol? If you are using a 7bit protocol or
one that escapes certain character sequences, the
upload will fail on those escape sequences. I believe
the VMODEM support under Ray Gwin's SIO that we use on
OS/2 boxes requires an 8 bit clean telnet session. A
lot of telnet sessions will assume 7 bit and/or an
escaped character set by default.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,036 |
Nodes: | 15 (0 / 15) |
Uptime: | 214:41:47 |
Calls: | 733 |
Calls today: | 7 |
Files: | 95,167 |
D/L today: |
10,370 files (492M bytes) |
Messages: | 298,587 |