What is a problem, is the desire to automate things. For cdrom this is easy, as all files are in one location.
For diskettes, programs are loaded on different disks.
disk 1 would be bootdisk
but since you don't want to swap disks too often, it also should contain at least the Fdisk program.
disk 2 would then contain the Format and Install programs, and the batchfiles guiding them.
disk 3 and further would be the data disks.
problem is, that upon the last data disk, we wish to execute another batchfile (to setup config.sys for example, or translate programs in your selected language).
For this, we must first continue the batchfile located on disk 2.
I don't like this (would require after installing the last disk, inserting disk2 again just to execute 1 line of code).
solution would be a Ramdisk to store the batchfile below, but unfortunately Tdsk does not work very well with command.com (auto-detect the drive-letter assigned to Tdsk)
@echo off rem disk2.bat install.exe /parameters rem other disks are inserted now. rem this last line of code below requires you to insert disk2 again... rem or put the calling batchfile on each diskette... c:\%dosdirectory%\post-installation-script.bat
Bernd
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
