Category : Alternate Operating Systems - Quarterdeck DesqView, CP/M, etc
Archive   : QMTEK601.ZIP
Filename : NWORK.TEC

ID:NW Networks, Setting up DESQview
Quarterdeck Technical Note #154
by Dan Sweeney


The most common questions:

Q: Can I run DESQview on my network?

A: Yes, though DESQview is not truly a network-aware program*. DESQview
interfaces with a network as if it were just another hardware device
such as a hard disk, modem, or printer. Simply load the network shell
and start DESQview.

*DESQview does make Novell and IBM PC LAN API calls for compatibility
purposes (DESQview checks for these networks when it loads).

Q: How many people can use a copy of DESQview on the network?

A: Quarterdeck Office Systems requires one purchased copy for each
individual that will be using our software. Currently there is no site
license policy. This requirement applies for all Quarterdeck Office
Systems products.

Q: Can I run my network file server software in a DESQview window?

A: No. Network operating systems are not DOS programs. The network
operating system would have to be specifically written for this purpose.

Q: Can I run my network file server software and then load DESQview?

A: This depends on the quality of the DOS emulation of the file server
software. It is possible to run DESQview after the server software has
been loaded with most Peer to Peer Networks.

Q: Can I load my workstation network shell in a DESQview window?

A: If the network shell program has been specifically written for this
purpose--Novell's Network Access Server's IPX.SYS and NET3.COM, for
example--the answer is yes. Some of our users report loading other
network shells in a DESQview window with some success. As a general
rule, loading non-DESQview specific network shells within a window is
not recommended. The reasons are that network shells are actually
interrupt arbitrators, re-directors, and/or repeaters. Depending on the
shell configuration (and the application software) intended to run in
the window, two primary factors must be considered.

1. A packet may arrive for the workstation while this window is not the
current task. The network must retry sending the packet, causing network
performance degradation (or the network may timeout and drop the work-
station).

2. Only that window would be able to see the network. Loading the network
shell in more than one window can also confuse the network unless the
shell has been specifically written for this purpose.

Q: Do I need to reconfigure my network card for DESQview?

A: It will probably not be required, but when running DESQview with an
exPANDed memory it can be very advantageous to do so. If your network
card places ROM and/or RAM in the reserved memory area (between 640K and
1024K), you should locate the ROM and/or RAM to create large contiguous
free blocks of high memory. Knowing the locations of these items can be
very useful in troubleshooting memory conflicts as well. DESQview can
use exPANDed memory to load itself into the unused areas. Large
contiguous blocks of memory allow DESQview to place more of its code
"high," leaving more available conventional memory for other programs.
In addition, Quarterdeck's HIRAM.SYS and LOADHI.COM utilities can map
RAM into these locations (if your hardware supports the EMS 4
specification), and you can then load small TSR programs like network
drivers, buffers, and files in this area rather than in conventional
memory.

Q: What kind of memory conflicts happen in this area with networks?

A: Most exPANDed memory drivers are loaded prior to the network shell. If
the shell initializes a RAM buffer in reserved memory after the memory
driver, it is quite possible that the EMS driver won't know about the
RAM buffer. When an application tries to use exPANDed memory it may
overwrite the RAM buffer causing various problems. Symptoms range from
network access failure to all-out system crashes.

Q: How can I tell where these locations are?

A: The best bet is to check the network card documentation. If you can't
locate it, consult the manufacturer of the card. It is best to know
these addresses in hexadecimal numbers.

Q: So how do I prevent memory conflicts?

A: Most exPANDed memory managers have the ability to exclude certain areas.
QEMM 50/60 and QEMM 386 both have this feature. After determining the
starting and ending address, place a parameter on the QEMM line of your
CONFIG.SYS file as listed below:

DEVICE=C:\QEMM.SYS EXCLUDE=XXXX-YYYY

The XXXX should be replaced with the starting hexadecimal address and YYYY
should be the ending address.

Q: Can I login as a different user in each window?

A: As the network shell is loaded before DESQview, logging in as a
different user in each window may cause problems. In the case of Novell
Netware, the IPX can only support one username per card. When this is
done, the previous username and network access rights are replaced with
the current rights assigned to the username you use. If you are using
the IPXSPX.SYS that is supplied with Novell's Remote Access Server
product, you can in fact login as different users in different windows.

Q: Can I change or set search maps in different windows?
A: Yes, but... The search mapping facility set in the last window becomes
the global search map for the workstation. Programs running in other
DESQview windows may fail if they are using a different map.

Q: Can I map drives in a DESQview window?

A: Yes. In DESQview 2.26 you can map network subdirectories or volumes to
drive letters. The new map takes effect globally, so use with caution.

Q: Can I load the network shell above 640K with QRAM?

A: Yes, provided you have EEMS or EMS 4.0 HARDWARE and SOFTWARE (and a
large enough contiguous area to load them in).

Copyright (C) 1991 by Quarterdeck Office Systems
* * *E N D O F F I L E * * *