🚀 go-pugleaf

I had exactly the problem (running fullpack) this morning. Solution:
Full restore of c:\os2\mdos from tape (this also restores the winos2
directory).

Cheers
-Markus

In article <3oe16u$nt8@beyond.escape.com>, j_weedon@escape.com  (Jay Weedon) writes:
>>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. 
>
>Why not try this simple diagnostic: Open a full-screen DOS session, and type at
>the command prompt "winos2". You'll probably see an error message of some
>kind that may give you a clue about what's going on. Video drivers are often
>the culprits here, but corrupted files, changed paths etc. are also possibilities.
>
>Jay Weedon.



-- 
Markus Weber, Infotec SA, Zurich
email: markus@infotec.ch, markus@dial.eunet.ch