|
Site Index - Feedback - Impressum |
| |||||||||
|
![[Forum]](../../../images.os2.org/de/forum.gif){kind=small} |
|
![[Forum]](../../../images.os2.org/de/forum2.gif){kind=small} |
| ( Archiv ) | ( Neues Thema ) |
| 31.12.2001 |
| ODIN: vereinfachte Kommando-Prozeduren für ODIN-Aufrufe (von: GA, 14:27:14) | ^ |
| Darryl Sperber(sperber@airmail.net) hat Prozeduren erstellt, um die Nutzung von ODIN-Anwendungen zu vereinfachen:
This is a very convenient way to run ODIN programs completely independent of OS/2 DLLs, etc. New ODIN releases can be installed "on the fly" without requiring re-boot. Etc., etc. Quoting that article from a few weeks back: ------------------------------------------------------------------------ Do NOT put PE in a directory on the PATH. Instead, invoke an "ODIN.CMD" before running PE on a Win32 program, to set the values of PATH and LIBPATH within that command-prompt window. For example, I have ODIN.CMD set as follows: @echo off set path=j:odinsystem32;%path% set beginlibpath=j:odinsystem32; set WIN32LOG_ENBABLED= Similarly, I have an ODINDBG.CMD (when debugging and wanting to produce a log trace) as follows: @echo off set path=j:odinsystem32;%path% set beginlibpath=j:odinsystem32; SET WIN32LOG_ENABLED=1 I personally don't use the WarpIN method for installation. I download the ZIP file (daily release or debug) more frequently than once a week, unzip it into my ODIN directory (overlaying the existing files), and then run j:ODINSYSTEM32ODININST.EXE to complete the installation. Then I modify j:ODINSYSTEM32ODIN.INI manually in order to insert my additions: {WinVersion] Version=Win98 [WINMM] DirectAudio=0 DefVolume=30 I invoke Win32 programs in either of two ways. The first is used when first trying a program for the first time or when needing to generate a debug trace log. The second is used when I move the program to "production", including setting up a program object for an invoking CMD file and associating the proper Win32 program icon (extracted if necessary from the Win32 EXE file while under Win98 using the Jones Icon Extractor, and converting to an OS/2 icon using PMVIEW). (1) In a command prompt window: odin or odindbg change to the proper program directory PE program_name (2) Double-click program object, e.g. AGENT.CMD, where the command is: @echo off call odin l: cd Agent pe agent If you want, the JonesSoft icon extractor for Win98 can be found (for free) at: http://members.ozemail.com.au/~jaesenj/software/software.html [ Leser: 144 ] |
| |||
| Mit * markierte Felder müssen ausgefüllt werden ! |
| ( Zeige alle Einträge ) | ( Zur Startübersicht ) |
|
| GA | 144 | 31.12.2001 | 14:27 |
|
