Fra         : LA6CU
Til         : LA6CU
Sendt       : 13-Mar 06:40
Mottatt     : 13-Mar 06:40
Type/status : PY
BID (MID)   : 28947_LA6CU
Meldingsnr. : 225555
Tittel      : CP LA6CU: FBB7 install suggestions
Original from VE4KV to FBB@WW
Path: !LA1B!LA7H!LA8D!LA2D!LA9H!SM6DLD!SK6SA!SM6KIK!SK6YW!SK6FV!SK7OA!OZ3BBS!
     !OZ3BOS!OZ4BOX!DB0HRO!DB0SAW!DB0NHM!DB0BAL!DB0MER!DB0LPZ!DB0HOT!DB0MAK!
     !DB0PV!DB0WGS!OE3XSR!OK0NKT!OK0PBB!OK0PAB!OH3RBR!VE4KV!

From: VE4KV@VE4KV.#WPG.MB.CAN.NA
To  : FBB@WW

Hi guys, now that the dust is starting to settle with the v7.00 release there
are some install  suggestions that were  not mentioned. I  have tried to  put
some of these together for a "typical" basic bpq plus phone modem install.

  It  appears the  install is  not overwritting  the old  5.15c  english.txt
language file. So the first thing to  do is rename it to anything other  than
english.txt so you get the updated  file. (there are afew extra lines  in the
new english.txt for the themes and  msg  hold  functions)  Now  proceed  with
copying the install files to a floppy and put in drive A: . Do the install.

  DO  NOT  load  FBBIOS  or  ESS comport  drivers  if  you  run  WinFBB. The
FBBCOMM.DRV  takes their  place in  the backround  with windows.  Check  your
autoexec.bat now to see they are disabled.

  WinFBB does it's  own memory management  so do not  use EMM386 or  QEMM in
either Win95 or Win3.11. With Win3.11 use himem.sys only.

  Do not use smartdrv.exe with Win95. (Yes use it with Win3.11)

  To prevent bpq and windows both  trying to grab the same comports  put the
following in your c:\windows\system.ini file     MaxComPort=0

  Put bpqcode.386 and bpqdll.dll  in the c:\windows\system directory.  Start
bpqcode.exe from your autoexec.bat.

  Use  a  single  inittnc1.sys  for bpq  and  another  for  the phone  port.
(inittnc4 in this case)

inittnc1.sys for bpq

A1
R0
UMAIL
M1
N1

inittnc4.sys for Robotics V Everything modem.

ATZ
ATZ^M
AT B0 V1
AT &B1 &C1 &H1 &M4 &N0 &K3 &A3 X3
AT S7=45
ATS02=255
ATS0=1

  DO NOT load more than one inittnc.sys for bpq ! Check NOW to see no others
exist and delete all not required.

  When WinFBB is installed it will be in the test mode by default. Run it in
test  mode  for  afew  minutes  to see  that  the  server  files  are working
(FBB_SVC.PIF) .  If the  bbs crashes  at this  point there  could be  several
reasons. Some servers are no longer  compatable  and  must  be  rewritten  as
DLLs. The same  goes for the  PG files like  some password programs that use
the C_filter. If in doubt disable all  PG and server files and bring back  up
one at a time once the bbs is stable.

  Another source of crashes at startup appears to be a possible problem with
AUTO7P message or WP imports. Nukem if in doubt.

Here  is  what  your  port.sys  should look  like  for  a  modem  port and  3
bpq comports.

#Ports TNCs
2     4
#
#Com Interface Adress (Hex) Baud
2   6         2f8          38400
8   2         0            19200
#
#TNC NbCh Com MultCh Pacln Maxfr NbFwd MxBloc M/P-Fwd Mode Freq
0   0    0   0      0     0     0     0      00/01   ----  File-fwd.
1   9    8   0      0     2     1     10     31/60   QULWY VE4KV-3
2   9    8   1      0     4     2     10     10/60   QULWY VE4KV-3
3   9    8   2      0     1     2     10     20/60   QUY   VE4KV-3
4   1    2   0      128   7     1     10     15/60   MUWR  MODEM


Notice that the first tnc is MultCh  0. Important if you wish to monitor  the
radio channels !

In  the  bpqcfg.txt a  SINGLE  virtual comports  is  defined as  com8  and is
reflected in the  above. The modem  is on Com2  and mouse on Com1. In reality
the  real physical  comports are  on a  STB-4 port  card and  reside on  high
inturrupts  and  spare  port  address's.  ie int12 03E8 etc. This is ofcourse
defined in the  bpqcfg.txt in the  physical port stuff.  Nice that bpq  takes
care of all this ! (thanks from all of us to G8BPQ !!)

 If your users attempt a ZPUT on  the phone port you will probably get  port
overruns unless you have a special IO  card like the Hayes ESP. It works well
in windows and has a 1k buffer for both TX and RX.

 On the subject of Comports you ARE using atleast 16550s on your radio ports
?? I  hope so  or you  will see  protocol errors  from bit  dropping. This is
really critical for 386 and low end 486 machines.

  The runfbb.bat must be checked  before walking away. The default  one will
try to backup  to B:\ .  If the system  GPFs on shutdown check the runfbb.bat
for typos.

  If the screen writes are slow  monitoring the freq then you need a Windows
vidio card with some horsepower.

  Hopefully these hints will be enough to get you going.

  The following  are some  sites you  may wish  to send  detailed reports of
problems ...

Beta test Managers -
G1DIL @ GB7BBS  - Andy
LA6CU @ LA6CU   - Per

Long term Beta testers who work with G1DIL
G6FCI @ GB7FCI  - Chris
VE4KV @ VE4KV   - Doug
KE0WO @ KE0WO   - Dean

Sorry I'm not sure who is working with LA6CU at this time.



Best73
Doug - WinFBB Beta Test Site

[Entered at 11:55 CST on 08-Mar/96]