home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
HATCH
/
WW4WARP2.ZIP
/
OS2WARP.CFG
< prev
next >
Wrap
Text File
|
1996-08-16
|
24KB
|
483 lines
Help With OS/2 Warp! SetUp File for WWIV.
Sam #1 @4051.WWIVnet
Sun Mar 05 01:49:27 1995
RE: OS/2 with WWIV
BY: Tom Catt #1 @7166
> Can some one please please please, send me a detailed description of how
>to setup WWIV 423 with OS/2 Warp. Just got a copy & am totally lost. Kinda
>got it to work a little, but when i did a NET call out i got so many errors,
>it was crazy. Would appreciate if ANY one can help, or call voice at
> (717) 425-2528.
Since I know it will be two weeks before this gets validated I'll email
it to you as well, but here it is for everyone else.
FAQ From Sam's BBS on OS/2
With the recent popularity of IBM's latest release of OS/2 called "Warp",
I have seen many people asking the same thing I did when I first got it.
"How in the world do I make this thing work with WWIV?"
Up until the release of Warp, I had never fiddled with OS/2 whatsoever.
With the help of Fred Flintstone, JAFO, and Starship Trooper, & some major
experimentation, I was able to get everything going in fine fashion.
I do not claim to be an expert on OS/2, but here are the settings that
work the best for me. You may have to adjust some of the settings, but if
you use these as a baseline, you should be very close to optimum. The setup
I am running here features three nodes on a 486 DX2/66 with 8 megs of RAM.
(I use the HPFS here, and *strongly* urge you to do the same once you are
comfortable with OS/2. I was amazed at the difference in performance the
HPFS made!) I will give you the setting for one node. You can duplicate
it for the rest of them with one exception. More on that later.
I am assuming you were able to install Warp on your computer. It is beyond
the scope of this text to go into each possible setup.
CONFIG.SYS:
The first thing I recommend doing is editing the config.sys file Warp
created when you installed it. It is in the root directory of whatever
drive you boot from. > BACK YOURS UP BEFORE YOU EDIT IT! <
Here is my config.sys file I use for OS/2 Warp and WWIV. I have made many
changes to it from the default config.sys that was created when I installed
Warp, and where I could remember, I have added in comments to indicate the
changes. I will not guarantee I marked them all, but I did as best as I
could remembering them all. It should become obvious to you which ones were
changed when you compare it to yours.
(I boot from C: I do use the High Performance File System on both drives,
and *highly* recommend it to everyone. The increase in performance was
dramatic.)
IFS=C:\OS2\HPFS.IFS /CACHE:1024 /CRECL:32 /AUTOCHECK:CD
; Above, change 256 to either 512 or 1024 (play with it) and 4 to 32
PROTSHELL=C:\OS2\PMSHELL.EXE
SET USER_INI=C:\OS2\OS2.INI
SET SYSTEM_INI=C:\OS2\OS2SYS.INI
SET OS2_SHELL=C:\OS2\CMD.EXE
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS,LAUNCHPAD
SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE
SET COMSPEC=C:\OS2\CMD.EXE
LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;C:\MMOS2\DLL;
SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\OS2\MDOS;C:\OS2\APPS;
D:\WINDOWS;C:\MMOS2;
SET DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\OS2\BITMAP;C:\OS2\MDOS;
C:\OS2\APPS;D:\WINDOWS;C:\MMOS2;C:\MMOS2\INSTALL;
; NOTE: by: " The Animal " Make a directory called: _:\BAT; add it to the
; end of your DPATH= statements and Place ALL of your DOS Program *.BAT
; files in that directory. Also Place a Program called: OSTSR12i.ZIP in
; here as well. This program will make your dos Programs give up timeslices
; under OS/2 Warp and run a LOT smoother as well. More comments on this
; later. <g>.
SET PROMPT=$i[$p]
SET HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;C:\MMOS2\HELP;
SET GLOSSARY=C:\OS2\HELP\GLOSS;
SET IPF_KEYS=SBCS
PRIORITY_DISK_IO=NO ; changed from YES
FILES=100 ; changed from 20 (play with this setting)
BASEDEV=IBMKBD.SYS
DEVICE=C:\OS2\BOOT\TESTCFG.SYS
DEVICE=C:\OS2\BOOT\DOS.SYS
DEVICE=C:\OS2\BOOT\PMDD.SYS
BUFFERS=90 ; this may have been default. Play with it some.
IOPL=YES
DISKCACHE=2048,LW ; you may have to set this lower depending on memory
; Note that it has NO effect on HPFS machines.
MAXWAIT=1 ; changed from 3
MEMMAN=SWAP,PROTECT
SWAPPATH=C:\OS2\SYSTEM 2048 4096 ; This gave me the best performance.
; You can play around with these. I tried
; them all the way up to 10240 (10 megs),
; but this works for me.
BREAK=OFF
THREADS=100 ; changed from 256
PRINTMONBUFSIZE=134,134,134
COUNTRY=001,C:\OS2\SYSTEM\COUNTRY.SYS
SET KEYS=ON
SET BOOKSHELF=C:\OS2\BOOK;C:\MMOS2;
SET SOMIR=C:\OS2\ETC\SOM.IR;C:\OS2\ETC\WPSH.IR;C:\OS2\ETC\WPDSERV.IR
SET SOMDDIR=C:\OS2\ETC\DSOM
REM SET DELDIR=C:\DELETE,512;D:\DELETE,512; ; NOTE if you want to be able to
; undelete files, you will need
; to un-rem this line.
BASEDEV=PRINT01.SYS
BASEDEV=IBM1FLPY.ADD
BASEDEV=IBM2FLPY.ADD
BASEDEV=IBM1S506.ADD
BASEDEV=XDFLOPPY.FLT
BASEDEV=OS2DASD.DMD
SET EPMPATH=C:\OS2\APPS;
PROTECTONLY=NO
SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS
FCBS=16,8
RMSIZE=639 ; changed from 640
DEVICE=C:\OS2\MDOS\VEMM.SYS
DOS=LOW,NOUMB
DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB
DEVICE=C:\OS2\MDOS\VDPMI.SYS
DEVICE=C:\OS2\MDOS\VDPX.SYS
DEVICE=C:\OS2\MDOS\VWIN.SYS
DEVICE=C:\OS2\MDOS\VW32S.SYS
DEVICE=C:\OS2\MDOS\ANSI.SYS ; added to enable ansi
DEVICE=C:\OS2\BOOT\OS2CDROM.DMD /Q
IFS=C:\OS2\BOOT\CDFS.IFS /Q
DEVICE=C:\OS2\MDOS\VCDROM.SYS
BASEDEV=OS2SCSI.DMD
BASEDEV=FD8XX.ADD /et ; See NOTE #1 after config.sys
rem DEVICE=C:\OS2\MDOS\VMOUSE.SYS ; remove mouse driver See NOTE #2
rem DEVICE=C:\OS2\BOOT\POINTDD.SYS ; remove mouse driver
rem DEVICE=C:\OS2\BOOT\MOUSE.SYS SERIAL=COM2 ; remove mouse driver
rem DEVICE=C:\OS2\BOOT\COM.SYS ; remove stock com driver
rem DEVICE=C:\OS2\MDOS\VCOM.SYS ; see NOTE #3
DEVICE=D:\SIO\SIO.SYS ; added sio com driver (see NOTE #3)
DEVICE=D:\SIO\VSIO.SYS ; added sio com driver
CODEPAGE=437,850
DEVINFO=KBD,US,C:\OS2\KEYBOARD.DCP
DEVINFO=SCR,VGA,C:\OS2\BOOT\VIOTBL.DCP
SET VIDEO_DEVICES=VIO_SVGA
SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA)
DEVICE=C:\OS2\MDOS\VSVGA.SYS
DEVICE=C:\MMOS2\SB16D2.SYS 1 1 5 7 220 4 330 /N:SBAUD1$ /Q
DEVICE=C:\MMOS2\AUDIOVDD.SYS SBAUD1$
SET MMBASE=C:\MMOS2;
SET DSPPATH=C:\MMOS2\DSP;
SET NCDEBUG=4000
DEVICE=C:\MMOS2\SSMDD.SYS
DEVICE=C:\MMOS2\R0STUB.SYS
NOTE #1: I have two Pioneer 6-disk CD Rom changers online. In order for
OS/2 to see all of the drives/disks, you MUST add the /ET to the
end of the line where your scsi card is defined. The FD8XX is my
Future Domain SCSI card driver that OS/2 installed in the initial
setup. I have not tried this with other SCSI or IDE cards, but
would assume you would have to add it. If you have CD towers and
Warp is only "seeing" the first disk, add the /ET at the end of the
adapter card call in config.sys
NOTE #2: I do not use a mouse. I have two active nodes for callers, and to
use a mouse would require me to purchase a "com 5" card, or to put
one of my modems on a non-standard IRQ, neither of which I care to
do. Warp will work just fine without a mouse. The only feature I
had trouble figuring out was how to "arrange" the Desktop without
a mouse. To do this, make Desktop your active window, and press the
spacebar to de-select any icon. Then press your Alt key, and you
will get the menu to handle your Desktop.
NOTE #3: I strongly urge you to get and use Ray Gwinn's SIO communications
drivers. They are much, much better than the ones that come with
OS/2. The settings I use for them are noted below.
AUTOEXEC.BAT:
I also recommend editing the path statement in the autoexec.bat that Warp
creates to include everything you used to have in your path before. This is
totally up to you, but I think you will be much happier if you do this step.
Make sure you add and search paths AFTER the ones OS/2 made, especially if
you include DOS..
MAKING A WWIV FOLDER:
Once you get Warp installed, you will have to set up Icons, or folders
as Warp calls them, for each node of your BBS. The process of how you set
up your folders is completely up to you. This is the way I did it, and is
the way I recommend you do it, at least until you are more familiar with
Warp. Open up the "Templates" folder, and find the template called
"Program". With your left mouse button (or arrow key) click on this folder
to highlight it (don't open it, just highlight it). Next, press Shift-F10.
You should get a menu. Click on (or use your arrow keys and press enter on)
"Copy". Copy this template to the Desktop.
[( See Comment by: The Animal later on making a folder.)]
Once you have copied this template over to the Desktop, press Alt-F4 to
close the template folder. This should put you back on the Desktop. If you
are not on the Desktop, get there. Alt-Esc will cycle you through the open
folders (the Desktop is always open), or Ctrl-Esc will bring up a list of
open folders from which you can select Desktop. On the Desktop, go to the
folder called "Program", and highlight it (again, do not open it, just
single click on it. If you are not using a mouse, arrow-key over to it).
Once it is highlighted, press Shift-F10. This will bring up a menu. Click
on "Settings". This will open up another screen.
TEACHING WARP TO SPELL WWIV:
The first thing we are going to do is define the path and filename of the
program. In my case, it is D:\WWIV\BBS1.BAT. Don't put anything in the
middle box (parameters). My BBS1.BAT looks like this:
---------------------------[ Sam's Batch file ]------------------------------
ostsr 3 /m
SET WWIV_INSTANCE=1
BBS -I1
------------------------[ The Animal's BATch file ]--------------------------
@echo off
C:
CD \WWIV
ostsr 3 /D
SET WWIV_INSTANCE=1 ; Remote Node=1 or Instance #1
BBS /I1
------------------------[ The Animal's Local Bat file ]----------------------
@echo off
C:
CD \WWIV
ostsr 3 /D
SET WWIV_INSTANCE=4
BBS /I4 /M ; /M for NOT to use a MODEM, denoting Local logon.
; Local Node=4 or Instance #4 /I is the Instance#
-----------------------------------------------------------------------------
(OSTSR.COM is a TSR that I recommend running. It converts time slice
requests in programs written for Desqview to OS/2. Mainly this will help
you (a LOT) when programs like DSZ and HS Link are running. The 3 sets the
interval to give up timeslices (I recommend 3), and the /m puts a little
smiley face with a spinning cursor in the upper left-hand corner of your
monitor so you can see it working.)
In the bottom of this opening settings screen, you will put whatever
the working directory is. In my case, it is D:\WWIV. We are done with that
page (Leave the parameters field blank). Next, press TAB followed by PgDn.
This will bring you to the "Session" page. How you have WWIV open is
entirely up to you. I have mine open to a "DOS Full Screen" and do NOT have
it "Start Minimized". Again, these are your preferences. Either use your
mouse and click on what you want, or use your tab key and press the spacebar
to toggle your choice. Next, tab to (or click on) the "DOS Settings ".
This is perhaps the most important part. Some people will dispute the
settings I am going to give you here, but as I said, these work great for
me. I am using WWIV v4.24 here. I was using the standard settings (the ones
most recommended by others) and I was not having what I would call good
performance. I tried & tried different settings until I came upon these.
Since I started using these, I have yet to have a lockup and my BBS runs
much faster. Once you get your BBS up and running, you can play around with
them and adjust them if you like. I recommend choosing "All DOS Settings"
as you can set them all at once instead of having to constantly go back and
open different pages.
If I don't mention a setting here and you think you should change it, by
all means play around with it some. I tried to make note of anything I
changed from default though, so hopefully I didn't miss anything. :)
(Side Note: The DPMI_DOS_API is a critical setting if you run Borland C.
You will need to ENABLE it for the window you run BC in, or you will not be
happy. 'Make' MAY run ok without it, but BC.EXE will not. I don't use Turbo
C, so I don't know how it would be affected.)
In the online documentation that come with Warp, there is a part that
tells you if you run a DOS communications program, to turn the HW_TIMER on.
Don't do that. (It may work ok for only one node, but with it turned on, I
could only initialize one com port.)
Here are the values I have in the Dos Settings windows in each of my
three BBS windows. I will not guarantee you they will work for you, but
before I made these changes, I was having intermittent lockups ALL the time
with WWIV 4.24 and OS/2 Warp. Since I have made these changes, the BBS runs
a LOT faster, and I have yet to experience a lockup.
The only thing that differs between windows is the "Com Port Allow Access".
For node 1 it is com 1, for node 2 it is com 2, & node three (my local node)
none of them are enabled. These are three very important settings, as you
WILL have lockups if you do not set these right. (Make sure you adjust them
to the proper com port for your particular setup. some use ports other than
com 1 and com 2. If you don't know which com port you are using, look in
INIT or ask someone for help in finding out.)
These are in order as they appear in the Dos Settings Window in OS/2 3.0.
I have placed a <C> by the ones I think I changed, and either a setting or
<Default> where I used the default value.
I use the DOS Full Screen, but these should work under DOS Window as well.
AUDIO_ADAPTER_SHARING NONE <C>
DOS_AUTOEXEC <Default>
DOS_BACKGROUND_EXECUTION ON
DOS_BREAK OFF
DOS_DEVICE <Default>
DOS_FCBS 50 <C>
DOS_FCBS_KEEP 16 <C>
DOS_FILES 100 (If you edited your config.sys
file as indicated above, this
should already be 100. If you
did not, change this to 100.)
DOS_HIGH ON <C>
DOS_LASTDRIVE Z (You may not need this set up to
Your Last Drive letter or (Z)
Which ever is the Closest. Saves
Enviromental space/memory.
DOS_RMSIZE 639 (Same note as the DOS_FILES
statement)
DOS_SHELL <Default>
DOS_STARTUP_DRIVE <Default>
DOS_UMB ON <C>
DOS_VERSION <Default>
DPMI_DOS_API ENABLED <C>
DPMI_MEMORY_LIMIT 4
DPMI_NETWORK_BUFFER 8
EMS_FRAME_LOCATION AUTO
EMS_HIGH_OS_MAP_REGION 32 <C>
EMS_LOW_MAP_REGION 384
EMS_MEMORY_LIMIT 0 <C> (See NOTE #7)
HW_NOSOUND OFF
HW_ROM_TO_RAM ON <C>
HW_TIMER OFF
IDLE_SECONDS 10 <C>
IDLE_SENSITIVITY 10 <C> (See NOTE #4)
INT_DURING_IO OFF
KBD_ALTHOME_BYPASS OFF
KBD_BUFFER_EXTEND ON
KBD_CTRL_BYPASS OFF
KBD_RATE_LOCK OFF
MEM_EXCLUDE_REGIONS <Default>
MEM_INCLUDE_REGIONS <Default>
PRINT_SEPARATE_OUTPUT ON
PRINT_TIMEOUT 15
SESSION_PRIORITY 2 (See NOTE #5)
SIO_ALLOW_ACCESS_COM1 ON
SIO_ALLOW_ACCESS_COM2 OFF (See NOTE #6)
SIO_ALLOW_ACCESS_COM3 OFF (See NOTE #6)
SIO_ALLOW_ACCESS_COM4 OFF (See NOTE #6)
<< All SIO Settings Left Default Except Below>>
SIO_IDLE_SENSITIVITY 32 <C>
VIDEO_FASTPASTE OFF
VIDEO_MODE_RESTRICTION CGA <C>
VIDEO_ONDEMAND_MEMORY ON
VIDEO_RETRACE_EMULATION ON <C>
VIDEO_ROM_EMULATION ON
VIDEO_SWITCH_NOTIFICATION OFF
VIDEO_WINDOW_REFRESH 1
XMS_HANDLES 32
XMS_MEMORY_LIMIT 1536 <C> (NOTE #7)
XMS_MINIMUM_HMA 0
NOTE #4: I tried the suggestion everyone makes about disabling idle
detection. At first, it appeared to me this was the best way, but
once I started learning more about OS/2, I quickly found Idle
detection is good, especially if you run more than one node. I
have a program here that shows how much of the CPU's processor time
is going to what. Without idle detection, with three nodes running,
they hog nearly all the CPU's time. With two nodes running, they
take about 33% each. (this is all while sitting at WFC). By enabling
idle detection & idle sensitivity as I have here, WWIV will take
from 1 to 6 percent of the processor's time sitting at WFC. That
means if you have a caller on node one, & none on node two, the
caller will get all the attention he needs from the CPU. With
callers on each node, the CPU is still noticeably less-taxed, & both
nodes seem to run faster & more efficiently than they did with idle
detection disabled.
NOTE #5: You can play around with this setting. On my system (486 DX2-66, &
8 Mb ram) I set all three WWIV Nodes, Borland C, Professional Write,
and DOS Full Screen to a Session Priority of 2. Everything else is
set to 1. I had a friend call & test the performance for me. With
a caller on node 2, my local node going, him on node 1, & Borland C
running, he saw no noticeable degradation in performance. Bear in
mind I set the idle detection/sensitivity the same in all other
windows as I did in the above settings.
NOTE #6: Again, this should be self-explanatory to you. Do NOT allow ANY
programs to access ANY com ports unless it needs it, & then only
allow it access to the com port it has to have access to.
NOTE #7: OS/2 loves memory. And it knows how to multi-task better than Bo
knows tennis shoes. But it needs to be able to use the memory to
work right. There is no sense to give WWIV the default OS/2 settings
of 2 megs of EMS and 2 megs of XMS. I set the EMS to 0 and the XMS
to one and a half megs. This is >plenty< for anything you will be
needing to do in WWIV, including running WWIVEdit. You can use
either EMS or XMS, but in my opinion XMS is better.
The next two pages, "Association" and "Window" do not need editing. Just
press "TAB followed by PgDn", twice, which will land you on the "General"
page. Here is where you change the name of the window from "Program" to
"WWIV", in the top box. It can be whatever you like. I use "WWIV Node One",
"WWIV Node Two", etc. Also be sure to click on the "Template" box to turn
off the ugly yellow background. Here is an icon for WWIV 4.24 you can use
(courtesy of JAFO at Blue Thunder BBS). You can edit it to say 4.23 or
whatever. UUDecode this and call it WWIV.ICO.
-----------------------------------[ Cut Here -------------------------------
section 1 of uuencode 5.10 of file wwiv.ico by R.E.M.
begin 644 wwiv.ico
M0TD:````"P`;`&H````,````(`!```$``0````#___]#21H````+`!L`:@$`
M``P````@`"```0`$`````(````"``("`````@(``@`"`@("`@,S,S/\```#_
M`/__````__\`_P#______P``````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````````````````````````````````````````
M````````````````````````#___________________\`______________
M______`/___________________P#___________________\`__________
M__________`/__S_____S\_,S,___\_P#__/S____\__S______/\`__S\__
M___/_\______S_`/_/_\_\S,S__,S,_,S,_P#_S__/_/_\_____/S__/\`__
M____S__/____S\__S_`/_____\__S__,S,_/_\_P#___________________
M\`____________________`/___________________P#_______________
M____\`__G_^?__^?_Y__G_^9__`/_Y__G___G_^?_Y__F?_P#_^9^9___YGY
MG_^?_YG_\`_Y^9GY__GYF?G_G_G_G_`/^?^?^?_Y_Y_Y_Y_Y_Y_P#_G_G_G_
M^?^?^?^?^?^?\`^?____GY____^?GY__^?`/G____Y^?____GY^?__GP#Y__
M__^?G____Y^?G__Y\`____________________`/___________________P
M#___________________\`____________________`/________________
3___P````````````````````````
`
end
sum -r/size 13563/1233 section (from "begin" to "end")
sum -r/size 34101/874 entire input file
---------------------------------[ Cut Here ]--------------------------------
Uudecode that file, & put it somewhere on your hard drive. On the current
page (General) choose "Find" and tell it to look for WWIV.ICO (in the "Name"
field). Don't worry about the "Start Folder". Once it finds it, you can
"Cancel Search" and click on "OK" and the ugly Icon will be replaced with a
bright shiny new WWIV 4.24 Icon. Again, make sure you click the check mark
OFF in the "Templates" box on the General page.
Congratulations! You are all done with setting up this node. All you will
need to do is highlight this node (don't open it, just highlight it), press
Shift-F10, and copy it to the Desktop. You will be prompted to rename it,
which you should do at this time. It will retain all of the settings you
identified when setting up the original folder, so be sure to go in and edit
the Com Port Access. DON'T FORGET TO DO THIS STEP! If you have a local node,
be sure to tell it that it cannot access any com ports.
AUTOMATIC STARTUP:
Now, if you are like me, you will want WWIV to automatically start up when
your computer is turned on. Remember how we copied the Program Folder over
from the Template to the Desktop? Well, you are going to do the same thing
with the WWIV folder(s) you just made, minus probably any local instance.
Find, highlight, and open the Startup Folder. It is probably in the OS/2
System Folder. Once you have it open, Press Alt-Esc until you get back to
the Desktop. Highlight the WWIV folder you just made (don't open it, just
highlight it) press Shift-F10, and Copy it to the Startup Folder. Do this
for any program you want to open automatically on startup.
I hope I have not overlooked any steps. I feel this should be helpful to
people who are like I was and are finding themselves totally lost with OS/2
Warp and WWIV.
⌠
⌡am