Hi
Does anybody knows if there is a documentation (any kind) on how OS/2 and eComStation directory structure should be?
For example.
- All the Programs goes on - x:\Programs\...
- All the DLL goes on - X:\OS2\DLL
- The installed drivers..
- Bitmaps ?
- Graphics ?
- ..etc.
Is there any formal, un-official or suggestion about it ?
DevCon:
http://ecomstation.ru/projects/developer/?action=eFDS
This is interesting reading guys; re: the inquiry from "miturbide" and the quick, precise and professional response from "EugeneGorbunoff" ;); all-in-all it is believed that interaction like these should auger well for the OS/2 Gene Pool (Watering Well). Can one's curiosity be further quenched by the revelation of a current listing of the "best" are "brightest"(within IBM and elsewhere around the world) and project development activities surrounding OS/2. ;)
Quote from: miturbide on 2008.04.03, 18:41:23
Hi
Does anybody knows if there is a documentation (any kind) on how OS/2 and eComStation directory structure should be?
For example.
- All the Programs goes on - x:\Programs\...
- All the DLL goes on - X:\OS2\DLL
- The installed drivers..
- Bitmaps ?
- Graphics ?
- ..etc.
Is there any formal, un-official or suggestion about it ?
I see you have already been given the eFDS link but no-one has warned you of the potential for "dll hell"...
eCS systems have 2 dll directories
\ecs\dll
and
\os2\dll
The config.sys usually has \ecs\dll before \os2\dll in the LibPath (config.sys).
To avoid the occasional unexpected happening with eg libc*.dll files you need to check what is installed in each of those directories and remove duplicate copies of dll files.
Regards
Pete