| |
F1OYP > BPQ 15.07.00 08:29l 572 Lines 21055 Bytes #-9579 (0) @ EU
BID : 307-F1OYP
Read: GUEST
Subj: BPQ help_cfg Windows (5/5)
Path: OE1XAB<OE3XPR<OE6XAR<OE5XBL<OE2XOM<DB0PV<DB0FSG<I4UKI<IK2HDG<IK1MAP<
I1YLM<IK1ZNW<KB7FRV<VE2RNT<F5JOE<F1OYP
Sent: 000707/0535Z @:F1OYP.FAQI.FRA.EU #:44315 [Perigueux] FBB7.00g25 $:307-F1O
From: F1OYP@F1OYP.FAQI.FRA.EU
To : BPQ@EU
[¯¯¯ TSTH V 143aF , UTC diff:5, Heure Locale:Ven Jul 07 06:21:44 2000®®®]
msg 5/5 :
re-send 07/07/2000 to bpq@eu
__________________________________________________________________________
Aide config BPQ sous windows
__________________________________________________________________________
> From:
> To : TOUS@FRA
>
> Message timed: 09:15 on 27 Feb 99
> Message sent using WinPack V6.4 & BPQ408a
n'avez vous pas remarqu‚ quelque chose dans la "signature" ?
il utilise Winpack avec un baycom , donc sous windows mais avec un driver
DOS = BPQ
ce qui veut dire que pour votre problŠme d'utilisation d'une platine baycom
sous Windows ( 3.1 , 3.11 , W95 , W98 ou W.Nt ) c'est normal qu'en
‚mulation directe par l'interface graphique Windows , ‡a ne marche pas !
deux solutions s'offrent … vous :
1- utilisation du driver TFX.com … la place des TFPCXxxx.exe , non adapt‚s
mais suivant les PC , ‡a peut fonctionner , comme donner les mˆmes
r‚sultats d‚cevants ... ‡a d‚pend du CPU et du Pc ! il faut tester ...
je vous donne un exemple de lancement de tsthost avec TFX.com :
(le tfx -c:2 correspond au com2 , modifiez cette valeur pour utiliser un
autre com )
tfx -c:2 -n
tsthost /t /i254
tfx -u
mais dans ce cas d'exemple , bpq ne marche pas avec tfpcx ou tfx ...
2- utiliser le logiciel BPQ ‚mul‚ sous DOS , avant de lancer le programme
packet sous windows.
-----
| Deux trucs windows au passage :
|
| - sous windows NE PAS OUBLIER de DESACTIVER le port
| COM utilis‚ par votre platine baycom. ( En gros , windows doit IGNORER le
| com et laisser BPQ driver sous DOS cette interruption )
| Que ce soit avec winpack ou winfbb , bpq doit OBLIGATOIREMENT ˆtre charg‚
| sous DOS avant que windows soit lan‡‚.
| - si certains (vieux) programmes DOS ne fonctionnent plus correctement sous
| Windows , il suffit tout simplement de CREER sur c:\ un r‚pertoire DOS
| qui n'existe pas sur les configs win95/98/NT ...
| et y copier dedans le fichier SHARE.exe d'un bon dos 6.2 ou 6.22.
| (en effet certains programmes ont ‚t‚ compil‚s … partir de logiciels
| qui font appel aux fichiers systŠme DOS et demandent un chemin c:\dos)
| aprŠs , windows se d‚brouillera tout seul ...
| ah , si j'oubliais ... path=c:\dos ...hi
-----
Pour mener … bien cette configuration , vous devez r‚cup‚rer la derniŠre
version en date de BPQ (version 4.08a ou 4.09) ainsi que deux fichiers
systŠme pour windows , … placer justement dans c:\windows\system :
- BPQDLL.DLL 43.044 ko 14/08/96
- BPQCODE.386 10.287 ko 29/07/96
Tant qu'… faire de r‚cup‚rer des fichiers , il vous faut aussi le driver
- BPQAX25.EXE 24.496 ko 29/07/93
plus sp‚cialement adapt‚ pour driver des cartes baycom et autres DRSI.
-------------------------------------------------------------------------------
je vous donne ci-aprŠs ma config de lancement , en consid‚rant que les
fichiers systŠme de BPQ sont dans c:\BPQ :
1/ fichier .bat de lancement
bpqcfg
rem bpqax25 -i60 -I4 -B3f8 -s150 -t8 -p128 -cd -b1200 -T0
bpqax25 -i61 -I3 -B2f8 -s150 -t8 -p128 -cd -b1200 -T0
bpqcode
win
vous voyez dans cette config , deux lignes de commande
la 1Šre correspond au com1 , la deuxiŠme au com2
ces mˆmes interruptions ( 60=3f8 , ou 61=2f8 ) doivent imp‚rativement ˆtre
d‚clar‚es dans le fichier principal de bpq : BPQCFG.TXT
pour bpq com1=96 com2=97
c'est l'adresse exad‚cimale commune demand‚e par bpq et son driver bpqax25.
pour d‚valider le com non d‚sir‚ , simplement mettre un ; devant dans
cet exemple je vous donne la config avec les deux coms , le com1 ‚tant
d‚valid‚ mais laiss‚ en exemple , … vous de choisir o— vous d‚sirez mettre
votre souris ...
2/ Fichier BPQCFG.txt : (j'abrŠge toutes les lignes commentaires...)
; For Version 4.08
; CONFIGURATION FILE FOR G8BPQ SWITCH SOFTWARE
;
HOSTINTERRUPT=127 ; Sets the Interrupt used to access BPQ Host Mode. Will
; normally be 127, but may be changed if this clashes with
; other software. BTRIEVE seems to use 127, so if you are
; using it, try INTERRUPT=126
EMS=0 ; dont use EMS RAM
;
DESQVIEW=0
NODECALL=F1OYP-2 ; NODE CALLSIGN
NODEALIAS=24PGX
BBSCALL=F1OYP-1 ; BBS CALLSIGN
BBSALIAS=BBS ; BBS ALIAS
;
IDMSG:
- Node BPQ Perigueux
- BBS F1OYP-1
***
;
UNPROTO=MAIL ; DEFAULT UNPROTO ADDR
INFOMSG:
#
F1OYP-2 Packet NODE , Champcevinel (24) jn05if
#
- Les commandes sont les mˆmes qu'un node NET/ROM
mais n'oubliez pas de sp‚cifier le num‚ro du port ( C 3 f1xxx )
- Utilisez la commande P(orts) pour lister ceux qui sont disponibles
***
;
; CTEXT - Normally will only be sent when someone connects to
; the NODE ALIAS at level 2. If FULL_CTEXT is set to 1, it
; will be sent to all connectees. Note that this could confuse BBS
; forwarding connect scripts.
;
CTEXT:
# F1OYP-2 # Packet Switch … Champcevinel (24)
Tapez ? pour lister les commandes.
***
FULL_CTEXT=0 ; SEND CTEXT ONLY TO L2 CONNECTEES TO ALIAS
; Network System Parameters
;
OBSINIT=5 ; INITIAL OBSOLESCENCE VALUE
OBSMIN=4 ; MINIMUM TO BROADCAST
NODESINTERVAL=60 ; 'NODES' INTERVAL IN MINS
IDINTERVAL=15 ; 'ID' BROADCAST INTERVAL (UK Regs require
; an AX25 ID every 15 mins)
;
BTINTERVAL=0 ; NO BEACONS
L3TIMETOLIVE=25 ; MAX L3 HOPS
L4RETRIES=3 ; LEVEL 4 RETRY COUNT
;
L4TIMEOUT=120 ; LEVEL 4 TIMEOUT
L4DELAY=10 ; LEVEL 4 DELAYED ACK TIMER
L4WINDOW=4 ; DEFAULT LEVEL 4 WINDOW
;
MAXLINKS=30 ; MAX LEVEL 2 LINKS (UP,DOWN AND INTERNODE)
MAXNODES=120 ; MAX NODES IN SYSTEM
MAXROUTES=35 ; MAX ADJACENT NODES
MAXCIRCUITS=64 ; NUMBER OF L4 CIRCUITS
MINQUAL=10 ; MINIMUM QUALITY TO ADD TO NODES TABLE
BBSQUAL=30 ; BBS Quality relative to NODE - used to
BUFFERS=255 ; PACKET BUFFERS - 255 MEANS ALLOCATE AS MANY
PACLEN=128 ; MAX PACKET SIZE
TRANSDELAY=0 ; TRANSPARENT MODE SEND DELAY - 1 SEC
T3=180 ; LINK VALIDATION TIMER (3 MINS)
IDLETIME=900 ; IDLE LINK SHUTDOWN TIMER (15 MINS)
;
;
; Configuration Options
;
BBS=1 ; INCLUDE BBS SUPPORT
NODE=1 ; INCLUDE SWITCH SUPPORT
;
HIDENODES=0 ; IF SET TO 1, NODES STARTING WITH # WILL
; ONLY BE DISPLAYED BY A NODES * COMMAND
;
; THE *** LINKED COMMAND IS INTENDED FOR USE BY GATEWAY SOFTWARE, AND
; CONCERN HAS BEEN EXPRESSED THAT IT COULD BE MISUSED. I RECOMMEND THAT
; IT IS DISABLED IF NOT NEEDED.
;
ENABLE_LINKED=Y ; CONTROLS PROCESSING OF *** LINKED COMMAND
;
;
; 1er Port :
TNCPORT
COM=n
ENDPORT
;
; 2Šme Port :
;TNCPORT
;COM=n
;ENDPORT
;
;
;--------------Port1
;PORT
;ID=Bpq_Baycom1
;TYPE=EXTERNAL
;PROTOCOL=KISS
;IOADDR=3F8H
;INTLEVEL=96
;SPEED=1200
;CHANNEL=A
;QUALITY=10
;MAXFRAME=1
;TXDELAY=500
;SLOTTIME=150
;PERSIST=128
;FULLDUP=0
;FRACK=7000
;RESPTIME=2000
;RETRIES=10
;PACLEN=128
;DIGIFLAG=1
;DIGIPORT=0
;MHEARD=1
;ENDPORT
;
;--------------Port2
PORT
ID=Bpq_Baycom2
TYPE=EXTERNAL
PROTOCOL=KISS
IOADDR=2F8H
INTLEVEL=97
SPEED=1200
CHANNEL=A
QUALITY=10
MAXFRAME=1
TXDELAY=500
SLOTTIME=100
PERSIST=64
FULLDUP=0
FRACK=7000
RESPTIME=2000
RETRIES=10
PACLEN=128
ENDPORT
;
;
ROUTES:
***
;
APPLICATIONS=BBS,,*SYS
;
_________________________________________________________________________
Suite … des pbs de dysfonctionnement , j'ai r‚duit le maxframe … 1
et le paclen … 128 , avec bpq la platine baycom coupait en ‚mission aprŠs
chaque trame , au lieu d'envoyer en ‚mission un seul paquet de 2 3 ou 4
trames en mˆme temps , d'o— collisions importantes . Je n'ai trouv‚ que
cette parade … ce problŠme.
_________________________________________________________________________
Une autre syntaxe peut ˆtre utilis‚e , c'est le chargement du fichier
BPQJJF.exe , l'ami g7jjf ayant re-‚crit un driver sp‚cifique BPQ pour
driver un baycom direct avec Winpack. (archive bpqjjf11.zip)
Aux dires de certains oms G , ‡a fonctionne super ...
Je n'ai jamais test‚ .
Ci-joint le fichier bpqjjf.txt :
BPQJJF.EXE V1.1 (c) G4IDE, June 1997
------------------------------------
What it does
------------
BPQJJF.EXE acts as an interface between G7JJF's BAYDRV Baycom driver for
Windows and G8BPQ's BPQCODE node software. It allows Windows packet
applications which support BPQ (such as WinPack) to be used with BAYDRV
and therefore with a Baycom modem. BPQJJF is not in itself a Baycom
driver, BAYDRV.VXD is the driver, which is (c) Jon Welch, G7JJF. If you
have any problems using BAYDRV in conjunction with BPQJJF.EXE, please
contact myself, DO NOT contact G7JJF. BAYDRV is a very clever piece of
software and I would like to thank G7JJF for giving his permission for
it to be used in this application.
Getting Started
---------------
My suggested route to using a Baycom modem with BPQ, BPQJJF, BAYDRV and
Windows is as follows:-
1. Make sure your modem works by using it in DOS with a DOS packet
program that supports it, such as the Baycom software.
2. Learn how to use BPQ - there's no easy way, you simply have to read
the docs! Run BPQ and the modem in DOS by using something like BPQAX25
as an interface between the modem and BPQ.
3. If you've successfully made it this far, follow the instructions in
the next section. If you skip any of the above steps and then find you
have problems with the Windows setup, you won't have a clue as to what
is not working.
Installation
------------
Note that, to use BPQ underneath Windows, you need version 4.08a or
later.
1. Put BAYDRV.VXD and BPQJJF.EXE in your WINPACK directory.
2. Edit BPQCFG.TXT in your BPQ directory and put in a port entry
something like this:-
PORT
ID=BAYCOM
TYPE=EXTERNAL
CHANNEL=A
INTLEVEL=96
MAXFRAME=2
FULLDUP=0
FRACK=7000
RESPTIME=2000
RETRIES=10
PACLEN=120
QUALITY=10
UNPROTO=ID
ENDPORT
3. Run BPQCFG.
4. Edit AUTOEXEC.BAT and put at the end (or before any possible WIN
command) something like:-
REM the next like is typical for a *standard* COM1.
C:\WINPACK\BPQJJF.EXE -I4 -B3f8 -i60 -dC:\WINPACK\BAYDRV.VXD
PAUSE
CD \BPQ
BPQCODE
CD \
NOTE - the "-I", "-B", "-i" and "-d" are case sensitive.
If you are using the modem on a *standard* COM2, then use:-
C:\WINPACK\BPQJJF.EXE -I3 -B2f8 -i60 -dC:\WINPACK\BAYDRV.VXD
The "-i" parameter is the software interrupt to be used and must match
the INTLEVEL in BPQCFG.TXT. NOTE - INTLEVEL is in decimal, "-i" is in
hex. This may seem rather strange, but I have kept the BPQJJF arguments
as compatible as possible with the DOS BPQAX25 driver. Software
interrupts may be used by other applications. If you are loading other
drivers in AUTOEXEC.BAT or CONFIG.SYS, particularly anything like an
ethernet packet driver, it is up to you to make sure that nothing elses
is using the software interrupt you select.
You MUST use the correct IRQ (the -I argument) and the correct address
(the -B argument) for the port on which you are using the modem. DON'T
try and use a port that shares an IRQ if there is going to be an active
device on the other port using the same IRQ. A common PC setup is that
COM1 and COM3 use IRQ4, COM2 and COM4 use IRQ3. If you have another
active device on a port using the same IRQ as the one you are using with
this driver, you will get in a big mess!
5. Restart the PC - when the PAUSE in AUTOEXEC.BAT occurs the screen
should be displaying the load message from BPQJJF - check that the
parameters look ok.
6. Run Windows.
7. Start WinPack and select "Options", "Comms Setup", "Host mode BPQ".
If you get error messages then you probably haven't put the BPQ files
BPQCODE.386 and BPQDLL.DLL in WINDOWS\SYSTEM. If, when you started
WinPack, it was set up to use a normal TNC on the port where you now
have the modem, you should restart the PC, because WinPack may have
interfered with the port (see "Known Problems/Limitations", point 3,
below).
8. It should all now work!
BPQJJF Options
--------------
The full list of possible command line arguments for BPQJJF is as
follows:-
-i<software interrupt> default 60h (96 decimal)
-I<COM port interrupt> default 4 (COM1)
-B<COM port address> default 3F8h (COM1)
-b<bit rate> default 1200 (should never need changing)
-c<DCD mode> default 3. The options are:-
0 - ignore channel activity.
1 - use DCD input from modem to detect
channel activity. A standard Baycom
modem does not support this.
2 - Use any sort of noise input to detect
channel acitvity - use with squelched
rig.
3 - 'Soft DCD'. Analyse the incoming noise
to detect packet activity - use with
an unsquelched rig.
-T<soft DCD threshold> default 50. A larger number makes it less
likely that noise will be detected as valid
packet activity.
-s<slot time> default 100.
-p<persistance> default 64.
-h<TX delay in bits> default 360 = 300 msec.
-t<TX tail in bits> default 24 = 20 msec.
-w<walk_step_div> default 16. This is an internal parameter
used in the decoding of received frames in
BAYDRV.VXD. Try 32 or 64 if reception seems
poor.
-l<load driver> default is '1', which makes BPQJJF attempt to
load BAYDRV.VXD when Windows starts. If you
put '0' then it assumes the VXD has been
loaded in SYSTEM.INI. (If you have WinTNC
installed on your PC, you should use '-l0').
-d<path to driver> default "\WINDOWS\SYSTEM\BAYDRV.VXD". So, if
you put BAYDRV.VXD in WINDOWS\SYSTEM and
always start Windows from the drive where
your WINDOWS directory is, you don't need to
use the "-d" argument.
If It Doesn't Work
------------------
1. Check your AUTOEXEC.BAT and BPQCFG.TXT entries again. Make sure that
the port address and IRQ you have specified are correct for the port you
are using - if necessary check the jumpers on the I/O card. Make sure
that INTLEVEL in the BPQ port definition matches the BPQJJF "-i"
parameter, noting the above comments that one is decimal and the other
is hex.
2. If you have a scope available, check the signal on the TXD pin of the
COM port (pin 2 on a 25 pin connector, pin 3 on a 9 pin connector)
after Windows has started. It should be an asymmetric square wave,
mainly +ve, with a period of just over 80 msecs. If you have an RS232
"mini tester" (a thing with LEDs on it that plugs into a serial port -
very useful) the TXD LED should flicker rapidly. If there is no activity
on that pin, it almost certainly means that the address and IRQ you are
passing to BPQJJF are wrong.
3. If you get a message when Windows starts saying it can't find
BAYDRV.VXD, check the "-d" parameter for BPQJJF.
4. If you get a message when Windows starts saying it can't find
BPQCODE.386, check the following:-
BPQCODE.386 must be in a directory called \WINDOWS\SYSTEM on the drive
from which you start Windows. It doesn't matter if your Windows is in a
directory called WIN31 or WIN95, BPQCODE.386 MUST be in \WINDOWS\SYSTEM.
If necessary, make the directory just for this one file. Also, you MUST
start Windows from the drive on which this directory lives. This is
because the path to BPQCODE.386 is hard-coded into BPQCODE.EXE.
Known Problems/Limitations
--------------------------
1. I have used BPQ/BPQJJF/BAYDRV with the following PCs:-
P120 with Win95 and 32Mb of RAM.
P120 with Windows for Workgroups and 32Mb of RAM.
DX4/100 with Win95 and 12Mb RAM.
DX2/66 with Win95 and 16Mb RAM (most testing done on this system).
I tried to use it with the DX2 and Windows for Workgroups 3.11, but
reception was very poor. That could well be a problem with this
particular PC - when running Windows for Workgroups it always gave
problems when I tried to use TF host mode with WinPack. I don't have any
PCs with either Windows 3.1 or 3.11 on them. I don't have anything less
than a DX2/66. I don't have any PCs with less RAM than the above
systems. In this type of application, where a large number of hardware
interrupts are being serviced, Win95 is definitely better than Windows
3.1x.
2. BAYDRV does a lot of work and services a huge number of interrupts.
It hits the performance of the PC. With BPQ also having an effect on
performance, the DX2 feels a bit "clunky".
3. When the driver is using a COM port, another Windows app can still
open the port - it is, of course, up to you as the user of the PC to
make sure that doesn't happen! You can if you wish "hide" the port from
Windows, see the WinPack help file - "Support for BPQ", "WinPack and
BPQ" for information on how to do this.
4. I have found on the good old DX2 that it works a lot better on some
ports than on others. The PC has 4 serial ports and the driver has been
working fine on two of them, but it doesn't seem to want to know about
the other two - I don't know why. So, if you find it won't work on one
port, try it on another.
Using More Than One Baycom Modem
--------------------------------
During testing on the DX2, I have been running two BPQ ports with Baycom
modems quite successfully. If you want to give it a try, do the
following:-
1. Create a second port entry in BPQCFG.TXT, more or less the same as
the first, but use a different INTLEVEL - 97 should be ok.
2. Load a second copy of BPQJJF.EXE in AUTOEXEC.BAT, specifying a
different COM port and whatever INTLEVEL you have used in BPQCFG.TXT
for the second port. For example:-
C:\WINPACK\BPQJJF.EXE -I3 -B2f8 -i61 -l0
The "-l0" tells this copy of BPQJJF.EXE not to try and load BAYDRV.VXD
when Windows starts. However, it isn't really needed, because a second
copy will detect that a previous copy has been loaded and will never
attempt to load the VXD.
3. You should now have two Baycom ports! However, how well they work
depends a lot on the speed of the PC.
For The Technically Minded
--------------------------
BPQJJF acts as an external port driver for BPQCODE using the software
interrupt specified in INTLEVEL in BPQCFG.TXT and the "-i" BPQJJF
parameter. It provides an interface (or shim) between BPQCODE and
BAYDRV, which is the Baycom driver.
Until Windows starts up, BPQJJF provides a dummy port on which nothing
can be sent or received.
When BPQJJF detects that Windows is starting, it requests Windows to
load BAYDRV.VXD (unless you have specified the "-l0" parameter).
About 10 seconds after Windows initialisation is complete, BPQJJF looks
for the loaded copy of BAYDRV, if it finds it then it initialises a
port according to the various command line parameters. If
initialisation is successful, the port becomes active. If BPQJJF can't
find BAYDRV or the initialisation fails, the port remains dummied out.
Because BAYDRV is a VxD, it runs in privilege ring 0, which means that
it is able to service hardware interrupts almost as quickly as an
application running in DOS. This gets rid of the problems of interrupt
latency which stop drivers such as BPQAX25 working effectively
underneath Windows.
Disclaimer, Etc.
----------------
BAYDRV.VXD and BPQJJF.EXE are supplied on the basis that if you can get
them to work, I'm happy for you, if you mess up your PC in the process,
don't blame me! In other words, you use them entirely at your own risk.
You may use this driver combination with programs other than WinPack.
BAYDRV.VXD is (c) Jon Welch, G7JJF.
BPQJJF.EXE is (c) Roger Barker, G4IDE.
Roger Barker, G4IDE
roger@peaksys.demon.co.uk
http://www.peaksys.demon.co.uk
G4IDE@GB7OAR.#16.GBR.EU
G8MZX@GB7SKG.#15.GBR.EU
9 June 97
_________________________________________________________________________
je vous souhaite bonne bidouille
il vous faudra peut ˆtre cogiter pour faire fonctionner correctement
votre installation , j'espŠre vous mettre sur la voie ...
Ham'iti‚s
jean-pierre
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
Û FBB 7.00g - jn05if - P‚rigueux Û
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
APRS=4511.50N/00044.54E
Read previous mail | Read next mail
| |
