
                  DOS/Windows under OS/2           (Fidonet)

                 Saturday, 11-Dec-1999 to Friday, 17-Dec-1999

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

From: Gregory Urban                                     10-Dec-99 08:43:00
  To: David Noon                                        11-Dec-99 06:20:20
Subj: GPFs in WinOS2

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

       <snip>

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

       <snip>

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

Thought that could be an issue.  I was using MGA GRADD with my Matrox
Millenium II 4mb card.  I downloaded the 12/3/99 release drivers from the
Matrox web site and installed them.  They didn't fix the problem...but things
do seem a bit zippier...

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

 DN> useos2shield=1

 DN> and change it to:

 DN> useos2shield=0

Just gave it a try....

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

Didn't work...if I run a SEAMLESS WinOS2 session, either Progman or the
COOKN99.EXE program I _still_ get the Winsheld GPF in OS2K386.EXE at
0002:1C56.  If I run a full-screen WinOS2 session and try launching the 
program I PROGMAN GPFs in OS2K386.EXE at 0002:1C56.  

Other ideas?

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                                        12-Dec-99 19:13:11
  To: Gregory Urban                                     13-Dec-99 03:32:21
Subj: GPFs in WinOS2

Hi Gregory,

Replying to a message of Gregory Urban to David Noon:

[snip]
 DN>> Edit your SYSTEM.INI and look for the line that reads:

 DN>> useos2shield=1

 DN>> and change it to:

 DN>> useos2shield=0
[snip]

 GU> Didn't work...if I run a SEAMLESS WinOS2 session, either Progman or
 GU> the COOKN99.EXE program I _still_ get the Winsheld GPF in OS2K386.EXE
 GU> at 0002:1C56.

When you have useos2shield=0 in SYSTEM.INI the WINSHELD.EXE program should not 
even be started. I don't see how it could GPF under such circumstances.

 GU>  If I run a full-screen WinOS2 session and try
 GU> launching the  program I PROGMAN GPFs in OS2K386.EXE at 0002:1C56.

That's the same location.

As I read that paragraph, the full-screen session starts Ok, but when you ask
the PROGMAN shell to run the application program it abends with that GPF. This 
implies that PROGMAN starts up, which it not the usual outcome when the video
drivers are playing up with WINSHELD's context switching.

 GU> Other ideas?

Not really.

Was OS2K386.EXE modified by the Fixpak you applied? If so, what changes were
made? [These should be described in one of the README files for the FP.]

Regards

Dave
<Team PL/I>

--- FleetStreet 1.24.1
 * Origin: The man who broke the bank at Monte Carlo (2:257/609.5)

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

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