🚀 go-pugleaf

>   barisax@iastate.edu (Jason W Blair) wrote:
>>This is a cry for help to anyone who has seen this problem 
>before. For
>>no apparent reason, one of my clients has lost the ability to 
>run any of
>>his windows applications. Whenever he tries to launch a windows 
>based
>>application, or a win-os2 window or full screen session, the 
>hard drive
>>is accessed for about a half second, and then nothing. The apps 
>will not
>>run from the launchpad, or from their original icons. They will 
>not run
>>from an os2 command line or a dos command line.
>
>Snip, snip
>
>>
>>Thanks in advance.  Jason - barisax@iastate.edu
>>			    TeamOS2
>>
>>
>
>I had very similar symptoms after accidently overwriting my OS/2 
>autoexec.bat file with a DOS autoexec.bat file.  I reinstalled 
>the OS/2 DOS support which reinstalled the default OS/2 
>autoexec.bat file which fixed the problem.

I also experienced a sudden inability to load any Windows app a
couple of days ago, and fixed it by reinstalling DOS support.  But
I don't think it was my AUTOEXEC.BAT file that was the problem,
as I immediately replaced the default one with the one I had been
using and it still worked.  Before I stumbled on this solution, I tried
changing a number of things in the \WINDOWS directory including
reinstalling WFWG 3.11 followed by Selective Install of WINOS2
support and none of that helped.  So I would recommend that
anyone with this problem first try Selective Install of just the
DOS support before messing with anything else.


//  Paul Saletan                 Austin, Texas
//  saletan@bga.com           (512)926-8585