The "BASE" is nothing else than a set of packages, they are not
different from any other packages (besides the fact that they have been
elected as being part of "BASE"). These packages can be removed,
installed and updated at will. That's the whole point of having packages.
For instance,
On Fri, Sep 11, 2015 at 9:40 AM, Jerome E. Shidel Jr. wrote:
>
> However, that being said. The BASE is the BASE and should not be removed
> by a package manager. It should always be there. :)
Except when you want or need to update BASE (like in upgrading from FD
1.1 to 1.2
> On Sep 11, 2015, at 10:51 AM, Mateusz Viste wrote:
>
> On 11/09/2015 16:39, Jim Hall wrote:
>> (...) then use FDNPKG or
>> UNZIP afterwards to install the other packages that you want.
>
> To avoid confusion, I will add that using UNZIP is not a one-to-one
> alternative to
> On Sep 11, 2015, at 12:58 PM, Mateusz Viste wrote:
>
> The "BASE" is nothing else than a set of packages, they are not
> different from any other packages (besides the fact that they have been
> elected as being part of "BASE"). These packages can be removed,
> installed
Will we implement an "advanced" setup?For example,after the welcome
screen,we could give the user two options:
1.Express install
2.Advanced setup
The first would be the user friendly setup,and the second would allow the
user to manually choose packages,and even access the command line (I think
it
Eric, I just get ...? LOL I guess you're not liking me again. (Just
kidding).
On Fri, Sep 11, 2015 at 10:31 AM Eric Auer wrote:
>
> Hi Jayden (and Mateusz and Jim and...) :-)
>
> > Will we implement an "advanced" setup? [...]
>
> > The first would be the user friendly
On Fri, 11 Sep 2015, Eric Auer wrote:
> Of course it is good to be able to reach a prompt,
> but I would not put effort in extra magic. To let
> the user manually select packages, the user could
> do a BASE install and afterwards simply run FDNPKG
> to install more of the packages which are
Hi Jayden (and Mateusz and Jim and...) :-)
> Will we implement an "advanced" setup? [...]
> The first would be the user friendly setup,and the second would allow the
> user to manually choose packages,and even access the command line (I think
> it has the prompt of X:\).This way,if the user
>> Will we implement an "advanced" setup? [...]
>
On Fri, Sep 11, 2015 at 9:30 AM, Eric Auer wrote:
>
> Of course it is good to be able to reach a prompt,
> but I would not put effort in extra magic. To let
> the user manually select packages, the user could
> do a BASE
On 11/09/2015 16:39, Jim Hall wrote:
> (...) then use FDNPKG or
> UNZIP afterwards to install the other packages that you want.
To avoid confusion, I will add that using UNZIP is not a one-to-one
alternative to FDNPKG. I strongly discourage using UNZIP to install
packages - such packages won't
Hi Mateusz,
>- the tricky part might be to make it possible to install FreeDOS on
> a system where there is already something (ie. multiboot), and make it
> actually bootable, without breaking the other stuff. Personally I
> wouldn't object if FreeDOS would just trash whatever there is
HI,
How many of you remember the DOS 6.22 install process? If possible, it
should aim for that. It's simple and straight to the point. It worked
across all platforms and got DOS up and running with minimal fuss. Once the
setup is done, after a reboot, the FreeDOS package manager can run to add
> On Sep 10, 2015, at 2:51 PM, Rugxulo wrote:
>
> Hi,
>
> On Wed, Sep 9, 2015 at 11:39 PM, Mateusz Viste wrote:
>>
>> - about RAMDisk: it might come handy indeed, but remember that
>> FreeDOS should still be able to install on old machines, ie. from a
I suggest three options:
1. Base install (Just the basic essential parts of FreeDOS)
2. Complete install (The base install of FreeDOS along with all bundled
third-party software)
3. Advanced install (Specify individual packages, install sources, etc.)
> On Tue, Sep 8, 2015 at 11:02 AM, Jerome E. Shidel Jr.
> wrote:
>>
>> Ok, I’m going to need some feedback on this.
>>
>> Especially things like:
>>
>> What I should strip out of the FDCONFIG.SYS and
>> AUTOEXEC.BAT?
>>
>> What should be
On Thu, Sep 10, 2015 at 5:10 PM, Eric Auer wrote:
> So we already have at least five use cases :-)
>
> * install from floppy XCOPY style to pre-386 computers, allowing
> the user to later add packages in a more manual way via FDPKG
>
> * install from CD / DVD / USB to
Hi Jerome, Jayden, Rugxulo, Jim, Matheusz, others! Some more thoughts:
> I don’t see a way to install the KERNEL.SYS without updating the
> boot sector. But, should always at least ask to back stuff up.
Read the output of SYS /? or the HTMLHELP page about SYS or the
readme of SYS to find such
> On Sep 10, 2015, at 9:01 PM, Eric Auer wrote:
>
>
> Hi Jerome, Jayden, Rugxulo, Jim, Matheusz, others! Some more thoughts:
>
>> I don’t see a way to install the KERNEL.SYS without updating the
>> boot sector. But, should always at least ask to back stuff up.
>
> Read
On Thu, Sep 10, 2015 at 8:54 PM, Mercury Thirteen
wrote:
> I suggest three options:
>
> 1. Base install (Just the basic essential parts of FreeDOS)
>
> 2. Complete install (The base install of FreeDOS along with all bundled
> third-party software)
>
> 3. Advanced install
> On Sep 10, 2015, at 6:10 PM, Eric Auer wrote:
>
>
> Hi, nitpicking and ideas coming up :-)
>
>> This gives the user the ability to partition and format elsewhere.
>> But, you cannot do an install without the drive C:.
>
> Actually a "live CD" mode would be nice. Give
Hi, nitpicking and ideas coming up :-)
> This gives the user the ability to partition and format elsewhere.
> But, you cannot do an install without the drive C:.
Actually a "live CD" mode would be nice. Give the user some menu
item to load a large ramdisk and install (with fdpkg / fdnpkg) a
Microsoft probably knows.I honestly have no idea.Maybe they thought it
would make it more 'user friendly'.
On Wed, Sep 9, 2015 at 8:57 PM, Antony Gordon wrote:
> Hi,
>
> I'm curious as to why a batch file and DOS 6 setup automatically initiated
> the format once the drive
> On 10/09/2015 10:51, Eric Auer wrote:
>> My personal opinion is that on 8086, you should rather use a floppy
>> distro like RUFFIDEA or BREZEL which has the "base" category already
>> pre-installed on one or a few floppies and you just XCOPY that to a
>> disk of your choice manually. Imagine how
>
> On Thu, Sep 10, 2015 at 3:35 PM, Jerome E. Shidel Jr.
> wrote:
>> (Please forgive me if I misquote or misunderstand the following Jim.)
>>
>> Jim says he wants a super simple, nearly option free installer.
>> With basically two choices:
>>
>> Full install
>>
>>
On Thu, Sep 10, 2015 at 1:08 PM, Antony Gordon wrote:
> HI,
>
> How many of you remember the DOS 6.22 install process? If possible, it
> should aim for that. It's simple and straight to the point. It worked across
> all platforms and got DOS up and running with minimal fuss.
To make the Base install viable (usefully execute fdnpkg), will networking
(wattcp and/or mtcp) & shsufdrv become a part of Base?
-L
On Thursday, September 10, 2015, Jim Hall wrote:
[SNIP]
>
> 1. Do you want to install all the extra software, or just the programs
> that
Hi!
> How many of you remember the DOS 6.22 install process? If possible, it
> should aim for that. It's simple and straight to the point. It worked
As far as I remember, it was 3 floppies and only "base" software...
Also, under which conditions would it format / partition your disk?
> across
On Thu, 10 Sep 2015, Eric Auer wrote:
>
> Hi!
>
>> How many of you remember the DOS 6.22 install process? If possible, it
>> should aim for that. It's simple and straight to the point. It worked
>
> As far as I remember, it was 3 floppies and only "base" software...
> Also, under which conditions
Could you stuff the keys? It should work provided your command line to
be piped to the next program is short enough (15 chars) to fit into the
keyboard buffer.
On 9/9/2015 6:33 PM, Jerome E. Shidel Jr. wrote:
> A minor snag in development is driving me nuts.
>
> First remember:
>
>
Hi Jerome,
if you want to store temp results in your batch, you could
work with errorlevels, the FreeCOM magic errorlevel variable
or indeed a ramdrive. In the past, we often used "memdisk",
which is a BOOTABLE RAMDRIVE. That way, the installer used
a virtual floppy to boot. As you cannot
Hi,
On Wed, Sep 9, 2015 at 5:33 PM, Jerome E. Shidel Jr. wrote:
>
> Unless I’m using it wrong RDISK doesn’t work with any reliability.
> I got it to work once in my FDI building Virtual Machine.
> I never got the Floppy boot disk version to work.
>
>
> On Sep 9, 2015, at 7:32 PM, Rugxulo wrote:
>
> Hi,
>
> On Wed, Sep 9, 2015 at 5:33 PM, Jerome E. Shidel Jr.
> wrote:
>>
>>Unless I’m using it wrong RDISK doesn’t work with any reliability.
>>I got it to work once in my FDI building
> On Sep 9, 2015, at 7:08 PM, Mercury Thirteen wrote:
>
> Could you stuff the keys? It should work provided your command line to
> be piped to the next program is short enough (15 chars) to fit into the
> keyboard buffer.
It’s an interesting thought. I also thought
> On Sep 9, 2015, at 8:03 PM, Eric Auer wrote:
>
>
> Hi Jerome,
>
> if you want to store temp results in your batch, you could
> work with errorlevels, the FreeCOM magic errorlevel variable
> or indeed a ramdrive. In the past, we often used "memdisk",
> which is a BOOTABLE
I honestly don't think it really matters,as long as it installs the OS in a
neat,efficient user friendly-ish way.
On Wed, Sep 9, 2015 at 6:03 PM, Jerome E. Shidel Jr.
wrote:
>
> > On Sep 9, 2015, at 7:08 PM, Mercury Thirteen
> wrote:
> >
> > Could
Hi,
No solutions here, only some ranting :)
- the tricky part might be to make it possible to install FreeDOS on
a system where there is already something (ie. multiboot), and make it
actually bootable, without breaking the other stuff. Personally I
wouldn't object if FreeDOS would just
Hi,
I'm curious as to why a batch file and DOS 6 setup automatically initiated
the format once the drive was selected.
On Wed, Sep 9, 2015, 9:28 PM Jerome E. Shidel Jr. wrote:
>
> > On Sep 9, 2015, at 8:03 PM, Eric Auer wrote:
> >
> >
> > Hi Jerome,
> >
Ok, I’ve decided that I will probably build the installer, or at least a working
prototype that could be used for installer.
Sorry, to anyone who may have been considering doing it.
But, as Mercury Thirteen said:
"That would probably be the most efficient solution, yes. :)”
First things first,we should try remaking the installer.We are trying to
better the installer,right?Why not create a new UI for the installer and
make it more efficient?Perhaps better package handling routines?Just some
ideas I am tossing around.
On Tue, Sep 8, 2015 at 11:02 AM, Jerome E. Shidel
Ok, I’m going to need some feedback on this.
Especially things like:
What I should strip out of the FDCONFIG.SYS and AUTOEXEC.BAT?
What should be included in the FDI Boot Floppy?
How does the Installer LOGIC.txt look?
40 matches
Mail list logo