6-23-94
README FOR 386/MULTIWARE 4.21
ALLOY COMPUTER PRODUCTS
For all your Networking and Data Storage Needs !
Alloy Sales / Support Contact Numbers:
VOICE (03) 574 9891 DEALER / DISTRIBUTOR SALES
VOICE (03) 574 9044 DEALER / DISTRIBUTOR TECHNICAL SUPPORT
VOICE (900) 680-2556 END USER SUPPORT
FAX (03) 561 7412 SALES
FAX (03) 561 4611 TECHNICAL SUPPORT
BBS (03) 560 3902 14400, 8, 1, N (24 HOURS)
** LINKPC USERS: LINKPC VERSIONS 3.1 AND BELOW NO LONGER SUPPORT FILE
TRANSFERS WITH THIS VERSION OF 386/MULTIWARE. A NEW NETLINK.COM IS LOCATED
IN THE \NX386\UTILS SUBDIRECTORY. COPY IT TO YOUR DEFAULT LINKPC
SUBDIRECTORY THAT YOU CHOSE DURING THE INITIAL INSTALLATION OF LINKPC. THE
DEFAULT IS \NETLINK. Version 3.2 of LINKPC is fully compatible.
*** NEW FEATURES IN MW386 4.21 ***
1. Limits password attempts.
*** NEW FEATURES IN MW386 4.20 ***
1. Added new default DOS task 1 sizes to be 704K and 736K for MDA/HGC
and CGA respectively.
2. Added support for SERVER COM 3 + 4. IRQ'S CAN NOT BE SHARED. These new ports
are available as physical ports NOT logical ports.
MODIFY THE "DEVICE=SER_DRVR.SYS" LINE IN THE NX386.CFG IN THE FOLLOWING MANNER;
DEVICE=SER_DRVR.SYS P3:3E8 I3:X P4:2E8 I4:Y
where P3 stands for COM3 at the base port address 3E8 HEX
where P4 stands for COM4 at the base port address 2E8 HEX
where X and Y are the IRQ's you picked in setting up your board.
3. ADDED TERMINIT SUPPORT.
Create a file in the NX386\MACHINE.000 subdirectory for remote users called
TERMINIT.Uxx (WHERE xx IS THE USER #). This file will automatically send
the codes stored in it to the modem connected to your terminal port at boot
time. @W is a special MW386 code to wait a second before processing the
next code, this may be required with some modems.
EXAMPLE OF THE CODES RECOMMENDED IN MODEMS.DOC (LOCATED ON THE ROOT) FOR MOST
MODEMS.
TERMINIT.U01 (FILE NAME FOR USER #1)
@WAT&F (RECALL FACTORY DEFAULTS)
@W&C1 (FOLLOW THE TRUE STATE OF CARRIER DETECT)
@WE0 (DISSABLE CHARACTER ECHO)
@WQ1 (DO NOT RETURN RESULT CODES)
@WS0=1 (AUTO ANSWER ON FIRST RING)
4. ADDED THE ABILITY TO LOAD MULTIPLE TERMINAL DRIVERS ON IMP2.
(TEXT, COLOR TEXT)
5. ADDED ABILITY TO LOAD MULTIPLE TERMINAL DRIVERS ON IMP8-R.
(TEXT, COLOR TEXT)
6. INCREASED BAUD RATE OF SERIAL DRIVER TO 115K.
7. NOW ALLOW SCSI DEVICES OTHER THAN HARD DISKS TO BE DAISY CHAINED TO THE
ADAPTEC 154X AND 164X.
8. MW386 now supports MS-DOS 6.0 & 6.2.
9. CHANGE TO EMMDEV FOR UMB SUPPORT.
Several changes to UMB checking. The following areas are reserved for the
purposes stated. If you try to include them you will receive an UPPER or
LOWER BOUNDS CONFLICT depending were the conflict is. You are free to
include any of the area's not reserved. The process is very similiar to
the MS-DOS EMM386 includes with the exception of the following.
1. ALL AREAS ARE EXCLUDED BY DEFAULT.
2. THE FIRST ADDRESS SPECIFIED IS THE STARTING ADDRESS.
3. THE SECOND ADDRESS SPECIFIED IS THE FIRST ADDRESS NOT UTILIZED.
EXAMPLE;
DEVICE = C:\NX386\DOS\EMSDEV.SYS A000-B000 B100-C800 C900-F000
THIS WILL GIVE YOU THE MAXIMUM AVAILABLE UMB'S ON A MDA TERMINAL. IF YOU ARE
USEING THE 704K OR 736K TASK SIZES THE A000 & B000 AREAS WILL NOT BE AVAILABLE
AS THEY WOULD HAVE ALREADY HAVE BEEN MAPPED INTO CONVENTIONAL USAGE.
MDA B000-B100 4K
HGC B000-C000 (host) B000-B800 (terminals) 64/32K
CGA B800-BC00 16K
EGA-VGA A000-C000 and C000-C800
System BIOS F000-FFFF (AT) or E000-FFFF (PS/2)
386/MultiWare BIOS C800-C900.
10. Change spooler default to NO BANNER or FORMFEED.
11. Support for VESA LOCAL BUS IDE controllers.
12. NEW TERMINAL DRIVER - VT220
TERM386.220
386/MultiWare VT220 Driver
Notes on version (v 1.00) of the VT220 terminal driver for 386/MultiWare.
Unlike the so-called PCTERM devices normally used on 386/MultiWare systems,
ASCII terminals generate one or more ASCII characters when a key is
depressed, rather than the keyboard scan-codes expected by the PC
BIOS and those applications which interface directly with the keyboard
controller. Consequently, one of the main tasks for a driver of this
sort is to translate ASCII strings from the terminal into the equivalent
scan-code sequence for processing by the host. In addition, many
keystroke sequences which are widely employed by PC applications (e.g.,
CTRL F1, Shift F1, etc.) produce no output at all when done on an ASCII
terminal, so they must be emulated by some other type of key sequence.
The keyboard mapping conventions for this driver are shown below.
Note: To maintain functionality with modems and remote terminals, the
VT-220 driver requires a carriage return to be received before the
driver becomes active. (ie; hit <cr> to 'wake it up')
Mapping of VT220 keyboard into IBM PC.
PC Key Equivalent VT220 Key or Key Sequence
------ ------------------------------------
Esc F11
Ctrl PF3, followed by second key in the sequence.*
Alt PF4, " " " " " " "
Left Shift PF2, " " " " " " "
Right Shift PF1, " " " " " " "
Home Find
End Select
Insert Insert Here
Delete Remove
Page Up Previous Screen
Page Down Next Screen
F6 thru F10 F6 thru F10
F1 thru F6 F16 thru F19 (F16 is marked Help, F17 is Do)
(*) Note:
The scope of Control, Alternate, and Shift keys will cover the
next normal key only. Once a valid key has been entered, the shifted
state will automatically be released. The shifted state can also be
released by hitting the Remove/Delete key or the F11/Esc key.
Special Hot Key Mappings.
F3 - VT220 Setup
F5 - Resets Terminal, 'reboots' user task.
F14 - Brings up 386/MultiWare Task Manager/Setup Screen.
(Same as AltF9)
F20 - Brings up 386/MultiWare Spooler
Special treatment of VT220 keys
Remove key -- if the terminal is in one or more of the shifted
states, the Remove key will just release all the shifted states.
If not in any shifted state, Remove maps to the DOS task as a
DELETE scan code.
Return key -- treated as Enter key (new line mode is off).
-----------------------------------------------------------------------
13. File XFER via LINKPC is now supported on MW386 EZ.
14. Hardware flow control with MW386 EZ is now supported.
15. Baud rates of 57.6k are now supported on IMP2'S, IMP8'S, IMP8-R'S &
COM PORTS (MW386EZ TERMINAL PORTS).
NOTE: 57.6 K ON EZ TERMINAL PORTS REQUIRES 16550 UARTS.
*** New Features in 386/MultiWare 4.10 ***
1. Exceeding 16 meg of ram with 2 IMP8Rs:
Memory expansion on ISA-bus (AT-style) systems - Many users have
requested that we somehow make it possible to configure larger main
memories in their 386/MultiWare host systems without causing
conflicts with the dual-ported 'memory windows' on their IMP
cards. This has always been possible for those systems which use
only IMP2 cards, because both of the 32 KB IMP2 memory windows
are always located below 1 MB, (at D0000h or D8000h) leaving all
of the memory space above 1 MB free for main memory. Similarly,
a system with only one IMP8R card would have no constraint on
main memory size, because the first IMP8R could be configured so
that its 64 KB window occupies the D0000h space. But, if two
IMP8Rs were installed, the second would have to be configured to
use memory space above the 1MB line, which would constrain the
maximum size of main memory. These restrictions have now been
eased, and both the IMP2 and IMP8R cards can be configured to
'live' in any of several spaces below 1 MB, leaving all the
upper-memory space above 1 MB free for use as a main memory
area. Consequently, memory size on ISA-bus machines which use
*only the IMP2 and/or IMP8R* cards can now be as large as the
system will support. (Most newer 486 motherboards support at
least 32 MB, and some support up to 64 MB.) The following
paragraph on SETUP contains more details on this feature. See
also the note on conflict between IMP8Rs and the Standard
Microsystems NIC cards in the Bug/Compatibility Fixes section
below.
SETUP for ISA-bus systems now supports a broader range of
'Memory Window' options below 1MB for the IMP2 and IMP8R cards,
which makes it possible to expand the main memory on an ISA
machine to whatever maximum is permitted by the motherboard.
This feature is available *only* with the IMP2 or IMP8R cards,
because the 'standard' IMP8 card cannot use a memory window
below 1MB. The 32KB memory windows for IMP2 cards may now be
located at A0000h, A8000h, D0000h, D8000h, E0000h, and E8000h.
Those for the IMP8R (which require 64KB) may be at A0000h,
D0000h, or E0000h. (Locating IMP8R windows *above* the 1MB line
is also possible, but as explained earlier, doing so will impose
an upper limit of the main-memory size. NOTE that use of the
A0000h window is possible *only* if the host machine has a
monochrome video adapter, because all color adapters use the
A0000h space for additional video RAM. Also, some motherboards
(PS/2s, most notably) use the E0000h space for additional ROM
BIOS code, which makes it unavailable to use as an IMP memory
window. We recommend using a 'memory-scan' utility to determine
which of the HMAs (High Memory Areas) are already in use on your
system. (The ASQ utility from Qualitas is excellent, and may be
downloaded at no charge from their BBS at 301-907-8030.)
2. PS/2 improvements:
New .ADF files for PS/2-compatible MicroChannel systems -
Until now, we have relied entirely upon an 'automatic' scheme
built into the 386/MultiWare IOC_PS2.SYS driver to initialize the
memory windows for any IMP2 and IMP8 cards found to be
installed. The only purpose served by the IMP .ADF files
(@7046.ADF and @7047.ADF) has been to enable the IBM setup
program to register the presence of IMP cards on the bus. With
this release, both .ADF files have been expanded to allow the
user to specify memory windows and the IRQ level for any IMP
cards during the standard IBM 'reference-disk' setup procedure.
Also, the IOC_PS2 driver has been revised so that it will read
the PS/2 system's 'POS' registers to determine what memory
windows (and IRQ level) to use, rather than attempting to figure
it out 'automatically'. Although use of the new .ADF files is
*not* required, (the old automatic scheme will be used if the
new .ADFs are not used) this new feature should help to
alleviate problems seen with many of the newer PS/2 models,
which attempt to cache dual-ported memory areas *unless* the IBM
BIOS has been made aware of their presence via the IBM setup
procedure. To use the new .ADF files, simply copy them from the
MW install disk to the working IBM reference disk (replacing the old
.ADF files) and rerun the IBM reference-disk setup procedures.
The IBM setup program will display the alternatives available
for IMP memory windows and IRQ level, and if anything selected
conflicts with already-assigned system resources, a warning will
be displayed. Please note that while each IMP card requires a
unique memory window, all of the IMP cards installed on a micro-
channel system *share the same IRQ level*. That IRQ *may not*,
however, be shared with any non-IMP adapters.
A note on PS/2 IMP board revisions: During the past year or so,
we have MADE AVAILABLE PS/2 IMP boards capable of using the
address space between 16 MB and 32 MB for their dual-ported
memory window. Earlier versions of the board could not use any
window above 16 MB, and therefore constrained the size of main
system memory to something less than 16 MB. The newer 'high-
memory' boards are designed to run just beneath the 32 MB line,
permitting main-memory sizes as large as 24-28 MB, depending on
the memory-expansion increments supported by the specific PS/2
model involved. All address-range choices offered by the new
.ADF file specify whether the range is available on either
version of the IMP boards, ('Any board') or is available only on
the earlier ('Low Board only') or later (High Board only)
revisions of the boards. In order to determine whether an IMP
board is one of the 'High' versions or not, look at the white
revision number label on the socketed 'PAL' chips. If the number
is #IC8151RC or #IC8159RB, then the board is the newer 'High'
version. Any other numbers indicate the STANDARD 'Low' version.
The new PALS are available by special order through Alloy sales,
508-486-0900
3. IMP2 handshaking support:
Support for DTR/DSR handshaking has been added to IOPCM2.BIN. Use
of this feature should fix a variety of problems associated with
using printers attached to a remote user-terminal. NOTE that the
cable used to connect the IMP2 card to the host must be wired to
support DTR/DSR. (The standard Alloy 'Rev F' cable supports DTR/DSR.)
4. 38.4 Kbaud on IMP2 & IMP8R cards - IOPCM2.BIN & IOPCM8R.BIN
have been modified to support 38.4 Kbaud transfer rates.
5. THE DPT SCSI CONTROLLERS SK2011/95 & SK2012/95 ARE NOW SUPPORTED.
THESE ARE ISA & EISA HIGH SPEED CACHING SCSI CONTROLLERS.
The driver name is DPTSCSI.SYS and may be specified in a CDISK or DISK
statement in the \NX386\MACHINE.000\NX386.CFG file. The driver accepts
two parameters:
/Bxxx where xxx is the port address 1F0 or 170h default 170
/Iyy where yy is the IRQ number 11,14,15h default 11
For example: CDISK=DPTSCSI.SYS /B1F0 /I14
will result in 386/MultiWare loading from the DPT controller IRQ 14 and
port 1F0.
A. Follow the installation instructions supplied with the DPT
controller for DOS.
B. Partition the drive(s) with FDISK and FORMAT them as well.
C. Make sure everything runs normally without 386/MultiWare involved.
D. Install 386/MultiWare if needed.
E. Modify NX386.CFG as above to include DPTSCSI.SYS.
F. Run 386/MultiWare.
Notes:
a. 386/MultiWare will assign the highest SCSI ID to first available drive
letter.
b. Non-removable hard disk media type is the only SCSI device type
supported.
c. Other SCSI devices on the controller will be ignored by DPTSCSI.SYS.
e. 386/MultiWare is limited to four hard disks per controller.
f. Under DOS 5 each partition may be 2GB in size and each physical
drive may have four partitions. This should allow use of SCSI drives
as large as 8GB to be used with 386/MultiWare and DOS 5. (THIS IS
THEORETICAL AS ONLY TWO PHYSICAL DISKS HAVE BEEN TESTED THE LARGEST
BEING 320 MEG)
g. You will notice that 386/MultiWare will take longer to initialize
because it now has to scan the SCSI bus for as many as 7 device IDs.
h. If you use the DISK= parameter a new 386/MultiWare kernel is required to
allow write access to the SCSI drives. Revision 4.00K and later have
the required changes.
6. Added NETBIOS emulation support.
A.) Insert line, "DEVICE = \NX386\DRV\NETB386.SYS", into
NX386.CFG file ( this file is in the \NX386\MACHINE.000
subdirectory ).
B.) Insert line "DEVICE = \NX386\DRV\NETBDOS.SYS" into
user "CONFIG.Unn" files (files are in \NX386\MACHINE.000
subdirectory).
7. Added CDROM support. The following controllers and drives are
supported with this driver. Other CDROMS should run with there standard
drivers provided that they do not use a memory window above A000h or an
IRQ.
CONTROLLERS DRIVES
HITACHI CDIF25A2 HITACHI CDR1600
HITACHI CDIF14 HITACHI CDR1700
HITACHI CDIF14A2 HITACHI CDR3600
HITACHI CDIF35A
A.) Insert the line,
"DEVICE = \NX386\DRV\HITACHIA.SYS /D:MSCD001 /N:1 /P:xxx"
(where xxx = HEX Port Address of CDROM Controller), into
NX386.CFG file (this file is in the \NX386\MACHINE.000
subdirectory).
B.) Insert line "DEVICE = \NX386\DRV\CDHOOK.SYS" into
user "CONFIG.Unn" files (files are also in the \NX386\MACHINE.000
subdirectory)
C.) run MW386
D.) run \NX386\DRV\MSCDEX /D:MSCD001 from DOS Task
*** Bug/Compatibility fixes in version 4.20 ***
1. If a 128k task was created the system would hang.
2. Unattended shutdown was not occurring on Sunday.
3. U.M.B. supported excluded C800-D000, changed to C800-C900. This is the
area that MW386 uses for system bios.
4. Fix for a problem with the WEB Station Manager where the "Cannot create
Station Manager temporary files" message would be received if you had a
MultiNode name of 5 characters in length. In that case only, the MS-DOS
Create Temporary File function would be called with a valid
null-terminated path, but there was an extraneous '\' immediately
AFTER the null terminator. (i.e. 'C:\NETWORK\TMP\',0,'\') So, the fix
for this is to look to see if the previous character was a
null-terminator before advancing ESI and fooling the file system into
thinking that the string had not terminated, yielding an invalid path.
5. Fix to par_drvr.sys
Changes for JetStream:
1. Test for not busy.
2. DMA memory allocation.
3. DMA offset not being reset.
4. Error codes not being returned.
6. Fix to par_drvr.sys
Change to Jetstream handling to test DMA complete before status reg
check. Seems to correct error checking and data overruns.
7. Moved call read_ticks to hw_timer procedure to decide on a global basis
when to "roll" the date. Fixes terminal time problems after 24:00.
8. Save user regs. Fix to terminal time problems after 24:00.
9. CHANGE TO FSHARE MESSAGE.
Message text changed to stronger warning of file corruption.
Version now 1.16.
10. Changed default user task name to MS-DOS Task 1
11. Many changes to schedule user task to support non-preemptive state.
Added new equate for don't preempt.
12. Added int 7F call to get task id for int 10.
13. Deleted incorrect register setup for INT 10 trap vector. This caused
incorrect ADAPTER_TYPE being reported to emmdev.sys.
14. Check for swapped out page. Heavy swapping caused page fault.
15. Clear upper end of 32bit register. Caused scrolling to sometimes
abort.
16. Fix right arrow wrap to not include 128KB.
Rev updated to v3.07.
17. FIXED ADAPTEC 164X DRIVER, NON FUNCTIONAL IN 4.1X.
18. FIXED CACHE, SYSTEM WOULD SLOW DOWN AS THE DAY PROGRESSED IN SOME CASES.
Change to not allow the total allocation of cache buffers to so-called
"system" buffer LRU chain. Change stops allocation of "data" buffers
after all unused buffers have been used to store records.
Prior to this change as time progressed all cache buffers were linked on the
"system" buffer LRU chain. This meant that only one prior "data" buffer was
remembered by the cache.
This change resulted in a 25% elapsed time improvement in house and 33% at
the Micro Systems site which isolated the problem.
19. Fix for diskette cache problems.
20. Fix for IBM Value Line 66DX2 keyboard duplicating characters problem.
21. Fixed warm shutdown on IBM Value Line 66DX.
*** Bug/Compatibility Fixes in 4.10 ***
1. MultiEdit version 6.1 - Fixed a kernel problem resulting in a
task crash during ME initialization. (i.e., Task would abort
with a 'USER PROCESS HAS EXECUTED INVALID INSTRUCTION(S)'
message.)
2. Fatal I/O Channel error - Corrected a rare problem involving
a few types of EGA/VGA adapters, which would occasionally cause
the system to stop with a 'FATAL - I/O CHANNEL ERROR' message.
3. MAPDRIVE failure - Fixed a problem which would cause this
utility to ignore a 'MAPDRIVE x AS NETWORK' command. The drive
would remain 'LOCAL', and no error message would be produced.
This problem first appeared in the 386/MultiWare 4.0 release, and
has been in all beta versions through 4.00d. The fix involved
changes to both the MW kernel and the MAPDRIVE.EXE utility.
4. NetWare file transfer performance - Modified the NETWARE.SYS
driver to correct a problem causing extremely slow file
transfers between a MW host and a Novell NetWare server.
5. MultiServer dropping off network - corrected a problem in
NETWARE.SYS which *may* have been responsible for most of the
'dropoff' problems reported.
6. Deleting and Renaming files from a MultiServer PC
workstation. - Corrected a kernel problem involving a DELETE or
RENAME command from a PC station, which would cause some files
to be 'missed' if the file spec contained wildcards.
7. TYPE command - Fixed a long-standing problem which would
cause a task TYPEing a lengthy file to go to sleep after
displaying a few lines. This problem was the result of incorrect
Intel documentation of the behavior of the 'BT' family of
machine-language instructions, and could also have been causing
a wide variety of other performance problems, most of them much
more subtle than the TYPE bug. (Essentially, the bug would cause
a key section of the kernel to *look in the wrong place* for PIF
information on any interrupt number higher than 1Fh.)
8. BCAST causing task crash - Fixed a bug in NETWARE.SYS which
would cause the user task to crash if initialization of the
task's NIC driver failed, and the user then enabled local
broadcasts.
9. Compatibility with SMC NIC cards - A number of changes were
made to the WD8_ISA.SYS driver so it will operate with the
Standard Micro Systems versions of the Western Digital NIC
cards. (SMC added a number of features to their 'WD-compatible'
cards, but some are not compatible with standard WD drivers.)
10. Conflict between IMP8R auto-configure & SMC NIC cards -
Until this release, 386/MultiWare would automatically search for and
set up any IMP8R cards. We have had to delete this feature,
because the search procedure required to identify an IMP8R,
happens to activate the 'change my port address' feature in
certain SMC NIC cards. The result of this was that the SMC card
would change its port address while 386/MultiWare was looking for
IMP8Rs, and the SMC driver would thereafter fail when attempting
to initialize the NIC card. (This condition would persist even
if 386/MultiWare was shut down, and the user attempted to bring up
the SMC NIC in real mode. The only cure is turning system power
off and back on again.) Therefore, *SETUP MUST NOW BE USED TO
CONFIGURE THE MEMORY WINDOW(S) FOR ANY IMP8R CARD. Failure to do
this will cause 386/MultiWare to ignore the presence of any IMP8R.
(The 'auto-configure' feature still works for IMP2s: If any are
found on the bus, 386/MultiWare will set them up to run in the
D0000h or D8000h window automatically, unless the user has
specified a different window in SETUP.)
11. RTS/CTS failure on IMP8 cards - IOPCM8.BIN has been changed
to fix problems with using RTS/CTS on the Terminal (9-pin)
ports. (Basically, RTS/CTS simply didn't work on the 9-pin
ports, even though it would on the 25-pin ports.)
12. Integrated PS/2 SCSI adapter. Many of the newer PS/2
machines have a SCSI adapter on the motherboard, and 386/MultiWare
would fail to initialize on these machines, because the device-
recognition protocol required for IBM motherboard devices is
completely unlike that used for those installed in a bus-adapter
slot. PS2SCSI.SYS has been modified so that it will initialize
properly with motherboard SCSI devices. Please note that *only*
the standard SCSI port address (3540h) is currently supported by
386/MultiWare. Changing the port address with the IBM setup program
will cause 386/MultiWare initialization to fail.
13. Adaptec 174x failure - The ADPSCSII.SYS driver has been
changed so that it will properly initialize with the 174x-series
(EISA bus) SCSI controllers. The failure was caused by the fact
that the 174x is not *entirely* compatible with the 154x (ISA)
adapter, even when the 174x is set up to run in STANDARD
(154x-compatible) mode. Please note that the 174x *must* be set
up (using the EISA configuration utility) to run in STANDARD
mode to be 386/MultiWare compatible. The 174x ENHANCED mode is not
supported by 386/MultiWare, because - according to Adaptec's
technical reference manual - it offers no performance advantage
over STANDARD mode. In fact, it's also worth noting that our
own tests have failed to show that the 174x performs any better
than the 154x, when tested on the same machines, with the same
disks. This may of course be due to the kind of tests we ran,
(high-volume sequential reads and writes) or to hardware
limitations not related to the controller. (Most tests were done
with a 50 MHZ DataExpert 486DX EISA motherboard, equipped with a
1.2 gigabyte Maxtor 'Panther' drive.)
14. TaskView (TV) failure to recognize foreground task - TV has
been revised to cure a problem which caused TV to sometimes
classify a 'foreground' task as 'background'. This would result
in TV refusing to reboot a foreground task with an error message
saying 'Task must be current task for reboot operation.' In
addition, the TV task-screen display would fail to display an
asterisk (*) character next to the user & task number at the
lower-right corner of the screen. (The asterisk is used to
indicate that the screen being displayed belongs to a foreground
task.) Please note that the term 'foreground', as used in MW
documentation, means the task which is currently controlling the
user-terminal screen, and which will receive any input from the
terminal keyboard.
15. Fix to Divide Overflow DOS message.
After several days of inactivity DOSTICKS would get too large for DOS
to handle. Fix sets the count to a max of 24hrs. Also changed the
tick logic to check for date overflow every clock tick rather than
every 100ms.
16. Added new support for 21/E3 subfunction 16h.
This was to pass the Station User Name as a Novell login name to
support a DBASE application.
17. Fix to int 16/00 and 16/01 keyboard read/status interrupts.
a. F11 and F12
b. ALT and ENTER pressed
c. Unshifted numeric keyboard 5
18. If a DOS 5 386/MultiWare system tried to load MW386 again a double fault
occurred. Fix to restore INT 15 DOS 5 special hook.
19. Fix for "losing files". Find First int 21/4e returned the first file
in the directory as in "C:\PAYROLL\". DOS 5 returns a Path Not Found
error in those cases. A change was made to 386/MultiWare Find First to
respond as DOS. If the program found a file in this directory
it deleted all files. British Accounting Application "PEGASUS".
20. Timer fix to allow moving past midnight for some apps. Change causes
the task update to wait until the TOD clock turns past midnight
21. Fix for DX266 PS/95 with SCSI. Wait for Adapter not busy.Version
change to 1.03.
22. Change to allow int 10/91h call in a DOS app to support UMB checking.
91h returns the adapter/display type in ax.
23. Added UMB limit checks for:
1. E000-FFFF or F000-FFFF system BIOS
2. A000-C000 or B000-C000 or B800-C000 VGA,HGC,CGA
3. C800-D000 386/MultiWare
24. Defined new MapDriveInUse bit in an used byte of the TSS.
This bit is to control the interpretation of int 21/5F0x depending if
*MAPDRIVE* is run at anytime in the task.
25. Fixed Double Faults when running without KMON. FS:[15F] changed to 03.
This wipeout may explain other unknown problems since the value of FS
was not setup. Version change to v4.02.
26. 1. Correctable ECC errors are now returned with no error.
2. Sector not found errors now cause automatic restore and retry for 3
times.
27. The default config.uxx files have been modified so the EMMDEV.SYS
driver does not load. DOS will still load high however, loading the
U.M.B. driver consumed approx. 384k per task.
******************************INCOMPATIBILITIES****************************
1. IBM DOS 5.02 or GREATER.
2. Any application that requires DPMI or any other DOS EXTENDER.
3. Any application that requires a minimum of a 286 PROCESSOR. MW386 offers
VIRTUAL 8086 TASKS.
*******************************************************************************
*******************************************************************************
IF YOU HAVE A MW386 4.XX TO 4.2 UPGRADE AND ARE DOING A FIRST TIME INSTALL YOU
WILL HAVE TO FOLLOW THE FOLLOWING INSTRUCTIONS IF YOU ARE USEING MS-DOS 6.0 OR
6.2!
*******************************************************************************
*******************************************************************************
*** Installation Procedures ***
1. EXISTING SYSTEMS RUNNING MS-DOS 5.0 AND MW386 4.XX
a. Upgrade the system to MS-DOS 6.0 OR 6.2.
b. Install MW386 version 4.20.
2. NEW SYSTEM RUNNING DOS 6.0 OR 6.20, MW386 NOT ON DISK.
a. Format a diskette with the /s parameter to a make
it bootable with MS-DOS 6.0 OR 6.20 and copy SYS.COM from
your DOS directory to the floppy.
b. Boot off an MS-DOS 5.0 bootable diskette with the
SYS command. (OBTAINABLE THROUGH YOUR LOCAL
COMPUTER DEALER.)
c. Execute SYS C: from the diskette, this will make
your system MS-DOS 5.0 bootable.
d. Open the floppy door and reset the system.
e. Install MW386 version 4.XX.
f. Execute MW386 from the NX386 directory to verify
that you have a good installation. If MW386 comes
up OK, perform a shutdown & proceed to the next
step.
g. With the diskette that was created in step a.
perform steps b. through d., the difference is that
you are making your system MS-DOS 6.0 OR 6.20 bootable
now.
h. Install MW386 version 4.20.
3. EXISTING SYSTEMS RUNNING DOS 3.30 OR 4.01 & MW386 4.XX.
a. Perform steps 2b. through 2d.
b. Perform an upgrade install with your 4.XX
distribution disk.
c. Perform steps 1a. & 1b.
*******************************************************************************
BUG FIXES IN 4.20A
1. FIXED LOCK AND WAIT WITH SEMAPHORES.
*** New Features in 386/MultiWare 4.20A ***
2. ADDED NEW HARD DISK DRIVER PS2IDE.SYS, REQUIRED WITH THE NEW IDE DRIVES ON
THE LATEST PS2 MOD 95'S.
BUG FIXES IN 4.20B
1. WHEN A TASK WAS REBOOTED IT DEFAULTED TO 640K, 704K OR 736K REGUARDLESS OF
THE TASKS SIZE WHEN IT WAS CREATED.
2. KMON HALTED CONTINUOUSLY.
BUG FIXES IN 4.20C
1. PRINTING ON AN IBM VALUEPOINT 66MHZ 486 CAUSED PRINTER OFF LINE ERRORS AS
WELL AS NUMEROUS FORMFEEDS.
*** New Features in 386/MultiWare 4.20D ***
1. ADDED THE LIMITING OF PASSWORD ATTEMPTS ON A PER USER BASIS, THIS WILL ALSO
DISCONNECT A REMOTE USER BY SENDING A "+++" OUT THE PORT. THE MODEM ON THE
HOST END MUST BE CONFIGURED TO DISCONNECT WHEN THAT STRING IS SENT.
BUG FIXES IN 4.20E
1. <ALT> <SYS REQ> WOULD DISABLE THE KEYBOARD WHEN RUNNING IN KMON.
2. EXCESSIVE SWAPPING CAUSED A PAGE FAULT.
BUG FIXES IN 4.20F
1. AUTOMATIC SHUTDOWN WOULD NOT WORK ON MONDAYS. THIS WAS CAUSED BY THE LOW
ORDER BITS IN THE REGISTER BEING TRASHED. THIS CAUSED MW386 TO KNOW THE
PROPER DAY 50% OF THE TIME.
BUG FIXES IN 4.20G
1. CHANGE IN SCHEDULER, WHEN TWO TASKS HAD CONTINUOUS KEYBOARD IMPUT IN
CERTAIN APPS (FOXPRO & NE SHOWED THE PROBLEM, WORD PERFECT DID NOT) THOSE
TWO TASKS WOULD GET "ALL" THE CPU TIME ON THE SYSTEM. THE OTHER TASKS EITHER
WERE EXTREMELY SLUGGISH OR APPEARED TO HANG UNTILL ONE OF THE PREVIOUSLY
MENTIONED TASKS STOPPED KEYBOARD INPUT.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.