Nope, no documentation...
That was the verdict at the time when we looked into this... And the question is if you want to break stuff yes or no...
Roderick, I understand completely your intention not to move OS/2 system dirs. But, from the current POV it might have been a good point of time to do so in the early days of eCS. That would have created a new standard, which would be fully accepted in this time.
Do you have similar thoughts (just out of curiosity)?
Years ago when we worked on eCS 1.1 or 1.2 we looked at the directory structure. Sadly I only remember the conclusion we where wondering if we would not open up Pandora's box.
We had some cases where we found fixed paths... One example I remember now that has floated around in my head this topic.
Please check:
\ecs\install\rsp\migrate.cmd
Comment: /* remove syslevelfiles to make sure IBM installer doesn't choke */
What I remember is that the peer installer when you have it installed on the boot drive and then do a miigrate of the network installation to another drive the peer installer would blow up.
The reason was it was also checking the BOOT drive. So your bootdrive for example is drive C: and you reinstall networking support to drive D:.
The instaler would allways check boodrive\IBMLAN. While not a path fix its an example of fixed path code left...
Martin already bumped into two problems one with MPTS and the other with UNICODE.SYS. My only point is how many other older applications this could simply break...
Apps you might not have access to...