b***@gmail.com
2017-06-24 04:36:39 UTC
Hi:
I guess I could develop this topic privately with
Arca support, who have been very prompt and helpful,
but I think it would serve our community much more
being public.
I have a franken system dating from OS/2 3.0, and
updated with newer packages including 4.52, eCS 2.1 and
2.2. I like the way it is, and I did not like many of
the UI changes brought forth since 3.0, many which I
considered a feeble response to the Windows 95 and the
ilk.
My drives date back to the old days when a full OS/2
install took about 30 MB, and all the boot partitions
had to be within the first 1024 cylinders.
Subsequently, with new installations, I was able to
increase my HPFS boot partition sizes using PQPM
(Partition Magic), and I made a new 600 MiB partition
for eCS 2.1.
This all seemed to suffice until now attempting to
install ArcaOS. My T60 has a 512 GiB SSD, and I
thought I would install on the 600 MiB JFS partition.
However, no matter what I tried, ArcaOS minimally
requires a 1000 MiB partition to continue installing.
I guess the 1024 boot requirement is obsolete. So, I
then considered making a new partition at the end of
the drive. I am pretty sure that PQPM (DOS boot) would
not work with my drive and JFS. I thought I was hooped
until I saw 'Resize' on the install root menu. {:-)
However, 'Resize' would not work anywhere on the SSD
drive. It appears somewhat ironic to me that ArcaOS
seems to be oriented more to supporting legacy
hardware, when it requires (drive) resources which
legacy systems do not have. Especially on a 'Custom
Install', the limitations should be circumventable.
My primary desire for getting ArcaOS installed was
to steal the new Panorama video driver, so (maybe) OS/2
could get the proper 1920X1080 24 bit video that the
legacy XP drive supports, as my T60 is limited to
1680X1050 on the external monitor.
I could see that my attempt to hack Panorama in from
the WPI files was doomed, so I thought I would use ANPM
to cleanly do it. I installed the ANPM WPI from the
DVD, but it miserably failed, as it required several
external libraries and applications, and I could see
that it was only a VX-REXX wrapper for WPI and YUM. I
am not a big fan of dependencies, and I see them as a
continuing and confusing problem for OS/2.
As it stands, I would like to install ArcaOS
separately, and steal useful parts for my main OS
partition. From reading user reports, I am not
confident that ArcaOS would/could supplant my current
system. The two immediate fixes that I would like to
see, are the removal of the 1000 GiB installing
requirement, and fixing "Resize".
thanks!
Baden
I guess I could develop this topic privately with
Arca support, who have been very prompt and helpful,
but I think it would serve our community much more
being public.
I have a franken system dating from OS/2 3.0, and
updated with newer packages including 4.52, eCS 2.1 and
2.2. I like the way it is, and I did not like many of
the UI changes brought forth since 3.0, many which I
considered a feeble response to the Windows 95 and the
ilk.
My drives date back to the old days when a full OS/2
install took about 30 MB, and all the boot partitions
had to be within the first 1024 cylinders.
Subsequently, with new installations, I was able to
increase my HPFS boot partition sizes using PQPM
(Partition Magic), and I made a new 600 MiB partition
for eCS 2.1.
This all seemed to suffice until now attempting to
install ArcaOS. My T60 has a 512 GiB SSD, and I
thought I would install on the 600 MiB JFS partition.
However, no matter what I tried, ArcaOS minimally
requires a 1000 MiB partition to continue installing.
I guess the 1024 boot requirement is obsolete. So, I
then considered making a new partition at the end of
the drive. I am pretty sure that PQPM (DOS boot) would
not work with my drive and JFS. I thought I was hooped
until I saw 'Resize' on the install root menu. {:-)
However, 'Resize' would not work anywhere on the SSD
drive. It appears somewhat ironic to me that ArcaOS
seems to be oriented more to supporting legacy
hardware, when it requires (drive) resources which
legacy systems do not have. Especially on a 'Custom
Install', the limitations should be circumventable.
My primary desire for getting ArcaOS installed was
to steal the new Panorama video driver, so (maybe) OS/2
could get the proper 1920X1080 24 bit video that the
legacy XP drive supports, as my T60 is limited to
1680X1050 on the external monitor.
I could see that my attempt to hack Panorama in from
the WPI files was doomed, so I thought I would use ANPM
to cleanly do it. I installed the ANPM WPI from the
DVD, but it miserably failed, as it required several
external libraries and applications, and I could see
that it was only a VX-REXX wrapper for WPI and YUM. I
am not a big fan of dependencies, and I see them as a
continuing and confusing problem for OS/2.
As it stands, I would like to install ArcaOS
separately, and steal useful parts for my main OS
partition. From reading user reports, I am not
confident that ArcaOS would/could supplant my current
system. The two immediate fixes that I would like to
see, are the removal of the 1000 GiB installing
requirement, and fixing "Resize".
thanks!
Baden