Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.16 $; site prism.UUCP
Path: utzoo!linus!decvax!cca!prism!matt
From: matt@prism.UUCP
Newsgroups: net.micro.pc
Subject: Re: REP vs. REPZ - I goofed.
Message-ID: <7700009@prism.UUCP>
Date: Wed, 14-Aug-85 10:35:00 EDT
Article-I.D.: prism.7700009
Posted: Wed Aug 14 10:35:00 1985
Date-Received: Mon, 19-Aug-85 21:33:03 EDT
References: <16092@watmath.UUCP>
Lines: 24
Nf-ID: #R:watmath:-1609200:prism:7700009:000:1175
Nf-From: prism!matt    Aug 14 10:35:00 1985


> /* Written  2:10 am  Aug 12, 1985 by bc@cyb-eng in prism:net.micro.pc */
> >    My appologies to MicroSoft and Lattice.  I (and others) are still
> > having difficulties with movmem(), but the cause is as yet unknown.
> > -Henry
> 
> Be aware that, as of Lattice C 2.15, movmem() does NOT preserve the contents
> of the ES register!  If you are using the small model, Lattice expects ES
> to be preserved across function invocations.  Lattice, Inc:  take note!
> -- 
> /* End of text from prism:net.micro.pc */

Note that MANY of the Lattice standard I/O routines have this problem,
including peek(), intdos(), and bdos().  This is a real loss if you are
using any of the DOS services that return vectors in ES:BX.

Is there anyone from Lattice on the net, now that they have a Unix box?

-----------------------------------------------------------------------------
 Matt Landau            {cca, datacube, ihnp4, inmet, mit-eddie, wjh12}...
 Mirror Systems, Inc.                                   ...mirror!prism!matt
 Cambridge, MA		(617) 661-0777
-----------------------------------------------------------------------------
 "Replace this mandolin with your wombat..."