Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Old IBM installer woes

7 views
Skip to first unread message

pronews/2user

unread,
Dec 30, 2009, 6:25:43 PM12/30/09
to
Hello all.

In the last few days I finally decided to install some software on my
eCS partition on this notebook, having noticed eCS is fairly stable on
it (just have to try ACPI 3.17/3.18, but all works well until now,
except for USB; only the fan is a little too loud, compared to the XP
install).

Too bad I seem unable to install any program which relies on the old
IBM OS/2 Installer.

PMView, Embellish, CERES Sound Studio and many other programs complain
there's not enough disk space. This may be due to the big volumes I
set for eCS install (circa 2 GB) and for apps/data volume (over 80
GB).

I feel that the correct solution would be unpacking all the software
and trying to repack it, maybe via WarpIN to replace the old
installer.

Some ideas anyone?

TIA
Mentore

Dave Yeo

unread,
Dec 30, 2009, 7:01:01 PM12/30/09
to

A quick fix would be to install them to a ram drive to unpack.
Don't forget about the installer not being able to handle spaces in
pathnames.
Dave

Trevor Hemsley

unread,
Dec 30, 2009, 8:19:12 PM12/30/09
to
On Wed, 30 Dec 2009 23:25:43 UTC in comp.os.os2.apps, ProNews/2 User wrote:

> I feel that the correct solution would be unpacking all the software
> and trying to repack it, maybe via WarpIN to replace the old
> installer.

There was a program called spacehog that would allocate dummy empty files to use
up free space so that you could do installs like this. Once installed you can
remove the spacehog files. Hopefully it's still on hobbes.

--
Trevor Hemsley, Brighton, UK
Trevor dot Hemsley at ntlworld dot com

Lars Erdmann

unread,
Dec 31, 2009, 10:12:59 AM12/31/09
to
Do you by chance have a C: drive that is unaccessible (for example because it is NTFS) but otherwise not hidden ?
In that case, you need to hide that drive.
An alternative is to set environment var EPFINSTDIR that determines where temporary files are to be created (normally the installer tries to create them on the C: drive if it is visible).
This solution has the drawback that the catalogue (IPFIS.INI) of what products are installed via IBM installer will be recreated at the location pointed to by EPFINSTDIR.

Lars

ProNews/2 User schrieb:

Steven Levine

unread,
Dec 31, 2009, 11:11:29 AM12/31/09
to
On Thu, 31 Dec 2009 15:12:59 UTC, Lars Erdmann <lars.e...@arcor.de>
wrote:

Hi guys,

> Do you by chance have a C: drive that is unaccessible (for example because it is NTFS) but otherwise not hidden ?
> In that case, you need to hide that drive.
> An alternative is to set environment var EPFINSTDIR that determines where temporary files are to be created (normally the installer tries to create them on the C: drive if it is visible).

If the error is EPFIE602, try pointing EPFITMPDIR to a directory to
hold the temporary files. This is usually sufficient.

Steven

--
---------------------------------------------------------------------
Steven Levine <ste...@earthlink.bogus.net>
eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com
---------------------------------------------------------------------

Mentore

unread,
Dec 31, 2009, 9:17:55 PM12/31/09
to
On Thu, 31 Dec 2009 15:12:59 UTC, Lars Erdmann <lars.e...@arcor.de>
wrote:

> Do you by chance have a C: drive that is unaccessible (for example because it is NTFS) but otherwise not hidden ?


> In that case, you need to hide that drive.

Maybe this is the real problem. The C: and F: volumes are reserved to
a Windows system (which I'm not using anymore; after an official
upgrade, it simply stopped booting, and I'm finding it more useless
time after time).

Mentore

Lars Erdmann

unread,
Jan 1, 2010, 5:49:01 AM1/1/10
to
Steven Levine schrieb:

> On Thu, 31 Dec 2009 15:12:59 UTC, Lars Erdmann <lars.e...@arcor.de>
> wrote:
>
> Hi guys,
>
>> Do you by chance have a C: drive that is unaccessible (for example because it is NTFS) but otherwise not hidden ?
>> In that case, you need to hide that drive.
>> An alternative is to set environment var EPFINSTDIR that determines where temporary files are to be created (normally the installer tries to create them on the C: drive if it is visible).
>
> If the error is EPFIE602, try pointing EPFITMPDIR to a directory to
> hold the temporary files. This is usually sufficient.
>
> Steven
>
Hi Steven,

you always have the ultimate solution :-)

Lars

Steven Levine

unread,
Jan 1, 2010, 11:47:32 AM1/1/10
to
On Fri, 1 Jan 2010 10:49:01 UTC, Lars Erdmann <lars.e...@arcor.de>
wrote:

Hi Lars,

> you always have the ultimate solution :-)

If only that were true more often. :-)

Allodoxaphobia

unread,
Jan 1, 2010, 11:58:14 AM1/1/10
to
On 01 Jan 2010 02:17:55 GMT, Mentore wrote:
>
> Maybe this is the real problem. The C: and F: volumes are reserved to
> a Windows system (which I'm not using anymore; after an official
> upgrade, it simply stopped booting, and I'm finding it more useless
> time after time).

Many of us would consider an un-bootable Windows system
as being put to its _best_ use. :-)

Happy New Year

Jonesy

Mentore Siesto

unread,
Jan 1, 2010, 4:15:00 PM1/1/10
to
Il Fri, 1 Jan 2010 16:58:14 UTC, Allodoxaphobia
<bit-b...@config.com> ha scritto:

Well, for me I'm sure the best use for a Windows volume is to be
recycled for OS/2 :)
--
Mentore Siesto

0 new messages