Installing Windows 3 in a Network
Environment
We have recently discovered a problem when using the Windows 3
"SETUP" program with its "/N" option (in the method described in IPB
2049) on a network workstation.
When "SETUP /N" is executed at the network workstation the
result is either the error message :-
"PROGRAM TOO BIG FOR MEMORY"
or
the workstation "HANGS" during the early stages of the
"SETUP /N" procedure with either a blank screen or with one of the first few
information screens displayed.
This situation is caused by a "Clash" between the Windows 3
Mouse Driver, which is using interrupt request level 3 (IRQ3), and other adapter cards
that are also using IRQ3, such as a Western Digital Ethernet (WDE) Adapter Card.
Possible Solutions :-
- If using Windows 3, in the above fashion, then IRQ3 should be avoided.
IRQ5 and IRQ7 are both usually available therefore when using a WDE Card change it to use
IRQ7.
- The above situation is particularly relevant for XEN-S users who have a
mouse connected to COM2 with "MOUSE.SYS" placed in "CONFIG.SYS", as
this combination utilises IRQ3. It should be noted that Windows 3 has its own in-built
mouse driver, therefore if a mouse is only used with Windows 3, "MOUSE.SYS" is
not required and should be removed from "CONFIG.SYS". If a mouse is used with
non-windows applications, such as MS-WORD or AUTOCAD, then the mouse could be connected to
COM1 instead.
- A further alternative is to substitute "MCAMOUSE.SYS" for
"MOUSE.SYS". This is valid even on an AT type machine because
"MCAMOUSE.SYS" is not, as its name suggests, exclusively for use on MCA
machines, but is an enhanced version of LOGITECH's AT mouse driver with extensions for MCA
machines added.
----------oOo---------- |
