| |
ZL1ABS > NBF 29.05.07 14:44l 161 Lines 5972 Bytes #999 (0) @ WW
BID : 300095ZL1ABS
Read: OE7HNT GUEST DO5JAB
Subj: Re: NBF Packet Program
Path: DB0FHN<DB0FOR<DB0SIF<DB0MRW<OK0PKL<DB0GRL<SR6BBA<SR1BSZ<OK4PEN<PY1AYH<
F4BWT<F6KBI<F5GOV<DB0RES<ON0AR<ZL2BAU<ZL1AB
Sent: 070529/1223Z @:ZL1AB.#06.NZL.OC #:61021 [AUCKLAND] FBB7.00i $:300095ZL1AB
From: ZL1ABS@ZL1AB.#06.NZL.OC
To : NBF@WW
Hi Ray VK2TV,
Very good to hear that you have your bbs.txt file in NBF set up to connect
over your LAN now.
Below is a NBF features list I downloaded.
For my BBS.txt file I needed the following:
c zl2aqy.ath.cx:23 zl1abs mypassword v187f "guest"):
BBS
The first part connects to ZL2AQY port 23 over the internet. The second
part is my login name (callsign). The third part is my password to ZL2AQY
Xrouter.
The fourth part is the login prompt that Xrouter sends upon connection
(different to the callsign: prompt that NBF expects by default).
The fifth part is the password prompt (actually the last ten characters
only) ZL2AQY Xrouter sends after a login (callsign) has been received
(again different to what NBF expects by default, so NBF needs to be told
what the password prompt looks like).
The second line tells ZL2AQY to connect to the local F6FBB BBS (ZL1AB).
If you don't have a password from Eddie ZL2AQY you can only connect to his
Xrouter & no further. It does let you test NBF Telnet to do a test login.
If anyone wants to try a test login to ZL2AQY, you are welcome to do so.
Eddie says to put your callsign in place of "ZL1ABS" and to use a password
of "guest" (don't include the quote signs).
DX_CLU.txt is a lot simpler connection file for NBF to go to ZL2AQY DX
Cluster server:
c zl2aqy.ath.cx:9000
zl1abs
Put your own callsign in the second line to do a test connection to ZL2AQY
DX Cluster.
You will not be allowed to send DX Spots, but you will be able to receive
all you want. You can get registered with ZL2AQY for full DX Cluster
privilages.
73 de Michael ZL1ABS@ZL1AB.#06.NZL.OC
NBF - A Better Program for Packet RadioNBF - More detailed information
Why NBF?
My old packet program works just fine. Why change to NBF ?
Message list system. The little green man which examines message
headers
has been put inside the grey box. Feeding is not necessary.
Enable multitasking: NBF doesn't steal CPU time, but it takes care
it
always gets the few per cent required for smooth operation. You
won't
even notice the machine to slow down when NBF is operating in the
background.
Experience the amazing speed of your 9k6 TNC. NBF is not written
in
basic.
No stupid "only one this and that function at a time" limitations.
User interface fine tuned for convenient everyday use.
Absolutely no registration fee. Still fully functional.
List of the main features
Possibility for multiple connections in different windows plus a
monitoring window.
Advanced list system. Automatic downloading and sorting of message
titles by various criteria, search feature.
Compressed mail forwarding. Address book.
Automatic HTML-viewer (currently requires IE5)
Scandinavian characters work correctly, an important feature here
in
Finland
Automatic decoding of 7plus-files. Corrects shifted/missing
linefeeds
automatically! (the most common reason for corrupted
7plus-messages)
Remote commands
Autobin protocol for file transfer (doesn't crash at 1MB, as some
programs do, hi)
Optimized COM-port handling: real qso-speeds in excess of 850 cps
possible on 9k6 (limited by the radio connection, not the program)
Direct FlexNet, AGW and Winsock (telnet) support, in addition to
the
WA8DED hostmode.
Sound (incoming connections, //bell-command, DX-tips)
Uses windows clipboard
A real 32-bit program, doesn't steal CPU time (eg. WinAmp works
simultaneously without any problems). Fast message list cleaning,
up to
5000 titles per second.
Low CPU load: only 4% on a 300MHz computer, full speed 9k6
download.
Easy to use, fully controlled by mouse
Easy to use, fully controlled by keyboard :-)
For ex-T4-users: configuration files and message lists can be
automatically converted.
Hardware requirements
NBF requires a 32-bit Windows platform (95/98/NT). In practise, at
least
a Pentium-class machine with 32 megs of ram is required to run any
Windows application. NBF is no exception. The program itself takes
less
than two megabytes of hard disk space, but you should reserve some
space
for message files too.
Connection to the surrounding world can be made either with a TNC,
FlexNet, AGW or telnet.
The TNC must have a WA8DED-compatible firmware, such as
TheFirmware. It
should run with at least 6 MHz clock (4 MHz with a slow 1k2 radio
connection). The faster the better. A backup battery is not
required nor
recommended because the TNC is reinitialised each time NBF starts.
FlexNet is a German software package which contains a great amount
of
drivers for different packet hardware. All FlexNet modules must be
loaded before Windows. NBF communicates directly with the FlexNet
kernel
so TFEMU should not be loaded.
AGW Packet Engine provides similar functionality as FlexNet. It is
started within Windows, so it also works with Windows NT.
The telnet interface is mainly intended for connecting to a Linux
node
across a LAN, such as in many clubhouse installations. It’s highly
experimental, and may not always work properly. Only ASCII
transfer is
supported so far, but binary transfer might also work depending on
the
configuration on the Linux side.
Some users have reported that NBF works under Linux too, with Wine
and
telnet (kernel 2.2.12). The hostmode interface has not been tested
under
linux yet, so if you have a suitable test setup, we’d definitely
like to
hear about the results.
oh1kzn@sral.fi
Read previous mail | Read next mail
| |
