🚀 go-pugleaf

On Wed, 28 Aug 2002 11:56:52, rjf@yyyindoserv.com (rj friedman) wrote:

> On Wed, 28 Aug 2002 11:33:58 UTC cocke@catherders.com wrote:
> 
> �>Win32k.sys used to work for me - but it no longer does - on  three
> �>separate systems, no less. During boot I get the  message that
> �>'Win32k.sys failed before probing the kernel'.
> �
> �>I don't know if it has to do with the latest versions of 
> �>ODIN, or something I did to 'improve' my machines, but I am  back to
> �>calling everything via 'pe' command files.
> 
> 
> �I've seen that a few times.  It means that the w32k.sys doesn't understand
> �the version of the OS/2 kernel that you've got.  As I understand it,
> �w32k.sys is coded for a particular kernel or set of kernels - it needs to
> �know specific memory locations.  
> 
>  
> Thanks for the info. If that's the case, they are going to 
> have ongoing problems. I would think they are going to have 
> to come up with something more flexible.

They have:  the symbol file (os2krnl.sym) that comes with most kernel
updates.  It identifies, by name, the location of whatever data (and
presumably, code) win32k.sys has to modify.  As long as the kernel
doesn't change radically, win32k should always succeed when provided
with this roadmap.  Since some kernel versions are so widely used,
win32k has this info built-in, so it doesn't need a symbol file for
these milepost releases.


-- 
 == == almost usable email address:  DragText AT E-vertise.Com == ==
___________________________________________________________________

                |               - DragText v3.5 -
Rich Walsh      |  A Distinctly Different Desktop Enhancement
Ft Myers, FL    |         http://e-vertise.com/dragtext
___________________________________________________________________