Changeset 1754


Ignore:
Timestamp:
Nov 15, 1999, 11:42:01 PM (26 years ago)
Author:
sandervl
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Readme.txt

    r1753 r1754  
    4747
    4848
    49 2.0 Using Odin to run your Windows applications
     492.0 Installing Odin
     50-------------------
     51Odin installation must be done manually at this time. However, only
     52a few simple tasks must be completed:
     53  - Unzip the odin zipfile into a new directory (i.e. C:\ODIN)
     54  - Add this directory to the LIBPATH and PATH statements of your config.sys
     55  - Optionally install the win32k device driver (see 2.3.3)
     56  - Reboot your machine
     57
     582.0.1 Log files
     59---------------
     60The alpha 5 binaries and daily build zipfiles can generate logfiles to show
     61what a win32 application is doing. This can be very useful to determine
     62why certain applications don't run correctly.
     63
     64The major disadvantage of loggging is the overhead. Therefor it has been
     65disabled by default in the alpha 5 release and daily builds.
     66To enable logging set the environment variable WIN32LOG_ENABLED:
     67   SET WIN32LOG_ENABLED=1
     68
     69To disable logging again, you must clear this variable:
     70   SET WIN32LOG_ENABLED=
     71
     722.1 Using Odin to run your Windows applications
    5073-----------------------------------------------
    5174
     
    5376
    5477
    55 2.1 The Ring3 Win32 Loader (PE.EXE)
     782.2 The Ring3 Win32 Loader (PE.EXE)
    5679----------------------------------
    5780
     
    78101
    79102
    80 2.1.1 PE loader issues
     1032.2.1 PE loader issues
    81104----------------------
    82105
     
    84107a process utility such as pstat will always show PE.EXE as the
    85108executable file.
    86 It is also possible that a certain Win32 applications becomes
     109It is also possible that a certain Win32 application becomes
    87110a zombie (that is when it does certain things the OS/2 kernel
    88111cannot recover such as die when waiting on a semaphore). Then
     
    99122
    100123
    101 2.2 The Ring0 conversion utility driver (WIN32K.SYS)
     1242.3 The Ring0 conversion utility driver (WIN32K.SYS)
    102125----------------------------------------------------
    103126
     
    105128executables by implementing a Ring 0 on-the-fly converter. The converter is
    106129Pe2Lx.exe. So, everything that works with Pe2Lx will probably work with
    107 win32k.sys. And vice versa, when Pe2lx don't make it, win32k.sys won't either.
     130win32k.sys. And vice versa, when Pe2lx can't handle it, win32k.sys won't either.
    108131
    109132You may wonder how you may run a Win32 program using a device driver. You
     
    122145
    123146
    124 2.2.1 WARNING
     1472.3.1 WARNING
    125148-------------
    126149
    127 The Win32k.sys is quite alpha software and any bugs which haven't been found
     150The Win32k.sys is alpha software and any bugs which haven't been found
    128151yet may crash and/or corrupt you entire system! Make sure you have backed up
    129152important stuff first!
     
    137160
    138161
    139 2.2.2 Requirements
     1622.3.2 Requirements
    140163------------------
    141164
     
    152175
    153176
    154 2.2.2.1 Warp 3
     1772.3.2.1 Warp 3
    155178--------------
    156179
    157180Win32k is not tested with Warp 3. It is supposed to work with Warp 3 provided
    158 that the os2krnl.sym file is present. Warp Server 4 have this, common Warp 3
    159 don't.
    160 
    161 
    162 2.2.3 Installation
     181that the os2krnl.sym file is present. Warp Server 4 has this, common Warp 3
     182doesn't.
     183
     184
     1852.3.3 Installation
    163186------------------
    164187
     
    169192directory.
    170193
    171 After doing this you'll have to reboot your machine to load the driver. During
     194After doing this, you'll have to reboot your machine to load the driver. During
    172195the boot process you will on a successful installation see some lines of
    173196technical info and finally a line saying:
    174197    'Win32k.sys succesfully initiated!'
    175198
    176 If you don't see the line above something is wrong!
    177 
    178 
    179 2.2.4 Win32k parameters
     199If you don't see the line above something is wrong.
     200
     201
     2022.3.4 Win32k parameters
    180203-----------------------
    181204
     
    187210
    188211
    189 2.2.5 Rings - Ring 0 / Ring 3
     2122.3.5 Rings - Ring 0 / Ring 3
    190213-----------------------------
    191214
    192215FYI. Ring 0 is the most priveleged level of execution in OS/2. The OS/2 kernel
    193 and device drivers execute at this level, while user applications executes in
     216and device drivers execute at this level, while user applications execute in
    194217Ring 3, the least priveleged executing level.
    195218
    196219
    197 2.3 The Ring3 conversion utility (PE2LX.EXE)
     2202.4 The Ring3 conversion utility (PE2LX.EXE)
    198221--------------------------------------------
    199222
     
    242265describe various aspects of the project such as accessing latest sources via
    243266cvs, building the binaries, running win32 applications, how to identify and
    244 report problems and bugs, as well as how to acticely participate in this very
     267report problems and bugs, as well as how to participate in this very
    245268promising project.
    246269
     
    327350  SET NOWIN32LOG=
    328351
     352Logging is enabled by default in the debug build, but disabled by default
     353in the nodebuginfo build and not present in the release build.
    329354
    3303553.1 Build problems
    331356------------------
    332357
    333 ODIN is moving at fast pace. Sometimes side effects of source dependencies may
     358ODIN is moving at a fast pace. Sometimes side effects of source dependencies may
    334359require you to do a full rebuild of the binaries instead of an incremental build.
    335360
Note: See TracChangeset for help on using the changeset viewer.