readme.txt file for MATLAB(R) Version 4.2c 
for Microsoft Windows
(C) Copyright 1994, The MathWorks, Inc.

---------------------------------------------------------------
Systems Requirements and Compiler Support
---------------------------------------------------------------
MATLAB 4.2c requires one of the operating system releases listed below:
	- MS-Windows 3.1
	- OS/2 2.1 with the ServicePak PTF-XR06200
	- MS-Windows NT 3.5
	- MS-Windows 3.1j (for a Kanji NEC machine)

The following compilers are supported for building MEX-files 
under MS-Windows 3.1:
	- Borland C++ 4.0
	- Microsoft Visual C++ 1.5 
	- MetaWare High C 3.1 (requires Phar Lap Linker 5.0)
	- Watcom 10.0 (general availability version)
	- Microway NDP Fortran 4.4 (requires Phar Lap Linker 5.0)

The following compilers are supported for building MEX-files 
under OS/2 2.1:
	-Watcom 10.0
	-Borland C++ 4.0

The following compilers are supported for building MEX-files 
under Windows NT 3.5:
	-Watcom 10.0
	-Borland C++ 4.0
	-MetaWare High C 3.1 (Requires Phar Lap Linker 5.0)
	-Microsoft Visual C++ 1.5 

The following compilers are supported for building MEX-files 
under a Kanji NEC machine:
	-Watcom 10.0
	-Microsoft Visual C++ 1.5 

The MATLAB Notebook requires MS-Word 6.0 (6.0a highly recommended).

---------------------------------------------------------------
General Help
---------------------------------------------------------------
a) If you use SIMULINK, Real-Time Workshop, or the SIMULINK
Accelerator, make sure you install the new versions, which are
included in your shipment and are compatible with MATLAB 4.2c.

b) There is a limitation of 350 uimenus per MATLAB figure window.  
Unpredictable results will occur if you exceed this limitation.

---------------------------------------------------------------
Notes for running under MS-Windows 3.1:
---------------------------------------------------------------
a) When printing to the HP 1200C printer, you should use the 
updated Windows driver (version 1.10) available through your HP 
customer representative.

b) The commands 'engGetMatrix' and 'engPutMatrix' do not work
with matrices containing more than 40,000 elements. 

c) We have found that this version of MATLAB is unable to print some
graphics to LaserJet IV (LJ4) and DeskJet 500 printers (DJ500) when using 
older versions of the Windows supplied printer drivers.  If you are using 
LJ4 drivers prior to version 1.35 or DJ500 drivers prior to version 4.1, 
please contact your HP customer support representative and request the 
latest drivers.

As an alternative to printing via the Windows drivers, it is possible
to use MATLAB's built in drivers.  For the LaserJet IV, use the
' print -dljet3' command.

For the DeskJet 500 Series, use one of the following commands:

print -dcdeskjet ( HP DeskJet 500C with 1 bit/pixel color )
print -dcdjcolor ( HP DeskJet 500C with 24 bit/pixel color and )
		 ( high-quality color (Floyd-Steinberg) dithering )
print -dcdjmono  ( HP DeskJet 500C printing black only )
print -dcdj550   ( HP Deskjet 550C )

For more information on the 'print' command, type 'help print' at the
MATLAB command prompt.

---------------------------------------------------------------
Notes for running under OS/2:
---------------------------------------------------------------
a)  We suggest that you run MATLAB from the WIN-OS/2 group folder.
Programs copied to the Desktop under OS/2 consume significantly 
more GDI resources when executed than those executed from their 
default installation location.

b) Run MATLAB as a Windows-OS/2 window in a separate session.

c) Set win_run_mode to 3.1 enhanced capability.

d) Opening multiple DOS windows causes visible system
degradation.

e) To print under OS/2 using the GhostScript devices, you must 
edit the M-file 'print.m'.  You can uncomment the pause statement 
on line 627 directly after the line 

dos(['gs386 @' rsp_file '' filename '<NUL|']);.  

This allows the print job to be successfully sent to the printer.
For more complicated graphs you will need to increase the pause length
to as much as 30.  (If you get the error message 'File not found or
permission denied' this indicates that the pause length you are using
is too short.)

f) Printing to an HP PaintJetXL300 is not supported.

---------------------------------------------------------------
Notes for running under NT:
---------------------------------------------------------------
a) When building mex-files using Watcom 10.0 under NT, you must install 
the native NT compiler in addition to the DOS libraries.

b) The MATLAB Notebook Suite under NT uses the default directory for MS-Word.

c) If you run the Watcom 10.0 compiler in NT while using the 
Real-Time Workshop, and you get a Dr. Watson error message, then you
must add the Watcom binnt directory to your path.  

d) When using the Real-Time Workshop under NT you must update the 
Windows NT path to include the following directories:
    watcom_root\binb          (so that 'wmake' can be found)
    watcom_root\bin           (so that 'dos4gw.exe' can be found)

There are two ways to add these directories:
  *Add the directories to your 'autoexec.bat' file, and reboot. 
  *Add the directories to the path through the system utility
     in the control panel and reboot.

e) When using the Real-Time Workshop or the 'cmex' command you must
either:
  *Manually close each inactive DOS window after banging out.
  *Use your PIF editor to edit the file 'ml_bang.pif' to close each 
window automatically on exit.  The file 'ml_bang.pif ' can be
found in the matlab\bin directory.

f) When using the SIMULINK Accelerator, you must add a line to  
'matlabrc.m' as follows: 
   set_param(0,'Compile command','dos(''cmex $model.c'');pause(3)');

---------------------------------------------------------------
Notes for running under a Kanji NEC machine:
---------------------------------------------------------------
a)  When using the Real-Time Workshop, you must use the 'wmake' command.
The 'gmake' command is not supported.  

b)  MS-Windows 3.1j has fewer system resources than MS-Windows
3.1.  Consequently, several resource-intensive demos may not display 
properly on the Kanji NEC machine.

c) When using the Real-Time Workshop or the 'cmex' command you must
either:
  * Manually close each inactive DOS window after banging out
  * Use your PIF editor to edit the file 'ml_bang.pif' to close each 
window automatically on exit.  The file 'ml_bang.pif can be
found in the matlab\bin directory.

---------------------------------------------------------------
Bug Fixes for MATLAB 4.2c and SIMULINK 1.3c
---------------------------------------------------------------
Platform specific:

MATLAB bug fixes:
--------------------
G103555 
-- Implemented support for the Watcom 10.0 compiler. 
			    
G64302 
-- The command 'lasterr' no longer returns erroneous data after it has
been manually reset. 
  
G100704 
-- The use of long vectors  with the 'sound' function has been improved.
		 			
G98246 
-- The 'close' command can now be used in Dynamic Data Exchange input 
streams. 
			       
G98700 
--Input stream from DDEs now supports the use of 'pause', 'input',
and 'keyboard' commands.
 
G102404 
-- Scalable text properties are now available for metafiles created
from an invisible figure.
	 
G103868 
-- PostScript driver code has been modified to support printer 
internationalization.   

SIMULINK bug fixes:
--------------------
G96863 
-- Sample time colors now copy properly to the clipboard from SIMULINK
block diagrams.  

G99770 
--The mask for the Transport Delay block now supports editing for the
'buffer size' field using dialog boxes.
 
G104644 
-- License violation messages will no longer occur if compatible 
versions of SIMULINK and the SIMULINK Accelerator have been installed.

G100011 
-- The 'pulse' generator block has been redesigned to support a width
setting of less than half of the clock period.


Multiple Platform Bug Fixes
------------------------------------------------------------
MATLAB bug fixes:
--------------------
G104535  
-- The file 'bench.m' which displays benchmarks for different machines
has been updated.

G63820
-- Limitations for the 'findobj' command using large numbers of objects
have been corrected.

G64401
-- The 'csvwrite' function has been redesigned to write matrices 
properly with commas used as a separator for elements.

G99587
-- Support for the -debug flag in the 'cmex' command has been 
implemented.

SIMULINK bug fixes:
--------------------
G66002  
-- Problems using the control keys for SIMULINK editing have been corrected.

G61872
-- A problem with short line connections has been corrected in SIMULINK.

G92235
-- Vectorization of SIMULINK MUX blocks has been implemented.


---------------------------------------------------------------
Bug Fixes for MATLAB 4.2c.1 and SIMULINK 1.3c
---------------------------------------------------------------
G108941 
-- For S-Functions with only discrete states, The Real-Time Workshop 
now correctly indexes into the states vector.


-----------------------------------------------------------------
Documentation Errata
-----------------------------------------------------------------
The current printed documentation is up-to-date with the following 
exceptions:
-----------------------------------------------------------------
Compiling MATLAB Engine programs:
-----------------------------------------------------------------
The commands to compile Engine programs on page 1-4 of the "External
Interface Guide Supplement" are incorrect.  The following are the
correct versions of these commands.  Note that, in all three of the
cases below, you should first set up your PATH, INCLUDE, and/or
LIB environment variables as described in your compiler manual.

1)      Microsoft Visual C/C++ 1.5:
	
	CL -ALw -FPi87 -I<matlab>\EXTERN\INCLUDE ENGTEST1.C
     <matlab>\EXTERN\LIB\LIBENGMS.LIB DDEML.LIB LLIBCEW.LIB LIBW.LIB
	
	This may generate the warning message:
	LINK : warning L4021: no stack segment
	This message can be ignored.

2)      Borland C/C++ 4.0:

	BCC -WE -ml! -f287 -2 -Od -I<matlab>\EXTERN\INCLUDE
     ENGTEST1.C <matlab>\EXTERN\LIB\LIBENGBC.LIB

3)      Watcom C/C++ 10.0:

	Create a file called 'engine.lnk' that contains the following
	lines:
	lib <matlab>\EXTERN\LIB\LIBENGWC.LIB
	lib win386.lib
	lib clib3s.lib
	lib math387s.lib

	Next, execute the command
	WCL386 /w3 /5s /7 /or /zw /l=win386/I<matlab>\EXTERN\INCLUDE 
     ENGTEST1.C @engine.lnk
	
	Finally, execute the command
	WBIND ENGTEST1 -n

-----------------------------------------------------------------
Running the engtest programs:
-----------------------------------------------------------------
The various Engine test examples provided with MATLAB pass the
variable 'lpszCmdLine' to the 'engOpen' call.  This means that the 
command line arguments entered when the Engine program is called will 
be used to start MATLAB.  Therefore, to run the engtest programs,
choose Run from the Program Manager, select or type in the
Engine program's name, and follow that with the full pathname to the 
MATLAB executable.  For example:

	c:\matlab\extern\src\engtest1.exe c:\matlab\bin\matlab

