Path: utzoo!attcan!uunet!snorkelwacker!usc!samsung!emory!mephisto!mcnc!rti!bcw
From: bcw@rti.rti.org (Bruce Wright)
Newsgroups: comp.windows.ms
Subject: Re: Barfing up 3.0 apps
Summary: win87em.dll, Windows 3.0, and old apps
Message-ID: <4011@rtifs1.UUCP>
Date: 9 Aug 90 15:30:39 GMT
References: <8685@gremlin.nrtc.northrop.com> <1990Aug8.020846.19494@portia.Stanford.EDU>
Organization: Research Triangle Institute, RTP, NC
Lines: 30

In article <1990Aug8.020846.19494@portia.Stanford.EDU>, shedevil@portia.Stanford.EDU (Anne Prisk) writes:
> Several people explain that upon trying to run certain apps. they get this 
> message:
> 
> >> >          Cannot find file; check to insure the path and
> >> >          filename are correct
>
> Just wanted to say that I am having the exact same problem with WINEYES,
> and a few other apps.  Hope someone who knows the fix reads this soon!

Someone else mentioned that WINEYES needs win87em.dll to be in the
Windows directory.  This may be true (I don't know anything about
the WINEYES program), but if it was built with the Windows 2.0
development kit it _may_ be trying to link to win87em.EXE rather 
than win87em.DLL.  (the most obvious way of linking under 2.0 will
link to win87em.EXE rather than .DLL which is the way 3.0 names the
file).

If this is the case, the fix is pretty simple:  just make a second
copy of win87em.DLL named win87em.EXE.  (Make a second copy, don't 
just rename it or 3.0 apps may not find win87em.DLL).

Seems like it would have been pretty simple for Microsoft to have
set things up so that such a trivial renaming wouldn't be necessary
(or at least noted it prominently in their documentation), but
floating point support isn't required by the vast majority of
Windows apps and this may have just fallen through the cracks
during their testing.

						Bruce C. Wright