OS/2 Shareware BBS: 14 Text/14-Text.zip/dosbbs.zip/OS2BBS.TXT

Text File | 1993-10-04 | 8KB | 203 lines

These settings should apply to just about any DOS-based BBS running
under OS/2 v2.1.

Here's the system I run:

ZEOS 486/66 Tower
Local Bus Video-Diamond Pro(VLB) and IDE Adapter
16 Megs of RAM
Seagate 2Mb SCSI-II Hard Drive
345Mb Seagate IDE Hard Drive
345Mb Maxtor IDE Hard Drive
Adaptec 1542C Fast SCSI-II SCSI controller
Texel 3024 Internal CD-ROM drive
Pioneer DRM-604X 6 CD Changer
Iomega Tape 250 Insider 250 Meg Internal Tape Backup (QIC 80)
16550 UARTs on a BOCA Serial I/O card
Hayes Optima 144 14400 baud External Modem
PPI 14400FXSA 14400 baud External Modem
Wildcat v 3.9
FrontDoor v 2.02nc
Wildmail v 3.01
Postlink v 1.07  (RIME Net software)
OS/2 2.1 Release GA (CD-ROM)
Ray Gwinn's SIO comm driver package, includes a FOSSIL (Current 1.11)

I run Frontdoor in a Dos Window under OS/2 2.1 GA.  I didn't have to do
any modifications to my BAT file that runs FD, or to any of my utility
programs for the BBS. I understand that the stock IBM comm drivers are
working properly in the GA release, but I like the SIO package, and Ray
is always available to help with a comm problem.  Plus, he gave me
outstanding support during the OS/2 Beta.


Settings for the DOS Session that runs Frontdoor and my BBS under OS/2:

AUDIO_ADAPTER_SHARING=OPTIONAL
DOS_AUTOEXEC=C:\AUTOEXEC.BAT   (See #1 below)
DOS_BACKGROUND_EXECUTION=ON
DOS_BREAK=ON
DOS_DEVICE=C:\OS2\MDOS\VX00.SYS  (Loads the FOSSIL only in this session.)
DOS_FCBS=16
DOS_FCBS_KEEP=8
DOS_FILES=30
DOS_HIGH=ON
DOS_LASTDRIVE=Z
DOS_RMSIZE=640
DOS_SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS
DOS_STARTUP_DRIVE=
DOS_UMB=OFF     (See #2 below)
DOS_VERSION=  (LEAVE THIS ALONE)
DPMI_DOS_API=AUTO
DPMI_MEMORY_LIMIT=4
DPMI_NETWORK_BUFF_SIZE=8
EMS_FRAME_LOCATION=AUTO
EMS_HIGH_OS_MAP_REGION=32   (See #3 below)
EMS_LOW_OS_MAP_REGION=384
EMS_MEMORY_LIMIT=2048
HW_NOSOUND=OFF
HW_ROM_TO_RAM=OFF  (But you may want to experiment.  OS/2's Shadow RAM)
HW_TIMER=OFF
IDLE_SECONDS=0
IDLE_SENSITIVITY=75
INT_DURING_IO=OFF
KBD_ALTHOME_BYPASS=OFF
KBD_BUFFER_EXTEND=ON
KBD_CTRL_BYPASS=NONE
KBD_RATE_LOCK=OFF
MEM_EXCLUDE_REGIONS=
MEM_INCLUDE_REGIONS=
MOUSE_EXCLUSIVE_ACCESS=OFF
PRINT_SEPARATE_OUTPUT=ON
PRINT_TIMEOUT=15
SIO_Allow_Access_COM1=ON
SIO_Allow_Access_COM2=ON
SIO_Allow_Access_COM3=ON
SIO_Allow_Access_COM4=OFF
SIO_Virtualize_16550A=ON
SIO_Virtualize_COM_Ports=ON
SIO_Virtual_RTS_is_HS=ON
VIDEO_8514A_XGA_IOTRAP=ON
VIDEO_FASTPASTE=OFF
VIDEO_MODE_RESTRICTION=NONE
VIDEO_ONDEMAND_MEMORY=ON
VIDEO_RETRACE_EMULATION=ON
VIDEO_ROM_EMULATION=ON
VIDEO_SWITCH_NOTIFICATION=OFF
VIDEO_WINDOW_REFRESH=1
XMS_HANDLES=32
XMS_MEMORY_LIMIT=2048
XMS_MINIMUM_HMA=0


Topical lines from my CONFIG.SYS:

IFS=C:\OS2\HPFS.IFS  /CACHE:1024 /CRECL:4 /AUTOCHECK:CDEFGHILKMJN
  I use only HPFS partitions.  With all the usage the BBS has, messages
  and such, I have never seen more than 2% fragmentation.  Also, it has
  saved me lots of space (FAT cluster sizes are too big on large
  partitions), and has proven to be very fast.

SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS
  This is stock, but is worth mentioning because it is what restarts
  your sessions if the system reboots for any reason.  HPFS partitions
  will automatically have Diskfix run on them if it was not a planned
  shutdown.

PRIORITY_DISK_IO=YES
  This gives the session in the foreground priority on disk accesses.
  You may want to set this to off if you find any comm errors while the
  BBS is in the background.  I can have a 14.4 caller, have my own 14.4
  session doing a transfer, and run Describe, or whatever in the
  foreground.  Both comm sessions still get a 1600+ CPS rate.

MAXWAIT=3
  This is how long a program must wait (maximum) before being given
  priority for running (getting a timeslice).  See MAXWAIT in the
  Command Reference.

DEVICE=C:\OS2\SIO.SYS (COM3:38400,3E8,5)
  This loads the SIO comm driver.  I use a nonstandard IRQ, so have to
  specify it.  The COM3:38400 locks that port at 38400.  If you don't
  want to lock your port, the command would be (3,3E8,5).

REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;E:\DELETE,512;....thru N
  I found that the Delete protection was a bit slow when running a BBS.
  If I did not protect the BBS partitions, why bother?  So, I shut it
  down.  Of course, taking the line (and any REM'd line) out will speed
  the booting process.



#1- AUTOEXEC.BAT

@ECHO OFF
ECHO.
PROMPT $i$p$g
PATH C:\OS2;C:\OS2\MDOS;C:\OS2\MDOS\WINOS2;C:\;E:\UTIL;K:\WC30
LOADHIGH APPEND C:\OS2;C:\OS2\SYSTEM
SET TEMP=C:\OS2\MDOS\WINOS2\TEMP
SET TMP=C:\
SET HOMEPATH=K:\WC30
SET WCHOME=K:\WC30
SET WCNODELIST=K:\WC30\DATA\

  I put most all the setting for anything associated with the BBS into
  the standard AUTOEXEC.BAT.  I can run any utility from another DOS
  session, and I know that any environment variables are set correctly.
  However, in my BAT file that runs FD and the BBS, I do have to set
  things like the DSZ port and DSZ log.  I do not want them the same for
  all sessions.  I use a different BAT in the AUTOEXEC setting for other
  comm programs so I can control what they use and do.  Pretty nice!

#2- I do not load any drivers high, so don't need the UMBs active.

#3- I had a utility that did not have enough EMS pages free.  Setting
    this to 32 gave it the room it needed.

I have ran under OS/2 2.1 for months now with out any trouble at all.  I
can even go away on vacation and not worry about the system locking up.
Plus, when I installed my CD changer, it took 10 minutes from the box to
operational, including loading the CDs.  Try that with DOS!  With an
Adaptec, the driver will be installed, but if you are running a changer,
you must put /ET at the end of the appropriate .ADD line.  This enables
the Extended Targets, which is what allows access to all the CDs.

If you find that this is in some way incomplete, please let me know so I
can provide accurate information to other Sysops.  If you'd like more
information or assistance, feel free to contact me.

Gary Hammer, Sysop  [Team OS/2]
The Northern Exchange BBS
1:355/24 FIDO
5325 RIME
71202,3462 CIS

*************************  Late News **************************
I have just upgraded several pieces of software.  No problems,
but my motto is 'If it ain't broke, upgrade it!'

Anyway, I have installed SIO115, I see no difference, but then,
I have never had problems with any of the released SIO drivers.

Installed Wildmail 3.10, absolutely no relationship to OS/2. I
just thought you may want to know it runs great.

Installed FD2.11 and I REALLY like it as well.  It knows it is
running in a DOS session under OS/2.  Therefore, it will give up
timeslices better than FD 2.02.

I have never found a reason to run TAME and/or OS2SPEED, but have
been asked what order they are started in.  So, if you want them
active in all DOS sessions, put them in the main AUTOEXEC.BAT.
I would just run them in the sessions that you think need them.
The individual AUTOEXECs are really nice for things like that.
At any rate, TAME before OS2SPEED.  I would think of these as a
last ditch effort however.  I see no slowdown in ANY application
or comm session (OS/2, Win, or DOS), yet my PULSE meter is always
pegged at 100%.  I feel that PULSE is quite useless.  You know
how an application should 'feel', use you own judgement.

10/4/93 21:25 Alaska Daylight Time