
                  DOS/Windows under OS/2           (Fidonet)

                 Saturday, 04-Dec-1999 to Friday, 10-Dec-1999

+----------------------------------------------------------------------------+

From: Gregory Urban                                     05-Dec-99 23:11:00
  To: All                                               06-Dec-99 09:49:05
Subj: GPFs in WinOS2

Greetings,

Some time ago I upgraded and committed to Fixpak 12 for Warp 4.
Things have been running pretty smoothly but now I've got a 
problem.  I am not sure if it is FP12 that is causing this or 
what but when I attempt to run a Win16 app, Cook'n99, I get
General Protection Faults!  

If I run a full-screen WinOS2 session and attempt to launch Cook'n99
I get:

	PROGMAN caused a General Protection Fault in
	module OS2K386.EXE at 0002:1C56

and the full screen WinOS2 session closes and I'm dumped back onto 
the Warp desktop.

If I try running Cook'n99 in a seamless WinOS2 session I get:

  	WINSHELD caused a GPF in module OS2K386.EXE
	at 0002:1C56.

then click "OK" and get

	USER.EXE caused a GPF in OS2K386.EXE at
	0001:1075

followed by a SYS3175.

Any idea what gives?  I really like this particular recipe program.

Thanks,
Greg
___ Blue Wave/OS2 v2.30 [NR]

--- QScan/PCB v1.19b / 01-0671
 * Origin: AirPower-telnet://bbs.airpower.dynip.com 610-259-2198 (1:273/408)

+----------------------------------------------------------------------------+

From: David Noon                                        09-Dec-99 20:55:17
  To: Gregory Urban                                     10-Dec-99 06:58:07
Subj: GPFs in WinOS2

Hi Gregory,

Replying to a message of Gregory Urban to All:


 GU>    WINSHELD caused a GPF in module OS2K386.EXE
 GU>  at 0002:1C56.

 GU> then click "OK" and get

 GU>  USER.EXE caused a GPF in OS2K386.EXE at
 GU>  0001:1075

 GU> followed by a SYS3175.

 GU> Any idea what gives?  I really like this particular recipe program.

I have seen these plenty of times. They are usually caused by video driver
problems. The solution is quite simple.

Edit your SYSTEM.INI and look for the line that reads:

  useos2shield=1

and change it to:

  useos2shield=0

Once you have made this change, you will lose that little OS/2 icon in the
bottom left corner of your full-screen WIN-OS/2 sessions, but the kernel
itself will be more stable.

Regards

Dave
<Team PL/I>

--- FleetStreet 1.24.1
 * Origin: The man who broke the bank at Monte Carlo (2:257/609.5)
154/15
260/10
396/1

+----------------------------------------------------------------------------+

+============================================================================+
