🚀 go-pugleaf

In a recent posting feustel@netcom.COM (David Feustel) writes:
>Now that I've got your attention, the problem is that Windows cannot
>find any of my non MS programs when I attempt to invoke them via the
>program manager. I've spent some time trying to get hold of MS to ask
>about this, but I can't get through and the $$$ are adding up.  All of
>these programs start properly under PCDOS 3.3. Is it possible that MS
>didn't test dos 5.0 with windows?!!!

I've been watching this thread and just realized that I've seen the
symptoms while trying to track down a nasty interaction between Windows
and (non-Windows) comm programs running in a DOS window.  You'll get 
the symptoms you described ("unable to find program" or whatever the
error message text is) if you run out of file handles.  (I saw it
because Windows shattered and returned to DOS without closing files.)

Check the files=nnn line in CONFIG.SYS to make sure you've got a minimum
of 30 (per the Windows manual) plus whatever your other programs are
using.

Joe Morris