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 natively boot DOS
from network, CD, DVD or BluRay, you have to use a virtual
boot disk for those anyway. Memdisk gives you the advantage
that the virtual boot disk is a writeable ramdrive floppy.

Memdisk is a bit more esotheric compared to using a floppy
image to directly make a CD or similar bootable, but both
methods work on most BIOS variants. As more and more users
have a BIOS which can boot from USB stick or SD cards, the
whole problem can be sidestepped with a bootable USB / SD.

Disadvantage of both methods is that the files inside the
boot "floppy" are less visible and less editable to people
who want to tune the boot CD / DVD image to their needs,
they tend to overlook the floppy image and / or lack the
tools needed to edit it, although free tools are available
for all common operating systems :-)

Cheers, Eric



PS: Why does FORMAT C: need pipes? You do not want to hide
messages and if you worry about confirmation requests, I
personally vote AGAINST automated saying yes to FORMAT C:
(also, our FORMAT has a command line option for that...).

> If no writeable file system is present, DOS throws many errors
> and cannot redirect the data from one program to another.

Many? Only if you try to explicitly use pipes ;-)


------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to