Changeset 2897


Ignore:
Timestamp:
Feb 25, 2000, 7:15:42 PM (26 years ago)
Author:
bird
Message:

Updated win32k section.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Readme.txt

    r1754 r2897  
    58582.0.1 Log files
    5959---------------
    60 The alpha 5 binaries and daily build zipfiles can generate logfiles to show 
     60The alpha 5 binaries and daily build zipfiles can generate logfiles to show
    6161what a win32 application is doing. This can be very useful to determine
    6262why certain applications don't run correctly.
    6363
    64 The major disadvantage of loggging is the overhead. Therefor it has been 
     64The major disadvantage of loggging is the overhead. Therefor it has been
    6565disabled by default in the alpha 5 release and daily builds.
    6666To enable logging set the environment variable WIN32LOG_ENABLED:
     
    122122
    123123
    124 2.3 The Ring0 conversion utility driver (WIN32K.SYS)
    125 ----------------------------------------------------
     1242.3.0 Win32k.sys - native OS/2 PE-"loader"
     125----------------------------------------
    126126
    127127The win32k.sys driver makes PE (Win32) executables equal to native OS/2
     
    148148-------------
    149149
    150 The Win32k.sys is alpha software and any bugs which haven't been found
     150The Win32k.sys is quite alpha software and any bugs which haven't been found
    151151yet may crash and/or corrupt you entire system! Make sure you have backed up
    152152important stuff first!
     
    164164
    165165Win32k should work on any Warp 4 or Warp Server for e-business installations
    166 which Odin32 works on. It requires only one thing, a kernel symbol file. The
    167 kernel symbol is looked for in \OS2\PDPSI\PMDF\WARP4 and
    168 \OS2\PDPSI\PMDF\WARP45_U/S. All warp 4 and WE4eB installations should have
    169 those direcotries (we hope). It is updated when you install a new fixpack - so
    170 there is really nothing to worry about for the common user.
    171 
    172 For those playing with debug-kernels, make sure that OS2KRNL.SYM is matching
    173 the running kernel, while this file too is investigated. (The complete list
    174 is found in src\Win32k\dev16\probkrnl.c,apszSym[] - odin32 source tree.)
    175 
    176 
    177 2.3.2.1 Warp 3
    178 --------------
    179 
    180 Win32k is not tested with Warp 3. It is supposed to work with Warp 3 provided
    181 that the os2krnl.sym file is present. Warp Server 4 has this, common Warp 3
    182 doesn't.
    183 
    184 
    185 2.3.3 Installation
    186 ------------------
    187 
    188 To use Win32k.sys you have to add the following line into your config.sys:
    189     device=<d:\path\>win32k.sys
    190 
    191 Where <d:\path\> is the path to the win32k.sys, i.e. the odin32 executables
    192 directory.
    193 
    194 After doing this, you'll have to reboot your machine to load the driver. During
    195 the boot process you will on a successful installation see some lines of
    196 technical info and finally a line saying:
    197     'Win32k.sys succesfully initiated!'
    198 
    199 If you don't see the line above something is wrong.
    200 
    201 
    202 2.3.4 Win32k parameters
    203 -----------------------
    204 
    205 There are some useful parameters for Win32k:
    206 -Q             Quiet driver initiation. (Default is verbose (-V) initiation.)
    207 -V             Verbose driver initiation. Default.
    208 -S:<filename>  Full path to the current OS/2 kernel symbol file.
    209 -K:<filename>  Full path to the running OS/2 kernel.
    210 
    211 
    212 2.3.5 Rings - Ring 0 / Ring 3
    213 -----------------------------
    214 
    215 FYI. Ring 0 is the most priveleged level of execution in OS/2. The OS/2 kernel
    216 and device drivers execute at this level, while user applications execute in
    217 Ring 3, the least priveleged executing level.
     166which Odin32 works on. It no longer requires a kernel file for non-debug
     167kernels. Win32k does now contain a "database" for the most recent retail
     168kernels. Currently this is:
     169    Warp 4 fp#5 -> fp#12
    218170
    219171
     
    262214----------------
    263215
    264 This readme is intended for making people more familiar with ODIN and to 
    265 describe various aspects of the project such as accessing latest sources via 
    266 cvs, building the binaries, running win32 applications, how to identify and 
    267 report problems and bugs, as well as how to participate in this very 
     216This readme is intended for making people more familiar with ODIN and to
     217describe various aspects of the project such as accessing latest sources via
     218cvs, building the binaries, running win32 applications, how to identify and
     219report problems and bugs, as well as how to participate in this very
    268220promising project.
    269221
     
    276228          (version 3.6 might also work, but version 4 is not
    277229           recommended)
    278         - OS/2 Warp 4 Toolkit (project apparently doesn't compile with 
     230        - OS/2 Warp 4 Toolkit (project apparently doesn't compile with
    279231          VAC's OS/2 headers)
    280232          Might also work with EMX headers. (haven't tried this!)
     
    285237
    286238Changes from last source code release:
    287         - Uses Wine headers and a stripped down version of os2win.h (Open32 
     239        - Uses Wine headers and a stripped down version of os2win.h (Open32
    288240          header)
    289241        - All Open32 apis have the 'O32_' prefix.
    290         - All Open32 declarations are appended with '_O32' (mostly due to 
     242        - All Open32 declarations are appended with '_O32' (mostly due to
    291243          calling convention differences)
    292244        - nmake DEBUG=1 builds the debug version
     
    311263          default value (150b))
    312264        - Use the correct Win32 api when there are two version (ascii & unicode)
    313           Calling the standard one (SendMessage) causes a error during 
     265          Calling the standard one (SendMessage) causes a error during
    314266          compilation.
    315267          Use SendMessageA instead.
     
    320272--------------------------------------
    321273
    322 Please check out http://www.netlabs.org/ and http://www.netlabs.org/odin. 
     274Please check out http://www.netlabs.org/ and http://www.netlabs.org/odin.
    323275
    324276
     
    326278-------------------------
    327279
    328 Basically, if your system setup meets above stated requirements, everything you 
     280Basically, if your system setup meets above stated requirements, everything you
    329281need to do for a binary build is:
    330282
     
    335287  nmake release (not working right now!)
    336288
    337 As the current state of the project is still known to be alpha level, one should 
    338 expect some functions not to work properly. Therefore, we recommend the use of 
    339 the debug-version which creates long logfiles for problem determination purpose 
     289As the current state of the project is still known to be alpha level, one should
     290expect some functions not to work properly. Therefore, we recommend the use of
     291the debug-version which creates long logfiles for problem determination purpose
    340292and to allow active debugging with debuggers such as IPMD, ICAT, KDB, etc.
    341293
    342 Please note if you do not want to suffer from the performance loss of writing 
    343 logfiles, you can disable logging even with the debug binaries of ODIN by 
     294Please note if you do not want to suffer from the performance loss of writing
     295logfiles, you can disable logging even with the debug binaries of ODIN by
    344296setting:
    345297
     
    356308------------------
    357309
    358 ODIN is moving at a fast pace. Sometimes side effects of source dependencies may 
     310ODIN is moving at a fast pace. Sometimes side effects of source dependencies may
    359311require you to do a full rebuild of the binaries instead of an incremental build.
    360312
    361 However, rarely it also happens the sources contained in the CVS repository do 
    362 not build completely due to erroneous source code. Usually, this is fixed within 
     313However, rarely it also happens the sources contained in the CVS repository do
     314not build completely due to erroneous source code. Usually, this is fixed within
    363315two days at maximum.
    364316In such event, one can normally stick with the previous version of the particular
     
    371323------------------------------------
    372324
    373 http://www.os2.org/ has setup an ftp server that hosts the automatically 
    374 built binaries on daily basis. For people that do not have a suitable 
     325http://www.os2.org/ has setup an ftp server that hosts the automatically
     326built binaries on daily basis. For people that do not have a suitable
    375327development setup for ODIN, we provide the latest binary code that way.
    376328
     
    379331-------------------------
    380332
    381 As ODIN became an open source project, everybody is kindly invited to 
     333As ODIN became an open source project, everybody is kindly invited to
    382334contribute his/her share to the progress of the project. May it be
    383 active coding, fixing bugs or just providing detailed information about 
     335active coding, fixing bugs or just providing detailed information about
    384336examined problems.
    385337
    386338We suggest you subscribe to win32os2-wai and the corresponsing mailing lists
    387339on http://www.egroups.com.
    388 In case you are interested in participating, every member of the project will 
    389 be happy to give you direction to the right places and to give a personal 
     340In case you are interested in participating, every member of the project will
     341be happy to give you direction to the right places and to give a personal
    390342introduction to further development of the particular modules.
    391343
Note: See TracChangeset for help on using the changeset viewer.