blob: ff32c217c5a7f0209558167de7a5a052c1210f40 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
<article lang="&language;" id="floppy">
<title>Floppy</title>
<articleinfo>
<authorgroup>
<author>&Alexander.Neundorf; &Alexander.Neundorf.mail;</author>
<!-- TRANS:ROLES_OF_TRANSLATORS -->
</authorgroup>
</articleinfo>
<para>
The floppy ioslave gives you easy access to the floppy disk drives
installed on your system.
</para>
<para>
The drive letter becomes the first subdirectory
in the floppy &URL;. Let's say there is a file <filename>logo.png</filename> on your floppy
disk in drive A, then the &URL; will be <userinput><command>floppy:</command><replaceable>/a/logo.png</replaceable></userinput>
</para>
<para>
If you want to access drive B, <userinput><command>floppy:/b</command></userinput> will do it.
<command>floppy:/</command> is a shortcut for <command>floppy:/a</command>.
</para>
<note><para>Note that <command>floppy:/logo.png</command> means you have a disk drive
named <filename>logo.png</filename>.</para></note>
<para>
To use it you need to have the mtools package
installed, and the floppy ioslave supports everything the various mtools
command line utilities support. You don't have to mount your floppy disks,
simply enter <userinput>floppy:/</userinput> in any &kde; 3.x app and you will be able to
read from and write to your floppy drive.</para>
<para>
It also works with USB sticks, ZIP and JAZ drives.
You can use <command>floppy:/u</command> for the USB stick and <command>floppy:/z</command> for the zip drive, for example.
To make this work, you might need to adjust your <filename>/etc/mtools</filename> file. See the manpage
for documentation.
</para>
<para>The ioslave gives read and write access to the floppy drive, but not
simultaneously. While you can read and write to the floppy during the same
session, reading and writing have to happen one after the other, not at the same
time.</para>
<para>Author: Alexander Neundorf <email>[email protected]</email></para>
</article>
|
