--------------- FIDO MESSAGE AREA==> TOPIC: 248 QMODEM USER Ref: EEQ00001 Date: 10/20/97 From: DAN MORGAN Time: 07:54pm \/To: RICH LONG (Read 0 times) Subj: packet RL>How do I disassemble the 720kb packet so that I can read it with OLX? Try to unzip the .QWk with PKUNZIP. Rename the .qwk to have .zip extension before unziping. Then use a editor or viewer to read it. --- GEcho/32 1.20/Pro * Origin: The File Exchange 410-744-1102 Catonsville MD (1:261/3090) --------------- FIDO MESSAGE AREA==> TOPIC: 248 QMODEM USER Ref: EER00000 Date: 10/09/97 From: KARL SPRINGER Time: 11:15pm \/To: STEPHEN MAYBA (Read 0 times) Subj: Stupid Local Echo SM> If anyone is an expert on Q-Modem, I could use some help. > I've managed to get Local Echo stuck on, and I don't know how > to turn it off. Sounds like your Duplex setting is wrong. For the DOS programs, Qmodem TD and QMPro, toggles between Half and Full Duplex. Each entry in the dialing directory has a Duplex setting. Karl karl.springer@tsbbs.com ... And now a report from our modem... NO CARRIER --- PCBoard (R) v15.3/10 * Origin: Fidonet * West Los Angeles BBS * 310-559-5333 (1:102/635) --------------- FIDO MESSAGE AREA==> TOPIC: 248 QMODEM USER Ref: EER00001 Date: 10/21/97 From: GREG EASTHOM Time: 12:51am \/To: RICH LONG (Read 0 times) Subj: packet RICH LONG asked: RL>How do I disassemble the 720kb packet so that I can read it with OLX? DAN MORGAN answered: DM> Try to unzip the .QWk with PKUNZIP. Rename the .qwk to have .zip DM>extension before unziping. The .zip extension isn't needed, but you should unzip in an empty directory, so you can see exactly what files come out. PKUNZIP -t for a basic integrity check of the zipfile. OLX will want to unzip it while it's running, so this procedure is for you to see if the files are all there & that they all extract properly. DM>Then use a editor or viewer to read it. That could be a little confusing, though, as the MESSAGES.DAT file stores all messages end-to-end, no normal linefeeds or carriage returns. My 90k .QWK (234k MESSAGES) has 3000 lines @ 80 chars, 230 lines @ 1022. Your 720k packet will have a !huge! MESSAGES.DAT file! Once unzipped, what do you see?... CONTROL.DAT has a list of conferences scanned, + other info. ???.NDX files contain coded pointers to the beginning of each message. MESSAGES.DAT has all the messages, as stated, end-to-end. It's arranged in 128-byte chunks, the first chunk of each message showing how many chunks there are for this message. BLT-x.y, DOOR.ID, NEWFILES.DAT, etc......... info files. Assuming everything worked OK before now, you haven't made any changes to OLX's setup, you're not D/Ling a BlueWave packet or something else, and your COMM program isn't acting up (watch for D/L errors), you might try re-installing OLX &/or your COMM prog, just in case something got corrupted. Re-install the unzipping program too. Better safe than sorry. Or do what I'm doing (just for fun of course)... find QWKLAY13.ZIP & use the info to write your own SLMR/OLX imitation QWK reader using Qbasic. OODLES of fun (yeah right), but I'm learning a lot more about QB! No, Mr. Moderator, this doesn't really concern Qmodem, so I'll stop now. * SLMR 2.1a * And this is the machine that goes PING! --- Maximus 3.01 * Origin: The BandMaster, Vancouver, B.C., Canada (1:153/7715) --------------- FIDO MESSAGE AREA==> TOPIC: 248 QMODEM USER Ref: EEX00000 Date: 10/27/97 From: ECHO MODERATOR Time: 12:04am \/To: ALL (Read 0 times) Subj: Monthly Echo Rules Announcement QMODEM_USER Echo RULES QMODEM_USER is a product support echo open to all for the discussion, chat, assistance, etc. of the excellent terminal program QMODEM. Posting a message in this echo will be understood by the Moderator to be a declaration of your intent to abide by these and any other rules that may, of necessity, be formulated. Repeated, willful and/or flagrant violations of the rules of QMODEM_USERS will result in a request to the offender's echomail supplier to cut their access to this echo. 1. The topics of this conference should be related to Qmodem and/or and utilities related to Qmodem, including but not limited to external protocols usable with Qmodem. Any messages not on-topic will be considered annoying. 2. Challenge the ISSUE, not the message poster. Foul language belongs on the street, not here. Foul or harsh language will not be tolerated. If you don't like what someone has to say for personal reasons, send them a reply using netmail - not echomail. 3. Use of handles and or aliases is not allowed. Those people who are ogged on to bbs's using an alias should post their real names prominently in he body of each message they post. 4. Discussion of software piracy, including ways to 'register' unregistered shareware will not be tolerated. 5. Advertising for commercial ventures, even though Shareware related, will not be tolerated. Use either a local conference which permits such material, or use Fidonet Matrix mail, where only you pay for it. NOTE: An author's announcement of a Shareware program will not be considered a commercial advertisement. 6. There will be no usage of any high ASCII characters, BBS colour control codes, or PGP 'signatures'. Standard signatures are requested to be only one line, but may NOT exceed two lines at the most. 7. There shall be no bashing of hardware, hardware manufacturers, software programs, software authors or any other individuals. If you have a roblem with a program, company or piece of equipment and want to discuss it in n effort to get some help, fine, but let's not tear something down unless you can offer constructive suggestions for building it back up. 8. This conference MAY NOT be gated to the BIX echomail system, GroupMail or to any other network's echomail system WITHOUT permission of the Moderator. This is not to say it cannot be done, however the moderator must know where the echomail is going, and who the gateways are. essages in this conference should conform with the FTSC (FidoNet Technical Standards Committee) format and must contain a tear and origin line. The tear line may not be longer than 35 characters including the "-" chars. The origin line must fit on one 80 character wide CRT including the " # Origin: " text. Eight-bit ASCII is not allowed in this conference. All characters in displayed message data (text/header) must be in the range 32 to 126, which rules out control characters. The exception to this rule is if you need to show someone a translation table that contains ight-bit ASCII. 9. Treat others as you wish to be treated yourself. Please keep the amount f quoted text down to the bare essentials. Do not quote SEEN-BY and/or " # Origin: " information unless it is ABSOLUTELY necessary. One of the biggest costs with distributed mail conferences is the use and MISuse of the quote feature. Please keep "Thank you" and/or "This is a test" messages in NETMAIL, where they belong. People are paying plenty of oney to ship this conference around and if we can keep unnecessary overhead down, we'll all be happier. 10. The use of an anonymous remailer to avoid being responsible to follow any of the echo rules is grounds for an immediate feed cut, without warning of any kind. 11. There is only one Moderator, me! If you feel someone has broken the ules please NETMAIL the Moderator and don't take it upon yourself to admonish anyone. Let the Moderator moderate! Leave the moderating to ME. If you want to moderate, become a moderator first. 12. Messages from the Moderator concerning enforcement of the rules are not considered off-topic, however, neither are they topics for general discussion by anyone other than the Moderator and the person being addressed. i.e., if the Moderator deems it necessary to write a person in the echo who is in violation of the rules, it is not a sign that the topic is a free for all and everyone can jump in. Discussion should remain between the Moderator and the person being addressed only! (Just a further clarification of "Let the Moderator Moderate!) I work on a "three strikes you're out" basis. * First a public warning. * Second a netmail warning. * Third time and you are asked to leave the conference. If you do not comply with a request to leave the conference, or if a sysop does not comply with the moderator's request to disallow a user from access to the conference, distribution of the echo can and will be cut to that node. Excommunication from the echo shall be for a minimum of 15 days cooling off period for first offense, 30-60 days minimum for a second offense (Moderator's option) and permanently should you be cut a third time. The SysOp of each board carrying this echo is granted the right to Edit or Kill messages which, in their opinion, are inappropriate and unacceptable n their system. Exception to this rule is the killing or editing of any messages received prior to feeding them to linked systems. This is NOT permitted. Please use common sense when interpreting this rule and, if in doubt, netmail queries will be promptly answered. However should you do o, I'd appreciate netmail explaining which message and why you felt it should be killed on your system. That's it, except that if someone comes up with a new and improved way to aggravate people, I reserve the right to make a rule to fit the occasion. Bob Seaborn Moderator QMODEM_USER Fidonet 1:140/12 Internet bob@nwstar.com --- RoboEcho v 3.0 (reg) * Origin: Further North (306) 956-3383 (1:140/12) --------------- FIDO MESSAGE AREA==> TOPIC: 248 QMODEM USER Ref: EEX00001 Date: 10/25/97 From: RICH LONG Time: 01:38pm \/To: DAN MORGAN (Read 0 times) Subj: PACKET DM>RL>How do I disassemble the 720kb packet so that I can read it with OLX? DM> Try to unzip the .QWk with PKUNZIP. Rename the .qwk to have .zip DM>extension before unziping. Then use a editor or viewer to read it. Thanks Dan. Did that. Came up with a huge 1.9 meg file. As soon as I can figure out how to make ###.NDX files, I'll have it readable. RL --- QMPro 1.51 If I learned from mistakes, I'd be a genius! --- FLAME v1.1 * Origin: Pacifier Online Data Service (1:105/101) --------------- FIDO MESSAGE AREA==> TOPIC: 248 QMODEM USER Ref: EEX00002 Date: 10/25/97 From: RICH LONG Time: 01:38pm \/To: GREG EASTHOM (Read 0 times) Subj: PACKET Greg Easthom replied thus: GE>RICH LONG asked: GE>RL>How do I disassemble the 720kb packet so that I can read it with OLX? GE>DAN MORGAN answered: GE>DM> Try to unzip the .QWk with PKUNZIP. Rename the .qwk to have .zip GE>DM>extension before unziping. GE>The .zip extension isn't needed, but you should unzip in an empty GE>directory, so you can see exactly what files come out. GE>PKUNZIP -t for a basic integrity check of the zipfile. GE>OLX will want to unzip it while it's running, so this procedure is for GE>you to see if the files are all there & that they all extract properly. GE>DM>Then use a editor or viewer to read it. GE>That could be a little confusing, though, as the MESSAGES.DAT file GE>stores all messages end-to-end, no normal linefeeds or carriage returns. GE>My 90k .QWK (234k MESSAGES) has 3000 lines @ 80 chars, 230 lines @ 1022. GE>Your 720k packet will have a !huge! MESSAGES.DAT file! Hi Greg. Boy you got that right. 1.9 meg. Unzipped it to a separate directory, and surprise, surprise. Word7 handled it, but I still want to be able to read what is there using OLX. GE>Once unzipped, what do you see?... Uh, the monitor? I'm missing the ###.NDX files. GE>CONTROL.DAT has a list of conferences scanned, + other info. GE>???.NDX files contain coded pointers to the beginning of each message. GE>MESSAGES.DAT has all the messages, as stated, end-to-end. GE> It's arranged in 128-byte chunks, the first chunk of each GE> message showing how many chunks there are for this message. GE>BLT-x.y, DOOR.ID, NEWFILES.DAT, etc......... info files. GE>Assuming everything worked OK before now, you haven't made any changes GE>to OLX's setup, you're not D/Ling a BlueWave packet or something else, GE>and your COMM program isn't acting up (watch for D/L errors), you might GE>try re-installing OLX &/or your COMM prog, just in case something got GE>corrupted. Re-install the unzipping program too. Better safe than sorry. This was a fluke as far as I can tell. The board I call is a RBBS system, with a QWK frontdoor that adds seenby's and message id to every message. Besides, my modem's error correcting. GE>Or do what I'm doing (just for fun of course)... find QWKLAY13.ZIP & use GE>the info to write your own SLMR/OLX imitation QWK reader using Qbasic. GE>OODLES of fun (yeah right), but I'm learning a lot more about QB! For Now to eternity: - : return Actually, what I need is some way to write the ndx stuff. As soon as I can figure it out, the rest should be smiple. GE>No, Mr. Moderator, this doesn't really concern Qmodem, so I'll stop now. GE> * SLMR 2.1a * And this is the machine that goes PING! Thanks again. RL --- QMPro 1.51 If I learned from mistakes, I'd be a genius! --- FLAME v1.1 * Origin: Pacifier Online Data Service (1:105/101) --------------- FIDO MESSAGE AREA==> TOPIC: 248 QMODEM USER Ref: EEZ00000 Date: 10/28/97 From: GREG EASTHOM Time: 09:48pm \/To: RICH LONG (Read 0 times) Subj: Packet RL>Word7 handled it, but I still want to be able to read what is RL>there using OLX. RL>GE>Once unzipped, what do you see?... RL>Uh, the monitor? RL>I'm missing the ###.NDX files. That's very strange. I took a QWK packet and deleted everything from inside it except CONTROL.DAT and MESSAGES.DAT. SLMR 2.1a and OLX 2.1 Test Drive both unzipped the QWK's 2 files, and began: "Scanning messages: Rebuilding index files: ....". Shelled to DOS & found those rebuilt NDX files in the "work" directory. Maybe the RBBS door isn't 100% QWK compatible, and is not storing the correct info in the 128 byte header of each message? RL>Actually, what I need is some way to write the ndx stuff. As soon as I RL>can figure it out, the rest should be smiple. Message header arrangement: (Have fun) Startbyte Length 1 1 Message status flag (unsigned character) 2 7 Message number (in ASCII) 9 8 Date (mm-dd-yy, in ASCII) 17 5 Time (24 hour hh:mm, in ASCII) 22 25 To (uppercase, left justified) 47 25 From (uppercase, left justified) 72 25 Subject of message (mixed case) 97 12 Password (space filled) 109 8 Reference message number (ASCII) 117 6 Num of 128-byte blocks in msg, incl header (ASCII) 123 1 Flag (ASCII 225 = active; 226 = to be killed) 124 2 Conference number (unsigned word) 126 2 Logical msg # in the current packet (unsigned word) 128 1 '*' = network tag-line present; ' '= there isn't one * SLMR 2.1a * And this is the machine that goes PING! --- Maximus 3.01 * Origin: The BandMaster, Vancouver, B.C., Canada (1:153/7715) --------------- FIDO MESSAGE AREA==> TOPIC: 248 QMODEM USER Ref: EF300000 Date: 10/29/97 From: DANIEL GELINAS Time: 10:52am \/To: ALL (Read 0 times) Subj: Qmodem 4.60 Hi !! I have try to use QModem with a Telnet session in OS/2, i'm using SIO and VModem but when i try to use a BBS VIA Telnet, it's very slow, i have a BBS with Telnet Session and all work very fine.. What is the configuration in the Qmodem 4.60 DOS for using this !! Great thank's Daniel Gelinas BBS Telnet://ShawiniganQc.ml.org ... RAM = Rarely Adequate Memory --- Blue Wave v2.11 [NR] * Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000) --------------- FIDO MESSAGE AREA==> TOPIC: 248 QMODEM USER Ref: EFC00000 Date: 10/29/97 From: KARL SPRINGER Time: 06:58am \/To: RICH LONG (Read 0 times) Subj: PACKET RL> * QMPro 1.51 * RL> How do I disassemble the 720kb packet so that I can read it > with OLX? The *internal* zip unpacker function of QMPro 1.51 won't unzip mail packets zipped with PKZIP 2.04g. There are at least two options to handle these packets: 1) Configure QMPro to use an *external* unpacker, PKUNZIP 2.04g. 2) Upgrade your setup to QMPro 1.53 where the *internal* unpacker supports packets zipped with PKZIP 2.04g. RL> As soon as I can figure out how to make ###.NDX files, I'll > have it readable. QMPro does not require ###.NDX files. Karl karl.springer@tsbbs.com ... Problem: Too much HD space. Solution: Save all your QWK packets. --- PCBoard (R) v15.3/10 * Origin: Fidonet * West Los Angeles BBS * 310-559-5333 (1:102/635) --------------- FIDO MESSAGE AREA==> TOPIC: 248 QMODEM USER Ref: EFD00000 Date: 11/08/97 From: ARMANDO SILVA Time: 09:09am \/To: ALL (Read 0 times) Subj: Latest Version Does anyone know what's the latest version of QModem ?? The one I have is 5.01. --- * Origin: The Software (1:387/601.3)