OS2 World Community Forum

OS/2, eCS & ArcaOS - Technical => Setup & Installation => Topic started by: Martin Iturbide on July 21, 2014, 04:44:51 am

Title: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 21, 2014, 04:44:51 am
Hi

I still dream of a next version of eCS (or anything else) that improves the directories structure to have a more clean C:\ root. Some years ago I wrote some suggestions like this one (Recommendation #8 – Directory and File Structure  (http://www.os2world.com/wiki/index.php/Comments_and_Suggestions_about_eComStation_User_Experience#Recommendation_.238_.E2.80.93_Directory_and_File_Structure)).

I want to know how hard will be to move some folder from the standard structure. I still dream of moving:
- DMISL
- IBMCOM
- IBMGSK
- IBMGSK40
- IBMGSK50
- IBMLAN
- LANGUAGE
- MMOS2
- MPTN
- MUGLIB
- PSFONTS
- TCPIP

Possible a good site for those folder can be under "/OS2/System".

What do you think.? Do you have any experience moving those directories? Which ones can be moved easily and which one of those are hardcoded and can not be place somewhere else?

Regards
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Dave Yeo on July 21, 2014, 05:11:37 am
I'd guess they all could be moved as long as config.sys,  the various INI files and various MPTN and other networking scripts were also updated. See x: /OS2/INI.RC  for an example of how to create OS2.INI.
The real problem is that eCS basically starts out by installing Warp v4.52 with that directory structure and changing it would be another step in the install process that might break.
BTW, I don't even have a C: drive which will screw anyone breaking in thinking its Windows. Even for a Windows install not using C: will make the system much more secure.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Ian B Manners on July 21, 2014, 07:20:37 am
The biggest hurdle is as Dave points out, its based on the Warp base.
Consider also updates which expect certain directories to exist.

Though on my own OS/2 and on the server I don't have a \TCPIP or \MUGLIB directorys, many years ago I simply moved the contents to \MPTN
and also remove all reference to \TCPIP, \MUGLIB in config and other places, or modified required values to look in \MPTN instead.

The \IBMGSK were also long deleted off my builds, SSL lives in \MPTN\BIN, DLL, and ETC.
I cant even remember what \DMISL was for now, I removed that from my boot drive at least a decade ago if not longer.

The directories are separate to \OS2 simply as \OS2 is operating system, the other directories are other packages or subsystems that are not
required for the core OS/2.

LANGUAGE and PSFONTS are the only ones that to me anyway, make more sense to be under \OS2.

\MMOS2, would be a pain to move that as I have so many links etc to packages I've installed under it. It is after all, MultiMedia.

I'm sure different people will have different ideas, and that is one of the great things about OS/2, it is flexible :)
As long as you have an idea of whats happening.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Roderick Klein on July 21, 2014, 09:08:05 am
Hi

I still dream of a next version of eCS (or anything else) that improves the directories structure to have a more clean C:\ root. Some years ago I wrote some suggestions like this one (Recommendation #8 – Directory and File Structure  (http://www.os2world.com/wiki/index.php/Comments_and_Suggestions_about_eComStation_User_Experience#Recommendation_.238_.E2.80.93_Directory_and_File_Structure)).

I want to know how hard will be to move some folder from the standard structure. I still dream of moving:
- DMISL
- IBMCOM
- IBMGSK
- IBMGSK40
- IBMGSK50
- IBMLAN
- LANGUAGE
- MMOS2
- MPTN
- MUGLIB
- PSFONTS
- TCPIP

Possible a good site for those folder can be under "/OS2/System".

What do you think.? Do you have any experience moving those directories? Which ones can be moved easily and which one of those are hardcoded and can not be place somewhere else?

Regards

I think you asked this question some time ago and from what I remember this was never done in eCS to prevent things from being broken.  Scripts and other programs.
I think this is also one of the last priorities to worry about, the directories in the OS...
And what it could break. About 8 years ago I looked at this and found about 4 to 5 items that would be broken. Most of the stuff does not use fixed paths. But why run the risk.

Again a low priority....

Roderick
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 21, 2014, 06:23:53 pm
What I want it is not necessary a priority of the rest.  But at least I can try to do it and document what it is getting broken, so in the future it can easy the job of the guys that "really" want to do it.

Nothing can go wrong if we try it on a VM and in a non-production machine.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 21, 2014, 06:32:18 pm
Hi

I started moving the "IBMGSK__" directories to /OS2/System  and fixing the paths on the config.sys.

I really never found out what "IBMGSK" is for.  According to some post from Alex Taylor some time ago they are part of MPTN and has the RSA encryption keys  and are only used by IBM HTTP server  (https://groups.google.com/forum/#!topic/comp.os.os2.misc/UyBAShzRPRs). Does other programs use them? Apache? any other server software?

Update: Andy Willis told me that "IBMGSK" is also used by "IBM Personal Communication" software.

Regards
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 21, 2014, 06:43:05 pm
About 8 years ago I looked at this and found about 4 to 5 items that would be broken. Most of the stuff does not use fixed paths. But why run the risk.

Roderick, did you documented this? did you posted somewhere? Please share the link.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Doug Bissett on July 21, 2014, 07:45:40 pm
Many years ago (before eCS was ever thought of), I played with moving a few things around. The idea, at the time, was to reduce the amount of disk space that was required for multiple boot systems, by sharing some common code. I remember that I was able to move the network stuff to a common disk, and it worked okay, but it became a PITA when it came time to update. I don't think I tried much more, because it was such a problem to try to manage it.

Moving directories to other directories (IBMGS* to the \OS2\SYSTEM directory, for example), really doesn't accomplish anything, even if it does work, so why bother?

In eCS, there is now an option to move the PROGRAMS directory off of the boot drive. I highly recommend doing that (it should never have been placed on the boot drive in the first place). There is also an option, in the WarpIn installer, to put the default directories (TOOLS, and PROGRAMS) onto a different drive, and I have not, yet, seen a problem with using the same directories on multiple boot systems. I have also moved eCUPS to a common drive, with no trouble.

My main objective was to remove stuff from the boot drive, that really doesn't belong there (ie, it is not actually part of OS/2). The exercise is not complete. There are still things on the boot drive, that really shouldn't be there, but the arcihitecture of the system limits what can be done, and most of what is left is not much of a problem. The main advantage is that installing a new version of eCS, is very much simplified. The main disadvantage, is that I need to remember to do WarpIn installs from both boot systems, to keep the WarpIn databases up to date.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: ivan on July 21, 2014, 07:51:03 pm
Martin, I'm sorry but I just don't understand what you are trying to do.

Moving those directories around id not going to save space so why bother?  The standard boot partition we use is less than 1 GB in size and that includes a few things we have added to the standard OS/2 install disk image ( cups, java, snap tools, utility and warpin ). 

For us 'programs' is a different partition as is 'data'.  We chose this because it makes backups very easy and by having images of the various partitions in both their 'first installed' state and 'when something changes' after that.  Restoring after system or disk failure is usually less than 2 hours including replacing failed parts.

What you are trying to do has the appearance of rearranging the deck-chairs on the Titanic - may look nice but is useless in improving the OS.  The examples you give in 'Recommendation #8 – Directory and File Structure', make me wonder if you have ever looked in the 'windows' directory - it is a mess much worse that anything seen on OS/2 and any flavour of Linux isn't much better.  To follow the windows way and dump everything on the boot partition (I know win7 does create a hidden boot partition if you let it) is just asking for trouble, something IBM were careful to try and avoid when they designed OS/2.

My thoughts can be summed up as, 'if it is working then there is no need to fix it'.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 22, 2014, 12:05:20 am
It seems that we have different concepts of what "User Experience" means.  While I like having the most basic directory structure on the root drive there are other people that just like to have dozen directories on the root. I disklike FHS like I told on the past, and YUM/RPM just make the root drive worst, so I want to move things a little bit.

"If it is working, don't fix it" works fine for some guys, and it is good policy for a business critical enviroment. But I want to give it a try to move the directories on my test enviroments and document it here. I'm not putting a gun on your heads to also do it or to help me with it, I'm just experimenting.

People have tried this on the past, but they haven't really documented it, where are the problems? which INI files do you have to change to make it work? What directories are unmovable? If you think that it is useless, low priority, waist of time, just move on to the next forum thread, that is not helping me to document this.

Tell me which directories do you think are un-movable and why for example.

Regards.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 22, 2014, 12:14:33 am
Hi Ian.

It seems that "C:\DMISL" was also a no brainer. I moved it to "C:\OS2\SYSTEM\DMISL" and changed the config.sys to "SET DMIPATH=C:\OS2\SYSTEM\DMISL\BIN".... But I'm not sure what it does either. The SLDB.DMI file was recreated again on the next eCS boot on the new directory.

Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: guzzi on July 22, 2014, 02:07:59 am
Interesting...
http://www.stardock.com/temp/kwilas/merlin/rootdir.htm
Almost as if Martin wrote it)
DMISL I -think- is an intel interface standard fro network cards. Not sure though.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Dave Yeo on July 22, 2014, 04:26:01 am
Quote
DMISL I -think- is an intel interface standard fro network cards. Not sure though.

Seems more to do with remote administration, at least my Warp v4 system has remoterr.mif installed under \dmisl\bin\mifs.
A bit of Googling shows https://en.wikipedia.org/wiki/Desktop_Management_Interface (https://en.wikipedia.org/wiki/Desktop_Management_Interface) which seems to be about this interface, though from IBM rather then MS.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Roderick Klein on July 22, 2014, 08:22:46 am
What I want it is not necessary a priority of the rest.  But at least I can try to do it and document what it is getting broken, so in the future it can easy the job of the guys that "really" want to do it.

Nothing can go wrong if we try it on a VM and in a non-production machine.

The point is you can not test it really. Its mostly down to dirty coded apps, sciripts that use hard coded paths. Besides depending on how you move this stuff around you might end up making the path/libpath length even longer... Unless you merge directories...

Roderick
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Roderick Klein on July 22, 2014, 08:24:48 am
About 8 years ago I looked at this and found about 4 to 5 items that would be broken. Most of the stuff does not use fixed paths. But why run the risk.

Roderick, did you documented this? did you posted somewhere? Please share the link.

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
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Alex Taylor on July 22, 2014, 11:34:57 am
It seems that "C:\DMISL" was also a no brainer. I moved it to "C:\OS2\SYSTEM\DMISL" and changed the config.sys to "SET DMIPATH=C:\OS2\SYSTEM\DMISL\BIN".... But I'm not sure what it does either. The SLDB.DMI file was recreated again on the next eCS boot on the new directory.

It's part of the "Problem Determination Tools" component.  Look in your "Installed Features" folder and examine "Feature Install Base" --> "Problem Determination Tools". 
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 22, 2014, 03:01:00 pm

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...

Yes !!! I'm doing this on a VM, not at someone else home's machine or a business critical environment. I want to experiment and produce some kind documentation (this forum and OS2World Wiki), what is wrong with that?
At least I plan to share the results (failure or not) with the community instead of having it locked in my mind.

What is it wrong with the collaborative spirit? People had tried differnt stuff with OS/2-eCS and never talked about it... and when someone tries it the only thing they say is "NO", without reasons, without documentation, without explaining what went wrong in detail. We need to change that. Use the Wiki, use the forum, this is not twitter, anybody is free to write more than 140 characters.

Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 22, 2014, 03:03:11 pm
The \Language directory is giving me some problems.

I'm moving it to \OS2\SYSTEM\LANGUAGE and changing the config.sys statement "ULSPATH=C:\OS2\SYSTEM\LANGUAGE" but on boot, when UNICODE.SYS loads it gaves me some errors that the files can not be found.

Maybe the path length is too much.

Regards
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Pete on July 22, 2014, 05:11:18 pm
Hi Martin

You will probably find that UNICODE.SYS has a hard coded path for \LANGUAGE which will, of course, result in "file(s) not found" error messages.


Regards

Pete
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 22, 2014, 05:49:23 pm
Hi.

According this documentation (http://www.edm2.com/index.php/The_Config.sys_Documentation_Project/DEVICE_Statements#DEVICE.3DUNICODE.SYS (http://www.edm2.com/index.php/The_Config.sys_Documentation_Project/DEVICE_Statements#DEVICE.3DUNICODE.SYS))
Unicode.SYS may have the path harcoded but only if you put the "-L" parameter to overide the Config.sys.

So, I'm not sure.

I have this Unicode.sys version.
Code: [Select]
Signature:       @#IBM:14.093#@ - Unicode DD
Vendor:          IBM
Revision:        14.93
File Version:    14.93
Description:     - Unicode DD
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 22, 2014, 07:25:37 pm
Putting "Language" aside for the moment...

It seems that "IBMLAN" is also not problematic.

I moved it (Close the active process running about it), and changed the config.sys.

Code: [Select]
     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

I'm no expert in IBM LAN Manager, but the programs still runs, I also did set Net commands and seems to work fine. It will be interesting to try to test it against other OS/2 machine on the network.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Andreas Schnellbacher on July 22, 2014, 11:28:03 pm
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)?
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 23, 2014, 06:24:28 pm
IBMCOM is giving me some problems.

Everything boots and works, network adapter and protocols, after moving the content and changing the config.sys.

But when I run "System Setup->Network->Adapters and Proptocols", it access, I click "Configure MPTS", and that moment it only shows the blank white screen that seems to be looping with something. And I need to kill the process to get out.

Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Sergey Posokhov on July 23, 2014, 07:45:05 pm
But when I run "System Setup->Network->Adapters and Proptocols", it access, I click "Configure MPTS", and that moment it only shows the blank white screen that seems to be looping with something.

Try to delete C:\IBMLVL.INI or edit it (using INI editor).
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Andy Willis on July 24, 2014, 01:01:58 am
But when I run "System Setup->Network->Adapters and Proptocols", it access, I click "Configure MPTS", and that moment it only shows the blank white screen that seems to be looping with something.

Try to delete C:\IBMLVL.INI or edit it (using INI editor).
Just using a text editor I see it has the path to my ibmcom directory.  I renamed the file and it rebuilt the ibmlvl.ini but the path now shows as:  PATH \I\IBMCOM   so you'd need to use the ini editor approach and change the path.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Sergey Posokhov on July 24, 2014, 10:25:22 am
Quote
the path now shows as:  PATH \I\IBMCOM
It should be "C:\I\IBMCOM".

"C:".
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Andy Willis on July 24, 2014, 04:50:04 pm
Quote
the path now shows as:  PATH \I\IBMCOM
It should be "C:\I\IBMCOM".

"C:".
Well, your close... had it recreated it correctly on it its own it would have been d:\ibmcom but then that was the point.  It does not recreate it correctly if you delete it and let it recreate, thus why the INI editor approach is necessary.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Roderick Klein on July 24, 2014, 06:43:00 pm

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...

Yes !!! I'm doing this on a VM, not at someone else home's machine or a business critical environment. I want to experiment and produce some kind documentation (this forum and OS2World Wiki), what is wrong with that?
At least I plan to share the results (failure or not) with the community instead of having it locked in my mind.

What is it wrong with the collaborative spirit? People had tried differnt stuff with OS/2-eCS and never talked about it... and when someone tries it the only thing they say is "NO", without reasons, without documentation, without explaining what went wrong in detail. We need to change that. Use the Wiki, use the forum, this is not twitter, anybody is free to write more than 140 characters.

Go to what I wrote and read it carefully. First of all the thing is you can test this. The only detail is you simply do not have access to all software and scripts to test this. So question is if your tests are sufficient enough to conclude that this directories moving around is something that will work  reliable.

Second as I said you might simply make the LIBPATH & PATH longer and its the question if that is something that is worth it...

The only thing that happens dis that we looked at this years ago at Mensys. And as is not a public surprise at Mensys we did not have a whole team to put conclusions we researched in a wiki of some sort. I simply remember the conclusion and wish I could have remembered the details from about 8 years ago, but thats ife..

So while I want to change it. In this case I can only tell you the details of this if I go back in time and can hear the discussion again
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Roderick Klein on July 24, 2014, 06:58:34 pm
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...

Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 24, 2014, 07:42:54 pm
Hi

I need to understand more about INI editing. Which tools do you recommend for it ?

I hope I can continue testing tomorrow.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 24, 2014, 08:01:55 pm
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...

I understand that there is variety of legacy OS/2 application that people may be using, and even that we can not find and know all of them, but I think we can document at least the most common errors on the most common apps when you try to move directories.

It may be interesting to discuss in the future which components do the community think can be scrapped for OS/2. Which is does not mean to put a gun against someone to scrap them, only to discuss it. But I want to focus on finish this moving directories experiment first.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Andreas Schnellbacher on July 24, 2014, 09:49:47 pm
I need to understand more about INI editing. Which tools do you recommend for it ?
I use Initor: http://hobbes.nmsu.edu/download/pub/os2/apps/editors/initor25.zip (http://hobbes.nmsu.edu/download/pub/os2/apps/editors/initor25.zip)
FM/2's ini editor works well, too, but I find Initor more comfortable.

The only thing one has to configure together with DragText is to add initor.exe to the DragText exceptions and activate the checkboxes for both drag and drop for lists. That re-activates initor's popup menu.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 24, 2014, 10:20:06 pm
Ohh. I found that MUGLIB path was also on IBMLVL.INI.

I will check Initor, thanks.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Greggory Shaw on July 25, 2014, 03:47:05 am
Martin could you delete the other thread.

Does eCS use the Home directory on startup ?

I've been playing around with rsync and AES, stunnel, others.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 25, 2014, 04:03:12 pm
IBMCOM:

Excelent. I just modified IBMLVL.INI with IniEditor.
I changed:
IBMLVL.INI  -> IBM_LANX -> PATH to C:\OS2\SYSTEM\IBMCOM
IBMLVL.INI  -> IBM_LS -> PATH to C:\OS2\SYSTEM\IBMLAN
IBMLVL.INI  -> IBM_UPM->PATH to C:\OS2\SYSTEM\MUGLIB.

I think that with the first one was enought for the "Adapters and Networks" GUI to start working again, but I just updated the correct paths on the rest.

It is working.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 25, 2014, 04:20:28 pm
Now, I tried PSFONTS.

To move the folder what I did was, I used the "System Setup-> Fonts" tool to first uninstall all the fonts from PSFONTS. I moved the folder to other location "C:\Resources\Fonts" on my case.  And after that I drag and drop them again on  "System Setup-> Fonts"  to install them again.

It seems to be working. But I'm not sure if that was the right way to do it.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 25, 2014, 06:52:33 pm
ok, I save the fun part for the last:

MMOS2

So I moved it to C:\OS2\SYSTEM\MMOS2.

Config.SYS Changes
    DEVICE=C:\OS2\SYSTEM\MMOS2\ssmdd.sys /S:64 /P:64 /H:256 /Q:1024 /E:1024
    DEVICE=C:\OS2\SYSTEM\MMOS2\r0stub.sys
    DEVICE=C:\OS2\SYSTEM\MMOS2\MMPLAYER\midi.sys
    DEVICE=C:\OS2\SYSTEM\MMOS2\vcshdd.sys
    DEVICE=C:\OS2\SYSTEM\MMOS2\UNIAUD32.SYS
    DEVICE=C:\OS2\SYSTEM\MMOS2\UNIAUD16.SYS /C
    LIBPATH=C:\OS2\SYSTEM\MMOS2\DLL;C:\OS2\SYSTEM\MMOS2\FREEDB;
    PATH=C:\OS2\SYSTEM\MMOS2\FREEDB;C:\OS2\SYSTEM\MMOS2;C:\OS2\SYSTEM\MMOS2\MMPLAYER;
    DPATH=C:\OS2\SYSTEM\MMOS2;C:\OS2\SYSTEM\MMOS2\INSTALL;
    HELP=C:\OS2\SYSTEM\MMOS2\HELP;
    BOOKSHELF=C:\OS2\SYSTEM\MMOS2;
    SET DSPPATH=C:\OS2\SYSTEM\MMOS2\DSP;
    SET MMBASE=C:\OS2\SYSTEM\MMOS2;
    RUN=C:\OS2\SYSTEM\MMOS2\mmfix.exe
    RUN=C:\OS2\SYSTEM\MMOS2\mididmon.exe
    RUN=C:\OS2\SYSTEM\MMOS2\mmhelpdd.exe
    RUN=C:\OS2\SYSTEM\MMOS2\qrymmcd.exe

Changed in INI Files

OS2.INI
OS2.INI -> CWMM

MMPM.INI
MMPM.INI -> MMPM2_AlarmSounds  (It has like ten values with paths to change)

MMPM2.INI
MMPM2.INI -> systemvalued -> workpath

UNIMIXPM.INI
UNIMIXPM.INI -> Program -> Name

RESOUTS:
No boot error, drivers keep loading.
System sound keeps working.
MPPM.EXE, IB.EXE, VOLUME.EXE


RESULTS - Failure
- MediaFolder and CWMM still want to load from the original location C:\MMOS2.
- Unimix died with an error attached here.
- "Sound" still points to C:\MMOS2\SOUNDS to look for sounds.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 25, 2014, 07:17:13 pm
After moving the MMOS2 folder, (and copying the ones blocked), after changing the config.sys and the INIs.

On the next boot this files remain locked on the original location. So I need to find who/where are they being turned on:
- C:\MMOS2\MEDIAFLD\BIN\mediafld.dll
- C:\MMOS2\MMCLASS\cwmm.dll
- C:\MMOS2\MMCLASS\BIN\mmres_en.dll
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Andreas Schnellbacher on July 25, 2014, 07:48:48 pm
Now, I tried PSFONTS.

To move the folder what I did was, I used the "System Setup-> Fonts" tool to first uninstall all the fonts from PSFONTS.
The complete filenames of all registered fonts are stored in OS2.INI -> PM_Fonts. It looks to me as if reregistering them is not required.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: dbanet on July 26, 2014, 02:16:15 am
After moving the MMOS2 folder, (and copying the ones blocked), after changing the config.sys and the INIs.

On the next boot this files remain locked on the original location. So I need to find who/where are they being turned on:
- C:\MMOS2\MEDIAFLD\BIN\mediafld.dll
- C:\MMOS2\MMCLASS\cwmm.dll
- C:\MMOS2\MMCLASS\BIN\mmres_en.dll

These are clearly SOM classes and WPS locks them. Anyway I wouldn't complain if Wolgemuth's classes stopped working: they are abandoned, closed source software (just like OS/2), and while I like the idea of it, I think that multimedia features of WPS should be provided by a third-party, powerful and replaceable (which means easily updateable) component, i. e. libavicodec (http://en.wikipedia.org/wiki/Libavcodec), the library that ffmpeg uses.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Greggory Shaw on July 26, 2014, 10:58:59 am
Is this new structure going to be 8.3 safe?
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: dbanet on July 26, 2014, 11:40:51 am
Is this new structure going to be 8.3 safe?

What structure? I think the subject of this topic is to determine if it is possible to move some directories from the root, but not to invent a new directory tree.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Joop on July 26, 2014, 03:55:52 pm
Is this new structure going to be 8.3 safe?
Don't understand that question because the Windows 3.1 part is within the boot drive of OS/2 and within the directory of OS/2. As it uses all, the standard installation is 8.3, what is done here is just put another directory path/name between the full name and that doesn't exceed the 8 of 8.3. So no problems here. The only problem you can get is that you are sooner through the (environment)space where programs have the full path statement of a program and some other things. With older programs this space is limited.

What Martin is trying to do has pro's and con's.  Pro is that from the root you have a simple structure, in the structure is will become a little more complicated. Backing up in a different way could be made impossible because you're going over the limit of full pathname together with name and extension. But I don't think he is going to move the Windows directory, that's already in the OS/2 directory. Its the Windows part which makes the troubles and needs insane length of pathnames, still don't know the use off that. Just go the register and ask yourself what purpose it has to go that deep.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Alex Taylor on July 26, 2014, 06:08:36 pm
Now, I tried PSFONTS.

To move the folder what I did was, I used the "System Setup-> Fonts" tool to first uninstall all the fonts from PSFONTS. I moved the folder to other location "C:\Resources\Fonts" on my case.  And after that I drag and drop them again on  "System Setup-> Fonts"  to install them again.

It seems to be working. But I'm not sure if that was the right way to do it.

OS/2 (i.e. Presentation Manager) doesn't care in the slightest what directory fonts are installed in, as the complete path to each font file is specificed in the PM_Fonts section of OS2.INI. You can install fonts to anywhere you like, even to multiple directories on multiple drives.

Now, some applications which want to do their own font lookups might default to looking in ?:\PSFONTS - for example I think Ghostscript and/or maybe gsview are by default configured to search for fonts in ?:\PSFONTS and a couple of other well-known paths, and don't use OS2.INI to search for fonts.

Some early and/or app-specific versions of fontconfig also defaulted to looking in ?:\PSFONTS, and I think one or two older versions of Java did as well. Fortunately, current fontconfig/mzfntcfgft versions are smart enough to check the INI file.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Greggory Shaw on July 27, 2014, 04:55:50 am
But I don't think he is going to move the Windows directory, that's already in the OS/2 directory...

Did I say one thing about Win ? Everything file in OS/2 has 8.3 naming.

And even Roderick tried this and said a no go. And the one thing about Os2 it hasn't changed, why change it now ?
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: dbanet on July 27, 2014, 05:54:17 am
And the one thing about Os2 it hasn't changed, why change it now ?

No one forces you to change anything.

Everything file in OS/2 has 8.3 naming.

And no, since eCS, I think, there are LOTS files not conforming to 8.3.

And even Roderick tried this and said a no go.

There I agree to you, I don't like what does he say mostly, too.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Greggory Shaw on July 27, 2014, 06:10:15 am
There I agree to you, I don't like what does he say mostly, too.

Don't Miss quote me.

What ever issue you have with him leave me out of it, he's a supporter !
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: dbanet on July 27, 2014, 06:12:08 am
There I agree to you, I don't like what does he say mostly, too.

Don't Miss quote me.

What ever issue you have with him leave me out of it, he's a supporter !

Relax, have fun. ;)
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Greggory Shaw on July 27, 2014, 06:30:18 am
Relax, have fun. ;)

Fine :)
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 27, 2014, 10:56:30 pm
It seems that moving MMOS2 did not go well here.

1) CWMM classes seems to keep looking form some DLLs on the C:\MMOS2.
I still haven't found which INIs or where does it points to this DLLs.
- C:\MMOS2\MEDIAFLD\BIN\mediafld.dll
- C:\MMOS2\MMCLASS\cwmm.dll
- C:\MMOS2\MMCLASS\BIN\mmres_en.dll

2) It seems that UNIAUD broke and some all the fixes created for eCS that are on MMOS2 stopped working. The sound keeps looping when it loads the startup sound or any sound. I remember that this was fixed some time ago on eCS, but I'm not sure what component was the one that fix it. 

3) Sound Schemes keeps pointing to the wrong location path.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Joop on July 28, 2014, 12:18:10 am
I still haven't found which INIs or where does it points to this DLLs.
d Schemes keeps pointing to the wrong location path.
I found in some Rexx scripts "mmpm2.ini".
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on July 30, 2014, 06:49:34 pm
Thanks for the replies.

I had documented the experience here on the wiki:   http://www.os2world.com/wiki/index.php/Experiment:_Moving_the_OS/2_Directory_Structure (http://www.os2world.com/wiki/index.php/Experiment:_Moving_the_OS/2_Directory_Structure)

I had failed with this two directories:
1) MMOS2
a) CWMM seems to give some problems moving it,.
b) System sounds keeps poiting to the sound scheme to the wrong locations.
c) UniAud driver sound loop bugfix got broken.

2) LANGUAGE
a) UNICODE.SYS on boot does not recognize the new location of the files.

Also testing:
DESKTOP
The desktop seems very safe to be dragged and drag and drop on other location. On my case I move it to \Home\Default\Desktop
Everything seems to work fine with it.

Maintenance Desktop
I haven't tried it yet. What do you think? do you know which INIs has its location?
I will try it later with "Maintenance Mode" and see what happens.

I want to try later movig etc, usr and var, since they are necessary of the all the RPM/YUM stuff, but I was told It was not much of a trouble moving them.


Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Dave Yeo on July 31, 2014, 05:37:57 am
Quote
Maintenance Desktop
I haven't tried it yet. What do you think? do you know which INIs has its location?

Looks like it might be /os2/install/install.ini, at least according to the rc files.
Note that rather then editing ini files, you could edit the rc files and then create virgin ini files from them with makeini, at that it seems that both os2.ini and install.ini are created from new.ini with a bit of sed magic.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: ivan on July 31, 2014, 11:47:21 am
Martin, I remember seeing an expanded dir of the ecs directory and it looked as if it was trying to emulate the os2 directory.  If that is the case why not move everything in it to the os2 directory as this eliminates one more directory.

I would also think it would be a very good idea to move the /home, /programs, /usr, /var to another partition.  Doing so will reduce the size of the boot partition considerably and gets away from the windows idea of 'everything on the root partition', although I shouldn't complain as it helps our cash flow when we have to clean up the problems it causes.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: dbanet on July 31, 2014, 07:21:10 pm
Martin, I remember seeing an expanded dir of the ecs directory and it looked as if it was trying to emulate the os2 directory.  If that is the case why not move everything in it to the os2 directory as this eliminates one more directory.

This is actually easily reachable by using original OS/2, non-eCS distribution.

I would also think it would be a very good idea to move the /home, /programs, /usr, /var to another partition.  Doing so will reduce the size of the boot partition considerably and gets away from the windows idea of 'everything on the root partition', although I shouldn't complain as it helps our cash flow when we have to clean up the problems it causes.

Yea of course, this is also of the user's business, because it's not hard to do so at all: UNIXROOT and HOME may be set to point to different location.

It is also, by the way, possible to move the hidden Nowhere directory.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on August 01, 2014, 12:40:39 am
Thanks.

To move the C:\MAINTENANCE DESKTOP directory I did something similar to the things I did with "Desktop". But this time I booted in Maintenane Mode and Drag And Dropped to the new location. On this case I moved it to C:\OS2\Maintenance Desktop.

I didn't modify the INSTALL.INI at first, and it worked, but later I noticed that on
Code: [Select]
INSTALL.INI -> FolderWorkareaRunningObjectsThere was two paths for the Maintenance Desktop, it was not giving problems, but I just erased the old one. 
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on August 04, 2014, 01:11:21 am
Now I want to check on how to move the RPM/YUM FHS structure from the "C:\" root.  (/usr, /var /tmp)

I know that RPM/YUM allows to be installed on other drive but the wpi installer always asks to install it on the root. But I'm not sure if RPM/YUM and all the programs installed on the FHS structure will work on OS/2 if I move the directories inside other folder like C:\Programs\FHS  for example.

Any thoughts? Can UNIXROOT be pointed to a specifically directory, or only to a drive letter?
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Alex Taylor on August 04, 2014, 03:34:04 am
Any thoughts? Can UNIXROOT be pointed to a specifically directory, or only to a drive letter?

It can be, but it's not recommended. According to Yuri, the packages he's ported should in theory work OK like that, but there's no guarantee that other ports will.

I tried putting it all under a subdirectory on one system... it appeared to work OK but I didn't use it extensively.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on August 04, 2014, 03:45:51 am
Thanks Alex.

Any notes on what I had to take notice before moving the directories? Any INI I had to change? any special .cmd file I don't have to forget to change to the new path?

Regards
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Dave Yeo on August 04, 2014, 04:57:36 am
Unixroot was originally designed so that it could be anywhere,  since the yum/rpm people have taken it over I don't believe there has been much thought or testing for having UNIXROOT pointing anywhere besides a root directory so whether everything will work...
Just be sure to use slashes for path separators and don't have a trailing slash, eg C:/Programs/FHS may work fine. Some ports may not like capital letters in pathnames and stay away from spaces.
Things like Odin will also need %UNIXROOT%\ lib\odininst.exe run to update the registry to the new location.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: dbanet on August 04, 2014, 10:00:34 am
You can also try explicitly specifing the locations of /usr and /var using kLIBC pathrewriters, cuz sh, for example, treats /@unixroot/usr as %UNIXROOT%\usr, but /usr as \usr. However, bash, it seems, is very broken, and doesn't understand /@unixroot/ at all...
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on August 05, 2014, 07:48:47 pm
I moved the FHS directories, and it seems that I didn't break anything (that I can notice).

I changed this on the config.sys

Quote
LIBPATH=C:\Programs\FHS\usr\lib;
PATH=C:\Programs\FHS\usr\sbin;C:\Programs\FHS\usr\bin;
SET LOGFILES=C:\Programs\FHS\var\log
RUN=C:\PROGRAMS\RSJCD\CDWFSD.EXE -p "C:/Programs/FHS/var/temp" -c20000 -b2048 -t2 -i3 -s0
SET TMP=C:\Programs\FHS\var\temp
SET TEMP=C:\Programs\FHS\var\temp
SET TMPDIR=C:\Programs\FHS\var\temp
SET UNIXROOT=C:\Programs\FHS;

After that I updated "yum-console.cmd" script and the shadow/shorcut of the "Yum Bootstrap Console".

I test it by checking of the Qt apps keeps working, checking the paths I updated and installing with YUM Qt4 Designer.  Everything is working fine so far.

This is my C:\ root drive now.

Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Andy Willis on August 05, 2014, 07:57:02 pm
I moved the FHS directories, and it seems that I didn't break anything (that I can notice).

I changed this on the config.sys

Quote
LIBPATH=C:\Programs\FHS\usr\lib;
PATH=C:\Programs\FHS\usr\sbin;C:\Programs\FHS\usr\bin;
SET LOGFILES=C:\Programs\FHS\var\log
RUN=C:\PROGRAMS\RSJCD\CDWFSD.EXE -p "C:/Programs/FHS/var/temp" -c20000 -b2048 -t2 -i3 -s0
SET TMP=C:\Programs\FHS\var\temp
SET TEMP=C:\Programs\FHS\var\temp
SET TMPDIR=C:\Programs\FHS\var\temp
SET UNIXROOT=C:\Programs\FHS;

After that I updated "yum-console.cmd" script and the shadow/shorcut of the "Yum Bootstrap Console".

I test it by checking of the Qt apps keeps working, checking the paths I updated and installing with YUM Qt4 Designer.  Everything is working fine so far.

This is my C:\ root drive now.
In theory this will probably work... the yum folks specifically state it is not a supported method (not having the unixroot set to the root of a drive) but I have not been able to think of a reason it would not work as I have considered doing something similar so that I can change the unixroot in a script to do testing.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Dave Yeo on August 06, 2014, 03:59:11 am
Boris complaining about Bash led me to look at some of the old ports of Bash 2.05 (Jun Sawataishi and Jeff Robinson) and there is code in the patches that expects UNIXROOT to equal a root or at least the second character to be :  These ports are over a decade old.
I also really think that there could be problems with using \ as a path separator as nix programs will consider it an escape character and especially scripts will die in weird ways. At least TMPDIR should use slashes along with UNIXROOT.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Dave Yeo on August 06, 2014, 04:10:02 am
Jun Sawataishi web site, http://homepage1.nifty.com/jsawa/os2/index-e.htm (http://homepage1.nifty.com/jsawa/os2/index-e.htm) including RPMs to break things :) I notice that his implementation used RPMDRV so as not to screw up ports that use UNIXOOT, one of my main complaints about the new YUM/RPM.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: dbanet on August 06, 2014, 09:39:34 am
Jun Sawataishi web site, http://homepage1.nifty.com/jsawa/os2/index-e.htm (http://homepage1.nifty.com/jsawa/os2/index-e.htm) including RPMs to break things :) I notice that his implementation used RPMDRV so as not to screw up ports that use UNIXOOT, one of my main complaints about the new YUM/RPM.

Sweet! Another unix-like env with its special settings and incompatible software builds. No, thanks.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on August 06, 2014, 02:26:56 pm
Hi.

I'm ending this experiment soon, and I had generated this basic Wiki page - http://www.os2world.com/wiki/index.php/Experiment:_Moving_the_OS/2_Directory_Structure (http://www.os2world.com/wiki/index.php/Experiment:_Moving_the_OS/2_Directory_Structure)

If it is possible I will like to hear suggestions about the two failures I had.

1) LANGUAGE. Moving this folders seems to be a problem. When "UNICODE.SYS" loads in the boot procedure it gives some errors that can not found the files that I moved.
It seems I reach a deadlock here, if someone knows more about UNICODE.SYS and can suggest something it will be appreciated.

2) MMOS2: I have this problems:
a.- CWMM seems to keep pointing to the original C:\MMOS2. This DLLs keeps pointing to the original location on the next reboot: - C:\MMOS2\MEDIAFLD\BIN\mediafld.dll - C:\MMOS2\MMCLASS\cwmm.dll - C:\MMOS2\MMCLASS\BIN\mmres_en.dll I still haven't found which INIs or where does it points to this DLLs.

b.- There used to be some audio problem with UniAud driver that made the sound to loop. It was fixed on eCS, but after moving MMOS2 the problem showed up again.

c.- On "System Setup" -> Sound, the sound schemes keeps pointing to the wrong location. There seems that I forgot to move the location from OS2SYS.INI, or I need to re-register the sound schemes to the new location.

Any comment on this subject is appreciated.

Regards
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: dbanet on August 06, 2014, 03:37:56 pm
http://www.os2world.com/wiki/index.php/Experiment:_Moving_the_OS/2_Directory_Structure (http://www.os2world.com/wiki/index.php/Experiment:_Moving_the_OS/2_Directory_Structure)

Cool! Great job!
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Alex Taylor on August 07, 2014, 04:09:38 am
1) LANGUAGE. Moving this folders seems to be a problem. When "UNICODE.SYS" loads in the boot procedure it gives some errors that can not found the files that I moved.
It seems I reach a deadlock here, if someone knows more about UNICODE.SYS and can suggest something it will be appreciated.

UNICODE.SYS has the path \LANGUAGE\ path hard-coded into it (you can easily confirm this by scanning through the driver with a hex editor). Technically, it isn't the boot drive but the current working drive (at the moment UNICODE.SYS is loaded) that it looks at, but unless you're doing something unorthodox like booting from Veit's MEMDISK environment, it comes to the same thing.

So yes, I think there's nothing you can do about that.

Quote
b.- There used to be some audio problem with UniAud driver that made the sound to loop. It was fixed on eCS, but after moving MMOS2 the problem showed up again.

I believe this is what MMFIX.EXE did (loaded from CONFIG.SYS). I think David A. may have written that... you could ask him maybe.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on August 16, 2014, 11:56:24 pm
Wow,  something strange happend today to the VM I reorganized the directories.

I just left MMOS2 and LANGUAGE on the original location and moved everything else.

Since yesterday on boot, I noticed that some directories was opening automatically on the desktop after boot. I don't remember when, but it seems that the VM remembered the folders I got opened once I did some hard-reset to the VM.

So, I checked the config.sys and removed "folders" from autostart. On the next boot it broke. When it loads the desktop, it loads the background, the virtual destop areas box and it spots there. The mouse keeps working, but the two buttons at the same time do not brings the "Window List". And if I send a Ctrl+Alt+Del to the VM, it will reboot showing normal reboot message.

I'm not sure if this is complete because of the directory re-organizing or because something else. I will bring back my Vm to a previous state and test more the "Folders" on the config.sys Autostart.

Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Greggory Shaw on August 17, 2014, 12:45:33 am
Wow,  something strange happend today to the VM I reorganized the directories.

...

So, I checked the config.sys and removed "folders" from autostart. On the next boot it broke.


WPS is considered a folder, so folders must be present in 'AutoStart'. It doesn't have anything to do with your re-organizing of directories. I learned the hard way on that a long time ago.


Greggory
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: dbanet on August 17, 2014, 01:00:59 am
Martin, don't remove FOLDERS from AUTOSTART, but better add the following to CONFIG.SYS:
Code: [Select]
SET RESTARTOBJECTS=STARTUPFOLDERSONLY,REBOOTONLY
This will stop WPS from reopening folders you had opened before the shut down or reboot.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on August 17, 2014, 03:54:27 am
It seems I also learned the hard way. I put back FOLDERS and the desktop started working. Now the folders that show up on startup are gone, which is good. But another thing shows up.

I didn't moved the MMOS2 folder on this VM, but now the problem of the "Startup Audio" looping at the end for ever started to show up. I really don't know how to use MMFIX, but it seems it broke.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Greggory Shaw on August 17, 2014, 06:25:12 am

...

I didn't moved the MMOS2 folder on this VM, but now the problem of the "Startup Audio" looping at the end for ever started to show up. I really don't know how to use MMFIX, but it seems it broke.

Try moving MMFIX around and higher in CONFIG.SYS.

Here's a thread on this issue, it took some time for the right placement for me but worked !

http://comments.gmane.org/gmane.org.netlabs.uniaud.general/2321


Greggory
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on August 17, 2014, 02:57:58 pm
Hi Greg

I moved the MMFIX to the top of the config.sys RUN statements and it didn't fix the issue.

Plus, I think I confused something later and the folders keep showing when the desktop loading. Does anybody knows where the setting to auto-open folders on boot are stored?

Regards.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Andreas Schnellbacher on August 17, 2014, 07:44:52 pm
Assumed that you use the RESTARTOBJECTS entry as Boris wrote, you may have multiple startup folders defined.

See OS2.INI -> PM_Workplace:Startup. Prepend a 3 to the key name to get the hex. WPS handle of the startup folder. Compare that with Startup -> Properties -> Icon -> Details... -> Object handle.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Greggory Shaw on August 23, 2014, 09:59:09 am
Martin Have you started on removing extra stuff yet ?  Like extra MACS or VAR\CID etc.

Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Greggory Shaw on August 24, 2014, 10:51:09 pm
Martin on your sound looping problem, I am very interested in what REMming out:

RUN=x:\MMOS2\ QRYMMCD.EXE

does and if anyone that gets the hang of the WPS with only the mouse pointer showing does it go away.


Greggory
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on August 25, 2014, 11:52:41 pm
I tried today the Experimental VM and the sound stopped looping. I don't remember doing any change yet...  and I have not rem out the "RUN=C:\MMOS2\qrymmcd.exe" yet.

I still have some folder that auto opens. I'm checking those right now to see what is happening.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Martin Iturbide on August 25, 2014, 11:57:58 pm
Thanks Andreas.

I checked "OS2.INI -> PM_Workplace:Startup"... I didn't understand the stuff there, so I deleted the two values inside it. On the next boot the folders that auto opened where gone.
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: dbanet on August 26, 2014, 12:21:14 am
I checked "OS2.INI -> PM_Workplace:Startup"... I didn't understand the stuff there, so I deleted the two values inside it.

 ;D ;D ;D
Title: Re: Re-organizaing OS/2-eCS Directories.
Post by: Andreas Schnellbacher on August 27, 2014, 12:21:43 am
I checked "OS2.INI -> PM_Workplace:Startup"... I didn't understand the stuff there, so I deleted the two values inside it. On the next boot the folders that auto opened where gone.
One entry should remain. It's that one from the current startup folder. If you use XWorkplace's startup folder(s), you don't need it, of course.

Some steps of my previous post explained (I use Initor):

1. OS2.INI -> PM_Workplace:Startup

-> This ini application has the key name 'C779' on my system. Its value is '59 00 00', which stands for  the letter 'Y', followed by 2 zero terminators.

-> You get the corresponding WPS handle of that startup folder if you prepend a 3 to the key name. That gives the hexadecimal WPS object handle '3C779'.

2. The next step is to open the properties of your current startup folder and to find the WPS handle there. (This works only if you have eWP or XWP installed.)

-> Open the properties dialog of it. Select the 'Icon' tab. Press the 'Details...' button.

-> In the tree under 'Details' you find the item 'Object handle'. It shows in my case '0x3C779'.

-> That is exactly the handle from the key name I got from OS2.INI -> PM_Workplace:Startup.

If you have more than one Startup folder entries, you should remove the wrong one(s) and keep the only correct one.