Sergie wrote:
>
> > > To make ONE diskmaker for ALL users is a real challenge. I would never make
> > > assumptions about the user's operating system or configuration or even their
> > > path, for instance. How do we create config.sys and autoexec.bat that takes
> > > into account the users' choices for memory managers and caching software ?
> >
> > > I'll probably be still thinking about it after the interest has
> > > disappeared.<G>
>
> OK. I born this discussion, seems like i should to kill it.
> I am really do not understand what is problem with different
> configurations.
> There is no any problem.
> All that user must have, that's enough RAM for ram disk.
> Everything else should not matter.
> If Arachne runs only in memory, and we don't need
> any stackers, dblspaces and so on, what's problem.?
> User's dos transferred to floppy with sys, it must exist in
> any dos packages. And we do not need to care about memory
> managers and caching software, cos when user booted from
> disk with Arachne it do not need them anyway.
Hi Sergei;
Yes we DO care about memory managers and caching software and ramdisk drivers
and THAT'S where it gets complicated. You can't boot and RUN Arachne from floppy
without that stuff. Well, if it's 100% on ramdisk maybe we can lose the caching
software but that would have speeded up the boot process and might be useful for
copying some stuff back to floppy.
If you just want to LOAD arachne from a floppy onto your OWN system then it's
no problem. If you want to make a portable and bootable floppy with Arachne on
it and you are going to manually write your own boot config.sys and autoexec
and then manually determine what might work in the other computer when you get
there then it's no problem.
If you want something universal then there is some complication.
- Clarence Verge
--
- Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
--
