! updates.txt
! This update file provides a means for developers to document changes and/or
! fixes they have provided to a particular NeXtMidas version number.
! When a NeXtMidas baseline is released, this file contains no update
! information.  As a developer modifies and/or debugs the code, they add to
! this file using the fields provided below.  This will provide a means to
! document code that is deployed between NeXtMidas baselines and will
! allow the developer to locate their changes/fixes within the NeXtMidas
! code structure.
! 
! When code is deployed, any deltas from the released NeXtMidas baseline
! can be reviewed by users during installation, execution and debugging.
!
!
! Example:
!   date        option.dir.file         method            update by
! ========      ===============         ======            =========
! 01/06/24      sys.lib.Datafile.java   seek(int)         Joe Midas
!           This is the description of the fix added to this version. 
!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  date      option.dir.file               method            update by
========    ===============               ======            =========
12/10/2008  hwc.prim.hwdriver             Ethernet Control  Erica Bush
	Please review the primitiave to see the comments added with the new
        changes.  In summary, the code has been updated to work with users 
	current hwconfig files and allow for device control via Ethernet.
	There was an issue when saving results to a results parmeter which
	was fixed with a work around by John March.
	
	"The reason why MR.put was not setting the result variable, is that the
	 HWDRIVER primitive is being called form a macro. Marcos have their own
	 results table, which is discarded once the macro in exited.
	 
	 To work around this, the code has been changed to put the result in the 
	 table associated with the level above the currnt level - the parent
	 result table- using MR.getPrevious().put. This assumes that the 
	 HWDRIVER primitive is never called directly, only by the HW macro."
	 
	 Other outstanding issues are that the /drf and /vrn switches that exits
	 in the XMIDAS routines are not programed to work in the NeXtMidas
	 routine.  The use of these switches needs to be investigated to 
	 detemine if there is a need for them by the users.
	    
