From: xmbs_gh@debet.nhh.no
Newsgroups: vmsnet.networks.desktop.pathworks
Subject: Re: Windows for Workgroups
Date: 13 Nov 92 01:17:30 GMT
Organization: MBS Fjerndata a.s Bergen, Norway

In article <5CD5AA5740200242@UMBCADMN.BITNET>, GREG BEAN 410-455-2580 <MIS9000@UMBCADMN.BITNET> writes:
> Greetings!
>  
> There have been a few messages posted that indicated limited success with
> the installation of Windows for Workgroups and Pathworks. What specifics
> can you offer on your configuration? What version of Pathworks are you using?
> Are there limitations with the enhanced redirector? What choices did you make
> in the WFW setup? What mods to config.sys, etc.? What services do you add,
> what do you lose?
>  

First of all: It works!

We've been beta-testing WFW for about 3 months before release. It took
some work, but we got it to work with the following configuration:

(Compaq) DOS 5.0
QEMM V6.02
PATHWORKS for VMS V4.1-1
PATHWORKS for DOS V4.1 (using DECnet as the PW client transport)
WFW

Here's what we did:

1) Install standard Windows 3.1
2) Install PW (netsetup) and select FULL LANMANAGER REDIRECTOR
3) Run WIN3SETU, but forget the added path in AUTOEXEC.BAT
4) Upgrade Windows 3.1 to Windows for Workgroups 3.1
5) Prepare your editor!

WFW modifies your system files and creates a new PROTOCOL.INI in
\WINDOWS. Here's what you have to fix:

Make sure that you load PATWORKS' PROTMAN.SYS in CONFIG.SYS, but use the
PROTOCOL.INI that WFW creates. For example, here's my CONFIG.SYS (note
that I've installed WFW in D:\WINGROUP and DECnet in D:\DECNET. You
would probably use C:\WINDOWS and C:\DECNET)

DEVICE=D:\QEMM\QEMM386.SYS RAM I=F000-F6FF FRAME=NONE
DEVICE=C:\DOS\DISPLAY.SYS CON=(,850,2)
DOS=HIGH,UMB
COUNTRY=47,850,C:\DOS\COUNTRY.SYS
BUFFERS=20
FILES=30
shell=C:\command.com /E:512 /P
STACKS=9,256
device=D:\QEMM\LOADHI.SYS /r:1 D:\DECNET\laddrv.sys /D:2
DEVICE=D:\DECNET\PROTMAN.SYS /I:D:\DECNET
device=D:\QEMM\LOADHI.SYS /r:3 D:\WINGROUP\workgrp.sys
DEVICE=D:\WINGROUP\DEPCA.DOS
device=D:\WINGROUP\msipx.sys
lastdrive=P

Note that LASTDRIVE=P is because I also connect to a Novell Netware
server and allocate the drives Q-Z to Novell.

Also note that I've copied WFW's PROTOCOL.INI to D:\DECNET for
simplicity. Next you will have to modify PROTOCOL.INI. Add to the end of
the file:

[DATALINK]
DRIVERNAME   = DLL$MAC
LG_BUFFERS   = 16
SM_BUFFERS   = 6
OUTSTANDING  = 32
HEURISTICS   = 0
BINDINGS     = MS$EWLC
;Specify IRQ level used by workstations network adapter
NI_IRQ       = 3

This entry is copied from PW's PROTOCOL.INI, and _added_ to the end of
WFW's PROTOCOL.INI. I have "BINDINGS = MS$EWLC" because I use DEC's
EtherWorks LC network card (selected during the installation of WFW).
Make sure that you specify BINDINGS in the [DATALINK] section just like
in the [MS$NETBEUI] section at the beginning of PROTOCOL.INI (take a
look in the PROTOCOL.INI created by NETSETUP for hints).

One of the big changes in WFW is that it takes care of much of the
network software, including the redirector. In other words, you should
_not_ start the redirector before you start Windows, as WFW takes care
of this! The downside of this is that you cannot connect to a file (or
printer) service (except Novell Netware services and LAD disks) unless
Windows is running.

Personally I got rid of STARTNET.BAT altogether and created my
own NETT.BAT:

@echo off
break on

D:
cd \decnet
rem Starting PATHWORKS specific stuff: DECnet etc.
D:\DECNET\dllndis
D:\DECNET\netbind
D:\DECNET\schk /H
loadhi D:\DECNET\dnneth.exe /rem:2
loadhi /r:2 D:\DECNET\last /N:BAPC08 /c:d /M:D /g:-1
loadhi /r:2 D:\DECNET\lad.exe /R:-1 /W:-1 /a:-1
loadhi /r:1 D:\DECNET\lat
D:\DECNET\cterm

rem Starting Windows for Workgroups specific stuff: IPX
loadhi /r:4 D:\WINGROUP\msipx
D:\WINGROUP\netx
echo.
rem Logging on to the Novell LAN
Q:LOGIN gunnar_h

echo.
echo You're running Netbeui, IPX, DECnet, LAST, LAD and LAT!
echo.

Note that I've skipped all the error-checking in STARTNET.BAT. You might
not want to do this...

My AUTOEXEC.BAT is not too special. I set up the display, keyboard and
path, call NETT.BAT (above) and finally start Windows for Workgroups.
Before you can start Windows however, you will have to take a look at
SYSTEM.INI (in your Windows directory). Please note the following:

Under the [386Enh] section you need the following:

netheapsize=24
DNETHeapSize=64
network=vnetbios.386,vnetsup.386,vredir.386,vserver.386,vbrowse.386,vdnet.386

Put DNETHeapSize in front of network=...
You will have to manually add ",vdnet.386" to the end of the network=
line in order to get full support for DECnet (FAL, NFT and so on).

That's it!

Using this setup I'm able to connect to PW for VMS file & print, PW for
OS/2 file & print, PW for Ultrix file & print and Novell Netware file &
print services. I have to connect to LAD disk either before WFW is
started or from a DOS Window after WFW is started because FileManager is
not willing to accept switches (/V) or connections without nodename when
making network connections. I can also use LAT and CTERM for terminal
emulation.

Limitations:

As I've noted, the network is mostly unavailable before you start
Windows. If you want to use the BroadCast Receiver under Windows you
will have to do this manually every time you reboot your PC:

1) Boot and start the network without loading the RCV TSR. This because
the machine name is not yet set, and RCV will not load. Do not attempt
to run SETNAME as this will confuse WFW!
2) Start WFW and log on to the LAN.
3) Exit WFW.
4) Run RCV (which will now load as the machine name is set).
5) Start WFW and start the Windows BroadCast Receiver.

Also you will most likely have to get aquainted with QEMM or some other
memory manager. You really need every byte you can squeeze out of the
640K area (base memory). Remember you will have to load a whole lot of
drivers and TSRs to make this work!

If you get "Out of memory" errors when you access the network from WFW
try juggling with the two parameters "netheapsize" and "DNETHeapSize" in
SYSTEM.INI (but don't set them too high! Experiment!). Also make as much
memory as possible available under 640K.

Finally: No guarantees or anything, but this setup has worked like a
dream for me for the past three or four months. I'm not looking back,
WFW is a great product and MS Mail, Scheduler+ and Chat makes it even
greater!

Note: "Windows" means Windows for Workgroups except where specifically
noted "Standard Windows" which means Windows 3.1.

Disclaimer: I do not represent Microsoft or Digital Equipment
Corporation and my views are mine alone!

Gunnar

/------------------------------------------------------------------------------\
| Gunnar Helliesen, Sen. Systems Cons., MBS Fjerndata a.s, Bergen, Norway      |
| INTERNET: xmbs_gh@debet.nhh.no        PHONE: Intl + 47 5 34 38 00            |
| From APPLELINK: add "@INTERNET#"      FAX: Intl + 47 5 34 56 90              |
|------------------------------------------------------------------------------|
| "The Universe is old enough and big enough to take care of itself"           |
|  - Douglas Adams in 'The Hitchhikers Guide to the Galaxy'                    |
\------------------------------------------------------------------------------/
Newsgroups: vmsnet.networks.desktop.pathworks