Ok, I certainly will try to do so this evening. Thanks for staying with me here....I am close to giving up out of pure frustration.

I decided to individually copy each file from a command line. I started with a file called CBF.DAT -it's 3 Bytes...while copying from
/home/user/RAID/CBF.DAT
to
/mnt/floppy I get no errors.

Then I tried CBF.exe, which is 461KB. I get this error:

cp: writing `/mnt/floppy/CBF.exe': Input/output error

The next file is called 'disk1'- 5Bytes. No errors

Next file is idecoi.dll, 288KB

I get this:

cp: writing `/mnt/floppy/idecoi.dll': Input/output error

Etc, etc.....

Then when I do

umount /mnt/floppy

and

mkfs.vfat /dev/fd0

I get this:

mkfs.vfat: failed whilst writing reserved sector

If I try to do:

mkfs.ext3 /dev/fd0

I get this:

mke2fs 1.39 (29-May-2006)
Warning: could not erase sector 2: Attempt to write block from filesystem resulted in short write
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
184 inodes, 1440 blocks
72 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=1572864
1 block group
8192 blocks per group, 8192 fragments per group
184 inodes per group

Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Warning: could not erase sector 0: Attempt to write block from filesystem resulted in short write
Writing inode tables: done

Filesystem too small for a journal
Writing superblocks and filesystem accounting information:
Warning, had trouble writing out superblocks.done

This filesystem will be automatically checked every 30 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.

It looks like a bad floppy diskette or drive. Backup the data on the diskette in windows first, then run badblocks on it to scan the disk for errors (you'll need to be root / use sudo for this):

Can you post the output of that command here? If there's too much output, try without the -v option.

It is possible that when Windows is copying data to the drive it is not verifying that the copy is error free. To test this, copy data to the diskette, then run a checksum on the diskette copy it and make sure the copy doesn't contain errors (comparing the result of the checksum with the checksum result from the original file).

-SIGH-

SOlved!.... in spite of my own stupidity. If I had just simply changed

/dev/fd0 /mnt/floppy auto user,sync,exec,rw 0 0

to

/dev/fd0 /mnt/floppy auto user,async,exec,rw 0 0


right off the bat like was suggested, I would have been done 2 days ago!

Thanks so much for your patience and help.

-SIGH-

SOlved!.... in spite of my own stupidity. If I had just simply changed

/dev/fd0 /mnt/floppy auto user,sync,exec,rw 0 0

to

/dev/fd0 /mnt/floppy auto user,async,exec,rw 0 0


right off the bat like you suggested, I would have been done yesterday! Now I can cp from command line or drag and drop to the floppy...changes are committed on umount of the floppy. Odd that "sync" does not work!

Thanks so much for your patience and help. It really means a lot, having such a helpful community.
(I tried to change the thread name to include "SOLVED", unsuccessfully)

It is strange that sync doesn't work. It might be an idea to make a bug report to your distro's bug tracker. Glad it's sorted out though.