maurit@nrtc.nrtc.northrop.com (Mark Aurit <maurit>) (08/03/90)
A while back I posted a message about getting the following messge when
I click on the "command.com" button in the MAIN menu:
Application Execution Error
Cannot find file; check to insure the path and
filename are correct
Sounds easy enough to fix; yet command.com WAS there. Whether I type it
in or use BROWSE to fetch the name, the same thing happens (this is on a
no-name standalone clone 386). I tried many things (moving command.com
to another directory and pointing to it), none of them working. Finally I
gave up.
But now at work, the same thing is happening on my PS/2 mod 70 attached to
a fat pig Banyan Vines network; but its not command.com, rather its the
SOFTTYPE windows app. Worked fine yesterday; today I Exported off some fonts
and copied off some unrelated windows files (excel, the word cbt, some DOS
apps) all to make room to create some fonts, and guess what happened when
I clicked on SoftFont? Tried the usual, nothing worked. Finally dusted
all SoftType directories, re-installed under another directory name,
used File Properties to point to the proper directory, makes no diff.
Took out every line in WIN.INI relating to soft fonts, still the same-o.
Would DESPERATELY appreciate any help
Mark Aurit
maurit@nrtc.northrop.comrommel@lan.informatik.tu-muenchen.dbp.de (Kai-Uwe Rommel) (08/06/90)
In article <8685@gremlin.nrtc.northrop.com> maurit@nrtc.nrtc.northrop.com (Mark Aurit <maurit>) writes: >A while back I posted a message about getting the following messge when >I click on the "command.com" button in the MAIN menu: > > Application Execution Error > Cannot find file; check to insure the path and > filename are correct > >Sounds easy enough to fix; yet command.com WAS there. Whether I type it >in or use BROWSE to fetch the name, the same thing happens (this is on a >no-name standalone clone 386). I tried many things (moving command.com >to another directory and pointing to it), none of them working. Finally I I had this bug too, when I played with a Windows 3.0 version which was labelled "version 3.0 RC6" in the Program managers about box. This was in May. Now I upgraded my own Windows and got one which is only labelled as "version 3.0" and did not have again this bug. The sources of the problem was, that Windows couldn't find some apps (mostly old applications) when more than eight fonts were installed with control panel. Usually, you have COURE, HELVE, TMSRE, SYMBOLE, MODERN, ROMAN and SCRIPT installed. I wanted to add the 8514 fonts COURF, HELVF, TMSRF and SYMBOLF to have bigger fonts for a 24pin printer which has the same aspect ratio than VGA and 8514. After adding the ninth font, this problem occured and after removing the ninth one it went away. I am wondering what these two things got to do with each other but this was the bug. It seems to be fixed in the current delivered versions. Kai Uwe Rommel -- /* Kai Uwe Rommel * Munich * rommel@lan.informatik.tu-muenchen.dbp.de */
oivindt@ulrik.uio.no (Oivind Toien) (08/07/90)
In article <3793@tuminfo1.lan.informatik.tu-muenchen.dbp.de> rommel@lan.informatik.tu-muenchen.dbp.de (Kai-Uwe Rommel) writes: > In article <8685@gremlin.nrtc.northrop.com> maurit@nrtc.nrtc.northrop.com (Mark Aurit <maurit>) writes: > >A while back I posted a message about getting the following messge when > >I click on the "command.com" button in the MAIN menu: > > > > Application Execution Error > > Cannot find file; check to insure the path and > > filename are correct > > > >Sounds easy enough to fix; yet command.com WAS there. Whether I type it > >in or use BROWSE to fetch the name, the same thing happens (this is on a > >no-name standalone clone 386). I tried many things (moving command.com > >to another directory and pointing to it), none of them working. Finally I > I had this bug too, when I played with a Windows 3.0 version which was > labelled "version 3.0 RC6" in the Program managers about box. This was > in May. Now I upgraded my own Windows and got one which is only labelled > as "version 3.0" and did not have again this bug. > The sources of the problem was, that Windows couldn't find some apps > (mostly old applications) when more than eight fonts were installed with > control panel. Usually, you have COURE, HELVE, TMSRE, SYMBOLE, MODERN, > ROMAN and SCRIPT installed. I wanted to add the 8514 fonts COURF, HELVF, > TMSRF and SYMBOLF to have bigger fonts for a 24pin printer which has the > same aspect ratio than VGA and 8514. > After adding the ninth font, this problem occured and after removing the > ninth one it went away. > I am wondering what these two things got to do with each other but this > was the bug. It seems to be fixed in the current delivered versions. > Kai Uwe Rommel No, I had the same problem with non-beta ver 3.0. I was trying to run WINEYES, but got the same errormessage, although the file was there. As far as I know, I have only the standard fonts installed.
adnan@rice.edu (Sarmad Adnan) (08/07/90)
> No, I had the same problem with non-beta ver 3.0. I was trying > to run WINEYES, but got the same errormessage, although the file was > there. As far as I know, I have only the standard fonts installed. For Wineyes you need win87em.dll in your windows or windows/system directory. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Sarmad Adnan (adnan@rice.edu) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
alu@cbnewsk.att.com (Alan Lustiger) (08/07/90)
When I had this problem, I increased BUFFERS and FILES.
This fixed it.
Well, it's easy enough to try, anyway!
--
Alan Lustiger
|_ | | AT&T Bell Laboratories ERC
/ |( Princeton, NJ
attmail!alustiger or att!pruxk!alu shedevil@portia.Stanford.EDU (Anne Prisk) (08/08/90)
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 >> > Someone speculates that it's cause of a) a beta version, and b) too many added fonts. Then someone says: > >No, I had the same problem with non-beta ver 3.0. I was trying >to run WINEYES, but got the same errormessage, although the file was >there. As far as I know, I have only the standard fonts installed. 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! -- <*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*> Anne (She Devil) Mitchell - Stanford Law - BBS: 415-497-5291,1200,N,8,1 No disclaimer necessary as this is *my* account, and besides - nobody would ever accuse anyone else of having these opinions anyway!
mcjilton@handel.CS.ColoState.Edu (charles mar mcjilton) (08/09/90)
In article <8685@gremlin.nrtc.northrop.com> maurit@nrtc.nrtc.northrop.com (Mark Aurit <maurit>) writes: >A while back I posted a message about getting the following messge when >I click on the "command.com" button in the MAIN menu: > > Application Execution Error > Cannot find file; check to insure the path and > filename are correct We were having the same problem. We found that the problem was with a TS program we were running that was being accessed under windows (It was the BTrieve record manager). We have fixed the problem by using the '/r' switch. Hope this helps. <Using a friends account> Sean
rommel@lan.informatik.tu-muenchen.dbp.de (Kai-Uwe Rommel) (08/09/90)
In article <1990Aug7.140051.9724@rice.edu> adnan@screech.rice.edu (Sarmad Adnan) writes: > >> No, I had the same problem with non-beta ver 3.0. I was trying >> to run WINEYES, but got the same errormessage, although the file was >> there. As far as I know, I have only the standard fonts installed. > >For Wineyes you need win87em.dll in your windows or windows/system >directory. And for marked Windows 2.x applications you need to copy win87em.dll to win87em.exe. Kai Uwe Rommel -- /* Kai Uwe Rommel * Munich * rommel@lan.informatik.tu-muenchen.dbp.de */
bcw@rti.rti.org (Bruce Wright) (08/09/90)
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
aap@cbnewsl.att.com (alan.a.parker) (08/09/90)
From article <1990Aug8.020846.19494@portia.Stanford.EDU>, by shedevil@portia.Stanford.EDU (Anne Prisk): > 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 >>> > > Someone speculates that it's cause of a) a beta version, and b) too many > added fonts. Then someone says: >> >>No, I had the same problem with non-beta ver 3.0. I was trying >>to run WINEYES, but got the same errormessage, although the file was >>there. As far as I know, I have only the standard fonts installed. > > 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! > > -- > <*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*><*> > Anne (She Devil) Mitchell - Stanford Law - BBS: 415-497-5291,1200,N,8,1 > No disclaimer necessary as this is *my* account, and besides - nobody > would ever accuse anyone else of having these opinions anyway! I solved this problem by putting a copy of win87em.dll into my windows directory and renaming it win87em.exe. I'm not sure why it worked, but it did, with several different applications. Alan Parker AT&T Bell Laboratories Whippany N.J. att!pace!aap
aaron@jessica.stanford.edu (Aaron Wallace) (08/10/90)
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 >>> > >Someone speculates that it's cause of a) a beta version, and b) too many >added fonts. Then someone says: >> >>No, I had the same problem with non-beta ver 3.0. I was trying >>to run WINEYES, but got the same errormessage, although the file was >>there. As far as I know, I have only the standard fonts installed. > >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! One cause of this error is not having WIN87EM.EXE in the Windows directory. Under Windows 2.xx WIN87EM.EXE was expected in the \WIN (or whatever) directory, but Windows 3.0 puts a WIN87EM.DLL file in the \WIN\SYSTEM directory. The easiest fix is to copy WIN87EM.DLL to WIN87EM.EXE in the appropriate place. Note that using the 2.xx version of WIN87EM.EXE is not recommended... Aaron Wallace
maurit@nrtc.nrtc.northrop.com (Mark Aurit <maurit>) (08/14/90)
In article <1990Aug9.161816.20126@cbnewsl.att.com> aap@cbnewsl.att.com (alan.a.parker) writes: >From article <1990Aug8.020846.19494@portia.Stanford.EDU>, by shedevil@portia.Stanford.EDU (Anne Prisk): >> 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 >>>> > >> Someone speculates that it's cause of a) a beta version, and b) too many >> added fonts. Then someone says: >>> <various stuff about fixing this problem> In the short time since I first posted the "Barfing up apps" message I have received a number of helpful ideas, some quite exotic. I tried them all, and none of them worked. But I did fix it! I simply set FILES= and BUFFERS= both 20. My PS/2 works fine with the FILES=30 and BUFFERS=10, my 386 clone (you may have seen it advertised in the back of PC Week as "the Beast") requires the other setting. Sigh. Mark maurit@nrtc.northrop.com "the LORD is my God"
poffen@sj.ate.slb.com (Russ Poffenberger) (08/16/90)
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 >>> > >Someone speculates that it's cause of a) a beta version, and b) too many >added fonts. Then someone says: >> >>No, I had the same problem with non-beta ver 3.0. I was trying >>to run WINEYES, but got the same errormessage, although the file was >>there. As far as I know, I have only the standard fonts installed. > >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! > I believe that the solution is to make sure that win87em.exe or win87em.dll is in a directory in your path (like the win3 directory itself) Russ Poffenberger DOMAIN: poffen@sj.ate.slb.com Schlumberger Technologies UUCP: {uunet,decwrl,amdahl}!sjsca4!poffen 1601 Technology Drive CIS: 72401,276 San Jose, Ca. 95110 (408)437-5254
tat@pccuts.pcc.amdahl.com (Tom Thackrey) (08/22/90)
In article <1990Aug15.225736.22515@sj.ate.slb.com> poffen@sj.ate.slb.com (Russ Poffenberger) writes: >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 >>>> > >I believe that the solution is to make sure that win87em.exe or win87em.dll is >in a directory in your path (like the win3 directory itself) Close. The problem is a little more complicated. If you are running a. windows 2.xx app you need WIN87EM.EXE, windows 3 apps need WIN87EM.DLL. The latter is installed in the subdirectory SYSTEM by the windows 3 install process. To eliminate the problem copy WIN87EM.DLL to the windows directory AND copy it again renameing it to WIN87EM.EXE for the benefit of the Windows 2 apps. Note that not all apps require the WIN87EM code and that the .DLL and .EXE versions are the same except for the name. Kudos to Microsoft for their help finding the problem and a poke with a sharp stick for a horrible error message.:-) -- Tom Thackrey sun!amdahl!tat00 [ The opinions expressed herin are mine alone. ]