
                  Bulletin Boards under OS/2       (Fidonet)

                 Saturday, 04-Dec-1999 to Friday, 10-Dec-1999

+----------------------------------------------------------------------------+

From: Steve Hayes                                       03-Dec-99 01:23:19
  To: All                                               04-Dec-99 10:24:08
Subj: Comms programs for Windows & OS/2

Perhaps one reason for the decline in BBSing is the difficulty in finding
decent comms programs for Windows or OS/2.

The computer I usually use to call BBSs died recently - it was a 386SX-16
running MS DOS 6.22

I installed an OLMR on the machine where I run my BBS, which runs OS/2 Warp
4, and tried to call using Halite, which comes with OS/2, and also Winramp, a
Windows 3.1 program, which I ran in WinOS/2.

Both worked a couple of times, and then bombed.

Winramp reported General Protection Fault errors.

Eventually the number of failed calls was getting too expensive, since they
were failing 5 out of 6 times, and getting one call for the price of 6 was
uneconomical, so I installed Telix 3.22 for DOS and ran it under a DOS
Window.


My question is: are there ANY decent and reliable comms programs for OS/2 or
Windows out there that one can recommend to users and potential users?

It seems that most people have some form of Windows these days, and in the
absence of a decent comms program it is simply too much hassle to call a BBS.

If there is a place like a Web site where one can download a comms program, I
would like to put a link to it from my BBS Web page, which I use to encourage
people to use BBSs -

http://www.geocities.com/hayesstw/bbsweb.htm

Keep well,

Steve Hayes

E-mail: methodius@bigfoot.com
        shayes@dunelm.org.uk
   Web: http://www.geocities.com/hayesstw/

 * Evaluation copy of Silver Xpress. Day # 6

--- WtrGate v0.93 Unreg
 # Origin: Unisa Editorial, Pretoria, Gauteng, RSA 27-12-429-8641 (5:7106/20)
 * Origin: The TALKING HUB * Alexandria, VA * (703) 549-5612 (1:109/11)

+----------------------------------------------------------------------------+

From: Stewart Buckingham                                05-Dec-99 04:45:06
  To: Steve Hayes                                       04-Dec-99 20:37:02
Subj: Comms programs for Windows & OS/2

Hi Steve,

> My question is: are there ANY decent and reliable comms programs for OS/2 or
> Windows out there that one can recommend to users and potential users?

Yep. ZOC for OS/2 & Windows. It also doubles as a telnet client. Lots of
people appear to use QMODEM for Windows.as well.

Stu/2

--- BBBS/2 v3.50 Flag-A
 * Origin: The Chili Channel * OS/2 - Java - Linux * chilies.com * (6:751/222)
120

+----------------------------------------------------------------------------+

From: Tobias Ernst                                      02-Dec-99 21:42:03
  To: All                                               05-Dec-99 01:56:05
Subj: A: Y2KTOOLS Version 4 released!

Hello everybody!

Y2KTOOLS package Release 4 (containing Pktdate 1.3) is now available. See
below for what's new in this version. The upgrade is definitely worth it. -
This package has two purposes:

First, PKTDATE is a PKT preprocessing utility. It can automatically process a
PKT file and fix year 2000 problems in that file and so keep the net running
even if individual nodes continue to use faulty software in the year 2000.

Second, the package contains an explantatory text that instructs users on how
they can check if their system is year 2000 ready, and tools for displaying
dates in various storage formats that aid them in this process.

You can obtain the file:

Y2KTOOL4.ZIP  366811  02 Dec 1999  Fidonet Year 2000 Utilities Release 4

- via fidonet f'req at 2:2476/418
- via WWW: http://www.physcip.uni-stuttgart.de/tobi/projects.html#y2ktools
- soon at ftp.juge.com or f'req at 1:106/2000
- soon at all GFD and BBSNet sites

This version has the following major changes, plus some minor ones:
  - PKTDATE has been enhanced by the feature to leave backup copies of the
    original unmodified files behind (renamed to .Y2K) if it fixes anything,
    so that you can afterwards see what exactly was wrong in the file (as
    an additional information to what is already in the log file).
  - PKTDATE with -q switch can now work with .QQQ files (Fastecho TempOut)
  - Bugs in PKTDATE have been fixed.
  - A JAM date display tool has been added.
  - German Documentation has been added.

I wish to thank everybody who contributed bugreports, ideas, documentation,
and code to this new version of the package. You really helped me.

I wrote Y2ktools and Pktdate because I realised that it is impossible to get
every single Point and Node to completely fix their software until 1/1/2000.
There are still many in the "silent masses" that do not even know that they
have to fix something, and this could cause a lot of trouble. So the concept
of Pktdate is that rather than trying to get every single user to fix his
software, one should rather install a "bug reversing utility" at central
cites, like Hubs, Hosts, Echomail backbone systems, and I/O gates, that can
undo the bugs that the individual users might introduce into the Net. If all
Hubs or Hosts would do this, Fidonet would be able to function correctly in
the year 2000 even if a lot of individual Nodes do not fix their problems. Or
at least, problems of individual Nodes would not be able to cause problems at
other sites (which currently cannot be guaranteed, unless you are using
Pktdate).

Consequently, I want to encourage everybody who has downlinks, be it a Node,
Hub or Host, to install the Pktdate utility, and if you are a NC or RC, I
think you should encourage the important persons in your net to do so. To make 
this easy for everybody, Y2KTOOLS are "Public Domain" free software, the
package contains ready-made binaries for OS/2, DOS, Linux, Windows 95/NT and
Amiga, plus the source code which is plain ANSI-C and should compile just
about everywhere.

Any feedback on this is highly welcome. Places where this is on-topic that I
do monitor include the 2000 Fidonet echo, the FIDO_UTIL and FTSC_PUBLIC
conferences, in Germany FIDO2000.GER and FIDOSOFT.GER, and of course my
Netmail folder :-).

Kind Regards,
Tobias.

--- MPost/2 v1.2
 * Origin: Badnerland BBS, Stuttgart (2:2476/418)
120
2320/38

+----------------------------------------------------------------------------+

From: Tobias Ernst                                      28-Nov-99 16:24:11
  To: All                                               05-Dec-99 01:56:05
Subj: A: The Husky Nodelist Utilities 1.0

Hello everybody!

I hereby announce a new portable, free and Open Source Fidonet utility for
Linux, Unix, OS/2, Windows and DOS, this time a set of nodelist maintainance
utilties: The Husky Nodelist Utilties 1.0.

You can obtain the file:

NLTOOL10.ZIP  432448     NLTOOLS 1.0 --- The Husky Nodelist Tools
                         ========================================
			 Written 1999 by Tobias Ernst. A tool kit
                         for keeping  your  nodelists  up to date
                         (nlupdate automatically finds the latest
                         diff files  using an Y2K-safe algorithm,
                         unpacks them,  and  applies them  to the
                         nodelist),  and a FIDOUSER.LST compiler.
                         The FIDOUSER.LST  file  can be used  for
                         sysop/node  number lookup  in Msged  and
                         other mail editors.  The tools are fido-
                         config integrated,  but can also be used
                         standalone. Public Domain software  with
                         source code,  compiles on a lot of  Unix
                         systems. Binaries for  OS/2, Windows 95/
                         98/NT, DOS(DPMI) and Linux are included.

from the following sites:

- via fidonet f'req at 2:2476/418
- via WWW: http://www.physcip.uni-stuttgart.de/tobi/projects.html#nltools
- soon at ftp.juge.com or f'req at 1:106/2000
- soon at all GFD and BBSNet sites

The archive contains a set of nodelist management utilities, in source code
and, if you got a full distribution, also with binaries for some common
operating systems.  The following functionality is provided:

- Compiling raw nodelists into a FIDOUSER.LST file, that can be used for
  nodelist lookup by sysop name, as supported by Msged and others.

- Keeping your raw nodelists up to date, i.E. logic is provided to find the
  nodediff files that apply to your current nodelist files, and a tool to
  apply nodediffs to nodelists.

- Easily readable Source code and tools for calulating nodelist CRC checksums
  and applying nodediff delta files. The source code is very portable and
  compiles on almost any Unix platforms as well as others.

This package does NOT presently include something like a V7 nodelist compiler.

A major advantage of these tools on Unix is that they have no case sensitivity 
problems. I.e. nodelist files and nodelist updates are found no matter if they 
are in lower, capital, or MiXeD case.

Feedback is very welcome, e.g. in this area, or in the international Husky
support area FIDOSOFT.HUSKY.

Kind Regards,
Tobias.

--- MPost/2 v1.2
 * Origin: Badnerland BBS, Stuttgart (2:2476/418)
120
2320/38

+----------------------------------------------------------------------------+

From: Jack Stein                                        01-Dec-99 18:37:00
  To: All                                               05-Dec-99 10:34:09
Subj: BBS2 Babble November Part 1 of 1

                               Part  1                               
                    The OS/2 REXX BabbloMeter Report                    
       Monthly Babble received in OS2BBS at Jack's Free Lunch BBS       
                           November, 1999                            

                    16 users babbled 22 Messages                     

Outbound Babble        %     K   Avg K | Incoming Babble         %
=======================================|============================
  3 STEPHEN MONTEITH 13.6%    5k   1.6 |   7 ALL               31.8%
  2 STEVEN THOMPSON   9.1%    2k   0.9 |   7 RODRIGO CESAR B   31.8%
  2 SEAN DENNIS       9.1%    4k   2.0 |   3 ALAN IANSON       13.6%
  2 RODRIGO CESAR BA  9.1%    2k   1.2 |   1 JEAN-MICHEL DOS    4.5%
  2 ALAN IANSON       9.1%    2k   1.2 |   1 NEIL WALKER        4.5%
  1 PETER KNAPPER     4.5%    2k   2.3 |   1 GORD HANNAH        4.5%
  1 RICH WONNEBERGER  4.5%    1k   1.1 |   1 TROY-WILLIAMS      4.5%
  1 MERCEDES PUZIO    4.5%    1k   1.5 |   1 FRANCOIS MASSON    4.5%
  1 RON MITCHELL      4.5%    1k   1.0 |  
  1 JEAN-MICHEL DOSS  4.5%    2k   1.8 |  
  1 JACK STEIN        4.5%    3k   2.5 |  
  1 FRANCOIS MASSONN  4.5%    1k   1.3 |  
  1 STEWART ARNETT    4.5%    1k   1.0 |  
  1 STEWART HONSBERG  4.5%    1k   1.0 |  
  1 TROY-WILLIAMS     4.5%    1k   1.2 |  
  1 BOB JUGE          4.5%    1k   1.4 |  

--- MakeMsg v2.1
 * Origin: Jack's Free Lunch 4OS2 USR16.8 Pgh Pa (412)492-0822 (1:129/171.0)
120

+----------------------------------------------------------------------------+

From: Ian Moote                                         05-Dec-99 10:30:00
  To: STEVE HAYES                                       05-Dec-99 13:33:05
Subj: Comms programs for Window

SH> Perhaps one reason for the decline in BBSing is the difficulty in
SH> finding decent comms programs for Windows or OS/2.
[...]
SH> My question is: are there ANY decent and reliable comms programs for
SH> OS/2 or Windows out there that one can recommend to users and
SH> potential users?

ZOC is supposed to be good. I don't use it, but a friend of mine did and 
liked it so much that he got the version for Windows 95 when he 
abandoned OS/2.

Telix also works under OS/2.

Take care and TTYL.

---
  Votez NON, NON, NON! au rfrendum de 1995!                        

--- AdeptXBBS v1.11y (FREEWare/2)
 * Origin: Moote Pointe (1:2424/140)
260/10

+----------------------------------------------------------------------------+

From: Alan Ianson                                       03-Dec-99 21:25:01
  To: Sean Dennis                                       05-Dec-99 13:33:05
Subj: Lord IGM's

 SD> Hmmm... I'd assume you have the - parameter set in SIO 
 SD> else you wouldn't be able to run DOS doors over the com 
 SD> handle... uhm... try running PMLM in a window while 
 SD> someone's online and using one of the faulty IGMs to 
 SD> see if everything is truly getting passed to the IGM 
 SD> correctly.  Unfortuatly, I don't use IGMs with my LORD 
 SD> setup, so this is kinda like a shot in the dark for me. 
 SD>  Any other ideas?

It took a bit of persistance but I got it figured out. I changed the drop file 
type to dorinfox.def and everything started working fine. That broke one of
the IGM's local and remote though, so I kept digging. I got a copy of a
door.sys from a telegard sysop who had it working and looked for differences.
Maximus's default door.sys lists the locked baud rate at "N" so I changed it
to 115200 and it's all working fine now. Kind of hard to figure out since I
have 20 other doors using door.sys and lord itself was working fine. But it's
all working fine now <big sigh of relief> :) Thanks for the reply..

 Ttyl :-),
         Al

--- Maximus 3.01
 * Origin: The Rusty MailBox - Vancouver, B.C. Canada (1:153/757)
911

+----------------------------------------------------------------------------+

From: Alan Ianson                                       28-Nov-99 14:45:08
  To: Stephen Monteith                                  05-Dec-99 13:33:05
Subj: Lord IGM's

 SM> What IGMs are you running?  I may be using them and can 
 SM> pass on my settings, or at least I may have an 
 SM> explaination.  I'm also running Max/2 3.01 and SIO 
 SM> 1.60D.  A sample of your SIO line in the config.sys may 
 SM> help too.

Hi Steve,

        I've changed things a bit here, I'm running Maximus under Win95, but I 
still have the same problem. I saw on the status line of one of the IGM's said 
it was in local mode when it should have been on com2. Where it gets the idea
it's in local mode I don't know. I had the comport set to read from drop file
before, I've changed it now for node 1 to com 2, so maybe that will fix it.
Have to wait and see when a user tries it.

        One of the IGM's I'm having problems with is LordNet 1.4N and I can't
remember the others now. Barak's House works fine though, and so does Marty's
Mercantile.

 Ttyl :-),
         Al

--- Maximus 3.01
 * Origin: The Rusty MailBox - Vancouver, B.C. Canada (1:153/757)
911

+----------------------------------------------------------------------------+

From: Alan Ianson                                       28-Nov-99 14:51:21
  To: Stephen Monteith                                  05-Dec-99 13:33:05
Subj: Lord IGM's

 AI> Your trying to flatter me, aren't you.. ;)

 SM> If he could only spell Asshole correctly though.  :)

I thought the same thing, but didn't want to confuse him.. :)

 Ttyl :-),
         Al

--- Maximus 3.01
 * Origin: The Rusty MailBox - Vancouver, B.C. Canada (1:153/757)
911

+----------------------------------------------------------------------------+

From: Bob Juge                                          05-Dec-99 11:32:01
  To: Steve Hayes                                       06-Dec-99 00:14:21
Subj: Comms programs for Windows & OS/2

Steve Hayes wrote in a message to All on Fri Dec 03 1999 at 01:23:

 SH> My question is: are there ANY decent and reliable comms programs
 SH> for OS/2 or Windows out there that one can recommend to users and
 SH> potential users? 

{COMMO} by Fred Brucker, although a DOS program, works exceptionally well
under both.  Available here as COMMO77.ZIP.

                                   - Bob
Internet  : bob@juge.com
Telnet, Vmodem, WWW or FTP to juge.com

--- timEd/2 1.10.y2k+
 * Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)
260/10

+----------------------------------------------------------------------------+

From: Kaare Olsen                                       05-Dec-99 20:19:27
  To: Steve Hayes                                       06-Dec-99 09:49:05
Subj: Comms programs for Windows & OS/2

Hi Steve,

Friday December 03 1999 01:23, Steve Hayes wrote to All:

 SH> My question is: are there ANY decent and reliable comms programs for
 SH> OS/2 or Windows out there that one can recommend to users and
 SH> potential users?

Zap-O-Comm (ZOC) is available for both OS/2 and Windows, and is the best
communications program I've come across.  It's shareware, about US$70 (a bit
too expensive, if you ask me).

ZOC can be downloaded from the authors' home page at http://www.emtec.com/ and 
registered online with BMT Micro (http://www.bmtmicro.com/).  Current version
is 3.13 for both platforms.

I'm sure there are several other decent and reliable communications programs
out there, but I rarely use that kind of programs these days...

Regards, Kaare - Team OS/2

--- GoldED/2 3.0.1
 * Origin: NightCall (2:237/10)
120

+----------------------------------------------------------------------------+

From: Dale A Cook                                       05-Dec-99 21:06:09
  To: Bob Juge                                          06-Dec-99 09:49:05
Subj: Comms programs for Windows & OS/2

 BJ> Steve Hayes wrote in a message to All on Fri Dec 03 1999 at 01:23:

 SH> My question is: are there ANY decent and reliable comms programs
 SH> for OS/2 or Windows out there that one can recommend to users and
 SH> potential users? 

 BJ> {COMMO} by Fred Brucker, although a DOS program, 
 BJ> works exceptionally well under both.  Available 
 BJ> here as COMMO77.ZIP.

        
           Please don't forget  Z.O.C.   !!!!!!

--- Maximus/2 3.01
 * Origin: Gargoyle's Place BBS (1:365/3253)
260/10

+----------------------------------------------------------------------------+

From: Francois Massonneau                               05-Dec-99 22:24:10
  To: Peter Knapper                                     07-Dec-99 00:48:00
Subj: nlmaint

Hello Peter!

Replying to a message of Peter Knapper to Francois Massonneau:

 FM>> As he said "the letter X is reserved for file request 
 FM>> capability,...." how can I make NLMAINT to accept the 
 FM>> new flags X2C and X2S.

 PK> You would have to use the FLAGS or UFLAGS files to allow them to be
 PK> included, however the person that processes the segment you output

I thought by reading the doc file that I *wasn't allowed* to add flags
beginning with the letter "X" in the FLAGS and/or UFLAGS files. Am I wrong ?
If I'm not wrong, how can I make NLMAINT to accept those flags.

 PK> That is because they are not USER flags and can only be approved for
 PK> use by your ZC, which means that if NLMAINT does not currently allow
 PK> them to be included, you need to define them in your FLAGS file.

Even if those flags _begin_ with the letter "X" ??

Bye, Francois!


Email: fmas@celtes.com
Web  : http://www.worldnet.net/~island/

---
 * Origin: Island's BBS, a Node in the Atlantic Ocean (2:326/2)
396/1

+----------------------------------------------------------------------------+

From: Peter Knapper                                     07-Dec-99 19:36:28
  To: Francois Massonneau                               07-Dec-99 05:58:03
Subj: nlmaint

Hi Francois,

 FM>> As he said "the letter X is reserved for file request 
 FM>> capability,...." how can I make NLMAINT to accept the 
 FM>> new flags X2C and X2S.

After reading your reply and going back to your first message, I now see what
you mean. You are correct, NLMAINT does totally block the use of flags that
start with the letters U (for obvious reasons) and G (reserved for Gateway
use), in either FLAG file. Note that in the UFLAGS file, you only need the
letters AFTER the U in the file itself, NLMAINT inserts U before the first U
flag included in an output segment.

There is also a qualified block on flags that start with X. Any manual X flag
you wish to define can only be 2 chars long, to allow continuation of the
existing use of the X flags for file request logic (XA, XB, XC, etc...) So
NLMAINT will not allow you to include flags that start with X (other than as
above). 

I am unsure where this restriction comes from, a quick check of the available
FTS files I have here provides no obvious clue. I also note that our Zone 3
Nodelist trailer has no mention of these flags. I wonder if the people who
decided to use the X2C, X2S flags in your Zone were aware of this potential
conflict.

Cheers........pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)
2320/38

+----------------------------------------------------------------------------+

From: Lee Aroner                                        06-Dec-99 09:37:01
  To: Steve Hayes                                       07-Dec-99 12:42:05
Subj: Comms programs for Windo

SH> Perhaps one reason for the decline in BBSing is the difficulty in finding
  > decent comms programs for Windows or OS/2.

   ZOC.

   (Zap O' Com)

   Excellent program and the Windows version is as stable as you can 
   expect anything running under Win to be...

                                       LRA


 -- SPEED 2.01 #2720: It was casual to the most obvious observer...

--- Maximus/2 3.01
 * Origin: Top Hat BBS (1:343/40)
120

+----------------------------------------------------------------------------+

From: Leonard Erickson                                  06-Dec-99 23:52:00
  To: Steve Hayes                                       07-Dec-99 19:44:14
Subj: Comms programs for Windows & OS/2

 -=> Quoting Steve Hayes to All <=-

 SH> My question is: are there ANY decent and reliable comms programs for
 SH> OS/2 or Windows out there that one can recommend to users and potential
 SH> users? 

Try FD 2.25. It *will* set up as a terminal program, and works rather
nicely as one.

k
--- Blue Wave/DOS v2.30
 * Origin: Shadowshack (1:105/51)

+----------------------------------------------------------------------------+

From: James Mckenzie                                    08-Dec-99 05:41:06
  To: Alan Ianson                                       10-Dec-99 06:58:06
Subj: Lord and Pascal "Run Time" Error

Hello Alan!

03 Dec 99 21:25, Alan Ianson wrote to Sean Dennis:

 SD>> Hmmm... I'd assume you have the - parameter set in SIO
 SD>> else you wouldn't be able to run DOS doors over the com
 SD>> handle... uhm... try running PMLM in a window while
 SD>> someone's online and using one of the faulty IGMs to
 SD>> see if everything is truly getting passed to the IGM
 SD>> correctly.  Unfortuatly, I don't use IGMs with my LORD
 SD>> setup, so this is kinda like a shot in the dark for me.
 SD>>  Any other ideas?

 AI> It took a bit of persistance but I got it figured out. I changed the
 AI> drop file type to dorinfox.def and everything started working fine.
 AI> That broke one of the IGM's local and remote though, so I kept
 AI> digging. I got a copy of a door.sys from a telegard sysop who had it
 AI> working and looked for differences. Maximus's default door.sys lists
 AI> the locked baud rate at "N" so I changed it to 115200 and it's all
 AI> working fine now. Kind of hard to figure out since I have 20 other
 AI> doors using door.sys and lord itself was working fine. But it's all
 AI> working fine now <big sigh of relief> :) Thanks for the reply..

However, I cannot run LORD here as I get the old Pascal "run time" error. 
What was the name of that "fix"?

James

... It's called Windows cuz it's a 'pane'
--- GoldED/2 3.0.1
 * Origin: Running Lora 2.40, OS/2 Native BBS Software! (1:15/64)
396/1

+----------------------------------------------------------------------------+

From: John Clarke                                       06-Dec-99 18:26:22
  To: All                                               10-Dec-99 06:58:06
Subj: Virus checker

Hello All,

NAI don't seem to be interested in the OS/2 McAfee virus checker.  I have sent 
3 emails asking about it and received nil replies.

What other OS/2 virus checkers are available?  I need to protect the operating 
system and check files imported via the net.

Regards ... John

Email: jclarke@zip.com.au

--- MsgedSQ/2 3.30
 * Origin: The Clearing House (3:713/730)
396/1

+----------------------------------------------------------------------------+

From: Wayne Steele                                      08-Dec-99 09:23:15
  To: All                                               10-Dec-99 06:58:06
Subj: SIO and Telnet nodes???

Hi All,

I have the following configuration for node coms 5-8 and was wondering
if they look alright???

(COM5,INTERNET:3E0,NONE:5,-) (COM6,INTERNET:2F0,NONE:5,-)
(COM7,INTERNET:2E0,NONE:5,-) (COM8,INTERNET:260,NONE:5,-)

If this is AOK what is the locked baudrate? Can I specify a locked
baudrate with the Internet command? I'd like to have 115200... As it
would make it alot easier with some doors that require a locked
baudrate...

Lata,
     Wayne
Internet: wsteele@ihug.com.au & welcome.to/BadNewsBBS   ICQ: 12489905

--- Ezycom V1.48g0 02fa001d
 * Origin: Bad News 4 Lines Computer Porn Kings (02)9625-5474 (3:713/690)
396/1

+----------------------------------------------------------------------------+

From: Steve Hayes                                       07-Dec-99 05:29:15
  To: Ian Moote                                         10-Dec-99 06:58:06
Subj: Re: Comms programs for Window

On 5 Dec 99 10:30am, Ian Moote wrote to STEVE HAYES:

 IM> ZOC is supposed to be good. I don't use it, but a friend of mine did and
 IM> liked it so much that he got the version for Windows 95 when he
 IM> abandoned OS/2.

Thanks very much -- I've seen a lot of people recommend it, so I'll try to
get hold of it.


 IM> Telix also works under OS/2.

I'm using Telix under a DOS Window in OS/2 to send this, and it works as well
as it did under straight MS-DOS.


Keep well

Steve Hayes

methodius@bigfoot.com

... BBSs on the Web: http://www.geocities.com/hayesstw/bbsweb.htm
 * Evaluation copy of Silver Xpress. Day # 10

--- WtrGate v0.93 Unreg
 # Origin: Unisa Editorial, Pretoria, Gauteng, RSA 27-12-429-8641 (5:7106/20)
 * Origin: The TALKING HUB * Alexandria, VA * (703) 549-5612 (1:109/11)

+----------------------------------------------------------------------------+

From: Steve Hayes                                       07-Dec-99 05:31:28
  To: Bob Juge                                          10-Dec-99 06:58:06
Subj: Re: Comms programs for Windows & OS/2

On 5 Dec 99 11:32am, Bob Juge wrote to Steve Hayes:

 SH>> My question is: are there ANY decent and reliable comms programs
 SH>> for OS/2 or Windows out there that one can recommend to users and
 SH>> potential users?

 BJ> {COMMO} by Fred Brucker, although a DOS program, works exceptionally
 BJ> well under both.  Available here as COMMO77.ZIP.

Thanks Bob.

I've found Telix works fine under OS/2 for me, though I haven't tried it
under Win98 yet.

But it sounds as though ZOC, which several have recommended, might be a
better bet for recommending to potential BBS users who use Win95/99/NT.


Keep well

Steve Hayes

methodius@bigfoot.com

... BBSs for genealogy: http://www.geocities.com/Athens/7783/bbs1.htm
 * Evaluation copy of Silver Xpress. Day # 10

--- WtrGate v0.93 Unreg
 # Origin: Unisa Editorial, Pretoria, Gauteng, RSA 27-12-429-8641 (5:7106/20)
 * Origin: The TALKING HUB * Alexandria, VA * (703) 549-5612 (1:109/11)

+----------------------------------------------------------------------------+

From: Dale A Cook                                       08-Dec-99 15:27:29
  To: John Clarke                                       10-Dec-99 06:58:06
Subj: Virus checker

 JC> Hello All,

 JC> NAI don't seem to be interested in the OS/2 McAfee 
 JC> virus checker.  I have sent 3 emails asking about 
 JC> it and received nil replies.

 JC> What other OS/2 virus checkers are available?  I 
 JC> need to protect the operating system and check 
 JC> files imported via the net.

 JC> Regards ... John

 JC> Email: jclarke@zip.com.au

      
     Ibm makes a good virus checker.  try a search using ibmav as keyword
 on snap.com..........
       
       

--- Maximus/2 3.01
 * Origin: Gargoyle's Place BBS (1:365/3253)
396/1

+----------------------------------------------------------------------------+

From: Alan Ianson                                       08-Dec-99 21:52:18
  To: James Mckenzie                                    10-Dec-99 06:58:06
Subj: Lord and Pascal "Run Time" Error

 JM> However, I cannot run LORD here as I get the old Pascal 
 JM> "run time" error.  What was the name of that "fix"?

There is a file about called TPPATCH.ZIP that fixed this problem on a friends
system. I don't think he used it on LORD, but it may work. It can be found I
believe on the MultiBoard FTP site (ftp.multiboard.com). I can't remember the
directory.. but the file is called rte200fx.zip there.

 Ttyl :-),
         Al

--- Maximus 3.01
 * Origin: The Rusty MailBox - Vancouver, B.C. Canada (1:153/757)
120

+----------------------------------------------------------------------------+

From: Francois Massonneau                               08-Dec-99 13:44:11
  To: Peter Knapper                                     10-Dec-99 06:58:06
Subj: nlmaint

Hello Peter!

Replying to a message of Peter Knapper to Francois Massonneau:

 PK> There is also a qualified block on flags that start with X. Any manual
 PK> X flag you wish to define can only be 2 chars long, to allow
 PK> continuation of the existing use of the X flags for file request
 PK> logic (XA, XB, XC, etc...) So NLMAINT will not allow you to include
 PK> flags that start with X (other than as above). 

I know the source code of NLMAINT has been released (I have it here) and I
hope someone will be able to take it and make the changes needed. NLMAINT Is a 
great OS/2 program.
This is part of a message David Nugent (the author of NLMAINT) sent me a while 
ago :
----------------------------------------
>Are you still supporting it ?
>If so, can I report a bug ?

No, and no. I'm no longer in FidoNet and have no interest in working on it
any further. This is why source code was released.

Regards,
David
----------------------------------------

 PK> I am unsure where this restriction comes from, a quick check of the
 PK> available FTS files I have here provides no obvious clue. I also note
 PK> that our Zone 3 Nodelist trailer has no mention of these flags. I
 PK> wonder if the people who decided to use the X2C, X2S flags in your
 PK> Zone were aware of this potential conflict.

These flags seem to be authorized worldwide. A check in the last fidonet
nodelist gives me that (I cut a part of it of course) :
;S  The following flags define modem capabilities supported:
;S
;S            Flag      Meaning
;S
;S            V22       ITU-T V22     1200 bps full duplex
;S            V29       ITU-T V29     9600 bps half duplex
;S            V32       ITU-T V32     9600 bps full duplex
;S            V32b      ITU-T V32bis 14400 bps full duplex
;S            V34       ITU-T V34    33600 bps full duplex
;S            V42       LAP-M error correction w/fallback to MNP 1-4
;S            V42b      LAP-M error correction w/fallback to MNP 1-5
;S            MNP       Microcom Networking Protocol error correction

/. a lot of stuff deleted ./

;S            VFC       Rockwell's V.Fast Class
;S            ZYX       Zyxel 16.8 Kbps (implies V.32Bis & V.42Bis)
;S            V90C      ITU-T V.90 modem Client. A modem having this
capability
;S                      can connect to a V90S-capable modem and potentially
;S                      achieve 56 kbit/s throughput in the direction server
to
;S                      client and normal V.34-type througput in the opposite
;S                      direction.
;S            V90S      ITU-T V.90 Server. A device having this capability
;S                      is mandatorily connected to the telephone network
using
;S                      a digital interface (probably ISDN) and can connect
with
;S                      any other V90-capable device.
;S                      V90S <-> V90S: symmetrical 64kb link can be
established.
;S                      V90S <-> V90C: see V90C user-flag
;S            X2C       US Robotics x2 client. A modem having this capability
;S                      can connect to an X2S-capable modem and potentially
;S                      achieve 56 kbit/s throughput in the direction X2S to
X2C
;S                      and normal V.34-type througput in the opposite
;S                      direction.
;S            X2S       US Robotics x2 server. A device having this capability
;S                      is mandatorily connected to the telephone network
using
;S                      a digital interface (probably ISDN) and can connect
;S                      either to another X2S-capable device or to an
;S                      X2C-capable device. In the former case, a symmetrical
;S                      64kbit/s link can be established. The latter case is
the
;S                      reverse of what is described under the X2C flag.
;S            Z19       Zyxel 19.2 Kbps (implies V.32Bis & V.42Bis & ZYX)
;S                      Can be used in combination with the V34-flag
indicating
;S                      V34 with ZyXEL-proprietary-protocol support


Bye, Francois!


Email: fmas@celtes.com
Web  : http://www.worldnet.net/~island/

---
 * Origin: Island's BBS, a Node in the Atlantic Ocean (2:326/2)
396/1

+----------------------------------------------------------------------------+

+============================================================================+
