ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng)/ProfitPress-MegaCDROM2.B6I/MISC/NETWORK/BLTS.ZIP/BLT16

Text File | 1990-06-21 | 22.3 KB | 612 lines

TECHNICAL BULLETIN
06.18.90 JCR

MULTI-TASKING - Windows, 3.0, Microsoft


Initial Comment
Windows 3.0 is a complex multi-tasking application, which offers a
variety of functions within network operation.  Because of this
complexity, our preliminary testing has been quite extensive and is
not yet complete. In addition, there are certain aspects of Windows
(network related) which do not function correctly with the LANtastic
network operating system.  These aspects include:

 - Running Windows 3.0 in enhanced mode on a server - this causes
   loss of network functionality, and in some cases, proves fatal to the
   network.

 - One must rely on NET Printer Management Queue to control network
   print jobs; the Printer Manager provided in Windows does not function
   with LANtastic

 - Windows 3.0 does not support the requirements for LANtastic Voice

 - Reports indicate that Artisoft's LANCACHE can not be run with Windows 3.0

We are currently working with Microsoft to provide the most
reasonable solutions, and I will update this bulletin as necessary.
This bulletin should replace all other notes generated from this
office on Windows 3.0 to date.  All other areas of testing to date
have proved successful.  Keeping these successes in mind, along with
the limitations, I have added Windows 3.0 to our compatibility list
(with the limitations noted).  While claiming Windows 3.0 and
LANtastic 3.x, are compatible, Artisoft is not responsible for the
compatibility of any other application(s) running within Windows
unless otherwise noted.

The following information is based on inhouse testing to date of
Windows.  If you are a registered user of LANtastic with a current
support policy, any technical questions may be directed to our
technical support staff.

Artisoft Inc.
575 E. River Road
Tucson, AZ  85704
[phone]


NETWORK INSTALLATION

Installing Windows 3.0
Windows 3.0 should be installed on the server with the network
already loaded, and should be installed following the procedures for
Microsoft NET.  While Windows 3.0 seems to function with either the
IBM PC LAN or MS NET driver, Microsoft recommends using the Microsoft
NET driver.

Windows creates several .INI files which contain various
configuration information:

CONTROL.INI          - Maintains color schemes and patterns
PROGMAN.INI          - Maintains group information
SYSTEM.INI           - Maintains system configuration
WIN.INI              - Maintains Windows configuration (devices, fonts, etc)
WINFILE.INI          - Maintains settings

When Windows 3.0 is installed with the network loaded using the
Microsoft NET driver, some modifications to the SYSTEM.INI and
WIN.INI files may still be necessary.  Copies of the entire files are
attached; the pertinent information from each file follows.

File Information, Cont.

SYSTEM.INI
[boot] section:
network.drv=msnet.drv   (configured during install for MS NET)

[386Enh] section:
EMMExclude=D000-D7FF  -exclude the RAMBASE address used by the Network adapter
NetHeapSize=76        -tells Windows the max buffer size in Kb required for
                       data transfer. The default value is 8; Microsoft's
                       initial test recommends 76
NetDMASize=            -tells Windows to provide buffer in Kb size for DMA.
                        Default is 32 on MicroChannel, 0 on all others
InDOSPolling=TRUE      -value should be TRUE, ON, YES or 1

* Note: The first three commands are additions to the [386Enh]
  section; each command requires a separate line.

WIN.INI
[ports] section:
LPT1.PRN=          -must be added to provide network printing redirection;
LPT2.PRN=           these files will be listed under Printer Ports in
LPT3.PRN=           Printer Configuration.

Note: These three lines must be added to the [ports] section; as
above, each command requires a separate line.  One does not need to
specify LPT2.PRN and LPT3.PRN if redirection to LPT2 or LPT3 is not
going to occur.

CONFIG.SYS
Windows will install any necessary devices in the config.sys file
during installation if prompted to do so.  The install program will
load any mouse or other specific devices, SMARTDRV.SYS and HIMEM.SYS
if applicable.  Windows requires an extended memory manager
(HIMEM.SYS) to run Windows in standard or 386 enhanced mode.

AUTOEXEC.BAT
As with config.sys, Windows will modify the Autoexec.bat during
installation if prompted to do so.  The installation adds Windows to
the PATH command and will add a SET TEMP= to the appropriate location
for Windows.

Configuration...
Once Windows has been installed, it may be configured individually
for each workstation on the network.  This procedures installs a
group of configuration files containing information about that
workstation's hardware configuration and startup options.  To run the
network setup, log into the network and change to the redirected
drive which contains Windows.  From that prompt run SETUP /N  (N is
the Network switch for Setup).

Windows will ask for a path\directory in which to install the local
files; the default is C:\WINDOWS.  Windows will then display an
initial configuration menu; if the selections shown are not correct
for that workstation, use the arrow keys to change each item.

Once the selections are correct, press enter to accept the changes
and Windows will copy the necessary files to the specified directory.
Once Windows has been installed, review the modifications as
necessary to the WIN.INI and SYSTEM.INI files in the local
workstation directory, and set PATH to include the redirected drive
designation for Windows, as well as the local workstation directory.

NETWORK OPERATION

Once Windows has been installed and configured, the user must log
into the server and share the directory which contains Windows.  From
that directory prompt, the user may run Windows in either of three
formats: WIN /S        Standard Mode: Provides access to extended
memory for 286-based systems or higher with at least 256K of extended
memory WIN /E        Enhanced Mode: Provides all standard mode
features for 386-based systems with at least 1MB of extended memory
plus: Virtual Memory, multiple virtual machines, configurable
time-slicing for DOS apps (to determine priority of execution) and
standard DOS apps can run in their own windows or full-screen NOTE:
Enhanced mode may also be activated by WIN /3.  WIN /R        Real
Mode: Base-level operating mode for 286/386-based systems with 640K
to 1 MB of memory.  Uses standard 640K conventional memory, standard
DOS and Windows apps can use EMS memory, and standard DOS apps run
full-screen in the foreground.

NOTE: We do not recommend running Windows 3.0 in enhanced mode on a
LANtastic server.

WIN will execute Windows in the most appropriate mode based on your
existing configuration.

The network should always be loaded prior to running Windows.  Once
Windows has been loaded, the user may execute a variety of network
functions. These functions can be handled through the DOS shell, a
PIF file or through Windows. The following is an outline of handling
these functions through Windows.  NOTE: If the user is not already
logged into the server, he may do so by running NET through the DOS
shell, the File Manager or a created PIF file.

Connecting a Network Drive
1.  The user must first be logged into the server containing the
    resource (If the user is not logged in, he may do so through the DOS
    shell or by running NET through the File Manager or through a created
    PIF file.
2.  From the MAIN group, select File Manager and pull down
    the Disk menu.
3.  Select Connect Net Drive
4.  Select the desired Drive Letter and enter the Network Path
    (ie \\SERVER\RESOURCE).
5.  Select Connect or press enter.
6.  The drive should now appear on the directory tree and NET should
    appear in the drive box.  Double click to access that drive.
    The bottom portion of the window indicates the full path name of
    the drive (\\SERVER\RESOURCE) and the available bytes on that drive.

Disconnecting a Network Drive
1.  From the MAIN group the user should select File Manager and pull
    down the Disk menu.
2.  Select Disconnect Net Drive and select the drive letter to be disconnected.
3.  The directory tree should now display any current connections.

Connecting a Printer
Our testing to date has produced a variety of results. It is
important to note that there are several functions involved; the
printer resource may be connected through a NET command in NOS, and
the port may be connected as a Network device in Windows.  The
printer driver itself in Windows can also be configured to any
designated port.

Print Manager
Windows has a Print Manager which has the capabilities of managing
network print jobs.  Any testing of this facility (as far as pausing
or disabling the manager) proved fatal to the print job, and in some
cases, to the network.  By establishing connections through Windows
to any network port, the manager did not operate and returned "A
General Network Error has Occurred" message.  By establishing
connections through NOS and configuring the printer drivers to a port
designated with .PRN (LPT1.PRN, LPT2.PRN etc), the job was redirected
to a file therefore bypassing the Printer Manager.  In this case the
Manager was not accessible, returning a "There are no printers
connected; run Control Panel to set up printers" message.

In both cases, the job did make it to the designated printer,
however, during preliminary testing, we were more successful when
establishing a link to the port through Windows and then configuring
the printer driver to that port (rather than a .PRN device).
Unfortunately, as this caused errors with the Printer Manager, it
also caused problems with local printing.

Keeping this in mind, when establishing connections to a printer, we
recommend the following:

1.  The user must first be logged into the server connected to the
    printer resource
2.  A link must be established to the printing device using NET
    through the DOS shell, any NET PIF file created, or prior to loading
    Windows.
3.  From the MAIN group, select Control Panel and select the Printers
    option. From the Printer menu, hi-lite the desired printer driver
    from the Installed Printers list and select the Configure option.
    Hi-lite the redirected port from the .PRN selections (LPT1.PRN,
    LPT2.PRN, etc.  If you do not see these ports listed under
    configuration, please review the installation notes regarding WIN.INI
    earlier in this bulletin).  Once in any application through Windows,
    pull down the File menu, select Printer Setup and select the printing
    device.

Printing to Local and Network Devices

1.  The user should have the network printer connected to a .PRN
    device as listed above.
2.  A printer driver should be installed for the local printer.
3.  From the MAIN group, select Control Panel and select the Printers
    option.  From the Printer menu, hi-lite the local printer driver from
    the Installed Printers list and select the Configure option.  Hi-lite
    the local port designation (do not select a .PRN device).  Once in
    any application through Windows, pull down the File menu, select
    Printer Setup and select the desired printing device.

Disconnecting Printers

1.  Since the initial connection of a printer can be done through the
application, the user may select a different printer device without
disconnecting the initial printer. The same holds true for changing
the driver; the user may run the Control Panel Printers program to
change the configuration of the printer port.

2.  If the user wishes to completely disconnect the device, he may
execute a NET command through the DOS shell or through a NET PIF
file.

Other Operations
LANtastic does not interfere with the normal operation of Windows;
one can share various network resources and run applications through
Windows with no apparent problems.

PIF Files
Whenever a non-Windows application is executed, Windows looks for
that application's Program Information File (PIF).  A PIF is a
special file containing settings that tell Windows how to run a
non-Windows application.  A PIF's filename usually matches that of
the corresponding application.  Once such a file has been created,
that application can started by double-clicking on the PIF filename.
It is not necessary to create a PIF for each non-Windows application.
Please refer to your Windows manual for more information.


SUMMARY

Avoiding Problems

Due to the complexity of Windows and the requirements for
installation, we can only provide brief recommendations to avoid
problems:

- Make sure Windows is installed using the Microsoft NET driver.
- To avoid addressing conflicts, ensure the network adapter RAMBASE
  (if applicable) has been excluded in the SYSTEM.INI file, and make
  sure there are no other memory conflicts.
- If Windows is running in enhanced mode on a workstation, make sure
  HIMEM.SYS has been loaded in the config.sys file.
- If Windows is a shared resource on the network, make sure SETUP /N
  has been run for each user and make sure each user has a path set to
  the local directory as well as the network directory for Windows.
- Make sure the NetBIOS and REDIR commands are being executed prior
  to loading Windows.
- If SERVER is loaded, make sure Windows is not being loaded in Enhanced mode.
- If printing problems occur; ensure the user has properly
  established all print connections and that the Print Manager has
  not been paused; this may cause a fatal network error.
- If the printing performance is not acceptable, optimize the printer
  configuration through LANtastic's NET_MGR program.  Since the program
  is printing through a file, a NET LPT TIMEOUT is not required.


TESTING

Equipment
We tested a version of Windows 3.0 directly from Microsoft, as well
as a version from CompuAdd.  Both yielded identical results, although
additional measures were necessary to install the version from
CompuAdd. In every case, follow the procedures outlined to install
Windows as a shared network resource for Microsoft NET. All other
procedures as listed in this bulletin remain the same.

Loading the Network
The network can be loaded through Windows (through DOS shell), but it
is recommended that the user have the network loaded prior to loading
Windows.

PROBLEMS ENCOUNTERED DURING TESTING

Below I have described all of the problems encountered so far with
Windows 3.0 and LANtastic.  As this is a continual process, this page
will be updated regularly until all problems have been resolved.

Running Windows 3.0 in Enhanced Mode on a Server
Windows 3.0 can be loaded in enhanced mode on a LANtastic server.
Some functionality is retained; the user can open multiple windows,
run non-Windows applications and shell to DOS.  When the user tries
to access any network function through the File Manager (for drive
connections), Control Panel (for printer connections), or by running
any LANtastic NET command (either through a PIF file or through the
DOS shell), a fatal network error may result.

While the server is running Windows 3.0 in enhanced mode, it is no
longer an available resource to the network.  Depending on operation,
when the user exits Windows on the server and returns to DOS, the
network resumes functionality.

Testing to date indicates that Windows 3.0 will run on a server in
Real and Standard mode; allowing the user to share drives and
printers through File Manager, Control Panel and through NET (either
through a PIF file or through the DOS shell).

Controlling Network Print Jobs through Print Manager
Windows provides a Print Manager, which handles network print jobs
very much like our NET Printer Queue Management application.  The
Print Manager does not need to be disabled, however, one cannot
manipulate network print jobs through the Print Manager.  If the
Manager has been paused (similar to our own NET QUEUE HALT); a
printing error will occur.

I have detailed more information about printing in the Connecting a
Printer section of this bulletin.

Running LANvoice with Windows 3.0
At this time Windows 3.0 does not support the necessary DMA
requirements to run LANvoice.  A detailed problem report has been
filed through Microsoft's ON-Line service by our engineering staff.

Running Lancache
Reports indicate that one can not run Artisoft's cache when running
Windows 3.0.  Further tests will be conducted to confirm reports, and
to determine cause of incompatibility and provide a solution.

Using Expanded Memory Managers
An expanded memory manager gives applications access to only a
limited amount of expanded memory at a time, and is slower to use
than extended memory. Therefore Windows uses expanded memory only
when running in real mode. (When running in 386 enhanced mode,
Windows can simulate expanded memory for applications that require it
using EMM386.SYS).  Windows requires that memory to conform to
version 4.0 of the Lotus-Intel-Microsoft Expanded Memory
Specification (LIM EMS 4.0).

If your applications require expanded memory with Windows in real
mode, the EMM386.SYS expanded memory emulator may be used.  When
using EMM386.SYS, it is important to note that one must exclude any
conflicting memory addresses.  The following is an example (the
EMM386.SYS file is loaded in the CONFIG.SYS file):

   device=emm386.sys x=d000-d7ff (Where D000-D7FF is the network
                                 adapter's RAMBASE)

In theory, the same should hold true for other expanded memory
managers, such Quarterdeck's QEMM or Qualitas' 386-To-The-Max.  We
are currently in the process of exploring these possibilities, and
will update this bulletin as necessary.

Using Extended Memory Managers
Extended memory is memory beyond 640K on 80286, 80386, and 80486
computers. It is an extension of your computer's conventional memory.
An extended memory manager is required in order to run Windows in
standard or 386 enhanced mode.  Windows includes the extended memory
manager HIMEM.SYS.  When running in Real mode, Windows uses extended
memory only for storing information.

NOTE: Summarized from the CompuAdd Windows User's Guide, Chapter 13:
Optimizing Windows.  Please refer to your manual for more information
on Memory Managers.

Once again, any questions should be forwarded to the appropriate
department (as described in the Initial Comments section).  The
following pages consist of System File information.

The following is a printout of all modified files:

CONTROL.INI
No modifications were made to this file;
it contains information on colors and patterns.

PROGMAN.INI
No modifications were made to this file;
it contains path information on groups.

CONFIG.SYS
shell=c:\command.com /e:1024 /p
device=c:\himem.sys
device=c:\dos\ansi.sys
break=on
files=30
buffers=20
fcbs=16,8
lastdrive=z
device=C:\WINDOWS\mouse.sys /Y
device=C:\WINDOWS\smartdrv.sys 768

AUTOEXEC.BAT
prompt [$p]
path c:\;c:\dos;c:\lantasti;c:\util;c:\winfiles;w:\windows
lanbios2 irq=15 iobase=dudu verbose
ne3 irq=3 verbose
ailanbio adapter=1 verbose
redir lab386 logins=15 verbose
share
server verbose

SYSTEM.INI
[boot]
386grabber=vga.gr3
286grabber=vgacolor.gr2
shell=progman.exe
network.drv=msnet.drv
language.dll=
fixedfon.fon=vgafix.fon
comm.drv=comm.drv
sound.drv=sound.drv
oemfonts.fon=vgaoem.fon
fonts.fon=vgasys.fon
mouse.drv=mouse.drv
keyboard.drv=keyboard.drv
display.drv=vga.drv
system.drv=system.drv
[keyboard]
subtype=
type=4
oemansi.bin=
keyboard.dll=
[boot.description]
network.drv=IBM PC LAN Program
language.dll=English (American)
keyboard.typ=Enhanced 101 or 102 key US and Non US
keyboards
mouse.drv=Microsoft, or IBM PS/2
display.drv=VGA
system.drv=MS-DOS or PC-DOS System


MULTI-TASKING: Windows 3.0: System
Files Pg(2 of 4)


SYSTEM.INI Cont.
[386Enh]
NETHEAPSIZE=256
EMMEXCLUDE=D000-D7FF
ebios=*ebios
display=*vddvga
keyboard=*vkd
mouse=*vmd
network=*vnetbios, *dosnet
device=*vpicd
device=*vtd
device=*reboot
device=*vdmad
device=*vsd
device=*v86mmgr
device=*pageswap
device=*dosmgr
device=*vmpoll
device=*wshell
device=*vhd
device=*vfd
device=*vpd
device=*parity
device=*biosxlat
device=*vcd
device=*vmcpd
device=*combuff
device=*cdpscsi
local=CON
FileSysChange=off
CGA40WOA.FON=CGA40WOA.FON
CGA80WOA.FON=CGA80WOA.FON
EGA40WOA.FON=EGA40WOA.FON
EGA80WOA.FON=EGA80WOA.FON
InDOSPolling=TRUE
[standard]
[NonWindowsApp]

WIN.INI
[windows]
load=
run=
Beep=yes
Spooler=yes
NullPort=None
device=HP LaserJet III,HPPCL5A,LPT1.PRN
BorderWidth=3
KeyboardSpeed=31
CursorBlinkRate=530
DoubleClickSpeed=452
Programs=com exe bat pif
Documents=
DeviceNotSelectedTimeout=15
TransmissionRetryTimeout=45
swapdisk=
NetWarn=1
[Desktop]
Pattern=(None)
Wallpaper=chess.bmp
TileWallpaper=1
GridGranularity=0
IconSpacing=75
[Extensions]
cal=calendar.exe ^.cal
crd=cardfile.exe ^.crd
trm=terminal.exe ^.trm
txt=notepad.exe ^.txt
ini=notepad.exe ^.ini

pcx=pbrush.exe ^.pcx
bmp=pbrush.exe ^.bmp
wri=write.exe ^.wri
rec=recorder.exe ^.rec

[intl]
sCountry=United States

[ports]
; A line with [filename].PRN followed by an equal sign causes
; [filename] to appear in the Control Panel's Printer Configuration dialog
; box. A printer connected to [filename] directs its output into
this file.
LPT1:=
LPT2:=
LPT3:=
COM1:=9600,n,8,1
COM2:=9600,n,8,1
COM3:=9600,n,8,1
COM4:=9600,n,8,1
EPT:=
FILE:=
LPT1.OS2=
LPT2.OS2=
LPT1.PRN=

[Windows Help]
Xl=169
Yu=125
Xr=576
Yd=428
Maximized=0
[fonts]
Symbol 8,10,12,14,18,24 (VGA res)=SYMBOLE.FON
Helv 8,10,12,14,18,24 (VGA res)=HELVE.FON
Courier 10,12,15 (VGA res)=COURE.FON
Tms Rmn 8,10,12,14,18,24 (VGA res)=TMSRE.FON
Roman (All res)=ROMAN.FON
Script (All res)=SCRIPT.FON
Modern (All res)=MODERN.FON
[HPPCL5A,LPT1]
paper=1
duplex=0
prtcaps=-13440
paperind=0
FontSummary=C:\WINDOWS\SYSTEM\FSLPT1.PCL
prtresfac=2
[PrinterPorts]
HP LaserJet III=HPPCL5A,LPT1.PRN,15,45
[devices]
HP LaserJet III=HPPCL5A,LPT1.PRN
[Solitaire]
Back=3
Options=89
[HPPCL5A,LPT1.PRN]
paper=1
duplex=0
prtcaps=-13440
paperind=0
FontSummary=C:\WINDOWS\SYSTEM\FSLPT1.PCL
[SciCalc]
layout=0

[Settings]
SaveSettings=1
MinOnRun=0
Replace=0
LowerCase=0
StatusBar=1
CurrentView=0
CurrentSort=201
CurrentAttribs=1841