Installing WWIV v4.30 with NetFoss and Net2BBS:

First I began with WWIV v4.30, performing a base install in C\wwiv\ by running INIT and configuring the basics.

Next, launch INIT ,1 ,e and select the Vmodem for Net32 as the modem option for node 1 and then exit.
Then, launch INIT ,2 ,e and select the Vmodem for Net32 as the modem option for node 2 and then exit.

Then, confirm that you can login locally by running bbs /m /o /b.
Log in as a new user and then once logged in, hit F1 to give yourself SysOP level access of SL:255 and DL:255, populate all AR's A-P by simply holding down a number and remove any restrictions by selecting the restriction and pressing on the letter you see to remove it. Quit out of the user security editor and then log off.

Download and install NetFoss and then configure as below:


My 4.30 config for NetFoss here:

Net2BBS.ini
---
[Settings]
Command=C:\netfoss\nf.bat /n*N /h*H C:\WWIV\bbs.exe /B115200 /o /N0 /A1 %1 %2 %3 %4 %5
StartPath=C:\WWIV\
... All below were left at default.
---

NF.BAT
---
C:\netfoss\netfoss.com &1
... All below were left at default.
---

launch net2bbs.exe.

And that is pretty much it. 4.30 should answer your Telnet calls right off.

Your next tasks will simply be to customize your messages and Subs.

---------------------------------------------------------------------------------------------------------------------------
Upgrading to WWIV v5 and the WWIV Telnet server

Upgrading to WWIV v5 takes a bit more work.

After downloading wwiv-bin-buildxx.zip, extract it over the 4.30 install only overwriting FILE_ID.DIZ
**wwiv-bin-build57.zip seems to be more stable than build 61**


Before launching the upgraded WWIV v5.x, you need to add the following lines to wwiv.ini


;=============================================================================
;                         WWIV v5.0 Additions
;=============================================================================
;
EXEC_LOGSYNCFOSS     = 1                   ;[ 1 | 0 ] - If non-zero then wwivsync.log will 
;                                          ;be generated.  The default setting is 1 and this
;                         		   ;is currently ignored.
EXEC_USECWAITFORIDLE = 1                   ;[ 1 | 0 ] - Under WindowsNT/2K/XP when launching
;                                          ;the child process WWIV uses WaitForInputIdle to wait
;                                          ;for the child process to process all normal input 
;                                          ;before starting the Fossil handling code.  Setting
;                                          ;this to 0 will disable that (acting like Win9x where
;                                          ;we just wait for a bit (See EXEC_CHILDWAITTIME).  The
;                                          ;default value of this is 1.
EXEC_CHILDWAITTIME   = 1000                ;(time to wait in milliseconds, this parameter is
;                                          ;only used on Win9X unless EXEC_USEWAITFORIDLE is
;                                          ;set to 0. The default value is 500 (1/2 second)
EXEC_WAITFORIDLETIME = 4000                ;(time to wait in milliseconds, only use
;                                          ;Windows NT/2K/XP unless EXEC_USEWAITFORIDLE=0).  
;                                          ;The default value for this is 2000 (2 seconds)
INTERNALZMODEM = 1			   ;[ 1 | 0 ] Turns interhal zmodem on & off
;
;
NEW_SCAN_AT_LOGIN = Y                      ; [ Y | N ] If you add this then when a user logs in they
;                                          ;           will be asked to scan all message areas for new
;                                          ; new messages
;
;=============================================================================
;                         END OF BBS SPECIFIC SETTING
;=============================================================================


Then after resolving an antivirus issue, WWIVTelnetServer actually started working and was able to receive a call via Telnet but then some odd glitches where every now and then WWIV50 would crash for a new caller.

I am now testing the entries right above where I added the new WWIV.INI entries to include the additional instances as follows:

;=============================================================================
;                        INSTANCE SPECIFIC OPTIONS
;=============================================================================
; There are only a very few settings that would or should be used for
; individual instances.  You may have an instance that does all network
; callouts or one that does all processing of Fido or other network mail.
; To define these instance specific settings, use an ID block [WWIV-<instance>]
; as follows:
;
; Instance #1
[WWIV-1]
NET_CALLOUT            = Y                 ; allow net callouts this instance
FIDO_PROCESS           = N                 ; process fido packets this instance
WFC_SCREEN             = Y                 ; Use ANSI WFC screen?
;
; Instance #2
[WWIV-2]
NET_CALLOUT            = N                 ; allow net callouts this instance
FIDO_PROCESS           = Y                 ; process fido packets this instance
WFC_SCREEN             = N                 ; Use ANSI WFC screen?
SCREEN_SAVER_TIME      = 120               ; Screen saver invoke time
;
; Instance #3
[WWIV-3]
NET_CALLOUT            = N                 ; allow net callouts this instance
FIDO_PROCESS           = Y                 ; process fido packets this instance
WFC_SCREEN             = N                 ; Use ANSI WFC screen?
SCREEN_SAVER_TIME      = 120               ; Screen saver invoke time
;
; Instance #4
[WWIV-4]
NET_CALLOUT            = N                 ; allow net callouts this instance
FIDO_PROCESS           = Y                 ; process fido packets this instance
WFC_SCREEN             = N                 ; Use ANSI WFC screen?
SCREEN_SAVER_TIME      = 120               ; Screen saver invoke time

(I have mine set to have 6 nodes)

Then run INIT50 ,1 ,e and INIT50 ,2 ,e (INIT ,x ,e for each node 'x' you want) to check and verify the modem settings then launch and adjust the WWIVTelnetServer.exe settings with the path of your install (c:\wwiv\wwiv50.exe)



.