Hi Bernd,
it seems even on modern hardware unpacking FreeCOM
during install may take VERY long, so we need a fix:
This seems to be specific to the old installer (v3.7.8 by Jeremy) I
think, as that unpacks entire packages. Sourcecode modification would be
required to add a -x source/*.
Op 11-4-2012 20:02, Rugxulo schreef:
Users will always need sources, esp. if they share, but they don't
necessarily need to unpack them. (Well, anyways, they probably don't
have all compilers anyways.)
The entire idea of opensource was to be able to modify sources to suit a
person's needs.
Hi,
On Wed, Apr 11, 2012 at 1:24 PM, Bernd Blaauw bbla...@home.nl wrote:
Op 11-4-2012 20:02, Rugxulo schreef:
The entire idea of opensource was to be able to modify sources to suit a
person's needs. Most people, including me, haven't got enough interest
or experience to be a programmer, but
Hi Bernd,
it seems even on modern hardware unpacking FreeCOM
during install may take VERY long, so we need a fix:
- it is good to have source and binary in one zip
- but you can use info-zip's command line options
(-x source/*) to exclude sources from unzip :-)
- a default install does not
actually I would not even OFFER a boot menu item to skip loading the
XMS driver at all: You cannot even boot the install CD / USB on old
pre-XMS PC.
Probably a bad idea for compatibility reasons, unless you offer multiple
choices for which XMS manager to install. E.g., I have a computer
the no-drivers choice, No. 4, is provided because some
programs, such as PLoP, will not load at all unless there
are *no drivers* loaded, at least on my system...
PLoP chokes on any drivers in freedos 1.1, saying:
cannot run under windows in a dos box, in effect.
i kid you not.
Have you tried explicit I=- and X=- commands with
JEMM386/JEMMEX??
I've tried several different JEMM options -- none of them fixed the problem on
that particular computer. I finally just gave up and went to other
alternatives.
Op 10-4-2012 18:21, Eric Auer schreef:
it seems even on modern hardware unpacking FreeCOM
during install may take VERY long, so we need a fix:
This seems to be specific to the old installer (v3.7.8 by Jeremy) I
think, as that unpacks entire packages. Sourcecode modification would be
required
Op 8-4-2012 19:44, Michael B. Brutman schreef:
Some of us figured out that on ancient hardware (8088, 80286, etc.) the
decompression process takes a long time. If you are running in a
virtual machine and your underlying hardware/operating system does not
fully support virtualization then you
On 4/3/2012 1:18 AM, Michael Robinson wrote:
There is a syntax error message that flashes before the where to install
freedos to and from menu comes up. Another problem, install freezes at
installing command.com. Uge!
Are you installing on old hardware or in a virtual machine?
Some of us
There is a syntax error message that flashes before the where to install
freedos to and from menu comes up. Another problem, install freezes at
installing command.com. Uge!
--
Better than sec? Nothing is better than
Hi,
On Tue, Apr 3, 2012 at 1:18 AM, Michael Robinson
plu...@robinson-west.com wrote:
There is a syntax error message that flashes before the where to install
freedos to and from menu comes up. Another problem, install freezes at
installing command.com. Uge!
I'm pretty sure it was agreed
12 matches
Mail list logo
