Text 1966, 111 rader
Skriven 2011-11-25 16:01:20 av Dariusz Piatkowski
Ärende: Re: Fixpak file mapping - how to get a good DEBUG/TRACE/DUMP ?
======================================================================
p74d14a1ffbc4b03fea480e4027ed128c884c16f093d5762c288673224ed373c0.newsdawg.com
comp.os.os2.setup.misc:645
From: "Dariusz Piatkowski" <dariusz@_NO-SPAM_mnsi.net>

Hi Lars!

On Thu, 24 Nov 2011 16:33:22 UTC, "Lars Erdmann" <lars.erdmann@arcor.de> wrote:

> The .TDF and .TFF always go into directory \os2\system\trace.
> On the other hand and as you have observed they will for some reason or the 
> other also show up in other directories (as duplicates I suppose).
> 
> The .TDF, .TFF are a black hole. You will need to make sure they match
> the corresponding DLLs (or OS2KRNL) for example. 


Yes sir...I completely understand what you are describing above and that was my

impression of how this was designed. This is why as I switched over to SMP 
execution and encountered my problems I wanted to make sure that the FP6 level 
of my software was correctly setup to debug at the SMP level as well. Glad to 
hear this confirmation though.


> For one reason or the other, an FP or CP install will not necessarily 
> install the .TDF,.TFF files when it updates the DLLs. You might want to
consider finding these files > in the CP,unpacking them by hand and moving them
to the \os2\system\trace directory. You might > need to distinguish between W4,
SMP and UNI kernel for those .TDFs that set dynamic tracepoints > in OS2KRNL.
Even worse, some updates like for example (I think) JFS might come with 
> updated .TDF files so you will have to make sure you also catch these.
> 
> What is CP2 with FP6 ? And is there no newer CP for you ?
> You should consider upgrading to eCS. That will give you CP4 and CP5.
> There even is a CP6 but it is unofficial, you would be on your own ...


As Steve Wendt pointed out in another post, CP2 is Convenience Pack2 and FP6 is

the latest, although unofficial fixpack available for this level.

My thinking behind this process is exactly as you pointed out. I am physically 
re-doing the FP6 install, only picking up the SMP specific stuff.

The SRV_PROD.OS2 file contained in each FP 'disk' sub-directory contains the 
mapping of the actual compressed files to where they need to go, along many 
other things, such as version checks and so on. The script to decode this was 
provided to me by Chuck McKinnis a few months back and really allows one to 
understand what the heck the FP is trying to do.

Here is an example of the OS2.2 subdirectory (small sub-set of the report):

=== START ===

Fixpak name: XR_C006
Product location on CSD: G:\TEST\FP6\fix\OS2.2\


..\..\OS2\INSTALL\UNI   	Stub File:  @UNIDIR
..\..\OS2\INSTALL\SMP   	Stub File:  @SMPDIR
..\..\OS2\PDPSI\PMDF\WARP45_U   Stub File:  @WARP45U
..\..\OS2\PDPSI\PMDF\WARP45_S   Stub File:  @WARP45S


Filename     Companion    Name On CSD  D# Date     Time  Size    Checksum 
Notes
------------ ------------ ------------ -- -------- ----- ------- --------  
--------------...
DF_DEB.EXE   @WARP45S     DF_DEB.SM_   12 10/17/06 09:19  144355 860D333F 
Packed, Add, Ver Check IBM:14.105   \OS2\PDPSI\PMDF\WARP45_S
DF_DEB.EXE   @WARP45U     DF_DEB.UN_   13 10/17/06 09:03  136237 04DC1503 
Packed, Add, Ver Check IBM:14.105   \OS2\PDPSI\PMDF\WARP45_U
DF_RET.EXE   @WARP45S     DF_RET.SM_   11 10/17/06 08:45  144323 89D6EE31 
Packed, Add, Ver Check IBM:14.105   \OS2\PDPSI\PMDF\WARP45_S
DF_RET.EXE   @WARP45U     DF_RET.UN_   12 10/17/06 08:34  136205 C3BE3148 
Packed, Add, Ver Check IBM:14.105   \OS2\PDPSI\PMDF\WARP45_U
DOSCALL1.DLL @SMPDIR      DOSCAL1S.DL_ 11 10/17/06 08:44  144677 B0478942 
Packed, Same Trg                    \OS2\INSTALL\SMP
DOSCALL1.DLL @UNIDIR      DOSCAL1U.DL_ 12 10/17/06 08:33  137659 5A078A43 
Packed, Same Trg                    \OS2\INSTALL\UNI
DOSCALL1.SYM @WARP45S     DOSCAL1S.SY_ 13 10/17/06 08:44   43828 499AE7EB 
Packed, Add                         \OS2\PDPSI\PMDF\WARP45_S
DOSCALL1.SYM @WARP45U     DOSCAL1U.SY_ 13 10/17/06 08:33   43476 A0EBEFD9 
Packed, Add                         \OS2\PDPSI\PMDF\WARP45_U
DOSCALL1.TDF @SMPDIR      DOSCALL1.SD_ 13 10/17/06 08:44    5534 A2F6C73F 
Packed, Add                         \OS2\INSTALL\SMP
DOSCALL1.TDF @UNIDIR      DOSCALL1.UD_ 13 10/17/06 08:33    5534 6FBFC3B9 
Packed, Add                         \OS2\INSTALL\UNI

=== STOP ===

The @UNIDIR placeholder is then decoded to an appropriate disk location and 
shows up in the 'Companion' column of the report. This is how I can tell what 
compressed file belongs to where and in particular, which level of OS2. SMP vs 
UNI is a great example as you can see above. I'm not quite sure what the 
@WARP45U and @WARP45S are, but as best as I can tell they may reference the UNI

and SMP enabled version of Warp4.5, which would effectively be an installation 
like mine: CP2 on top of the regular Warp4 (but this is just a hypothesis).

So...at this point in time, I have ucompressed all the corresponding files and 
have them sitting in their destination locations, this has been done for SMP 
stuff ONLY. The curiosity arose becase I have no idea what the \OS2\INSTALL\SMP

location is used by, and as you pointed out, I have always looked at the 
\OS2\SYSTEM\TRACE as the final destination for the TDF/TFF files.

Thanks!

--- Internet Rex 2.31
 * Origin: NewsGuy - Unlimited Usenet $19.95 (1:261/20.999)