Experiment: Moving the OS/2 Directory Structure

From OS2World.Com Wiki
Revision as of 18:41, 23 July 2014 by Martini (talk | contribs) (→‎TCPIP)
Jump to navigation Jump to search

Warning: This is an experiment. OS/2 and eComStation may became unstable.

This experiment is for the people that will like to move some directories that are installed by default on the root drive.

OS/2 and eComStation has the following directories installed on the root:

So let's see what happens:

IBMGSK

IBMGSK is a set of libraries for RSA encription for some programs. It is hard to know if it is ok to move them since (as far as I know) they are only usefull for some programns like IBM Personal Communicator, IBM HTTP Server and maybe IBM DB2 on OS/2.

So moving it for example to \OS2\SYSTEM does not gives problem in this experiment.

Config.sys Changes:

  • LIBPATH=C:\OS2\SYSTEM\IBMGSK50\LIB;C:\OS2\SYSTEM\IBMGSK40\LIB;C:\OS2\SYSTEM\IBMGSK\LIB;
  • PATH=C:\OS2\SYSTEM\IBMGSK50\BIN;C:\OS2\SYSTEM\IBMGSK40\BIN;C:\OS2\SYSTEM\IBMGSK\BIN;
  • SET IKEYMAN40_HOME=C:\OS2\SYSTEM\IBMGSK40
  • SET IKEYMAN50_HOME=C:\OS2\SYSTEM\IBMGSK50
  • SET IKEYMAN_HOME=C:\OS2\SYSTEM\IBMGSK

Testing:

I have not tested if this component is working fine. It surely does not break OS/2 by moving it, but I can not be sure of the software that uses this libraries works.

DMISL

This directory which seems to be the IBM OS/2 DMTF Service Layer‎ and used by the "Problem Determination Tools", looks that there is not problematic to move. But I'm not a "Problem Determination Tools" expert.

It seems that C:\OS2\DMISL.EXE that keep running in the background is locking the "SLDB.DMI" file, so you can not move this one. And if you kill the DMISL.EXE process, it will load again.

The SLDB.DMI file can not be moved, but it will get created automatically on the next boot according the DMIPATH path location (config.sys). So on the next removed you can erase the almost empty C:\DMISL folder.

So moving it for example to \OS2\SYSTEM does not gives problem in this experiment.

Config.sys Changes:

  • SET DMIPATH=C:OS2\SYSTEM\DMISL\BIN


Testing:

I don't use the OS/2's "Problem Determination Tools", so I'm not sure about if it is working 100%. The SLDB.DMI got automatically created in the new location after loading.

LANGUAGE

The Language Directory‎ is required for UNICODE.SYS to work right, and UNICODE.SYS is required for JFS.IFS. The config.sys statement is by default "SET ULSPATH=C:\LANGUAGE"

This directory is giving me some errors if I move it.

When "UNICODE.SYS" loads in the boot procedure it gives some errors that can not found the files if you move them.

IBMLAN

This is part of the IBM LAN Server, which is the thing that helps you connect to other OS/2 servers and clients to share files and services.

You can not move the IBMLAN folder if the following services are running:

  • PEER.EXE
  • VNRMINIT.EXE
  • WKSTA.EXE
  • WKSTAHLP.EXE
  • MSRV.EXE

So, I moved some via the WPS, and I also moved the file (net.acc) booting eCS from command line mode.


Config.sys Changes

  • DEVICE=C:\OS2\SYSTEM\IBMLAN\NETPROG\RDRHELP.200
  • IFS=C:\OS2\SYSTEM\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\OS2\SYSTEM\IBMLAN /N
  • DEVICE=C:\OS2\SYSTEM\IBMLAN\NETPROG\VNETAPI.OS2
  • LIBPATH=C:\OS2\SYSTEM\IBMLAN\NETLIB;
  • PATH=C:\OS2\SYSTEM\IBMLAN\NETPROG;
  • DPATH=C:\OS2\SYSTEM\IBMLAN\NETPROG;C:\OS2\SYSTEM\IBMLAN;
  • HELP=C:\OS2\SYSTEM\IBMLAN\NETPROG;
  • BOOKSHELF=C:\OS2\SYSTEM\IBMLAN\NETPROG;
  • SET NWDBPATH=C:\OS2\SYSTEM\IBMLAN\NETPROG
  • SET DLSINI=C:\OS2\SYSTEM\IBMLAN\NETPROG\NETGUI.INI
  • RUN=C:\OS2\SYSTEM\IBMLAN\NETPROG\LSDAEMON.EXE
  • RUN=C:\OS2\SYSTEM\IBMLAN\NETPROG\VNRMINIT.EXE

Startup

On the startup procedure on OS/2 it runs

  • C:\OS2\SYSTEM\IBMLAN\NETPROG\NETSTCMD.CMD

with the paramenter "START PEER".

WPS

It is a good thing that the OS/2-eCS Desktop is intelligent and point the icons on the desktop to right places.

Testing

Sadly, I'm no expert on this component, and I don't have several OS/2 machines sharing files with this functionality.

I made some basic "NET USE" commands, logged in without problems to the local machine.

NET START also worked:

[C:\]net start
Checking IP configuration ...
These services are started:
REQUESTER                MESSENGER                PEER
The command completed successfully.

IBMCOM

The IBMCOM directory is very important since it has all the network adapters device drivers, protocols device drivers (like Netbios, TCPIP) and the software to install them and configure them on the system.

I got some problems to move the folder while OS/2 was running. I copied the content to \OS2\SYSTEM\ and changed the Config.sys. The OS/2 and network services runned fine, but I broke the GUI application.

C:\ibmcom\PROTOCOL\NBTCP.EXE is blocked but it can be copied to the new location.

Config.sys Changes

  • DEVICE=C:\OS2\SYSTEM\IBMCOM\PROTOCOL\LANPDD.OS2
  • DEVICE=C:\OS2\SYSTEM\IBMCOM\PROTOCOL\LANVDD.OS2
  • DEVICE=C:\OS2\SYSTEM\IBMCOM\LANMSGDD.OS2 /I:C:\OS2\SYSTEM\IBMCOM /S
  • DEVICE=C:\OS2\SYSTEM\IBMCOM\PROTMAN.OS2 /I:C:\OS2\SYSTEM\IBMCOM
  • DEVICE=C:\OS2\SYSTEM\IBMCOM\PROTOCOL\TCPBEUI.OS2
  • DEVICE=C:\OS2\SYSTEM\IBMCOM\PROTOCOL\NETBIOS.OS2
  • DEVICE=C:\OS2\SYSTEM\IBMCOM\MACS\PCNTND.OS2
  • LIBPATH=C:\OS2\SYSTEM\IBMCOM\DLL;
  • PATH=C:\OS2\SYSTEM\IBMCOM;
  • DPATH=C:\OS2\SYSTEM\IBMCOM;C:\OS2\SYSTEM\IBMCOM\MACS;
  • CALL=C:\OS2\SYSTEM\IBMCOM\PROTOCOL\NETBIND.EXE
  • RUN=C:\OS2\SYSTEM\IBMCOM\LANMSGEX.EXE
  • RUN=C:\OS2\SYSTEM\IBMCOM\PROTOCOL\NBTCP.EXE

NIF Files

I'm checking if in case of installing new network adapters and protocols, it will be required to change the .nif file point to the new path of the network adapter and protocols.

Testing

The MAC and protocols runs fine with Config.sys, but the GUI tools got broken.

MUGLIB

MUGLIB from what I can see is the tools and libraries required to log on to a network machine with IBMLAN manager.

It seems that there is no major problem on moving it.

The following files are locked after boot:

  • muglrqst.exe
  • DLL\mailslot.dll
  • DLL\mug.dll
  • DLL\netapi.dll
  • DLL\mnetapi32.dll

Config.sys Changes.

  • LIBPATH=C:\OS2\SYSTEM\MUGLIB\DLL;
  • PATH=C:\OS2\SYSTEM\MUGLIB;
  • DPATH=C:\OS2\SYSTEM\MUGLIB;

Testing

After moving it a run a "NET USE" that loaded the login window and I was able to login to the same computer.


MPTN

MPTN is a important part of hte TCP/IP and networking feature of OS/2-eCS. It contains several protocols drivers and network executable programs (link ping.exe)

I was able to move it without any issue.

The followin process are running after boot:

  • dhcpcd.exe

Some locked files when trying to move it:

  • \BIN\cntrl.exe
  • \DLL\so32dll.dll
  • \DLL\tcp32.dll
  • \DLL\tcpip32.dd
  • \DLL\tcpmri.dll

Config.sys Changes.

  • DEVICE=C:\OS2\SYSTEM\MPTN\PROTOCOL\SOCKETSK.SYS
  • DEVICE=C:\OS2\SYSTEM\MPTN\PROTOCOL\AFOS2.SYS
  • DEVICE=C:\OS2\SYSTEM\MPTN\PROTOCOL\AFINETK.SYS
  • REM DEVICE=C:\OS2\SYSTEM\MPTN\BIN\VDOSTCP.VDD
  • DEVICE=C:\OS2\SYSTEM\MPTN\PROTOCOL\FWIP.SYS
  • LIBPATH=C:\OS2\SYSTEM\MPTN\DLL;
  • PATH=C:\OS2\SYSTEM\MPTN\BIN;
  • DPATH=C:\OS2\SYSTEM\MPTN;
  • HELP=C:\OS2\SYSTEM\MPTN;C:\OS2\SYSTEM\MPTN\HELP;
  • SET NLSPATH=C:\OS2\SYSTEM\MPTN\MSG\NLS\%N;C:\TCPIP\msg\ENUS850\%N;
  • SET ETC=C:\OS2\SYSTEM\MPTN\ETC
  • RUN=C:\OS2\SYSTEM\MPTN\BIN\CNTRL.EXE
  • CALL=C:\OS2\CMD.EXE /Q /C C:\OS2\SYSTEM\MPTN\BIN\MPTSTART.CMD >NUL
  • REM RUN=C:\OS2\SYSTEM\MPTN\BIN\VDOSCTL.EXE

Script Changes

I changed "MPTSTART.CMD" to:

@ECHO OFF
IF NOT EXIST C:\OS2\SYSTEM\MPTN\BIN\SETUP.CMD GOTO NBSETUP
INETWAIT 1>NUL
IF ERRORLEVEL 1 GOTO END
CALL C:\OS2\SYSTEM\MPTN\BIN\SETUP.CMD
:NBSETUP
IF NOT EXIST C:\OS2\SYSTEM\MPTN\BIN\NBSETUP.CMD GOTO END
CALL C:\OS2\SYSTEM\MPTN\BIN\NBSETUP.CMD
:END


Testing

I tested the GUI programs to check my assigned IP, plus some of the commands to test it was working.

TCPIP

This folder contains some important TCP/IP components and some other useless binaries from IBM's network on the 90's.

It seems that I was able to move it without any negative impact on the OS.

'Config.sys changes

  • REM DEVICE=C:\OS2\SYSTEM\TCPIP\bin\vdostcp.sys
  • LIBPATH=C:\OS2\SYSTEM\TCPIP\DLL;
  • PATH=C:\OS2\SYSTEM\TCPIP\BIN;
  • HELP=C:\OS2\SYSTEM\TCPIP\HELP;
  • BOOKSHELF=C:\OS2\SYSTEM\TCPIP\HELP;
  • SET NLSPATH=C:\OS2\SYSTEM\MPTN\MSG\NLS\%N;C:\OS2\SYSTEM\TCPIP\msg\ENUS850\%N;

'Scripts changes

tcpstart.cmd needs to be changed pointing to the new path.


Testing

  • Firefox keeps working :)
  • "TCP/IP Configuration" GUI keeps working.

Other Notes

Config.x

Remember to update config.x with the new paths/libpats/run/etc. This is the config.sys file that loads when you boot OS/2-eCS in command line mode with Alt+F1 and F2 option.

Things that I will like to test

* DOS/WIN16: I don't use DOS and Win16 , so maybe it will be a good idea to check if something broke on that part.