Re: mcopy <filID> a: 'stuck' after initial fail ?

On 2007-11-17, Dave {Reply Address in.Sig} <noone$$@llondel.org> wrote:
In message <1195316841.296475@xxxxxxxxxxxxxxxx>, problems@gmail wrote:

If I do a
mcopy <filID> a:
without a diskette inserted, I obviously get the error message.

But ! when I then insert a good diskette, where
mdir a:
is OK, I get: : "Can't open /dev/fd0: Read-only file system
Cannot initialise 'A': "

Also mount ..... shows 'Read-only'.

This is on FC1. Why does mature software still have bugs ?
Probably most new boxes don't even have fd0?
I can't reboot and lose all my setting, just to clear this
bug and I need to move stuff via fd0 to another box.

What should I do ?

Have you tried remounting fd0 as r/w? Aer you sure the write-protect tab
isn't set wrong on the disk itself? It could even be a fault in the drive
that thinks it is.

mdir and mcopy don't require fd0 to be mounted. It could be the root
filesystem that needs to be remounted rw.

.