Hi, I've noticed an annoying thing when writing to floppies. OK, say I'm in a hurry......... I would mount the floppy , and write to it. Then I wait for floopy activity to stop, and issue a umount command and remove the floppy. Sometimes it dosn't get fully written. It seems that the kernel just decides when it wants to write it, sometimes it's right away, and sometimes it waits. How can I force it to do the write immediately? -- use Perl; #powerful programmable prestidigitation
O
Hi, I've noticed an annoying thing when writing to floppies. OK, say I'm in a hurry......... I would mount the floppy , and write to it. Then I wait for floopy activity to stop, and issue a umount command and remove the floppy.
Sometimes it dosn't get fully written. It seems that the kernel just decides when it wants to write it, sometimes it's right away, and sometimes it waits.
How can I force it to do the write immediately?
Hi, Another solution is to use mtools. This works if your floppy is formatted as FAT. I found that it writes immediately and you do not have to mount the drive to put the data there. Just another way of doing it Marshall "Nothing is impossible, We just do not have all the anwsers to make the impossible, possible."
The 02.11.27 at 10:03, zentara wrote:
I've noticed an annoying thing when writing to floppies. OK, say I'm in a hurry......... I would mount the floppy , and write to it. Then I wait for floopy activity to stop, and issue a umount command and remove the floppy.
The umount command should not return till the floppy has really finished writing and can be safely removed. I usually just copy things, and then (immediately) umount. When I get the prompt back, the floppy stops spinning and I extract it. It has never failed for me. -- Cheers, Carlos Robinson
participants (4)
-
Carlos E. R.
-
Dan Am
-
Marshall Heartley
-
zentara