Change History (10)

probably pe or pec isn't a good idea, as right now it throws a popup when is doesn't find the app. and the user has to hit the ok button.
eventually a small "odin.exe" with only "--version" parameter would be better.

it will try to locate kernel32.dll in [BEGIN/END]LIBPATH and print its version information to the standard output on success, e.g.:

0.8.2

Note that since the 0.8.1/0.8.2 builds of Odin lack the bldlevel information, we will have to release a new version, 0.8.3, where this is fixed (so that a new, 0.8.x series of Odin could be successfully detected with bldlevelx).

Do you mean to enhance it so that it can also resolve the full path when things like OS2KRNL and DANIS506.ADD are given? Well, this is doable. I.e. for OS2KRNL and friends we can simply assume BootDrive:\, for .ADD files -- BootDrive:\OS2\BOOT and so on. If this is really necessary and you provide me with the extensions you are interested in, I will do that.

If you mean requesting the information for files other than DLL and EXE, this works of course, provided that you specify a full file name (e.g. C:\OS2KRNL).

BTW, if you want to use this in a WPI, you can copy-paste the GetBldLevel? procedure and use it in a <REXX> function in .WIS for extracting the necessary information instead of requiring to have bldlevelx.cmd already installed.