Thank you for the reply.
I now have a more puzzling problem. I can read floppies, but I cannot determine the filesystem of the boot disk! So, I can't copy it, etc.
I can read the "rescue disk." However, there is a tar.gz file and then several files in an unknown format. So... I have no idea how this will ever "rescue" me.
I guess this is my punishment for downloading the "free" (no support) version of Icepack (which seems like a pretty good package, though, as far as I can tell).
Well, I have done a lot of searching and reading to understand this problem and I will write below what I found out since I notice other people have posted similar questions about floppy disks in the past.
I am using the KDE desktop. There is a "right click" option to mount the floppy (on the floppy icon), which must be used after the floppy is put in the drive. After using the floppy, it must be "unmounted," which can also be done via the right-click menu.
However, because the floppy is assigned to "owner" in the fstab file (under "etc"), it can only be mounted and unmounted when logged as "root" I think.
Mounting can also be done via a command prompt. But here is something weird, bash does not recognize the "unmount" command, even though it recognizes the "mount" command, at least from the default directory I get when I open a Konsole. So, to unmount I had to use the "right click" menu on the desktop icon for the floppy disk.
After all this, it seems that my earlier post was not specifically correct. The floppy >does< work when mounted. It picks up the file system "automatically," because it is set to "auto" in the fstab file.
HOWEVER, the filesystem on the boot disk created at the time of install apparently is unknown to the auto system. I tried to "mount" the floppy drive using the name of every filesystem I could find (it is not easy to find such a list) and in each instance it wouldn't mount. When I used "auto" I was told that I had to "specify the file system".
I don't like the prospect of having to "reinstall" in the event the floppy disk goes bad, so I will have to do more research to figure this problem out.
And ... move on to the next two problems, first being how to get the hard disk to boot without the floppy; second being to get the SB Live sound card working. (It was properly identified during setup, but no sound.)
The boot problem may be insurmountable. For hardware reasons, I put the linux on "Drive D," which is on the "master" of the secondary controller, making it the third drive, I guess.
Something I read said that the boot image had to be on one of the first two drives, so I may be out of luck on this. I thought I would "get lucky" since my BIOS allows me to specify "D" as the boot drive, but so far -- no.
Naturally, if you've got solutions for any of these problems, I'll appreciate the info!