"Brent L. Bates" <[log in to unmask]> wrote:
> That I don't know.  It took me a long while just to figure out that I
> needed to use `dd' with an image file as input and directing the output
> to the floppy device.  The device driver package we have had a number of
> individual files, .o's, etc.  We first tried copying the .o's, etc. to a
> mounted floppy drive and that didn't work.  One of the files was about
> 1.5-1.7 MB in size.  At first I thought that was too big to fit on a
> 1.44MB floppy, but 1.44MB is the capacity after a file system isinstal-
> led.  The floppy actually has more room than that.  I tried dd'ing the
> file to the floppy and it didn't croak.  I then tried using it as a
> driver disk and that worked.
>
> Check to see if any of the driver files is about the right size for a
> floppy image file and just try dd'ing to a floppy.
>
> I went digging to find the driver files we used and found them.  We had
> a file with the following extensions on it:
>
>   .img.gz
>
> The file is described as a `DUD file'.  I `unzipped' the file and then
> used `dd' to copy it to a floppy.
>
> I never did find a definition of a `DUD' file.  I simply guessed at what
> it was based on what little information I could find.
>
> I hope this is of some help.  Good luck.

It's a lot of help, Brent, thanks.  With your and Martin's comments I've
now got some procedural tools with which to start addressing my problem.

- Dushan