This article was written by Jon
If you have a comment about the content of this article, please feel free to vent in the OS/2 eZine discussion forums.
Which OS/2 version ?
Warp 4.0 with at least FixPak 6. FixPak 14
Be careful with FixPaks : don't install a FixPak
just because there is one available. FixPaks are meant mainly to correct a number
of specific bugs and in some cases bring additional features to OS/2. If these bugs
don't occur on your system, then try to stick to the following principle :
never fix a working operating system
Make sure you have activated the
support for the Microsoft Joliet file system. The Joliet file system makes it possible
to use files with long names (with a maximum length of 64 characters) on CD's. There
is a norm for this : the so called ISO9660 norm with Rockridge extension. CD's written
according to ISO9660 can be read on OS/2, UNIX, Windows and Mac, but as we all know
the Microsoft motto is :
why a norm if you can do it otherwise?
If you have a CD with Windows software
which hold files with a ~ in their name then the Joliet support is probably not
active. IBM has added Joliet support starting from FixPak 4. You can activate this
support by adding /w in the config.sys to the following line
De resulting line is then
IFS=C:\OS2\BOOT\CDFS.IFS /Q /W
Another way to get full Joliet support
is to access your CDROM using the excellent CD-writer software of RSJ (http://www.rsj.de)
with the following command
cdattach z: -d g:
where g: stands for the drive letter
of your regular CD-ROM and z: for the new drive letter you want to use to access
your CD-ROM to get Joliet support.
You can detach the CD-ROM to eject
the CD by issuing the command
cdattach z: -no_flush
You can also try Scitech Display
Doctor which is available in two versions :
What do you need for ODIN ?
What you need is an Odin build.
There is almost daily a new build
(it is really incredible with what dedication the members of the Odin team accomplish
this in their own free time, don't forget this before sending an angry complaint).
You can download the daily builds
by ftp :
ftp.os2.org in the directory /odin/daily
You can do this via Netscape by entering
the following url
There are three kinds of builds :
How to install ODIN ?
Installation is very straightforward.
It is not necessary to make modifications to your config.sys.
For a further explanation of the
installation we assume that you'll be using the normal release version of Odin.
Step 1 : Make the directory
Create in the root of your boot partition
(this probably C:) a directory with the name ODIN32. If you want it you can also
do this in another partition, but I don't recommend this. This is not because it
will cause problems for ODIN, but because a lot of Windows programs assume that
the system directories are situated on the C partition and therefore try to copy
and configure all kinds of files to the C-partition.
Step 2 : Install the ODIN build
Method 1 : Installation by
Unzip the debug version in the directory
C:\ODIN32. This results in the following directory structure :
Method 2 : Using WarpIN
WarpIN has to be installed before
you can use it to install software packages.
The WarpIN software can be found
To install it you have to the following
This registers WarpIN with os2.ini
and creates a folder that contains the program objects.
You can now install ODIN by just
double clicking on the WarpIN ODIN package. You can easily recognize it because
by installing WarpIN it has now the WarpIN icon attached to it.
Proceed with the installation by
clicking on the Next button.
Now select all the subpackages for
installation by choosing the menu options
The WarpIN installation of ODIN will
modify your config.sys by default. You must uncheck the option Update CONFIG.SYS
to prevent this.
One of the advantages of using WarpIN
is that you can easily de-install all software packages that were installed by it.
This easy de-installation is possible
because WarpIN maintains its own database of installed packages. This database is
stored within the WarpIN directory in the file DATBAS_C.INI. The fact that
everything is stored within the WarpIN directory makes it possible to move this
directory from within the WPS to another place without interfering with the way
Please keep in mind that WarpIN is
still in development (by some dedicated volunteers) and that it still may contain
bugs. If you encounter any bugs you can report them through the egroup warpin-user
Extended installation to be
done after applying Method 1 or Method 2
Now use the command odininst.exe
that can be found in the system32 directory to create an additional directory structure
for better Windows compatibility. Just execute the following commands :
This results in the following directory
Step 3 : make a command file
Now create a file odin.cmd
which contains the following lines
Standard behavior is that while executing
a line the contents of the line will be printed to the screen. The @-sign prevents
this from happening.
The chcp command is used to
specify the codepage. The codepage is responsible for the correct display of characters
such as ë, ï, ... If your country is e.g. Belgium then you can probably
find the following line in your config.sys
850 is one of the standard codepages
for international characters while 437 stands for the codepage according to the
American norm. In this case you can leave out the
In normal circumstances codepage
850 is quite sufficient, but ... there is of course MicroSoft which honors the principle
that if you can change a norm you have the holy duty to do so. Microsoft Windows
uses in most cases codepage 1004. If you notice an incorrect character display while
running Windows/9x programs (e.g. an ë is not displayed as an ë) then
you must make a little modification in your config.sys by substituting the line
Make this change also to the file
odin.cmd by changing the line
Remark : if you receive E-mail that
has been send by a Windows minded colleague it can happen that in OS/2 special characters
like ë, ï, ... are displayed incorrectly. This can be easily solved in
most cases by making proper use of codepages. Make sure you have the following line
in your config.sys
If you use e.g. PMMail as E-mail
client, create then a .cmd file e.g. startpmmail.cmd with the following contents
With this line the environment variable
PATH is adjusted for as long as the file odin.cmd is executed. This
way we can temporarily change the value of PATH without having to do this
in the config.sys.
With this line the environment variable
LIBPATH is adjusted. Normally LIBPATH contains a list of directories
that contain DLL-files. LIBPATH is not a normal environment variable i.e.
it can not be changed as can be done with normal variables. IBM has therefore in
one of their fixpacks added two extra environment variables :
- BEGINLIBPATH : this allows
the adding of DLL-directories to the beginning of the list specified in LIBPATH
- ENDLIBPATH : this allows
the adding of DLL-directories to the end of the list specified in LIBPATH
@start /n PE %1 %2 %3
start /n allows you to start
a program without starting first an extra OS/2 cmd.exe instance in the background.
PE is a program that adapts
the Win32 executable and DLL's to OS/2.
%1 %2 %3 allows us to pass
3 arguments to the PE executable.
Step 4 : some precautions
In normal circumstances Odin can
not damage your OS/2 system, but as we all know there is also something like unreliable
Windows programs. Therefore following precautions.
How to install a Windows/9x program
First some considerations.
You can only run 32-bit Windows programs
with ODIN. Microsoft was however so friendly to use a partly 16-bit installation
program for some of its 32-bits software packages. Therefore these programs can
not be directly installed through ODIN. For most non-Microsoft programs this is
luckily not the case. Should you encounter such an ill-designed installation procedure
then there is a little bit more work to get things working.
Should you encounter such an ill-designed
installation procedure then there is a little bit more work to get things working.
There are two possible roads you can take : The first road you can take is trying
to install the software by replacing the original SETUP.EXE and _ISDEL.EXE on the
installation CD or floppy by its 32-bit counterparts that can be found in win32inst.zip.
win32inst.zip can be downloaded from hobbes (http://hobbes.nmsu.edu). Copy the CD
with the Windows software to a directory on your hard disc and replace SETUP.EXE
and _ISDEL.EXE. Now write everything back to a CD-RW. The reason I do this is that
in some cases the installation software makes links to the CDROM and I'm a little
bit too lazy to correct these links within the configuration files. Of course if
you want you can also try to install the software by starting SETUP.EXE in the directory
on your hard disc. The second road is for the more technical persons among you :
If the above considerations don't
count for your Windows program you can just install it with
c:\odin32\odin install.exe or
c:\odin32\odin setup.exe or no matter
what other executable you have to start for installation
Use ODIN programs the same way
as Seamless Windows programs
If you have installed a Windows program
through Odin and it is working you can very easily start this by using an icon.
Go to the folder Programs
and create a new program object by dragging the 'new program'-template to
the desired folder, e.g. ODIN Programs.
At path and filename you enter
the following line
At parameters you enter the
path and the name of the Windows executable e.g.
At working directory you enter
the installation directory of the Windows program e.g.
Now switch to the tab Icon
and enter a name for the new created program object and assign an icon to it.
Some examples of Windows programs
that work through ODIN
The Van Dale dictionaries for Windows95
(very stable, rarely crashes)
Van Dale dictionaries
More information can be found on
the following web sites :
- official ODIN web site :
- non official ODIN web site
- list of working applications :
and through the following mailinglists
More information about OS/2 updates
in general can found on :
- WarpDoctor : http://www.warpdoctor.org
- IBM Fixpak Database : http://service5.boulder.ibm.com/pspfixpk.nsf/
- OS/2 TCP/IP Updates list
- Summary of LAN component versions
and fix levels under OS/2 Warp :
- IBM OS/2 Warp Updates Summary
If you want to help with development
You can checkout the sources via
CVs 1.1.0 (CVs is an extension on top of RCS to allow multiple users to do version
The CVs 1.1.0 software can be downloaded
from hobbes (http://hobbes.nmsu.edu).
To run CVs you need to have the EMX
runtime installed. This can also be downloaded from hobbes.
Make sure to add the following lines
in your config.sys
In this example D:\Odin_source is
the directory into which the sources will be placed. You can substitute it with
whatever directory you like but make sure that this is an existing directory.
If you use XFree86/2 this environment
variable is normally already present in your config.sys.
Now execute the follow command to
check out the sources
CVs -z3 co .
To update your tree regularly, go
to the odin32 directory and execute
CVs -z3 update -dP
And now it is up to you. Give ODIN
Hereby I wish to thank Achim Hasenmueller
from Innotek for proofreading this document and supplying me with valuable extra
information that I wasn't aware about.