is that why you are being coy about the identity of the software?
Ah, thanks for a good laugh. Great choice of words, you made my day!
I got the .zip files from a very legit-looking link posted by contributor Geek-9pm:
.
http://www.gurus.org/margy/pc-file.htm.
Sounds like the installer is looking for the different disk volume labels. Possibly if you told what the program is called, we might be able to remember (or locate) a workaround that has been discovered in the past.
The program is Pc-File, but I did not want to mention it from the start because I wish for the replies to be focused on finding a generic method, and not be program-specific, neither from the start nor in the end...
Apart from Pc-File, I'm looking to experiment with several DOS-installable old small Linux distros, downloadble as zip-files-from-diskettes too.
And, apart from this instance of already zipped diskette files, I also have an unopened set of 123-R3 (that I had to put side after I bought it, to learn & use Excel at work), about 12 disks, I'd like to find out how I should zip them (using a friend's floppy drive) onto a flashdrive, for smooth, "diskette-free" install later.
I do remember from the old days of DOS, about diskette ID requirement on some programs, but not enough to figure it out now: thank you for your interest and for your help here!
.
Regarding the current instance, here is the files list from the 3 zip files:
.
Disk 1
install.com
pcf1.zip
pkunzip.exe
readme.doc
vendor.doc
.
Disk2
dbrpt.exe
fconvert.exe
msherc.com
pcg2.exe
pclabel.exe
pcpack.exe
read.me
setu.com
[additional file are 2 sample databases]
.
Maybe you can help elucidate the disk ID process? (Oherwise, I'm wondering if the documentation and the install.com program are wrong, and it is not supposed to copy the files from disk 2, i.e.you should copy them manually).
The doc says disk 3 is an additional, documentation disk which you are supposed to copy manually. Please note I'm not simply trying to run PC-file here, I'm trying to work out the install process in general, which should load disk 1 then disk 2 from within the install program. Then I could apply this to the other programs I mentioned above.