> On Jul 18, 2016, at 2:34 AM, Louis Santillan <lpsan...@gmail.com> wrote:
>
> On Sun, Jul 17, 2016 at 5:21 PM, Dimitris Zilaskos <dimitr...@gmail.com>
> wrote:
>
> […]
>
>> Is there a recommended strategy to get FreeDOS installed on such an ancient
>> system? Did some research and tried several bootdisks that float around,
>> nothing worked quite like FreeDOS 1.0.
>
> If you're willing to test FDI 1.2, download the beta boot floppy [0],
> and the cdrom iso [1]. Make sure the boot floppy can recognize your
> two hard drives and your CD-ROM. Add drivers and edit
> autoexec.bat/fdconfig.sys as necessary (especially wrt to ensuring
> CD-ROM access). Install FD 1.2 beta. `sys c:` at the end of your
> install.
>
> [0] http://dnld.lod.bz/FDI-2016-07-17-0.pre.zip
> <http://dnld.lod.bz/FDI-2016-07-17-0.pre.zip>[1]
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/cdrom.iso
>
> <http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/cdrom.iso>
Louis is correct. Once you get the FDI 1.2 Preview floppy to boot and access
your CD-ROM,
you should be able to run the installer. If the included driver (UDVD2) does
not work with your
drive, you to hunt down an alternate driver or even vendor specific driver for
your hardware.
There are a couple of other drivers in the old FreeDOS 1.1 Repository. These
have been
removed from version 1.2 for various reasons. But, you could try UIDE [2],
XCDROM [3] or
GCDROM [4].
If you have a functioning non-FreeDOS boot disk (like MS-DOS 5) that can access
your
CD-ROM, you could try booting it and then sticking in the FDI floppy and CD.
Then manually
run the SETUP.BAT. Assuming that works, you would have problems when you reboot
the
installed system.
If everything else fails, you could try the the spare disk install method. It
is mentioned in the
FDI Readme [5]. More or less, you copy everything from one of the USB images to
a spare
hard drive root directory using another computer. The put that drive in the
computer where you
want to install FreeDOS and run the SETUP.BAT. The spare drive should NOT be
the drive
where you want to install FreeDOS. Normally, FDI will not permit you to install
from and to
the same drive. Trying to override this behavior using FDI in advanced mode is
NOT
recommended and can cause very unpredictable results.
Just a note on the 1.2 Repository CD-ROM [1]. Building the CD can place a heavy
load on
the server for several minutes. So, when packages in the 1.2 repo are updated,
building
of this image is postponed until the end of the day. This process is completely
automated
and is self maintaining. When packages have changed, a new repo CD will be
automatically
created and be posted at approximately 0300-0315 EST the next morning.
Generally, this
image is not updated at release time. But, it takes care of itself within 24
hours.
There are static CD [6], SLIM [7], USB [8] and Latest Floppy [9] that are
created at release time.
these are also available on ibiblio [10]. The packages on these images are not
updated
once a Preview or Release is issued.
All released versions use the same version of FDI. However, the booted system
configuration
can vary slightly. The biggest difference is the Floppy image. Unlike the
others, it loads
disk caching software at startup to increase the performance when running FDI
from a
real floppy drive. FDI itself is unchanged from one format to another.
So, for instance, you could pull the BOOT.IMG from RepoCD [1]. Write it to a
real floppy disk.
Grab the SLIM USB [7] image and write it to a USB stick. Then boot the floppy
and either
just let FDI run. Or, exit FDI. Switch to the USB stick. Remove the Floppy,
Then run
SETUP.BAT. The result should be the same. (Although, FDI does a couple things
differently when you run it manually.)
[2]
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/util/uide.zip
<http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/util/uide.zip>
[3]
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/util/xcdrom.zip
<http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/util/xcdrom.zip>
[4]
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/util/gcdrom.zip
<http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1/repos/util/gcdrom.zip>
[5] https://github.com/shidel/FDI/blob/master/README.md
<https://github.com/shidel/FDI/blob/master/README.md> or
http://dnld.lod.bz/FDI-README.md <http://dnld.lod.bz/FDI-README.md>
[6] http://dnld.lod.bz/FDI-CD.iso <http://dnld.lod.bz/FDI-CD.iso>
[7] http://dnld.lod.bz/FDI-SLIM.zip <http://dnld.lod.bz/FDI-SLIM.zip>
[8] http://dnld.lod.bz/FDI-USB.zip <http://dnld.lod.bz/FDI-USB.zip>
[9] http://up.lod.bz/FDI/latest <http://up.lod.bz/FDI/latest>
[10]
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/previews/
Jerome
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
