Thanks to all.
Solved.
It was a multiple cause issue:
1st: BIOS Setting was incorrect (had to enable 1.2MB 5.25 rather than
3.5 which was it set to - an oversight in the firts place, that occured
to me).
2nd: Cable issue: I had a combined cable (3.5 connector at the end and
edge
from Christoph Kukulies k...@kukulies.org:
Thanks to all.
Solved.
It was a multiple cause issue:
1st: BIOS Setting was incorrect (had to enable 1.2MB 5.25 rather than 3.5
which was it set to - an oversight in the firts place, that occured to me).
2nd: Cable issue: I had a combined
On Sat, 02 Oct 2010 10:50:00 +
Thomas Mueller mueller6...@bellsouth.net articulated:
from Christoph Kukulies k...@kukulies.org:
Thanks to all.
Solved.
It was a multiple cause issue:
1st: BIOS Setting was incorrect (had to enable 1.2MB 5.25 rather
than 3.5 which was it set
Hi Christoph,
In the end it turns out that the floppies that were lying in a drawer
for 19 years, are producing read errors.
Do NOT throw them out.
I have a tool that can rescue near all data.
http://berklix.com/~jhs/src/bsd/jhs/bin/public/valid/
Cheers,
Julian
--
Julian Stacey: BSD
I'm in the need of reading some data from old 5.25 floppy media (1.2MB).
I lent 2 drives from neighbour institutes at the university and after
having recalled that the
floppies have to be enabled in the BIOS I'm now seeing the fd0 device in
dmesg (FreeBSD 8.0 RELEASE).
I can do a dd
On Fri, 01 Oct 2010 15:04:40 +0200, Christoph Kukulies k...@kukulies.org
wrote:
I'm in the need of reading some data from old 5.25 floppy media (1.2MB).
I lent 2 drives from neighbour institutes at the university and after
having recalled that the
floppies have to be enabled in the BIOS
On Fri, 1 Oct 2010, Christoph Kukulies wrote:
I'm in the need of reading some data from old 5.25 floppy media (1.2MB).
I lent 2 drives from neighbour institutes at the university and after having
recalled that the
floppies have to be enabled in the BIOS I'm now seeing the fd0 device in
dmesg
