[Discussion] OO204 startup problem with LVM

[mwizard99 at comcast.net]

In <courier.4669B2D0.00002940 at mail.abiliba.net>, on 06/08/07 
   at 02:44 PM, mwizard99 at comcast.net said:

>In <E1HwhqC-0005f8-00 at pop-cowbird.atl.sa.earthlink.net>, on 06/08/07 
>   at 09:39 AM, "Steven Levine" <steve53 at earthlink.net> said:

>>In <courier.46696FD4.0000467A at mail.abiliba.net>, on 06/08/07
>>   at 08:52 AM, mwizard99 at comcast.net said:

>>Hi,

>>>Linking an application with a partitioning service (and
>>>isn't installed on many Warp4 clients out there.) doesn't seem logical to
>>>me.

>>There you go, making assumptions again.  Have you actually tried to
>>understand what lvm.dll does?

>>>It seems that when runing with LVM people are either problem prone or
>>>they are not.

>>Almost everyone running MCP and eCS is using LVM.  I sure one or two
>>adventurous souls have removed it for one reason or another.  The number
>>of end users still running non-LVM Warp4 systems are in the minority. 
>>Can you point me at a large number of recent problem reports regarding
>>LVM issues?  Frankly, I know more folks that have problems with Disk
>>Druid and its ilk.

>>>troubles with LVM and it prevents (albiet temporarily I believe) them
>>>from properly running their system.

>>This is mostly an education issue. 20 years ago folks had similar
>>problems getting used to Boot Manager.  Before that it was fdisk.

>>>They have no troubles with LVM, and use it without hesitation, and
>>>probably with little trouble.

>>Nothing is perfect.  I've fixed systems with LVM issues.  However, I try
>>to avoid living my life in fear of what might go wrong.  I asses the
>>benefits and the costs and take reasonable precautions and move forward.

>>>I run the risk of falling into the problem prone
>>>category should I install this on my system just for OO use.

>>No one that knows anything has said you need to convert your system to
>>LVM volume management to use OOorg.

>>>The OO docs and ecomstation website do not mention the LVM requirement,

>>Which docs?  From read1st.txt

>><snip>
>>- Use LVM to query drive-types in file-open dialog.
>></snip>

>>>though they mention the UCLIP and the other lib package which are
>>>provided in the download.

>>I'd suspect the doc was written with eCS users in mind.  LVM is not an
>>add-on component for these users.

>>>And in my opinion, I shouldn't
>>>have to have found that site before ordering the package, if I had read
>>>the ecomstation pages on OO.

>>I recommend you discuss this with Mensys.  I don't get to edit their
>>website content all that often.

>>>1. Install LVM and configure my drives with it.

>>Not a requirement.

>>>2. Cancel my intended usage of OO204 since I don't have the LVM
>>>requirement.

>>This is a choice you can make.

>>>3. Defer the use of 00204 on OS/2 until such a time as I have an LVM
>>>system (and someday I will), or the ecomstation folks

>>This is a choice you can make.

>>>(You, Chuck, and
>>>others) opt to rework that code to remove the LVM requirement.

>>As you suspect, this is not going to happen.

>>>(I note
>>>your suggestion above that tells me the rework is unlikely.)

>>Agreed.  There's no reason to remove the features it provides.  If enough
>>Warp4 users request it, perhaps the features will be make optional.

>>>In the mean time, ecomstation support is still looking at my problem and
>>>trying to help me out.

>>Odd.  The answer is simple and the os2bbs pages tells you exactly what to
>>do.  Perhaps they are busy.

>Steven,

>Please clarify.  It seems that you are implying that I can install LVM on
>my Warp4 system and allow Open Office to use it.  

>But I don't have to run it or configure any of my drives after I've done
>the manual install?

By the say, my read1st.txt file does not contain the line you refer to
above.

Regards,
-Mark
--