The subject sounds simple doesn't it? We'll see....
My task is to take a collection of bios, firmware, and driver files,
compress them, wrap a license agreement around them and post them on
the web for download. When the user runs the downloaded executable, I
present them with the option to make individual floppy disks from the
compressed file so they can pick and choose which files they want to
extract. For example, they might just want to make a bios disk and
forget about the drivers.
Of course, there are some limitations:
1) I do not have a license to redistribute any DOS files, so I can't
bundle choice.com in the package.
2) The software I distribute is not public domain, so I can't
redistribute any files that are covered under the GNU license (which
eliminates Free DOS).
3) The user is expected to run the executable file on a windows-based
PC to make the floppy disks.
4) This has to be done without paying for any new software licenses,
can't violate copyright law, and I can't put my software into the
public domain as defined by the GNU license.
5) The user can't be expected to open and edit any of the batch files
So far, I have all of this working with a series of batch files:
1.BAT creates the BIOS disk on drive A:
2.BAT creates the firmware disk on drive A:
All the user has to do is type in the correct number and they get the
disk they want. The problem is that some users don't have a floppy
drive designated as "A:". They use external USB floppy drives that
can be any drive letter. I
-could- create 100+ little batch files that cover every drive letter
from A to Z for every disk option, but the user menu would be too
large and confusing.
Given these limitations, how can I let the user designate the
appropriate drive letter for the floppy disk or somehow figure out
what drive letter is assigned to the floppy disk and then use that
drive letter to extract the files appropriately?