Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!iuvax!noose.ecn.purdue.edu!samsung!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!nuug!ulrik!ulrik!oivindt From: oivindt@ulrik.uio.no (Oivind Toien) Newsgroups: comp.windows.ms Subject: Re: Barfing up 3.0 apps Message-ID: Date: 6 Aug 90 19:40:03 GMT References: <8685@gremlin.nrtc.northrop.com> <3793@tuminfo1.lan.informatik.tu-muenchen.dbp.de> Sender: oivindt@ulrik.uio.no (Oivind Toien) Organization: University of Oslo, Norway Lines: 38 In-Reply-To: rommel@lan.informatik.tu-muenchen.dbp.de's message of 6 Aug 90 09:56:40 GMT 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 ) 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.