🚀 go-pugleaf

In <D82D4H.A7M@lexmark.com> gczaja@lexmark.com(Gregory Czaja) writes:

>In <3oarqb$mue@news.iastate.edu>, barisax@iastate.edu (Jason W Blair) writes:
>>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.

>Jason,

>What version of OS/2 is it? Is is "for Windows" (i.e. using the original
>Windows code) or is it with Windows built-in (i.e. fullpak)?

>Most likely the customer installed something under Windows.
>It may be a video driver or unsupported version of Win32s...

>You can try:

> selective reinstall of Windows support

> open a fullscreen DOS session and run WIN /B, watch the messages.

>Thanks, <G>reg                                  ---> DeskMan/2 utilities
>(WZ00329 on TalkLink, 71052,720 on CIS)


Thanks for the info! 8-) I ran win /b and found out that the keyboard
driver failed to load when I checked the bootlog.txt file. Also thanks
to those who responded via email. My client and I are very very happy
now. 8-) 
BTW, it's nice to know that Warp is smart enough to sense the problem
and just kill the offending app. I'd like to see a Micro$oft product do
that, ha ha.

Jason - TeamOS2




-- 
Jason W Blair			ADP Center systems team
barisax@iastate.edu