LANtastic(r) and Windows(tm) for Workgroups Networks

An addendum to the 11/92 Comparison documet Sales Guide
 
Since its release of Windows(tm) for Workgroups has been the subject of 
many reviews and product comparisons.

"Windows for Workgroups evokes fear and loathing in IS 
corridors... Since WFW will be widely available in retail stores, 
it's likely that users will buy the product and try to install it 
themselves.  However, installation is a matter best left to a LAN 
administrator, according to many WFW beta testers.
PC Week, October 26, 1992

A number of published articles report that the initial sales and acceptance 
of Windows(tm) for Workgroups have not meet Microsoft's expectations.  This 
hangup in the acceptance of Windows for Workgroups presents an opportunity 
for Artisoft resellers to demonstrate the LANtastic(r) system to end users.  
These endusers may be those who are considering Windows for Workgroups 
or those who have purchased Windows for Workgroups but are dissatisfied 
with its performance, functionality, or the limitations it place on some PC 
hardware types (XTs, ATs).

The tremendous amount of advertising that Microsoft has done for Windows 
for Workgroups has also raised end user awareness of the benefits of 
networking.  We can take advantage of this heightened awareness to place 
LANtastic into additional sites.

The November 12, 1992 Wall Street Journal highlighted some of the 
drawbacks of Windows for Workgroups.

     "On the videotape, which lasts 15 minutes, this process 
[setting up the network] looks trivial.  By the end, two actors not 
only have networked a pair of PCs, but are happily exchanging E-
mail.
     "This isn't possible.  In my own case, it took about three 
hours and a call to Microsoft to get everything running right.  And 
that may understate the time required, because I've done this sort 
of thing before...
     "Windows for Workgroups has other drawbacks.  Its 
pricing is confusing.  Six versions, ranging from $60 to $630 in 
discount stores....
     "However, Windows for Workgroups has an even bigger 
drawback:  It works fully only on PCs running Windows.  In fact, 
it's a part of Microsoft's basic strategy to promote Windows as the 
universal way of running PCs.  But most PCs still rely on the older 
MS-DOS operating system.  These computers can only be 
connected via a $70 add-on product, and even then they can 
merely use files on Windows machines; they can't share their own 
files with Windows or DOS machines.
     "If you are in this majority of PC owners and want to set up 
a simple network, you would do well to consider instead the 
current market leader in the field, LANtastic, by Artisoft, Tucson 
Ariz.  This product runs on DOS and Windows, costs about the 
same as Microsoft's entry and is relatively simple to set up."

This recommendation has special impact because the Wall Street Journal is 
not a computer industry publication, but is a highly respected business 
publication, that owes no allegiance to major computer companies with large 
advertising budgets.

Using components of Windows for Workgroups with the LANtastic system

Since the release of Windows for Workgroups, Artisoft has done some testing 
of the product.  Here are some of our findings:

oWindows for Workgroups can use all Artisoft's "AE" boards when they are 
set in the NE2000 mode.

oThe mail and schedule features of Windows for Workgroups will work under 
the LANtastic system.  This is accomplished by removing the workgroups 
network from Windows for Workgroups with the result being regular 
Microsoft Windows with the Mail, Schedule+ and a toolbar for File 
Manager.  This is accomplished by modifying the Windows SYSTEM.INI file 
and the CONFIG.SYS file.

oWindows for Workgroups will not work under LANtastic.  It has its own 
REDIR and SERVER and low level drivers which are not compatible with the 
LANtastic system.

To replace a Windows for Workgroups network with a LANtastic network 
change the SYSTEM.INI file as follows:

[Boot]
Replace
network=wfwnet.drv
with:network.drv=lantnet.drv
[386Enh]
Delete all but vnetbios.386 from below line
network=vnetbios.386,vnetsup.386,vredir.386,vserver.386,vbrowse.386,vwc.386
replace with:network=vnetbios.386,lantasti.386

Replace
NetHeapSize=20
with:NetHeapSize=64

After you have made the above changes you need to add the following to the 
SYSTEM.INI file

[386Enh]

Add
NetAsynchFallback=TRUE
NetAsynchTimeout=5.0
PerVMFiles=0

[LANtastic]
Network_IRQ=(15) (appropriate IRQ setting for that machine)

After these changes have been made you have Windows 3.1 with the 
following additions:
     Mail
     Schedule+
     Network File Manager
     ClipBook (this includes the original ClipBoard)  The ClipBook Viewer 
     will work locally, however it will not share the file across the
     network

After these changes are made, the following Windows for Workgroups 
functions will not work:
     
     NetDDE Programs (The LANtastic for Windows DDE feature will function.)
          Chat
          Hearts (game)
     VSERVER.386 programs
          NetWatcher
          WinMeter

The Intel EtherExpress 16Bit network interface card that ships with Windows 
for Workgroups will work with LANtastic A/I(tm).  The driver used is 
EXP16LAN.EXE.  It was developed by Intel Corporation.  Version 2.01 of 
the driver was tested with LANtastic/AI v4.1 and was found to be compatible, 
except when trying to configure multiple adapters on one computer.  In this 
case, frequent disconnects were encountered.  The EXP16LAN.EXE driver is 
not yet included in the LANtastic/AI standard distribution diskette.  Users 
can download the driver by calling Intel's BBS at 503-645-6275 or Artisoft's 
BBS at 602-293-0065.  Version 2.01 of EXP16LAN.EXE is not backward
compatible with earlier versions of LANtastic/AI. and does not currently work 
on XT machines.  This is not a problem in a Windows for Workgroups 
situation, since WfW cannot be installed on an XT machine.  For other types 
of adapters, you should check the current compatibility list on Artisoft's 
BBS. If Windows for Workgroups was loaded using the Intel EtherExpress(tm) 
adapter cards, you must also remove the low level drivers from the 
CONFIG.SYS file.



Listed below is an example of the SYSTEM.INI file after the changes have 
been made:
   SYSTEM.INI:
     [boot]
     shell=progman.exe
     mouse.drv=mouse.drv
    +   network.drv=lantnet.drv
     language.dll=
     sound.drv=mmsound.drv
     comm.drv=comm.drv
     keyboard.drv=keyboard.drv
     system.drv=system.drv
     386grabber=vga.3gr
     oemfonts.fon=vgaoem.fon
     286grabber=vgacolor.2gr
     fixedfon.fon=vgafix.fon
     fonts.fon=vgasys.fon
     display.drv=vga.drv
     drivers=mmsystem.dll
     SCRNSAVE.EXE=(None)
     [keyboard]
     subtype=
     type=4
     keyboard.dll=
     oemansi.bin=
     [boot.description]
     keyboard.typ=Enhanced 101 or 102 key US and Non US keyboards
     mouse.drv=Microsoft, or IBM PS/2
     network.drv=Microsoft Windows for Workgroups (version 3.1)
     language.dll=English (American)
     system.drv=MS-DOS System
     codepage=437
     woafont.fon=English (437)
     aspect=100,96,96
     display.drv=VGA
     [386Enh]
     32BitDiskAccess=OFF
     device=*int13
     device=*wdctrl
     mouse=*vmd
    +   network=vnetbios.386,lantasti.386
    ++  PerVMFiles=0
    ++  NetAsynchTimeout=5.0
    ++  NetAsynchFallback=TRUE
     ebios=*ebios
     woafont=dosapp.fon
     display=*vddvga
     EGA80WOA.FON=EGA80WOA.FON
     EGA40WOA.FON=EGA40WOA.FON
     CGA80WOA.FON=CGA80WOA.FON
     CGA40WOA.FON=CGA40WOA.FON
     keyboard=*vkd
    +   netheapsize=64
     device=vtdapi.386
     device=vcd.386
     device=vshare.386
     device=vpicd.386
     device=vpd.386
     device=*vtd
     device=*reboot
     device=vdmad.386
     device=*vsd
     device=*v86mmgr
     device=*pageswap
     device=*dosmgr
     device=*vmpoll
     device=*wshell
     device=*BLOCKDEV
     device=*PAGEFILE
     device=*vfd
     device=*parity
     device=*biosxlat
     device=*vmcpd
     device=*combuff
     device=*cdpscsi
     local=CON
     FileSysChange=off
     PermSwapDOSDrive=C
     PermSwapSizeK=7786
     transport=vnb.386
     device=VASBID.386
     [standard]
     netheapsize=8
     [NonWindowsApp]
     localtsrs=dosedit,ced
     CommandEnvSize=1024
     [mci]
     WaveAudio=mciwave.drv 4
     Sequencer=mciseq.drv 
     CDAudio=mcicda.drv
     [drivers]
     timer=timer.drv
     midimapper=midimap.drv
     wave=sndbrd.drv
     [DDEShares] 
     [network]
     ComputerName=DAN
     Workgroup=WORKGRP
     UserName=
     [ClipShares] 
     [sndbrd.drv]
     NumAdapters=1
     InDMA.1=1
     OutDMA.1=3
    ++  [LANtastic]
    ++  Network_IRQ=15

+  Lines that have been changed
++ Lines that have been added

Should you have any questions concerning the conversion of Windows for 
Workgroups networks, call Artisoft technical support, at 602-293-6363.  
Select number three for the technical support queue, and then number one for 
the Windows support queue.

(C)1992 Artisoft, Inc. All rights reserved.  Artisoft and LANtastic are 
registered trademarks and LANtastic/AI a trademark of Artisoft, Inc.  
Windows is a trademark of Microsoft Corp.  Other company, brand and 
product names are the property and/or trademarks of their respective 
companies.
