[Discussion] OO204 startup problem with LVM

[mwizard99 at comcast.net]

In <courier.466E9D39.00005264 at mail.abiliba.net>, on 06/12/07 
   at 08:16 AM, mwizard99 at comcast.net said:

>In <courier.466E9C03.000010E4 at mail.abiliba.net>, on 06/12/07 
>   at 08:06 AM, mwizard99 at comcast.net said:

>>In <20070612052325.3848V75QS1 at priv-edmwaa06.telusplanet.net>, on 06/11/07

>>   at 10:25 PM, "Dave Yeo" <daveryeo at telus.net> said:

>>>On Mon, 11 Jun 2007 22:50:00 -0500, mwizard99 at comcast.net wrote:

>>>>0[H:\usrdlls]dir lib*.dll
>>>>
>>>>The volume label in drive H is HPFS2-H.
>>>>The Volume Serial Number is 3FCB:35DF.
>>>>Directory of H:\usrdlls
>>>>
>>>> 4-14-04   4:37p    356330           0  LIBC05.DLL
>>>> 5-05-07  11:00p     48120           0  libc06.dll
>>>> 5-05-07  11:00p     48120           0  libc061.dll
>>>> 5-05-07  11:00p   1349060           0  libc062.dll
>>>> 7-17-05   4:08p    912103           0  LIBC06R1.DLL
>>>>        5 file(s)    2713733 bytes used
>>>>                   1307883 K bytes free
>>>>
>>>>Opening the libc062.dll, at offset 012B000, you can find x'13', c'kLIBC
>>>>version 0.6.2'
>>>>
>>>>This all suggests to me that libc062.dll is properly installed on my
>>>>system.  Would you conclude the same, or is there another test that I can
>>>>run?
>>>>
>>>>I've checked the program directory, and all the DLL's you mention above
>>>>are there.
>>>>
>>>>Any other ideas that I might look into?

>>>Probably won't make a difference but you might want to update to libc063
>>>which includes a forwarder for libc062 (and 061 and 060). Seems libc062
>>>was slightly buggy. You'll need to install it for things anyways.
>>>ftp://ftp.netlabs.org/incoming/gcc/libc-0.6.3-csd3.zip
>>>Dave

>>Dave,

>>There doesn't appear to be a gcc subdirectory in the incoming directory.

>>All I see is a samba file in the incoming directory.

>>It seems to be in the pub/gcc subdirectory.  I'll download that one. 
>>Please let me know if there is a different one that I need.

>Dave,

>I've installed the new libraries, and it hasn't changed my problem.

>I'm hanging on to the change though since they contain bug fixes.

>I appreciate the help.

Everyone,

I think my problem is now solved.  eCS support had supplied me with an
LVM.DLL through their ticket system.  This is the DLL that I used in my
initial work that changed the LVM problem RC from 2, to 191.

I have since used the warpupdates website lvm14105 update to LVM as the
source of the LVM.DLL.  Once I replaced the eCS support supplied DLL with
the one from the aforementioned package, OO now seems to come up fine.

So, yes, I can definitely vouch to the fact that 00 2.0.4 for OS/2 will
run on an older Warp4 system, as the eCS team has already mentioned in the
past.

I would encourage everyone to support eCS and buy the support for 002.0.4
and use the product.

For everyone who helped me out, I want to give you a very sincere thank
you.

regards,
-Mark
--