From: scastill@nmsu.edu (Steve Castillo)
Newsgroups: comp.os.os2.misc
Subject: Re:  very strange bug w/winos2
Date: 10 Sep 92 15:37:22 GMT
Distribution: comp.os.os2.misc
Organization: NMSU Computer Science


In article <520O02.y21c101@JUTS.ccc.amdahl.com>
cdf00@OUTS.ccc.amdahl.com (Chris Finan) writes:


>>I am experiencing a very strange problem in os/2 when running full
>>screen windows apps.  I am running on a 50 MHz EISA 486 with an award
>>bios and an ATI Graphics Ultra video card.  The machine has 16 Mbytes
>>of memory.  I would like to be able to run both full screen dos apps
>>and windows apps simultaneously.  For instance Wordperfect for Windows
>>and Drawperfect for DOS.  However, whenever I startup a full screen
>>windows session, switch to the desktop, switch back to the windows
>>full screen session and then back again and then try starting a
>>windowed dos session, a
>>full screen dos session or a full screen os/2 session, OS/2 does not
>>open any of these three sessions correctly.  This is independant of whether or not the full screen
>>windows session is still running.  Trying to bring up any of these
>>three types of sessions only results in a full screen dos session
>>which does not echo any of the characters that I type.  I found 
>>that if my initial full screen windows session was Wordperfect,
>>trying to start up any of the other three sessions puts me into the
>>startup directory for wpwin!  If I simply startup full screen windows
>>initially, then trying to start up any of the other three sessions
>>puts me into the startup directory for winos2 (\).  It almost acts like
>>the three sessions are using the settings from my windows app rather
>>than their own once I have gone through the previously described
>>sequence with the winos2 full screen session.  However I checked the
>>settings for all the sessions, and all seems well.
>>
>>This occurs with both the generic IBM 8514 or ultra driver for
>>windows.  I am using the IBM 8514 driver for os/2.
>>
>>I would appreciate any words of wisdom on this one.
>>
>>Steve Castillo
>>Electrical Engineering
>>New Mexico State U.
>>Las Cruces, NM  88003
>>
>>(505)646-3214
>>scastill@nmsu.edu

>I have the exact same problem as you describe. I also have an ATI graphics
>ultra. Machine is a 486DX2 50Mhz ISA with AMI bios. One thing I noticed is
>that the only problem is that the screen is messed up. You really are in the
>correct directory. If you create a file via a DOS command (typing blind 
>since the characters don't show up) it is in the directory the session is 
>supposed to be in, not the directory shown in the screen command prompt.

>You can avoid this problem by toggling the values of the              
>VIDEO_SWITCH_NOTIFICATION and the XGA_IOTRAP settings for all Full Screen DOS
>and WinOS2 sessions. (Sorry I can't remember the exact settings or the 
>setting values but I'm not at my OS/2 machine now.)

>However after making the above setting changes I have a different (but less
>disastorous) problem. When I want to switch from the WinOS2 full screen 
>session to the OS2 desktop I click on the OS2 Icon. My keyboard and mouse 
>now lock up for just about 13 seconds exactly with no disk activity.
>After the 13 seconds the switch to the OS2 Desktop happens and everything is
>back to normal. 
>
>I'm curious if you have similar pause in your system after making the setting 
>changes. 
>
>Does anyone know how to solve these problems?
>
>Chris Finan
>cdf00@cd.amdahl.com
>408-737-5366

I did try your fix and everything works except for the pause after I
switch from the full screen winos2 session back to the os/2 desktop.
I get an annoying 14 - 15 second pause everytime.  I also get a
"shadow" of the winos/2 icon that I clicked on from the WPS that
remains with my mouse pointer for a short time
after I have switched backed to the full screen
windows session.  Strange.  Thanks for the information.
--
*****************************************************************
Steve Castillo
New Mexico State University
Las Cruces, NM

scastill@nmsu.edu
(505)646-3214