From: "Chuck McKinnis"    
      
   On Sun, 24 Jul 2011 15:50:48 UTC, "Dariusz Piatkowski"    
    wrote:   
      
   > Folks,   
   >    
   > Trying to understand the exact mapping of the files in the un-official   
   MCP/ACP    
   > FP6. Looking at the individual OS2.1, OS2.2, OS2.3, etc...directories there   
   is a   
   > file present called SRV_PROD.OS2. This appears to be the 'map' for the   
   fixpack    
   > tool to know which file goes where (or so my uneducated OS2 thinking goes at   
   the   
   > moment...lol).   
   >    
   > Basically, sample contents follow (OS2.4 directory of FP6) :   
   >    
   > === START ===   
   >    
   > SYSLEVEL    
       
   > Çâ / E    
   > XR_C006_XR_4501_Convenience Package - OS/2 Warp Server for e-business    
   Æ    
   > 5639A5550 \   
   > E XR_C006_XR_4502_Convenience Package - OS/2 Warp Server for   
   e-business    
   > Æ 5639A5550 \   
   > E XR_C006_XR_4503_Convenience Package - OS/2 Warp Server for   
   e-business    
   > Æ 5639A5550 \   
   > ..\..\ ..\..\OS2\dll DF_DEB.EXE @PMDFDIR DF_DEB.EX_ 3 Q5oJ   
       
   > IBM:14.105 u3   
   >    
       
   > DF_RET.EXE @PMDFDIR    
   > DF_RET.EX_ 3 Q5úE IBM:14.105 1   
       
      
      
      
       
   > DOSCALL1.DLL @OS2DLL DOSCALL1.DL_ %5 Q5ìE !   
       
   > BëG   
       
   > DOSCALL1.TDF   
   @TRCDIR    
   > DOSCALL1.TD_ Q5ÄE ?°   
       
      
      
      
       
   > HARDERR.EXE HARDERR.EX_ ): Q5ÉE    
   > IBM:14.105 1c    
   >    
   > === STOP ===   
   >    
   > It's a somewhat binary file which obviously has some type of a record layout    
   > that needs to be deciphered.    
   >    
   > Is there a tool out there already that does this? If not, does anyone know   
   the    
   > record layout?   
   >    
   > Just to help out a tad, the file is somewhat self explanatory, you can tell   
   what   
   > the 'product' the particular files need to be applied to given the 1st   
   record    
   > (or more if multiple levels are applicable). Then you see the listing of   
   each    
   > individual file, along with the proper destination path. I would like to   
   have a    
   > utility which can decipher this for me automatically. The fixpack tool   
   already    
   > does this obviously, but how can I get at this info in a human readable form    
   > first?   
   >    
   > Thanks as always!!!   
      
   Send me an email.   
      
   --    
   Chuck McKinnis   
      
      
   --- Internet Rex 2.31   
    * Origin: The gateway at Omicron Theta (1:261/20.999)   
|