ODIN on OS/2 Warp 3 HOWTO

Copyright © 2002 by

2003-Mar-03

This is a 'quick and dirty' HOWTO document describing how to enable OS/2 Warp 3 running 32bit windows applications with the ODIN runtime.


Table of Contents
1. Requirements
1.1. Open32 (DAX)
1.2. Kernel / OS/2 PM Merged Library
1.3. WarpIN
1.4. ODIN
2. Installation
2.1. Before you begin
2.2. Install ODIN
3. Opera
3.1. Requirements
3.2. Install Opera
4. Links

1. Requirements

1.1. Open32 (DAX)

Before go on please read section 'Before you begin' !

ODIN is build on top of IBMs Open32 therefore you need this library. Open32 is included in Fixpak 26 and above, it is recommend that you install the latest available Fixpak for the OS/2 Warp 3 Client - FP40, this can be downloaded for free from IBM.
Note: Do not install any Fixpak above 40, these are for Warp Server only !

Check your bootdrive for the following files...

\OS2\DLL\pmwinx.dll DAX Library  
\OS2\DLL\pmddeml.dll DDE Library  
\OS2\INSTALL\inst_dos.exe Window DOS Registry Initialization Routine  
\OS2\SYSTEM\rsrv.exe Registry Server  

... if they exist Open32 is installed. Build up the registry and verify that it is fully working using the Regedit/2 registry editor. However IBM didn't include this tool as in the Warp 4 Fixpaks, get the files from Warp 4 (Fixpak 6 or higher) or any Warp 4.5x version like eCS, WSeB ... . You can also download my own build Regedit/2 package, available in english or german.

FILE COPY TO  
README.REG \OS2\HELP  
REGCONV.EXE \OS2\SYSTEM  
REGEDIT.HLP \OS2\HELP  
REGEDIT2.EXE \OS2\SYSTEM  
REGISTRY.DLL \OS2\DLL  
REGISTRY.MSG \OS2\SYSTEM  
REGISTRY.REP \OS2\SYSTEM  

Start REGEDIT2.EXE in a command line window or from the WPS, the first time you start the editor you see a popup window that the registry is currently build/imported, afterwards you have 3 refreshed *.dat files in root and 2 new files in \OS2\SYSTEM called SYSTEM.DAT and USER.DAT, if these 2 files were not created start REGCONV.EXE.

Note:
There are 6 root keys, the first 2 represent OS2.INI and OS2SYS.INI the other 4 are are the Odin/Windows root keys. In my case Regedit/2 [-> Image] didn't show any key in the Odin root keys, don't know why but it doesn't matter the registry is ok and you can use regedit.exe [-> Image] from windows for tweaking.

1.2. Kernel / OS/2 PM Merged Library

1.2.1 OS/2 Kernel

The ODIN loader requires a kernel symbol file (os2krnl.sym) but FP 40 doesn't include such a file. IBM regulary post new kernel for Warp 4 and Warp 4.5x on testcase but not for Warp 3, anyway download the Warp 3 Kernel w31023uni, the installation is described in the readme file.

1.2.2 OS/2 PM Merged Library

A newer pmmerge.dll than the one from FP40 is required, because it is not compatible with the IBM WGSS image library that was included since ODIN build 2001-01-09, besides you get an SYS2070 with Odin apps:

------------------------------------------------------------
WGSS50->PMMERGE.5478
182
------------------------------------------------------------

I tried the pmmerge.dll from FP 41/42 and 43 but none works, maybe the one from FP 45 works but FP45 is only available on demand and not for free ! At least I took this file from my Warp 4 FP 12 installation this one works. What you loose are the Warp 3 window controls, they are now in Warp 4 style. Download the required Warp 4 pmmerge.dll (en/gr).
You cannot copy this file over the old one because this file is locked, restart the system press Alt-F1 immediately when the OS/2 logo is displayed in the left upper corner to get the 'RECOVERY CHOICES', press C to go to command line, rename the current pmmerge.dll in \OS2\DLL and copy the new file in this place, reboot.
Note: Some users report that this pmmerge.dll replacement will not work on OS/2 Warp 3 SMP (Warp Server Advanced) !

1.3. WarpIN

Odin is packed in a new archiv format (*.wpi as extension) which is handled by the WarpIN installer for a very fast and easy install/uninstall. The latest WarpIN build can be found on the ftp.netlabs.org server, for more information visit the WarpIN homepage. To install just execute warpin*.exe.

1.4 ODIN

Odin is work in progress there are 2 different builds available: weekly (wpi-archive) and daily (zip-archive). For the first time installation use a weekly build named odin32bin-200xxxxx-release.wpi in conjunction with WarpIN, download this file in binary mode !

Note:
Later you can update ODIN with an up to date daily build, just unzip the file over the existing installation but save your customized odin.ini in \odin\systen32 before !

2. Installation

2.1 Before you begin

It is recommend that you have a valid backup from your system and working utility diskettes with chkdsk on it !

WARRANTY
YOUR USE AND BROWSING OF THE SITE IS AT YOUR OWN RISK. THIS PUBLICATION MAY INCLUDE INACCURACIES OR ERRORS. THESE DOCUMENTS, THE INFORMATION CONTAINED THEREIN PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY OR TITLE. EXCEPT AS OTHERWISE PROVIDED BY LAW, NO AUTHOR, COPYRIGHT HOLDER OR LICENSOR SHALL BE LIABLE TO YOU FOR DAMAGES OF ANY KIND, EVEN IF THEY HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

2.2 Install ODIN

Install the odin32bin-2002xxxx-release.wpi using WarpIN by a double click on the *.wpi file or starting WarpIN with the name of the *.wpi file as an argument from command line (WarpIN directory had to be in PATH statement in config.sys).

Install ODIN by hand (WarpIN method recommend):

  • get a daily build (zip-archive) from ftp.netlabs.org
  • create a directory named ODIN in root e.g. c:\odin
  • unzip the daily build in this directory
  • add a device entry for win32k.sys (from \odin\system32) in config.sys, there's also a *.ddp file for 'Device Driver Install' (ddinstal.exe)
  • add the ODIN system directory e.g. c:\odin\system32 to the path and libpath statements in config.sys
  • run odininst.exe from \odin\system32 this will update odin.ini and create some registry keys
  • reboot for changes to take effect (at boot you should see a successfull load of the win32k.sys driver)
  • on demand start the 'Win32k Control Center' (win32kcc.exe) [-> Image] to adjust the win32k.sys settings
  • test your ODIN runtime by installing the 'ODIN Test Application', download it from ftp.netlabs.org

3. Opera

3.1. Requirements

3.1.1 Opera

Want a fast browser which is comfortable and need less ressouces ? Opera is the choise ! Opera for OS/2 is build against the odin libraries, Beta 1 need an installed ODIN runtime, Beta 2 has its own build in ODIN runtime. Since you have no soundcard installed, Opera requires multimedia support (MMOS2).The current version is 5.12 Beta 2, get it from Opera.com. Opera 5.12 Beta 2 requires WarpIN 0.9.14 or higher to install.

3.1.2 TCP/IP Stack

Warp 3 with Internet Access Kit (IAK) installed has a stripped down TCP/IP V2.0 Stack, inetver returns 2.05h. Opera requires a higher version of the stack in order to work, otherwise you get a SYS2070:

------------------------------------------------------------
WSOCK32->SO32DLL.WINSOCKCLEANUPSOCKETS
127
------------------------------------------------------------

You can download MPTS WR08423 (inetver 4.02r) if you have a valid license, install fixpak WR08425 afterwards if you encounter some problems.
MPTS did not check if a TCP/IP stack is already installed, fortunately it is installed in different directories (\IBMCOM,\IBMI18N and \MPTN) than the IAK (\TCPIP). Before you start the installation of MPTS, backup your current config.sys and cleanup all device & run statements with path to the IAK directory (\TCPIP) in config.sys that the old stack did not interfere with the new one.

Note:
This stack has neither DOS support nor any TCP/IP applications (dialer, ftp ...)

Unpack the DSK Archives with diunpack.exe or dskxtrct.exe (get these tools from hobbes) in a temporary directory and start the installation with INSTALL.CMD.
The next step is the configuration, I assume that you have no LAN and no installed nic. Start MPTS from the 'System Setup' folder or command line with mpts.exe, first Configure -> LAN adapters and protocols if you have no nic select No Network Adapter and add the protocol TCP/IP to it, exit. Second go to TCP/IP -> TCP/IP Configuration, activate a LAN interface (lan0) and assign e.g. IP address 192.168.23.1 and Subnet mask 255.255.0.0 to it, however you cannot activate localhost, therefore save settings and exit MPTS edit the file \MPTN\BIN\setup.cmd and enable the lo interface by adding the line ifconfig lo 127.0.0.1 right before lan0. Note: everytime you start MPTS you have to add this line again because MPTS removes it. Reboot the machine and a ping to the new interfaces should work.
You have no TCP/IP applications included in this stack, but the old one from the IAK should work like FTP-PM does [-> Image].

You can also setup the machine behind a router, doing this is easy because this MPTS-TCP/IP package is well integrated: nic and lan setup in one place, not messing with Java notebook and mpts like in Warp 4.5x ;-)
The way to go: install the nic driver and protocols in LAN adapters and protocols, activate the LAN interface (lan0) with Network Interface Parameters, enter the Routing information and the DNS information in the end. Exit MPTS and manually activate localhost, see note above, reboot.

3.2. Install Opera

Install the *.wpi (Beta1) or *.exe (Beta3) by a double click on the file, WarpIN is invoked for the installation. Beta2/3 has some problems with fonts and the enabled OS2Look (window controls). Start the program by a double click on the Opera object within the created Opera folder and it should start and run fine like here [-> Image].

4. Links

In conclusion all listed Links in one place:


€ w3odin.html   main