🚀 go-pugleaf

kbennett@cpcug.org (Keith Bennett) wrote:

>We have a PM app running on OS/2 *2.1* systems that has a button
>which starts an OS/2 Window session.  Sometimes (but not usually),
>when the user selects the button, the following error message appears:


> ---
>OS/2 Window Cannot Start.

>Make sure the path for the program is correct and the file is an OS/2
>or DOS program.  There might not be enough memory available to run
>the program or the file may be locked by another process.  Do you
>wish to modify the setting for the object OS/2 Window?

> Yes    Cancel   Help
> ---

>I also tried it from the command line, "start cmd".  We got error #1059: 

>SYS1059: The system cannot execute the specified program.

>EXPLANATION: The operating system encountered an unknown
>error while attempting to start up the program.

>ACTION: Contact the supplier of the program.

>When I tried "start /fs cmd" to start it in full screen mode, it worked
>fine.

>Anyone know what this might be?  I don't think it's a memory or
>thread availability issue because just before this button is
>selected, several processes are shut down, freeing up more memory and
>threads than the OS/2 Window uses.

>When the machine is rebooted, it works fine. (?!?!)

>Thanks for any help.

>- Keith

>-- 
>--------------------------------------------------------------------------
>Keith Bennett                             Bennett Business Solutions, Inc.
>Silver Spring, MD USA                     OS/2 & DOS Software Development
>kbennett@cpcug.org                        (301) 871-7696


The problem appears to be related to a memory leak. I`m sure that if
you checked very little except a full screen session will start on the
machine. Try booting the machine as clean as possible and the do the
exercise of starting OS/2 windows.