Author Topic: OS/2 Components / Architecture - Indentifying OS/2 Files  (Read 60480 times)

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4744
  • Karma: +41/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #45 on: June 24, 2015, 10:34:56 pm »
I'm now trying to identify this DLLs.

NAMEDSP.DLL
NAMEFW.DLL
NAMEREXX.DLL

One says it is the "Name Framework", but I never hear of that on OS/2. Or should I count them as part of Unicode? This three reference the  LIBUNI.DLL and UCONV.DLL files.

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4744
  • Karma: +41/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #46 on: July 11, 2015, 12:35:04 am »
Hi.

I got a tip about this files.

Even that I'm not sure about it, I prefer to do something wrong and be corrected on the future, instead of not doing anything. And the good things is that what a Wiki is good for.

So, I'm putting the NAME*.DLL files on a component called  WPOS_Name_Framework.  Maybe I'm very wrong, but someone can correct it on the future.

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Joop

  • Hero Member
  • *****
  • Posts: 633
  • Karma: +5/-0
    • View Profile
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #47 on: July 11, 2015, 12:42:37 am »
I'm now trying to identify this DLLs.

NAMEDSP.DLL
NAMEFW.DLL
NAMEREXX.DLL

One says it is the "Name Framework", but I never hear of that on OS/2. Or should I count them as part of Unicode? This three reference the  LIBUNI.DLL and UCONV.DLL files.

Regards
Has probably to do with the tree structure. You can find a few things about name*.* in the help.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4744
  • Karma: +41/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #48 on: July 12, 2015, 02:20:57 pm »

Has probably to do with the tree structure. You can find a few things about name*.* in the help.

Hi Joop, can you please point me to which help file has information about this files?

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Joop

  • Hero Member
  • *****
  • Posts: 633
  • Karma: +5/-0
    • View Profile
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #49 on: July 12, 2015, 03:04:40 pm »

Has probably to do with the tree structure. You can find a few things about name*.* in the help.

Hi Joop, can you please point me to which help file has information about this files?

Regards

Seems to be the file CMDREF.INF in the directory "\OS2\BOOK" on my system. Don't know if this is standard, the setup date of my system is 03-08-2005 and I can't remember what I did then. But it must be not difficult to track it down in your OS/2 directory.

Regards

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4744
  • Karma: +41/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #50 on: July 13, 2015, 10:30:35 pm »
Hi Joop.

I checked CMDREF.INF. The only reference I was available to find about the NANE*.* files (that I'm trying to assign to a component) is NAMEPIPES.DLL which only says it is required if you want to run some FTPREMOTE from a diskette.

But I will move on to Control Program and get back to those DLLs if someone can find a better explanation.

Regafrds
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Joop

  • Hero Member
  • *****
  • Posts: 633
  • Karma: +5/-0
    • View Profile
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #51 on: July 14, 2015, 07:19:13 pm »
Hi Joop.

I checked CMDREF.INF. The only reference I was available to find about the NANE*.* files (that I'm trying to assign to a component) is NAMEPIPES.DLL which only says it is required if you want to run some FTPREMOTE from a diskette.

But I will move on to Control Program and get back to those DLLs if someone can find a better explanation.

Regafrds
Huhh? And what about NAMEADD, NAMEEXT, NAMECOPY, NAMEDEL, NAMEMOD and NAMEMOVE?

Regards

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4744
  • Karma: +41/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #52 on: July 14, 2015, 10:05:04 pm »
Hi Joop.

My goal (at this moment) is trying to assign to which OS/2 component does the NAMEDSP.DLL, NAMEFW.DLL and NAMEREXX.DLL files belongs too.  I currently assigned it to a proposed component which I'm not sure on the Components page.  (WPOS Name Framework)

About the CMDREF.INF (The Warp Server Commands and Utilities) has some referenced to name* functions, but from what I'm checking on these NAME*.DLL files I can not find a relation between these name* functions you are telling me and this files. So I guess are not related.

But I may be complete wrong, so anybody is free to correct me.

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4744
  • Karma: +41/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #53 on: July 15, 2015, 04:58:21 pm »
Hi

Now I'm trying to figure it out to which OS/2 component should I assign this files:

- ATMDATA.DAT
- DOSRFICO.DLL
- FILEVER.DLL
- FKA.DLL
- IMP.DLL
- NWIAPI.DLL
- SYSFONT.DLL

Suggestions are welcome.

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4744
  • Karma: +41/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #54 on: July 21, 2015, 07:12:03 pm »
I'm not sure what IMP.DLL does. I can not find information about the functions that it has inside.

For the moment I noticed that WPCONFIG.DLL and PMWP.DLL uses it.

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Andreas Schnellbacher

  • Hero Member
  • *****
  • Posts: 827
  • Karma: +14/-0
    • View Profile
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #55 on: July 21, 2015, 08:10:15 pm »
Exehdr should help here a bit:

Code: [Select]
epm: G:\DEV\TOOLKT45\BIN > G:\DEV\TOOLKT45\BIN\EXEHDR.EXE /NO D:\OS2\DLL\IMP.DLL
Library:                        IMP
Description:                    Input Method Profiler

Module type:                    Dynamic link library
Number of memory pages:         00000004 (4)
Initial CS:EIP:                 object 0 offset 00000000
Initial SS:ESP:                 object 0 offset 00000000
Automatic data object:          4

 no. virtual  virtual  map      map      flags
     address   size    index    size
0001 1baa0000 0000076c 00000001 00000001 EXECUTABLE, READABLE, DISCARDABLE,
                                         16:16 ALIAS
0002 1bab0000 000001d0 00000002 00000001 EXECUTABLE, READABLE, 32-bit
0003 1bac0000 00000027 00000003 00000001 EXECUTABLE, READABLE, 16:16 ALIAS
0004 13cc0000 000000b4 00000004 00000001 READABLE, WRITEABLE, SHARED,
                                         16:16 ALIAS
0005 13cd0000 00000038 00000005 00000000 READABLE, WRITEABLE, SHARED,
                                         16:16 ALIAS


Exports:
 ord  obj   offset    name
   1    1  00000000  IMPSETAIMPROFILE exported, shared data
   2    2  00000000  IMP32SetAIMProfile exported, shared data
   3    1  00000544  IMPRESETAIMPROFILE exported, shared data
   4    1  000004f8  IMPQUERYAIMPROFILE exported, shared data
   5    2  000000b4  IMP32ResetAIMProfile exported, shared data
   6    2  000000fa  IMP32QueryAIMProfile exported, shared data

"Input Method" is for DBCS languages.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4744
  • Karma: +41/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #56 on: July 21, 2015, 10:19:38 pm »
Thanks Andreas.

I completed the  information on the wiki. I'm not sure to which "Component" of OS/2 assign this file yet.

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4744
  • Karma: +41/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #57 on: July 21, 2015, 11:09:10 pm »
I don't know I will put IMP.DLL into Bidirectional Language API for the moment.

Regards
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4744
  • Karma: +41/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #58 on: July 30, 2015, 04:12:29 pm »
Hi.

I'm still trying to figure it out on which component to fit this last files:

- ATMDATA.DAT
- DOSRFICO.DLL (I'm putting this on the "Install Library"
- FILEVER.DLL
- FKA.DLL
- NWIAPI.DLL
- SYSFONT.DLL

Any ideas about "ATMDATA.DAT"? It seems realted to fonts, but which component/DLL calls it or use it.  It is related to Adobe Type Manager or it is no ? Any idea to find it there is any relation with PMATM.DLL?
« Last Edit: July 30, 2015, 04:25:35 pm by Martin Iturbide »
Martin Iturbide
OS2World NewsMaster
... just share the dream.

Wim Brul

  • Sr. Member
  • ****
  • Posts: 295
  • Karma: +25/-0
    • View Profile
    • Wim's home page
Re: OS/2 Components / Architecture - Indentifying OS/2 Files
« Reply #59 on: July 31, 2015, 04:13:15 pm »
Hi Martin, this is what I found:

ATMDATA.DAT - This file contains a list of aliases and filenames separated by a '>' for Japanese ATM fonts. It has references for User Defined Characters (UDC) of the HeiseiKakuGothic and HeiseiMincho fonts. The IBM supplied CIDFont names are IBJHKGW5.CID for Japanese Heisei Kaku Gothic (JHKG), and IBJHMNW3.CID for Japanese Heisei Mincho (JHMN). See g5445854.pdf for more information. It seems to me that ATMDATA.DAT is a leftover from using Type Transformer.

DOSRFICO.DLL - DosRefreshIcons dll for System Installation. Used by RSPINST.EXE - OS/2 V3 Response File Installation.

FKA.DLL - Function Key Area DLL - Used by LXLITE.EXE and it seems that PMMERGE.DLL loads it. EPMKWDS.C knows its ordinal functions such as ORD_FKAINIT. These are defined a.o. in the BSEORD.H of the toolkit.

FILEVER.DLL - OS/2 File Version Check. INSTALL.DLL and NPFI.DLL are using it. CHECKASD.EXE - Check ASD Features Utility is using it too.

NWAPI.DLL - Network generic API's. NWDDE.EXE is using it.

SYSFONT.DLL - Used by MIRRORS.DLL and contains SYSFONT #FONTRES CONTINUOUSSCALING : Sysfont, whatever that is, and OS/2 FONT bitmaps of the Mirrors-EGA, Mirrors-OEM-EGA, Mirrors-VGA, Mirrors-OEM-VGA, Mirrors-XGA, Mirrors-OEM-XGA fonts.

Wim.