home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
HATCH
/
WWIVNEWS.ZIP
/
9605_1.NWS
< prev
next >
Wrap
Text File
|
1996-05-23
|
30KB
|
644 lines
┌┐┌┐┌┐┌┐┌┐┌┐┌────┐┌┐ ┌┐┌─┐ ┌┐┌────┐┌┐┌┐┌┐┌────┐
╔═════════════││││││││││││└─┐┌─┘││ │││ └┐│││┌───┘│││││││┌───┘═════════════╗
║ Volume 7 ││││││││││││ ││ └┼┐┌┼┘│ └┘││└───┐│││││││└───┐ Spring ║
║ Issue 1 ││││││││││││ ││ ││││ │┌┐ ││┌───┘││││││└───┐│ 1996 ║
╚═════════════│└┘└┘││└┘└┘│┌─┘└─┐ └┼┼┘ ││└┐ ││└───┐│└┘└┘│┌───┘│═════════════╝
│ └────┘└────┘└────┘ └┘ └┘ └─┘└────┘└────┘└────┘ │
│ Serving WWIV Sysops & Users Across All WWIV Networks │
└──────────────────────────────────────────────────────┘
┌─────────────────────┐
│This Issue's Features│
┌────────────────────────┴─────────────────────┴────────────────────────────┐
│ Random Notes........................................Wayne Bell (1@1) │
│ │
│ Soft Servings: News from WWIV Software Services....Sam (1@2863) │
│ │
│ Third-Party Developers and WWIV.....................Dawg (1@2121) │
│ │
│ Shareware Mods...An Idea Who's Time has Come?.......Pug (1@11750) │
│ │
│ Running WWIV Under Novell Netware...................Festus Hagen (1@9400) │
│ │
│ Understanding Viruses (Part 3 in a Series)..........Sam (1@2863) │
│ │
│ Type 2/0 Forum......................................Sam (1@2863) │
│ │
│ Filo's Mod of the Month.............................Frank Reid (1@8213) │
│ │
│ Technical Section...................................Burmese (1@15111) │
│ │
│ Classified Ads......................................A Compilation │
│ │
│ On the Lighter Side.................................Sam (1@2863) │
│ │
│ Closing Thoughts....................................Sam (1@2863) │
└───────────────────────────────────────────────────────────────────────────┘
───────────────┬─────────────────────────────────────────────┬───────────────
│ Random Factors │
│ Creative Commentary by Wayne Bell (1@1) │
└─────────────────────────────────────────────┘
Well, I've been spending most of my free time lately investigating
Internet and PPP connectivity (for NGTRANS). I don't really have
anything coded yet, but that doesn't mean too much. Most of my
programming seems to be of the form of, "Contemplate until it comes
together, then program it." My PPP ideas haven't completely coalesced
yet, but things are getting closer. Since windows/OS2 .DLL files aren't
as advanced as Unix .so files, it will probably end up requiring a bit
more work on the part of sysops than most WWIV stuff has in the past.
How do I see BBS's in relation to the Internet? Well, Internet email
support within BBS's will definitely be a good thing, and probably some
Usenet support will be good also (although I still think BBS subs are
superior to usenet newsgroups). If you're interested in how BBS's and
the Internet will end up together/apart, you'll probably be interested
in subscribing to sub type "NETWAR" hosted by @3000, a sub dedicated to
figuring out how it all will end up, and how BBS's can "compete" with
the Internet. Note, this is not a flame-type sub, but is dedicated to
serious discussions and suggestions.
How is the OS/2 native version of WWIV coming along? Last I heard, it
was doing fairly well. I hope it'll become available in the fairly near
future, but can't offer any promises yet.
How will computer networks end up working a year from now? Ha-ha-ha, if
I could tell (I wish), I'd be borrowing money to invest in stock options
as I type. Or, I guess, when the brokerage is open. In any case, the
future of computers, networking, and BBS's is much more up-in-the-air
today than it has been in the past. It'll require the experience and
knowledge and effort of all of us to help ensure that it all turns out
for the best, as opposed to letting the future be driven by (as my
father would say) "people unable to identify a computer two out of three
times." And that would tend to include about 99.99% of all politicians.
-=■=-
───────────────┬─────────────────────────────────────────────┬───────────────
│ "Third Party Programs and WWIV" │
│ By Dawg (1@2121) │
└─────────────────────────────────────────────┘
There has been an ongoing debate for several years regarding the
inclusion of items into WWIV that have traditionally been external programs.
The debate came to a head with the Asylum QWK mod being included into WWIV.
There was a great hue and cry that it would mark the beginning of the end
of third party programs for WWIV. I for one do not believe that has happened
and nor do I believe it will.
I believe that anything that WSS can include with WWIV will only serve
to enhance it's marketability and it's viability in the marketplace. It's
true that many system operators have no need for the QWK or the RIP that is
now part of stock WWIV, there are those out there that would not use the
software without it. If including these basic functions can help sell WWIV
then all of the systems running it stand to benefit from further development
and support.
I understand the arguments made by those who were supporting Mike
Leib's WWIVmail program. I've registered many shareware programs (and
authored several as well). However, with that being said it's my belief that
if the program is truly worth the money it will survive and perhaps prosper
even more. I'll use the French Mod Division WWIVsys program as an example.
The majority of the functions performed by that piece of software duplicate
what is already either internal to WWIV or available in modification form.
Yet, there are still over eighty registrations for the software. The first
question that would pop to mind might be "Why?". I can't speak for everyone
else, but I registered it recently because of the excellent support offered
for it as well as the ease of use. For me it's far easier to be open to open
a separate OS/2 session and be able to do almost any conceivable maintenance
task for WWIV with ease. FMD seems to have found a market and taken advantage
of it. The same can be said to a lesser extent about Rob Raper's Fedit.
Fedit seemed headed for doom quite sometime ago with WSS's decision to include
Adam Caldwell's WWIVedit program in an accessory package for WWIV. However,
Adam sold the rights to WWIVedit to WSS. Despite reports to the contrary
WSS has not been able to release an updated version with such things as time
slicing code which is vital to the many of us running in multi-tasking
environments. That being the case Fedit has a new lease on life and is taking
shape as the new "editor of choice" for many system operators. These two
examples may be two of the better ones, but there are more out there.
What I believe will destroy third party programs is not what WSS
chooses to include with WWIV; but rather is people who choose to use the
shareware programs and not register them. It's my experience that many
authors do not write these programs as a line of work, but merely in their
free time. The occasional registration check is a nice incentive to not only
support what has already been written, but to encourage more programs to be
written. There will always be someone out there talented enough to write
a program to improve upon whatever Wayne Bell and WSS includes in the basic
WWIV package. It'll be a matter of if there is an incentive for them to take
the time to do so.
-=■=-
───────────────┬─────────────────────────────────────────────┬───────────────
│ "Shareware Mods" │
│ By Pug (1@11750) │
└─────────────────────────────────────────────┘
As many of you know, I have recently released a new multinode
chatroom for WWIV. It is technically a "mod", as far as it requires your
source code to be recompiled. I have a shareware and a registered version
of this mod. How, you ask? Rather than releasing the source code to the
public, almost everything dealing with the chatroom's operation is contained
inside a separate .OBJ file which is linked into your source code.
This has caused some controversy. I received various responses, some
positive, some negative. I am going to address the negative ones. The most
common negative response was "You expect people to PAY for a mod?" Yes. I
have written 17 mods which available to the public free. They each took me
between 2 hours to 3 days to program. I don't have a problem releasing that
sort of thing for free. However, my chatroom took OVER two months to program.
When I work on something for two months, I don't think giving it away for free
is absolutely necessary.
I believe that most sysops that write mods are discouraged to write
really large mods, because in the past no one had thought of a way to charge
for them. Releasing "shareware mods" in .OBJ files is an excellent idea. I
don't think mod authors should charge for every mod they program, but for
large mods, it's definitely a good idea. Also, many programs, such as
chatrooms, don't work nearly as well as external executable files as they do
as internal mods. Mods use very little overhead and can operate quickly.
There are definite advantages to linking in an .OBJ rather than using an
external program to do the same thing.
The other complaint I received was that a foreign .OBJ file could
contain back doors. I can't argue that it couldn't, but I can argue that
an .EXE could just as easily have back doors. Any program that can locate
your CONFIG.DAT & user data files can provide someone with the system password
and the user's password of their choice. The program could even shell someone
to a DOS prompt if programmed properly. My chatroom, to the best of my
knowledge, contains no back doors whatsoever, but any other executable door
being run could contain them.
Shareware mods aren't such a bad idea. It encourages mod authors to
write bigger and better modifications that work faster than external programs.
Just because sysops complain about paying for something that was free in the
past doesn't mean it's a bad thing. I am in no way suggesting that all mods
be charged for, just mods that take a great deal of time and effort on the
part of the mod author.
-=■=-
───────────────┬─────────────────────────────────────────────┬─────────────────
│ Running WWIV Under Novell Netware │
│ By Festus Hagen (1@9400) │
└─────────────────────────────────────────────┘
[Editor's Note-
With the recent debate over which is the better operating system (OS/2 or
Windows 95), perhaps the best solution for multi-node WWIV operation has been
overlooked - Netware.
The following is a "how to" written by Festus Hagen. As a Novell CNE myself,
I found it very informative and easy to understand. For those of you able to
get yourself a copy of Netware, this may be just what you have been looking
for.]
[Short background on Netware volumes]
Netware uses segments of storage space called "volumes" as opposed to drives.
With Netware 3.12, it is possible to have up to 32 volumes that span 64
physical drives that contain up to 32 TB of space. A volume can span across
multiple physical drives. Conversely, more than one volume can reside on the
same drive. Most (all) netware volumes should be set up where the first
volume is called SYS. Additional volumes are usually called VOL1, VOL2, etc,
though their names are not as critical as the first volume being called SYS.
Novell uses drive "mappings". A drive mapping is simply a pointer to a
logical portion of your netware volume. For instance, if you have a subdir-
ectory called APPS off of the root, you could "map a drive pointer" to that
directory. For instance, if you type
map g:=sys:apps
Whenever you go to the "g drive" you will actually be in the \apps directory.
WWIV needs what it believes is a TRUE drive!
So you need to 'map root' the drive.. like so:
map root s:=sys:user/bbs
^^^ ^^^^^^^^... Whatever you want!
| .. Whatever volume you want!!
That will give you a fake "ROOT" directory called drive s: off of volume
SYS:\USER\BBS
Change to S: and you will be in SYS:\USER\BBS directory!
S:\>
But using a drive letter that far down the letter chain will cause you to
lose to many SEARCH drives!! SEARCH drives start at Z and work backwards!!
(A "search drive" is simply a mapped drive that is treated just as DOS
directories placed in your PATH= statement are treated....that is, they are
just another place the operating system looks for the commands you give it
if it cannot find them in RAM or in the current directory. You can have up to
16 search drives.)
For the most part, mapped drives start at F and work forward. Depending on
whether your client is using VLM or NETX and what the LASTDRIVE statement
in your workstation config.sys file is set to, this may differ. It is beyond
the scope of this article to delve into that area.
Personally I use P: for my BBS
My setup As Novell Netware sees it: I have cut this down to size!!
VOL3:\ // 4th Drive = 1.2gigs
├──BB1 // MAP ROOT P:=VOL3:BB1, MAP S16:=VOL3:BB1\BBS
│ ├──BAT // MAP S16:=VOL3:BB1\BAT
│ ├──BBS // Main WWIV dir!
│ │ ├──BADLINK // Linkers LAME empty dir
│ │ ├──CHAINS // Onliners
│ │ │ ├──DRAWPOKE // JNS Draw Poker
│ │ │ ├──STREE // JNS Soli-Tree
│ │ │ // Cut to shorten
│ │ ├──DATA // WWIV data dir
│ │ ├──GFILES // WWIV gfiles dir
│ │ │ └──SUBAVAIL // Compilation of SUBS.x Avail via 'G'files
│ │ ├──LANG // Language parent
│ │ │ ├──ENG // English
│ │ │ ├──SPAN // Spanish
│ │ │ ├──FREN // French
│ │ │ └──GERM // German
│ │ ├──LOGS // Various Log files
│ │ ├──MSGS // WWIV message dir
│ │ ├──NETS // Networks parent
│ │ │ ├──ICENET // ICEnet data
│ │ │ ├──TCG // TCGnet data (Private)
│ │ │ ├──WWIV // WWIVnet data
│ │ │ └──XANTH // XanthNET data
│ │ ├──TMP // Temp dir parent
│ │ │ ├──BATCH1 // node 1
│ │ │ ├──BATCH2 // etc...
│ │ │ ├──BATCH3 // etc...
│ │ │ // Cut to shorten
│ │ │ ├──TEMP1 // node 1
│ │ │ ├──TEMP2 // etc...
│ │ │ ├──TEMP3 // etc...
│ │ │ // cut to shorten
│ │ └──WEDIT // WWIVEdit
│ │ ├──CONFIG
│ │ ├──DICT
│ │ └──DOC
│ ├──DLDS // Downloads (Partial)
│ │ ├──CODEING // Most of my dloads are on other VOL's
│ │ // Cut to shorten
│ ├──DOCS // All Doc's
│ ├──FAX // Fax setup
│ └──UPLOADS // New uploads!!
// cut to shorten
My WWIV is setup to use P:\BBS
Changing to MAP ROOT'ed drive P: results in this:
P:\ // Actual Netware path, VOL3:\BB1
├──BAT // MAP S16:=VOL3:BB1\BAT
├──BBS // Main WWIV dir!
│ ├──BADLINK // Linkers LAME empty dir!
│ ├──CHAINS // Onliners
│ │ ├──DRAWPOKE // JNS Draw Poker
│ │ ├──STREE // JNS Soli-Tree
│ │ // Cut to shorten
│ ├──DATA // WWIV data dir
│ ├──GFILES // WWIV gfiles dir
│ │ └──SUBAVAIL // Compilation of SUBS.x Avail via 'G'files
│ ├──LANG // Language parent
│ │ ├──ENG // English
│ │ ├──SPAN // Spanish
│ │ ├──FREN // French
│ │ └──GERM // German
│ ├──LOGS // Various Log files
│ ├──MSGS // WWIV message dir
│ ├──NETS // Networks parent
│ │ ├──ICENET // ICEnet data
│ │ ├──TCG // TCGnet data (Private)
│ │ ├──WWIV // WWIVnet data
│ │ └──XANTH // XanthNET data
│ ├──TMP // Temp dir parent
│ │ ├──BATCH1 // node 1
│ │ ├──BATCH2 // etc...
│ │ ├──BATCH3 // etc...
│ │ // cut to shorten
│ │ ├──TEMP1 // node 1
│ │ ├──TEMP2 // etc...
│ │ ├──TEMP3 // etc...
│ │ // cut to shorten
│ └──WEDIT // WWIVEdit
│ ├──CONFIG
│ ├──DICT
│ └──DOC
├──DLDS // Downloads (Partial)
│ ├──CODEING // Most of my dloads are on other VOL's
│ // cut to shorten
├──DOCS // All Doc's
├──FAX // Fax setup
└──UPLOADS // New uploads!!
Create a Novell multiple logon account named 'BBS', Give it RWCEMF rights
to VOLx:\BB1.. (Read, Write, Create, Erase, Modify, and Filescan rights).
Create a login script for each user that you want to be able to run the
BBS and add these commands!
MAP ROOT P:=VOLx:BB1
MAP S16:=VOLx:BB1/BBS
^^^.. Maps the next available search drive letter!
(Of course change the VOLx to whatever your system has and you are going
to use)
Personally, I don't use Multiple Login Accounts! I use Groups, And
IF MEMBER OF statements in my SYSTEM logon script. Then all I have to do is
add whomever I want to be able access the BBS to the BBS group!
In my writings above I used 'MAP S16:=VOLx:BB1/BBS' to show how to
setup a search drive for the BBS dir!! You will see that I'm not practicing
what I preach!! I am FORCING my search drives to be specific versus using
S16 which just uses the next available search drive letter! :) Increases
management time, reduces debug time..
Here is part of my Novell Netware 3.11 SYSTEM Login script. I have trimmed out
alot of items that don't pertain to wwiv. I will comment this script with
Novell legal comments '#'
# Setting up the PROMPT and USERN variables!!
# Not much needs saying about the prompt! (Besides I like it)
# You will notice that it shows the username!
# This is what it looks like:
# TCGUY: Mon 02-19-1996 @ 3:56:25
# P:\BBS=> _
# The USERN variable, Welp, It's kinda handy..
SET PROMPT="%LOGIN_NAME: $d @$t$h$h$h$_$p$q$g "
SET USERN="%LOGIN_NAME"
# I use a Group! If you are a member of it then you can access it!
# 1) map root the drive
# 2) setup a search the BBS directory
# 3) setup a search to the BBS's .BAT directory
IF MEMBER OF "BBS" THEN
MAP ROOT P:=VOL3:BB1
MAP INS S8:=VOL3:BB1\BBS
MAP INS S9:=VOL3:BB1\BAT
ENDIF
# A second copy to play with! Why crash the good one.. :)
IF MEMBER OF "BB2" THEN
MAP ROOT P:=VOL3:\
MAP INS S8:=VOL3:BB2\BBS
MAP INS S9:=VOL3:BB2\BAT
ENDIF
My BBS batch file (BB.BAT)
I have cut some repeated stuff out to shorten it!
(and have added a few comments!)
-=-=-=-=-=-=-=-=-=-=-=-=- BB.BAT
@echo off
rem **** BB.BAT = BBS inst = Next
SET PKNOFASTCHAR=YES
p:
cd\bbs
REM **** inst_loc.xxx prevents one from running Multiple copies of
REM **** the same instance!
if not exist inst_loc.1 goto inst1
if not exist inst_loc.2 goto inst2
REM **** Cut to shorten!
goto allused
REM **** set the WWIV instance number
:inst1
SET WWIV_INSTANCE=1
goto okdoit
:inst2
SET WWIV_INSTANCE=2
goto okdoit
REM **** cut to shorten
goto allused
:okdoit
REM **** Safety check!
if exist inst_loc.%WWIV_INSTANCE% goto no2run
REM **** echo 'Instance in use' to INST_LOC.xxx file
echo Instance %WWIV_INSTANCE% is already running!>inst_loc.%WWIV_INSTANCE%
REM **** run the BBS
P:\BBS\BBS.EXE /I%WWIV_INSTANCE% /N0 /A1 %1 %2 %3 %4 %5
REM **** delete the INST_LOC.xxx file
del inst_loc.%WWIV_INSTANCE% >nul
goto done
:no2run
REM **** If saftey check fails
REM **** display the inst_loc file to show that instance is already in use
type inst_loc.%WWIV_INSTANCE%
goto done
:allused
REM **** Tell them all instances are used!
echo !!! NOTICE !!! All Instances are currently used!
:done
REM **** exit cleanup
SET PKNOFASTCHAR=
SET WWIV_INSTANCE=
-=-=-=-=-=-=-=-=-=-=-=-=-=-=- End BB.BAT
The only problem with this batch setup is if you have to BOOT out of a
locked WWIV the INST_LOC.xxx file doesn't get deleted! My work around for
this is 'del inst_loc.xxx' in each workstations autoexec.bat according to what
instance that workstation's primary instance is! I know, Clumsy but simple!
Without some sort of prevention, you'll end up running multiple SAME instances
of WWIV at the same time on two (or more) different workstations!! This will
cause MAJOR wwiv file damage!! Thats why the INST_LOC.xxx file is echoed to
the WWIV main dir! And the BB.BAT check for their existence!!
I'm sure there is a better method, This works without a hitch for me!!
If you anyone needs more, E-Mail me your VOICE number and a good time
to call and I'll help you out! I will NOT call during daytime hours!!,
Nights, weekends only!!
-=■=-
───────────────┬─────────────────────────────────────────────┬───────────────
│ Running WWIV Under Windows 95 │
│ By Wild Thing (1@11753 │
│ bdiamondz@aol.com │
└─────────────────────────────────────────────┘
DISCLAIMER:
I take no responsibility for damages that may occur to your
computer when following these instructions!
This is for those of you who have installed Windows 95 and wish to multi-task
your BBS with it.
I have been running WWIV v4.24a in Windows 95 for quite a while now. I'm
using a PENTIUM 100mhz with 16 megs of RAM. My BBS has two nodes, one uses a
28.8 Sportster modem and the other is a local node I have for personal use.
An advantage to running your BBS in Windows 95 is that it is very easy to get
your BBS going for the first time, and any problems you come across (which
shouldn't be any) can be easily resolved. Most full-screen editors will work
with perfection. I suggest Fedit or WWIVEdit. They seem to run the
smoothest. I have also ran many other programs such as Microsoft Works and
games like Civilization without the BBS slowing down. Things like virus
scanners also work well while the BBS is in use.
I have yet to find any doors that will not run in WIN95. This is a good sign,
but doesn't mean that there are not some out there that won't run. I have
found that most of the popular doors like LORD and USURPER will work fairly
well. DSZ works VERY good along with most Transfer Protocols.
I have almost no experience with fossil drivers. I use BNU 2.02, and it has
met my needs, so I haven't tried anything else. BNU works with perfection in
Windows 95, I haven't had a single problem with it. However, I can't say much
about other drivers.
In my own opinion, Windows 95 is a much better multi-tasker than OS/2 WARP.
I have tried both (however, I did not try WARP as extensively as I did WIN95).
I found that OS/2 WARP was a lot less user friendly and more confusing to use.
I was also in constant fear that WARP would do some kind of harm to my system.
Windows 95 will multi-task just as well as WARP, with a little more ease and a
lot less effort.
There are some problems that I have come across with running my Bulletin
Board in WIN95 that you may or may not run across. One of the major
problems, is that when I run my tape backup to backup my hard drive, it will
slow the BBS down considerably to about a 1200 baud crawl. During this time,
or if I am running 5+ programs at once, LORD will slow itself so that you
must type a command twice in order for LORD to actually carry out that task.
This creates a big problem for users. I have yet to find a way around this
problem, but I hope to get it resolved soon. Like most OS's, you can't run two
programs that require the same comm port at once. You must quit your BBS in
order to run a COMM program.
Do not use QEMM with Windows 95!! For one, QEMM is almost completely
incompatible with WIN95. Also, if you use QEMM, there is a good chance that
your BBS will run choppy and slow. I have found it better not to use QEMM,
but to run WIN95 and as many drivers as you can in high memory. This should
leave enough extended memory for all nodes of your BBS.
Enough jabber! Lets set up your system!
First, you need to make some changes to your CONFIG.SYS. The following should
be enabled:
DOS=HIGH,UMB
FILES=100
BUFFERS=30
The best way that I found to run a BBS in Windows 95, is to create a .PIF for
it. This can be done by using any standard PIF editor. This is what mine
looks like:
-------------------------------------------------------------------------------
Program Filename: <Path to your BBS.EXE or .BAT file for more than one node>
Window Title: <Title of your BBS Icon>
Video Memory: [X] Text [_] Low Graphics [_] High Graphics
Memory Requirements: KB Required [448] KB Desired [640]
EMS Memory: KB Required [348] KB Limit [1024]
XMS Memory: KB Required [448] KB Limit [1024]
Display Usage: [_] Full Screen Execution: [X] Background
[X] Windowed [_] Exclusive
[X] Close Window on Exit
Advanced Options:
Multitasking Options:
Background Priority: [1000] Foreground Priority: [1000]
[X] Detect Idle Time
Memory Options:
[X] EMS Memory Locked [_] XMS Memory Locked
[X] Uses High Memory Area [_] Lock Application Memory
Display Memory Options:
Monitor Ports: [X] Text [_] Low Graphics [_] High Graphics
[X] Emulate Text Mode [_] Retain Video Memory
-------------------------------------------------------------------------------
That's it! Now if you want to run a second node for your users, then I would
suggest using the same settings as above. If you wish to run a local node
for yourself, then you want to make another .PIF. This is what mine looks
like:
-------------------------------------------------------------------------------
Program Filename: <Path to your .BAT file>
Window Title: <Title of your BBS Icon>
Video Memory: [X] Text [_] Low Graphics [_] High Graphics
Memory Requirements: KB Required [350] KB Desired [640]
EMS Memory: KB Required [0] KB Limit [4069]
XMS Memory: KB Required [0] KB Limit [4069]
Display Usage: [_] Full Screen Execution: [X] Background
[X] Windowed [_] Exclusive
[X] Close Window on Exit
Advanced Options:
Multitasking Options:
Background Priority: [100] Foreground Priority: [100]
[X] Detect Idle Time
Memory Options:
[X] EMS Memory Locked [_] XMS Memory Locked
[X] Uses High Memory Area [_] Lock Application Memory
Display Memory Options:
Monitor Ports: [X] Text [_] Low Graphics [_] High Graphics
[X] Emulate Text Mode [_] Retain Video Memory
-------------------------------------------------------------------------------
If you want to run more then one node, you need to setup a .BAT file for each
node in your main BBS directory. Mine look like this:
----------------------------------------------------------------------------
WWIV.BAT
REM Node 1:
set wwiv_instance=1
bbs -I1
----------------------------------------------------------------------------
LOCAL.BAT
REM Node 2 (local):
set wwiv_instance=2
bbs -M -I2
----------------------------------------------------------------------------
These .BAT files would be the program filename in the .PIF's you just created.
Mine are called WWIV.BAT for my user's node and LOCAL.BAT for my personal
node. You can find more information about these .BAT files in the WWIV docs.
Next, you need to setup an Icon for each node in Windows 95. Do this by
clicking on Start, and then Settings. Choose Taskbar and then Add. Give the
path and name to your .PIF and the name of your Icon, and put it in a program
group or create a new one.
The last thing you need to do, is to run your BBS and see how it works. Just
click on the icon you just made and your BBS will boot right up!
I hope this has helped you to get your BBS setup in Windows 95 with great
performance, but if you encounter any problems at all, please feel free to
e-mail me at 1@11753.WWIVNet or bdiamondz@aol.com.
-=■=-